bannera

Book A.
Introduction

Book B.
7150 Requirements Guidance

Book C.
Topics

Tools,
References, & Terms

SPAN
(NASA Only)

Link
Leave blank if none exists

Title
This is the text which will be hyperlinked, if a link exists

CMMI for Development, Version 1.3: Improving processes for developing better products and services,

SWE or Topic

SWE-004, SWE-005, SWE-013, SWE-014, SWE-024, SWE-032, SWE-036, SWE-040, SWE-044, SWE-049, SWE-050, SWE-051, SWE-054, SWE-056, SWE-075, SWE-076, SWE-077, SWE-090, SWE-091, SWE-092, SWE-093, SWE-094, SWE-095, SWE-096, SWE-100, SWE-101, SWE-105, SWE-106, SWE-107, SWE-109, SWE-117, SWE-129, SWE-136, SWE-209, Intro, Topic 5.04, Topic 5.05, Topic 5.09, Topic 5.15, Topic 7.01, Topic 7.4, Topic 7.04, Topic 7.5, Topic 7.05, Topic 7.18, SRS, Maint, Metrics, SAP, Train, Topic 8.51,

Citation
This contains additional information, which will appear after the title, separated by a comma

CMMI Development Team (2010). CMU/SEI-2010-TR-033, Software Engineering Institute.

Notes
More specific directions where to look in the resource for relevant content

Example Reference as it will appear to end user:

  1. Title, Citation

where:


Quotes used in SWEs and Topics

"Criteria are established for determining what constitutes a significant deviation from the project plan. A basis for gauging issues and problems is necessary to determine when corrective action should be taken. Corrective actions can lead to re-planning, which may include revising the original plan, establishing new agreements, or including mitigation activities in the current plan. The project plan defines when (e.g., under what circumstances, with what frequency) the criteria will be applied and by whom."

Requirements Analysis - Analyze requirements to ensure that they are necessary and sufficient - SP3.3
"In light of the operational concept and scenarios, the requirements for one level of the product hierarchy are analyzed to determine whether they are necessary and sufficient to meet the objectives of higher levels of the product hierarchy. The analyzed requirements then provide the basis for more detailed and precise requirements for lower levels of the product hierarchy."
"As products are defined, their relationship to higher level requirements and the higher level definition of the functionality and quality attributes should be understood. Also, the key requirements used to track progress are determined. For instance, the weight of a product or size of a software product can be monitored through development based on its risk or its criticality to the customer."