|
| 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 Use Case Document Task |
| The basic flow should be completed before attempting to write alternate flows and re-structure the use case. Alternate flows and sub-flows can then be added when the overall flow is well understood. |
| If the flow is complex, then an activity diagram should be added as a guide. Supporting information and references should be added as required, but in places seperate from the flow description. |
| The Develop Use Case Document Task - © CRaG Systems 2006 - 2011 |