Goals
- Provide traceability and activity history across the authoring process
Background and strategic fit
To understand the status of a particular piece of work, and how it got to that state
Assumptions
- This links to the traceability requirements (below) on the Milestones page for the Content Request Service (CRS) development.
Traceability
Requirement | Notes |
---|---|
Each content request task, generated through CRS, will be associated to one authoring task. | |
Each authoring task may be associated with many requests and have multiple SCT content changes | |
Reports should be able to show what has changed within an authoring task once it has been promoted | |
When a project is promoted, the information all the authoring tasks being promoted, along with the content changed on each task, should be available for reporting | |
At each status change of an authoring task, any associated CRS task should be updated appropriately | |
By having a track of content being worked on in authoring tasks, authors should be able to see if content they wish to edit/maintain is already being worked on by another author |
Traceability (copied from CRS)
Technical design
User interaction and design
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
---|---|