Behavioral completeness
| Line 1: | Line 1: | ||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://esinyqynyso.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]= | ||
| + | ---- | ||
| + | =[http://esinyqynyso.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
From {{Ref|1}}: | From {{Ref|1}}: | ||
| − | + | <blockquote>Each software object not only knows the properties of the real-world entity that it represents, but also knows how to model the behaviour of that entity. ... We call this principle 'behavioural completeness'. This does not mean that the object must implement every possible behaviour that could ever be needed. It means that all the behaviours associated with an object that are necessary to the application being developed should be properties of that object and not implemented somewhere else in the system</blockquote> | |
==Example== | ==Example== | ||
| − | In {{Ref|1}}, an example of a Wheel object in | + | In {{Ref|1}}, an example of a Wheel object in "a simulated truck suspension system" is given: |
| − | + | <blockquote>[Each] Wheel object knows not just the dimensions and mass of a wheel, but also how to turn, to bounce, to model friction, and to pass on forces to the Axle object.These behaviours may operate continuously, or they may be specifically invoked by sending a message to the object.</blockquote> | |
==References== | ==References== | ||
Revision as of 06:27, 24 November 2010
From [1]: <blockquote>Each software object not only knows the properties of the real-world entity that it represents, but also knows how to model the behaviour of that entity. ... We call this principle 'behavioural completeness'. This does not mean that the object must implement every possible behaviour that could ever be needed. It means that all the behaviours associated with an object that are necessary to the application being developed should be properties of that object and not implemented somewhere else in the system</blockquote>
Example
In [1], an example of a Wheel object in "a simulated truck suspension system" is given: <blockquote>[Each] Wheel object knows not just the dimensions and mass of a wheel, but also how to turn, to bounce, to model friction, and to pass on forces to the Axle object.These behaviours may operate continuously, or they may be specifically invoked by sending a message to the object.</blockquote>
