Technical
Processes
PROJECT NAME
Confidential
and Proprietary Information
This document contains
information that is proprietary to <COMPANY NAME>. Transmittal, receipt,
or possession of this document does not express license, or imply rights to
use, sell, design, manufacture, or to have manufactured, any product, concept,
or service from this information. No reproduction, publication, or disclosure
of this information, in whole or in part, electronic or otherwise, shall be
made without prior written authorization of an officer of <COMPANY NAME>
Authorized transfer of
this document from the custody and control of <COMPANY NAME> constitutes
a loan for limited purpose(s), and this document must be returned to
<COMPANY NAME> upon request, and in all events, upon completion of the
purpose(s) of the loan.
Document
Change Log
|
Prepared By |
Title |
Date |
Version |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Revisions
|
Modified By |
Reason |
Date |
Version |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2.2. Time
Builds Are Kicked Off
2.3. Approximate
Completion Time
2.4. Who
Kicks Off the Build (If It Is Not Automated)
2.5. Who
Is Responsible for Ensuring the Build Is Done
2.6. Who
Is Responsible for Fixing Problems That "Break" The Build
2.7. Which
Builds Are Given to QA for Testing
The process should define the source code used, the process for checking in and checking out code, who is responsible for the source code system ,and procedures for dealing with problems that require the source code to be restored or rebuilt.
The process should define the versioning method and who is responsible for tracking the current version.
The configuration management process should be defined—who owns it, who uses it, and the process for using the CM system for building the final products.
Project
Name