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

Chapter 3: Writing Fantastic Features with the Gherkin Language

In the previous chapter, we discussed capabilities and features and we learned how to define and model them using Impact Maps. We also introduced Behavior-Driven Development (BDD) and discussed how it's centered around features. In this chapter, we'll build on this knowledge by talking exclusively about Features. We'll discover how to write them correctly, how to accurately specify system behavior with Scenarios, and what makes our Features executable specifications that can be used to automate our system's verification. Features being written incompletely or inaccurately will mean that our system's behavior will not be properly conveyed to our stakeholders, which is the pre-cursor to ambiguity, misinterpretations, and – ultimately – project failure. In this chapter, we will make sure that this doesn't happen.

In particular, we will cover the following:

  • What's...
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