HeptaMS Architecture Owner
Leads to certification: HeptaMS Certified Professional – Architecture Owner
The course covers responsibility for technical sustainability.
- Scope
- 10 blocks of 4 h = 5 days 10 blocks of 4 hours
- Formats
- Live Online · In person
- Exam
- Multiple choice, 10–15 questions, 70 %, 3 attempts · optional practical submission
- Prerequisites
- Development or architecture experience. S8 Spec Driven Development strongly recommended; block 9 assumes it.
What it covers
The course covers responsibility for technical sustainability. Topics include decoupling across identity, data and presentation, the relationship between emergent design and intentional architecture, Conway's Law, DevOps and deployability, service management, the choice between cloud and self-operated infrastructure, monitoring and on-call duty. Two parts cover the safe operation of AI agents and the analysis of AI-induced incidents. Practical exercises carry out a blast radius audit, apply spec-driven development at architecture level and build a chain of decision database, requirements agent and coding agent.
Whether a system landscape consists of one large system or of interchangeable components determines years later whether a change remains possible. At the same time, AI agents introduce a class of damage for which the classic operations vocabulary has no terms.
What you can do afterwards
- Decouple a system landscape across the three integration layers and justify the decision.
- Balance emergent design and intentional architecture.
- Apply Conway's Law to a concrete team structure.
- Collect and interpret the four DORA metrics.
- Select from the service management practices those that produce measurable value, and set up a configuration database that stays current.
- Draw up a five-year cost comparison for cloud and self-operated infrastructure, and distinguish data location from data sovereignty.
- Define service level objectives and error budgets, and alert on symptoms rather than on infrastructure.
- Carry out a blast radius audit and limit an agent's scope of action.
- Analyse an AI-induced incident forensically.
- Document and defend an architecture decision.
Who this course is for
Development architects, technical team leads, senior developers with architectural responsibility. Anyone who answers for the technical sustainability of a system.
Anyone growing into the architecture role. System and enterprise architects who want to anchor their role at team level. DevOps and platform roles. Operations leads with architectural ambitions.
Learning objectives in detail
- 1 Decouple a system landscape across the three integration layers – identity, data, presentation – and explain why that is a strategic rather than a technical decision.
- 2 Deliberately balance emergent design and intentional architecture.
- 3 Apply Conway's Law to a concrete team structure.
- 4 Collect and interpret the four DORA metrics and apply Westrum's question to their own organisation.
- 5 Select from the 34 ITIL practices those that produce measurable value and set up a CMDB as a database rather than as documentation.
- 6 Draw up a five-year TCO comparison for cloud versus on-premise and distinguish data location from data sovereignty.
- 7 Define SLOs and error budgets and alert on symptoms rather than on infrastructure.
- 8 Carry out a blast radius audit and draw an agent's action boundary so that the maximum damage stays manageable.
- 9 Work through an AI-induced incident forensically – version snapshot, test battery, responsibility analysis – and apply the ACC principle operationally.
- 10 Build an HIH chain and maintain an architecture decision log that makes the agent more decision-informed with every iteration.
- 11 Defend an architecture decision to value owners and leadership when nothing is visibly broken.
Dates & demand pools
No date yet - express interest in a demand pool and we will set one when enough peers join.
No date that fits? Express non-binding interest in a demand pool - once enough peers join, we set a date and place and get in touch.
Name your preferred date and start a pool for this course. Once enough people join we schedule it and get in touch – you only book after that.
Is this course right for your situation?
If no date fits or you need the course in-house: drop us a line and we will come back with a proposal.