Requirements Review Process

19,234 views
18,683 views

Published on

Published in: Economy & Finance, Business
0 Comments
9 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
19,234
On SlideShare
0
From Embeds
0
Number of Embeds
76
Actions
Shares
0
Downloads
1
Comments
0
Likes
9
Embeds 0
No embeds

No notes for slide
  • 11/10/09 16:19
  • 11/10/09 16:19
  • 11/10/09 16:19
  • 11/10/09 16:19
  • Set scope of review
  • Here is a set of levels that illustrate the maturity of a proces Hazel I would like to change this and animate it such that the negative levels come on last
  • Requirements clarification The requirement may be badly expressed or may have accidentally omitted information which has been collected during requirements elicitation. Missing information Some information is missing from the requirements document. It is the responsibility of the requirements engineers who are revising the document to discover this information from system stakeholders. Requirements conflict There is a significant conflict between requirements. The stakeholders involved must negotiate to resolve the conflict. Unrealistic requirement The requirement does not appear to be implementable with the technology available or given other constraints on the system. Stakeholders must be consulted to decide how to make the requirement more realistic.
  • Understandability Can readers of the document understand what the requirements mean? Redundancy Is information unnecessarily repeated in the requirements document? Completeness Does the checker know of any missing requirements or is there any information missing from individual requirement descriptions? Ambiguity Are the requirements expressed using terms which are clearly defined? Could readers from different backgrounds make different interpretations of the requirements? Consistency Do the descriptions of different requirements include contradictions? Are there contradictions between individual requirements and overall system requirements? Organisation Is the document structured in a sensible way? Are the descriptions of requirements organised so that related requirements are grouped? Conformance to standards Does the requirements document and individual requirements conform to defined standards? Are departures from the standards, justified? Traceability Are requirements unambiguously identified, include links to related requirements and to the reasons why these requirements have been included?
  • Requirements Review Process

    1. 1. Requirements Review Process Yaron Zelichover November 2009
    2. 2. <ul><li>Review process concept </li></ul><ul><ul><li>Concept </li></ul></ul><ul><ul><li>Reviewers </li></ul></ul><ul><ul><li>Process </li></ul></ul><ul><ul><li>Activities </li></ul></ul><ul><ul><li>Checks </li></ul></ul><ul><li>How to implement review process in DOORS </li></ul>Agenda
    3. 3. <ul><li>What is Requirement Review? </li></ul><ul><li>A group of people read and analyze the requirements, look for problems, meet and discuss the problems and agree on actions to address these problems </li></ul>Review process - concept
    4. 4. <ul><li>Purpose of Review process </li></ul><ul><li>Certifies that the requirements document is an acceptable description of the system to be implemented </li></ul><ul><ul><ul><li>“ Have we got the right requirements?” </li></ul></ul></ul><ul><li>Checks a requirements document for </li></ul><ul><ul><li>Correct content of requirements </li></ul></ul><ul><ul><li>Adopting restrictions and standards </li></ul></ul><ul><ul><li>Quality of requirements writing </li></ul></ul><ul><ul><ul><li>“ Have we got the requirements right?” </li></ul></ul></ul>Review process - concept
    5. 5. <ul><li>Who are the reviewers? </li></ul><ul><li>Reviews should involve a number of stakeholders from different backgrounds </li></ul><ul><ul><li>People from different backgrounds bring different skills and knowledge to the review </li></ul></ul><ul><ul><li>Stakeholders feel involved in the process and develop an understanding of the needs of other stakeholders </li></ul></ul><ul><li>Review team should always involve at least a domain expert and an end-user </li></ul>Review process - reviewers
    6. 6. Review process - reviewers Stakeholders driving the System Requirements Stakeholders in the Supply Chain Stakeholders within the Solution Team Stakeholders receiving the Solution Stakeholders driving the Business Requirements
    7. 7. Review process - reviewers <ul><li>Examples of Reviewers </li></ul><ul><li>Requirements Author </li></ul><ul><li>Team Leader </li></ul><ul><li>Tester </li></ul><ul><li>Project Manager (if required) </li></ul><ul><li>Group Leader (if required) </li></ul><ul><li>… </li></ul>
    8. 8. Define Review Process <ul><li>Define Review Process </li></ul><ul><li>Define Reviewers </li></ul><ul><li>Work teams </li></ul><ul><li>Gates/Checkpoints </li></ul><ul><li>Baselines/Versions of requirements document </li></ul><ul><li>Review Iterations </li></ul><ul><li>Comments handling </li></ul><ul><li>Approval procedure </li></ul>
    9. 9. Define Review Process Baseline working document Issue review plan Issue Document to reviewers Inform reviewers Receive and sort change requests Decide on each change request Implement decisions Issue new baseline
    10. 10. Review Activities <ul><li>Review Activities </li></ul><ul><li>Plan Review </li></ul><ul><li>Distribute Documents </li></ul><ul><li>Prepare for Review meeting </li></ul><ul><ul><li>Individual reviewers read the requirements to find conflicts, inconsistencies, deviations from standards and other problems </li></ul></ul>
    11. 11. Review Activities – cont. <ul><li>Review Activities (cont.) </li></ul><ul><li>Requirements Review Meeting </li></ul><ul><ul><li>Comments and problems are discussed </li></ul></ul><ul><ul><li>Set of actions to address the problems is agreed </li></ul></ul><ul><li>Follow up actions </li></ul><ul><li>Revise Document </li></ul>
    12. 12. Review Activities – cont. <ul><li>Review inputs and outputs </li></ul>
    13. 13. Review Checks 1 2 3 4 5 CMMI Maturity Level Initial Repeatable Defined Managed Optimized      Checklists Metrics Process
    14. 14. Review Checks <ul><li>Check for problems in the requirements </li></ul><ul><li>Requirements clarification </li></ul><ul><li>Missing information </li></ul><ul><li>Requirements conflict </li></ul><ul><li>Unrealistic requirement </li></ul>
    15. 15. Review Checks <ul><li>Review Checklist </li></ul><ul><li>Understandability </li></ul><ul><li>Redundancy </li></ul><ul><li>Completeness </li></ul><ul><li>Ambiguity </li></ul><ul><li>Consistency </li></ul><ul><li>Organization </li></ul><ul><li>Conformance to standards </li></ul><ul><li>Traceability </li></ul>
    16. 16. Requirements Testing <ul><li>Requirements Testing </li></ul><ul><li>Each requirement should be testable </li></ul><ul><li>Inventing requirements tests is an effective validation technique </li></ul><ul><li>Each functional requirement should have an associated test </li></ul>
    17. 17. Review Process – implement in DOORS <ul><li>Using DOORS to implement Review Process </li></ul><ul><li>Attributes and Views </li></ul><ul><ul><li>Review attributes: Status, checkpoint, etc… </li></ul></ul><ul><ul><li>Review views </li></ul></ul><ul><li>Link Analysis </li></ul><ul><ul><li>Monitor coverage and impact of requirements </li></ul></ul><ul><ul><li>Traceability reports </li></ul></ul>
    18. 18. Review Process – implement in DOORS <ul><li>Using DOORS to implement Review Process (cont.) </li></ul><ul><li>Discussions </li></ul><ul><ul><li>Comments handling </li></ul></ul><ul><ul><li>‘ Pre-Review’ activity </li></ul></ul><ul><li>Baselines </li></ul><ul><ul><li>Manage versions of requirements document </li></ul></ul><ul><ul><li>Electronic signatures </li></ul></ul>
    19. 19. Review Process – implement in DOORS <ul><li>Using DOORS to implement Review Process (cont.) </li></ul><ul><li>Change-Proposal mechanism </li></ul><ul><li>Customizations: </li></ul><ul><ul><li>Utility to send emails to reviewers </li></ul></ul><ul><ul><li>‘ Track Changes’ view </li></ul></ul>

    ×