Your SlideShare is downloading. ×
a process definition of CMMI Level 2 Requirements Management  Gestão da Qualidade | MIEIC-FEUP Friday, December 5th 2008 D...
Contents <ul><li>Environment analysis </li></ul><ul><li>Purpose </li></ul><ul><li>Prerequisites </li></ul><ul><li>Process ...
Environment Analysis <ul><li>In a perfect world: </li></ul><ul><ul><li>Speed, quality  and  developing the correct softwar...
Purpose <ul><li>Definition of a process plan to achieve optimization in the process area of requirements management. </li>...
Prerequisites <ul><li>The practices needed to be done are: </li></ul><ul><ul><li>Initiative to plan the Process </li></ul>...
SP 1.1 - Obtain an Understanding of Requirements <ul><li>Purpose: </li></ul><ul><ul><li>Develop an understanding with the ...
SP 1.1 - Obtain an Understanding of Requirements Context | Environment analysis | Purpose | Prerequisites |  Process defin...
SP 1.2 - Obtain Commitment to Requirements <ul><li>Purpose: </li></ul><ul><ul><li>Obtain commitment to the requirements fr...
SP 1.2 - Obtain Commitment to Requirements Context | Environment analysis | Purpose | Prerequisites |  Process definition ...
SP 1.3 - Manage Requirements Changes <ul><li>Purpose : </li></ul><ul><ul><li>Manage changes to the requirements as they ev...
SP 1.3 - Manage Requirements Changes Context | Environment analysis | Purpose | Prerequisites |  Process definition  | Con...
SP 1.4 - Maintain Bidirectional  Traceability of Requirements <ul><li>Purpose : </li></ul><ul><ul><li>Maintain bidirection...
SP 1.4 - Maintain Bidirectional  Traceability of Requirements Context | Environment analysis | Purpose | Prerequisites |  ...
SP 1.5 - Identify Inconsistencies between  Project Work and Requirements <ul><li>Purpose : </li></ul><ul><ul><li>Identify ...
Context | Environment analysis | Purpose | Prerequisites |  Process definition  | Conclusions SP 1.5 - Identify Inconsiste...
 
Conclusions <ul><li>If we don’t have a good control of requirements, it is not possible to: </li></ul><ul><ul><li>Develop ...
Cláudio Costa | Ezilda Almeida | João Costa Lima | Rafael Pires Thank you for your attention!! Gestão da Qualidade | MIEIC...
Upcoming SlideShare
Loading in...5
×

CMMI-Dev REQM

3,313

Published on

Requirements Management - a process definition of CMMI-Dev

Published in: Business, Technology
0 Comments
13 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,313
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
1
Comments
0
Likes
13
Embeds 0
No embeds

