Email:
Password: [?] 
  Register with the DACS
Site Search: Advanced Search
Search: Bibliographic Database(SEBD)     Lifecycle Database(SLED)    DoD Acronyms 
DACS Home DACS Services Publications Training About Us DACS Store Suggest A Link
Rate this page's content:
  poor
excellent


Software Risk Management is a proactive approach for minimizing the uncertainty and potential loss associated with a project by providing insights to support informed decision making. It is performed continually over the life of a program, from initiation to retirement. Some categories of risk include product size, business impact, customer-related, process, technology, development environment, staffing (size and experience), schedule, and cost.


See also DACS Gold Practice Formal Risk Management.

  • Case Studies (5) - Reports and studies describing the impact of risk on
    software projects.

  • Education and Training (5) - Courses, seminars, conferences, training products, and resources for learning about Software Risk Management.

  • Experts (10) updated - Researchers, educators, and experts in Software Risk Management and related topics.

  • Literature (7) updated - Literature devoted to Software Risk Management.

  • Related Resources (12) - Information-rich sites containing materials relevant to Software Risk Management.

  • Service Providers/Consultants (13) - Organizations and corporations offering Software Risk Management products and services.

  • Tools (10) - Developers, catalogs, and demonstrations of Software Risk Management tools and methods.

  • Subtopics of Special Interest
    • Verification and Validation (10) - Verification and Validation (V&V) is a series of technical and managerial activities performed by someone other than the developer of a system to improve the quality and reliability of the system and assure the developed product satisfies the user's operational needs. Verification is the assurance that the products of a particular development phase are consistent with the requirements of that phase and preceding phase(s), while validation is the assurance that the final product meets system requirements. V&V can be performed by an outside agency, which is referred to as Independent V&V, or IV&V, or by a group within the organization but not the developer, referred to as Internal V&V. Use of V&V often accompanies testing, can improve quality assurance, and can reduce risk.

Suggest Supporting Web Sites
Related pages:
sidebar
sidebar
sidebar

s

s

s

s


SISOS cover
DACS Latest Technical Report


TEMS Logo
Visit the DTIC TEMS Initiative

   DACS Gold Practice Initiative ROI Dashboard
 
Acquisition Process Improvement
Architecture-First Approach
Assess Reuse Risks and Costs
Binary Quality Gates at the Inch-Pebble Level
Capture artifacts in rigorous, model-based notation
Commercial Specifications and Standards/Open Systems
Defect Tracking Against Quality Targets
Develop and Maintain a Life-cycle Business Case
Ensure Interoperability
Formal Inspections
Formal Risk Management
Goal-Question-Metric Approach
Integrated Product and Process Development
Manage Requirements
Metrics-based Scheduling
Model Based Testing
Plan for Technology Insertion
Requirements Trade-Off/Negotiation
Statistical Process Control
Track Earned Value
  Access benefit data from software technical and management improvements including SEI CMMI, PSP/TSP, Cleanroom, Inspections, and Agile Development.

View the ROI Dashboard
Copyright © 2010, ITT Corporation    Privacy Policy
webmaster@thedacs.com
775 Daedalian Drive Rome, NY 13441
(800) 214-7921 Fax: 315-838-7130
This site is best viewed in Firefox 1.0+ or IE 6.0+
XHTML