Copyright © 2007 Boeing Unpublished Work. All Rights Reserved Export Classification Determination is carried on the cover page of this document. No ITAR.

Slides:



Advertisements
Similar presentations
© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v
Advertisements

Systems Engineering From a Life Cycle Perspective John Groenenboom Director Engineering – Mesa Boeing Rotorcraft Dec 12, 2007.
Knowledge Management Strategies to Improve Business Performance Chris Paladino March 11, 2002 (703) Knowledge Technologies.
Prescriptive Process models
Requirements Specification and Management
1 PROJECT MANAGEMENT ROLE OF KEY PERSONNEL Bernd Madauss International Space University Strasbourg February, 2011
© 2009 The MITRE Corporation. All rights Reserved. Evolutionary Strategies for the Development of a SOA-Enabled USMC Enterprise Mohamed Hussein, Ph.D.
Lecture # 2 : Process Models
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
GAI Proprietary Information
LR NYU Fall 2007 Business Operations New Product Development Process.
Rational Unified Process
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
DoD Systems and Software Engineering A Strategy for Enhanced Systems Engineering Kristen Baldwin Acting Director, Systems and Software Engineering Office.
Lecture 13 Revision IMS Systems Analysis and Design.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
Requirements Analysis Concepts & Principles
Fundamentals of Information Systems, Second Edition
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Iterative development and The Unified process
Systems Engineering Management
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Principles of Object Technology Module 1: Principles of Modeling.
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
S/W Project Management
Extreme Programming Software Development Written by Sanjay Kumar.
© VESP International Pty Limited To Contents Slide CLICK to advance slides/ bullet points within slides Integrated Master Planner An Overview.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Chapter 2 The process Process, Methods, and Tools
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
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.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Chapter 10 Information Systems Analysis and Design
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems The Integrated Master Plan (IMP) and the Integrated Master Schedule.
Rational Unified Process Fundamentals Module 5: Implementing RUP.
Software Engineering - I
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Verification and Validation — An OSD Perspective — Fred Myers Deputy Director, Test Infrastructure Test Resource Management Center November 4, 2009.
Developed by Reneta Barneva, SUNY Fredonia The Process.
Project Initiation at The Regence Group 12/19/2015John Garrigues1.
Software Project Management Iterative Model & Spiral Model.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Systems Development Life Cycle
SQA project process standards IEEE software engineering standards
DoD Template for Application of TLCSM and PBL
Sample Fit-Gap Kick-off
Introduction to Project Management
Supportability Design Considerations
School of Business Administration
DoD Lifecycle Changes that affect you!
SQA project process standards IEEE software engineering standards
The Open Group Architecture Framework (TOGAF)
INCOSE – North Texas Chapter
Raytheon Parts Management
Engineering Processes
The Design Process.
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Knowledge Management Strategies to Improve Business Performance
Presentation transcript:

Copyright © 2007 Boeing Unpublished Work. All Rights Reserved Export Classification Determination is carried on the cover page of this document. No ITAR data is contained herein – (314) Program Milestone Activities Across The Program Life Cycle William E. Jennings Costa Mesa, CA, February 9-12, 2009 No License is required for the dissemination of the information contained herein to foreign persons other than those from or in terrorist supporting countries identified in the EAR. It is the responsibility of the individual in control of this data to abide by U.S. export laws.

Copyright © 2007 Boeing Unpublished Work. All Rights Reserved Export Classification Determination is carried on the cover page of this document. No ITAR data is contained herein Biography: Bill is a senior study lead and analyst in all Operations Analysis (OA) and System Engineering (SE) technical disciplines. His career in Operations Analysis has focused on developing the skills needed to perform requirements development and validation analyses in an integrated manner with the product- design engineering disciplines, a widely understood industry challenge. He has recognized the ongoing need to define the types of questions that must be answered and decisions that need to be made as programs mature through their life cycle. He is currently leading a team that is responsible for defining the Program Milestone Activities as part of the Systems Engineering contribution to the IDS 10X Initiative. Name: William E. Jennings Key Technical Field: Integrated Requirements And Product Development Phone number: (314) Fax number: (314)

Integrated Defense Systems Systems Engineering Program Milestone Activities Define Products & Tasks Across Program Life Cycle Process Inputs Customer Inputs –Desired Capabilities/Needs –Constraints Technology Base SE Activities Across Life Cycle Process Outputs Fielded Designs Executable CONOPs Evolving Capabilities –User Feedback –Maturing Technologies Understand Capability Needs Capture Maturing Requirements Hypothesize Solution Concepts & CONOPs Define How To Evaluate Solution Concepts Evaluate Solution Concepts Create Conceptual, Preliminary and Critical Designs New DoD Guidance: Emphasizes Prototypes Competition Through Milestone B Timeframe – Now Includes A Preliminary Design Review-1

