|
| 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 Diagram Task |
| The ideal source for the system use case model is a business model. If this is available, then system actors and system use cases can be explicitly mapped from business actors, business workers, primitive business processes and business worker responsibilities. |
| Otherwise system actors and use cases will have to be found directly from a stakeholders understanding of the system requirements. This would normally be done in a workshop with the stakeholder. |
| The diagram cannot be fully structured until the detail of the use case flow has been developed, so don't spend a lot of time developing the diagram before developing the use case document. |
| 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 Use Case Diagram Task - © CRaG Systems 2006 - 2008 |