Term
|
Definition
| an approach to software development that organizes both the problem and its solution as a collection of discrete objects; both data structure and behavior are included in the representation. |
|
|
Term
|
Definition
| refers to the fact that the data are organized into discrete, distinguishable entities called objects |
|
|
Term
| Name (reference) (handle) |
|
Definition
| the name distinguishes one object from one another |
|
|
Term
|
Definition
| groups objects that have attributes and behaviors in common |
|
|
Term
|
Definition
| has its own attribute values but shares attribute names and behaviors with the other instances of the class |
|
|
Term
|
Definition
|
|
Term
|
Definition
| simplify the hierarchy where no objects of the class may be defined except as instances of a subclass |
|
|
Term
|
Definition
| an action or transformation that an object performs or to which it subjected |
|
|
Term
|
Definition
| the same behavior may be exhibited differently on different classes or subclasses |
|
|
Term
|
Definition
| specific implementation of an operation or a certain class |
|
|
Term
|
Definition
| the ability of an object’s name, state, and behaviors to transcend time or space |
|
|
Term
|
Definition
| includes descriptions of the objects, attributes, behaviors, and relationships |
|
|
Term
|
Definition
| describe communication, control/timing, and the states and state changes |
|
|
Term
|
Definition
| describe constraints on the structure and the dynamic behavior |
|
|
Term
|
Definition
| describe particular functionality that a system is supposed to perform or exhibit by modeling the dialog of that user, external system, or other entity will have with the system to be developed |
|
|
Term
|
Definition
| entity interacting with the system |
|
|
Term
|
Definition
| brief textual sketch of how the function is performed |
|
|
Term
|
Definition
| depiction of some aspect of system functionality that is visible to the actor whose perspective is reflected by the use case |
|
|
Term
|
Definition
| extends a use case to illustrate a different or deeper perspective |
|
|
Term
|
Definition
| is actually a reuse of an already-defined use case |
|
|
Term
|
Definition
| define the entire customer process by describing the activities that the customer will peroform |
|
|
Term
|
Definition
| defines classes of objects in terms of their functions |
|
|
Term
|
Definition
| show how messages flow from one object to another |
|
|
Term
|
Definition
| use object and sequence information to show the flow of events between objects |
|
|
Term
|
Definition
| show how the classes are logically divided into modules |
|
|
Term
|
Definition
| reflect the actual, final system modules |
|
|
Term
|
Definition
| show the network links involved with the application being built |
|
|
Term
|
Definition
| when two classes occur together, and when the relationship must be preserved for some period of time |
|
|
Term
|
Definition
| when one class is part of another class |
|
|
Term
|
Definition
| a mechanism that restricts access to class members; other objects cannot see the attributes or (some) methods for that class |
|
|
Term
|
Definition
| allows access to some methods, but not to attributes, since a public attribute would violate the principle of encapsulation |
|
|
Term
|
Definition
| view the system as a small collections of packages |
|
|
Term
|
Definition
| when if two packages changes the definition of one may cause changes in the other |
|
|
Term
|
Definition
| used to describe how operations and behaviors are handled by the objects in the design |
|
|
Term
|
Definition
|
|
Term
|
Definition
| when a message is sent to itself |
|
|
Term
|
Definition
| we name each operation, the object it takes as parameters, and the values returned by the operation |
|
|
Term
|
Definition
| collection of all its operations’ signatures |
|
|
Term
|
Definition
| request is associated with an object’s particular operations at runtime |
|
|
Term
|
Definition
|
|
Term
|
Definition
| composition, no internal characteristics of the building-blocks are visible to the developer. |
|
|
Term
|
Definition
| set of related reusable classes |
|
|
Term
|
Definition
| template of abstract architectural elements that can be used to guide you in generating your design |
|
|
Term
|
Definition
| explains the situations in which the pattern would be appropriate |
|
|
Term
|
Definition
| elements of the context that vary to some degree |
|
|
Term
|
Definition
| reuse of part of a domain-specific design |
|
|
Term
|
Definition
| refers to a process in the system; it may be event-driven or time-driven |
|
|
Term
|
Definition
| is initiated when a particular event occurs |
|
|
Term
|
Definition
| invoked at a particular time |
|
|
Term
|
Definition
| knows its observers and provides and interface for attaching and detaching observer objects |
|
|
Term
|
Definition
| set of methods that might be executed in response to a message received by an object in that class |
|
|
Term
|
Definition
| number of method invocations in a class |
|
|
Term
| Data abstraction coupling |
|
Definition
| number of abstract data types used in the measured class and defined in another class of the system |
|
|
Term
|
Definition
| number of classes calling this class |
|
|
Term
|
Definition
| number of classes called by this class |
|
|
