21 terms

401 Chapter 7 - The Object-Oriented Approach to Requirements

Use Case Model
A collection of models that can be used to capture system requirements based on use cases with the object-oriented approach.
Use Case Diagram
A diagram to show the various user roles and how those roles use the system.
System Sequence Diagram (SSD)
A diagram showing the sequence of messages between an external actor and the system during a use case or scenario.
The communication between objects within a use case.
Domain Model
A model that describes classes of objects and their states.
State Machine Diagram
A diagram showing the life of an object in states and transitions.
A symbol used to denote a group of similar elements.
Interaction Diagram
Either a communication diagram or a sequence diagram that shows the interactions between objects
lifeline, or object lifeline
The vertical line under an object on a sequence diagram to show the passage of time for the object
True/False Condition
Part of a message between objects that is evaluated prior to transmission to determine whether the message can be sent
A condition during an object's life when it satisfies some criterion, performs some action, or waits for an event
The movement of an object from one state to another state
The starting point of a state machine diagram indicated by a black dot
Destination State
For a particular transition, the state to which an object moves after the completion of a transition
Origin State
For a particular transition, the original state of an object from which the transition occurs
Message event
The trigger for a transition, which causes the object to leave the origin state
A true/false test to see whether a transition can fire.
A description of the activities performed as part of a transition
Concurrency, or concurrent state
The condition of being in more than one state at a time
A sequential set of a connected states and transitions
Composite State
A state containing other states and transitions [that is, a path]