|
| 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 | |
||||
| Incremental Process Flow Waterfall Process Flow |
System Analysis Stage |
| System analysis produces a 3-dimensional logical technology free model of everything that the system will do. This model serves as a starting point for the System Architecture Stage and the Detailed Design Stage. System analysis revolves around developing use case implementations for each use case in the increment. This involves producing a high level sequence diagram for each flow in each use case and linking them together to follow the flow of the use case. If this is the first or only increment then an initial logical data model should be produced first using class diagrams. The logical data model is then updated as part of each use case implementation. The state model consists of one statechart for each object with state dependent behaviour and can be developed and updated at any part of the stage. |
| It is preferable that this model should be produced by those with a sound knowledge of the problem domain under the guidance of system developers rather than just by system developers themselves. It is a role that would suit analyst/programmers. |
| Tasks | |||
![]() |
![]() |
![]() |
|
| Templates and Examples Get .eap File Viewer/Editor | |||
|
|||
| Task Guidelines | |||
![]() |
![]() |
![]() |
|
| 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) |
|||
| Suggested Task Flow | |||
![]() |
|||
| The System Analysis Stage - © CRaG Systems 2006 - 2011 |