- Paperback: 330 pages
- Publisher: Microsoft Press,U.S. (1 Oct 1999)
- Language English
- ISBN-10: 0735606315
- ISBN-13: 978-0735606319
- Product Dimensions: 22.9 x 18.8 x 3 cm
- Average Customer Review: 4.2 out of 5 stars See all reviews (5 customer reviews)
- Amazon Bestsellers Rank: 1,351,963 in Books (See Top 100 in Books)
- See Complete Table of Contents
Software Requirements
and over one million other books are available for Amazon Kindle .
Learn more
| ||||||||||||||||||||||||
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Plus, get an extra £5 Gift Certificate when you trade in books worth £10 or more before June 30, 2012. Visit the Books Trade-In Store for more details. |
|
There is a newer edition of this item:
|
Product details |
More About the Author
Product Description
Amazon.co.uk Review
"Requirements" are essential for creating successful software because they let users and developers agree on what features will be delivered in new systems. Karl Wiegers' Software Requirements shows you how to define and get more out of software requirements with dozens of "best practices" and tips that make this book a valuable resource for both software project managers and developers.
The book's common-sense approach provides exemplary project management skills tailored to gathering (and refining, implementing and eventually tracking) software requirements. While the book often cites recent software engineering studies, the focus always returns to practical management techniques. A case study for a chemical tracking application frames the book, and most chapters begin with anecdotes that demonstrate situations in which users and developers fail to comprehend each other about a software project's ultimate goals. (If you've ever worked in the field, these stories will probably sound all too familiar.)
This book offers hope, though, for improving your software design process with dozens of tips on getting better design input from your customers and then using these requirements to generate a variety of design documents. There are numerous "templates" and sample documents, too--a big help for the busy software manager.
Several standout sections here cover negotiating difficult steps in the process, particularly how to manage shifting requirements as projects move forward and keeping the various users and stakeholders contented throughout the software process. Late in the book, the author surveys today's software management tools and shows how to pick the right ones for your organisation.
Anchored by the author's considerable experience and software engineering expertise, this jargon-free and practical guide to software requirements can definitely give you the edge in managing software projects more efficiently. --Richard Dragan
Topics covered: software requirements specifications (SRS), business and user requirements, risk management, the requirements process, sample documents and templates, requirements development: elicitation, analysis, specification and verification, rights and responsibilities for software customers, best practices, project management tips, process assessment and improvement, types of users, product champions, use cases and other diagrams, tips for prototyping, managing requirements change, change centred boards (CCBs), evaluating and using requirements tools, requirements traceability matrix, impact analysis.
Product Description
Concise, readable, and expert advice for collecting and analyzing software requirements. Wiegers presents a palette of best practices for collecting, validating and managing software requirements, together with examples of their successful application to real-world projects. This is one of the few pragmatic resources on this topic.
Inside This Book
(Learn More)
Browse and search another edition of this book.
Browse and search another edition of this book.
First Sentence
If you've ever been on the customer side of a conversation like this, you know how frustrating it is to use a software product that doesn't let you perform an essential task. Read the first page
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
If you've ever been on the customer side of a conversation like this, you know how frustrating it is to use a software product that doesn't let you perform an essential task. Read the first page
Explore More
Concordance
Browse Sample PagesConcordance
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
9 of 9 people found the following review helpful
Format:Paperback
I've been using this book for over 2 months now and find it invaluable. It has provided a flexible framework for introducing requirements engineering and management practices into my working regime. There are templates for Vision and Scope documents, Software Requirements Specifications and other useful documents. Furthermore, it demonstrates how Use Case driven elicitation, and notations such as DFD's, Class Diagrams etc. fit together. One critisism, and a bonus too, is that it does not prescribe a definate process, but simply introduces techniques that you can use in your projects, and so may be a little overwhelming to the begginer .
6 of 6 people found the following review helpful
Format:Paperback
If you are interested in learning more about pure requirements analysis then this is a great point of reference. Wiegers assumes no previous knowledge so the user is lead through chapters providing overviews of key analysis skills, the role of the requirements analyst and key analysis techniques.
In software apporach terms this book will take you up to the formation of a 'Vision and Scope' document and Requirements Specification. It does not focus as much on Systems Analysis (which is a positive as there are many other books on that subject). Instead it focuses on the early stages of software development and walks the reader through a case study based on a new cafeteria system.
I find this book useful as a quick and easy reference for training and mentoring new analysts. There is very little technical jargon and the key messages are clear and well presented. For experienced analysts it is still of use as a reference text but many chapters will simply be skimmed through.
The only criticisms I have is that it doesn't cover the role of the requirements analyst in more contemporary agile software approaches. However, Wiegers has collated together a strong collection of knowledge and advice and it is a worthwhile addition to anyones analysis book collection.
Format:Paperback
"Software Requirements" by Karl Wiegers is a book on how to keep all the turnaround of analysis process under control. For this intelligent and useful book, Wiegers goes over the last ten years of technical literature on the multiple aspects of analyzing and designing software, managing project risks and requirements changes. From all this literature Wiegers takes only working methods, practical tips, useful tools and stimulating solutions, reabsorbing all in a complex but smooth methodology that assigns to the analyst a role of collaborator and guide for business and project managers, users, developers and testers all along the process of software production - that is, a process of shaping and implementing requirements. The customer/analyst partnership transforms at first business needs in high level requirements through the formulation of a vision and scope document; then analysts and user representatives descend from the context diagram to the product details with the help of use cases and prototyping; finally a software requirements specification is drafted and handled through version control, requirements estimation, prioritization, inspection and tracing, and the adoption of a requirements change control process. This book can effectively help analysts to rethink and reshape the way to face all the difficulties of their work, from the very first contact with customers and their needs. They will recognise many frustrating situations - and find hints and instruments to govern them. Surely a book worth the money.
Would you like to see more reviews about this item?
Were these reviews helpful?
Let us know
Most Recent Customer Reviews
Good book
I've read it quite easily and appreciated both the contents and accessible language used. Easy to understand.
Looking forward to read part II (more about SR).
Looking forward to read part II (more about SR).
Published on 16 Jan 2008 by Paulo G. Pedro
ATTENTION: Big disappointment.
I am a quality assurance manager at a software house. If you want to improve or just assess your requirements engineering process/procedures, this is definetely NOT your book. Read more
Published on 28 Feb 2000
Listmania!
|
|
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
