2.11 transition rules

Editor's Note: This subsection has been added to describe an aspectof a number of Analysis and Design Methods.

Analysis and Design Methods

SA: Each class has a set of transitionrules which "specify what new state is achieved when an instance ina given state receives a particular event."

CA: Transitions rules are shown as apart of the service charts.

RA: Not explicit

JA: Not explicit

WD: Not used

MD: Not used

EA: "The events and actions thatactivate state transitions are called triggers." "A trigger givesthe conditions that, when met, may cause the transition to fire."

FA: "A life-cycle expression definesthe allowable sequences of interaction that a system may participate inover its lifetime. If at any point the system receives an event that isnot allowed according to the life cycle, then the system ignores it andleaves the state of the system unchanged. ... Life cycles are simple extensionsto regular expressions or grammars." [The method] "does not usestate machines during analysis. "

FD: A node of a state machine.

OA: 'Triggers' and 'control conditions'determine what state change takes place when an event occurs. See 9.6.'Operations' are associated with states, transitions, or both. "Thecurrent trend is to employ a combination of Mealy and Moore modeling techniques."

BD: [A] "change of state [causedby an event] is called a state transition." "Each ... event islikely to trigger some action ..." The actions are shown as text onthe state transition diagram.

HA: State transitions are modeled usingobjectcharts.

NA: Not used.

features matrixintro page