Shulou(Shulou.com)06/02 Report--

Editor to share with you what the Visual Studio 2010 architecture design function is, I believe most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!

Overview of VS2010 Modeling

In the software application life cycle management (ALM), VS 2010 describes the system architecture graphically through the new Architecture browser (Architecture Explorer) and Architecture layer Diagram (Architecture Layer Diagram), so that the technical or non-technical personnel in the project can collaborate in a graphical way with models, and define enterprise and system functions. In addition, VSTS 2010 also supports both Unified Modeling language (UML,Unified Modeling Language) and Domain specific language (DSL,Domain Specific Language). Architecture designers can design architecture and modeling in VS2010, thus getting rid of the traditional use of non-VS architecture design tools and enabling designers to design .net architecture more efficiently.

At the beginning of Microsoft, the technicians in the project used a number of separate development tools for software development, such as architects using Rose for architectural design and developers using Visual Studio for coding. At the same time, the non-technical personnel in the project use some general project management tools for project management, such as project managers use Project,Excel to make project plans, divide and assign tasks, and so on. Therefore, the interrelation and intercommunication between the various functions in VS2010 are also greatly enhanced.

We can use the VS2010 architecture swimming lane (swim-lane) diagram to have a more intuitive understanding of the application of VS2010 modeling process functions. As shown in figure 1.

In the process of architecture modeling and design, we also follow the process definition of ALM (understanding code, domain understanding, control and maintenance, extensibility, etc.). According to the problem that the product aims at, we will analyze the functional process of VS2010 modeling through the four topics in the figure above. For example, understanding Code describes how to use code analysis and visualization techniques in VS2010 to help users analyze and understand existing systems. Finally, users can use these technologies to help customers achieve their functional requirements on the basis of the existing code base.

VS2010 Architecture Analysis tool

VS 2010's new architectural tools allow us to understand application and functional design and help verify that the design and execution do not deviate from the development purpose. It not only supports the general system analysis and design process (requirements-> entities), but also supports another kind of process-reverse engineering (Reverse Engineering).

Reverse engineering allows you to understand that the parts between applications are important dependencies to determine that problems may occur. In addition, visual diagrams can help us find places to perform new functions. The DGML file enables the dependency matrix and layout generated by the solution, and each view can provide a different view in the project structure. As shown in figure 2.

The overall structure of the model can be analyzed through advanced view functions. In an area, you can modify the dependencies for changes between 15 minutes and an hour as needed, or you can enlarge the diagram between local classes.

The type of VS2010 reverse engineering can be divided into static and dynamic, static refers to the static structure of the whole program code, such as the relationship between components or categories, and dynamic refers to the order in which the program code is executed, such as the order of method calls and responses related to a certain program code segment.

Static reverse engineering (Static Reverse Engineering)

VS2010 provides analysis tools for different functional levels to assist program code in reverse engineering. Layer Diagram can look at the architecture from a high-level perspective; Architecture Explorer can cut in from a specific point and explore only the parts we care about; .net Class Diagram can analyze the Class structure of the detailed part. There are three main tools for static reverse engineering: Architecture Explorer, Layer Diagram, and Class Diagram. Layer Diagram allows us to analyze the entire software structure from a high-level perspective, and the degree of refinement is free to choose, from the project, Namespace, Classs, to the method.

Dynamic reverse engineering (Dynamic Reverse Engineering)

In the past, when people such as program developers had no idea about the analysis of the program code, they needed to understand the program flow directly from the program code, which was difficult and painful. VS2010 new architecture tools support dynamic reverse engineering, there are two main tools: dependency graph (Dependency Graph) and Sequence Diagram (sequence diagram), the use of these two tools will greatly enhance the efficiency of code analysis. Dependency graphs can help to understand the structure and relationships of program code, and can be generated through the Schema browser (Architecture Explore). Sequence diagram is an image tool used to express program flow. VS2010 is also used in the design of object import system. Sequence Diagram function can be drawn directly by hand, and graphics can be generated automatically according to selected code segments through reverse engineering. As shown in figure 3.

VSTS 2010 Model browser

In the actual project development practice, in most cases, a new system is built on the basis of the existing code. In this case, a typical problem encountered by architects or developers is that there are no good tools to help them understand the architecture of the existing code, so it is difficult to effectively build on the existing code. Add new features to meet new requirements. To solve this problem, VSTS 2010 provides two important new modeling tools: the UML Model browser (UML Model Explorer) and the Architecture browser (Architecture Explorer). The new model browser allows architects to create complete architectural diagrams of existing code and to understand how the components of the original system work together. This will provide valuable reference information for architects to decide how to design, use, reuse, or whether to abandon existing code.

UML Model browser (UML Model Explorer)

In the VSTS 2010 Architecture and Ultimate versions, a new tool window (UML Model Explorer) has been added to help users understand and use the UML model created. It is a tree-structured WPF component that shows the hierarchy in the UML model. In this case, the model refers to the content in the Modeling Project (project template) created. Through this project template, you can create a model project, and then create a UML diagram in the model project. In other words, UML class diagrams, activity diagrams, use case diagrams, and component diagrams can only be created in the model project, and can be designed and created in accordance with the model architecture.

