JJ & E Research Specialty Engineering as an Element of Systems Engineering INCOSE MEETING (Enchantment Chapter) August 9, 2006 Murray Elowitz JJ & E Research.

Slides:



Advertisements
Similar presentations
JJ & E Research INCOSE 8/17/04 SE In Acquisition System Engineering in the Acquisition Process Presented to INCOSE Enchantment Chapter August 18, 2004.
Advertisements

Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
1 Highly Accelerated Life Test (HALT) Wayne Bradley 8 April 2014.
Chapter Twelve Approaches to Systems-Building. The Traditional Systems Lifestyle The systems lifecycle is a traditional methodology for developing an.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Fundamentals of Information Systems, Second Edition
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Principles of Information Systems, Sixth Edition 1 Systems Investigation and Analysis Chapter 12.
Development Processes and Product Planning
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Investigation and Analysis Chapter 12.
Systems Engineering Management
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
Mastering OOA/OOD with UML. Contents Introduction Requirements Overview OOAOOD.
Engineering Systems of.
Software Evolution Planning CIS 376 Bruce R. Maxim UM-Dearborn.
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
1.1 1 Introduction Foundations of Computer Science  Cengage Learning.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Definition of Concurrent Engineering "Concurrent engineering is a systematic approach to the integrated, concurrent design of products and their related.
Design Development Image credit:
Software System Engineering: A tutorial
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter 2 Computer-Based System Engineering As modified by Randy Smith.
SOFTWARE ENGINEERING1 Introduction. Software Software (IEEE): collection of programs, procedures, rules, and associated documentation and data SOFTWARE.
Managing Motor Fleet Safety Programs: Training for the Safety Director Unit 3 – The Quality Approach to Safety Programs NATMI © 2014.
Identify steps for understanding and solving the
Best Systems Engineering Products Drive CMMI NDIA 6th Annual Systems Engineering Supportability & Interoperability Conference October 21, 2003 Dr. Tom.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
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)
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
Bill Fournier Nov 2014 Systems Engineer for Non SE Bill Fournier
SOFTWARE ENGINEERING1 Introduction. SOFTWARE ENGINEERING2 Software Q : If you have to write a 10,000 line program in C to solve a problem, how long will.
Project Management Cross lifecycle Activity
© Wiley Total Quality Management by Adnan khan.
Unit-3 Reliability concepts Presented by N.Vigneshwari.
Objectives how to use a systematic, top-down process when designing computer networks focuses on the first step in top-down network design: analyzing your.
How the NCSX Project Does Business
Systems Engineering (Sistem Mühendisliği) Doç. Dr. A. Egemen YILMAZ Ankara Üniversitesi Elektrik-Elektronik Müh. Bölümü
PROGRAMMING FUNDAMENTALS INTRODUCTION TO PROGRAMMING. Computer Programming Concepts. Flowchart. Structured Programming Design. Implementation Documentation.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
1 ME Spring 2015 Systems Engineering, Part II Session 8 5 February 2015 Mr. Larry Hopp, CPL © Copyright 2013.
Advanced Software Engineering Dr. Cheng
Chapter 11 Project Management.
Session 2 Dr. Dan C. Surber, ESEP
Chapter 1 The Systems Development Environment
Supportability Design Considerations
Chapter 1 The Systems Development Environment
Systems Analysis and Design in a Changing World, 4th Edition
Principles of Information Systems Eighth Edition
Chapter 1 The Systems Development Environment
Introduction SOFTWARE ENGINEERING.
SE and SSE Trade-Off Analyses
Development Projects / Analysis Projects / On-site Service Projects
Chapter 1 The Systems Development Environment
Data Collection Learning Objectives
Chapter 3: Design Solutions
Problem Solving: Structure Charts
Project Management Chapter 11.
RELIABILITY Reliability is -
Chapter 1 The Systems Development Environment
System architecture, Def.
Chapter 2: Development process and organizations
Presentation transcript:

