Term
|
Definition
| The process of elaborating the detailed design with interaction diagrams for a particular use case |
|
|
Term
|
Definition
| standard design techniques and templates that are widely recognized as good practice |
|
|
Term
|
Definition
| type of interaction diagram that emphasizes the sequence of messages sent between objects for a specific use case |
|
|
Term
|
Definition
| types of interaction diagram that emphasizes the objects that send and receive messages for a specif use case |
|
|
Term
|
Definition
| a representation of the period during which a method of an object is alive and executing |
|
|
Term
| Separation of responsibilities |
|
Definition
| a design principle that recommends segregating classes into separate components based on the primary focus |
|
|
Term
|
Definition
| problem domain classes that must be remembered between program executions (ie require storage in a database) |
|
|
Term
|
Definition
| a relationship between packages, classes, or use cases in which a change in the independent item requires a change in the dependent item |
|
|
