Term
Object-oriented design (OOD) |
|
Definition
| an approach used to specify the software solution in terms of collaborating objects, their attributes, and their methods. |
|
|
Term
|
Definition
| an object class that contains business related information and implements the analysis class |
|
|
Term
|
Definition
| an object class that provides the means by which an actor can interface with the system. Examples include a window dialogue box, or screen. For nonhuman actors, an application program interface (API)is the interface class. Sometimes called a boundary class. |
|
|
Term
|
Definition
| an object class that contains application logic. Examples of such logic are business rules and calculations that involve multiple entity object classes. Control classes coordinate messages between interface classes and entity classes and the sequences in which the message occur. |
|
|
Term
|
Definition
| an object class that provides functionality to read and write persistent attributes in a database. |
|
|
Term
|
Definition
| an object class that handles operating system - specific functionality. |
|
|
Term
|
Definition
| the level of access an external object has to an attribute or method |
|
|
Term
|
Definition
| the software logic that is executed in response to a message. |
|
|
Term
|
Definition
| the obligation that an object has to provide a service when requested and thus collaborate with other objects to satisfy the request if required. |
|
|
Term
|
Definition
| a UML diagram that models the logic of a use case by depicting the interaction of messages between objects in time sequence |
|
|
Term
|
Definition
| a condition of the object at one point in its lifetime. |
|
|
Term
|
Definition
| an occurrence that triggers a change in an object's state through the updating of one or more of its attribute's values. |
|
|
Term
|
Definition
| a UML diagram that depicts the combination of states that an object can assume during the lifetime, the events that trigger transitions between states, and the rules governing the objects transition. Also called a state chart diagram or state transition diagram. |
|
|
Term
|
Definition
| the act of simulating object behavior and collaboration by acting out an object's behaviors and responsibilities. |
|
|
Term
|
Definition
| a diagram that depicts classes that correspond to software components that are used to build the software application. |
|
|
Term
|
Definition
| the degree to which one class is connected to or relies upon other classes. |
|
|
Term
|
Definition
| the degree to which the attributes and behaviors of a single class are related to each other. |
|
|
Term
|
Definition
| a common solution to a given problem in a given context, which supports reuse of proven approaches and techniques. |
|
|
Term
|
Definition
| object framework = a set of related, interacting objects that provide a well-defined set of services for accomplishing a task. |
|
|
Term
|
Definition
| a group of objects packaged together into one unit. An example of a component is a dynamic link library (DLL) or executable file. |
|
|
Term
|
Definition
| models the interaction of objects via messages focusing on the structural organization of objects in a network format. Called a collaboration diagram prior to UML 2.0. |
|
|
Term
|
Definition
| depicts the organization of programming code divided into components and how the components interact. |
|
|
Term
|
Definition
| depicts the configuration of software components within the physical architecture of the system's hardware "nodes". |
|
|
