Links in the Chain Why Mature Systems Engineering is Needed Richard Conn Microsoft December 2003.

Slides:



Advertisements
Similar presentations
SOFTWARE PROCESS IMPROVEMENT “Never Stop Learning”
Advertisements

S3-1 © 2001 Carnegie Mellon University OCTAVE SM Process 3 Identify Staff Knowledge Software Engineering Institute Carnegie Mellon University Pittsburgh,
Chapter 2 The Software Process
S2-1 © 2001 Carnegie Mellon University OCTAVE SM Process 2 Identify Operational Area Management Knowledge Software Engineering Institute Carnegie Mellon.
Low Defect Potentials (< 1 per function point)
1 The Role of the Revised IEEE Standard Dictionary of Measures of the Software Aspects of Dependability in Software Acquisition Dr. Norman F. Schneidewind.
Software Quality Processes – Part I CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 16, 2007.
SE 470 Software Development Processes James Nowotarski 12 May 2003.
SE 450 Software Processes & Product Metrics 1 Quality Systems Frameworks.
Dr. Richard Frost Global Director, Systems Development and Program Management Driving Global IT Performance with the CMMI for Acquisition November
Capability Maturity Model (CMM) in SW design
Capability Maturity Model (CMM) Done By :Delayel Alhajeree.
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Lecture 11 CMM CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
Capability Maturity Model
Careers in Human Factors Also called Ergonomics or Engineering Psychology Wally Boot, Ph.D. Department of Psychology Florida State University.
OSE2 - 1 Introduction to Software Engineering Professional Issues SWENET OSE2 Module June 2003 Developed with support from the National Science Foundation.
Project Management Methodology More about Quality Control.
Process: A Generic View
Mission Assurance SI International’s Quality Management System John Wheeler Director, Mission Assurance 16, April 2008.
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
Test Organization and Management
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
N By: Md Rezaul Huda Reza n
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 1 (Ch. 1, 2, & 3)
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
INTERNATIONAL SOCIETY FOR TECHNOLOGY IN EDUCATION working together to improve education with technology Using Evidence for Educational Technology Success.
Chapter 2 Process: A Generic View
Integrated Defense Systems 1. 2 Greatest Needs: Engineers (Software, Avionics, Systems) Financial Analysts Current Critical Skills: Software Quality EngineerElectrical.
EngMat/JWS.PPT 10/17/ CMMI ® Today – The Current State CMMI ® Technology Conference 2003 November 18, 2003 Ron Paulson Vice President, Engineering.
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
SAM Executive Seminar Software Measurement.
SEI CMM Robert Johnson Bobby Kolski Rafi Seddiqi Kumeel Alsmail.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
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.
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
Process: A Generic View
Click to add text SUITE SEM Implementation Process Training.
DOD SOFTWARE ASSURANCE INITIATIVE: Mitigating Risks Attributable to Software through Enhanced Risk Management Joe Jarzombek, PMP Deputy Director for Software.
1 Bill Prymak, US Department of Energy Golden Field Office February 19, 2009 Energy Assessments: What are the Benefits to Small and Medium Facilities?
COMP 6710 Course NotesSlide 3-0 Auburn University Computer Science and Software Engineering Course Notes Set 3: Software Process Maturity Computer Science.
Statistical Organization and Management: Information Technology Stefan Schweinfest, UNSD Workshop for SADC Member States, Luanda, December 2006.
1 Chapter 2 A Generic View of Process Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
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
Chapter 9 The People in Information Systems. Learning Objectives Upon successful completion of this chapter, you will be able to: Describe each of the.
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.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
P ERSONAL & TEAM PROCESS MODELS Lecture 05 Part -2.
1 Integration of Process Initiatives And Assessments Common Process Framework Integration of Management System Standards and Initiatives (QMS/CMMI/Lean/PMBP)
Advanced Software Engineering Dr. Cheng
CS4311 Spring 2011 Process Improvement Dr
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Compliance and Audit Block 17 Block 17.
Software Engineering (CSI 321)
2012 Capstone Design Conference Amin Karim, DeVry University
CMMI Overview.
Where We Are Now. Where We Are Now Project Oversight Project Oversight Oversight’s Purposes: A set of principles and processes to guide and improve.
Business Relationship Management
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Capability Maturity Model
Use of CMMI in an Acquisition Context Using CMMI for Process Improvement at USAF Space and Missile Systems Center (SMC) Dr. Jack R. Ferguson
Capability Maturity Model
Presentation transcript:

Links in the Chain Why Mature Systems Engineering is Needed Richard Conn Microsoft December 2003

Links in the Chain - Systems Engineering2 Motivation – Software-Intensive Systems Engineering More and more, systems are becoming software intensive, containing millions of lines of code! People have to work in teams to produce many kinds of products – one person cannot do it alone in most cases!

Links in the Chain - Systems Engineering3 The Systems We Build  Business-Critical  Financial  Infrastructure  Mission-Critical  Business-Critical  Domain-Specific  Safety-Critical  Lives are at stake! More and more, failure is NOT an option!

