Objective
After the requirements analysis and the overall process design is complete, we then begin to design the system structure. This article will introduce you to the support for the component Diagram (component diagram) in Visual Studio 2010, and a way to design the logical structure of your system using Visual Studio 2010.
Background
Previous: Using Visual Studio 2010 from Analysis to implementation (4)--Designing message sequences using sequence diagram
Not familiar to the component diagram Brother please refer to: http://www.ibm.com/developerworks/cn/rational/rationaledge/content/feb05/bell/bell.html
After the system requirements are determined, we enter the UML based OOD system design phase, in this phase, will be through the following three articles to show the VS2010 in the design phase of support and application:
Using Visual Studio 2010 from Analysis to implementation (4)--Designing message sequences using sequence diagram
Using Visual Studio 2010 from Analysis to implementation (5)--Design system structure using component diagram
Using Visual Studio 2010 from analysis to implementation (6)--Implementing system components using logical Class diagram
Component diagrams
In Ooad, we use component diagrams to provide interfaces for systems and behaviors.
In theory, a component should be able to demonstrate a single major functional module in the system, such as Web Services,. NET, COM, CLR, or user interface (UI). A component diagram can help us to understand the logical structure of a system from the "provision" and "consumption" of a system service.
Of course, we can also design a protocol interface to define the communication between the components to be implemented in the next static class design.
Component Diagram Establish 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 "Component Diagram" and then OK, the file name extension is ". Component"