Architecture Example¶
Purpose¶
This section contains the completed ES-104 — Architecture example for the LMU Campus Operations and Incident Coordination Platform.
This is the architecture package for LMU-COICP-ARCH-001. It establishes the structural model for the same LMU business problems that later appear in Design, Implementation, Integration, Testing, Release, Operations, Deployment, Monitoring, Stewardship, and Governance.
The architecture does not simply say “incident workflow.” It introduces the concrete synthetic scenarios that drive the rest of the lifecycle: Information Commons leak intake, Damen Hall Facilities handoff, Mertz Hall Residence Life access, Cudahy Science HVAC closure, emergency-boundary rejection, and Mundelein Wi-Fi ownership coordination.
Architecture context¶
| Field | Value |
|---|---|
| Source planning package | ES-103 — Planning |
| Architecture baseline produced | LMU-COICP-ARCH-001 |
| Design baseline expected next | LMU-COICP-DES-001 |
| Implementation baseline expected later | LMU-COICP-IMPL-001 |
| Integrated baseline expected later | LMU-COICP-INT-001 |
| Release candidate expected later | LMU-COICP-RC-001 |
| Downstream release posture | Internal engineering review only |
| Planned downstream review environment | LMU-COICP Internal Engineering Review Environment |
| Planned downstream dataset | Spring Semester Synthetic Incident Dataset |
| Planned downstream synthetic records | 421 |
| Planned downstream reviewer accounts | 24 |
| Planned downstream review window | March 18–22, 2026 |
| AI Incident Summary | Deferred / disabled |
| Operational pilot | Not approved |
LMU scenarios that drive the architecture¶
| Scenario ID | Scenario | Primary Business Problem | Architecture Use | Downstream Flow |
|---|---|---|---|---|
| COICP-SYN-001 | Information Commons ceiling leak near public printer area | Campus Operations needs a simple intake record and Facilities visibility. | Demonstrates create workflow, current state, and creation evidence. | Design IF-001 / WF-001 → Implementation IW-003 → Testing TC-001 |
| COICP-SYN-118 | Damen Hall water leak affecting evening student event setup | Campus Operations must hand off to Facilities with evidence of ownership transfer. | Demonstrates Workflow Service, Evidence History Service, owner change, handoff evidence, and future review package. | Design IF-002 / WF-002 → Implementation IW-004 → Testing TC-005 / TC-007 |
| COICP-SYN-204 | Residence hall exterior door access issue at Mertz Hall | Residence Life needs scenario visibility without broad export or unrelated access. | Demonstrates role-scoped access and protected evidence visibility. | Design access matrix → Implementation IW-005 → Testing TC-004 / TC-011 |
| COICP-SYN-219 | HVAC outage affecting three evening classrooms in Cudahy Science | Facilities needs status progression and closure rationale after mitigation. | Demonstrates status transitions, closure evidence, and reviewability. | Design WF-004 → Implementation IW-004 / IW-007 → Testing TC-006 |
| COICP-SYN-322 | Emergency-related safety concern mistakenly entered as COICP item | Campus Safety must prevent COICP from becoming emergency response. | Demonstrates scope boundary, policy layer, blocked normal incident creation, and warning evidence. | Design WF-005 → Implementation IW-007 → Testing TC-012 |
| COICP-SYN-407 | Wi-Fi disruption affecting scheduled class check-in in Mundelein Center | IT ownership and Campus Operations coordination must be visible without exposing unrelated data. | Demonstrates owner assignment, access boundary, and optional handoff extension. | Design optional extension → Implementation future work → Testing future access/handoff cases |
Recommended workflow¶
Architecture Overview
↓
System Context
↓
Component Model
↓
Data and Evidence Flow
↓
Quality Attribute Strategy
↓
AI-Control Architecture
↓
Architecture Decision Records
↓
Architecture Review
↓
Architecture Readiness Summary
↓
ES-105 DesignRepository location¶
docs/examples/lmu-coicp/architecture/
In a project workspace, the comparable evidence would normally live under:
docs/project-workspace/architecture/
Example set¶
Architecture Overview
Introduce LMU-COICP-ARCH-001, the scenario set, architecture priorities, boundaries, and downstream lineage.
02System Context
Show which LMU actors, systems, datasets, and emergency boundaries are inside and outside the architecture.
03Component Model
Define components by showing how they handle concrete LMU scenarios.
04Data and Evidence Flow
Trace incident data and evidence events through named LMU examples.
05Quality Attribute Strategy
Connect auditability, access, usability, AI accountability, and reviewability to LMU scenario risks.
06AI-Control Architecture
Keep AI Incident Summary disabled while preserving future draft-review boundaries.
07Architecture Decision Records
Record scenario-driven architecture decisions that feed Design.
08Architecture Review
Review scenario coverage, open issues, and design carry-forward actions.
09Architecture Readiness Summary
Summarize readiness to begin ES-105 Design with concrete handoff items.
Architecture prepares Design and controlled implementation only. It does not approve operational pilot, production use, real campus incident use, AI Incident Summary, emergency response, or sensitive-record processing.