Historical errata for Design It!

In the “Explore Ideas” section the second paragraph, first sentence is missing a “we”:

Exploring software architecture requires that [we] try out combinations of struc- tures to find a mix that best promotes our desired quality attributes.

First sentence of the first paragraph uses the word ‘new’ when it should be ‘knew’

As a result of this prototype our stakeholders work to describe a deeper layer of the problem that nobody new [-> knew] was important until now

First paragraph last sentence is missing the word ‘better’ and ‘able’?.

The better we empathize with their needs, the [better] we’ll be [able] to see and understand the real problems that need to be solved.

Top of the page, the fourth bullet point has confusing wording.

“Who are the [they] helping?”

“It may seem counterintuitive, but architecture is a mechanism for preserving ambiguity and enabling change.”
should read
“It may seem counterintuitive, but architecture is a mechanism for preventing ambiguity and enabling change.”

“creating a simple application that walks through parts of their application”

Hard to understand what a “simple application” is in this context. I interpreted this as a simple ‘scenario’ that walks through parts of their application.

“architecture tangible.[space]You
can make [the] most of them [by] on your own but”.

Add a space after full stop.
Add ‘the’ between ‘make most’.
Drop ‘by’ before ‘on your own’.

“Facilitates[e] informal, conversational discussions about the architecture”. Extra e after ‘Facilitates’.

The following sentence is misleading: “In Software Architecture in Practice [BCK12] Paul Clements, Len Bass, and Rick Kazman group structures into three basic categories: module, component and connector, and allocation.”

You state there’s three basic categories(which would line up with Static Dynamic and Physical), but you listed four. Nothing major! Just something difficult for a spell checker to catch :)

Btw, really dig the book so far! Really looking forward to seeing it evolve.

-Mark Poko(mpoko@trivenidigital.com)

secton 7. Software architecture enables agility.
….
Inserted word “A specific, well-design architecture is can bend without breaking.”
….

Needs space after period in this sentence
“We call these influential functional requirements.Influential functional … ”

In the section “Design is Re-Design” in the middle of the second paragraph
“”"
Other teams have problem seen a problem similar to the one you face currently
“”"

I think this is to read
“”"
Other teams have probably seen a problem similar to the one you face currently
“”"

the code.zip for windows is empty nothing in that

The link to the article that discusses the form of decision records is incorrect. The hostname is missing a dot in front of the com and should be “thinkrelevance.com”

pull together everything you’ve learned in this chapter by ceating an architec- ture design plan.

Only one person can talk on the phone at a ftime.

s/ftime/time/

Last sentence of first paragraph: “…whether a goal _has is satisfied.” → “…whether a goal is satisfied.”

In “Decide How Much to Design Up Front”, page number unknown because I’m reading on Safari:

“In this case, spending less than about 20 percent of the original project schedule on architecture has a diminishing return.”

Was probably meant to read:

“In this case, spending more than about 20 percent of the original project schedule on architecture has a diminishing return.”

That is, “more than about 20 percent”, not “less than about 20 percent”.

In “Decide How Much to Design Up Front”, page number unknown because I’m reading on Safari:

“systems” should be singular, not plural in “every software systems has a design sweet spot”

In “Find a Design That Satisfices”, page number unknown because I’m reading on Safari:

The word “to” appears to be missing between “need” and “do” in the phrase “we still need do some design work up front.”

In “Define the Quality Attributes”

The word “of” appears to be missing between “type” and “quality” in the sentence “The stimulus kicks off the scenario and will vary depending on the type quality attribute.”

In “Define the Quality Attributes”

The word “scenario” appears to be missing between “availability” and “might” in the sentence “For example, the stimulus for an availability might be a node becoming unreachable whereas the stimulus for a modifiability scenario might be a request for a change.”

In “Define the Quality Attributes”

The word “initiations” should be “initiates” in the sentence “The source is the person or system that initiations the stimulus.”

In “Define the Quality Attributes”, the wording of the Project Lionheart quality attribute scenario “A user’s searches for open RFPs and receives a list of RFPs 99% of the time on average over the course of the year” is awkward and may be grammatically incorrect. Suggested alternatives: “Users’ searches for open RFPs receive lists of RFPs 99% of the time on average over the course of the year.” or “A user’s searches for open RFPs receive lists of RFPs 99% of the time on average over the course of the year.”

Before the section Create a Design Plan, the last sentence says, “…everything you’ve learned in this chapter by ceating an architecture design plan.” Ceating to creating.