No notes for slide
  • Transcript of "CMMI-Dev REQM"

    1. 1. a process definition of CMMI Level 2 Requirements Management Gestão da Qualidade | MIEIC-FEUP Friday, December 5th 2008 December 5 th 2008
    2. 2. Contents <ul><li>Environment analysis </li></ul><ul><li>Purpose </li></ul><ul><li>Prerequisites </li></ul><ul><li>Process definition </li></ul><ul><li>Conclusion </li></ul>Contents
    3. 3. Environment Analysis <ul><li>In a perfect world: </li></ul><ul><ul><li>Speed, quality and developing the correct software on the first attempt </li></ul></ul><ul><li>In the real world: </li></ul><ul><ul><li>Many projects fail because of poor requirements management </li></ul></ul><ul><ul><li>40% of effort in software projects is spent on correcting errors </li></ul></ul><ul><ul><li>Lack of alignment between IT and the business causes: </li></ul></ul><ul><ul><ul><li>Business stakeholders, users and development teams not to be on the same wavelength regarding requirements </li></ul></ul></ul><ul><li>Good Requirements management results in the avoidance of: </li></ul><ul><ul><li>Extra development costs </li></ul></ul><ul><ul><li>Unnecessary efforts of rework </li></ul></ul><ul><ul><li>Project failure </li></ul></ul><ul><ul><li>Unpredictability </li></ul></ul><ul><ul><li>Unplanned projects delays </li></ul></ul>Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    4. 4. Purpose <ul><li>Definition of a process plan to achieve optimization in the process area of requirements management. </li></ul><ul><li>Provide good requirements management ensuring: </li></ul><ul><ul><li>All the organization’s stakeholders are “speaking the same language”. </li></ul></ul><ul><li>Company’s core business is web development where management of requirements provided by the stakeholders are essential. </li></ul><ul><li>Definition of the process is based on the company’s context </li></ul>Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    5. 5. Prerequisites <ul><li>The practices needed to be done are: </li></ul><ul><ul><li>Initiative to plan the Process </li></ul></ul><ul><ul><li>Provide Resources </li></ul></ul><ul><ul><li>Assign Responsibilities </li></ul></ul><ul><ul><li>Train people </li></ul></ul><ul><ul><li>Identify and Involve Relevant Stakeholders </li></ul></ul><ul><ul><li>Perform Specific Practices </li></ul></ul>Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    6. 6. SP 1.1 - Obtain an Understanding of Requirements <ul><li>Purpose: </li></ul><ul><ul><li>Develop an understanding with the requirements providers on the meaning of the requirements. </li></ul></ul><ul><li>Associated activities: </li></ul><ul><ul><li>Act 1.1 - Establish criteria for distinguishing appropriate requirements providers and identification of the requirements providers. </li></ul></ul><ul><ul><li>Act 1.2 - Establish objective criteria for the evaluation and acceptance of requirements. </li></ul></ul><ul><ul><li>Act 1.3 - Analyze requirements to ensure that the established criteria are met. </li></ul></ul><ul><ul><li>Act 1.4 - Reach an understanding of the requirements with the requirements provider so that the project participants can commit to them. </li></ul></ul><ul><li>Major Roles: </li></ul><ul><ul><li>System Analyst </li></ul></ul><ul><ul><li>Technical Advisor </li></ul></ul><ul><ul><li>Providers selected at Act 1.1 </li></ul></ul><ul><li>Associated roles: </li></ul><ul><ul><li>Relevant End-users </li></ul></ul><ul><ul><li>Relevant Stakeholders </li></ul></ul><ul><ul><li>Relevant Customers </li></ul></ul>Context | Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    7. 7. SP 1.1 - Obtain an Understanding of Requirements Context | Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    8. 8. SP 1.2 - Obtain Commitment to Requirements <ul><li>Purpose: </li></ul><ul><ul><li>Obtain commitment to the requirements from the project participants. </li></ul></ul><ul><li>Steps needed: </li></ul><ul><ul><li>Act 2.1 - Assess the impact of requirements on existing commitments. </li></ul></ul><ul><ul><li>Act 2.2 - Negotiate and record commitments. </li></ul></ul><ul><li>Major Roles: </li></ul><ul><ul><li>System Analyst </li></ul></ul><ul><ul><li>Project Manager </li></ul></ul><ul><li>Associated Roles : </li></ul><ul><ul><li>Technical Advisor </li></ul></ul><ul><ul><li>Relevant project participants </li></ul></ul>Context | Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    9. 9. SP 1.2 - Obtain Commitment to Requirements Context | Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    10. 10. SP 1.3 - Manage Requirements Changes <ul><li>Purpose : </li></ul><ul><ul><li>Manage changes to the requirements as they evolve during the project . </li></ul></ul><ul><li>Steps needed : </li></ul><ul><ul><li>Act 3.1 - Document all requirements and requirements changes that are given to or generated by the project and maintain the requirements change history with the rationale for the changes. </li></ul></ul><ul><ul><li>Act 3.2 - Evaluate the impact of requirement changes from the standpoint of relevant stakeholders. </li></ul></ul><ul><ul><li>Act 3.3 – Make the requirements and change data available to the project. </li></ul></ul><ul><li>Major Roles : </li></ul><ul><ul><li>System analyst </li></ul></ul><ul><ul><li>Project Manager </li></ul></ul><ul><li>Associated Roles : </li></ul><ul><ul><li>Client </li></ul></ul><ul><ul><li>Relevant project participants </li></ul></ul>Context | Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    11. 11. SP 1.3 - Manage Requirements Changes Context | Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    12. 12. SP 1.4 - Maintain Bidirectional Traceability of Requirements <ul><li>Purpose : </li></ul><ul><ul><li>Maintain bidirectional traceability among the requirements and work products . </li></ul></ul><ul><li>Steps needed : </li></ul><ul><ul><li>Act 4.1 - Maintain requirements traceability to ensure that the source of lower level (derived) requirements is documented. </li></ul></ul><ul><ul><li>Act 4.2 - Maintain requirements traceability from a requirement to its derived requirements and allocation to functions, interfaces, objects, people, processes, and work products. </li></ul></ul><ul><ul><li>Act 4.3 - Generate the requirements traceability matrix. </li></ul></ul><ul><li>Major Roles : </li></ul><ul><ul><li>System Analyst </li></ul></ul><ul><ul><li>Project Manager </li></ul></ul><ul><li>Associated Roles : </li></ul><ul><ul><li>Relevant project participants </li></ul></ul>Context | Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    13. 13. SP 1.4 - Maintain Bidirectional Traceability of Requirements Context | Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    14. 14. SP 1.5 - Identify Inconsistencies between Project Work and Requirements <ul><li>Purpose : </li></ul><ul><ul><li>Identify inconsistencies between the project plans and work products and the requirements . </li></ul></ul><ul><li>Steps needed : </li></ul><ul><ul><li>Act 5.1 - Review the project’s plans, activities, and work products for consistency with the requirements and the changes made to them. </li></ul></ul><ul><ul><li>Act 5.2 - Identify the source of the inconsistency and the rationale. </li></ul></ul><ul><ul><li>Act 5.3 - Identify changes that need to be made to the plans and work products resulting from changes to the requirements baseline. </li></ul></ul><ul><ul><li>Act 5.4 - Initiate corrective actions. </li></ul></ul><ul><li>Major Roles : </li></ul><ul><ul><li>System Analyst </li></ul></ul><ul><ul><li>Project Manager </li></ul></ul><ul><li>Associated Roles </li></ul><ul><ul><li>Test Lead/Manager </li></ul></ul><ul><ul><li>Technical Advisor </li></ul></ul><ul><ul><li>Relevant project participants </li></ul></ul>Context | Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    15. 15. Context | Environment analysis | Purpose | Prerequisites | Process definition | Conclusions SP 1.5 - Identify Inconsistencies between Project Work and Requirements
    16. 17. Conclusions <ul><li>If we don’t have a good control of requirements, it is not possible to: </li></ul><ul><ul><li>Develop quality systems </li></ul></ul><ul><ul><li>Meet deadlines </li></ul></ul><ul><ul><li>Meet budgets </li></ul></ul><ul><ul><li>Meet expectations of costumers </li></ul></ul><ul><li>It is necessary to define a process to manage requirements </li></ul><ul><li>The implementation of a process requires: </li></ul><ul><ul><li>Investment of resources </li></ul></ul><ul><ul><li>Preparation of the team </li></ul></ul><ul><ul><li>A change of culture </li></ul></ul><ul><li>The process must be: </li></ul><ul><ul><li>Institutionalized </li></ul></ul><ul><ul><li>Spread among all people concerned </li></ul></ul><ul><ul><li>A commitment of all people regarding the use of the process. </li></ul></ul>Context | Environment analysis | Purpose | Prerequisites | Process definition | Conclusions
    17. 18. Cláudio Costa | Ezilda Almeida | João Costa Lima | Rafael Pires Thank you for your attention!! Gestão da Qualidade | MIEIC-FEUP Friday, December 5th 2008 December 5 th 2008

    ×