Object-Oriented Modeling

Dynamic Model Concepts

Dynamic Models Evolve through the following four stages

1)Use Cases - we've discussed

2)Scenarios- A sequential list of events, An event is an incident that causes an object to change state. E.g. an object exchanges information with another object, sensor, user, etc.  An event occurs anytime information comes into the system or flows out from the system.  A scenario represents a sequence of related transactions between an actor and the system itself in the form of a dialogue.  Internal objects are also typically part of the interaction.  Scenario depict how you expect the system to be used.  They can have lots of specific details.

3) Sequence Diagrams  (aka Event Traces) - Next we identify events between objects.  An event trace can be prepared for each scenario.  Prepare sequence diagrams for your successful/normal scenarios, but keep in mind there may be anomolous scenarios that affect the development of your state transition diagrams.  Sequence diagrams are built by

        1) identifying events in Scenarios

         2) identifying the object/actor that sends an event (sends information)

         3) identifying the object/actor that receives an event (receives information)

   4. State Transition Diagrams - see link