This Indonesian video will guide you the first step to capture system and actor requirement. This tutorial uses Visual Studio Modeling project as a part of ALM features in Visual Studio started from 2010 version. Here are some conclusions from this video
- Actor and Action are the main part of use case diagram
- Keep the diagram simple, eliminating the technical aspect such as extend or include, except you use this use case for technical communication between technical team only
- Kite level best for business use case, while sea level use case good for deep dive with the system requirement
- It will be great to split up use case diagram for one actor (the video join the entire users for simplicity purpose only)
- Use case will be explained further in Activity Diagram
Enjoy this video,
Leave a Reply