View Source

h3. Functional requirements

{tip}
* Good requirements meet a specific need
* Good requirements are verifiable
* Good requirements are attainable
* Good requirements are clear
{tip}

*Template* (As from Gilb)

* Stakeholders: <stakeholders>
* Scale: <what we want to measure successful>
* Meter: <how to measure>
* Past <base to measure against, our own or competition >
* Goal <what we need to archive to be successful >

*Norsk eksempel*
* Interessent:
* Måleverktøy:
* Målemetode:
* Før:
* Mål:



h3. Requirement organization

* Level 1 - main functional areas (as seen from the system users)
** Level 2 - user tasks for each functional area
*** Level 3 - alternate flows
* Level 1 - administrative functional areas
** Level 2 - administrative tasks
*** Level 3 - alternate flows
* Level 1 - other

h3. Prioritization template

||Feature||Total Value||Relative Cost||Relative Risk||Priority||