Chapter 1: How is software built?

Anyone who simply lets an AI start programming away quickly gets code and just as quickly loses certainty about whether this code does the right thing.

Dr. Norbert Lotter
Dr. Norbert Lotter


The answer lies in a shift of the checkpoint: no longer is every line of code at the center, but rather the specification. The first chapter shows how to keep control without losing speed by building an end-to-end chain of need, requirements, assurances, and code. In this way, AI-supported custom development becomes not only fast but also methodically manageable.

Related News

Part 1: Two Survival Questions for the Software Industry

Part 1: Two Survival Questions for the Software Industry

How do you keep control over what emerges when it is no longer humans who write the code, but AI?

Part 2: Specifying with Structure and Method

Part 2: Specifying with Structure and Method

How do you write a specification from which an agent reliably builds, and which at the same time captures the why of a system?

Part 3: Teamwork in the Age of Coding Agents

Part 3: Teamwork in the Age of Coding Agents

What becomes of Scrum when coding agents change the work?

Part 4: When the Methodology Itself Becomes Agentic

Part 4: When the Methodology Itself Becomes Agentic

Is today’s approach suited to continue supporting AI-supported development also in the future?

Back