Term
|
Definition
| Vertical rectangles on a sequence diagram that indicate when an object is executing a method. |
|
|
Term
|
Definition
| A class invented by a system designer to handle a needed system function. |
|
|
Term
|
Definition
| A class that exists on a system's automation boundary, such as an input window. |
|
|
Term
|
Definition
| A method that is associated with a class instead of with objects of the class. |
|
|
Term
|
Definition
| A qualitative measure of the consistency of functions within a single class. |
|
|
Term
|
Definition
| A class that mediates between boundary classes and entity classes, acting as a switch board between the view layer and domain layer. |
|
|
Term
|
Definition
| A qualitative measure of how closely the classes on a design class diagram are linked. |
|
|
Term
|
Definition
| A class that is used to retrieve data from a database. |
|
|
Term
|
Definition
| A standard solution template to a design requirement that facilitates the use of good design principles. |
|
|
Term
|
Definition
| A relationship among elements on package diagrams, class diagrams, and interaction diagrams that indicates which elements affect other elements in a system so that designers can track the carry-through effects of changes. |
|
|
Term
|
Definition
| A design principle of objects in which both data and program logic are included within a single self-contained unit. |
|
|
Term
|
Definition
| A design identifier for a problem domain class. |
|
|
Term
|
Definition
| A design principle in which an intermediate class is placed between two classes to decouple them but still link them. |
|
|
Term
|
Definition
| A design principle in which data associated with an object is not visible to the outside world, but methods are provided to access or change the data. |
|
|
Term
|
Definition
| Creation of an object based on the template provided by the class definition. |
|
|
Term
|
Definition
| Notations on a collaboration diagram that carry messages between objects or between actors and objects. |
|
|
Term
|
Definition
| A notation that shows all of the information needed to invoke, or call, the method. |
|
|
Term
|
Definition
| A design principle in which one object is able to view and interact with another object. |
|
|
Term
|
Definition
| A design principle in which objects are responsible for carrying out system processing. |
|
|
Term
|
Definition
| A design principle in which a set of standard objects can be used over and over again within a system. |
|
|
Term
|
Definition
| A method with the same name but two or more different parameter lists. |
|
|
Term
|
Definition
| An entity that exists after a system is shut down |
|
|
Term
| Protection From Variations |
|
Definition
| A design principle in which parts of a system that are unlikely to change are segregated from those that will. |
|
|
Term
|
Definition
| A specification of all detailed system processing for each use case. |
|
|
Term
| Separatoin of Responsibility |
|
Definition
| A deign principle in which analysts divide a class into several highly cohesive classes. |
|
|
Term
|
Definition
| A way of categorizing a model element by its characteristics, indicated by guillemets (<<>>). |
|
|
Term
|
Definition
| A class that systems designers create to serve as a collection point for incoming messages. |
|
|
Term
|
Definition
| Notation of whether an attribute can be directly accessed by another object; indicated by plus or minus signs. |
|
|
