Authoring studio
Import a project from a spreadsheet, check it, and download the file to commit. Nothing here changes the published site until you push.
Sheets for the project itself — Project, Scope, Stakeholders, Timeline, Dependencies, Risks — and one per artefact type: Requirements, Acceptance Criteria, Business Rules, Actors, Process Steps, the five Spec sheets, Diagrams, Wireframes, API Endpoints, SQL Validations, Test Cases, Documents. Bring only the sheets you have; column headings are matched loosely.
Proposed from the name, and never one that is already taken. Edit it if you would rather choose.
Import a file and watch the checks run — nothing here changes the site.
The studio reads a spreadsheet in your browser and reports what it finds: counts, unresolved references, duplicate ids, coverage. That much works for anyone, and the file never leaves your machine.
Adding a project to the workspace, publishing it and deleting one write files into the source, so they only run where the source is — on the analyst's own machine, behind a password the server checks.
The same checks, run against what is on the site now.
Every reference resolves and no ids clash.
- TC-EP-070 linked requirement NFR-Maintainability does not exist
- TC-EP-070 not reachable from any requirement
- Wireframes nothing here yet
Every reference resolves and no ids clash.
Every reference resolves and no ids clash.
Every reference resolves and no ids clash.