Following Requirements Elicitation is Verification (Ch. 4 of HoRaBA). Below are the factors that must be evaluated and enforced:
[ ] #420
[ ] #421
[ ] #422
[ ] #423
[ ] #424
[ ] #425
[ ] #427
[ ] #426
[ ] #429
[ ] #428
[ ] #431
[ ] #430
[ ] #432
[ ] #433
[ ] INVEST Criteria for User Stories
In order to do so, a workflow concept needs to be introduced
[ ] #434
Which means a Requirement must track not only who last modified a requirement, but who created it
[x] #442
Since requirements can no longer be deleted, Full Database Temporal Tables are required instead of the Audit table currently in place (#204):
[ ] #435
[ ] #436
The Workbox concept goes away. Each respective Requirement table will gain a Status column and trigger the approval workflow as appropriate.
[ ] #437
If a particular requirement requires user interaction (a result of the verification process), then the card panels need a red badge to guide the user to the appropriate place.
[ ] #439
[ ] #438
Free-Form requirements should still be possible from the Solution landing page, along with specific Requirement types to avoid having to navigate to multiple places. The notable changes here is that this is accomplished via a Drop Button which impressionistically looks like:
Where clicking a Requirement type will open a dialog for form entry to create the Proposed item.
[ ] #441
Clicking the Free-Form option will open a dialog wizard with the textarea for entry.
The second step of the wizard will display the list the parsed Requirement types for approval by the user. Approval makes these parsed items new Proposed requirements
Following Requirements Elicitation is Verification (Ch. 4 of HoRaBA). Below are the factors that must be evaluated and enforced:
In order to do so, a workflow concept needs to be introduced
Which means a Requirement must track not only who last modified a requirement, but who created it
Since requirements can no longer be deleted, Full Database Temporal Tables are required instead of the Audit table currently in place (#204):
The Workbox concept goes away. Each respective Requirement table will gain a
Statuscolumn and trigger the approval workflow as appropriate.If a particular requirement requires user interaction (a result of the verification process), then the card panels need a red badge to guide the user to the appropriate place.
Free-Form requirements should still be possible from the Solution landing page, along with specific Requirement types to avoid having to navigate to multiple places. The notable changes here is that this is accomplished via a Drop Button which impressionistically looks like:
Where clicking a Requirement type will open a dialog for form entry to create the Proposed item.
Clicking the Free-Form option will open a dialog wizard with the textarea for entry. The second step of the wizard will display the list the parsed Requirement types for approval by the user. Approval makes these parsed items new
Proposedrequirements