Chapter 43 — Industry or public-service practice
Lesson map
Lesson 43 published. Map, example, EX127.
flowchart TD
N0["Learning outcomes"]
N1["43.1 Joining the team"]
N2["43.2 Pressure and pragmatism"]
N3["43.3 Study versus practice"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX127"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["43.1 Joining the team"]
N2["43.2 Pressure and pragmatism"]
N3["43.3 Study versus practice"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX127"]
[Learning outcomes]
|
v
[43.1 Joining the team]
|
v
[43.2 Pressure and pragmatism]
|
v
[43.3 Study versus practice]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX127]
Learning outcomes
You will (1) work within a professional architecture team; (2) apply course methods under real time and budget pressure; (3) reflect on differences between study and practice.
43.1 Joining the team
In year five Sofia spends a semester as a junior member of Corvia's architecture team. Her tasks are real but supervised: reviewing designs submitted by project teams, maintaining the architecture model, joining threat-modelling sessions and drafting decision records. She quickly finds that projects rarely arrive with complete context statements or requirements. Much of her work is asking the questions from chapters 20 and 21 of busy project managers, politely and persistently, because the review cannot proceed without answers. Professional architecture is as much about facilitation as about technical knowledge.
43.2 Pressure and pragmatism
A project to add a new partner for bike-share integration must launch in three weeks. A full design process is impossible. Sofia and her supervisor agree a proportionate review: confirm the integration uses the partner gateway with scoped tokens, check the data shared against the classification, run a one-hour threat-modelling session and record two residual risks for the business owner to accept. They document what was not reviewed. Sofia learns that proportionate review, with honest records of its limits, protects the organisation better than either blocking every project or approving without looking.
43.3 Study versus practice
Sofia keeps a reflective journal. In study, problems were well defined and information complete; in practice, information is partial and changes weekly. In study, she owned her designs; in practice, she influences designs owned by others. Methods still apply, but in lighter forms: a quick data-flow sketch rather than a full model, a ranked risk list rather than a quantitative analysis. Her supervisor's feedback notes that her strength is clear writing and her development area is negotiation. The journal becomes part of her final portfolio.
Worked example
Sofia reviews project designs, runs a proportionate three-week review for a bike-share integration with two accepted residual risks and records reflections comparing study and practice.
Synthetic case. The team, projects and feedback are synthetic.
Errors and limits
Proportionate reviews can miss issues; their limits must be recorded. Placement experience in one organisation may not generalise.
Exercises
- EX127 — Facilitation finding. What did Sofia find much of her review work consisted of? Rubric: 3 = asking context and requirement questions of busy project managers;; 2 = questions;; 1 = coding;; 0 = none.
- EX128 — Proportionate review. What did the bike-share review include? Rubric: 3 = gateway and scoped tokens check, data classification check, one-hour threat model, two accepted residual risks;; 2 = three;; 1 = vague;; 0 = none.
- EX129 — Development area. What development area did her supervisor note? Rubric: 3 = negotiation, alongside her strength in clear writing;; 2 = negotiation only;; 1 = writing;; 0 = none.
Synthesis
Professional practice applies course methods proportionately, records limits and relies on facilitation as much as technique.
Continue studying — chapter 43 of 50
← Chapter 42 (draft) · Course chapter index · Chapter 44 (draft) →