Traceability
Connect problems, objectives, requirements, features, tests, outputs, and evidence.
Research / App case study
ScopeWatch
A requirements-traceability workspace linking problems, objectives, features, tests, evidence, and change decisions, with server-side membership checks and deterministic scope-risk findings.
Requirements-traceability workspace prototype
- Next.js
- TypeScript
- Cloudflare D1
- R2
- Drizzle
- Supabase Auth
01 / Overview
What it’s built for.
Keep requirements, implementation evidence, tests, and change decisions connected so project scope can be reviewed explicitly.
Who it serves
Student project teams and advisers reviewing scope, progress, and evidence.
02 / Features
Inside the app.
Scope-risk review
Record progress and test runs and derive deterministic findings from saved project records.
Membership and decisions
Use invitations and active project membership; advisers hold the change-decision role.
03 / Workflow
From task to outcome.
Sign in with a verified Google account and access an authorized project.
Build trace links and attach evidence to project artifacts.
Record progress and test results and run the risk review.
Submit a proposed change for an adviser decision.
04 / Technical layers
How the pieces work.
Next.js · TypeScript · Vinext
Workspace routes and project APIs run through the Sites adapter.
Deterministic risk engine
Findings, metrics, and exports are derived from saved records rather than landing-page examples.
Cloudflare D1 · Drizzle · R2
D1 holds project and audit records; protected R2 objects hold evidence files.
Supabase Auth · Server membership checks
Verified Google identity is separate from project authorization; inaccessible projects return 404.
05 / Limitations
What to keep in mind.
- The public landing sample is separate from authenticated project metrics.
- Deployment access and Google-login rollout checks are documented separately from source-code functionality.
- The engine reports deterministic scope risks; it does not replace adviser decisions.
06 / Evidence
Follow the source.
These descriptions were reviewed against the linked source snapshot on October 12, 2026. Repository code and documentation may evolve after this review.