FM / docs

/home/techb158/cosmic.abdallabala.com/docs/

/home/techb158/cosmic.abdallabala.com/docs

Name	Size	Mode	Actions
00-design-study.md	3678	0666	edit dl rm
01-uml-class-diagram.puml	11869	0666	edit dl rm
02-use-case-diagram.puml	3763	0666	edit dl rm
03-sequence-diagrams.puml	9732	0666	edit dl rm
04-database-entity-model.mmd	7051	0666	edit dl rm
05-database-schema.sql	13372	0666	edit dl rm
06-diagram-preview.html	5021	0666	edit dl rm
07-design-checklist.md	3256	0666	edit dl rm
08-step-2-storage-layer.md	5325	0666	edit dl rm
09-step-3-risk-crud-ui.md	3380	0666	edit dl rm
10-step-4-mitigation-workflow.md	3996	0666	edit dl rm
11-step-5-deployment-gate-workflow.md	2292	0666	edit dl rm
12-step-6-multi-pm-integration.md	3770	0666	edit dl rm
13-step-6-1-microsoft-planner-integration.md	2335	0666	edit dl rm
14-step-7-reporting-export.md	4158	0666	edit dl rm
15-step-7-1-oauth-live-connectors.md	4545	0666	edit dl rm
16-step-8-user-roles-access-control.md	3297	0666	edit dl rm
17-step-9-production-deployment-security.md	4228	0666	edit dl rm
18-step-10-final-academic-submission.md	3199	0666	edit dl rm
19-final-report-draft.md	6814	0666	edit dl rm
20-instructor-submission-checklist.md	3639	0666	edit dl rm
21-demo-script.md	3948	0666	edit dl rm
22-traceability-matrix.md	4847	0666	edit dl rm
23-testing-evidence.md	2961	0666	edit dl rm
24-evaluation-rubric-mapping.md	2910	0666	edit dl rm
25-final-deployment-runbook.md	3214	0666	edit dl rm
26-known-limitations-and-future-work.md	2632	0666	edit dl rm
27-final-qa-checklist.md	2893	0666	edit dl rm
28-demo-rehearsal-script.md	3618	0666	edit dl rm
29-submission-freeze-report.md	2769	0666	edit dl rm
30-final-known-issues.md	1876	0666	edit dl rm
dashboard-spec.md	3691	0666	edit dl rm

Edit: /home/techb158/cosmic.abdallabala.com/docs/07-design-checklist.md (3256B)

# COSMIC AI-Risk Dashboard, Instructor Design Checklist

## 1. Required diagrams

| Required item | File | Status |
|---|---|---|
| UML Class Diagram | `01-uml-class-diagram.puml` | Complete |
| Use Case Diagram | `02-use-case-diagram.puml` | Complete |
| Sequence Diagrams | `03-sequence-diagrams.puml` | Complete |
| Database Entity Model | `04-database-entity-model.mmd` | Complete |
| Database schema | `05-database-schema.sql` | Complete |

## 2. Source traceability

| Requirement | Source basis | Implementation mapping |
|---|---|---|
| Quantify AI risk | COSMIC-Risk measurement objective | RiskScore, RiskScoringService, project risk score |
| Organizational, technical, human dimensions | AI Governance Triangle | Risk.dimension and dimension scores |
| ISO-style indicators | ISO 15939 and VIM measurement intent | Indicator and MeasurementRecord entities |
| Software prototype and API | COSMIC-Risk objectives and timeline | API controllers and service classes |
| PM tool integration | Methodology mentions PM tool integration | ProjectManagementIntegration, ExternalWorkItemMapping, and ProjectManagementIntegrationService |
| Risk profiles by project typology | COSMIC-Risk project typology | Project.projectType field |

## 3. Feature-to-design rule

Each feature must be implemented only after it maps to the design model.

| Feature | Use case | Class | Entity | API |
|---|---|---|---|---|
| Create risk | Register AI risk | Risk, RiskService | risks | POST /api/projects/{id}/risks |
| Score risk | Score risk | RiskScore, RiskScoringService | risk_scores | POST /api/projects/{id}/calculate-risk |
| Add mitigation | Add mitigation action | MitigationAction | mitigation_actions | POST /api/risks/{id}/mitigations |
| Record indicator | Record indicator measurement | Indicator, MeasurementRecord | indicators, measurement_records | POST /api/projects/{id}/measurements |
| Track experiment | Track experiment | Experiment, ModelMetric | experiments, model_metrics | POST /api/projects/{id}/experiments |
| Evaluate gate | Evaluate deployment gate | DeploymentGate, GateCriterion | deployment_gates, gate_criteria | POST /api/projects/{id}/gate/evaluate |
| Sync PM work item | Sync Trello/Jira/Asana work item | ProjectManagementIntegration, ExternalWorkItemMapping, ProjectManagementSyncRun | project_management_integrations, external_work_item_mappings, project_management_sync_runs | POST /api/integrations/{integrationId}/sync |

