 Trade In this Item for up to £11.80
Trade in Requirements Engineering: A Good Practice Guide for an Amazon.co.uk gift card of up to £11.80, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
More About the Authors
Discover books, learn about writers, and more.
Product Description
Product Description
"A marvellous book.a unique focus on what practising engineers need to do." Watts Humphrey, Software Engineering Institute, USA Requirements Engineering A good practice guide Find more RE resources at this web support site http://www.comp.lancs.ac.uk/computing/resources/re–gpg/ Visit our Web page! http://www.wiley.com/ compbooks/ Requirements engineering is the process of discovering, documenting and managing the requirements for a computer–based system. The goal of requirements engineering is to produce a set of system requirements which, as far as possible, is complete, consistent, relevant and reflects what the customer actually wants. Although this ideal is probably unattainable, the use of a systematic approach based on engineering principles leads to better requirements than the informal approach which is still commonly used. This book presents a set of guidelines which reflect the best practice in requirements engineering. Based on the authors′ experience in research and in software and systems development, these guidelines explain in an easy–to–understand way how you can improve your requirements engineering processes. The guidelines are applicable for any type of application and, in general, apply to both systems and software engineering. The guidelines here range from simple ′common sense′ to those which propose the introduction of complex new methods. The guidelines and process improvement schemes have been organised so that you can pick and choose according to your problems, goals and available budget. There are few dependencies between guidelines so you can introduce them in any order in your organisation. Guidelines presented in the book
∗ are consistent with ISO 9000 and CMM
∗ are ranked with cost/benefit analysis
∗ give implementation advice
∗ can be combined and applied to suit your organisation′s needs
∗ are supported by a web page pointing to RE tools and resources
∗ are consistent with ISO 9000 and CMM
∗ are ranked with cost/benefit analysis
∗ give implementation advice
∗ can be combined and applied to suit your organisation′s needs
∗ are supported by a web page pointing to RE tools and resources
From the Publisher
Sci Tech Book News, Sept 1997
Presents guidelines which reflect good practice in requirements engineering, based on the authors' experience in research and in software and systems development. The guidelines range from common sense tips to complex new methods, and can be used in any order which suits the reader's problems, goals and budget. Guidlelines are consistent with ISO 9000 and CMM, are ranked with cost and benefit analysis, include implementation advice, and can be combined and applied to suit an organization's needs.
Presents guidelines which reflect good practice in requirements engineering, based on the authors' experience in research and in software and systems development. The guidelines range from common sense tips to complex new methods, and can be used in any order which suits the reader's problems, goals and budget. Guidlelines are consistent with ISO 9000 and CMM, are ranked with cost and benefit analysis, include implementation advice, and can be combined and applied to suit an organization's needs.
Inside This Book
(Learn More)
First Sentence
This chapter introduces the notion of requirements engineering and requirements engineering process improvement. Read the first page
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
This chapter introduces the notion of requirements engineering and requirements engineering process improvement. Read the first page
Explore More
Concordance
Browse Sample PagesConcordance
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
1 of 1 people found the following review helpful:
5.0 out of 5 stars
A thorough and well-organised reference book for practitioners,
By
This review is from: Requirements Engineering: A Good Practice Guide (Paperback)
Of all the books and articles on requirements that I have read (and some that I have written), this book remains for me one of the best, and I find myself constantly referring back to it.
It is structured in the form of practices; this is reflected in each chapter title being in imperative form, such as "Define system boundaries" or "Organise formal requirements inspections". There are (according to my count) 82 practices covered, easily accessible thanks to the structure of the book. So far as I can see, the treatment given in the book remains surprisingly thorough. Even though it was written a decade ago, it is still highly relevant. I highly recommend it.
5.0 out of 5 stars
Requirements Engineering,
This review is from: Requirements Engineering: A Good Practice Guide (Paperback)
excellent condition. very practical book which has already prooved helpful in my work as a Business Analyst. I'm also studying a diploma in business analysis and this is very helpful for the RE module.
Share your thoughts with other customers: Create your own review
Most Helpful Customer Reviews on Amazon.com (beta) Amazon.com:
3.8 out of 5 stars (4 customer reviews) 13 of 13 people found the following review helpful:
5.0 out of 5 stars
Great for use at different levels,
By Doug Childs (dchilds@mediaone.net) - Published on Amazon.com
This review is from: Requirements Engineering: A Good Practice Guide (Paperback)
I've been in this part of the business for a while and I haven't seen anything quite like this book for requirements. A nice blend of theory and VERY practical advice, you can easily use the book in at several ways: 1. Better understanding of a particular techniques' effectiveness and context, for example use cases (called viewpoints here) or state-transition diagrams. 2. Flip through the book and see which guidelines you can most effectively apply to your current project, e.g. building a database or putting in a table of contents. 3. Evaluate your "maturity level" & determine how to improve your current requirements process.I can't tell if would be helpful to someone who had never wrestled with serious requirements, but even then, it has a good bibliography & website. Belongs on the analyst's working bookshelf. 10 of 12 people found the following review helpful:
2.0 out of 5 stars
Some decent suggestions, but fluff to content ratio is 5:1.,
By A Customer - Published on Amazon.com
This review is from: Requirements Engineering: A Good Practice Guide (Paperback)
There are some usable guidelines for requirements gathering, though I feel common sense would give you many of them. I think this book is watered down heavily to fill 350 pages; the content could have fit in 50 pages. The book was not thought out.
4 of 4 people found the following review helpful:
4.0 out of 5 stars
Valuable advices, but not for beginners,
By Christophe Addinquy - Published on Amazon.com
This review is from: Requirements Engineering: A Good Practice Guide (Paperback)
I found this book very insightfull, but it needs to have a first idea about what is the requirements engineering and how it's processed. Once you have this idea, this book helps you. You'll find here, essentially pieces of advices which looks like process patterns (in my opinion it should even improve the book to show these advices through a pattern form) to tackle specific problems whith requirements engineering. Moreover, these advices can be read separately. For the beginners, it mises a strong frame along the book to know what is exactly requirements management and so on. But I think the authors are right to do not try to satisfy everybody. As a weakness, I don't know why, but this book seems to be a bit old, where the edition date is only 1997, through a lot of details I feel to read a book written in the early 1980s. But this book is not about technology, so it's not a big weakness.
|
|
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.
|
