Introduction to Deployment（部署）

• Purpose
• [Relation to Other Disciplines](#Relation to Other Disciplines)

Purpose

The Deployment Discipline（学科） describes the activities associated with ensuring that the software product is available for its end users.

The Deployment Discipline describes three modes of product deployment:

• the custom install
• the “shrink wrap” product offering
• access to software over the internet

In each instance, there is an emphasis on testing the product at the development site, followed by beta-testing before the product is finally released to the customer.

Although deployment activities peak in the Transition Phase（移交阶段）, some of the activities occur in earlier phases to plan and prepare for deployment.

Relation to Other Disciplines

The deployment discipline is related to other disciplines, as follows:

• The Requirements（需求） discipline produces the Software Requirements Specifications that consists of the use-case model and non-functional requirements. Together with the User-Interface（接口） Prototype（原型）, the Software Requirements specification is one of the key inputs to developing End-User Support Materials and Training Materials.
• Testing is an indispensable partner to deployment, and the essential elements from the testing are the Test（测试） Evaluation Summary（测试评估总结） and the activities for implementing, executing, and managing the tests.
• The Configuration & Change Management discipline is referenced for providing the baselined build, and releasing the product and mechanisms for handling Change Requests that are generated as result of beta-tests and acceptance tests.
• In the **Project Management（项目管理）**discipline, the activities to develop an Iteration（迭代） Plan（迭代计划） and a Software Development Plan（软件开发计划） are influential on developing the Deployment Plan. Also, the work to produce a Product Acceptance plan has to be coordinated with how you manage acceptance test in the Deployment discipline.
• The **Environment（环境）**discipline provides the supporting test environment.