We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byClaud Stevens
Modified about 1 year ago
Pittsburgh, PA 15213-3890 CMMI Acquisition Module - Page M7-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. M7-Conclusion v0.1 Introduction to the CMMI ® Acquisition Module (CMMI-AM) SM CMM Integration, IDEAL, and SCAMPI are service marks of Carnegie Mellon University. ®Capability Maturity Model, Capability Maturity Modeling, CMM, and CMMI are registered in the U.S. Patent and Trademark Office by Carnegie Mellon University. Module 7: Conclusion
© 2005 by Carnegie Mellon University CMMI Acquisition Module - Page M7-2 CMMI ® M7-Conclusion v0.1 “Ad Hoc” Acquisition Practices Operational Need
© 2005 by Carnegie Mellon University CMMI Acquisition Module - Page M7-3 CMMI ® M7-Conclusion v0.1 Explicit Acquisition Practices Acquisition Planning RFP Prep. Solicita- tion Source Selection System Acceptance Program Leadership Insight / Oversight Transition PlanDesign Integrate & Test DevelopDeliver CMMI-SE/SW/IPPD/SS CMMI Acquisition Module Operational Need Developer Acquirer
© 2005 by Carnegie Mellon University CMMI Acquisition Module - Page M7-4 CMMI ® M7-Conclusion v0.1 Questions to Ask About Your Program 1 If you are in the pre-award phase: 1.Do I have a sound risk management program with the PMO? 2.Do I have the proper staffing for the acquisition of a software intensive system? 3.Have I established good working relationships with ALL my stakeholders? 4.Have I considered and documented several alternative acquisition strategies? 5.Have I negotiated my acquisition strategy with all my stakeholders? 6.Do my RFP and/or contract address issues specific to software intensive systems? 7.Are my top-level requirements sound and do they include the “ilities?”
© 2005 by Carnegie Mellon University CMMI Acquisition Module - Page M7-5 CMMI ® M7-Conclusion v0.1 Questions to Ask About Your Program 2 If you are early in execution (concept definition, risk reduction, and/or design phase): 1.Do my PMO and contractor teams have sound processes in place, and can they be integrated appropriately? 2.Does my contractor have a robust risk management program that interfaces to the PMO risk program? 3.Are my system and software architectures responsive to functional and non-functional requirements and are they well documented? Has there been a technical evaluation? 4.Is my software design and code well documented and reviewed? 5.Are my test plans being written and reviewed early? 6.Is my schedule slipping such that the test time will be reduced unacceptably?
© 2005 by Carnegie Mellon University CMMI Acquisition Module - Page M7-6 CMMI ® M7-Conclusion v0.1 Questions to Ask About Your Program 3 If you are later in execution (integration & test phase): 1.Does the contractor have a robust defect handling/tracking system? 2.Are the transition to operations and support plans being developed in time, does it include user input, and does it include any required system certifications? 3.Is the contractor developing a software maintenance plan (to include COTS/GOTS/Open Source)? 4.Is the configuration management system in place? 5.Is the software being tested for robustness as part of the system testing? 6.Are all the interfaces being tested?
© 2005 by Carnegie Mellon University CMMI Acquisition Module - Page M7-7 CMMI ® M7-Conclusion v0.1 What Do I Do Now? 1 If you are in an early program phase: Evaluate the current state of process within the PMO Develop and execute a PMO process improvement plan If you haven’t released your RFP: Ensure the RFP includes contractor process requirements Ensure the evaluation criteria reflect areas of process maturity Ensure you are asking for appropriate measures and artifacts to provide on-going assessment of contractor process compliance
© 2005 by Carnegie Mellon University CMMI Acquisition Module - Page M7-8 CMMI ® M7-Conclusion v0.1 Government Contacts Office Of The Secretary Of Defense: Kristen Baldwin OUSD(AT&L) Defense Systems System Engineering Room 3D1075, 3090 Defense Pentagon, Washington, DC 20301-3090 (703) 695-2300 – Fax: (703) 614-9884 Kristen.Baldwin@osd.mil Air Force: Mike Nicol, Government Co-Chair USAF ASC/EN – Technical Advisor, Embedded Computer Systems Software Bldg 560, 2530 Loop Road West, Wright-Patterson AFB, OH 45433-7101 (937) 255-9566 – Fax: (937) 255-5305 Michael.Nicol@wpafb.af.mil Army: Anthony D’Agosto US Army RECOM-ARDEC – Director, Fire Control Systems & Technology AMSRD-AAR-AEF, Picatinny Arsenal, NJ 07806-5000 (973) 724-3439 – Fax: (973) 724-7321 Anthony.firstname.lastname@example.org Navy: Brenda Zettervall US Navy, ASN/RDA CHENG – Software Systems Engineer 1333 Iasaac Hull Ave, SE, Stop 5012, Washington Navy Yard, DC 20376-5012 (202) 781-3261 Brenda.email@example.com NASA: Dr. John C. Kelly NASA HQ – Suite 2J40, Office of Chief Engineer Washington, DC 20546-0001 (202) 358-3296 – Cell: (202) 997-0245 – Fax: (202) 358-3296 John.C.Kelly@nasa.gov Defense Contract Management Agency: Kathryn (Kathy) Lundeen Defense Contract Management Agency, DCMA CMMI Project Manager, DCMA-OCT 6350 Walker Lane, Metro Park 2, Alexandria, VA 22130 (703) 428-1830 – Fax: (703) 428-1898 Kathryn.firstname.lastname@example.org
© 2005 by Carnegie Mellon University CMMI Acquisition Module - Page M7-9 CMMI ® M7-Conclusion v0.1
Pittsburgh, PA CMMI Acquisition Module - Page M5-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This.
Pittsburgh, PA CMMI Acquisition Module - Page M4-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This.
Pittsburgh, PA Sponsored by the U.S. Department of Defense © 2003 by Carnegie Mellon University This material is approved for public release.
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.
© 2010 Carnegie Mellon University ® CMMI is registered in the U.S. Patent and Trademark Office by Carnegie Mellon University. V&V Principles Verification.
Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 2001 by Carnegie Mellon.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
Pittsburgh, PA CMMI Acquisition Module - Page M3-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This.
Best Systems Engineering Products Drive CMMI NDIA 6th Annual Systems Engineering Supportability & Interoperability Conference October 21, 2003 Dr. Tom.
Cost & Benefit Analysis Executive Overview David F. Rico.
Managing CMMI® as a Project
IV&V Facility 7/28/20041 IV&V in NASA Pre-Solicitation Conference/ Industry Day NASA IV&V FACILITY July 28, 2004.
Carnegie Mellon University Software Engineering Institute CMMI v1.1 Today -– The Current State November 2003 CMMI v1.1 Today - Page 1 © 2003 by Carnegie.
1 Integration of Process Initiatives And Assessments Common Process Framework Integration of Management System Standards and Initiatives (QMS/CMMI/Lean/PMBP)
Copyright ProcessVelocity, LLP Slides intended for informational purposes only. CMM and Capability Maturity Model are registered in the U.S. Patent.
Copyright © 2003 by Cooliemon TM, LLC 1 Causal Analysis & Resolution (CAR) at Level 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
DoD Systems and Software Engineering A Strategy for Enhanced Systems Engineering Kristen Baldwin Acting Director, Systems and Software Engineering Office.
Pittsburgh, PA Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense.
The Software Product Life Cycle. Views of the Software Product Life Cycle Management Software engineering Engineering design Architectural design.
Earned Value Management Presented By: Steve Krivokopich May , 2006.
Copyright © 2003 by Cooliemon TM, LLC 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead Assessor (CMM ® ) SCAMPI Lead Appraiser SM (CMMI.
Roles and Responsibilities
Project Management Methodology More about Quality Control.
Capability Maturity Model Integration (CMMI) COMP Group Assignment #1 Ario Nejad, Davit Stepanyan, Ian Jackman, Sebastian Henneberg, Wan Chi Chio.
DoD Procurement Conference and Training Symposium May 13, 2010 Peer Reviews Dick Ginman Deputy Director, DPAP.
SEI CMM Robert Johnson Bobby Kolski Rafi Seddiqi Kumeel Alsmail.
Capability Maturity Model. Reflection Have you ever been a part of, or observed, a “difficult” software development effort? How did the difficulty surface?
EngMat/JWS.PPT 10/17/ CMMI ® Today – The Current State CMMI ® Technology Conference 2003 November 18, 2003 Ron Paulson Vice President, Engineering.
© 2001 by Carnegie Mellon University PSM-1 OCTAVE SM : Senior Management Briefing Software Engineering Institute Carnegie Mellon University Pittsburgh,
1 Implementing A PMO & Enterprise Project Management at NIH February 3, 2005 Bill Vesey, PMP Manager EPM Consulting Practice Forte Systems, Inc General.
Michael Dermody September 2010 Capability Maturity Model Integration ◦ Is a Trademark owned by the Software Engineering Institute (SEI) of Carnegie.
Requirements Development in CMMI
CS Process Improvement CMM Hans Van Vliet, Software Engineering, Principles and Practice, 3 rd edition, John Wiley & Sons, Chapter 6. W. Humphrey,
DOD SOFTWARE ASSURANCE INITIATIVE: Mitigating Risks Attributable to Software through Enhanced Risk Management Joe Jarzombek, PMP Deputy Director for Software.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Verification and Validation — An OSD Perspective — Fred Myers Deputy Director, Test Infrastructure Test Resource Management Center November 4, 2009.
Cost and Management Challenges of Systems of Systems True Program Success TM Cost and Management Challenges of System of Systems Arlene Minkiewicz, Chief.
Verification and Validation Mark C. Paulk July 16, 2003 SEEK 2003
2004 DoD Standardization Conference Product/Process Certification Panel Bldg. 33 Washington Navy Yard Federal Bldg. Oakland, CAU.S. Courthouse Las Vegas,
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
© 2017 SlidePlayer.com Inc. All rights reserved.