|
| Overview | Process Concepts | Process Configurations | Process Glossary | Process Map | |
|
||
| Model-Driven Development Process | ||||
|---|---|---|---|---|
|
||||
|
| Business Analysis | Requirements Gathering | System Analysis | System Architecture | Detailed Design | | Project Management | Project Support | Coding | Testing | Rollout | |
||||
| Return to System Analysis | Develop State Model Task |
| A state model is made up of statecharts: one for each class that has state dependent behaviour. Most will be children of classes in the logical data model and will model the life history of the entity. | In order to prevent developing an activity diagram, which is the logical inverse of a statechart, the statechart should be developed in the order: states, transitions, events and conditions. Actions are not necessary for the analysis as these appear in the relevant sequence diagrams. Activities should be avoided. |
| Statecharts provide a place to put certain kinds of business rule and a check of the completeness of the functional requirements in the use case model. Statecharts can also be created during business modelling as children of business data entities. |
| Suggested Step Flow | ||||
![]() |
||||
| Guidelines, Templates and Examples | ||||
| ||||
| Training | ||||
| Object Oriented System Analysis Using UML System Requirements Definition and System Analysis using Use Cases and UML Business Analysis, Requirements Definition and Systems Analysis using UML Object Oriented Analysis and Design using UML (OOAD) |
||||
The Develop State Model Task - © CRaG Systems 2006 - 2008 |