## 4. Development sequence after instructor approval

1. Confirm diagrams and database model.
2. Update JSON storage to match the entity model.
3. Add service layer files.
4. Add API endpoints by use case.
5. Add tests for scoring and gate decisions.
6. Connect UI screens to stable endpoints.
7. Add multi-PM synchronization only after local risk flow works.

## 5. Open decisions before coding

| Decision | Recommended answer |
|---|---|
| MVP database | Keep JSON storage during prototype, migrate to SQLite or PostgreSQL after diagrams are approved |
| User authentication | Use role model now, add login later |
| Risk scoring formula | Keep normalized score and residual score as implementation extension |
| Multi-PM integration | Implement after risk CRUD and gate evaluation are stable |

# COSMIC AI-Risk Dashboard, Instructor Design Checklist ## 1. Required diagrams | Required item | File | Status | |---|---|---| | UML Class Diagram | `01-uml-class-diagram.puml` | Complete | | Use Case Diagram | `02-use-case-diagram.puml` | Complete | | Sequence Diagrams | `03-sequence-diagrams.puml` | Complete | | Database Entity Model | `04-database-entity-model.mmd` | Complete | | Database schema | `05-database-schema.sql` | Complete | ## 2. Source traceability | Requirement | Source basis | Implementation mapping | |---|---|---| | Quantify AI risk | COSMIC-Risk measurement objective | RiskScore, RiskScoringService, project risk score | | Organizational, technical, human dimensions | AI Governance Triangle | Risk.dimension and dimension scores | | ISO-style indicators | ISO 15939 and VIM measurement intent | Indicator and MeasurementRecord entities | | Software prototype and API | COSMIC-Risk objectives and timeline | API controllers and service classes | | PM tool integration | Methodology mentions PM tool integration | ProjectManagementIntegration, ExternalWorkItemMapping, and ProjectManagementIntegrationService | | Risk profiles by project typology | COSMIC-Risk project typology | Project.projectType field | ## 3. Feature-to-design rule Each feature must be implemented only after it maps to the design model. | Feature | Use case | Class | Entity | API | |---|---|---|---|---| | Create risk | Register AI risk | Risk, RiskService | risks | POST /api/projects/{id}/risks | | Score risk | Score risk | RiskScore, RiskScoringService | risk_scores | POST /api/projects/{id}/calculate-risk | | Add mitigation | Add mitigation action | MitigationAction | mitigation_actions | POST /api/risks/{id}/mitigations | | Record indicator | Record indicator measurement | Indicator, MeasurementRecord | indicators, measurement_records | POST /api/projects/{id}/measurements | | Track experiment | Track experiment | Experiment, ModelMetric | experiments, model_metrics | POST /api/projects/{id}/experiments | | Evaluate gate | Evaluate deployment gate | DeploymentGate, GateCriterion | deployment_gates, gate_criteria | POST /api/projects/{id}/gate/evaluate | | Sync PM work item | Sync Trello/Jira/Asana work item | ProjectManagementIntegration, ExternalWorkItemMapping, ProjectManagementSyncRun | project_management_integrations, external_work_item_mappings, project_management_sync_runs | POST /api/integrations/{integrationId}/sync | ## 4. Development sequence after instructor approval 1. Confirm diagrams and database model. 2. Update JSON storage to match the entity model. 3. Add service layer files. 4. Add API endpoints by use case. 5. Add tests for scoring and gate decisions. 6. Connect UI screens to stable endpoints. 7. Add multi-PM synchronization only after local risk flow works. ## 5. Open decisions before coding | Decision | Recommended answer | |---|---| | MVP database | Keep JSON storage during prototype, migrate to SQLite or PostgreSQL after diagrams are approved | | User authentication | Use role model now, add login later | | Risk scoring formula | Keep normalized score and residual score as implementation extension | | Multi-PM integration | Implement after risk CRUD and gate evaluation are stable |