Sefguide CEDE PSU Ppt

4/10/2003 1

SYSTEMS ENGINEERING FUNDAMENTALS

4/10/2003 2Jim Hines

WHAT’S A SYSTEM?DOD :An integrated composite of people, products, andprocesses that provide a capability to satisfy astated need or objective.

NASA: A set of interrelated components which interact with one another in an organized fashion toward a common purpose.

INCOSE:A construct or collection of different elements that together produce results not obtainable by the elements alone.


SOME EXAMPLES OF SYSTEMS

• NEW COMPUTER NETWORK SYSTEM

• REUSABLE LAUNCH SYSTEM

• A UNIVERSITY

• NATIONAL MISSILE DEFENSE SYSTEM

• 35 MM CAMERA SYSTEM

• TRANSPORTATION SYSTEM

• COMMUNICATION NETWORK SYSTEM

• A ROCK? THE EARTH? A CAR?


ROCK SYSTEM?

Crystalline structure formed of various chemical compoundsChemical compound is formed from chemical elementsEach Element is composed of protons, neutrons, and electronsEven though a rock has a well defined boundary, a rock can be a part of a river bed or part of a geological formation


SOMEONE’S SYSTEM IS SOME ELSE’S SUBSYSTEM

A system is most often hierarchical.

Your system is someone else’s subsystemSomeone’s system, may be your subsystem.


System Understanding

SystemSystem

BoundaryBoundary

EnvironmentEnvironment



BoundaryBoundary

BoundaryBoundary

System Description• Objective or Function: What is purpose or goal? Is it static or dynamic? Is it open or closed?• Control: How is it regulated?• Structure: How is it assembled? Is it physical or conceptual?• Complexity: How many parts and how are they related?• Origin: Is it natural, man-made, etc.?

System Elements• Components• Attributes• Relationships


SYSTEMS ENGINEERING DEFINITIONS International Council Of Systems Engineers (INCOSE): An interdisciplinary approach and means to enable the realization of successful systems.

Electronic Industry Alliance (EIA) Standard IS-632, Systems Engineering (1994): An interdisciplinary approach that encompasses the entire technical effort, and evolves into and verifies an integrated and life cycle balanced set of system people, products, and process solutions that satisfy customer needs.

Institute of Electrical and Electronics Engineering (IEEE) 1220,Standard for Application and Management of the Systems Engineering Process (1994): An interdisciplinary, collaborative approach that derives, evolves, and verifies a life-cycle balanced system solution which satisfies customer expectations, and meetspublic acceptability.


WHY SYSTEMS ENGINEERING?• Increased complexity of products and processes

• Large number of interfaces among components, sub- components, etc

• Evolution of world wide competitive markets & Time to Market (Competition)

• Exponential expansion of knowledge & technology

• Customer demand for optimized systemsIndividuals can no longer solve complex problems by themselves. It has become necessary to organize multi-disciplined teams where each member contributes a specific skill or expertise to achieve a common goal.


SYSTEM COMPLEXITY EXAMPLE –INDY RACE CAR

Carbon- Fiber SkinSophisticated electronic nervous system

Serpentine wiresPrecision sensorsLCDs Spread spectrum wireless communications equipment

Antilock brake systems kick in when sensors detect a spinData Acquisition Geeks (DAGs)

Laptop pulse monitoring of a 800 horsepower data terminal remote control as it speeds around the track at 220mph

4/10/2003 10Jim Hines

Speed of Human Transportation

0

500

1000

1500

2000

2500

0 500 1000 1500 2000 2500

Time (AD)

Mile

s pe

r H

our

RAPID TECHNOLOGY CHANGES

Speed of a galloping horse: 43 MPH

Fastest Jet Airplane: 2193 MPH

Speed of sound 758 MPH ; Chuck Yeager October 1947

Steam powered trains: 126 MPHFirst Autos: 39 MPH

Bullet Trains: 300 MPHFastest Prop Plane: 600 MPH

Fastest jet-powered automobile: 740 MPH

Fastest rocket powered airplane: 4534 MPH

Nuclear powered space craft: 32,000 MPH

Stafford Beer: Brain of the Firm

4/10/2003 11Jim Hines

THREE BASIC ARGUMENTS FOR THE VALUE OF SYSTEMS ENGINEERING

• The cost-time trade effect

Time from project start

Cost to fixa missedrequirement

• Assurance that the system will accomplish its objectives

• Insurance against serious low-probability consequences

4/10/2003 12Jim Hines

