Visual Studio 2010 from Analysis to implementation (3)--Design system interaction using use case diagram

Background

Previous: Using Visual Studio 2010 from Analysis to implementation (2)--using activity diagram to refine business processes

The brother who is unfamiliar with the use case diagram please refer to: http://www.ibm.com/developerworks/cn/rational/r-usecase-atm/

The Visual Studio 2010 development team's role in the white paper for use case diagram in the software lifecycle is described as follows:

1. Focus on the smaller portion of the system (subsystem) so that we can analyze the interactions in the subsystem in a more detailed environment

2. In the design and expansion of the system, can make the interaction between the various systems or subsystems significantly prominent.

3. Visually help us define the components necessary for system interaction logic.

4. Highlight interactions across multiple subsystems.

5. Summarize the interaction logic in the system at the business logic level

Use Casediagram steps

1. New Solutions

2. New Project (Project), type "Modelingprojects"

3. Right-click the newly created Modelingproject in Solution Manager to add the new item

4. Select "Usecasediagram" and then OK, the file name extension is ". UCD"

5. Drag and drop elements from the left side of the toolbar into the use case diagram.

Visual Studio 2010 provides activity diagram support:

In the visual Studio CTP, the use case diagram element is as follows:

1.Actor Active Person

2.UseCase use case

3.Comment notes

4.Subsystem subsystem to show part of the system

5.Reference allows us to add a reference to a use case diagram, such as a document or code snippet

6.Association Association Line

7.Dependency dependencies

8.Include include relationship

9.Extend Extended Relationship

10.Generalization Generalization Relationship

11.CommentLink link annotation label and corresponding element

12.ReferenceLink link Reference label and related elements

Activity diagram Drawing steps: