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

This article will explain in detail how to use VSTS2010 for software life cycle management, the content of the article is of high quality, so the editor will share it with you for reference. I hope you will have some understanding of the relevant knowledge after reading this article.

Application Lifecycle Management

Like anything in the world, software development has its life cycle. Usually, the life cycle of a software is divided into several stages, such as analysis, design, development, testing, deployment, maintenance and * * abolishment, etc., and the use of various tools to help manage each key link is called application life cycle management (ALM: Application Lifecycle Management).

Throughout the life cycle of the application, each key link has its own task, and the specification is generated or the program is delivered to the next link. If there is a lack of management, or if a link in the process is based on the wrong results produced by a process, the whole software project is likely to fail. The focus of application lifecycle management is to treat the whole process of software development as a continuous and repeatable process: definition, design, development, testing, deployment and management. Every part of the process needs to be taken seriously and monitored to ensure that the whole process can be completed smoothly.

By implementing application lifecycle management, we can achieve the following benefits:

◆ increases productivity, and the whole team shares the development and deployment practice (Best Practices) process, while developers only need to focus on specific business requirements (Business Requirement)

◆ improves quality so that the final delivered application meets user expectations (Expectation)

◆ breaks down the barriers in the process of cooperation, especially the communication barriers between technicians and non-technical personnel, and makes the flow of all kinds of information in the project smooth.

◆ accelerates development with simplified integration solutions

◆ synchronizes the design with the application, thus reducing maintenance time

◆ enables investment in skills (Skill), process (Process), and technology (Technology).

◆ increases the flexibility of applications to respond to business changes by reducing the time required to modify and build the program

With the deepening of software development practice, application life cycle management is more and more accepted by the industry as a practical and reliable software development model that can create high-quality applications. However, to implement the entire application lifecycle management is very complex, we must use some tools to help us complete the entire lifecycle management. Initially, the technicians in the project used 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.

At that time, these software were simply and loosely grouped together, the information flow between each software could not be communicated, and the software development process and the project management process were completely separated. Causes information to block within the project. At the same time, due to the growth of software development complexity (Complexity) and mixing degree (Sophistication), the tool set with version control software as the core has been extended to more aspects, thus putting forward more requirements for application life cycle management software.

Visual Studio Team System 2010

Microsoft has seen the trend that application lifecycle management is gradually accepted in the industry, so in the third generation of Microsoft Visual Studio Team System--Visual Studio Team System 2010, it will provide collaborative and consistent application lifecycle management tools to make it easier for all kinds of people involved in software development, from architects to developers, from project managers to testers, to collaborate throughout the ALM process.

As we can see, the users of VSTS 2010 include project managers, architects, developers and testers who cover the entire software development lifecycle. On the other hand, VSTS 2010 provides corresponding tools for people with different roles in the software development project process, and the most important thing is to integrate these tools with Team Foundation Server as the core to enhance the communication and cooperation among the software development team. With Visual Studio Team System, we will be able to implement complete application lifecycle management, enabling the development team to ensure higher predictability and better quality early in the development process and throughout the development process.

Architecture

Among them, in terms of architecture, VSTS 2010 will graphically describe the system architecture through the new Architecture browser (Architecture Explorer) and Architecture layer Diagram (Architecture Layer Diagram), so that both technicians and non-technical personnel in the project can collaborate graphically through models, and define enterprise and system functions. In addition, VSTS 2010 also supports both Unified Modeling language (UML: Unified Modeling Language) and domain-specific languages (DSL: Domain Specific Language).

In the actual project development practice, in most cases we build a new system 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 existing code, so that they cannot effectively build on the existing code. Add new features to meet new requirements. To solve this problem, VSTS 2010 provides a new modeling tool, the Architecture browser (Architecture Explorer). The new architecture browser allows architects or developers to create complete architectural diagrams of existing code and understand how the components of the original system work together. This will provide sufficient valuable reference information for architects or developers to decide how to use, reuse, or discard existing code.

Development and testing

On the testing side, VSTS 2010 enhances testing capabilities while simplifying tools to integrate testing throughout the application lifecycle. New features include removal of No-Repro errors, rapid design and development of tests, test case management, test plan integrated with Team Foundation Server, and ensuring that all updated program code is tested.

In VSTS 2010, the collaboration between testers and developers is emphasized. It provides two views: the test impact view (Test Impact View) and the code change view (Code Changes View). Through these two views, developers can have a better understanding of the impact of development on testing. When the developer changes the code, the test impact view analyzes which tests need to be run to verify the code changes. This will help developers to run only the necessary tests to validate code changes and thus have confidence in the checked-in code. The new test impact view shows a list of tests that must be run after code changes, as well as the code changes affected by each test. The code changes view shows a list of all code changes and the tests that must be run to verify the code changes. This avoids the waste of running all the tests to verify a small code change and makes the test more efficient.

Collaboration

VSTS 2010 improves collaboration capabilities by strengthening Team Foundation Server (TFS), including providing process templates that allow teams to configure and adopt any Agile software development model they like. The team can track based on a wealth of work item links and establish hierarchical work item relationships. In application lifecycle management, what we are most concerned about is how project managers participate in the entire lifecycle. Through the close cooperation between TFS, Peoject and Excel, project managers can use their familiar project management tools to obtain project-related information directly from TFS, understand the operation of the project through rich project reports, and accurately plan and manage various tasks in the project.

In addition, on the program code management system, TFS provides visual tools to track all changes from branch to product version, as well as various versions of workflow programs to detect errors in advance.

On how to use VSTS2010 software life cycle management to share here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

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.