liveBook · Manning

Requirements

As explained in Developer Experience on Kubernetes

A statement of a needed software capability or change, typically accompanied by conditions for considering it complete.

A requirement is a formal description of what a system should do or how it should behave. It turns a problem statement into a starting point for delivering software value. section 1.1.1 section 2.1.1

Requirements can describe several kinds of software change:

  • Creating a new application. section 1.2
  • Adding a feature to an existing distributed system. section 1.2
  • Fixing a bug in a microservice or refactoring a modular monolith. section 1.2

Teams may capture requirements in different forms. A user story keeps the feature short and user-centered: “As a [role], I want [feature] so that [benefit].” It supports planning and prioritization while leaving implementation details for later discussion. section 2.1.1

Acceptance criteria define when a requirement is complete. Developers and stakeholders agree on these conditions before implementation, then use them to determine whether the requested behavior has been delivered. section 1.2 section 2.1.1

Appointment category selection

As a patient, I want to select an appointment category so that I can book the right kind of appointment. Given Cardiology is selected, the booking options should show only options for that category.

How Developer Experience on Kubernetes covers it

How deep it goes
Defines requirements, user stories, and acceptance criteria, then connects them to inner-loop implementation without detailing implementation mechanics.
Examples
Uses appointment-category selection and a Cardiology booking scenario to demonstrate a user story and testable behavior.
What you can do after
Apply requirements by expressing user value, agreeing on completion conditions, and initiating focused implementation work.
How it connects
Connects problem statements, user stories, acceptance criteria, inner loops, outer loops, version control, and the software development lifecycle.

Also explained in

Compare how 16 books explain requirements →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Developer Experience on Kubernetes. The section links point to the parts of the book it draws on.