Using VisualStudio2010 from analysis to implementation (2)-refining business processes using activity diagram

Objective

As we all know, Visual Studio 2010 has made a lot of effort on every aspect of the software development cycle, and this article goes on to show you how to use Visual Studio 2010 to support activity diagram, and to use Visual Studio 2010 Method of refining business process.

Background

Previous: Using Visual Studio 2010 from Analysis to implementation (1)--installation of Visual Studio CTP2

Not familiar with the activity diagram brother please refer to: http://www.ibm.com/developerworks/cn/rational/tip-drawuml/

The first point of software project development is to obtain the demand from the reality, refining the business process, so as to provide the necessary conditions for the design and development, even if the prototype method iterative development, but also need more careful analysis of requirements. In the era of process development, there are no very superior requirements analysis methods, are based on some of the now rarely heard graphics to describe (the University of software engineering tutorials in the poster 4 version). After UML1.1 stereotypes, the UML-based approach to ooad is growing, and today, the modeling we need is often done with activity Diagram (active diagram) and use case Diagram (use cases diagram), Visual Studio 2010 support for both graphs has also been well done.

Activity diagram Use 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 "Activitydiagram" and OK

5. In Activitydiagram, we can drag and drop elements from the left side of the toolbar to the activity diagram.

Visual Studio 2010 provides activity diagram support:

Because the current mainstream of UML is divided into 1.1 standard and 2.0 standard, the elements provided are slightly different, not completely unified. For example, Visio uses a 1.1,truefun of 2.0.

In the visual Studio CTP, we can see that the elements he provides are very rich, as follows:

1.InitialNode start node

2.ActivityFinalNode Active End Node

3.Action activity

4.ObjectNode Object Node

5.DecisionNode decision Node

6.MergeNode Merge Node

7.ForkNode Branch Node

8.JoinNode Connection Node

9.SendSingnalAction New Send Activity

10.AcceptEventAction Event Reception Activity

11.CallBehaviorAction Behavior Invoke activity

12.CallOperationAction Operation invoke Activity

13.InputPin input Mark

14.OutputPin output Tag

15.ActivityParamenterNode Activity Parameter Node

16.Connector Connector (arrow)