|
| 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 System Analysis | Develop Use Case Implementation Task |
| Use case implementation is about defining the interactions between internal objects that need to take place in order to implement the functionality defined in the use case document. A class diagram is created to define the objects that will be involved in the use case implementation including system interface objects and an optional use case control object. |
| These objects are added to a sequence diagram for the basic flow and a sequence of interactions between the objects is created to implement each line in the use case description. Further sequence diagrams are created to implement each alternate flow and sub flow. These are connected together with hyperlinks to make the use case implementation easy to navigate. |
| Each time a sequence diagram is completed the object model is updated to ensure that it fully supports the functionality of the use case. |
| Suggested Step Flow | ||||
![]() |
||||
| Guidelines, Templates and Examples | ||||
| ||||
| 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) |
||||
The Develop Use Case Implementation Task - © CRaG Systems 2006 - 2008 |