Visual Studio Team System ALM深度探索

需积分: 5 178 浏览量更新于2024-08-01 收藏 6.65MB PDF 举报

"Pro Visual Studio Team System Application Lifecycle Management" 《Pro Visual Studio Team System Application Lifecycle Management》是一本由Joachim Rossberg编写的书籍，专注于Visual Studio Team System（VSTS）在应用程序生命周期管理（ALM）中的专业实践。这本书详细阐述了如何利用VSTS工具集来高效地进行软件开发的各个环节，包括需求管理、设计、编码、测试和部署等。 VSTS是微软推出的一套集成开发环境，专为团队协作和应用程序的全生命周期管理而设计。它提供了版本控制、工作项跟踪、自动化构建、测试管理和代码分析等功能，旨在提高软件开发团队的生产力和质量。书中的内容可能涵盖了以下关键知识点： 1. **需求管理**：VSTS通过工作项跟踪系统，帮助团队定义、组织和优先级化项目需求，确保团队对目标有清晰的理解，并能够有效地跟踪进度。 2. **设计与架构**：VSTS支持多种设计工具，如UML图表，帮助团队规划和沟通软件架构，确保设计的可维护性和扩展性。 3. **版本控制**：VSTS内置的Team Foundation Version Control（TFVC）系统，允许团队成员协同编辑代码，管理不同版本，解决冲突，并保持代码历史记录。 4. **自动化构建**：VSTS提供自动化构建功能，可以设置触发规则，如每次代码提交后自动构建，以确保代码的持续集成和快速反馈。 5. **测试管理**：VSTS包含测试计划、测试用例和测试结果管理，支持自动化测试，帮助团队实施持续测试策略，确保产品质量。 6. **缺陷跟踪**：通过工作项类型，VSTS可以追踪和管理软件中的缺陷，从发现到修复的整个过程都有迹可循。 7. **报告与度量**：VSTS提供了丰富的报表和度量工具，帮助团队监控进度，识别瓶颈，以及做出数据驱动的决策。 8. **团队协作**：VSTS的协作平台允许团队成员进行讨论、分享文件、跟踪任务，促进跨职能团队的有效沟通。 9. **持续集成/持续交付(CI/CD)**：VSTS支持配置CI/CD管道，实现代码变更自动触发构建和部署，加速产品发布流程。 10. **适应性与扩展性**：VSTS具有高度的可定制性和扩展性，允许团队根据自身需求调整工作流程，整合第三方工具和服务。这本书的技术审阅者包括Norman Guadagno和Dan Massey，他们可能为内容的专业性和准确性提供了宝贵的建议。此外，书中的编辑团队也包括多位业界专家，确保了书中的信息及时且具有权威性。《Pro Visual Studio Team System Application Lifecycle Management》是针对希望提升软件开发效率和质量的团队的一份宝贵资源，它深入探讨了VSTS在ALM中的应用，旨在帮助读者掌握高效协作和质量管理的方法。

Acknowledgments

Sam Guckenheimer, Microsoft. Thanks for giving me valuable information and contacts

at Microsoft.

Dan Massey, Microsoft. Dan, thanks for giving priceless input for the book. As a technical

reviewer, you have been great. The book is so much better now after all your input.

Norman Guadagno, Microsoft. Norman, your feedback as a technical reviewer has been

invaluable. Together with Dan, the two of you have improved the book very much.

Tony Campbell, Apress. Thanks for all the feedback, Tony. Having three technical reviewers

scared me at first, but the improvements to the book were great.

Dag König, Microsoft. Dag, I missed giving you credit in my last book. I’m sorry about that.

Thanks for the continuing support.

Jeff Levinson. Thanks for writing the foreword and giving feedback on my work.

Ewan Buckingham, Apress. Ewan, thanks for pushing me in deciding to write this book.

Ameya Bhatawdekar, Microsoft. Thanks for taking your time to discuss the Project Connector

with me.

