AISE502/moodle/week_10.html

61 lines
6.4 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!-- ==========================================================================
AISE502 · Moodle course page · Week 10
Section title (Edit section → Section name): Week 10: The Fit II – Hybrids, Evolution Paths, and the Decision Procedure
Three blocks follow, matching the FHGR section template. Paste each block into the
corresponding 'Text and media area' (editor → source code view), or all three into one.
The slide set of lecture 10 is added by the lecturer as a file resource below block 2.
Generated by src/build_moodle.py from src/content/week_10.json – edit the JSON, not this file.
========================================================================== -->
<!-- BLOCK 1 · Learning objectives -->
<h4>🎯 Learning objectives</h4>
<ul>
<li>I can explain why hybrids are the normal case and what the unit of fit evaluation is.</li>
<li>I can explain why fit decays over time (Lehman's laws, assumption A5) and name the three migration strategies.</li>
<li>I can read the evolution-path diagram: MM is both sanctioned start state and consolidation target.</li>
<li>I know Maxim 5: buy options on tomorrow's profile via modules and ports, not speculative distribution.</li>
<li>I can name the eight steps of the decision procedure with the artefact and measurement of each.</li>
<li>I can distinguish a sensitivity point from a trade-off point and explain what a weight-variation flip means.</li>
<li>I know Maxim 6: without a response measure a decision is an opinion; with a fitness function, a testable hypothesis.</li>
<li>I can judge my A2 against the reference run ADR-007: options, vetoes, fitness functions, evolution path.</li>
<li>I can read a row rationale of the matrix: gate, veto, documented mitigation, primary recommendation, central trade-off.</li>
<li>I can defend the C10 verdict: a designed hybrid with the determinism boundary – agents propose, deterministic services decide and book.</li>
</ul>
<!-- BLOCK 2 · Theory -->
<h4>🧑‍🏫 Theory</h4>
<p><strong>Lecture 10: The Fit II – Hybrids, Evolution Paths, and the Decision Procedure</strong> · 3 lessons lecture + 1 lesson standup/coaching<br>
This lecture treats fit as a function of time (hybrids, evolution paths), then runs the eight-step decision procedure through ADR-007 and reads the ten matrix rows cell by cell.</p>
<ul>
<li>Eight of the ten primary recommendations of Section 33 are compositions; the unit of fit evaluation is the subsystem with its own architecture quantum, recorded in a C4 container diagram.</li>
<li>Fit is a function of time (Lehman's laws, assumption A5): every recommendation carries a migration strategy – MonolithFirst, Strangler Fig in both directions, sacrificial architecture; MM is start state and consolidation target.</li>
<li>Maxim 5: choose the pattern for the profile verifiable today and buy options on tomorrow's via module boundaries, ports and a strangler-ready seam – not via speculative distribution.</li>
<li>AI Lens: for a C10 system's AI layer, sacrificial architecture is the rational default – replaceable behind a port, eval harness as acceptance gate; the deterministic core is designed to last.</li>
<li>The matrix only pre-filters: eight steps – ASRs, scenarios with numbers, utility tree whose (H,H) leaves are the weights of R(a), matrix shortlist, ATAM-light, ADR, measurement contract, measure in operation.</li>
<li>Sensitivity point: one decision, large effect on one attribute; trade-off point: opposing effects on several attributes. A weight variation that flips the recommendation calls for stakeholder negotiation, not a formula.</li>
<li>Steps (vii)–(viii) are the genuinely new obligations. Maxim 6: a decision without a response measure is an opinion; with response measure and fitness function it is a testable hypothesis.</li>
<li>ADR-007 (reference run, class C10) narrates one matrix row: decision drivers are the utility-tree weights, considered options the matrix shortlist (auditable), the final section the measurement contract (falsifiable).</li>
<li>In the ten row rationales every cell is traceable to R(a) against C(p) – gate, veto, documented mitigation – plus primary recommendation and central trade-off; the recurring resolution: consistent core, asynchronous edges.</li>
<li>C10's verdict is a designed hybrid – hexagonal modular monolith core, pipelines, orchestrated agents, EDA spine secondary – governed by the determinism boundary: LLM agents propose, deterministic services decide and book.</li>
</ul>
<p>📎 <strong>Materials:</strong> Slide set of Lecture 10 <em>(added below by the lecturer)</em> · Script: Part IV – Sections 35 (Hybrids and Evolution Paths), 36 (The Decision Procedure) and 33 (Cell Rationales: The Ten Rows in Detail).</p>
<!-- BLOCK 3 · Self-study and assignments -->
<h4>🧑‍💻 Self-study and assignments</h4>
<p><strong>📖 Reading before the lecture:</strong> Part IV – Sections 35 (Hybrids and Evolution Paths), 36 (The Decision Procedure) and 33 (Cell Rationales: The Ten Rows in Detail).</p>
<p><strong>Also before the lecture:</strong></p>
<ul>
<li>Have your A2 dossier (ADR, C4 container diagram, measurement contract) at hand – the lecture holds it against the reference run ADR-007.</li>
<li>Make sure the walking skeleton runs end-to-end (M3 check, week 9) before M4 starts this week.</li>
</ul>
<p><strong>🧩 Exercise session:</strong> The exercise slot is one lesson of standup/coaching for milestone M4: implementing the deterministic Performance, Risk and Optimization services with exact tests against the reference vectors.</p>
<p><strong>🛠️ Project work this week</strong> · Milestone M4 – Deterministic Core and Resilience (weeks 10–11)</p>
<ul>
<li>Implement the Performance, Risk and Optimization services and test them fully against the reference vectors – exact tests, not approximate ones.</li>
<li>Pin the deterministic services with tests before you trust any agent output.</li>
<li>Keep the deterministic core free of LLM calls – this is the line that is graded (ADR-007's determinism boundary: agents propose, deterministic services decide and book).</li>
<li>Commit after the milestone and record architectural decisions as ADRs as you go – a revised decision is a new, superseding ADR.</li>
<li>Plan the second half of M4: resilience patterns on all external calls and verified graceful degradation follow next week (M4 check end of week 11).</li>
</ul>
<p><em>No deliverable is due this week.</em></p>