How deeply does "Looks Good to Me" cover requirements?

Connects requirements to feature discussion and acceptance criteria, but does not prescribe a formal requirements method.

Requirements

As explained in "Looks Good to Me"

A requested capability, behavior, or constraint that software is expected to satisfy.

Requirements are the requested capabilities, behaviors, or constraints that software is expected to satisfy. In practice, implementation can fail by omitting requested components, missing acceptance criteria, or solving the wrong problem. section 4.4.4

Make requirements easier to satisfy by:

Discussing new features thoroughly before implementation. section 4.4.4
Defining clear acceptance criteria for each feature. section 4.4.4
Encouraging questions and clarification during development. section 4.4.4

A requirement missed in review

A pull request may appear complete yet fail because it does not address what the business requested, implements only part of the request, or satisfies neither the agreed acceptance criteria nor the actual problem. section 4.4.4

How "Looks Good to Me" covers it

liveBook manning.com

Read "Looks Good to Me" on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Lead Developer Career GuideA specified capability, behavior, or constraint that a software product or feature must satisfy.
liveBook manning.com

BDD in Action, Second EditionA requirement is a stated capability, condition, or constraint that a software system is expected to satisfy.
liveBook manning.com

Architecting an Apache Iceberg LakehouseA storage requirement is an explicit, testable condition that a storage system or architecture must satisfy.
liveBook manning.com

Delivering Machine Learning Projects: From design to deploymentA requirement is a stated need, capability, quality attribute, constraint, or operational condition that a system or project must address.
liveBook manning.com

Object-Oriented Software Design in C++A software requirement is a capability, constraint, or condition that a software system must satisfy.
liveBook manning.com

Software Design for Python ProgrammersA software requirement is a specified capability, constraint, or quality that a software application must satisfy.
liveBook manning.com

Build Python Web Apps with StreamlitSoftware requirements are stated needs, capabilities, goals, and constraints that a software system is expected to satisfy.
liveBook manning.com

Everyday Data VisualizationA stated need, capability, constraint, or condition that a project, product, or system is expected to satisfy.
liveBook manning.com

Functional Design and Architecture: Examples in HaskellA requirement is a stated capability, constraint, or goal that a software system must satisfy.
liveBook manning.com

Coding with AISoftware requirements are specified capabilities, constraints, and qualities that a software system must satisfy.
liveBook manning.com

Collaborative Software Design: How to facilitate domain modeling decisionsA requirement is a stated need, constraint, or capability that a software system is expected to satisfy.
liveBook manning.com

Design for DevelopersA business need or constraint is a product or project outcome that an organization expects to satisfy.

Compare how 13 books explain requirements →

Related concepts

nonfunctional requirementincludes · A nonfunctional requirement specifies a quality attribute, constraint, or operating condition that a system must satisfy beyond the particular functions it performs.
controlimplemented by · Control is the means or degree of influence over a system’s actions, behavior, processes, or operation.
functional requirementincludes · A functional requirement specifies a behavior or capability that a system must provide or enable.
testmeasured by · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
use caseused by · A use case is a description of a situation or interaction in which a system, method, or capability is applied to achieve or support a goal or outcome.

This explainer was generated by Manning's knowledge graph from the text of "Looks Good to Me". The section links point to the parts of the book it draws on.