Download presentation
Presentation is loading. Please wait.
1
Requirements Management
Methodology, tools and CMMI
2
Presentation Objectives
What questions should be asked? When: Building a Requirement Management Methodology Choosing the tool supporting the methodology How these questions relate to CMMI? These objectives are as advertised in the course datasheet. Reviewing the course objectives helps the students put the depth of the material into context. My experience 21st April 2010 Eric Mariacher - Logitech 2
3
Eric Mariacher - Logitech
Intended Audience Anyone involved in managing, auditing or architecturing Requirement Management Processes This audience is as advertised in the course datasheet. This is a good place to query the audience regarding their background. 21st April 2010 Eric Mariacher - Logitech 3
4
Eric Mariacher - Logitech
Agenda Background Defining a methodology Choosing the right tool Using the tool right: my experience How right? Bundle it all: CMMI 21st April 2010 Eric Mariacher - Logitech
5
Eric Mariacher - Logitech
Product lifecycle Marketing: Doing the right thing Specify Test Management: Getting visibility Product QA: Checking thing is done right Process QA: Checking how right thing is done Develop Developers: Doing thing right 21st April 2010 Eric Mariacher - Logitech
6
Eric Mariacher - Logitech
Product lifecycle Process Management Checking how right thing is done Doing the right thing Requirement Management Test Management Checking thing is done right Configuration Management Doing thing right 21st April 2010 Eric Mariacher - Logitech
7
Eric Mariacher - Logitech
Agenda Background Defining a methodology Choosing the right tool Using the tool right: my experience How right? Bundle it all: CMMI 21st April 2010 Eric Mariacher - Logitech
8
Eric Mariacher - Logitech
Methodology Roles and Responsabilities Document Flow Iterative Manage change proactively 21st April 2010 Eric Mariacher - Logitech
9
Roles and Responabilities
Management, Project managers Marketing System architects / Technical leaders Developers Product QA Process QA 21st April 2010 Eric Mariacher - Logitech
10
Eric Mariacher - Logitech
Document Flow Marketing / Users Requirements Test Plan System/ Architecture Specification Test Execution Test Reports Functional Specification Bugs Test Management Files and Releases Configuration Management Requirement Management 21st April 2010 Eric Mariacher - Logitech
11
Accept all changes as they occur
Passive? - Un-trackable - Frustrations Accept all changes as they come time changes
12
Freeze requirements at Project start
Overkill? Passive? - Waterfall model -> too lengthy schedule - Un-trackable - Frustrations Freeze Accept all changes as they come time changes time changes
13
« stepped RM process » as a response to requirement change
Proactive Overkill? Passive? + Trackable + Iterative - Waterfall model -> too lengthy schedule - Un-trackable - Frustrations Re-negociate changes at defined milestones Freeze Accept all changes as they come time changes time changes time changes Agile
14
Eric Mariacher - Logitech
Agenda Background Defining a methodology Choosing the right tool Using the tool right: my experience How right? Bundle it all: CMMI 21st April 2010 Eric Mariacher - Logitech
15
Questions / checklist: Centralized & Attributes
Attributes / template What is the priority of this requirement? What is the complexity and/or risk associated to this requirement? I don’t find the info I need in this requirement? Unique ID What requirement are you talking about? Centralized repository Where do you find this document? Tool / Methodology Feature Priority Question
16
Questions / checklist: Process Flow
Tool / Methodology Feature Priority Question Discussion thread & Process flow I was not aware of this change I commented it, haven’t you read it? Process flow Have we finished to implement this requirement? Is this requirement agreed by everyone? Attributes / template, Roles and Responsibility & Process flow Who is the owner of this requirement?
17
Questions / checklist: Traceability
Tool / Methodology Feature Priority Question Traceability What is the minimum set of tests we must run to have 100% coverage? Have all requirements been tested? Have all Marketing requirements been translated into system specifications? What is the impact if we change this requirement? Why are we implementing this feature?
18
Questions / checklist: Miscelleanous
Customization How can I build this special report and this special view? Tool / Methodology Feature Priority Question Synchronization Working offline or on distributed servers Reuse / platform Can we reuse this requirement from a previous project? Attributes / template & History / baselines Project/Global Requirement Maturity/Stability trend? History / baselines On what exact set of requirements did we agree on? Printing Is there something I can print?
19
Questions / checklist: Easy to use
User adoption
20
Eric Mariacher - Logitech
Agenda Background Defining a methodology Choosing the right tool Using the tool right: my experience How right? Bundle it all: CMMI 21st April 2010 Eric Mariacher - Logitech
21
What the user really wanted…
21st April 2010 Eric Mariacher - Logitech
22
Questions / checklist: Centralized & Attributes
Attributes / template high What is the priority of this requirement? mid What is the complexity and/or risk associated to this requirement? I don’t find the info I need in this requirement? Unique ID What requirement are you talking about? Centralized repository Where do you find this document? Tool / Methodology Feature Priority Question Priorities given on these questions often reflect the type of environment project where methodology and tool are active Priority attribute of high importance -> start-up environment: things can be renegociated
23
Minimum set of Mandatory attributes
Priority Maturity / Volatility Proposed Agreed Dropped Traceability Other possible attributes: New Unique Difficult attribute Area involved: Mechanical, electrical, FW, SW, etc… Just use the very minimum number of attributes, otherwise if it is not absolutely necessary, their use will not be coherent. Define thoroughly the meaning of each attribute. 21st April 2010 Eric Mariacher - Logitech
24
Eric Mariacher - Logitech
Interactive Poll How do you grade the importance of the previously asked questions? 21st April 2010 Eric Mariacher - Logitech
25
Questions / checklist: Process Flow
Tool / Methodology Feature Priority Question Discussion thread & Process flow mid I was not aware of this change low I commented it, haven’t you read it? Process flow Have we finished to implement this requirement? Is this requirement agreed by everyone? Attributes / template, Roles and Responsibility & Process flow Who is the owner of this requirement? Have we finished to implement this requirement? Low -> PM is well aware of where his/her project is without relying on this. Project may not be too complex.
26
Project document flow Common Feature Library Mktg & Eng Generic
Owner: Mktg & Eng Generic System Spec Owner: System Architect In RMTool: Libraries In RMTool: Project documents In TestMgmtTool Traceability Matrix Owner: PQA Mktg Reqs Owner: Mktg System Spec Owner: System Architect Test Plan Owner: PQA 21st April 2010 Eric Mariacher - Logitech
27
Questions / checklist: Traceability
Tool / Methodology Feature Priority Question Traceability low What is the minimum set of tests we must run to have 100% coverage? high Have all requirements been tested? mid Have all Marketing requirements been translated into system specifications? What is the impact if we change this requirement? Why are we implementing this feature?
28
Eric Mariacher - Logitech
Traceability Trees Marketing requirements System Specifications Functional Specifications Test Plan test156 MktgReq12 sys3 func73 test89 func15 sys7 MktgReq53 test67 func26 2 kind of views: tree and table Tree: where dose item come from? Table: test coverage Why not adding source code? sys45 test22 func57 test124 21st April 2010 Eric Mariacher - Logitech
29
Traceability Matrix Tests Requirements Test1 Test2 Test3 Req1 Req2
What is the minimum set of tests we must run to have 100% coverage? Can get rid of T2 or T3
30
Questions / checklist: Miscelleanous
Customization mid How can I build this special report and this special view? Tool / Methodology Feature Priority Question Synchronization Working offline or on distributed servers Reuse / platform & Traceability high Can we reuse this requirement from a previous project? Attributes / template & History / baselines low Project/Global Requirement Maturity/Stability trend? History / baselines On what exact set of requirements did we agree on? Printing Is there something I can print? Not only reuse but also consistency accross product line. Trends / measures Low -> PM is well aware of where his/her project is without relying on this. Project may not be too complex.
31
Requirement Management: Project stepped maturity trend
How can I build this special report and this special view? Project/Global Requirement Maturity/Stability trend? -> not the overall project health, just RM targeted Short life cycle, very high market changes reactivity 21st April 2010 Eric Mariacher - Logitech
32
Am I sure this requirement is not going to change (Stability)?
Post mortem measure 21st April 2010 Eric Mariacher - Logitech
33
How long did it take to write a requirement (Maturity)?
Post mortem measure Comparison mktg vs system specs 21st April 2010 Eric Mariacher - Logitech
34
Questions / checklist: Easy to use
Document view vs Database view 21st April 2010 Eric Mariacher - Logitech
35
Ease of use. Document view vs Database view
high Yet another title yet another body sys5 mid Another req title another requirement body sys4 Requirement title requirement body sys3 Priority Requirements ID Yet another title sys5 Another req title sys4 Requirement title sys3 Requirements ID high Requirement title requirement body sys3 Priority Requirements ID
36
Eric Mariacher - Logitech
Agenda Background Defining a methodology Choosing the right tool Using the tool right: my experience How right? Bundle it all: CMMI 21st April 2010 Eric Mariacher - Logitech
37
Eric Mariacher - Logitech
All models are false… but some models are useful... George E. P. Box 21st April 2010 Eric Mariacher - Logitech
38
What does the CMMI address?
How well? CMMI How? Development Processes Our job Delivering the product How well against what you want to achieve not against whether « how » is correctly executed or not 21st April 2010 Eric Mariacher - Logitech
39
Eric Mariacher - Logitech
CMMI in 1 slide Improving processes for better products Process Management Process Areas Project Management Process Areas Support Process Areas Configuration Management Engineering Process Areas Requirement Development Requirement Management SG specific goal SP specific practice SubPractices // Typical Work Products 21st April 2010 Eric Mariacher - Logitech
40
Eric Mariacher - Logitech
RM vs RD Requirement Management addresses managing requirement once they have been developed Requirement Development produces and analyzes customer and product requirements In this presentation: focus is on RM 21st April 2010 Eric Mariacher - Logitech
41
CMMI: Requirements Management Process Area
SG 1 Manage Requirements SP 1.1 Obtain an Understanding of Requirements SP 1.2 Obtain Commitment to Requirements SP 1.3 Manage Requirements Changes SP 1.4 Maintain Bidirectional Traceability of Requirements SP 1.5 Identify Inconsistencies Between Project Work and Requirements GG1 to 5 Generic Practices Every specific practice are covered by following questions. 21st April 2010 Eric Mariacher - Logitech
42
Questions / checklist: Centralized & Attributes
SP 1.1Obtain an Understanding of Requirements What is the priority of this requirement? What is the complexity and/or risk associated to this requirement? I don’t find the info I need in this requirement? GP2.6 Manage Configurations What requirement are you talking about? Where do you find this document? CMMI practice or subpractice Question
43
Questions / checklist: Process Flow
CMMI practice or subpractice Question SP 1.3 Manage Requirements Changes I was not aware of this change SP 1.1Obtain an Understanding of Requirements I commented it, haven’t you read it? GP2.6 Manage Configurations Have we finished to implement this requirement? SP 1.2 Obtain Commitment to Requirements Is this requirement agreed by everyone? Who is the owner of this requirement?
44
Questions / checklist: Traceability
CMMI practice or subpractice Question SP 1.4 Maintain Bidirectional Traceability of Requirements What is the minimum set of tests we must run to have 100% coverage? Have all requirements been tested? Have all Marketing requirements been translated into system specifications? SP 1.5 Identify Inconsistencies… SP 1.3 Manage Requirements Changes What is the impact if we change this requirement? SP 1.4 Bidirectional Traceability SP 1.5 Identify Inconsistencies Between Work and Requirements Why are we implementing this feature?
45
Questions / checklist: Miscelleanous
How can I build this special report and this special view? CMMI practice or subpractice Question Working offline or on distributed servers Can we reuse this requirement from a previous project? GP2.8 Monitor and Control the Process Project/Global Requirement Maturity/Stability trend? SP 1.2 Obtain Commitment to Requirements On what exact set of requirements did we agree on? Is there something I can print? CMMI does not cover everything…
46
Question / Checklist: Summary
Centralized Attributes Process Flow Traceability SP 1.1Obtain an Understanding of Requirements X SP 1.2 Obtain Commitment to Requirements SP 1.3 Manage Requirements Changes SP 1.4 Bidirectional Traceability SP 1.5 Identify Inconsistencies Between Work and Requirements GP2.6 Manage Configurations Attributes help requirement understanding (context, priority, ownership) Process Flow is about « requirement management » Traceability used when requirements change
47
Going Further
48
Eric Mariacher - Logitech
Traceability Trees Marketing requirements System Specifications Functional Specifications Test Plan test156 MktgReq12 sys3 func73 test89 func15 sys7 MktgReq53 test67 2 kind of views: tree and table Tree: where dose item come from? Table: test coverage Why not adding source code? func26 sys45 test22 func57 21st April 2010 Eric Mariacher - Logitech test124
49
Level of integration with other tools (CM, TM)
This is where you tell the students about the material they have been provided for the course. Show them the materials in the Student Kit: Student Manual - the main book used in the class Student Handouts book - contains templates, examples, and white papers Managing Requirements Management by Dean Leffingwell and Don Widrig Miscellaneous materials - pen, pad, etc. Describe any additional materials that are not listed on this slide, but are received in the Student Packs (small additions may have been made after this slide was released). Also, describe any supplementary material you may be providing. Requirements Tests Bugs/Changes Source files Pairing the wireless keyboard with the new wireless receiver wrong UI message to the user sw_pairing.c time out too short fw_pairing.c with an already owned wireless receiver previous pairing not cleared Sending characters to the PC Typing machine failing at 50 characters/seconds fw_matrix_scanning.c fw_rf_sending.c latency when waking up 21st April 2010 Eric Mariacher - Logitech 49
Similar presentations
© 2025 SlidePlayer.com Inc.
All rights reserved.