- Hardcover: 198 pages
- Publisher: Springer; 2nd edition (September 14, 2004)
- Language: English
- ISBN-10: 1852338792
- ISBN-13: 978-1852338794
- Product Dimensions: 6.1 x 0.6 x 9.2 inches
- Shipping Weight: 14.4 ounces (View shipping rates and policies)
- Average Customer Review: 8 customer reviews
- Amazon Best Sellers Rank: #3,451,123 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Requirements Engineering 2nd Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
From the Back Cover
Using the latest research and driven by practical experience from industry, the third edition of this popular book provides useful information to practitioners on how to write and structure requirements. • Explains the importance of Systems Engineering and the creation of effective solutions to problems • Describes the underlying representations used in system modelling and introduces the UML2 • Considers the relationship between requirements and modelling • Covers a generic multi-layer requirements process • Discusses the key elements of effective requirements management • Explains the important concept of rich traceability In this third edition the authors have updated the overview of DOORS to include the changes featured in version 9.2. An expanded description of Product Family Management and a more explicit definition of Requirements Engineering are also included. Requirements Engineering is written for those who want to develop their knowledge of requirements engineering, whether practitioners or students. --This text refers to an out of print or unavailable edition of this title.
Discover books for all types of engineers, auto enthusiasts, and much more. Learn more
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
This book really didn't hit the mark for me. It mainly falls down in not clearly communicating its content. It tries to cover a fair bit of territory in a small book, and the result is you can only understand it if you already know the content, which pretty much defeats the purpose of reading it.
A fair bit of the content covered things that I wanted to know more about, but I found that the book either told me things I already knew, or else covered things that I didn't know but didn't explain them properly. It is pitched at a reasonably high level, so if you are newer to the area you would get lost or baffled quickly.
It is a fairly short book, at a little under 200 small pages, and so coverage of some areas was very brief and as a result not informative.
The authors are from a software background, and although they have tried to make the book applicable to any systems engineering process, their software background does come through. Often content is explained using concepts and language from software engineering, which may not communicate well to those from other fields.
There is some use of examples in the book, and this does help to explain the concepts, but I found many of the examples were too limited or trivial to provide a deeper understanding.
Modelling section. Techniques were only briefly covered, and although the fact that there is an intimate relationship between modelling and requirements is stressed early on in the text, there is no significant explanation of how to use modelling to help generate requirements.
Chapter 4 has quite a good coverage of spec writing, but really quite brief (just 14 pages). Nothing specific is mentioned about reviewing, apart from the implication that the criteria for good requirements stated should be the basis for reviewing. The boilerplate requirement concept was quite good.
Perhaps the best chapter in the book for me was Chapter 7 on advanced traceability. This had some good ideas that were generally well explained, although at times the explanations used concepts and language that were targeted towards software types.
FORMATTING AND PRESENTATION
Despite my real desire to learn more about requirements engineering, I couldn't help my attention and interest level taking a dive whenever I read more of this book. It's hard work to digest - both in the writing style, the graphics, and the whole approach to informing the reader. Little effort has been giving to making the experience enjoyable or easy.
Diagrams are very basic, and typically uninformative. Have a look at the diagram on p116 in the "look Inside" function as a typical example. If figure 6.1 makes the text on this page clear to you, then disregard my comment about the diagrams being uninformative for your case.
Formatting of the document (eg font) is very dull, which adds to the lack of readability. There are also occasional editorial problems, like sentences chopped off with out an ending.
Maybe I'm being a little harsh on this book, because at the same time I was reading a book called "The non-designers Design Book", about designing documents. The Design book was a model of clear presentation, visually attractive, lots of clear examples and enjoyable to read, which Requirements Engineering was none of. Although the Design book is pitched straight at beginners, after reading it, the flaws in the design of Requirements Engineering book as a document were very obvious.
The beautiful thing aboout this generic process (and the concrete ones to follow it) is that V&V and change management are intrinsically part of it. The authors are particularly strong in their treatment of traceability. They have gone into an unusual depth. The book has some good advice on writing better requirements . In particular, I find the idea of requirements boilerplates (i.e. templates for each class of requirements) extremely useful. The book concludes with an introduction/demonstration of the DOORS RE tool, from Telelogic (the affiliation of two of the authors).
Overall, this is an excellent book that every requirements engineer, should have on their desk.