MSF Process Model design in Visual Studio Ultimate

Process model is a part of software engineering, just like what process method we use to build the software "house". In this section, we will provide a brief overview of the VS 2010 new delivery and architecture tools and model diagram features. But it does not include UML details and other architectural concepts, and you will see every design process using the VS 2010 modeling feature, with a project template, "Modeling Engineering" (modeling project), that allows us to create a variety of graphs. In VSTS 2008, there is no support for creating a composition of UML frames, while in VS 2010 it provides some useful UML diagram designs. These charts provide us with advanced designs for the solution and the underlying implementation architecture (no support for deployment diagram design elements).

The traditional Microsoft Solution Framework (Microsoft Solution Framework, MSF) contains the conceptual and planning phases. Although some designs are created in the conceptual phase, the completion occurs in the planning phase, and the planning phase is further divided into three different processes:

L Conceptual Design (conceptualdesign)

L Logical Design (logicaldesign)

• Physical Design (physicaldesign)

In VS 2010, provides support for iterative development of Agile (Scrum, XP, etc.) process model cycles (cycle processes). The Microsoft MSF software Process Infrastructure Model framework is shown in Figure 1.

Figure 1 Microsoft MSF software Process Fundamentals model

① Conceptual Design (conceptualdesign): This is a process that involves gathering information from business and user perspectives on business information, the current application environment, and leveraging this information to capture, analyze business and user needs, and validate and optimize solutions. To include a description of the current and future use scenarios for your system, the goal is to achieve a common understanding of the functionality and usage of the user and the project team after the system is complete. It is the process of collecting, analyzing, and prioritizing, using the requirements document (requirement document) and use case diagrams, which are the business processes within the system. We can use the "activity diagram" workflow mode. The conceptual design will list all user roles interacting with the system and the overall structure of the system. In the future state of the system (physical function list), the definition of the architecture will contain the logical layer, and we can use the performance model of the provided "layer diagram" in VSTS. We can use the performance model of the provided "layer diagram" in VSTS 2010.

The L-use case diagram (use case Diagram) requirements can be modeled and expressed using the "Use Cases" diagram. The use Case Diagram Toolbox (Toolbox) enables you to build relationships between your modeling roles, use cases, subsystems, and annotations. These relationships can be of the following types: associations, dependencies, inclusions, generalizations, and extensions. One of the best features of the use case diagram in VSTS 2010 is the ability to associate elements with WorkItems, as shown in Figure 2.

Figure 2 Use case diagrams to create associations with WorkItems