Governed architecture portfolio¶
Use one private copy. Submit no personal/student information to the public repository. Use the section identifiers below to connect your portfolio to the phase instructions.
| Section | Required content |
|---|---|
| Phase_1_Requirements | Stakeholder statement, entities, relationships, attributes, confidence, follow-up question |
| Phase_2_LDM | Editable ERD, keys, attributes, cardinality, junctions; annotate logical relationships, delete/update behavior, proposed enforcement and verification in the existing rationale |
| Phase_3_OLTP_vs_OLAP | Grain, facts/dimensions, workload placement and tradeoff memo |
| Phase_4_Governance | Owner, handling classification (Public / Internal / Sensitive / Restricted), confidentiality impact (Low / Medium / High), regulatory applicability/uncertainty, retention, risk, permitted use, proposed control and evidence status |
| Phase_5_Evaluation | Claim, observed evidence, limitations, missing deployment validation |
| Phase_6_Evidence | Evidence appendix used by capstone Phase 5 (not the presentation phase) |
| Architecture defense | Presentation and responses to stakeholder questions (capstone Phase 6) |
| Individual reflection | Contribution, learning, uncertainty and next improvement (capstone Phase 7) |
| Governance operations | Observation, policy, accountable role, review decision, action, verification and next review trigger |
| AI governance | Dataset card, bias/mitigation analysis, transparency, accountability and deploy/reject decision |
These are fields in your existing phase entries, not additional reports. Stakeholder assertions, proposed controls and demonstrated behavior must remain distinguishable.
For each claim label it demonstrated, simulated, proposed, or untested. Demonstrated means implemented and tested in the named environment; untested means implemented or asserted without sufficient verification. Include environment, command or artifact, result and limitation. Attach the peer review and response. Do not use generic lab screenshots as proof of unimplemented capstone controls.
Claim and revision record¶
Copy these fields for each important claim. Use requirement identifiers of your own choosing so the same decision can be traced across phases.
| Requirement/source | Decision and alternative | Evidence label | Artifact/command and environment | Result and limitation | Next check / accountable role |
|---|---|---|---|---|---|
| Fill in | Fill in | Demonstrated / simulated / proposed / untested | Fill in | Fill in | Fill in |
For each revision record the phase, feedback or new evidence, change, rationale and affected artifacts. Keep team contributions and reviewer identities private.
Author: Isaac K. Nti. Citation and reuse terms.