Term
|
Definition
A person or thing to which action, thought, or feeling is directed
A uniquely identifiable, attribute value bearing, instance of a class |
|
|
Term
|
Definition
A general template, “cookie cutter”, which we use to define a type of objects
Instantiating a class results in an object in the class
People or things grouped together because of their common traits or behavior |
|
|
Term
|
Definition
| the information that is used to describe the object |
|
|
Term
|
Definition
| a behavior/service/process/function that an object can perform |
|
|
Term
|
Definition
combine data (attributes) and processes (methods) into a single entity
-E.g., Faculty class
-Attributes: Name, DOB, Phone, Address, Office
-Methods: Pay parking fine, buy lunch, teach courses |
|
|
Term
|
Definition
exactly how the behavior/service is implemented is hidden
Private vs. Public |
|
|
Term
| Inheritance/Generalization |
|
Definition
| abstract the common features (attributes and methods) among multiple classes into a more general class |
|
|
Term
|
Definition
The subclass inherits attributes and methods from the superclass
“Is-A” relationship |
|
|
Term
| Abstract vs. Concrete Class |
|
Definition
An abstract class
-Does not have direct instances
-Class name font is italic
-May or may not have abstract methods
-If the method is abstract, it should be italicized
-May have concrete methods
A concrete class
-Can have direct instances
-Class name font is regular, not italic
-All methods are concrete (regular font)
-Cannot have abstract methods
-If a superclass is an abstract class, its concrete subclass must implement all abstract methods in the superclass |
|
|
Term
| Three Types of Association Relationships |
|
Definition
1) Simple Association - straight line
2) Aggregation - transparent diamond
3) Composition - black, filled in diamond |
|
|
Term
|
Definition
indicates how many objects participate in a given association relationship
1..1
1..*
*..* |
|
|
Term
|
Definition
one object knows the other and they can communicate with and send messages to each other
Requires cardinality at each end in UML |
|
|
Term
|
Definition
expresses a Part-of (Part-Whole) relationship between a component object and an aggregate object
The parts exist on their own without need for the whole |
|
|
Term
|
Definition
-A strong type of aggregation
-A Part-Whole relationship
-The part’s existence depends on the whole
-If the whole is deleted, the parts are deleted as well |
|
|
Term
|
Definition
Messages are sent between objects to trigger some services
A message is essentially a function call from one object to another object
Ex. The dean (object) calls the “makeCopy()” function/method in the secretary (object) |
|
|
Term
|
Definition
| means that the same message can be interpreted differently by different objects |
|
|
Term
|
Definition
| delays identifying the type of the object until run-time |
|
|
Term
|
Definition
1) Entity Class - hold most of the data of an application
2) Boundary Class - used by actors to interact with the system; they are the Graphical User Interface (GUI) objects
3) Control Class - coordinate the tasks and capture the main application logic in a use case |
|
|
Term
| Visibility in terms of attributes and methods |
|
Definition
Public - Any one can access it
Private - Only methods within the class can access it
Protected - Only methods within the class, or within the same package, can access it
Attributes are usually private
Methods are usually public |
|
|
Term
|
Definition
Biggest advantage of OO approach
Objects can be reused over and over in many different systems
Changes within an object will not affect other objects |
|
|
Term
|
Definition
| This approach views a system as a collection of self-contained objects, including both data and processes |
|
|
Term
|
Definition
| Collection of diagramming disciplines and documentation that defines the static and dynamic characteristics of a problem or a system |
|
|
Term
|
Definition
Class Diagram
Component Diagram
Deployment Diagram |
|
|
Term
|
Definition
| Classes and relationships between classes |
|
|
Term
|
Definition
Use Case Diagram
Sequence Diagram |
|
|
Term
|
Definition
| Diagram that documents business requirements and interactions between user and system |
|
|
Term
|
Definition
| Diagram that shows dynamic interaction of objects within a particular use case |
|
|
Term
|
Definition
| These capture the intended behavior of the system and this behavior may be expressed as services, tasks, or functions the system is required to perform |
|
|
Term
|
Definition
A person or another system that interacts with the system
Who initiates, participates in, and/or receives the result of system behavior
A role that a user plays |
|
|
Term
|
Definition
| Marks out what behavior is relevant to the modeling |
|
|
Term
|
Definition
| A process that the system performs |
|
|
Term
|
Definition
| A two-way communication between the use case and the actor |
|
|
Term
|
Definition
| This factors out behavior common to two or more actors into a parent actor |
|
|
Term
|
Definition
| This factors out behavior common to one or more use cases into parent use cases |
|
|
Term
|
Definition
A use case may be employed like a "subroutine" within another use case
The base case is not complete without its inclusion use cases |
|
|
Term
|
Definition
| A way of inserting new behavior into an existing use case |
|
|
Term
|
Definition
| what must be in place for the use case to be possible |
|
|
Term
|
Definition
| what actions occur for the use case to succeed |
|
|
Term
|
Definition
| what must be in place after this use case completes |
|
|
Term
|
Definition
| Creates branches in the main flow |
|
|
Term
|
Definition
Create alternative flows
Alternative flows capture errors, branches, and interrupts to the main flow
Alternative flows frequently do not return to the main flow
Alternative flows often have different postconditions |
|
|
Term
|
Definition
| Provides a dictionary of key business terms and definitions |
|
|
Term
|
Definition
| show the sequence of messages and events that are permitted between objects of specific classes |
|
|
Term
|
Definition
| messages that require the sender to wait until the activation caused by the message is completed |
|
|
Term
|
Definition
| messages that cause an activation in the receiver but do not require the sender to wait |
|
|
Term
|
Definition
| receiver of a message is also the sender of the message |
|
|
