1. As-built specs:
OCD (2)
Check for the proposed system diagram's consistency with the proposed
architecture.
SSRD (5)
Well described implementation and support requirements
Testable capability requirement description
Clear prioritization of capability requirements
SSAD and MDL (20)
Go through the Rose Model and match the model against the
structure given in
Tools-->Rationale Rose template for MBASE product models (5)
Well described entities, use cases, and components (2)
Software level operations and classs model (8)
Proper signature descriptions for methods.
Use of proper associations, aggregations and
dependencies
Completed enterprise model consistent with the
entity model in OCD (3)
Configuration model (2)
Package and directory structure consistent with
the architecture
FRD (3)
Explanation of the priorities (1)
Explanation of risks (1)
Explanation of business case (1)
LCP (20)
Milestones and Products (3)
Responsibilities (3)
Approach (12)
Resources (2)
Iteration Plan (13)
1.1 Capabilities to be implemented (1)
Consistent with LCP
1.2 Capabilities to be tested (1)
Clear explanation of testing methods or why the
capability is not being tested
2.1 Schedule (5)
Should be a MS Project based plan
2.2 Resources (1)
All team members should be accounted for.
2.3 Responsibilities (3)
Each team member should have clear set of
responsibilities with the developers assigned responsibility for individual modules
3 Approach (1)
Consistent with the LCP and other parts of CTS
documents
4 Assumptions (1)
Iteration Assessment Report (5)
1.1 Capabilities Implemented (1)
Consistent with Iteration Plan 1.1
1.2 Summary of test results (1/2)
Consistent with test reports
1.3 Open problems (1/2)
Consistent with test reports
1.4 Objectives Reached (1/2)
Consistent with Iteration Plan 1.4
2 Adherence to Plan (1)
Lessons learned, deadlines missed and
achievements
3 Approach and suggestions (1/2)
Suggested changes to approach for next
iteration
4 External Changes Occurred (1/2)
Events occurred out of the control of this
project that influenced application of the plans
5 Suggested Actions (1/2)
Changes to the architecture, test or concept of
operation
Release Description (5)
1 Inventory released (1)
List of items released including software,
documents and manuals
2 Compatibility notes (1/2)
List of compatible softwares such as browser
versions and workarounds
4.1 New features (1)
Consistent with Iteration Assessment Report 1.1
4.3 Upcoming changes (1)
Consistent with LCP for next iteration
5 Known bugs (1/2)
Consistent with Iteration Assessment report 1.3
6 Defect and Change Reporting Procedures (1)
Description of tools and procedures to be used
for reporting errors and tracking change, Consistent with QMP 2.6
Quality Management Plan (10)
2.1 Design Guidelines (2)
Specific criteria to be used for design,
optimization and avoiding errors
2.2 Coding Guidelines (2.5)
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 (1/2)
Consistent with test plan
2.4 Inspection and Reviews (1/2)
Consistent with inspection plan
2.5 Configuration Management (3)
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 (1.5)
Procedure and tools for reporting bugs, change
requests and defect tracking tools
Test Plan (10)
2.1 Approach (1)
Consistent with LCP, SSRD and Iteration Plan for features to be tested
2.3 Requirements Verification Matrix (1)
Consistent with 2.1
3.1 Hardware preparation (1/2)
Explanation of hardware required and the the
preparation of the hardware such as network connectivity
3.2 Software preparation (1)
Installation of software required including the
sequence
3.3 Other pre-test preparations (1)
Describe where the test data is going to come
from
4.1 Responsibilities and staffing (2)
Identify who will be responsible for each test
reponsibility
4.3 Schedule for testing (2)
as per guidelines
5 Key measures (1/2)
Explain the metrics used to measure defects and
test progress
7, 8 Defects and changes (1)
Consistent with QMP 2.6 and RD 6
Test Reports (10)
Read the guidelines for grading the section
2 Test preparation (1/2)
Consistent with TP 3
3 Test specifications (4)
4 Test procedure specifications (1.5)
5 Test incident report (1)
6 Test log (1)
7 Test Summary (2)
Inspection Plan (6)
2 Inspection Items, participants and roles (2)
Identify the documents, code and designs to be
inspected and who participates in inspections
3 Milestones (1)
A high level description of the schedule .
4 Process description (.5)
High level description of the inspection
process
5.1 Defects Severity (1)
Explanation of each level major and minor with
examples
5.2 Defect Type (1)
Explanation of each type with examples
5.3 Category (0.5)
Explanation of each category with examples
Inspection Reports (6)
1 Participants and roles (1)
Consistent with Inspection Plan 2
2 Inspection Items (1)
Consistent with Inspection Plan 2
3, 4, 5 Defect data (1.5)
6 Inspection Statistics (1.5)
7 Defect Correction and Rework (1)
Questions or
Suggestions
Last Updated on 4/3/2000