liveBook · Manning

Requirements

As explained in Data-Oriented Programming in Java

A requirement is a stated condition or capability that a software system or process must satisfy.

Requirements state the conditions or capabilities a software system or process must satisfy. They often arrive as loose statements, so the practical work is to expose vague assumptions and turn them into precise, explicit rules. section 4.1 section 5.1

A useful requirements pass makes the domain meaning visible by:

  • Starting with the stated goal rather than existing implementation code. section 4.1
  • Separating combined rules such as thresholds, eligibility, dates, amounts, and configurable values. section 5.1
  • Connecting each implementation decision to a recognizable business requirement instead of disguising meaning behind fields, null checks, or service calls. section 5.2
  • Representing alternatives and combinations explicitly, so the resulting model can prevent invalid states and misuse. section 4.1

Late-fee requirements

A late-fee feature must find open past-due invoices, calculate a percentage of the customer's total past-due balance in USD, apply grace periods and configurable minimum and maximum thresholds, and preserve every decision for auditing. Turning this into explicit requirements exposes details that a mechanical sequence of repository calls can hide. section 5.1 section 5.2

Table 5.1 Requirements!
ID
Requirements
A0
The system shall charge late fees to customers with open past due invoices as of the Evaluation Date plus the customer's Grace Period
A1
 
The fee shall be calculated as a percentage of the customer's total past due
A2
 
Fees shall be computed in USD
A3
 
The Due Date of the Fee Invoice shall be based on the customer's Payment Terms
A4
 
Delivery and Invoice Number generation shall handled by the Billing System
B0
The customer shall have a Grace Period
B1
 
Customers in good standing receive a 60-day grace period
B2
 
Customers in acceptable standing receive a 30-day grace period
B3
 
Customers in poor standing must pay by end of month
C0
The system shall charge these fees based on Configurable Rules
C1
 
The system shall have a Minimum Due Threshold
C2
 
The system shall have a Maximum Due Threshold
C3
 
The Fee Percentage must be configurable based on the customer's billing Country Code
D0
The system shall not charge late fees for special cases
D1
 
Fees less than Minimum Due Threshold shall not be sent to the customer
D2
 
Fees greater than Maximum Due Threshold shall not be sent to the customer UNLESS the customer has been marked as Approved for Large Fees
E0
The system shall track Customer Approvals
E1
 
Customers exceeding the Maximum Due Threshold must be flagged for Manual Approval
F0
All fees will be auditable and recorded by the system
F1
 
The system shall record which invoices were involved in the fee computation
G0
 
The system shall record a rationale for invoices which cannot be billed

Browse the requirement table for identifiers, customer standing rules, fee thresholds, percentages, currency, payment terms, and billing-system responsibilities. section 5.1

How Data-Oriented Programming in Java covers it

How deep it goes
Refines ambiguity into explicit rules and models, while stopping short of prescribing one complete implementation.
Examples
Uses rocket manufacturing checklists and an auditable late-fee service with customer standing, thresholds, dates, and billing rules.
What it assumes
Assumes enough domain context to interpret business statements, while teaching how to begin from ambiguity rather than existing code.
What you can do after
Build it from scratch by translating ambiguous business statements into precise, explicit domain rules and safer code models.
How it connects
Connects requirements to domain modeling, algebraic data types, domain behaviors, business rules, and data orientation.

Also explained in

Compare how 16 books explain requirements →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Data-Oriented Programming in Java. The section links point to the parts of the book it draws on.