IS 401 CH. 5 (TERMS) Flashcards
use case description
a textual model that lists and describes the processing details for a use case
Preconditions
identify what the state of the system must be for the use case to begin, including what objects must already exist, what information must be available, and even the condition of the actor prior to beginning the use case.
Postconditions
identify what must be true upon completion of the use
case. Most importantly, they indicate what new objects are created or updated by the use case and how objects need to be associated. The postconditions are important for two reasons.
(1) They form the basis for stating the expected results for test cases that will be used for testing the use case after it is implemented. For example, in the Create customer account use case, it is important to test that a customer record, address record, and account record were successfully added to the database.
(2) The objects in postconditions indicate which objects involved in the use case are important for design.
system sequence diagram (SSD)
a diagram showing the sequence of messages between an external actor and the system during a use case or scenario
An SSD is a type of interaction diagram (which is 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
loop frame
notation on a sequence diagram showing repeating messages
true/false condition
part of a message between objects that is evaluated prior to transmission to determine whether the message can be sent
opt frame
notation on a sequence diagram showing optional messages
alt frame
notation on a sequence diagram showing if-then-else logic