| Prev | Next |
Review Requirements
Requirements are typically discovered and written by a variety of team members, and are commonly sourced from a variety of documents and stakeholders at disparate times. All of these factors lead to a tendency for the Requirements to lack quality, be inconsistent and to contain issues. Best practice encourages early and continuous reviews of Requirements to detect and remove defects before the Requirements reach the design and implementation teams. Enterprise Architect provides sophisticated tools for reviewing Requirements including the Model Library tool, Discussions, and Maintenance items.
Requirement Review Tools
Review Tool |
Description |
|---|---|
|
Model Library |
The Model Library is a useful tool that allows team members to collaborate and review the contents of the repository. It is particularly useful with requirements validation as it allows a set of requirements to be discussed and reviewed. Each review could be set up as a category and then different types of review could be set up as topics, with posts being used to enter review items. Model elements can be added to a post, allowing - for example - a post to report two or more conflicting requirements. Team members would have the chance to post replies and view the linked elements. Statuses can be applied to indicate the progress through a workflow. The Model Library tool can be used in conjunction with the Discuss & Review window (where individual elements are managed) and the Discuss & Review - History window (which contains a composite list of all element discussions in the repository). 
|
|
Discussions |
During the progress of a Requirements Review there will inevitably be ambiguities, issues and defects detected. Before these are entered against the Requirement as maintenance items, it is common for analysts conducting the review to want to discuss these items with team members or stakeholders. The Discuss & Review window is a useful place to record this information, allowing other team members to post replies. This is a particularly convenient facility because in many requirement tools these discussions are typically written in the text of the element, making it difficult to produce customer-ready documentation until they are all removed. It is quite common for modelers to enter discussions even outside a formal review and these will assist the reviewers to resolve Requirement defects or issues. 
|
|
Element Maintenance Items |
As Requirements are developed Changes will inevitable occur, Issues will be raised, Events will happen, Defects will be found, Tasks will need to be assigned and Decisions will need to be made. Enterprise Architect has a useful set of facilities to manage these items through the Project Maintenance facility. There is a window tab for each of these maintenance items where details of the item such as its Name, Description, Author, Completion Date and more can be assigned. 
|
|
Requirement Checklist |
Enterprise Architect has a convenient Requirements Checklist element available from the 'Extended Requirements' page of the Requirements Toolbox. This is a convenient way of recording visually whether a Requirement is of high quality and is a useful mechanism for team reviews.
|
