Task: Review Requirements
var defaultQueryStr = '?proc={38A9C609-9A59-4D03-B835-AA84A716E626}&path={38A9C609-9A59-4D03-B835-AA84A716E626},{28B39D62-9D73-4254-9CB8-26CFA737D45E},_J3d_kEohEdqrjq4i3fchvA';
var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_e_O28N7KEdm8G6yT7-Wdqw", path: ["_e_O28N7KEdm8G6yT7-Wdqw", "_vCtak0JHEdq4z9xc-r201w", "_vChNQkJHEdq4z9xc-r201w", "_vChNREJHEdq4z9xc-r201w", "_cy8_AUsaEdqchp_cYmfkiA", "_kcnw8CJbEdqQipbmJ0SDbw", "_J3d_kEohEdqrjq4i3fchvA"]}, {view: "view:_e_O28N7KEdm8G6yT7-Wdqw", path: ["_e_O28N7KEdm8G6yT7-Wdqw", "_vCtak0JHEdq4z9xc-r201w", "_vCtajUJHEdq4z9xc-r201w", "_vCtai0JHEdq4z9xc-r201w", "_XIC1MUsbEdqchp_cYmfkiA", "_kcnw8CJbEdqQipbmJ0SDbw", "_J3d_kEohEdqrjq4i3fchvA"]}, {view: "view:_e_O28N7KEdm8G6yT7-Wdqw", path: ["_e_O28N7KEdm8G6yT7-Wdqw", "_vCtak0JHEdq4z9xc-r201w", "_vCtaj0JHEdq4z9xc-r201w", "_vCtakkJHEdq4z9xc-r201w", "_1OqDcUsbEdqchp_cYmfkiA", "_kcnw8CJbEdqQipbmJ0SDbw", "_J3d_kEohEdqrjq4i3fchvA"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_PEpmMCVuEdqSZ9OimJ-AzA", "_-kFhcCVuEdqSZ9OimJ-AzA", "_pV4NgSFsEdqrX8YVzvtlIg", "_-VJOICJbEdqQipbmJ0SDbw", "_kcnw8CJbEdqQipbmJ0SDbw", "_J3d_kEohEdqrjq4i3fchvA"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_PEpmMCVuEdqSZ9OimJ-AzA", "_SkuIwCVwEdqSZ9OimJ-AzA", "_gM9X0CGFEdqMcovRzkCQow", "_gShAwDHtEdqLw-lQEI8RPw", "_kcnw8CJbEdqQipbmJ0SDbw", "_J3d_kEohEdqrjq4i3fchvA"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_PEpmMCVuEdqSZ9OimJ-AzA", "_cn2akCVwEdqSZ9OimJ-AzA", "_zUDkgSGFEdqMcovRzkCQow", "_bE7sIDHuEdqLw-lQEI8RPw", "_kcnw8CJbEdqQipbmJ0SDbw", "_J3d_kEohEdqrjq4i3fchvA"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_e_O28N7KEdm8G6yT7-Wdqw", "_vCtak0JHEdq4z9xc-r201w", "_vChNQkJHEdq4z9xc-r201w", "_vChNREJHEdq4z9xc-r201w", "_cy8_AUsaEdqchp_cYmfkiA", "_kcnw8CJbEdqQipbmJ0SDbw", "_J3d_kEohEdqrjq4i3fchvA"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_e_O28N7KEdm8G6yT7-Wdqw", "_vCtak0JHEdq4z9xc-r201w", "_vCtajUJHEdq4z9xc-r201w", "_vCtai0JHEdq4z9xc-r201w", "_XIC1MUsbEdqchp_cYmfkiA", "_kcnw8CJbEdqQipbmJ0SDbw", "_J3d_kEohEdqrjq4i3fchvA"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_e_O28N7KEdm8G6yT7-Wdqw", "_vCtak0JHEdq4z9xc-r201w", "_vCtaj0JHEdq4z9xc-r201w", "_vCtakkJHEdq4z9xc-r201w", "_1OqDcUsbEdqchp_cYmfkiA", "_kcnw8CJbEdqQipbmJ0SDbw", "_J3d_kEohEdqrjq4i3fchvA"]}];
contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, true, true, false);
Task: Review Requirements
This task describes how to review the requirements work products.
Purpose
The purpose of this task is to formally verify that the results of the requirements tasks conform to the customer's
view of the system.
Relationships
RolesMain:
Technical Reviewer
Additional:
Assisting:
InputsMandatory:
Business Case
Iteration Plan
Software Requirement
Optional:
Actor
Change Request
Glossary
Software Requirements Specification
Stakeholder Requests
Storyboard
Supplementary Specifications
Use Case
Use-Case Model
Use-Case Package
Vision
External:
None
Outputs
Review Record
Steps
General Recommendations
Purpose
General recommendations for each review.
The following guidelines are helpful when reviewing the results of Requirements:
Always conduct reviews in a meeting format, although the meeting participants might prepare some reviews on their
own.
Continuously check what is produced to make sure the quality is as high as possible. Checklists are provided for
this purpose; refer to the checklist for each work product. You can use them for informal review meetings or in
daily work.
The reviews should concentrate on the requirements currently being developed.
The following roles will participate in the review meetings:
Requirements Reviewer: A person acting as a requirements
reviewer has some essential knowledge of the business or technology domain and detailed knowledge of the applied
facilitation and modeling techniques
Requirements Specifier
System Analyst
You should also consider the following roles for participation in review meetings, especially at key milestones:
Stakeholders - customers and users (Where possible)
Change Control Manager (Where reviewing Change Requests)
Test Designer (Optional)
Software Architect (Optional, usually early in the software
lifecycle when the software architecture is under development)
Project Manager (Optional, usually during the early parts of the
the lifecycle, or when major changes are being reviewed)
It is important to find the right balance between including the desired review participants and keeping the review
manageable and productive. Care should be taken to include only those participants who will contribute to achieving the
objectives of the review. It is usually more productive to hold several focused review sessions with a smaller number
of participants, than to hold one review involving many.
Recommended Review Meetings
Purpose
To define the scope and the goals of the review.
To define the approaches used for each specific scope/goal combination.
Normally, you should divide the review into the following meetings:
A review of change requests which impact the existing requirements set.
A review for each of the key requirements work products. If the system is large, break this review into
several meetings, possibly one per key functional area.
Even if you can review everything at the same meeting, you probably won't get approval of your conclusions the first
time. Be prepared to carry out new reviews for each new version of the requirements work products.
Prepare Review Record and Document Defects
Purpose
To document the review results.
To ensure that identified defects are documented.
Following each review meeting, the results of the meeting are documented in a Review Record. In addition, any defects are documented in accordance with the project's change management process.
Further Reading
See: [BIT03] Chapter11.
Properties
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable
More Information
Checklists
Glossary
Software Requirements Specification
Stakeholder Requests
Supplementary Specifications
Use-Case Model
Vision
Guidelines
Review Existing Requirements
Tool Mentors
Creating an Actor Report Using Rational SoDA
Creating a Use-Case Model Survey Using Rational SoDA
Creating a Use-Case Report Using Rational SoDA
Publishing Web-based Rational Rose Models Using Web Publisher
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
contentPage.onload();
contentPage.processPage.fixDescriptorLinks();
Wyszukiwarka
Podobne podstrony:
review requirements tmS4695E9review requirements]F661FEreview existing requirements?763922BASIC MILITARY REQUIREMENTS 2REVIEWANSWERSJRC NRD 525 technical reviewDoD Joint Services Weapon Safety Review Processmanage changing requirements?6AC18Dproduct reviewsReview05requirementsNE062EErup review record?AA30B5więcej podobnych podstron