T-012-024 Software Candidate Release Phase 3 Checklist
Actors
Name | Title | Meaning | Approved Date & Time |
---|---|---|---|
Change history
Revision | Summary | Date |
---|---|---|
Process overview
The purpose of the Software Design Checklist review is to ensure the outputs of Phase 3 satisfy the criteria listed in the next section.
Project information
- Project title:
- Project manager (name and function):
Planning
Phase | Object | Done |
---|---|---|
Phase 1 Product Design Review | Establish input data | |
Phase 2 Software Design Review | SRs, Architectural Design and UI Prototypes | |
Phase 3 Software Candidate Release | Coding, integration and test plan | |
Phase 4 Software Verification Review | Software version verified and residual anomalies | |
Phase 5 Product Validation Review | Validation activities, Technical Documentation and DHF |
Previous reserves
Instructions
If there were any reserves or outstanding issues identified during Phase 2, list them here. Include a brief description of each reserve, the actions required to address them, and assign an owner and targeted completion date. See T-012-022 Software Design Phase 2 Checklist for an example.
N° | Documents / Purpose / Actions to implement | Owner | Targeted Date | Satisfying |
---|---|---|---|---|
Version identifier
- Version:
- Version type: Major/minor/patch
- Git tag:
- Version objectives:
- Changelog:
List of implemented software requirements
Key | Summary | Software item |
---|---|---|
Software requirements
List the expected records and observations
Item | Satisfying | Comment | Reserves |
---|---|---|---|
Test plan
- Regression test type:
- Test planification:
Reserves
N° | Documents / Purpose / Actions to implement | Owner | Targeted Date |
---|---|---|---|
Conclusions
Instructions
Summarize the outcome of the review for this phase, clearly stating whether the project milestone can proceed. Include the following elements:
- A brief assessment of whether the reviewed outputs (e.g., software requirements, traceability, test plan, documentation) are available, complete, and relevant.
- A statement confirming whether all identified software criteria for the release have been met.
- Indicate whether any reserves exist and whether they impact the approval of the phase.
- Explicitly confirm whether the release candidate has been accepted for the next phase (e.g., verification).
Be factual and concise. Use present-tense language and avoid vague expressions.