|
| 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 Requirements Gathering | Develop Proof of Concept Prototype Task |
| Proof of concept prototyping is generally about discovering all the elements that need to be on the interface and labelling and grouping them in a way that is intuitive for the user. Use a simple drawing tool rather than a GUI development tool. You are specifying the interface, not designing it. Do it in a workshop with the stakeholder and in parallel with developing the use case description. |
| If the interface becomes too large or cluttered, then it will need to be broken down. This will usually necessitate reworking the use case description to fit the new flow requirements introduced by adding more parts to the interface. |
| Suggested Step Flow | |||||
![]() |
|||||
| Guidelines, Templates and Examples | |||||
|
|||||
| 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) |
|||||
The Develop Proof of Concept Prototype Task - © CRaG Systems 2006 - 2008 |