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 Specification and Agile Methodologies 149
Priority—this is based on the prioritization scheme adopted. Priority can be
assigned based on “traditional” prioritization of importance or on level of
detail (higher priority is assigned to higher detail).
Story points—this is the estimated time to implement the user story. is
aspect makes user stories helpful for effort and cost estimation.
Description—this is one to three sentences describing the story.
A sample layout for these elements on an index card is shown in Table 7.1.
Initial user stories are usually gathered in small offsite meetings. Stories can be
generated either th
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