If I had to pick one diagram that most people have seen and generally understand, it's the activity diagram. Sometimes called a process flow. The activity diagram can illustrate complicated flows.
These can also be developed using swimlanes making it easy to distinguish actors in the process flow.
Keep in mind we're focused on requirements related artifacts, where we maintain a focus on what the system will do, not how the system will be implemented. This diagram adds the ability to show alternative flows and more advanced notation allows for parallel flows and various types of decision points and merges. Remember to keep your diagrams relatively simple. Break large flows into a series of small flows. Use subprocess where it makes sense. Activity diagrams have many of the same characteristics as the other dynamic models. Be careful to not get carried away with heavy formality. Be judicious in your choice of which models to maintain long term.
No comments:
Post a Comment