How Should We Use System of Systems … And Why Should We Care? Dan Cocks Lockheed Martin - MS2 July, 2006.

Slides:



Advertisements
Similar presentations
PROJECT MANAGEMENT BASICS
Advertisements

Project management.
1 Introduction to Software Engineering Rajkumar Buyya Grid Computing and Distributed Systems Lab Dept. of Computer Science and Software Engineering University.
International Business 9e
1 of 18 Information Dissemination New Digital Opportunities IMARK Investing in Information for Development Information Dissemination New Digital Opportunities.
College of Continuing Education Systems Engineering Non-credit Certificate.
Introduction to Product Family Engineering. 11 Oct 2002 Ver 2.0 ©Copyright 2002 Vortex System Concepts 2 Product Family Engineering Overview Project Engineering.
Objectives To introduce software project management and to describe its distinctive characteristics To discuss project planning and the planning process.
2005 Operating Review & 2006 Strategy outline January, 2006 China Oilfield Services Limited.
EECE 310: Software Engineering Modular Decomposition, Abstraction and Specifications.
Chapter 10 Fashion Distribution Buying Fashion Selling Fashion.
Cost as a Business Driver 1 John Brown C Eng MIEE mr_ Software Cost Estimation.
© 2009 South-Western, Cengage LearningMARKETING 1 Chapter 9 DEVELOPING A MARKETING STRATEGY AND MARKETING PLAN 9-1Elements of a Marketing Strategy 9-2Marketing.
Customer Development Week 3.
5.9 + = 10 a)3.6 b)4.1 c)5.3 Question 1: Good Answer!! Well Done!! = 10 Question 1:
Component-Based Software Engineering Main issues: assemble systems out of (reusable) components compatibility of components.
How to commence the IT Modernization Process?
Absolute-Value Equations and Inequalities
FPA – IFPUG CPM 4.1 Rules.
NDIA SoS SE Committee Topics of Interest May 25, 2009.
Bottoms Up Factoring. Start with the X-box 3-9 Product Sum
Supply Chain Performance Measurement
Ch. 13: Supply Chain Performance Measurement: Introduction
Supply Chain Performance Measurement
Software Quality David Jones, Director. 2 Agenda What is it and why is it important? How do we deliver it? Conclusions.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Systems Engineering in a System of Systems Context
Software Engineering Techniques for the Development of System of Systems Seminar of “Component Base Software Engineering” course By : Marzieh Khalouzadeh.
CHAPTER 11 Inference for Distributions of Categorical Data
Tip for expanding size of video screen 1. Introduction of features & benefits The evolution of selling 2 No model Separation of sales & acct. mgmt. Solution.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 5 Slide 1 Project management.
Software Project Management Course Instructor Samana Zehra (Assistant Professor)
Software Engineering Principles Chapter 3 From Software Engineering by I. Sommerville, Slide 1 project managementorganizing planning scheduling Learning.
Thinking Actively in a Social Context T A S C.
17136C Understanging Buyers Ch.09 Attitudes Section A:True or False.
Dayton High School Mr. Martin. Lesson Objectives After this lesson, you will be able to:  Describe the process of product planning and development. 
AD3112 BRAND COMMUNICATION A.Autcha Sudhankitara (A.JIG)
~ pertemuan 2 ~ Oleh: Ir. Abdul Hayat, MTI 06-Mar-2009 [Abdul Hayat, The Project Management and IT Context, Semester Genap 2008/2009] 1 THE PROJECT MANAGEMENT.
A COMPETENCY APPROACH TO HUMAN RESOURCE MANAGEMENT
11-1 Copyright © 2013 Pearson Education, Inc. publishing as Prentice Hall Chapter 11 Marketing Processes and Consumer Behavior.
Measuring Complex Achievement
Chapter 13 Promotion Strategies: Personal Selling, Publicity, and Sales Promotion.
1 Project Management Introduction. 2 Chap 1 What is the impact? 1994: 16% of IT projects completed “On-Time” 2004 : 29% of IT projects “On- Time” 53%
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
CPSC 871 John D. McGregor Module 6 Session 3 System of Systems.
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 2 Project Management Cycle.
The Practice of Statistics, 5th Edition Starnes, Tabor, Yates, Moore Bedford Freeman Worth Publishers CHAPTER 11 Inference for Distributions of Categorical.
Chapter 11: Inference for Distributions of Categorical Data Section 11.1 Chi-Square Goodness-of-Fit Tests.
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
Copyright 2009 John Wiley & Sons, Inc. Chapter 6 Project Activity Planning.
Advanced Quantitative Research ED 602. You know, Mary Stevens has really blossomed this year. She is doing much better. Actually, this whole fifth grade.
Project Management Role or Discipline Geof Lory – GTD Consulting, LLC.
MM271 Introduction to Marketing Topic 4 Identifying Market Segments & Targets.
CSC480 Software Engineering Lecture 5 September 9, 2002.
1 IT Project Management, Project Failure and Success  Introduction  Projects operate in a broad organizational environment.  Project managers need to.
INCOSE Systems of Systems Working Group Alan Harding BAE Systems Dr. Judith Dahmann MITRE Corporation SoS Working Group Co-chairs.
Chapter 2 : The Project Management and Information Technology Context Information Technology Project Management, Fourth Edition.
National Response Department 2010 TCT Refresher Session.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Alex Jacobson Presents An Introduction To Software Engineering.
Power point presentation for the first two weeks Biology Grade 9.
Thinking Maps: How to and Why
Getting to the Root of the Problem Learn to Serve 501 Commons November 6, 2013 Bill Broesamle.
The Marketing Concept Implementing the Marketing Strategy.
Developing Personal Identity and Character (2:35) Click here to launch video Click here to download print activity.
Thinking Maps Bridget Vannice. Thinking Maps Learning Target Participants will learn about the 8 Thinking Maps. Success Criteria: By the end of this class.
Assistant Professor of Computer Science Washington State University
The Systems Engineering Context
Identify Different Chinese People with Identical Names on the Web
Chapter 2: The Project Management and Information Technology Context
Presentation transcript:

