Term
|
Definition
| A collection of models that can be used to capture system requirements based on use cases with the object-oriented approach. |
|
|
Term
|
Definition
| A diagram to show the various user roles and how those roles use the system. |
|
|
Term
| System Sequence Diagram (SSD) |
|
Definition
| A diagram showing the sequence of messages between an external actor and the system during a use case or scenario. |
|
|
Term
|
Definition
| The communication between objects within a use case. |
|
|
Term
|
Definition
| A model that describes classes of objects within a use case. |
|
|
Term
|
Definition
| A diagram showing the life of an object in states and transitions. |
|
|
Term
|
Definition
| A symbol used to denote a group of similar elements. |
|
|
Term
|
Definition
| Either a communication diagram or a sequence diagram that shows the interactions between objects. |
|
|
Term
| Lifeline, or Object Lifeline |
|
Definition
| The vertical line under an object on a sequence diagram to show the passage of time for the object. |
|
|
Term
|
Definition
| Part of a message between objects that is evaluated prior to transmission to determine whether the message can be sent. |
|
|
Term
|
Definition
| A condition during an object's life when it satisfies some criterion, performs some action, or waits for an event. |
|
|
Term
|
Definition
| The movement of an object from one state to another state. |
|
|
Term
|
Definition
| The starting point of a state machine diagram, indicated by a black dot. |
|
|
Term
|
Definition
| For particular transition, the state to which an object moves after the completion of a transition. |
|
|
Term
|
Definition
| For a particular transition, the original state of an object from which the transition occurs. |
|
|
Term
|
Definition
| The trigger for a transition, which causes the object to leave the origin state. |
|
|
Term
|
Definition
| A true/false test to see whether a transition can fire. |
|
|
Term
|
Definition
| A description of the activities performed as part of a transition. |
|
|
Term
| Concurrency, or Concurrent State |
|
Definition
| The condition of being in more than one state at a time. |
|
|
Term
|
Definition
| A sequential set of connected states and transitions. |
|
|
Term
|
Definition
| A state containing other states and transitions.(that is, a path) |
|
|
Term
|
Definition
| Creation of an object based on the template provided by the class definition. |
|
|
Term
|
Definition
| A system that has shared resources among multiple people or groups in an organization. |
|
|
Term
|
Definition
| A type of implementation diagram that shows the overall system architecture and the logical components within it. |
|
|
Term
| Application Program Interface (API) |
|
Definition
| The set of public methods that is available to the outside world. |
|
|
Term
|
Definition
| A type of implementation diagram that shows the physical components across different locations. |
|
|
Term
|
Definition
| A class invented by a system designer to handle a needed system function. |
|
|
Term
|
Definition
| Specification of all detailed system processing for each use case. |
|
|
Term
|
Definition
| A way of categorizing a model element by its characteristics, indicated by guillemets. (<<>>) |
|
|
Term
|
Definition
| A design identifier for a problem domain class. |
|
|
Term
|
Definition
| An entity class that exists after a system is shut down. |
|
|
Term
| Boundary Class or View Class |
|
Definition
| A class that exists on a system's automation boundary, such as an input window. |
|
|
Term
|
Definition
| A class that mediates between boundary classes and entity classes, acting as a switchboard between the view layer and domain layer. |
|
|
Term
|
Definition
| A class that is used to retrieve data from a database. |
|
|
Term
|
Definition
| A notation of whether an attribute can be directly accessed by another object; indicated by plus or minus signs. |
|
|
Term
|
Definition
| A notation that shows all of the information needed to invoke, or call, the method. |
|
|
Term
|
Definition
| A method with one name but two or more parameter lists. |
|
|
Term
|
Definition
| A method that is associated with a class instead of with objects of the class. |
|
|
Term
|
Definition
| An attribute that contains the same value for all objects in the system. |
|
|
Term
|
Definition
| A method in a subclass (with inheritance) that overrides the method in the parent class. |
|
|
Term
|
Definition
| A class that can never be instantiated. (no objects can be created of this type) |
|
|
Term
|
Definition
| A normal class that can be instantiated. (objects can be created) |
|
|
Term
|
Definition
| A design principle in which one object has a reference to another object and thus can interact with it. |
|
|
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 principle in which a set of standard objects can be used repeatedly within a system. |
|
|
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
| A qualitative measure of how closely the classes in a design class diagram are linked. |
|
|
Term
|
Definition
| A qualitative measure of the consistency of functions within a single class. |
|
|
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 design principle in which an intermediate class is places between two classes to decouple them but still link them. |
|
|
Term
|
Definition
| A design principle in which objects are responsible for carrying out system processing. |
|
|
Term
|
Definition
| The process of elaborating the detailed design with interaction diagrams of a particular use case. |
|
|
Term
|
Definition
| Standard design techniques and templates that are widely recognized as good practice. |
|
|
Term
|
Definition
| A representation of the period in which a method of an object is alive and executing. |
|
|
Term
| Separation of Responsibilities |
|
Definition
| A design principle to segregate classes into separate components based on the primary focus of the classes. |
|
|
Term
|
Definition
| In a communication diagram, the connection between classes that indicates messages can be passed. |
|
|
Term
|
Definition
| A relationship between packages, classes, or use cases that indicates a change in the independent item will require a corresponding change in the dependent item. |
|
|
