Software Integration Procedure -
Change Control Plan
- Created
- Formative Development with Informative
Revision Control
- Detailed Design Document
(Documentation)
- Get a private copy of then main
build. (The last label)
- Checkout and lock needed files.
(Checkin but keep checkedout when needed)
- Developer develops a piece of code.
- Developer unit test the code.
(goto 4)
- Developer steps throught every line of code,
including all exception and error cases, in an interactive debugger. (goto 4)
- Developer informally turns code over to
testing for test case preparation.
- Developer subimts code for technical review.
- Developer fixes any problems identified
during the review. (goto 5 or goto 4)
- System Testing (goto 4)
- Get a new copy of dependent files changed since stage 2. Lock
out others for integration with main build.
- Developer integrates final code with the
main build.
- System Testing/ (goto 11)
- Formal review and
Acceptance (goto 2.4)
- Code is declared "Complete"
- Check in all code and set a new
version label.
- Update Documentation
- Accepted
- Formal Change Control
- Goto 4
- Final Acceptance
- Released
- Begining development
of next product version - goto 1
|