WorkProductDescriptor
Work Product (Artifact): Build Procedures
This artifact describes how to generate an executable copy of the system.
Purpose
Build Procedures are documented to ensure that the procedures can be executed at any time by the development team without depending on particular team members.
Relationships
RolesResponsible: Modified By:
Input ToMandatory: Optional:
  • None
External:
  • None
Main Description
This artifact may include such items as which files are required, which links must be in place, which libraries are accessed, the sequence of steps required to generate the system, decisions and rationale for all integration procedures, or any required passwords.
Properties
Optional
Planned
Key Considerations

This is a very straightforward work product.  Write the build procedures so any team member can follow them. 

If security is an issue, ensure that the team knows where and how to get the password.  One solution is letting the project manager keep passwords in a sealed envelope in a secure location. However, the proper people must be aware of how to gain access to this location, if necessary.

You can test the Build Procedures by having a team member unfamiliar with the process walk through the procedures.

Tailoring
Impact of not havingUndocumented build procedures can lead to confusion and chaos during system builds. If the procedures are unrecorded, there is a risk of building incorrect or incomplete copies of the system, resulting in easily avoidable delays.
Reasons for not needingBuild procedures should always be developed to guide builds and releases. They should never exist only in someone's head.
Representation OptionsBuild procedures can be written as textual guidance, most often as a checklist and/or sequence of steps.  They may also be automated using a tool such as IBM Rational Build Forge(R).
More Information
Checklists