Compliance and Audit Block 17 Block 17.

Slides:



Advertisements
Similar presentations
Implementing CMMI® for Development Version 1.3
Advertisements

Copyright © 2003 by Cooliemon TM, LLC 1 Causal Analysis & Resolution (CAR) at Level 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead.
Team Software Process By: Bryan Peterson. Presentation Topics History Brief overview of the Team Software Process (TSP) TSP Team Launch Team-working Conclusion.
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
SE 470 Software Development Processes James Nowotarski 12 May 2003.
Capability Maturity Model Integration (CMMI). CMMI Enterprise-wide process improvement framework Focuses on processes for improved product Process areas:
CMMI Overview Quality Frameworks.
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Organizational Project Management Maturity: Roadmap to Success
Lecture 11 CMM CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
Project Management Methodology More about Quality Control.
Chapter : Software Process
Process: A Generic View
Integrated Capability Maturity Model (CMMI)
UNIT-II Chapter : Software Quality Assurance(SQA)
Software Quality Assurance Activities
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
OHT 23.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The benefits of use of standards The organizations involved in standards.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
SQA System Overview Chapter 4. Where we have been so far, Where we are going Where do software errors come from? What is quality? How can quality be measured?
Chapter 2 Process: A Generic View
By Ritesh Reddy Nagaram.  Organizations which are developing software processes are facing many problems regarding the need for change of already existing.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
University of Sunderland CIFM03Lecture 2 1 Quality Management of IT CIFM03 Lecture 2.
Quality Concepts within CMM and PMI G.C.Reddy
Models of Quality Assessment
Lecture Topics covered CMMI- - Continuous model -Staged model PROCESS PATTERNS- -Generic Process pattern elements.
SAM Executive Seminar Software Measurement.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
@2002 Copyright, Itreya Technologies CMMI kick off July 2005.
Software Engineering - I
CS Process Improvement CMM Hans Van Vliet, Software Engineering, Principles and Practice, 3 rd edition, John Wiley & Sons, Chapter 6. W. Humphrey,
CSE4002CMMI Capability Maturity Model Integration (CMMI) CMMI is replacing the well established CMM rating for software developers and systems engineers.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Pittsburgh, PA CMMI Acquisition Module - Page M4-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This.
Requirements Development in CMMI
Copyright © 2003 by Cooliemon TM, LLC 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead Assessor (CMM ® ) SCAMPI Lead Appraiser SM (CMMI.
Evidence about the Benefits of CMMI ® What We Already Know and What We Need to Know Joe Jarzombek, PMP Deputy Director for Software Assurance Information.
SOFTWARE PROCESS IMPROVEMENT
Pittsburgh, PA CMMI Acquisition Module - Page M5-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This.
Software Engineering (CSI 321) Software Process: A Generic View 1.
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
Certification: CMMI Emerson Murphy-Hill. Capability Maturity Model Integration (CMMI) Creation of the Software Engineering Institute (SEI) at Carnegie.
1 Integration of Process Initiatives And Assessments Common Process Framework Integration of Management System Standards and Initiatives (QMS/CMMI/Lean/PMBP)
SQA project process standards IEEE software engineering standards
Configuration Management
Sample Fit-Gap Kick-off
Thoughts on IT Enterprise Architecture Maturity Models for the
Emerging Technologies
School of Business Administration
Business Process-driven DAF products
CS4311 Spring 2011 Process Improvement Dr
SQA project process standards IEEE software engineering standards
CMMI Overview Quality Frameworks.
Process Maturity Profile
Software Engineering (CSI 321)
د. حنان الداقيز خريف /28/2016 Software Quality Assurance ضمان جودة البرمجيات ITSE421 5 – The components of the SQA.
Information Technology Project Management – Fifth Edition
CMMI Overview.
CMMI – Staged Representation
Quality management standards
Capability Maturity Model Integration (CMMI)
THE SOFTWARE PROCESS (revisited)
Use of CMMI in an Acquisition Context Using CMMI for Process Improvement at USAF Space and Missile Systems Center (SMC) Dr. Jack R. Ferguson
Acknowledgment of achievement
Software Verification and Validation
Requirements Development in CMMI
Capability Maturity Model
Presentation transcript:

Compliance and Audit Block 17 Block 17

Overview Intent Be able to audit EA products for quality and compliance with the DAF, in order to determine how they can be improved Content Again, using AnnL to assess risks (of an EA as documented) Principles Quality measures Report risks CV3 CV4 In this Block we will see how to assess the risks of emerging technologies, including the price/ performance trade-offs. This material supports 035C1 primarily. This Block draws upon Block 6 Information Collection. The sources of information about emerging technologies, such as www.portal.acm.org are most pertinent here. Of course, it also builds upon Block 9, where we saw how AnnL can be used to develop strategic objectives. Block 17

Activity: What is Compliant? Block 17

Principles of EA Remind them that we have seen Principles for EA before, in Block 5. We can use them as a basis for checking the Compliance of the proposed products with the DAF. Several of the Principles are not all that useful for checking. Most are expressed in general terms - they are values. We need to find the measures that can serve as more precise indicators of the likelihood that these values will not be met by a product. Block 17

Qualities to Audit Use the questions of stakeholders from the DAF Course as values also? What is the difference between these and the principles? Check verification and validation = process risk and product risk Which is what? Principles = process risk Stakeholders = product risk There are additional values that can describe the quality of a proposed EA. What is the difference between the two sets of values? Process risk = quality of the DAF products themselves (verification): logical, well-formed, understandable Product risk = meet the needs (validation): correctly capture capabilities, lead to correct OCT/ FPS Block 17

Using AnnL in Auditing Open In sheet for AnnL for Audit Point out values and measures Block 17

Assess risk of EA products Block 17

Activity: Discuss Remedies Briefly discuss what could be done to reduce the identified shortfalls. Bring out rework effort in redrawing or rethinking design Block 17

Activity: Find risk of own Product As a team For 20 minutes Take one of your products Use AnnL to assess the compliance and quality Be prepared to discuss risks and remedies with others Bring out the point of risk analysis is to find remedies. Ask participants to open AnnL for Audit (pre-populated with values and measures from principles and DAF qualities) Ask team to select one of their own products, get them to set it up as an option in AnnL and then assess it against the measures. Ask them to consider three principles and the three other values that they think have the most impact. After 15 minutes Ask participants to print a risk report (R_11Rsks) Ask one team to highlight risks Ask other team to suggeest what can be done to improve the product in the risk areas. Block 17

Activity: Build CV-3 As a team For 7 minutes Fill in a CV-3 for the risks identified for your own product Block 17

Capability Maturity Model Developed by Software Engineering Institute, Carnegie Mellon University Determines how well an organization uses processes to develop systems Often used to assess suppliers Capability Maturity Models developed by Software Engineering Institute (SEI) at Carnegie Mellon University in Pittsburgh, under contract to the US DOD primarily. Initially had CMM for software, systems engineering, and personnel. Combined them into CMMI-I (Integrated). Used for any process really, including acquisition and now EA (developed in Australia not SEI) Use the framework of CMM as a guide to how well Defence is using EA as an organization. CMMI certification to a certain level is common in tenders for software suppliers (subject to some abuse?) Block 17

CMM Framework Level 1 - Initial Level 2 - Managed (Repeatable) Plans, controls Level 3 - Defined Standards, consistency Level 4 - (Quantitatively) Managed Level 5 - Optimized

Activity: Complete a CV-4 As a team For 10 minutes Rate how well Defence meets the CMM criteria Block 17

Summary Risk management continues with the audit of EA products. We have tools - and forms - for determining these compliance and quality risks Next Block Analysis and presentation Bring out the need to have the best possible products before they are presented to senior officers as part of the capability development process. Block 17