11 Steps in VV&A:
Introduction
What and Why of VV&A
1. Examine Proc Doc
2. Examine Sys Doc
3. Interview Developers
4. Interview Users
5. Examine Code I
6. Examine Code II
7. Determine Truth
8. Generate Test Cases
9. Run Test Cases
10. Review Test Output
11. Assessment
SDP Template
SQPP Template
SCMP Template
WBS Template
|
Basic Software Development Plan (SDP) Template
- Introduction
- Reference Documents
- Deliverables
- Code
- Documentation
- Demos
- Briefings
- Project Organization [see note below]
- Project Manager
- Project Software Manager
- Software Engineering Manager
- Software Configuration Management (SCM) Manager
- SQA Manager
- System Engineering Manager
- Test and Support Manager
- Subcontractor Manager
- Software Development Team
- Schedule
- List milestones
- List required tools
- Project Estimates
- Cost
- Staffing
- Size
- Risk Management
- Software Requirements
- Process model
- Producing Changes
- Reviewing Changes
- Managing Changes
- Traceability of Changes
- Controlling Changes
- Software Design
- Preliminary Design
- Detailed Design
- Design Reviews
- Coding
- Style standards
- Unit testing
- Software Development Folders
- Overview of Configuration Management
- Reviews
- Team Composition
- Process
- Criteria for Peer Reviews
- Criteria for Customer Reviews
- Criteria for Software Quality Assurance (SQA)
- Integration Testing
- Test Procedures
- Format of Test Case Input, Output, and Truth
- Documentation
- External Documentation
- Internal (Project or Company) Documentation
- Metrics (planned and actuals)
- Size
- Cost
- Staffing
- Milestones
- Training
- Security
- Subcontractor Agreements
The set of managers in Section 4 will all exist (or at least be separate individuals) only in large projects (50 to 100 people or more). In small or medium-size projects, one individual will hold several (or all) of these positions.
|