• Developer

• Developer

• Refine the Architecture
• Run Tests
• Run Tests

• Implement Test Scripts

• Implement the Solution
• Integrate and Create Build

• Construction Phase Iteration  >  Develop Solution (for requirement) (within context)  >  Build
• Construction Phase Iteration  >  Test Solution  >  Build
• Construction Phase Iteration  >  Develop Solution Increment  >  Build
• Construction Phase Iteration  >  Test Solution  >  Build
• Develop Solution (for requirement) (within context)  >  Build
• Develop Solution Increment  >  Build
• Develop Solution Increment (no TDD)  >  Build
• Develop the Architecture  >  Develop the Solution  >  Build
• Develop the Architecture  >  Build
• Develop the Architecture  >  Develop Solution Increment  >  Build
• Elaboration Phase Iteration  >  Develop Solution (for requirement) (within context)  >  Build
• Elaboration Phase Iteration  >  Test Solution  >  Build
• Elaboration Phase Iteration  >  Develop the Architecture  >  Build
• Elaboration Phase Iteration  >  Develop Solution Increment  >  Build
• Elaboration Phase Iteration  >  Test Solution  >  Build
• Inception Phase Iteration  >  Develop Architecture Spike  >  Build
• Test Solution  >  Build
• Test Solution  >  Build
• Transition Phase Iteration  >  Develop Solution (for requirement) (within context)  >  Build
• Transition Phase Iteration  >  Test Solution  >  Build
• Transition Phase Iteration  >  Develop Solution Increment  >  Build
• Transition Phase Iteration  >  Test Solution  >  Build

This working version of the system is the result of putting the implementation of the system through a build process (typically an automated build script) that creates an executable version of the system, or one that runs. This executable version of the system will typically have a number of supporting files that are also considered part of this composite artifact.

There will always need to be an operational version of the system.

This work product is almost always a composite product made up of numerous parts required to make the executable system. Therefore a build is more than just executable files; it additionally includes such things as configuration files, help files, and data repositories that will be put together resulting in the product that will be run by the users. The specifics of those parts will vary by technology in use.

• Continuous Integration

• Continuous Integration
• Promoting Changes