|
| 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 |
Requirements Gathering Stage |
| Requirements gathering is highly iterative and based around developing use cases. There is one use case document per use case on the use case diagram. Proof of concept protoypes are developed, where appropriate, together with the use case document, usually in the same user workshop. Non-functional requirements are specified in a seperate document that should be updated as use cases are developed. The words used in all documents and models should be made consistent with the glossary as they are used. |
| If business modelling is performed then the glossary should be started during the Business Analysis Stage. If there is no business data model or the logical data model of the System Analysis Stage will not be developed in-house, then a data dictionary should also be maintained. |
| Tasks | |||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
| Templates and Examples Get .eap File Viewer/Editor | |||||
![]() ![]() ![]() |
![]() ![]() |
![]() |
![]() |
![]() |
![]() |
| Task Guidelines | |||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
| Training | |||||
| System Requirements Definition Using Use Cases 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 Requirements Gathering Stage - © CRaG Systems 2006 - 2008 |