Term
| object-oriented analysis (OOA) |
|
Definition
| be reused or adapted for new uses and (2) define new or modified objects that will be combined with existing objects into a useful business computing application |
|
|
Term
|
Definition
| a technique for identifying objects within the systems environment and identifying the relationships between those objects. |
|
|
Term
| Unified Modeling Language |
|
Definition
| a set of modeling conventions that is used to specify or describe a software system in terms of objects. |
|
|
Term
|
Definition
| something that is or is capable of being seen, touched, or otherwise sensed and about which users store data and associate behavior. |
|
|
Term
|
Definition
| the data that represents characteristics of interest about an object. |
|
|
Term
|
Definition
| each specific person, place, thing, or event, a well as the values for the attributes of that object. Sometimes referred to simply as an object. |
|
|
Term
|
Definition
| the set of things that an object can do and that correspond to functions that act on the object's data (or attributes). In object-oriented circles, an object's behavior is commonly referred as a method, operation, or service (we may use the terms interchangeably throughout our discussion). |
|
|
Term
|
Definition
| the packaging of several items together into one unit. |
|
|
Term
|
Definition
| a set of object instances that share the same attributes and behaviors. Often referred to simply as a class. |
|
|
Term
|
Definition
| the concept wherein methods and/or attributes defined in an object class can be inherited or reused by another object class. |
|
|
Term
| generalization/specification |
|
Definition
| a technique wherein the attributes and behaviors that are common to several types of object classes are grouped (or abstracted) into their own class, called a supertype. The attributes and methods of the supertype object class are then inherited by those object classes(subtypes). Sometimes abbreviated as gen/spec. |
|
|
Term
|
Definition
| an entity that contains attributes and behaviors that are common to one or more class subtypes. Also referred to as abstract or parent class. |
|
|
Term
|
Definition
| an object class that inherits attributes and behaviors from a supertype class and then may contain other attributes and behaviors that are unique to it, also referred to as child class and, if it exists at the lowest level of the inheritance hierarchy, as concrete class. |
|
|
Term
| object class relationship |
|
Definition
| a natural business association that exits between one or more objects and classes. |
|
|
Term
|
Definition
| the minimum and maximum number of occurrences of one object class for a single occurrence of the related object class. |
|
|
Term
|
Definition
| a relationship in which one larger "whole" class contains one or more smaller "parts" classes. Conversely, a smaller "part" class is part of a "whole" larger class. |
|
|
Term
|
Definition
| an aggregation relationship in which the "whole" is responsible for the creation and destruction of its "parts". If the "whole" were to die, the "part" would die with it. |
|
|
Term
|
Definition
| communication that occurs when one object invokes another object's method(behavior)to request information or some action. |
|
|
Term
|
Definition
| literally meaning "many forms," the concept that different objects can respond to the same message in different ways. |
|
|
Term
|
Definition
| a technique whereby a subclass(subtype)uses an attribute or behavior of its own instead of an attribute or behavior inherited from the class(supertype) |
|
|
Term
|
Definition
| a use case that documents the interaction between the system user and the system. It is highly detailed in describing what is required but is free of most implementation details and constraints. |
|
|
Term
|
Definition
| a diagram that can be used to graphically depict the flow of a business process, the steps of a use case, or the logic of an object behavior (method). |
|
|
Term
|
Definition
| a diagram that depicts the interaction between an actor and the system for a use case scenario. |
|
|
Term
|
Definition
| a graphical depiction of a system's static object structure, showing object classes that the system is composed of as well as the relationship between those object classes. |
|
|
Term
|
Definition
| a class that describes an object that outlives the execution of the program that created it. |
|
|
Term
|
Definition
| that describes an object that is created temporally by the program and lives only during that program's execution. |
|
|