COST OVERRUN AS A FUNCTION OF SYSTEMS ENG. EFFORT

Reference: Metrics and Case Studies for Evaluating Engineering Designs, Moody et al

5 10 15 20 25

0

0

40

80

120

160

200* GRO 78

* OMV * TDRSSGALL *

* CHA

SEASAT * * UARS

* STS

* MARS

* TETH

* Ulysses

* Voyager

* COBE

* ERB 80

* ISEE* HEAO

CEN *

* HST

* DB

Systems Engineering Effort (% of Total Cost)

Cos

t Ove

rrun

(%)

4/10/2003 13Jim Hines

AEROSPACE SYSTEMS FAILURES - EXAMPLE OF THE NEED FOR SYSTEMS ENGINEERING

• Multiple failures across different launch vehicles and contractorsVehicle Launch Spacecraft Failure ModeTitan IVA-20 12 Aug 98 NRO Electrical cable shortDelta III 26 Aug 98 Galaxy 10 Vehicle roll stabilityTitan IVB-27/IUS-21 9 Apr 99 DSP-19 IUS Stage separationAthena II 27 Apr 99 IKONOS Fairing failure to sepTitan IVB-32/Centaur-14 30 Apr 99 MILSTAR-3 Centaur guidance s/wDelta III 4 May 99 ORION-III RL10-B2 engine

• No common hardware or software failures/causes among incidents

• Each individual incident considered a small error or oversight •that led to total loss of mission

• Cost of these failures to various users/customers: Over $3 billion!

• Failures initiated president’s broad area review

4/10/2003 14Jim Hines

WHO DOES SYSTEMS ENGINEERING?• All Members of a Multi-disciplinary Team

• Engineering• Quality • Subcontract Management• Business Management• Etc.

• Everyone involved with development of a system should be a “systems-thinker”.

• Keep the end result in mind.• Everyone should use a common framework (PROCESS) and language (REQUIREMENTS):

Sees the forest amongst the trees

Common language and plan

4/10/2003 15Jim Hines

Science determines what IS……..

Component Engineering determines whatCAN BE ……..

Systems Engineering determines whatSHOULD BE …………

Systems engineering provides a systematic and orderly framework that should be accepted and used by all disciplines during the development of complex systems.

4/10/2003 16Jim Hines

A SYSTEMS ENGINEER IS ONE WHOOrientation to customer (s) /stakeholder (s)Promotes broad-based thinkingPractices a top down approachRecognizes the importance of processesEmploys evolving innovative skills, techniques & toolsDevelops appreciation for the role of all disciplines and their integration (Facilitator/ Integrator)Acquires an experience base that prepares & motivates for greater individual responsibility

“Does the Right Things Right”

4/10/2003 17Jim Hines

GENERAL PRINCIPLES OF SYSTEMS ENGINEERINGKnow the problemFocus on purpose(s) Know the customer, ex. the consumer, the user, stakeholder expectationsDiscipline focus on the end productUse operational effectiveness criteria Establish and manage requirements and performance measuresVerify requirements and validate system performanceIdentify and assess alternatives so as to converge on a solutionManage interfacesPerform risk managementMaintain the integrity of the systemUse an articulated and documented processManage against the planCorporate focus on continuous and process improvement and lessons learned

4/10/2003 18Jim Hines

SYSTEMS ENGINEERING IS A PROCESS AS WELL AS A FIELD OF STUDY

4/10/2003 19Jim Hines

APPLICATION OF SYSTEMS ENGINEERINGSystems Engineering process & discipline applies to all programsApplication & Balancing Considerations (“Art of Systems Engineering”)

Size and complexity of the systemLevel of system definition detailScenarios and missionsSet of measures of effectiveness/metricsKnown constraints and requirementsTechnology baseOther factors related to major risk areasEnterprise best practices and strengthsCost, Schedule, and Risk

4/10/2003 20Jim Hines

SUMMARYA system is a construct that produces results not obtained by its elements alone“Systems” Engineering competence is the fundamental skill needed in today’s environment to provide a systematic and orderly framework that can be used by multiple disciplines during development of complex systemsWhat you do upfront will have greatest impact on success/failure later onSomebody’s system can be someone else ‘s subsystemSystems Engineering is a process and a discipline (a field of study).

Requirements key =f[customer, user, developer, life cycle view, program management effort] Systems engineering activity must be designed to manage risk and performance parametersEnsures exploration of a more comprehensive design space

Sefguide CEDE PSU Ppt

Documents

Transcript of Sefguide CEDE PSU Ppt