Electric Power Research Institute (EPRI) Home Page

About | Newsletter | Site Index  

Software Development Requirements   

 You Are Here: Home > Development Process > Step 2 / Step 3 / Software Type Matrix > Developer Corporate Software Quality Assurance Plan

 Development Process:

  1. Concept Development
  2. Request for Proposal
  3. Contract Package
  4. Implementation
  5. Preproduction Test
  6. Final Acceptance Test
  7. Support & Maintenance

 Software Requirements:

 Software Type Matrix

Developer Corporate Software Quality Assurance Plan

The developer must include the following topics in their quality assurance plan:

  1. Corporation, Plan Title and version, date effective
  2. Purpose of Plan
  3. Glossary of Terms
  4. How documentation is handled (some examples are):
    • Statement of Work
    • Planning Documents such as the Software Requirements Document (SRD)
    • User's Manual / Developer's Manual, etc.
  5. Verification & Validation (V&V) of software
  6. Project management
  7. Software standards used
  8. User Interface Standards used
  9. Development Tools and Techniques
  10. Configuration Management and how source code is saved
  11. Reviews and Audits
  12. Testing
  13. Bug Reporting and Tracking
  14. Training
  15. Risk Management
  16. Process Improvement
  17. Signoffs needed for plan and plan revisions

Note: All topics above must be covered in the plan, but the plan should not be limited to just these topics.


Careers | Contact EPRI | Copyright Policy | Privacy Statement | Terms of Use | EPRI Site Map 
EPRI 3420 Hillview Avenue, Palo Alto, California 94304
© Electric Power Research Institute, Inc. 2001- All rights reserved