JJ & E Research Specialty Engineering as an Element of Systems Engineering INCOSE MEETING (Enchantment Chapter) August 9, 2006 Murray Elowitz JJ & E Research Corp Greenview NE Albuquerque, NM (505)

JJ & E Research Aug 9, 2006 M. Elowitz2 To discuss how System Engineers include SPECIALTY ENGINEERING in their project Defining Specialty Engineering Where it fits into System Engineering Example 1: Meeting spec Example 2: More subtle Purpose Goal: Maximize effectiveness of specialties to support program success

JJ & E Research Aug 9, 2006 M. Elowitz3 Exercise for the student – define products of each specialty Defining Specialty Engineering Murrays Definition (Todays version) – Specialty Engineering is the collection of those narrow disciplines that are needed to engineer a complete system Some specialty engineering has deliverable functional products, Some specialty engineering is analytic.

JJ & E Research Aug 9, 2006 M. Elowitz4 What are specialties SAMPLE LIST (For integrated hardware/software/data systems) RELIABILITY, MAINTAINABILITY, AVAILABILITY Human Factors Safety Electromagnetic Effects Facilities Some people include Logistics Exercise for the student – Name other specialties

JJ & E Research Aug 9, 2006 M. Elowitz5

JJ & E Research Aug 9, 2006 M. Elowitz6 Definitions

JJ & E Research Aug 9, 2006 M. Elowitz7 Typical Org Chart Program Manager System Engineer Specialties RMA Human Factors Safety Etc HardwareSoftwareLogistics Alternate Specialties under System Engineering - Allows careful direction to get to needed results

JJ & E Research Aug 9, 2006 M. Elowitz8 Characteristics Why distinguish the specialties from System Engineering? –Usually a narrow discipline; e.g., RMA –In project team, hard to level load manpower –Practitioners usually want their own identity Why place specialties under System Engineering? –For early phases (Concept Definition through DemVal) SE needs to control or task the specialties Knows where the problems and issues are Understands and performs top-level trades Exercise for the student – Give more reasons

JJ & E Research Aug 9, 2006 M. Elowitz9 In System Engineering Process System Requirements Specialty Require System Design Specialty Design System Analysis Specialty Analysis Preliminary Design Specialty Des, Anal

JJ & E Research Aug 9, 2006 M. Elowitz10 Example 1: Meeting spec Critical Requirement is reliability of commercial aircraft After initial modeling, AVIONICS is critical segment Model Reliability Design Iteration Add Detail Reliability Design Iteration Reflect results Two sides to iteration Underdesign drives loss of sales Underdesign drives warranty costs Overdesign drives cost, possibility loss of sales Did Not Meet Specs Did Not Meet Specs Add Detail Reliability OK Meets Specs

JJ & E Research Aug 9, 2006 M. Elowitz11 Process Reliability Handbook Model System Look up Failure Rates Crunch Present Examples of the kind of system level trades needed instantly System engineer needs special studies What is sensitivity of R to tolerance on controlled temperature? If tightening up on Temp increases vibration, what is system R? If we replace component C with a cheaper one, but use redundancy, will we still meet R spec?

JJ & E Research Aug 9, 2006 M. Elowitz12 Example 2: More subtle Availability – Requires reliability calculations and corresponding MTTRs What if the baseline design makes component K hard to replace, creating a large MTTR? –System tradeoffs may involve lowering MTTR on other components, improving R of component K or others, major design changes to lower Ks MTTR, and so on (and on) –System engineer needs to direct Specialty Engineering to solve the right problem Then SE may need to address whether spec is reasonable

JJ & E Research Aug 9, 2006 M. Elowitz13 System Engineering Golden Rules

JJ & E Research Aug 9, 2006 M. Elowitz14 Summary In the early phases of a program, System Engineering needs tight control over Specialties –Needs to direct resources –Needs to prioritize –Needs responsiveness Putting Specialties under System Engineer provides needed control System Engineer needs to know the capabilities and limitations of each specialty