AI Assisted Software Engineering

Map

The map of the book

Nothing in software engineering stands alone. An estimate depends on how size is counted, a schedule on how progress is credited, reliability on what reviews and tests can catch. This wheel shows all 18 chapters in their four parts, colored by verdict, the 159 key concepts they define, and the 77 pairs of chapters that lean on each other most. Click a chapter or a concept to follow the connections.

Verdict
Part
Part I: FoundationsPart II: The Life Cycle, AuditedPart III: Agent TeamsPart IV: Practice 1 The Coordination Problem 2 The Assumption Audit 3 Life-Cycle Models 4 Requirements 5 Size Estimation 6 Cost and Schedule 7 Project Management 8 Coordination at Scale 9 Risk Management 10 Design for Change 11 Construction 12 Reviews 13 Testing and Evaluation 14 Configuration Mgmt. 15 Reliability 16 Roles and Assurance 17 Coordination, No Talk 18 The Whole Life Cycle 18 chapters159 concepts · 77 links

HoldsRecalibrateBreaksInvertsNo verdictConceptLines join chapters that cite each other; thicker means more often

The same map as a list

  1. 01 The Coordination Problem, 1968 to Now Part I
  2. 02 The Assumption Audit: A Method That Outlasts the Tools Part I
  3. 03 Life-Cycle Models When Iteration Is Cheap Recalibrate
  4. 04 Requirements as the Primary Artifact Inverts
  5. 05 Size Estimation: What Function Points Still Measure Breaks
  6. 06 Cost and Schedule Estimation After COCOMO Breaks
  7. 07 Project Management and Where Value Is Earned Recalibrate
  8. 08 Coordination at Scale: Shared Context vs. Shared Messages Holds
  9. 09 Risk Management: Project Risk and Adversarial Risk Recalibrate / Breaks
  10. 10 Design for Change, and for Agents Holds
  11. 11 Construction When Code Is Cheap Inverts
  12. 12 Reviews: Inspecting Evidence, Not Diffs Recalibrate
  13. 13 Testing, Evaluation, and Tests as Steering Recalibrate
  14. 14 Configuration Management When Agents Commit Breaks
  15. 15 Reliability of Nondeterministic Systems Breaks
  16. 16 Roles and the Four Conditions for Assurance Part III
  17. 17 Coordination Without Communication: The Bound and the Leak Test Part III
  18. 18 Running the Whole Life Cycle: The Engineer as Manager of an Agent Team Part IV

The thirteen verdicts

ChLoad-bearing assumptionVerdict
3Iteration is expensive, so phase boundaries and loop length are set by the cost of reworkRecalibrate
4Implementers fill gaps with tacit knowledge and ask when unsureInverts
5Product size predicts effortBreaks
6Effort is a function of the size of human-written codeBreaks
7Progress is measured by work completedRecalibrate
8Coordination happens through bandwidth-limited messagesHolds
9Risks have estimable probabilitiesRecalibrate / Breaks
10Maintainers can hold only part of a system in mind, so design knowledge must be localized behind interfacesHolds
11Code is scarce; its author understands itInverts
12Rates and checklists are calibrated to human authorsRecalibrate
13Tests are written with intent independent of the defectRecalibrate
14Behavior is determined by versioned source, and the version history records how each change was producedBreaks
15The program is fixed between fixes; execution is deterministic; failures are independentBreaks

Concepts are the chapters' key terms. A concept is linked to another chapter when that chapter uses the term by name.