Project Planning

-------------------------------------------------

Requisitos do Projeto

Apresentação |

Project Title:_____________________________________________________________ | Date Prepared:______________________ |

Version:___________________________________________ | |

Matriz de Requisitos |

Stakeholder | Requirement | Category | Priority | Acceptance Criteria |

| ID | Description | | | |

Identify the name or organization of the stakeholder | Requirement Identification | Describe the requirement. | Assign a category | Prioritize in total or by category | Define the criteria for acceptance |

| | | | | |

| | | | | |

| | | | | |

| | | | | |

| | | | | |

| | | | | |

Características de um BOM Requisito |

Característica | Explicação |

Unitary (Cohesive) | The requirement addresses one and only one thing. |

Complete | The requirement is fully stated in one place with no missing information. |

Consistent | The requirement does not contradict any other requirement and is fully consistent with all authoritative external documentation. |

Non-Conjugated (Atomic) | The requirement is atomic, i.e., it does not contain conjunctions. E.g., "The postal code field must validate American and Canadian postal codes" should be written as two separate requirements: (1) "The postal code field must validate American postal codes" and (2) "The postal code field must validate Canadian postal codes". |

Traceable | The requirement meets all or part of a business need as stated by stakeholders and authoritatively documented. |

Current | The requirement has not been made obsolete by the passage of time. |

Feasible | The requirement can be implemented within the constraints of the project. |

Unambiguous | The requirement is concisely stated without recourse to technical jargon, acronyms (unless defined elsewhere in the Requirements document), or other esoteric verbiage. It expresses objective...