A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Category | Area | User Story | Priority (1 = critical, 3 = nice to have) | Notes | Questions? | |||||||||||||||||
2 | C6 | Business | Collections | The UI for the system should support potentially long lists of collections (100s) | 3 | ||||||||||||||||||
3 | R3 | Business | Revision tracking | When viewing node revisions, the system should allow for a complete view of the node, it's changes, and a simple way to see the differences between nodes - good UX is important here | 3 | Drupal already *does* this, but the UX is pretty rough and it could use some help. It would also be good to integrate it with the "state history" capability. | |||||||||||||||||
4 | TM5 | Business | File system | The system has no requirement to track revisions to files. Deleted or renamed files (including images) will simply not function when viewing the site history or the site future. | 3 | ||||||||||||||||||
5 | TM6 | Business | Theme | The system has no requirement to track theme revisions. This could be future functionality or administrators could create a new sub-theme to use in conjunction with content staging. | 3 | ||||||||||||||||||
6 | W15 | Business | Workflow UI | A user shall be able to easily define previous next states in a simple way that allows them to easily define valid workflows for each role / content pair where workflow can be applied | 2 | ||||||||||||||||||
7 | C1 | Functional | Collections | A user shall be able to create custom collections and assign them human-readable names | 1 | ||||||||||||||||||
8 | C10 | Functional | Collections UI | The system shall provide a user interface for administering collections | 1 | ||||||||||||||||||
9 | C11 | Functional | Collections UI | Uses shall be able to see a list of valid collections listed by label, machine name and archive status | 1 | ||||||||||||||||||
10 | C12 | Functional | Collections UI | Users shall be able to add, edit, and delete collections from the administrative interface | 1 | ||||||||||||||||||
11 | C13 | Functional | Collections UI | Users shall be able to reorder ollections in lists using the administrative interface | 2 | ||||||||||||||||||
12 | C14 / W16 | Functional | User interface | The system shall provide a user interface for administering active / inactive site components (this could be part of another UI for managing states) | 1 | ||||||||||||||||||
13 | C15 / W17 | Functional | User Interface | 2 | |||||||||||||||||||
14 | C3 | Functional | Collections | A user shall be able to assign a colllection to a node by name when adding or editing that piece of content | 1 | ||||||||||||||||||
15 | C4 | Functional | Collections | A user shall be able to assign a colllection to a site component by name when adding or editing that piece of content | 2 | ||||||||||||||||||
16 | C5 | Functional | Collections | A user shall be able to change the collection assigned to any content where it is present | 1 | ||||||||||||||||||
17 | C7 | Functional | Collections | A user shall be able to specify which content types or site components the collection applies to | 2 | These should apply to vocabularies, menus, blocks, content types, and other core things. | |||||||||||||||||
18 | C8 | Functional | Collections | A user shall be able to specify when a collection is archived | 2 | ||||||||||||||||||
19 | R2 | Functional | Revision tracking | The system shall provide a user interface to allow for users to view the states and state history of each piece of content (both nodes and site components) on the site. This could be divided into several sections or integrate with existing UI's (e.g. when in the menu UI have the ability to view the states / state history for each menu and menu link) | 3 | ||||||||||||||||||
20 | R6 | Functional | State History | A user shall be able to see a list of all workflow / collection changes clearly labeled in order of the dates the changes were made | 2 | ||||||||||||||||||
21 | R7 | Functional | State History | A user shall be able to see the associated revisions with each historical item and links to those revisions | 2 | ||||||||||||||||||
22 | R8 | Functional | State History | A user shall be able to see the associated users with each historical item and links to those users | 2 | ||||||||||||||||||
23 | S1 | Functional | Scheduling | A user shall be able to configure a collection with beginning and ending effective dates | 2 | ||||||||||||||||||
24 | S4 | Functional | Scheduling | A user shall be able to schedule a workflow transition from within the add / edit screen of any node | 1 | ||||||||||||||||||
25 | S5 | Functional | Scheduling | A user shall be able to schedule a workflow transition from within the add / edit screen of any site component | 2 | ||||||||||||||||||
26 | S7 | Functional | Scheduling | A user shall be able to define a start date for a workflow state when scheduling that state | 1 | ||||||||||||||||||
27 | TM1 | Functional | Time machine | A user shall be able to browse a site based upon a specified date and state. All parts of the site should function normally relative to these two parameters. | 2 | ||||||||||||||||||
28 | TM10 | Functional | User interface | The time machine functionality for both states and dates should be available as a URL parameter with appropriate access controls (e.g. http://site.com/page?=YYYY-MM-DD,collection) | 2 | ||||||||||||||||||
29 | TM2 | Functional | Time machine | A user shall be able to browse a site based upon a specified date. The system will take into account all workflow states for each piece of content and publish the site as of that date. | 1 | ||||||||||||||||||
30 | TM3 | Functional | Time machine | A user shall be able to browse a site based on a specified collection. The syste will take into account the effective collections as of the date specified for each piece of content. | 2 | ||||||||||||||||||
31 | TM9 | Functional | Time Machine UI | The system shall provide a user interface for the "time machine" functionality allowing a user to specify a date and collection to browse / view the site | 1 | ||||||||||||||||||
32 | W1 | Functional | Workflow | A user shall be able to create custom workflow states and assign them human-readable names | 2 | ||||||||||||||||||
33 | W10 | Functional | Workflow UI | Users shall be able to add, edit, and delete workflow states from the administrative interface | 1 | ||||||||||||||||||
34 | W11 | Functional | Workflow UI | Users shall be able to reorder workflow states in lists using the administrative interface | 2 | ||||||||||||||||||
35 | W12 | Functional | Workflow UI | A user shall be able to define a workflow for any combination of a role and piece of conent on the system (nodes, blocks, etc) where workflow can be applied | 1 | ||||||||||||||||||
36 | W13 | Functional | Workflow UI | A user shall be able to define a default workflow state for any role / content pair where workflow can be applied | 1 | ||||||||||||||||||
37 | W14 | Functional | Workflow UI | A user shall be able to define valid current / next states for each role / content pair where workflow can be applied | 1 | ||||||||||||||||||
38 | W16 | Functional | Workflow UI | The system shall provide a user interface for administering workflow | 2 | ||||||||||||||||||
39 | W3 | Functional | Workflow | A user shall be able to define each workflow state as being a state where content is "published" in the system. | 1 | ||||||||||||||||||
40 | W4 | Functional | Workflow | A user shall be able to assign a workflow state to a node when adding or editing a node | 1 | ||||||||||||||||||
41 | W5 | Functional | Workflow | A user shall be able to assign a workflow state to a site component when adding or editing that component. | 2 | ||||||||||||||||||
42 | W6 | Functional | Workflow | A user shall be able to specify which content types or site components the workflow applies to | 2 | These should apply to vocabularies, menus, blocks, content types, and other core things. | |||||||||||||||||
43 | W7 | Functional | Workflow | A user shall be able to specify when a workflow state is published | 2 | ||||||||||||||||||
44 | W8 | Functional | Workflow UI | The system shall provide a user interface for administering workflow states | 1 | ||||||||||||||||||
45 | W9 | Functional | Workflow UI | Uses shall be able to see a list of valid workflow state listed by label, machine name and published status | 1 | ||||||||||||||||||
46 | C2 | Technical | Collections | The system shall automatically define a machine name for a collection that a user will be able to override | 1 | ||||||||||||||||||
47 | C9 | Technical | Collections | The system shall exculde archived collections from lists throughout the system | 2 | It might make sense to only exclude it from certain lists and keep it available in others. Archive may just mean that you can't add it to new content. | |||||||||||||||||
48 | R1 | Technical | Revision tracking | The system shall track all changes to a node and its associated fields as a revision and associated a date and time with each revision whenever a workflow state or collection changes. | 3 | ||||||||||||||||||
49 | R4 | Technical | Component tracking | The system should track revisions for other site components (e.g. taxonomy terms, menus, etc) and associate a date and time with that revision | 2 | ||||||||||||||||||
50 | R5 | Technical | Component tracking | A user shall be able to view each revision of a site component with changes highlighted | 3 | ||||||||||||||||||
51 | S2 | Technical | Scheduling | The system should be able to automatically assign the current time to the starting date of a collection or workflow state | 3 | ||||||||||||||||||
52 | S3 | Technical | Scheduling | The system shall maintain a record of all previously assigned collections and workflow states and their effective dates | 2 | ||||||||||||||||||
53 | S6 | Technical | Scheduling | The system shall limit the selection of scheduled workflow states to those that are valid for the user role and the content they're adding / editing | 1 | ||||||||||||||||||
54 | TM4 | Technical | Time machine | The system shall manage all site components, nodes, and other information for display relative to the specified date or collection The idea is to be able to view the site in a complete hypothetical way. | 1 | This requirement should be revised based final solution architecture | |||||||||||||||||
55 | TM7 | Technical | Theme | The system shall provide a hook should be provided to allow for a theme change to be logged at a specific date / time. This hook would allow for the time machine functionality to dynamically adapt the theme based on the hook. | 3 | ||||||||||||||||||
56 | TM8 | Technical | API | The system shall provide a hook for other modules to work with the time machine functionality. | 2 | ||||||||||||||||||
57 | W2 | Technical | Workflow | The system shall automatically define a machine name for a workflow state that a user will be able to override | 2 | ||||||||||||||||||
58 | |||||||||||||||||||||||
59 | |||||||||||||||||||||||
60 | |||||||||||||||||||||||
61 | |||||||||||||||||||||||
62 | |||||||||||||||||||||||
63 | |||||||||||||||||||||||
64 | |||||||||||||||||||||||
65 | |||||||||||||||||||||||
66 | |||||||||||||||||||||||
67 | |||||||||||||||||||||||
68 | |||||||||||||||||||||||
69 | |||||||||||||||||||||||
70 | |||||||||||||||||||||||
71 | |||||||||||||||||||||||
72 | |||||||||||||||||||||||
73 | |||||||||||||||||||||||
74 | |||||||||||||||||||||||
75 | |||||||||||||||||||||||
76 | |||||||||||||||||||||||
77 | |||||||||||||||||||||||
78 | |||||||||||||||||||||||
79 | |||||||||||||||||||||||
80 | |||||||||||||||||||||||
81 | |||||||||||||||||||||||
82 | |||||||||||||||||||||||
83 | |||||||||||||||||||||||
84 | |||||||||||||||||||||||
85 | |||||||||||||||||||||||
86 | |||||||||||||||||||||||
87 | |||||||||||||||||||||||
88 | |||||||||||||||||||||||
89 | |||||||||||||||||||||||
90 | |||||||||||||||||||||||
91 | |||||||||||||||||||||||
92 | |||||||||||||||||||||||
93 | |||||||||||||||||||||||
94 | |||||||||||||||||||||||
95 | |||||||||||||||||||||||
96 | |||||||||||||||||||||||
97 | |||||||||||||||||||||||
98 | |||||||||||||||||||||||
99 | |||||||||||||||||||||||
100 |