Andreas Nordenadler, Microsoft. Thanks for your support.

Colin Bird, Conchango. Thanks a lot.

Thomas Gustavsson, Know IT. Thanks for helping me out.

Mattias Olausson, Sweden. Thanks for helping me with some code samples and discussions.

Per Wallentin, Know IT. Thanks for all the support and the nice MacBook Air I have used to

write this book.

Thanks to all the other people at Apress working on this book: Beth Christmas, Sharon Wilkey,

Laura Esterman, and anyone else who was involved. It couldn’t happen without you.

I’m sure I forgot someone in this list, but I thank everybody who has helped me and supported

me along the line.

I also thank you, the reader, for purchasing this book. Without readers, there would be

no books.

xix

Introduction

At the end of 2006, Know IT was asked by Microsoft Sweden if we were interested in putting

together a seminar tour introducing Visual Studio Team System (VSTS) in Sweden. This was

too interesting for me to pass up, so a colleague and I set of to work. Microsoft gave us free

rein in filling the seminars with topics, which was great because we then did not feel like we

had to please them but instead could be realistic about the set of tool(s).

We were invited to visit important customers and talk about the benefits (and of course

the concerns) of using VSTS in an enterprise. We traveled from the north of Sweden to the

south and had a pretty interesting time. Some customers had already started adopting VSTS,

but most of them were curious and had not taken the step yet.

During this tour, my interest in Application Lifecycle Management (ALM) started for

real. I had of course heard the term before, but now I had to dive deep inside it to see what

place VSTS had in all this. Before this, my focus had been mostly on the tool itself and never

about where it fits in an organization. I was impressed by what I saw, and by what I felt such

a tool could do in my own projects. I knew that the tool at that stage was not entirely ready

for everything in ALM, but I felt it had great potential. And so far it has lived up to my

expectations.

What This Book Will Cover

I will try to cover a great deal in this book. The primary focus of the book is to help organiza-

tions invest in IT projects that return business value to the customer. This can be done in

many ways, and by investing in the Application Lifecycle Management process and tools

supporting this process, I hope to give you my vision on this.

These are the chapters and a short overview of each.

Chapter 1

The first chapter focuses mainly on the IT project world of today. Far too many IT projects

seem to fail or at least have significant overruns when it comes to time and budget. More

important, many of them seem to not deliver the business value that the customer wants.

And this is a very bad thing. You will look at some of the difficult questions that challenge IT

organizations. What makes it so hard to calculate the outcome of an IT project? What are the

challenges they face? Why don’t IT systems align better with the business processes? Why

don’t IT projects seem to deliver the business value the customer wants? What can be done

to eliminate these problems?

xxi

Chapter 2

In Chapter 2, we discuss what Application Lifecycle Management (ALM) really is. I define ALM

so we will have a common ground to stand on for the rest of this book. You will also see how

the ALM process can be supported by tools and what requirements we can have on such tools.

Chapter 3

All organizations have processes for how work is carried out. They could have a sales process, a

procurement process, and so on. Chapter 3 focuses on the development process and gives a few

examples of different popular processes, such as Microsoft Solutions Framework and Scrum.

Chapter 4

One of the biggest issues in IT development today is that there is a gap between the business

and IT sides of many organizations. This chapter shows two topics that can help bridge this

gap and that are important to address in the ALM process. The first is service-oriented archi-

tecture (SOA), which is a popular software system architecture intended to provide flexibility

in our IT systems so we can better align these with the business process in the organization.

This is extremely important for the ALM process to be successful.

The second topic is IT architecture and the roles of IT architects, big topics in ALM.

Traditionally, an IT architect has a very technical position, holding deep technical knowl-

edge. By redefining the architect role and extending it to cover business areas as well, we

can make sure the IT systems really support the business and the business processes.

Chapter 5

I have seen many organizations implementing Visual Studio Team System (VSTS) over the last

few years. Some of them have truly used the potential of the product while others have imple-

