|
Essential Contents
|
Unacceptable
(0-5 pts.)
|
Acceptable
(6-10 pts.)
|
Distinguished
(11-12 pts.)
|
|
problem statement
|
- Problem statement is not included
|
- Problem statement is included, with some elaborating discussion to provide context for IT system
|
- Problem statement is included, with a detailed discussion of the boundaries of the IT system, with engineering rationale
|
|
project scope
|
- No project scope discussion is provided
|
- Project scope is discussed, but this section essentially reiterates the problem statement
|
- Project scope is clearly discussed and clearly linked to problem statement, with engineering rationale
|
|
actors and responsibilities
|
- There is limited to no discussion of the roles and responsibilities of the key actors in the project
|
- Only the project manager and software engineers are discussed
|
- The project manager, software engineers, testers, QA, CM, V&V, and client are discussed
|
|
project effort and duration estimates
|
- Only a qualitative discussion of effort and duration is provided
|
- A quantitative analysis of project effort and duration is provided based on techniques discussed in the text or other valid references
|
- Multiple quantitative methods for effort and duration are provided to demonstrate the need to show variations and rationales for the best-estimate
|
|
project schedule with work breakdown
|
- No Gantt chart or other graphic depiction of the SDLC schedule is given
- There is no correlation of the schedule and the duration and effort estimates
- There is no decomposition of high-level SDLC tasks into lower-level sub-tasks, i.e., work breakdown
|
- Gantt or other chart depicting critical SDLC tasks over time is provided
- Project timeline is consistent with the project duration estimate
- SDLC tasks are insufficiently or not at all decomposed
|
- Schedule correlates with project effort and duration estimates
- SDLC task decomposition, i.e., work breakdown, within schedule is detailed, and incorporates overarching CM and QA tasks.
|
|
staffing
|
- No estimate is made of staff size based on effort and duration estimates
- There is only a limited discussion of the required staffing, with no rationale
|
- Staff size estimate is quantitative but not based on the methods provided in the text or other references
|
- Detailed discussion of staffing is provided using formal estimation models, e.g., COCOMO, that are based on the text or other valid references
|
|
resources, dependencies, and project specifics
|
- Little to no discussion of project resources, including staff, is provided
- No discussion of project dependencies is given
|
- Discussion includes resources, besides staff, that are required for the successful completion of the project
- Project dependencies are addressed
|
- Comprehensive discussion itemizes all resources required for the successful completion of the project
- SDLC process is selected
- Programming language is identified with rationale
- Project dependencies are discussed
|
|
risk assessment
|
- No risk assessment is provided
|
- Project risks are discussed qualitatively, with no analysis or ranking of risks
|
- Project risks are presented quantitatively and ranked according to techniques described in the text or other valid references
- Risk mitigation is discussed for the highest-ranked risks
|
|
formal document structure based on an industry standard, including title page, TOC, references
|
- SDP has little formal structure
- No references are provided
|
- SDP has little formal structure
- References are provided
|
- SDP has formal structure based on an SDP standard
- Complete list of references is provided, including problem statement and SPP standard
|