Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
11 Cards in this Set
- Front
- Back
State Transition Diagram
|
Final piece of info needed for describing functional requirements
identifies: -Possible states -What makes the objects change its state |
|
State transitions occur
|
-Within a Use Case
-Across Use Cases |
|
State
|
Value of some condition that happens during an objects life
semi permanent condition |
|
Object moves to a new state when
|
-External event
-Internal Change in data or time |
|
Composite state
|
has other states nested internally
|
|
Concurrent object
|
can be in more than one state at a time
|
|
Object Transitions are labeled with 3 different transitions
|
-Message- causes obj to leave and change to a new state
- [Guard-Condition]- Must be true for state to change -Action expression := happens when a transition occurs |
|
Statechart diagram
|
represents concurrent behaviors with multiple paths called threds
|
|
vertical bars (Pseudostate)
|
indicate where concurrent behavior begins or ends
|
|
Two notations to show Concurrent threads
|
-Swimlane Notation (within composite state)
-Synchronization Pseudostate |
|
Threads
|
having multiple threads in a state chart
|