Links in the Chain - Systems Engineering4 The Systems Engineering Job  Produce quality product  Contain costs  Complete on time BudgetSchedule plan actual plan actual

Links in the Chain - Systems Engineering5 Capability Maturity Target Time/$/... Repeatable Level Defined Level Managed Level Optimizing Level Initial Level Probability Target

Links in the Chain - Systems Engineering6 Software Intensive Systems  DUSD(S&T) responsible for Software Intensive Systems - Mar 99  Established:  Software Intensive Systems Directorate  Software Intensive Systems Steering Group  Defense Software Collaborators

Links in the Chain - Systems Engineering7   SIS Strategy:   Policy   Collaboration   Education and Training   Science and Technology   SIS activities are focused on recent Defense Science Board Recommendations. DoD’s Software Intensive Systems Strategy

Links in the Chain - Systems Engineering8  Stress software process and past performance  Institutionalize independent expert program reviews  Improve software skills of acquisition and program management  Collect, disseminate and employ best practices  Restructure contract incentives  Strengthen the technology base Defense Science Board Recommendations

Links in the Chain - Systems Engineering9  Established to provide a single model framework for engineering process improvement  Incorporates critical engineering principles by integrating systems and software engineering  Oct 99 - Compliance with maturity level 3 required for all DoD contractors Capability Maturity Model Integration (CMMI)

Links in the Chain - Systems Engineering10 Context  Maturity is about …  People  Following a disciplined process  To create software- intensive products

Links in the Chain - Systems Engineering11 People are … MMMMembers of a Team AAAAssigned one or more leadership/management roles TTTTeam Leader DDDDevelopment Manager PPPPlanning Manager QQQQuality/Process Manager SSSSupport Manager EEEEach role has a set of specific responsibilities TTTThese responsibilities vary from process to process RRRRecurring responsibilities, which are repeated in all processes, also exist

Links in the Chain - Systems Engineering12 The Process is …  A set of activities for producing a product or set of products  Processes may also contain other processes  Each process has at least –  An entry criteria  A set of activities or processes to follow  A set of products to be consumed  A set of products to be created or modified  An owner (who can change it), a controller (who runs it)  An exit criteria

Links in the Chain - Systems Engineering13 The Products are …  Software (in the context of Software Engineering)  Code (obviously)  Documents  Data  Hardware  Created by people  Used by people

Links in the Chain - Systems Engineering14 Real-World Processes In-Class Exercise  Industrial-Strength Software-Intensive Systems Engineering  Academic-Strength Software Engineering  Paper and talk to be published and presented at SIGCSE 2004

Links in the Chain - Systems Engineering15 Context (Reprise) = optional People following a disciplined process to create software - intensive products

Links in the Chain - Systems Engineering16 Aircraft Requirements Sources Aircraft SW Direction Assessments SEI SW CMM DOD STDS FAA DO-178B Multiple Customers In Multiple Countries ISO 9001 Safety Critical Software Process Guide Software Products Safe / Reliable Low Risk Maintainable Modular Reusable Cost Effective Mission-Critical SPP/SDP CoRE ADARTs SPARK MC/DC Test Template Based Training Metrics IEEE AeroCorporate

Links in the Chain - Systems Engineering17 Perspectives  Department of Defense  Outsourcing  Learning Federation  Microsoft

Links in the Chain - Systems Engineering18 Department of Defense Perspective  Undersecretary of Defense for Science and Technology Briefing (2001)  Department of Defense  The Road Ahead  DoD Directive

Links in the Chain - Systems Engineering19 Outsourcing Perspective  Building Airplanes in the Sky  Adaptive Organizations  Statistics, Issues

Links in the Chain - Systems Engineering20 Learning Federation Perspective  What is the Learning Federation?  Roadmaps for the Future

Links in the Chain - Systems Engineering21 Microsoft Perspective  Bill Gates – Microsoft Research Faculty Summit 2003

Links in the Chain - Systems Engineering22 New World Order Our society depends on software for its day-to-day existence, and the failure of software systems is increasingly becoming intolerable. Software Engineering is entering universities around the world, becoming a necessary component of an education in computer science and information technology.  Universities such as MIT, Carnegie Mellon University, and Stanford have had software engineering programs  Computing Curriculum 2001 of the Association for Computing Machinery’s Special Interest Group in Computer Science Education contains Software Engineering Knowledge Units  Software Engineering program accreditation by the Accreditation Board for Engineering and Technology (ABET) began in the Fall of 2002  Systems Engineering is coming! USC (TRW), UMR (Boeing), SPSU (Lockheed), UHCL (NASA)

Links in the Chain - Systems Engineering23 Link to the Warfighter New Ideas, Knowledge High Risk, High Payoff Innovation, Transition Maximum National Security Payoff Service Labs Universities DARPAIndustries Expanded Resource Base Interagency Coalition Capability International S&T Requires Strong Partnerships

Links in the Chain - Systems Engineering24