“If the purpose is to create one of the best books on requirements yet written, the authors have succeeded.” —Capers Jones Software can solve almost any problem. The trick is knowing what the problem is. With about half of all software errors originating in the requirements activity, it is clear that a better understanding of the problem is needed. Getting the requirements right is crucial if we are to build systems that best meet our needs. We know, beyond doubt, that the right requirements produce an end result that is as innovative and beneficial as it can be, and that system development is both effective and efficient. Mastering the Requirements Process: Getting Requirements Right, Third Edition, sets out an industry-proven process for gathering and verifying requirements, regardless of whether you work in a traditional or agile development environment. In this sweeping update of the bestselling guide, the authors show how to discover precisely what the customer wants and needs, in the most efficient manner possible. Features include The Volere requirements process for discovering requirements, for use with both traditional and iterative environments A specification template that can be used as the basis for your own requirements specifications Formality guides that help you funnel your efforts into only the requirements work needed for your particular development environment and project How to make requirements testable using fit criteria Checklists to help identify stakeholders, users, non-functional requirements, and more Methods for reusing requirements and requirements patterns New features include Strategy guides for different environments, including outsourcing Strategies for gathering and implementing requirements for iterative releases “Thinking above the line” to find the real problem How to move from requirements to finding the right solution The Brown Cow model for clearer viewpoints of the system Using story cards as requirements Using the Volere Knowledge Model to help record and communicate requirements Fundamental truths about requirements and system development
"Mastering the Requirements Process: Getting Requirements Right" sets out an industry-proven process for gathering and verifying requirements, regardless of whether you work in a traditional or agile development environment. In this sweeping update of the bestselling guide, the authors show how to discover precisely what the customer wants and needs, in the most efficient manner possible.
"If the purpose is to create one of the best books on requirements yet written, the authors have succeeded." —Capers Jones It is widely recognized that incorrect requirements account for up to 60 percent of errors in software products, and yet the majority of software development organizations do not have a formal requirements process. Many organizations appear willing to spend huge amounts on fixing and altering poorly specified software, but seem unwilling to invest a much smaller amount to get the requirements right in the first place. Mastering the Requirements Process, Second Edition , sets out an industry-proven process for gathering and verifying requirements with an eye toward today's agile development environments. In this total update of the bestselling guide, the authors show how to discover precisely what the customer wants and needs while doing the minimum requirements work according to the project's level of agility. Features include The Volere requirements process—completely specified, and revised for compatibility with agile environments A specification template that can be used as the basis for your own requirements specifications New agility ratings that help you funnel your efforts into only the requirements work needed for your particular development environment and project How to make requirements testable using fit criteria Iterative requirements gathering leading to faster delivery to the client Checklists to help identify stakeholders, users, nonfunctional requirements, and more Details on gathering and implementing requirements for iterative releases An expanded project sociology section for help with identifying and communicating with stakeholders Strategies for exploiting use cases to determine the best product to build Methods for reusing requirements and requirements patterns Examples showing how the techniques and templates are applied in real-world situations
Requirements are a crucial ingredient of any successful project. This is true for any product--software, hardware, consumer appliance, or large-scale construction. You have to understand its requirements--what is needed and desired--if you are to build the right product. Most developers recognize the truth in this statement, even if they don't always live up to it. Far less obvious, however, is the contribution that the requirements activity makes to project management. Requirements, along with other outputs from the requirements activity, are potent project management tools. In Requirements-Led Project Management, Suzanne and James Robertson show how to use requirements to manage the development lifecycle. They show program managers, product and project managers, team leaders, and business analysts specifically how to: Use requirements as input to project planning and decision-making Determine whether to invest in a project Deliver more appropriate products with a quick cycle time Measure and estimate the requirements effort Define the most effective requirements process for a project Manage stakeholder involvement and expectations Set requirements priorities Manage requirements across multiple domains and technologies Use requirements to communicate across business and technological boundaries In their previous book, Mastering the Requirements Process, the Robertsons defined Volere--their groundbreaking and now widely adopted requirements process. In this second book, they look at the outputs from the requirements process and demonstrate how you can take advantage of the all-important links between requirements and project success.
Author: Jeremy Dick
Release Date: 2017-08-23
Written for those who want to develop their knowledge of requirements engineering process, whether practitioners or students. Using the latest research and driven by practical experience from industry, Requirements Engineering gives useful hints to practitioners on how to write and structure requirements. It explains the importance of Systems Engineering and the creation of effective solutions to problems. It describes the underlying representations used in system modeling and introduces the UML2, and considers the relationship between requirements and modeling. Covering a generic multi-layer requirements process, the book discusses the key elements of effective requirements management. The latest version of DOORS (Version 7) - a software tool which serves as an enabler of a requirements management process - is also introduced to the reader here. Additional material and links are available at: http://www.requirementsengineering.info
Author: Ellen Gottesdiener
Publisher: Addison-Wesley Professional
Release Date: 2002
"I spend much time helping organizations capture requirements and even more time helping them recover from not capturing requirements. Many of them have gone through some motions regarding requirements as if they were sleepworking. It's time to wake up and do it right-and this book is going to be their alarm clock." -Jerry Weinberg, author of numerous books on productivity enhancement "In today's complex, fast-paced software development environment, collaboration-the intense peer-to-peer conversations that result in products, decisions, and knowledge sharing-is absolutely essential to success. But all too often, attempts to collaborate degenerate into agonizing meetings or ineffectual bull sessions. Ellen's wonderful book will help you bridge the gap-turning the agony of meetings into the ecstasy of effective collaboration." -Jim Highsmith, a pioneer in adaptive software development methods "Requirements by Collaboration presents a wealth of practical tools and techniques for facilitating requirements development workshops. It is suitable-no, essential reading-for requirements workshop facilitators. It will help both technical people and customer representatives participate in these critical contributions to software success." -Karl Wiegers, Principal Consultant, Process Impact, author of Software Requirements "The need for this particular book, at this particular time, is crystal clear. We have entered a new age where software development must be viewed as a form of business problem solving. That means direct user participation in developing 'requirements,' or more accurately, in jointly working the business problem. That, in turn, means facilitated sessions. In this book, Ellen Gottesdiener provides a wealth of practical ideas for ensuring that you have exactly the right stuff for this all-important area of professional art." -Ronald G. Ross, Principal, Business Rule Solutions, LLC, Executive Editor, www.BRCommunity.com "Gottesdiener's years of software development experience coupled with her straight-forward writing style make her book a perfect choice for either a senior developer or a midlevel project manager. In addition to her technical experience, her knowledge of group dynamics balance the book by educating the reader on how to manage conflict and personality differences within a requirements team-something that is missing from most requirements textbooks...It is a required 'handbook' that will be referred to again and again." -Kay Christian, ebusiness Consultant, Conifer, Colorado "Requirements by Collaboration is a 'must read' for any system stakeholder. End users and system analysts will learn the significant value they can add to the systems development process. Management will learn the tremendous return they may receive from making a modest time/people investment in facilitated sessions. Facilitators will discover ways to glean an amazing amount of high-quality information in a relatively brief time." -Russ Schwartz, Computer System Quality Consultant, Global Biotechnology Firm "In addition to showing how requirements are identified, evaluated, and confirmed, Ellen provides important guidance based on her own real-world experience for creating and managing the workshop environment in which requirements are generated. This book is an engaging and invaluable resource for project teams and sponsors, both business and IT, who are committed to achieving results in the most productive manner possible." -Hal Thilmony, Senior Manager, Business Process Improvement (Finance), CiscoSystems, Inc. "Project managers should read this book for assistance with planning the requirements process. Experienced facilitators will enrich their knowledge. New facilitators can use this book to get them up to speed and become more effective in less time." -Rob Stroober, Competence Development Manager and Project Manager, Deloitte &Touche Consultdata, The Netherlands "While many books discuss the details of software requirement artifacts (for example, use cases), Ellen's new book zeros in on effective workshop techniques and tools used to gather the content of these artifacts. As a pioneer in requirements workshops, she shares her real-life experiences in a comprehensive and easy-to-read book with many helpful examples and diagrams." -Bill Bird, Aera Energy LLC "Requirements by Collaboration is absolutely full of guidance on the most effective ways to use workshops in requirements capture. This book will help workshop owners and facilitators to determine and gain agreement on a sound set of requirements, which will form a solid foundation for the development work that is to follow." -Jennifer Stapleton, Software Process Consultant and author of DSDM: The Methodin Practice "This book provides an array of techniques within a clear, structured process, along with excellent examples of how and when to use them. It's an excellent, practical, and really useful handbook written by a very experienced author!" -Jean-Anne Kirk, Director DSDM Consortium and IAF Professional Development "Ellen has written a detailed, comprehensive, and practical handbook for facilitating groups in gathering requirements. The processes she outlines give the facilitator tools to bring together very different perspectives from stakeholders elegantly and with practical, useable results." -Jo Nelson, Principal, ICA Associates, Inc., Chair, IAF (2001-2002) Requirements by Collaboration: Workshops for Defining Needs focuses on the human side of software development--how well we work with our customers and teammates. Experience shows that the quality and degree of participation, communication, respect, and trust among all the stakeholders in a project can strongly influence its success or failure. Ellen Gottesdiener points out that such qualities are especially important when defining user requirements and she shows in this book exactly what to do about that fact. Gottesdiener shows specifically how to plan and conduct requirements workshops. These carefully organized and facilitated meetings bring business managers, technical staff, customers, and users into a setting where, together, they can discover, evolve, validate, verify, and agree upon their product needs. Not only are their requirements more effectively defined through this collaboration, but the foundation is laid for good teamwork throughout the entire project. Other books focus on how to build the product right. Requirements by Collaboration focuses instead on what must come first--the right product to build.
Author: Ian F. Alexander
Publisher: Addison-Wesley Professional
Release Date: 2002
Well-written requirements are crucial to systems of all kinds. This text explains and demonstrates exactly what requirements are for, and how to write them. It provides practical techniques and defines key terms, explaining and illustrating to develop the skills of good requirements writing.
Author: Ivy F. Hooks
Publisher: AMACOM Div American Mgmt Assn
Release Date: 2001
Genre: Business & Economics
This is a guide to eliminating the waste of time, money and effort resulting from poor product development. It provides product definition requirements needed at the start of any product development process.
Now in its third edition, this classic guide to software requirements engineering has been fully updated with new topics, examples, and guidance. Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development and management activities on software projects. Describes practical, effective, field-tested techniques for managing the requirements engineering process from end to end. Provides examples demonstrating how requirements "good practices" can lead to fewer change requests, higher customer satisfaction, and lower development costs. Fully updated with contemporary examples and many new practices and techniques. Describes how to apply effective requirements practices to agile projects and numerous other special project situations. Targeted to business analysts, developers, project managers, and other software project stakeholders who have a general understanding of the software development process. Shares the insights gleaned from the authors’ extensive experience delivering hundreds of software-requirements training courses, presentations, and webinars. New chapters are included on specifying data requirements, writing high-quality functional requirements, and requirements reuse. Considerable depth has been added on business requirements, elicitation techniques, and nonfunctional requirements. In addition, new chapters recommend effective requirements practices for various special project situations, including enhancement and replacement, packaged solutions, outsourced, business process automation, analytics and reporting, and embedded and other real-time systems projects.
Author: Robin F. Goldsmith
Publisher: Artech House
Release Date: 2004
While a number of books on the market deal with software requirements, this is the first resource to offer you a methodology for discovering and testing the real business requirements that software products must meet in order to provide value. The book provides you with practical techniques that help prevent the main causes of requirements creep, which in turn enhances software development success and satisfaction among the organizations that apply these approaches. Complementing discovery methods, you also learn more than 21 ways to test business requirements from the perspectives of assessing suitability of form, identifying overlooked requirements, and evaluating substance and content. The powerful techniques and methods presented are applied to a real business case from a company recognized for world-class excellence. You are introduced to the innovative Problem Pyramidtm technique which helps you more reliably identify the real problem and requirements content. From an examination of key methods for gathering and understanding information about requirements, to seven guidelines for documenting and communicating requirements, while avoiding analysis paralysis, this book is a comprehensive, single source for uncovering the real business requirements for your software development projects.
Author: Alan M. Davis
Publisher: Prentice Hall
Release Date: 1993-01-01
This revision of the bestselling software requirements book reflects the new way of categorizing software requirements techniques--objects, functions, and states. The author takes an analytical approach by helping the reader analyze which technique is best, rather than imposing one specific technique.
Learn how to create good requirements when designing hardware and software systems. While this book emphasizes writing traditional “shall” statements, it also provides guidance on use case design and creating user stories in support of agile methodologies. The book surveys modeling techniques and various tools that support requirements collection and analysis. You’ll learn to manage requirements, including discussions of document types and digital approaches using spreadsheets, generic databases, and dedicated requirements tools. Good, clear examples are presented, many related to real-world work the author has done during his career. Requirements Writing for System Engineeringantages of different requirements approaches and implement them correctly as your needs evolve. Unlike most requirements books, Requirements Writing for System Engineering teaches writing both hardware and software requirements because many projects include both areas. To exemplify this approach, two example projects are developed throughout the book, one focusing on hardware and the other on software. This book Presents many techniques for capturing requirements. Demonstrates gap analysis to find missing requirements. Shows how to address both software and hardware, as most projects involve both. Provides extensive examples of “shall” statements, user stories, and use cases. Explains how to supplement or replace traditional requirement statements with user stories and use cases that work well in agile development environments What You Will Learn Understand the 14 techniques for capturing all requirements. Address software and hardware needs; because most projects involve both. Ensure all statements meet the 16 attributes of a good requirement. Differentiate the 19 different functional types of requirement, and the 31 non-functional types. Write requirements properly based on extensive examples of good ‘shall’ statements, user stories, and use cases. Employ modeling techniques to mitigate the imprecision of words. Audience Writing Requirements teaches you to write requirements the correct way. It is targeted at the requirements engineer who wants to improve and master his craft. This is also an excellent book from which to teach requirements engineering at the university level. Government organizations at all levels, from Federal to local levels, can use this book to ensure they begin all development projects correctly. As well, contractor companies supporting government development are also excellent audiences for this book.