Errata

Head First Software Architecture

Errata for Head First Software Architecture

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Other Digital Version Section: "Writing ADRs: Establishing the context" and Section "Writing ADRs: Writing the decision" o
Figure 2-43 and Figure 2-45.

I read this awesome book (Early Release) on O'Reilly.

1. Figure 2-43 and 2-45 both should make "Context" come before "Decision"
2. Figure 2-43 should make "Context" blod.
3. Figure 2-45 should make "Decision" blod.

 Longyue Li  Jul 03, 2023 
Other Digital Version Chapter 1, software architecture crossword
6 down

"Decisions can be strategic of ____"

should be

"Decisions can be strategic or ____"

 Wes Reynolds  Apr 03, 2024 
O'Reilly learning platform Page Chapter: 04, Section: a_balancing_act
paragraphs after the tightly coupled logical components

After the tightly coupled architecture diagram, there are four paragraphs describing the trade-offs. Could you please advise if the second and fourth paragraphs are correctly placed, or should they be swapped?

Thank you.

The four paragraphs:

With the tightly coupled architecture, if you want to know what happens when a customer places an order, you only have to look at the Order Placement component to understand the workflow.

However, changing the Item Pricing and Supplier Ordering components will no longer affect the Order Placement component.

With loose coupling, you distribute the knowledge about what needs to happen, so that no one component knows all the steps. If you want to understand the workflow of placing an order, you have to go to multiple components to get the full picture.

However, in this case, the Order Placement component is dependent on four other components. If any one of those components changes, it could break the Order Placement component.

 Ahmed Farag  May 13, 2024 
O'Reilly learning platform Page Near the end of Ch 10
Above the section "Wrapping it up"

There is a missing or corrupted graphic near the end of chapter ten of the book on the O'Reilly Learning Platform. Where the little square is showing, there should be a graphic.

 Anonymous  Jul 01, 2025 
PDF Page xviii
1st para

an architectural

should be

an architecture

 Bhavesh  Sep 10, 2025 
PDF Page 2. Architectural Characteristics: Know Your Capabilities
Characteristics are nondomain design considerations

There is a typo (`porject`) under:
2. Architectural Characteristics: Know Your Capabilities
-> Characteristics are nondomain design considerations

```
Alex: Well, our business analysts have never worked on a software porject, so they probably won’t understand the impact of one decision versus another.
```

 Anonymous  May 16, 2025 
Printed Page 72
1st parapragh

Missing the 't' at the end of about

"We'll talk abou the other part, logical components..."

 Thomas  Jul 27, 2024 
Printed Page 72
1st parapragh

Missing the 't' at the end of about

"We'll talk abou the other part, logical components..."

 Thomas  Jul 27, 2024