Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Managing Software Requirements the Agile Way

You're reading from   Managing Software Requirements the Agile Way Bridge the gap between software requirements and executable specifications to deliver successful projects

Arrow left icon
Product type Paperback
Published in Aug 2020
Publisher Packt
ISBN-13 9781800206465
Length 214 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Fred Heath Fred Heath
Author Profile Icon Fred Heath
Fred Heath
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Chapter 1: The Requirements Domain 2. Chapter 2: Impact Mapping and Behavior-Driven Development FREE CHAPTER 3. Chapter 3: Writing Fantastic Features with the Gherkin Language 4. Chapter 4: Crafting Features Using Principles and Patterns 5. Chapter 5: Discovering and Analyzing Requirements 6. Chapter 6: Organizing Requirements 7. Chapter 7: Feature-First Development 8. Chapter 8: Creating Automated Verification Code 9. Chapter 9: The Requirements Life Cycle 10. Chapter 10: Use Case: The Camford University Paper Publishing System 11. Other Books You May Enjoy

Analyzing requirements

In Chapter 1, The Requirements Domain, we talked about the concept of the requirements funnel. This is a mental model that illustrates how requirements keep coming at us from many directions and in many forms and shapes. We need to filter these requirements and convert them to quantifiable and knowable entities so that we can process them. These items are our requirement domain entities (goals, stakeholders, capabilities, and features). If you've done chemistry at school, you may have used a separating funnel. These funnels are used to separate mixed liquids, such as oil and water. To convert requirements to requirement domain entities, we must use a mental separating funnel, which will filter the mixture of incoming requirements and then identify and create the relevant domain entities. Once we've done that, we can model those entities as an impact map, that is, our requirements model.

Our funnel will consist of distinct filtering techniques. These...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime