Iteration Plan (17)
1.1 Capabilities to be implemented
Consistent with LCP
1.2 Capabilities to be tested
Clear explanation of testing
methods or why the capability is not being tested
2.1 Schedule
Should be a MS Project based
plan
2.2 Resources
All team members should
be accounted for.
2.3 Responsibilities
Each team member should
have clear set of responsibilities with the developers assigned responsibility
for individual modules
3 Approach
Consistent with the LCP
and other parts of CTS documents
4 Assumptions
Iteration Assessment Report (13)
1.1 Capabilities Implemented
Consistent with Iteration
Plan 1.1
1.2 Summary of test results
Consistent with test reports
1.3 Open problems
Consistent with test reports
1.4 Objectives Reached
Consistent with Iteration
Plan 1.4
2 Adherence to Plan
Lessons learned, deadlines
missed and achievements
3 Approach and suggestions
Suggested changes to approach
for next iteration
4 External Changes Occurred
Events occurred out of the
control of this project that influenced application of the plans
5 Suggested Actions
Changes to the architecture,
test or concept of operation
Release Description (10)
1 Inventory released
List of items released including
software, documents and manuals
2 Compatibility notes
List of compatible softwares
such as browser versions and workarounds
4.1 New features
Consistent with Iteration
Assessment Report 1.1
4.3 Upcoming changes
Consistent with LCP for
next iteration
5 Known bugs
Consistent with Iteration
Assessment report 1.3
6 Defect and Change Reporting Procedures
Description of tools and
procedures to be used for reporting errors and tracking change, Consistent
with QMP 2.6
Quality Management Plan (15)
1 Purpose
2.1 Design Guidelines
Specific criteria to be
used for design, optimization and avoiding errors
2.2 Coding Guidelines
Specific and complete guidelines,
if required reference to external standards to be referenced
Check for headers, commenting
and change/revision control
2.3 Testing guidelines
Consistent with test plan
2.5 Configuration Management
Identify each item to be
placed under CM, where it is to be stored, which tools to be used and the
personnel in charge of maintaining the baseline
2.6 Defect and Change Management
Procedure and tools for
reporting bugs, change requests and defect tracking tools
Test Plan (10)
2.1 Approach
Consistent with LCP, SSRD and Iteration Plan for
features to be tested
2.3 Requirements Verification Matrix
Consistent with 2.1
3.1 Hardware preparation
Explanation of hardware
required and the the preparation of the hardware such as network connectivity
3.2 Software preparation
Installation of software
required including the sequence
3.3 Other pre-test preparations
Describe where the test
data is going to come from
4.1 Responsibilities and staffing
Identify who will be responsible
for each test reponsibility
4.3 Schedule for testing
as per guidelines
5 Key measures
Explain the metrics used
to measure defects and test progress
7, 8 Defects and changes
Consistent with QMP 2.6
and RD 6
Test Reports (20)
Read the guidelines for grading the section
2 Test preparation
Consistent with TP 3
3 Test specifications
4 Test procedure specifications
5 Test incident report
6 Test log
7 Test Summary
Inspection Plan (7)
2 Inspection Items, participants and roles
Identify the documents,
code and designs to be inspected and who participates in inspections
3 Milestones
A high level description
of the schedule .
4 Process description
High level description of
the inspection process
5.1 Defects Severity
Explanation of each level
major and minor with examples
5.2 Defect Type
Explanation of each type
with examples
5.3 Category
Explanation of each category
with examples
Inspection Reports (13)
1 Participants and roles
Consistent with Inspection
Plan 2
2 Inspection Items
Consistent with Inspection
Plan 2
3, 4, 5 Defect data
6 Inspection Statistics
7 Defect Correction and Rework
Questions or Suggestions
Last Updated on 4/11/2000