Skip to Main Content
Requirements Engineering for Software and Systems
book

Requirements Engineering for Software and Systems

by Phillip A. Laplante
March 2011
Intermediate to advanced content levelIntermediate to advanced
264 pages
7h 40m
English
CRC Press
Content preview from Requirements Engineering for Software and Systems
Requirements Risk Management 107
Leaving incompleteness in the SRS document is an invitation to disaster later
in the project. While it is likely that there may be a few incomplete terms in a
well-written SRS due to pending requirements, the number of such words should
be kept to an absolute minimum.
Subjects
Subjects are a count of unique combinations of words immediately preceding
imperatives in the source file. is count is an indication of the scope of subjects
addressed by the specification.
e ARM tool counted a total of 372 subjects in the Smart Home SRS document.
Specification Depth
Specification depth counts the number of imper ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

System Requirements Engineering

System Requirements Engineering

Jean-Yves Bron
Process for System Architecture and Requirements Engineering

Process for System Architecture and Requirements Engineering

Derek Hatley, Peter Hruschka, Imtiaz Pirbhai

Publisher Resources

ISBN: 9781420064681