Abstract
The entire book up until this point was spent talking about requirements as purely shall statements. This concept of requirements was the foundation of the waterfall development methodology, starting with hardware and then translated to software. However, other types of requirements are referred to such as user stories, use cases, and modeling.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
“Capability Maturity Model,” Wikipedia (see the "Reference" section)
- 2.
“Capability Maturity Model Integration,” Wikipedia (see the "Reference" section)
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2016 George Koelsch
About this chapter
Cite this chapter
Koelsch, G. (2016). Supplementing or Replacing Standard Requirements. In: Requirements Writing for System Engineering. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2099-3_12
Download citation
DOI: https://doi.org/10.1007/978-1-4842-2099-3_12
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-2098-6
Online ISBN: 978-1-4842-2099-3
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)