Copyright © 2006 Boeing. All rights reserved. Integrated Defense Systems Engineering Systems Engineering PMA Define How To Apply BPIs/BPGs In An Integrated Approach Answers to Questions & Decisions Gate (Stage) Questions to be answered & Decisions to be made BPIs Are Used in Combinations Activity threads appear disconnected from perspective of BPIs BPI X BPI YBPI Z

Integrated Defense Systems Systems Engineering What is PMA Technology? Tool for integrated planning for how to get through each formal life cycle phase successfully –Defines the technical content for the life cycle phase (e.g. SRR phase) in the IMP & IMS –Standardizes entry/exit criteria, products that satisfy them, tasks that must be performed A logical workflow of tasks and products throughout each phase Establishes formal definitions of products and data repositories –Defines multiple levels of detail needed across life cycle to mechanize the SE V New DoD Guidance

Integrated Defense Systems Systems Engineering PMAs Strategy and Approach Formal GuidanceQuestion-based Construct By Stage IMP Accomplishment Criteria Objectives by stage Entry/exit criteria Process descriptions Apply formal guidance to identify questions Define information needed to meet objectives Identify tasks & data content Align engr. discipline processes & tools Apply questions to define ACs by stage Define IPT ownership Capture closure criteria & exit product IMS Tasks By IPT Tasks & data content definition Resource alignment (skills, tools, & funding) Critical path & process logical flow

Integrated Defense Systems Systems Engineering Applies Defense Acquisition Guidebook Knowledge-based Approach Why DAG? –Its very difficult to argue with the questions –Gets to the intellectual content of what should be done –Explicitly focuses attention on answering questions vice just do work DAG questions apply to the government program office Boeing must help the DoD customer answer the questions Boeings Challenge: –Address the ambiguity in the questions –Define specific tasks to address the exit criteria –Tailoring tasks as required for specific programs –Provide individual programs with SME guidance for how to answer the questions and provide documented justification

Integrated Defense Systems Systems Engineering What is Unique About The PMA Approach? Defines how to address development activities that are about discovery (e.g., requirements development, functional analysis, trade studies, validation) –Captures an approach that is able to address blind alleys, iterations, and major decision points that are inherent in the discovery process –Planning around processes that are followed from beginning to end works well Discovery and decision making are about answering questions –It is natural to frame the planning and execution process in question framework Information gathering -- Have we collected the right information in preparation for making a decision? Decision making -- Given the alternatives and the available information, which alternative should be selected? Responds to the need for a different paradigm for planning and executing –Not a stove-piped process driven activity The questions framework creates a logical workflow of integrated tasks and products throughout each phase

Copyright © 2006 Boeing. All rights reserved. Integrated Defense Systems Engineering Systems Engineering BPIs/BPGs Tools & Methods for Developing Answers Question Databases Tools for Capturing & Displaying Answers What to Do PMA Framework Guidance on Mapping Requests to Services Services Visualizing the Role of the PMA Framework

Integrated Defense Systems Systems Engineering Systems Requirements Review-Based Questions

Integrated Defense Systems Systems Engineering Logic Flow From Questions To Tasks: Capability Needs Does the program have documented capability needs at the system level (Capability Description Document or equivalent)? –Does the program have documented capability needs at the system level? 1. Identify the inputs that may have capability needs 2. Search the inputs for capability needs 3. Add the capability needs to a consolidated list 4. Identify capabilities being deferred as related to spiral development 5. Produce architecture operational capabilities and concepts view –Have these capability needs been reviewed for understanding by the program? –Have areas of potential misunderstanding or lack of clarity been resolved for consensus within the program and with the customer? Establishing The Foundation The Tasks Approach is repeated for mission scenarios & constraints

Integrated Defense Systems Systems Engineering Validation Of PMA Approach On Multiple Programs

Integrated Defense Systems Systems Engineering Measures for Success Long Term: –Generating the necessary information at the right time to be more competitive –Proactively addressing problems earlier –More successful proposals –Reduction in traveled work and rework on programs –Reduction in Action Items from major program milestones/reviews –Improvement in CPI/SPI –Improvement in Award Fees Near Term: –Acceptance by internal Boeing Customer Community (programs) –Acceptance/endorsement by external Boeing Customer Community (e.g., NAVAIR) –PMA approach leads to improved Program execution and successful entrance/exit of major program milestone/reviews

Integrated Defense Systems Systems Engineering Capabilities Available In CY2009 System-level Program Milestone Activity Threads for ITR, ASR, SRR, SFR, PDR, and CDR LTD Training Module –Overview of the contents and breadth of application of this approach across IDS –Top level tutorial on how to use the Program Milestone Activities (PMA) Planning approach –Detailed guidance for implementation on a program Updated BPG "Integrated Master Plan & Schedule –Work Product Definitions for each major program milestone/review BPG Enhancement & Development to institutionalize PMA approach –Additions to BPG on SEMP Method –Creation of BPGs for each PMA thread Define the integrated tool environment needed to capture engineering technical PMA work-product data artifacts and final products