mented only parts of it. Most companies I have seen, however, belong to the latter group and

use mostly the VSTS version-control system.

By doing a thorough assessment of our ALM process (including the Software Development

Lifecycle, or SDLC, process) by using a couple of tools from Microsoft, we can better see which

parts of VSTS will help us most in improving our ALM process.

Chapter 6

Here you will see how to use VSTS to fulfill the ALM vision. In Chapter 6, I give an overview

of what Visual Studio Team System is and what tools are included in it. This set of tools is

Microsoft’s answer to how we can improve our ALM process, including such things as a flexi-

ble development process foundation, collaboration platform, version-control system,

development environment, work item workflow system, and much, much more.

After you read this chapter, I want you to have a good understanding of the benefits and

concerns of using VSTS as an ALM tool.

■INTRODUCTIONxxii

Why Do We Develop Business

Software and Systems?

Information is available at our fingertips all the time if we want it these days. I remember the

days back when I was a teenager. Music and movies were, and always will be, two of my top

interests. This obsession started during my teens, and I chased rare records of my favorite

artists and hard-to-find horror movies everywhere. When I found a rare vinyl pressing of a pre-

cious record from the United States, for instance, I was ecstatic. Not to mention my emotional

turmoil when I managed to purchase a Japanese edition of the same record. Those days I

wrote snail mail asking for record mail-order catalogs from all over the world, based on ads in

magazines such as Rolling Stone or Melody Maker. After carefully considering what I wanted to

purchase, I wrote down my purchase order, enclosed crisp bills, and sent a letter with my

order inside. Then came the long wait for the package. And believe you me, this wait could be

long indeed. These days I just go on the Internet, check some sites, and purchase what I want

directly by using a credit card. The stock of many sites is so huge compared to what they were

in my teens, and I can usually find what I want very quickly. In a few days the package comes,

and I can start using the things I bought.

We communicate differently as well. Sites such as MySpace and Facebook have generated

massive followers, not only by the early adopters of technology, but by our societies as a

whole. MSN Messenger, mobile phones, Short Message Service (SMS), and other means of

communication practically have exploded, at least in the parts of the world where the infra-

structure for this is available.

Development teams in organizations also use new collaboration tools such as Visual

Studio Team System, the focus of this book. VSTS, as it is generally called, is an Application

Lifecycle Management (ALM) platform tying together a company’s business side with its infor-

mation technology (IT) side. Application Lifecycle Management itself is, briefly, the process an

organization can use to care for an application or software system from its conception to its

retirement. ALM is the glue that ties the development processes together and defines the

efforts necessary to coordinate the process. You will see more about this in Chapter 2.

With the new opportunities organizations have to do business, much has changed in

the world for us, including the reality for our companies. They now have to deal with a global

environment presenting both opportunities and challenges. This means that business has

changed and still is changing at a rapid pace. This is why we need to be clear on why we

develop business systems and software.

I know that in my early days as a developer and system designer, I did not think about busi-

ness value much, if at all. Those days I was much more interested in cool technology and clever

ways of solving technical and logical problems. And I definitely was not alone in doing so.

CHAPTER 1

剩余332页未读，继续阅读

suixsy

粉丝: 14

Visual Studio Team System ALM深度探索

Visual Studio 2005 Team System软件测试指南

HP Application Lifecycle Management 11.00 Excel Add-in 用户指南

HP Application Lifecycle Management 11 用户指南

Professional Application Lifecycle Management with Visual Studio 2013 epub

Professional Application Lifecycle Management with Visual Studio 2013 mobi

Professional Application Lifecycle Management with Visual Studio 2013 无水印pdf

Beginning Application Lifecycle Management(Apress,2014)

HP Application Lifecycle Management 11_00 自述文件.mht

Application LifeCycle Management测试用例

HP Application Lifecycle Management 11.50 + SP2 Simplified Chinese SW E-Media

最新资源