39 |
The system will indent a child requirement underneath its parent requirement. Similar to an ordered list. |
Solution |
Stated |
1 |
View |
Edit |
Delete
|
40 |
The system shall maintain a numbered list of requirements and user stories. If a requirement number is 3, then its children will start with 3.1,3.2 etc |
Stakeholder |
Stated |
2 |
View |
Edit |
Delete
|
41 |
The numbered list shall be for each section, one for requirements within a module and one for user stories within a module. |
Solution |
Stated |
3 |
View |
Edit |
Delete
|
46 |
The system shall display requirement/user story details in a pop up window with an 'X' to close in the upper right |
Solution |
Stated |
4 |
View |
Edit |
Delete
|
47 |
The system will use buttons for options that take an action (add, update, delete) |
Solution |
Stated |
5 |
View |
Edit |
Delete
|
48 |
When viewing the requirement/user story details window, there should be an 'update' button that will take you to a screen to perform the update |
Solution |
Stated |
6 |
View |
Edit |
Delete
|