Discovering Requirements: How to Specify Products and Services Paperback – 23 Mar 2009
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Frequently Bought Together
Customers Who Bought This Item Also Bought
Enter your mobile number 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.
Getting the download link through email is temporarily not available. Please check back later.
To get the free app, enter your mobile phone number.
From the Back Cover
This book is not only of practical value. It s also a lot of fun to read. Michael Jackson, The Open University. Do you need to know how to create good requirements? Discovering Requirements offers a set of simple, robust, and effective cognitive tools for building requirements. Using worked examples throughout the text, it shows you how to develop an understanding of any problem, leading to questions such as: What are you trying to achieve? Who is involved, and how? What do those people want? Do they agree? How do you envisage this working? What could go wrong? Why are you making these decisions? What are you assuming? The established author team of Ian Alexander and Ljerka Beus–Dukic answer these and related questions, using a set of complementary techniques, including stakeholder analysis, goal modelling, context modelling, storytelling and scenario modelling, identifying risks and threats, describing rationales, defining terms in a project dictionary, and prioritizing. This easy to read guide is full of carefully–checked tips and tricks. Illustrated with worked examples, checklists, summaries, keywords and exercises, this book will encourage you to move closer to the real problems you re trying to solve. Guest boxes from other experts give you additional hints for your projects. Invaluable for anyone specifying requirements including IT practitioners, engineers, developers, business analysts, test engineers, configuration managers, quality engineers and project managers. A practical sourcebook for lecturers as well as students studying software engineering who want to learn about requirements work in industry. Once you ve read this book you will be ready to create good requirements!
What Other Items Do Customers Buy After Viewing This Item?
Top Customer Reviews
This book is well organised, practical and insightful. The authors propose a matrix of "Elements" and "Contexts" for requirements discovery. Following this model, the book is divided into two parts; Part 1 - Discovering Requirement Elements (with chapters on Stakeholders; Goals; Context, Interfaces, Scope; Scenarios; Qualities and Constraints; Rationale and Assumptions; Definitions; Measurements, and; Priorities), and Part 2 - Discovery Contexts (with chapters on Requirements from Individuals; Requirements from Groups; Requirements from Things; Trade-offs, and; Putting it all Together). In the Introduction, the authors state that requirements specification can be considered to be a network of related elements, "...and indeed, the chapter structure of this book can be seen as a customisable template for organising the requirements on your project."
If pithy quotes are a good measure of the value of a book, then this is a great book. I stopped scribbling down quotes by page 10 when I had amassed the following:
* "Requirements are discovered by the use of appropriate inquiry techniques. They are not sitting about, waiting to be `captured'."
* "Discovery, however surprising and delightful the actual moment of realisation, comes as a result of a deliberate search."
* "Projects need to pay attention to discovering their requirements, using a battery of complementary techniques...Read more ›
The authors approach their task in a typically rigorous manner by describing firstly different requirements elements, then different discovery contexts, before combining both elements and contexts to suggest approaches for different types of project.
Among the highlights of the book are:
- A lucid explanation of Alexander's onion model for stakeholder analysis, put in context using goal diagrams, where stakeholders' aspirations are mapped to look for any conflict early in the project.
- The use of the Soft Systems Method to capture the soft boundaries of the project environment before formalising it using context diagrams and event tables.
- Some simple but effective ways to capture high-level scenarios in a workshop environment.
- Using goal analysis to capture constraints and qualities. There is a lot of material in this chapter, including some that will be increasingly important in coming years, such as sustainability.
- The use of rationale models and goal structuring notation to document assumptions.
- A large chapter on measurements, with a balanced approach to the debate on whether acceptance tests are a substitute for requirements statements (a view promulgated in the Agile world), leaving the reader to decide what is best for his or her circumstances. Recognising that many large projects now include a service element, there is a sizeable section on quality of service measures.Read more ›
The book is so useful I have it as a reference guide in my day to day work as a Business Analyst, I wish I'd bought the book several years ago.
But the term defining implies that your customer tells what they want and you write it down in a meeting, polish later on, and that's it. Go on and start a project ... and problems like above surfaces.
Requirements need to be discovered and this is the best book on how to systematically "tease" out what the customer (=stakeholders) want, what are they assuming, but not saying unless explicitly asked, etc.
The "abstraction level" is very good, not too cookbook specific and not too academically general. Text is very readable and clear and well structured.
This book helps you to direct your (and your customer) thinking to obtain desired goals, and thus is valuable also for people outside the engineering field.
In their book, Discovering Requirements, Ian Alexander and Ljerka Beus-Dukic combine their years of experience to produce a work that will be of value to the practitioner and the academic alike. It is a work that, as it says on the cover, is timely, practical and reliable.
The book starts from the earliest project, or even pre-project, stage, where context and scope are typically unclear. Stress is placed on the importance of understanding the real business need before attempting to satisfy that need; crucial advice in the present economic climate.
In Part 1 of the book, the reader is guided through a logical process in which the stakeholders and their goals are identified, analysed and progressively refined, leading to the creation of validated, verifiable and non conflicting requirements.
Although there is a logical flow to part 1, the book, wisely, does not define a prescriptive process. It does however contain all the ingredients and sufficient guidance to allow the reader to create their own recipes for `processes' that can be intelligently applied to specific situations. The book's two part structure directly supports this goal; part 2 describes the contexts in which the ingredients can be used and mixed in order to discover the requirements. The final chapter of this large work contains invaluable advice on `Putting It All Together'.
In short, this book provides a valuable addition to the literature on requirements. I can thoroughly recommend it.
Most Recent Customer Reviews
I am only 70 pages into this book and my first impression is that its style is very much in the tradition of 'teach yourself'
Its laid out well and instructs the... Read more
An excellent and practical book on requirements engineering (RE) that can be recommended for both novices and experience professionals. Read morePublished on 23 Dec. 2009 by Ilia Bider
Outstanding! Its construction reflects clearly the authors are intimately acquainted with the real world and what is practicable in terms of approach. Read morePublished on 9 May 2009 by A. J. Gavaghan
Look for similar items by category
- Books > Business, Finance & Law > Management > Human Resources > Professional Development
- Books > Computing & Internet > Digital Lifestyle > Online Shopping > Amazon
- Books > Computing & Internet > Programming > Languages & Tools
- Books > Computing & Internet > Programming > Software Design, Testing & Engineering > Functional Programming
- Books > Computing & Internet > Programming > Software Design, Testing & Engineering > Software Architecture