Modeling Project is a container for model data, chart files, and other resources (such as Excel, Word documents) that users want to store. Users can add the project to any new or existing solution, and also support different program projects (C #, VB, Web, etc.) in the solution. Model engineering Modeling Project also supports versioning. Generally speaking, the root node in UML Model Explorer is used to represent the Modeling Project itself. As shown in figure 4.

After the model project is created, the * .uml file under the default folder "ModelDefinition" under Solution Explorer is automatically added and maintained by the modeling tool without any manual intervention by the user. They store the corresponding model relation definition within the UML diagram, which is the core of the whole model engineering. The uml file corresponds to the Package object in the model one by one. When a new model project is created, a default ModelDefinition.uml file is created, which corresponds to the root Package of the entire model, that is, the root node in the "UML Model Explorer" window.

Schema browser (Architecture Explorer)

In Visual Studio 2010, Architectural browser (Architecture Explorer) tools are provided to assist developers to analyze and understand existing code or compiled .net Assembly. It can browse existing system code in the way of Class View, Solution View and File System. Class View and Solution View support browsing of Visual C # and Visual Basic.Net projects, while the File System-> Select Files mode can be used to browse the contents of any .net-based compiled Assembly file, similar to the function of the Reflection decompiler. As shown in figure 5.

In addition, you can drag and drop the content in the architecture browser directly to the existing dependency diagram. In addition to browsing the open project, the framework browser can also directly browse the namespaces and types in the compiled Assembly file, but can not double-click to navigate to the corresponding code, the rest are similar to directly browsing the project. As shown in figure 6.

Specification browser (Spec Explorer)

Spec Explorer is a model-based testing tool released by Microsoft that is closely integrated with Visual Studio 2010. It is also a plug-in to the Visual Studio integrated development environment. It has been heavily used for testing by Microsoft's internal technical teams, and has been involved in the Windows protocol testing project (more than 200 engineers are involved and working together). The integrated work environment of Spec Explore and VS is a model-based testing (Model-Based Testing,MBT) technology, which is a lightweight, formal method to verify the software system, and can formally model the test software system (System Under Test,SUT) and design a machine-readable model. At present, the cost of fully verifying consistency is very high, and heavyweight formal methods are often difficult to be applied to practical projects, while model-based testing shows its advantages in this aspect, and has been applied to many large-scale projects. As shown in figure 7.

Users can model the expected behavior of a software system through Spec Explorer and automatically generate test code that can be run under the test framework of Visual Studio. The model can be developed with the current mainstream programming language C #, and then the model can be configured and tailored through Cord language scripts.

The Spec Explorer tool can automatically explore all the potential behaviors of a specification (Specification,Spec) and represent its behavior model as a state machine. The output of an exploration can be very large, so Spec Explorer provides the Cord language to tailor the output and pick out the scenarios of real concern in the test. And can efficiently solve the problem of state explosion.

The SpecExplorerVS2010.msi plug-in can be found in

Download http://msdn.microsoft.com/en-us/devlabs/ee692301.aspx.

Development and design model

The ALM of Visual Studio 2010 Ultimate covers tools from system design to testing. In terms of architecture, it includes a new architecture review tool (Architecture Explorer) and added support for Unified Modeling language (UML), such as class diagrams, use case diagrams, activity diagrams, sequence diagrams, etc. And the architecture layer diagram (Architecture Layer Diagram), which describes the system architecture in a graphical way, so that the technical or non-technical personnel in the project can collaborate through the model graphically, and define the functional relationship between the enterprise and the system.

VSTS 2010 architecture features, the main functions are divided into three parts: 1) understanding existing code; 2) clear structural design; 3) teamwork. As shown in figure 8.

Understand existing code. One of VSTS2010's Architecture goals is to help understand existing code. Because only when you understand it can you use it correctly. In the actual work, we often encounter the problem that only by understanding what the existing code can do can we carry out the follow-up work.

Define the structural design. Software people often need to design and describe the architecture of the software, define a name for a particular problem to describe it, and then make it acceptable and understood by other members of the development team. VSTS2010 Architecture supports the UML model, so Microsoft has enhanced the DSL tool, which supports the key technologies of many functions in VS2010. All UML diagrams of VS2010 Architecture are built through the DSL tool and run on the DSL runtime. In VSTS 2010, 5 UML charts are supported.

Teamwork. In development projects, we often need to make the results of modeling an important part of the whole software development cycle. VSTS 2010 provides a variety of ways for models to interact with Team Foundation Server and Visual Studio itself, such as the newly introduced engineering category "Modeling Project".

The new Architecture function of VS2010, which can be used by software architects and developers, can help understand the code and user requirements, and make the software system have better quality. For example, the unified modeling language can be used to design use cases, activity classes and sequence diagram functions of user requirements to describe and communicate user requirements, thus enhancing the cycle management control of ALM. The Architecture tool template, as shown in figure 9.

When the system requirements are determined, we enter the UML-based object-oriented design (Object-Oriented Design,OOD) system design phase, in which the following UML diagrams will be used to show the support and application of VS2010 in the design phase.

VS2010's Architecture tool includes the following UML diagram (see figure 9):

Activity diagrams (Activity Diagram): clarify the workflow of the business use case realization among the actors.

Component diagram (Component Diagram): the main purpose of a component diagram is to show the relationship between structures or interfaces between system components.

Class diagram (Class Diagram): shows the logical structure of the system and the relationship between classes and interfaces. Can be used to exchange data types for relationships between storage and the system.

Sequence diagram (Sequence Diagram): mainly shows the chronological order of messages sent between objects.

Use case diagram (Use Case Diagram): describes the relationship between roles and use cases, focusing on the functions that the system must implement to analyze customer requirements during the requirements analysis phase.

In addition, you can create from existing code: layer diagrams (Layer Diagram), dependencies between different parts of the code; class diagrams

Types and their .NET relational code; sequence diagrams, in the method call .NET code order.

The UML 2.1.2 specification defines 13 diagrams, and Visual Studio 2010 supports five of the most commonly used diagrams (class diagrams, use case diagrams, activity diagrams, component diagrams, and sequence diagrams). Their underlying Meta model is a model relationship that fully conforms to the UML2.1.2 specification.

These are all the contents of the article "what are the functions of Visual Studio 2010 Architectural Design?" Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.