Course 2100 CaliberRM and CMMI Requirements Management - PowerPoint PPT Presentation

evonne
course 2100 caliberrm and cmmi requirements management l.
Skip this Video
Loading SlideShow in 5 Seconds..
Course 2100 CaliberRM and CMMI Requirements Management PowerPoint Presentation
Download Presentation
Course 2100 CaliberRM and CMMI Requirements Management

play fullscreen
1 / 29
Download Presentation
Course 2100 CaliberRM and CMMI Requirements Management
395 Views
Download Presentation

Course 2100 CaliberRM and CMMI Requirements Management

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Course 2100CaliberRM and CMMI Requirements Management Jerry D. Odenwelder Jr. Principal Software Engineer

  2. Agenda • Brief Overview of CMMI • CaliberRM Support for Requirements Management Process Area • Questions

  3. CMMI Summary • Capability Maturity Model Integration • Product of the Software Engineering Institute at Carnegie Mellon • It is not a software development process • It is a tool to assess the effectiveness of a process

  4. Software CMM V1.1 Software CMM V2.0c SE-CMM EIA/IS 731 SECM CMMI V1.1x CMMI V1.0x SECAM SA-CMM v1.01 IPD-CMM v0.98 Timeline not to scale Time 1993 2002 CMMI History

  5. CMMI Structure

  6. Staged http://www.borland.com/resources/cmmi/staged/static/CMMI%20Staged%20MainPage.html

  7. Continuous • Categories • Process Management • Project Management • Engineering • Support • One profile per category

  8. CMMI Results 75% cost reduction In an SEI report (SEI 92-TR-24), data were averaged over 1233 separate projects in 261 organizations spanning 10 countries, to gauge the benefits of reaching higher maturity levels. (data normalized to a 200K line-of-code project).

  9. Requirements Management PA • Purpose • To manage the requirements of the project's products and product components and to identify inconsistencies between those requirements and the project's plans and work products.[1] • Assessed in • Level 2 when using the Staged Representation • The Engineering Category for Continuous Representation [1] Capability Maturity Model Integration (CMMISM) Version 1.1, pp. 82 (staged representation)

  10. Relationship to Other PA

  11. Goal • Requirements are managed and inconsistencies with project plans and work products are identified [1] • What Does that mean • Maintain a collection of approved requirements and track changes to these requirements • Maintain relationships between requirements, the project plans and other artifacts • Identify inconsistencies between the requirements, the project plan and other artifacts • Take corrective action, when necessary. [1] Capability Maturity Model Integration (CMMISM) Version 1.1, pp. 83 (staged representation)

  12. Specific Practices • Obtain an understanding of requirements • Obtain a commitment to requirements • Manage requirements changes • Maintain bidirectional traceability • Identify inconsistencies between project work and requirements.

  13. CaliberRM Framework • Ensure all users have access to the same data • Works in your environment • Generate the paperwork • Document Factory • Reporting

  14. Requirements Understanding • Rich Text Descriptions • Typed Requirements • User Defined Attributes (UDAs) • Default Values • Control the Requirement Version • Glossaries • Collaboration • Discussions • E-mail Notifications

  15. Requirements Review and Commitment • Document Factory • Requirement Grid • Filter and Sort • Datamart

  16. Manage Change • History • What was changed • Who made the change • E-mail notifications • Creation • Modification • Delete • Posting a discussion • Changes to a baseline

  17. Maintain Bi-directional Traceability Valuable Traces • Dependent Requirements • Project Task • Model Components • Validation Procedures • Tracing to code not always practical

  18. Traceability Support in CaliberRM • Support for tracing to • Other Requirements (in any project) • Together Artifacts • Starteam Artifacts • Mercury Test Director and Quality Center • SCM Tools that comply with Microsoft SCC Specification • Document References

  19. Identify Inconsistencies • Traces Surfaced in • Trace Matrix • Trace Graph • Reports and Generated Documents • Suspect Trace Identification

  20. Baselines • Isolate requirements for a release or iteration • Emphasize changes to a release • Support for locking and Digital Signatures

  21. Conclusion • CMMI is about improving existing process, it’s not about process • The CaliberRM Framework provides the functionality to achieve success in the Requirements Management Process Area

  22. CMMI CaliberRM Obtain an understanding of requirements  Rich Text  Typed Requirements  Custom Attributes  Discussions  Glossaries Manage requirement changes  History  Notifications  Grid  Document Factory  Discussions Maintain bi-directional traceability  Traces  Custom Attributes  Document Links Identify Inconsistencies  Traces  Suspect Trace Identification Conclusion

  23. Questions

  24. Resources • CMMI Online • http://www.borland.com/us/services/cmmi.html • Software Engineering Institute • http://www.sei.cmu.edu • Books • “Interpreting the CMMI: A Process Improvement Approach” by Margaret K. Kulpa, Kent A. Johnson • “CMMI Distilled A Practical Introduction to Integrated Process Improvement Second Edition” by Dennis M. Ahern, Aaron Clouse, and Richard Turner