The Interface Between Requirements Development and All Other Systems Engineering Processes
Hood, C., Wiedemann, S., Fichtinger, S., Pautz, U.
2008, XII, 275 p.
Springer eBooks may be purchased by end-customers only and are sold without copy protection (DRM free). Instead, all eBooks include personalized watermarks. This means you can read the Springer eBooks across numerous devices such as Laptops, eReaders, and tablets.
You can pay for Springer eBooks with Visa, Mastercard, American Express or Paypal.
After the purchase you can directly download the eBook file or read it online in our Springer eBook Reader. Furthermore your eBook will be stored in your MySpringer account. So you can always re-download your eBooks.
It is well known that incorrect requirements account for up to two-thirds of software defects in software products. And yet, too many software development organizations still do not have a formal requirements process. Those who do practice requirements management often do not fully understand the special relationships between requirements management and the other disciplines of software development. This book attempts to show how requirements form the thread that connects all the disciplines of software development – a relationship that has long eluded many software development organizations. For software development organizations that are looking for ways to do requirements traceability, this book can show them what to trace from and what to trace to. … Using the interfaces as described in the book, the authors demonstrate how an implemented feature can be traced back to the person or group that wanted it during the requirements elicitation. Another positive feature is the arrangement: it is organized so that it can be used as a reference book. For every aspect of the software development process, the reader can zero in on the particular area of interest to see how requirements management relates to that development discipline.
(In: Computing Reviews, April 2009, Boniface Nwugwo, Ellicott City, MD)