How Should We Use System of Systems … And Why Should We Care? Dan Cocks Lockheed Martin - MS2 July, 2006

2 Context: Systems Engineering (SE) is a relatively new engineering discipline SE is characterized by a disciplined process that can be applied across a variety of problems –Telephony (early 1900s) –Missile defense (~1940s) –Software-intensive systems (~1970s) Premise: In order for the term System of Systems Engineering (SoSE) to have meaning apart from SE, there must be meaningful differences in their respective processes

3 Introduction: You have recently been asked to lead a Systems Engineering (SE) development project. At your first meeting, you have learned that it is actually a System of Systems (SoS) project. What does that change for you? –Additional engineering steps for your team? –Different milestones? –Different types of risks? –Different skill mix needed to staff the team? Does it tell you anything for sure?

4 Common SoS Characteristics: System of Systems: operational independence of individual systems managerial independence of the systems geographical distribution emergent behavior evolutionary development Many SoS definitions & characterizations look like a result of whiteboard brainstorming of lots of ideas of what systems of systems often look like.

5 Common Characteristics are not Always Distinguishing Characteristics SoS does not always mean geographically dispersed –some systems (not SoS) are dispersed A SoS may not always display emergent behavior –many systems (not SoS) have emergent behavior) Many fast cars are red –Color does not make them fast

6 SE vs. SoSE In order to have SoS Engineering (SoSE) that is distinct from SE, we must identify: –A boundary that clearly segregates SE and SoS projects and/or systems so we can tell them apart. –Engineering steps or other characteristics that apply to one and not both engineering projects so we know why we need to tell them apart.

7 Whats in a Name? What makes Ketchup Fancy? –More vinegar & spice? –More sugar? –More preservatives? Is Fancy used to convey meaning, or just to impress? Pictures courtesy of The Original Condiment Packet Museum

8 Is SoSE just Fancy SE? Does SoSE convey meaning, –Different life cycle –Different development/sustainment processes –Different development/sustainment staffing needs Or is the term used more to impress than to inform? –Bigger –Harder –More complex in some unspecified number of ways

9 SoSE is not Bottoms-up Engineering Some see: Systems Engineering (SE) as top-down solutions to a known mission or problem SoSE as a bottom-up discovery of new problems that can be solved using existing systems in new ways. –Hence, a Lego ® problem: What can I build from these? Pictures from

10 A Postulated Definition for SoS: A system of systems is a product of a system engineering process that contains one or more systems for which significant aspects of the integration and life cycle development of the component system(s) are beyond the managerial control or influence of the larger system.

11 Is it SE, SoSE, or FoSE*? *FoSE = Family of Systems Engineering

12 Is the SoSE Process Different than an SE Process? SoSE is part of SE, so there are no process steps that are unique to SoSE SoSE is a particular type of SE: –Trade studies may be fewer because large chunks of functionality are already provided in legacy systems –Risks may be greater since legacy systems have managerial independence –Development staffing, schedules, & budgets should be adjusted to reflect these differences

13 Summary SoSE is not a meaningful term –The engineering processes for a SoS are the same as SE processes for any other system SoS is a sub-category of systems for which component parts are systems with managerial independence –SoS programs have common risks and attributes so the balance of SE steps tend to be similar –Programs can benefit from recognizing a SoS and planning accordingly

14 Back-up (to Ketchup) Someone actually paid $7.00 to Google Answers to get about a page of research that concluded: –It would appear that the use of Fancy, as with many other packaging notations, is merely a marketing ploy to try to convince the consumer that one brand of seasoned tomato glop is better than another.