Seems that I am not answering the question, right? But actually this question could related to this. If we have agile mindset, we can apply sequence diagram as a scenario modeling techniques iteratively and incrementally.
- We can obtain a piece of requirement by identifying a use case (just name: verb + noun & a user goal) example: Withdraw Cash from ATM
- We then leave a list of use case there and later for prioritization of them
- If the use case to be scheduled in the coming release, then we elaborate it with flow of events (the steps the actor interacts with the system); and No lower level things involved!
- System Sequence Diagram describes the interaction between the actor(s) and system. (no internal details)
- Perhaps, at most, a system sequence diagram could model:
- high-level interactions between user of the system and the system, between the system and other systems, or between subsystems (sometimes known as system sequence diagrams)
UML Sequence Diagram for software design:
Perhaps, if you want to understand the scenario in further details, you could refine the system sequence diagram into an MVC sequence diagram. This improve the quality of your code to be more reusable and extensible.
You can use a Detailed Sequence Diagram for the following purposes:
- Testing blueprint
- implementation of code in MVC framework
- Aids for designing wireframes
- Identify classes for the target system
- Generate Code
- Model alternative scenarios (sequence diagrams)
No comments:
Post a Comment