liveBook · Manning

Chapter 2: Understanding the problem

What you will learn in chapter 2 of Decision Engineering

The chapter introduction explains why engineers must understand the problem and its business context before choosing a technical solution.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The chapter introduction explains why engineers must understand the problem and its business context before choosing a technical solution.

Key terms: problem, solution, constraint, business context, requirements

2.1 Problem definition beyond requirements

The section frames problem definition as understanding what people are trying to accomplish and separating architecture-defining requirements from implementation details.

Key terms: problem definition, functional requirements, implementation detail, design-deciding requirement

2.1.1 From quick solutions to the real needs

This section shows how engineers can get past an initial request for a system to understand the need behind it, consider fitting alternatives, and hear user context firsthand.

Key terms: pull toward solutions, underlying needs, Jobs-to-Be-Done, Impact Mapping, reflex solutions, purpose-built tool, best fit, discovery sessions, raw signals, product requirements

2.1.2 How engineering shapes the requirements

Engineering helps shape requirements by exposing feasibility and architectural costs early, so teams can meet the underlying user need at an acceptable cost.

Key terms: requirements, viable, engineering input, full-text search, synchronisation pipeline, operational overhead, guided filtering, product ideation workshop, design sprint, feasibility

2.1.3 Architecturally significant requirements

This section explains how to identify requirements that could change a system’s architecture and how to consider likely future needs without overengineering.

Key terms: Architecturally significant requirements, ASRs, foundational design, what would break this, minimal design, advanced relevance ranking, ASR, non-functional requirements, NFRs, scale

2.2 Thinking in service tiers

The section explains why engineers must make non-functional expectations explicit and introduces service tiers as a way to connect those expectations to architectural choices.

Key terms: functional requirements, non-functional requirements, ASR, service tier, non-functional expectation, architectural implications, service tiers, consequences of failure, over-engineering, under-engineering

2.2.1 Availability

Availability tiers turn uptime needs into a business conversation about the cost of downtime and the architectural investment it justifies.

Key terms: availability tiers, downtime, High, Standard, Service Level Objective (SLO), uptime target, availability requirements, system, subsystem, standalone component

2.2.2 Durability

This section explains how to judge data durability by the consequences of loss and the failures a design protects against, while considering durability alongside availability.

Key terms: availability, durability, durability forces, failure scenario, architectural guarantees, tiers, source of truth, search index, reindex, durability tiers

2.2.3 Latency

The section shows how human perception and usage context turn latency expectations into service tiers that guide targets and engineering trade-offs.

Key terms: latency, service tiers, synchronous path, asynchronous, percentile, p95, latency expectations, Responsive tier, Acceptable, backoffice

2.2.4 Load

This section explains how to describe load, plan for peaks, and choose scalability measures that fit each component’s actual demand.

Key terms: throughput, load, scalability, load profile, daily peaks, read-heavy paths, write-heavy ones, background processing, peak load scenarios, worst case

2.2.5 Volatility

The section treats expected frequency of change as a non-functional requirement that should influence architectural investment.

Key terms: volatility, volatility tiers, isolation, decoupling, foundational components, campaign components, ranking and relevance logic, configuration-driven ranking rules, feature-flagged algorithms, index schema

2.2.6 Comparing service tiers

The section shows how comparing systems across five service-tier dimensions reveals differences that should shape architectural choices before solution discussions begin.

Key terms: service tiers, spider diagram, availability, durability, latency, load

2.3 Compliance requirements

This section explains why compliance needs a different approach from tiered non-functional requirements: legal obligations depend on applicability, while security depends on specific risks and controls.

Key terms: compliance requirements, non-functional, service tiers, continuous properties, legal and regulatory obligations, security, risk-and-control, threats, controls

2.3.1 Separating requirements from controls

The section distinguishes compliance requirements from the controls used to satisfy them and explains how to maintain and select those controls.

Key terms: requirement, control, threat models, legal, compliance, or security specialists, controls, implementation complexity, legal or security risks

2.3.2 Legal requirements

This section explains how legal and contractual requirements constrain architecture, why they must be identified early, and how a data inventory helps map them to design decisions.

Key terms: legal requirements, data residency, right to erasure, contractual obligations, costly redesign, legal, data inventory, personal or regulated data, jurisdictions, retention

2.3.3 Security requirements

This section explains where security requirements come from and how teams derive system-specific requirements from threats before choosing controls.

Key terms: industry best practices, standards and regulations, security requirements, security requirements catalogs, use case, threat modelling, threats, security requirement, control, collaborative discussion

2.3.4 Common tips for addressing compliance requirements

The section explains how to address legal and security requirements collaboratively: involve specialists early, choose proportionate controls, and record why each control was chosen.

Key terms: compliance stakeholders, architectural options, constraints, compliance requirements, controls, risk, sensitivity, proportional safeguards, requirements, threat

2.3.5 What about architecture requirements?

This section defines architecture requirements as internal constraints on system design and deployment and explains when those constraints provide value.

Key terms: architecture requirements, compliance requirements, deployment targets, approved languages, frameworks, or libraries, consistency, simplify operations, well-supported path, shared component library, mature deployment platform

2.4 When the problem is ready for solution discussion

The section explains when a problem description is sufficiently clear to discuss solutions and shows how a backoffice-search example keeps needs and constraints distinct from implementation choices.

Key terms: problem understanding, ready for solutions discussion, job, solution space, ASRs, architecture-shaping, implementation details, non-functional dimension, service tier, compliance constraint

2.5 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 1: Understanding technical decisions Chapter 3: Reading the context →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.