Design Example¶
Purpose¶
This section contains the completed ES-105 — Design example for the LMU Campus Operations and Incident Coordination Platform.
This is not a generic design template. It is the design package for LMU-COICP-DES-001, the baseline that prepares a controlled first implementation increment for realistic LMU internal engineering review. The design uses concrete LMU synthetic scenarios, reviewer roles, evidence events, access boundaries, AI disablement, and emergency-boundary behavior so later stages can implement, integrate, test, release, operate, deploy, monitor, steward, and govern one coherent project.
Design context¶
| Field | Value |
|---|---|
| Source architecture package | ES-104 — Architecture |
| Design baseline produced | LMU-COICP-DES-001 |
| Implementation baseline expected next | 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 synthetic scenarios used throughout design¶
| Scenario ID | Scenario | Primary Reviewer Group | Design Use |
|---|---|---|---|
| COICP-SYN-001 | Information Commons ceiling leak near public printer area | Campus Operations / Facilities | normal create and Facilities handoff |
| COICP-SYN-118 | Damen Hall water leak affecting evening event setup | Campus Operations / Facilities | handoff, owner change, evidence timeline |
| COICP-SYN-204 | Mertz Hall exterior door access issue | Residence Life / Campus Operations | role-sensitive visibility and handoff |
| COICP-SYN-219 | HVAC outage affecting three evening classrooms in Cudahy Science | Facilities / Campus Operations | queue priority, status update, closure rationale |
| COICP-SYN-322 | Emergency-related safety concern mistakenly entered as COICP item | Campus Safety liaison | emergency-boundary block and redirection |
| COICP-SYN-407 | Wi-Fi disruption affecting scheduled class check-in in Mundelein Center | Campus Operations / IT | ownership, access, evidence, review package |
Recommended workflow¶
Design Overview
↓
Interface Design
↓
Data Design
↓
Workflow Design
↓
Access-Control Design
↓
AI Interaction Design
↓
Error and Exception Design
↓
Technical Decision Records
↓
Design Review
↓
Design Readiness Summary
↓
ES-106 Implementation ReadinessRepository location¶
docs/examples/lmu-coicp/design/
In a project workspace, the comparable evidence would normally live under:
docs/project-workspace/design/
Example set¶
Design Overview
Summarize LMU design objectives, scenarios, assumptions, risks, and downstream baseline lineage.
02Interface Design
Define implementation-facing contracts using COICP synthetic incident examples.
03Data Design
Define real-looking incident, evidence, reviewer-role, scope-warning, and deferred AI data structures.
04Workflow Design
Define LMU-specific workflows for creation, handoff, closure, emergency-boundary rejection, and deferred AI.
05Access-Control Design
Define reviewer groups, protected actions, role-sensitive visibility, denied behavior, and testing implications.
06AI Interaction Design
Document AI Incident Summary as deferred/disabled and specify future AI draft-review controls.
07Error and Exception Design
Define realistic LMU failure cases and safe responses.
08Technical Decision Records
Record project-specific design decisions that feed implementation and testing.
09Design Review
Record LMU review findings and carry-forward actions.
10Design Readiness Summary
Summarize readiness to begin implementation readiness.
ES-105 prepares controlled implementation only. Downstream release posture remains internal engineering review only, with AI Incident Summary disabled, Spring Semester Synthetic Incident Dataset only, approved reviewer accounts only, and no real campus incident use.