1.0 Title: Contract Deliverable Requirements List
2.0 Purpose: This is a dual purpose document - for both the planning and the execution stage of a project.
In the planning stage:
Use the CDRL to identify and evaluate the correct CDID's to use, identify missing CDID's which need to be developed and to assess the cost/benefit of having the document or artefact at all. The purpose of the CDID "key codes" is to identify the high profile data elements and to prevent their redundant creation if possible. Ideally - critical data elements have one control point and are not calculated again and again by different sources (and usually with different values as a result.)
In the execution stage:
The CDRL is the "go to" document to identify what project artefacts have been deemed worthy of being produced (and hence - paid for), what their status is, who's responsible for it, where to find them, etc.
note: replaces km4
3.0 Usage
4.0 Frequency
5.0 References
6.0 Responsibility
7.0 Ownership
8.0 Effort
9.0 Risks
10.0 Contents
The pm2c CDRL
10.1 filename
11.0 MetaData
12.0 File Handling Policy
13.0 Procedures
14.0 Tutorials
14.1 CDID template