Tutorial: Defining Requirements with Use Cases using TopTeam

Visualize Use Case text using the automatically generated diagrams

Visualize Use Case text using the automatically generated diagrams

Previous topic Next topic No directory for this topic  

Visualize Use Case text using the automatically generated diagrams

Previous topic Next topic Topic directory requires JavaScript  

 

Overview

 

TopTeam converts the text of Use Case Flow-of-events into an easy-to-understand graphical representation that all stakeholders can follow. This is a fully automatic process that requires no manual intervention.

 

Using TopTeam you can visualize the Use Case text using these types of diagrams:

 

1.Flow Diagram - The Flow Diagram displays the Use Case text as a diagram that mimics the simplicity of the Flow-of-events. In this diagram each Flow is represented as an independent Activity Diagram with decision boxes branching into each Alternate Flow/Variation from the Main Flow. Because Flow Diagrams mimic the Flow-of-Events of the Use Case, most stakeholders find this type of diagram the easiest to understand and follow.

 

2.Activity Diagram - The Activity Diagram displays the Use Case text as a UML Activity Diagram. The Main Flow-of-events and the Alternate Flows are combined into a single diagram.
 
3.Swimlane Diagram - The Swimlane Diagram displays the Use Case text by placing each step of the Use Case into the lane that represents the Actor that performs the action in that step. Using the Swimlane diagram you can follow the exchange of responsibility and information between Actors of the Use Case and the System.
 

Each type of diagram helps you and other the stakeholders get a different perspective on the Use Cases which are the Behavioral Requirements of the system.

 

 

You can use the automatically generated diagrams to:

 

1.Review the Use Case definition with stakeholders.
 
2.Simulate the application and get useful feedback from stakeholders much earlier in the development lifeearlycycle.