| | |  | Computer Security | Home » » Software Requirements | | | | | | | Description: | | Learn proven, real-world techniques for managing the software requirements engineering process. This award-winning book has been expanded with new topics, including use cases, up-to-date tools, more field examples, and a new troubleshooting guide. | | | Features: | |
• ISBN13: 9780735618794
• Condition: New
• Notes: BUY WITH CONFIDENCE, Over one million books sold! 98% Positive feedback. Compare our books, prices and service to the competition. 100% Satisfaction Guaranteed
| | | Product Details: | | | Author:
| Karl E. Wiegers | | Paperback:
| 544 pages | | Publisher:
| Microsoft Press | | Publication Date:
| February 26, 2003 | | Language:
| English | | ISBN:
| 0735618798 | | Package Length:
| 8.8 inches | | Package Width:
| 7.3 inches | | Package Height:
| 1.4 inches | | Package Weight:
| 2.35 pounds | | Average Customer Rating:
|  based on 48 reviews |
| | | | Customer Reviews: | |
Average Customer Review:
Write an online review and share your thoughts with other customers.
0 of 2 found the following review helpful:
 Worth your timeJan 22, 2010
For the most part this is rather informative and practical text.
Positive: It establishes an importance of solid software requirements process. Without solid requirements process, software engineering/development is doomed to be extremely painful for stakeholders, developers, and pretty much everyone involved in the project. After reading this book you will have to reconsider the importance of requirements engineering as foundational to the project success. It give practical examples on development SRS (soft. requirements specifications) and Vision and Scope document.
Negative: Some sections are not well elaborated (which is understandable, due to the nature of the specific subject of the book). For instance, when it deals with various diagrams, I would rather recommend reading other supplemental texts to give you better understanding of various diagrams, and their use. As you may know, for example, in ERD, it is not advisable to have M:N relationships (many-to-many). But of course SOME specific situations may require otherwise.
Other thing I did not like, is invisible to the most readers couple expression found in the book on p. 214 "Avoid getting caught up in the dogmatic mindsets and religious wars that sometimes take place in the world of software development methods and models. Instead use what you need to best explain your system's requirements". Here, while the underlying idea is somewhat valid, the wording is not.
1.) "Avoid getting caught in the dogmatic mindsets" - is in itself pretty much sound like a dogma.
2.) "Religious wars" - is somewhat disrespectful to the question matter of the ultimate reality - i.e. God. Unless you are Freudian, Marxist, or otherwise secular naturalist, there is no reason to compare "religious wars" to the political wars, where second is well known show. In other words, I wold appreciate author not using religious terminology, or comparing religious language to the politics.
All in all, this is practical and informative book about requirements engineering.
Recommended.
1 of 1 found the following review helpful:
 Great overview on methodology of requirements gatheringNov 09, 2009
Wiegers' book is one of the standard references for requirements gathering that's around. We have these on our shelves at our company for all the analysts and while there are other references around on project management and project implementation, this book has outlines of all the different parts focusing on requirements gathering: gathering participants on the project and client side, setting expectations, how to document, what your first steps are as well as the pitfalls. Every analyst needs this on their book shelf as a reference.
1 of 1 found the following review helpful:
Excellent and very practical book, I DO recommend itApr 09, 2009
I do recommend this book, both for experienced of novice sofware developers or consultants for several reasons:
1. The content has a great balance between practical advice and theory, so it won't burden you with information applicable to 5% (e.g. huge projects) of your daily work
2. It is well written, both in content and edition style (format) so it is very easy to read and understand quickly
3. It has references to standards and literacy but it is just to illustrate and not so heavily that makes it hard to read
To sum up, its one of the very best SW Engineering books I've read so far and so that I do recommend it.
Alex Ballarin
IT Consultant
Cynertia Consulting, Barcelona, Spain
Bible of requirementsSep 20, 2008
Very practical book about requirements, from communication with customer to changing Your organization requirement elicitation process. Almost anything is thoroughly covered. Companion site includes numerous documents to get You started.
Great coverage of requirements development with example documentsJun 07, 2008
I have had this book for some time and recently realized how often I use it as a reference when I am trying to figure out a way to document or model a feature. This book is well worth the price, I have definitely benefited from keeping this book near my desk.
Although this book is not to replace books dedicated to topics such as Use Cases, technical writing, UML and modeling, change control, or test case development it is a great place to see them all work together in context.
Don't forget to visit the `Requirements Engineering" section of the authors' site. There you will find the samples from the book and other useful articles.
| | |
|
