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


Requirements Development, which includes elicitation, definition, analysis,specification, and validation. This is a Level 3 (Defined) Process Area for the SEI CMMI for Development (CMMI-DEV), and is separate from requirements management (a Level 2 CMMI-DEV Process Area), although there is considearble overlap. Requirements Development is also a Level 2 Process Area in the CMMI for Acquisition. Acquisition Requirements Development has three specific goals: developing customer requirements, developing contractual requirements, and analyzing and validating requirements.

The resources listed here primarily address requirements development, but could also address requirements management and use cases, two other subtopics for requirements engineering.
  • Education and Training (3) updated - Education and training courses which primarily address this subtopic of Requirements Development, which includes elicitation, definition, analysis,specification, and validation. Other courses that address requirements development can be found in the main toopic area of Requirements Engineering.

  • Literature (10) updated - Books, articles, and Tech Reports which primarily address this subtopic of Requirements Development, which includes elicitation, definition, analysis,specification, and validation. Other courses that address requirements development can be found in the main toopic area of Requirements Engineering.

  • Related Resources (6) updated - Resources which primarily address this subtopic of Requirements Development, which includes elicitation, definition, analysis,specification, and validation. Other courses that address requirements development can be found in the main toopic area of Requirements Engineering.

  • Subtopics of Special Interest
    • Requirements Tradeoffs/Negotions (4) updated - This is a subtopic of requirements development, and addresses performing negotiations and doing trade-offs as part of the requirements development process. Requirements Negotiation (RN) is a practice implemented early in the planning stages for each project, or phase of an incremental or evolutionary development approach (and whenever requirements change) in a collaborative environment where there is mutual respect and trust among stakeholders.

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