log in:


Story #24

"Describe and record requirement"

<p>The requirement is given a description, which is recorded in a series. The description uses the form: "The system shall..." followed by the action a supporting product must take. The requirement is associated with one (or sometimes several) responses. It may also be associated with outcomes, or events.</p> <p>The source (names of people) of the requirement is recorded. The rationale, or why this requirement is important to the process, is recorded.</p> <p>Fit criteria are written. Process value is established. Dependencies on and conflicts with other requirements are identified and recorded.</p> <p>Cost of obtaining solution is estimated.</p> <p>The requirement is submitted for acceptance.</p>


These interruptions may happen during (or after) this story.

Interruption Next Stories
Identify civil society story Describe and record civil society story. 
Time to accept requirement Accept requirement. 

These interruptions may cause this story.

Cause Interrupted stories
Time to begin requirements analysis work Do item in iteration plan.  Deliver contracted services.  Develop software club. 
Identify requirement Do item in iteration plan.  Create new requirements specification document.  Review iterative working.  Upgrade software application service.  Describe and record civil society story.  Create new requirements project. 


Products supporting this story satisfy the following requirements.

Requirement Ticket
The system shall support recording requirements (user stories) in the form of the Volere requirement shell (uid, type, story, description, rationale, source, fit criterion, satisfaction, dissatisfaction, dependencies, conflicts, supporting materials, history)  
The system shall allow domain objects to be bookmarked similarly to AboutUs.org


This story has been included within the following product specifications: