qaweb

Enterprise & Internet Test Development & Localization

Skip to Content ↓
  

16 Critical Software Practices (Excerpt US Navy)

Sep 11th, 2011
by admin.

COMPLETE ARTICLE AT http://www.spmn.com/16CSP.html

16 Critical Software Practices CD Online


16 CRITICAL SOFTWARE PRACTICESTM

for Performance-based management

PURPOSE

PROJECT INTEGRITY
1. ADOPT CONTINUOUS PROGRAM RISK MANAGEMENT
2. ESTIMATE COST AND SCHEDULE EMPIRICALLY
3. USE METRICS TO MANAGE
4. TRACK EARNED VALUE
5. TRACK DEFECTS AGAINST QUALITY TARGETS
6. TREAT PEOPLE AS THE MOST IMPORTANT RESOURCE

CONSTRUCTION INTEGRITY
7. ADOPT LIFE CYCLE CONFIGURATION MANAGEMENT
8. MANAGE AND TRACE REQUIREMENTS
9. USE SYSTEM-BASED SOFTWARE DESIGN
10. ENSURE DATA AND DATABASE INTEROPERABILITY
11. DEFINE AND CONTROL INTERFACES
12. DESIGN TWICE, CODE ONCE
13. ASSESS REUSE RISKS AND COSTS

PRODUCT STABILITY AND INTEGRITY
14. INSPECT REQUIREMENTS AND DESIGN
15. MANAGE TESTING AS A CONTINUOUS PROCESS
16. COMPILE AND SMOKE TEST FREQUENTLY

  • Share this:
  • Facebook
  • Print
  • Email

Posted in: QA-munity.

← JMeter Links Offsite QA Resources →

Leave a Reply Cancel reply

You must be logged in to post a comment.

  • RSS QA in San Diego

    • Sr. .NET Programmer Analyst
    • Software Development Quality Analyst
    • QA Analyst
    • QTP Automation Engineer
    • Project Manager - Data Center
  • Articles

    • History’s Worst Software Bugs
    • Education predicts Economic Success?
    • Helpful Online Consumer Resources
    • Offsite QA Resources
    • 16 Critical Software Practices (Excerpt US Navy)
    • JMeter Links
    • Android versus iPhone
    • Nations Ranked by Education
    • Web Testing Scope and Browser Market Share
  • Login

    • Register
    • Lost your password?
© 2012 qaweb   ~   ~ united states of america