Use use case diagrams in Visual Studio to describe the relationship between the system and the participants

A "Use case diagram" is used to describe who uses the system and what the system does. Use case diagrams do not involve using details, they are used only to describe the relationship between the people and the system, and do not involve the sequence of actions. To experience it together.

Create a solution using Visual Studio 2012.

Create a blank, named "TailspinToys" solution.

Right-click the solution, tap "Add", "Add New Project", select "Modeling Project" on the left, and name "Tailspintoys.analysismodel".

Right click "Tailspintoys.analysismodel", click "Add", "New Item", select "UML use case diagram", named "Brainstorming Workshop", click "Add".

Select subsystem in the left-hand toolbox, drag to the right interface, name "Tailspin Toys", and resize, and fill the color with the property settings.

Drag "notes" from the Toolbox, drag into "subsystem", and note the text as follows:

From the Toolbox, drag 3 "participants" to the interface, named "Customer", "Storemanager", and "time", respectively.

Right-click the 3 "Participants" icon, and add the following associations:

Add notes to the participant and the system, respectively, as follows:

Note:

Create a solution before creating a use case diagram
Clear system boundaries, who use systems, who do not use systems
Describe goals and value to users from a user's perspective
Describe the information as thoroughly as possible

Reference: https://channel9.msdn.com/Blogs/clinted

Use use case diagrams in Visual Studio to describe the relationship between the system and the participants