MITESD_33SUM10_lec01

7/28/2019 MITESD_33SUM10_lec01

1/52

ESD.33 Systems Engineering

Lecture 1Course Introduc8on

Instructors:Dr. Qi Van Eikema Hommes

Mr. Pat Hale

Mr. David Erickson

Teaching Assistants:

Ellen Czaika

Ipshita Deepak


2/52

Agenda

Welcome and Introduc8on of Teaching Staff Why are we here?

What are Systems? What is Systems Engineering? Why do we study Systems Engineering?

Course Schedule and Logis8cs

Qi Van Eikema HommesJ une 8, 2010 2


3/52

Dr. Qi Van Eikema Hommes

ESD Research Associate and Lecturer

years of work experiences in automo8vecompanies (Ford and GM)

Senior Research Scien8st at GM R&DPowertrain Systems Engineer at Ford

Qi Van Eikema Hommes

Ph.D. and M.S. in

Mechanical Engineering B.S. in MechanicalEngineering

J une 8, 2010 3

MIT University ofKentucky


4/52

Dr. Pat Hale

SDM Director, ESD Senior Lecturer

Military experience:

-20 years in U.S. Navy: submarines Industry experience:

-Draper Labs (Director, Systems Engineering)-O8s Elevator (first Director, Systems &

Controls Engineering) Past INCOSE president

J une 8, 2010 Qi Van Eikema Hommes 4


5/52

Academic Background

B.S. Mechanical Engineering

University of Minnesota

M.S. Mechanical Engineering

Engineers Degree in Ocean Engineering

Massachusetts Institute of Technology

MBA

Cornell University



6/52

About me:

Product designer/ manager, systems engineer,

mobile tech enthusiast, a mother, vocal ar8st and a

second year SDM student



7/52

About me:

SDM0

Former manager of systems engineering team

Ethnographer

Athlete (numerous sports: rowing, yoga, skiing/snowboarding,hiking, biking, sailing, surfing, etc.)



8/52

Why Are We in This Class?



9/52

Qi Van Eikema Hommes June 8, 2010

9

Image by MIT OpenCourseWare.


10/52

Is This a System and Why?

http://science.howstuffworks.com/power.htm/printable


Power grid image removed due to copyright restrictions.

Image can be found at HowStuffWorks.com.
http://science.howstuffworks.com/environmental/energy/power.htmhttp://science.howstuffworks.com/environmental/energy/power.htm


11/52




12/52



Name

Headquarters

SecurityDepartment

Name

StrategyDepartment

Name

FinanceDepartment

Name

IT Department

Name

PersonnelDepartment

Name

LegalDepartment

Name

Public RelationsDepartment

Name

MarketingDepartment

Name

SalesDepartment

Name

ResearchDepartment

Name

LogisticsDepartment

Name

Production

Name

Administration

Name

Corporate Name



13/52

Is This a System and Why?http://ccl.northwestern.edu/netlogo/models/WolfSheepStrideInheritance(ANIMATION)Works in Firefox browser

Wolves eats sheep.

Sheep eat grass.Wolves and sheep reproduce.

They move in random directions.

Try when there are more wolves than

sheep.

J une 8, 2010 Qi Van Eikema Hommes13
http://ccl.northwestern.edu/netlogo/models/WolfSheepStrideInheritancehttp://ccl.northwestern.edu/netlogo/models/WolfSheepStrideInheritance


14/52

What Types of Systems Have You

Worked on?

Why do you call them systems?



15/52

Defini8on of Systems

A combina8on of interac8ng elementsorganized to achieve one more stated

purposes.

An integrated set of elements, subsystems, orassemblies that accomplish a defined

objec8ve. These elements include products

(hardware, soware, firmware), processes,people, informa8on, techniques, facili8es,

services, and other support element.Source: INCOSE SE Handbook, V3.2



16/52

Characteris8cs of Systems

Interac8on

Hierarchical

Emergent Dynamic

Interdisciplinary


Di it l Ph t h


17/52

Digital Photography


Inkjet Photo Printer

PictBridge Compatible

Printers (with Direct Print)

PC CompatibleComputer

CF/SD Cards

USB Cable

USB Cable

USB Cable

(FireWire IFC-200D4/D44 or IFC-450D4/D44cable for EOS 1Ds Mark IIand EOS 1D Mark II)

Interface CableIFC-300PCU/IFC-400PCU(EOS-1Ds Mark II , 1D Mark II,20D, Digital Rebel XT, Digital Rebel)

CF/SD CardReader

PC Card Adapter

EOS Digital Cameras(with Direct Print)

EOS-1Ds Mark II

EOS-1D Mark II

EOS-20D

EOSDigital Rebel

EOS

Digital Rebel XT

Computers

MacintoshComputer

Compact Photo Printer



18/52

System of Systems

Largescale interdisciplinary problems involvingmul8ple, heterogeneous, distributed systems.

System elements operate independently.

System elements have different life cycles. The iniAal requirements are likely to be ambiguous.

Complexity is a major issue.

Management can overshadow engineering.

Fuzzy boundaries cause confusion.

SoS engineering is never finished.Source: INCOSE SE Handbook V3.2



19/52

This Class Focus



20/52

Agenda






21/52

What is Systems Engineering?

Systems engineering is a discipline that concentrates on the

design and applica8on of the whole (system) as dis8nct from

the parts. It involves looking at a problem in its en8rety, taking

into account all the facets and all the variables and rela8ng

the social to the technical aspect.

Systems engineering is an itera8ve process of topdown

synthesis, development, and opera8on of a realworld system

that sa8sfies, in a near op8mal manner, the full range of

requirements for the system. INCOSE SE Handbook V3.2



22/52

What is Systems Engineering?

Systems engineering is an interdisciplinary approach and

means to enable the realiza8on of successful systems. It

focuses on defining customer needs and required

func8onality early in the development cycle, documen8ng

requirements, and then proceeding with design synthesis and

system valida8on while considering the complete problem:

opera8ons, cost and schedule, performance, training and

support, test, manufacturing, and disposal. SE considers both

the business and the technical needs of all customers with the

goal of providing a quality product that meets the user needs.

INCOSE SE Handbook V3.2



23/52

Applica8on Domains of Systems

Engineering Aerospace Urban Infrastructure

Communica8ons systems

Data and informa8on systems

Healthcare systems

Electric power systems

Produc8on/construc8on systems

Waste disposal systems

Transporta8on systems

Financial systems

Educa8on systems

Source: Blanchard, Fabrycky, Systems Engineering and Analysis, 5th ed.



24/52

Waterfall Process Model

Introduced by Royce

in 1970, initially forsoftware

development.



RequirementsAnalysis

Specifications

Design

Implementation

Test

Maintenance

FEEDBACK



25/52

Spiral Process Model

Boehm, 196.

Adapted from

Waterfall model Itera8ve

Prototyping



Need

System

Requireme

nts

Deter

mination

Function

Defin

ition

Detail

Requi

rement

s

Feasibility

Analysis

Requirem

ents

Allocation

Component

Design

Components

System

Analysis

System

Specification

Select

Design

Equip

ment

Definiti

on

Trade-Off

Studies

Evaluationand

Optimization

ConceptualReview

TestandReview

FormalDesignReview

Operational

Prototype

SynthesisSyste

m

Prototype

Implemen

tation



26/52

INCOSE VEE Model


27/52

INCOSE VEE Model




28/52

Is There a Winner?

It is observed that preferences expressed byindividuals and groups for one of the system

models is subjec8ve.

Research is needed to see which model fitswhat situa8on beer.

Class Discussion:

What are common among these processes?Is Systems Engineering the same from Product

Development?



29/52


30/52

Agenda





The Value of Systems Engineering


31/52

y g g




32/52

The Value of Systems Engineering

Systems engineering efforts reduce cost andschedule overrun.

Class discussion: Why? Think back about the

characteris8cs of systems.

Interac8onHierarchicalEmergenceDynamicInterdisciplinary



33/52

History of Systems Engineering

The MachineAge

1940s

The SystemsAge


Th M hi A


34/52

The Machine Age Reduc9onismEverything can be reduced, decomposed, or

disassembled to simple indivisible parts. Analy9cal way of thinking

Take apart what is to be explained Explain the smaller parts. The whole is the sum of its parts.

Mechanism

Cause and effect, determinis8c thinking Closed System Thinkingignore the environment a

phenomenon is in.

Mechaniza9on Industrial revolu8on (119th century) Machine subs8tute people for physical work Dehumaniza8on of work



35/52

Examples of Machine Age Thinking

Ancient roots

Aristotle (Physicsfire, earth, air, water, aether )Archimedes

BiologyStudy of cells and organs

Physics

Study of atoms

F. W. Taylor Scien8fic Management



36/52

Class Discussion Points

Your examples?

Strength and Weakness of Machine AgeThinking


h


37/52

The System Age Circa 1940s

Supplemen8ng the Machine Age thinking

Expansionism

All objects and events, and all experience of them as parts of largerwholes.

Stochas8c view of the systems. Synthe9c Thinking (Systems Thinking)

Instead of focusing on explaining the whole but taking it apart,synthe8c thinking focuses on explaining something in terms of its role

in the larger system.

The whole is not equal to the sum of its partssome8mes more,some8mes less.

Teleologically oriented

Systems have purposes More focuses on the human aspect of organiza8on design and

management.



38/52

Machine Age vs. Systems Age

Machine Age Thinking Systems Age Thinking

Reduc8onism Expansionism

Analy8cal thinking Synthe8c thinking

Mechaniza8on Teleologically Oriented

These two eras show continuous human inquiry tounderstand the world.

They are complementary, not contradictory. System Engineering is a more recent phenomenon. Understanding the history helps us to think critically.



39/52

INCOSE

The Interna8onal Council on Systems Engineering (INCOSE) is

a notforprofit membership organiza8on founded to develop

and disseminate the interdisciplinary principles and prac8ces

that enable the realiza8on of successful systems.

Mission: Share, promote and advance the best of systems

engineering from across the globe for the benefit of humanity

and the planet.

Vision: The world's authority on Systems Engineering.

hp://www.incose.org/

http://www.incose.org/http://www.incose.org/


40/52

Agenda





C L i Obj 8


41/52

Course Learning Objec8ves

This course intends to help you develop the capability of systems thinking by

introducing classical and advanced systems engineering theory, methods, and

tools. Aer taking this class, you should be able to:

Develop a systems engineering plan for a realis8c project. Judge the applicability of any proposed process, strategy, or methodology for

systems engineering using the fundamental concepts from disciplines such as

of probability, economics, and cogni8ve science.

Understand system engineers role and responsibili8es. Understand the roleof organiza8ons.

Apply systems engineering tools (e.g., requirements development andmanagement, robust design, Design Structure Matrix) to realis8c problems;

Recognize the value and limita8ons of modeling and simula8on. Formulate an effec8ve plan for gathering and using data. Know how to proac8vely design for and manage system lifecycle targets.



42/52

Qi Van Eikema Hommes June 8, 201044

Lecture 4

Stakeholder Analysis and

Requirements Defini8on

Lecture 2

Systems Engineering

As Human Ac8vity

Lecture 13

Design Verifica8on

and

Valida8on, Lifecycle

ManagementLecture 5 innova8on in

Systems Engineering

Lecture 6 Axioma8c

Design and DMDSMMethod

Lecture 8

Trade Space Explora8on

Concept Selec8on

Lecture 10 : Experiments

Lecture 11

Lecture 12:

: Robust Design I

Robust Design II

Course Layout

C i l


43/52

Course Materials

Textbooks: INCOSE Systems Engineering Handbook, V3.2.40 PrinciplesQBQ

Reference books:

Strongly recommended: Blanchard, B. S., andFabrycky, W. J., Systems Engineering and nalysis,

5th edi8on, Pren8ce Hall, 2010.


C P li i


44/52

Course Policies

Reading please be prepared for classdiscussions

Class sessions

2 sessions/week, 2 hours/sessionSession 3, 3 hours, project proposalSessions 19 and 20, 4 hours, final

presenta8ons.

Aendance and class par8cipa8onInstructor will randomly pick student names for

class discussion


Class Time Commitment


45/52

Class Time Commitment

Course is H 306 This is a 9 units class in a normal semester (14

weeks).

Summer is 10 weeks, which means this courserequires 12.6 hours of work per week.

12.6 hours = 4 hours in class + .6 hoursoutside

.6 hours include reading, homeworkassignments, and project work.


Grading


46/52

Grading Project (presenta8ons and reports):

Individual Project proposal (presenta8on and 1page) 10% Midterm (group presenta8on) 10% Final (group presenta8on) 20%

Homework Assignments 10% x 5

The first four are individual assignments 10% x 4 The fih is a group presenta8on 10%

Aendance and class par8cipa8on 10%

Each class unaended without instructors permissionreduces 1% of the grade

Please let the instructor know if you are unable to aendthe class.


Term Project


47/52

Term Project

The goal is to apply the systems engineeringmethods and tools to a topic that fits your interest /your industry.

Acceptable topic examples:

Design of a new system (technical, organiza8onal,enterprise level, etc.). The project must haveenough detail so that it can demonstrate the use

of the methods and tools taught in the class.

Indepth inves8ga8on of a successful or failedproject Choose a project that you have access to informa8on

and data.

J une 8, 2010 Qi Van Eikema Hommes49


48/52

Term Project Deliverables

Proposal (Session 3)

Individual students propose project topicsVoluntarily form teams of 35. Four

member teams are strongly encouraged.

Submit team forma8on report by Session 5. Midterm presenta8on (Session 9) Final presenta8on (Sessions 19 and 20)


k i


49/52

Homework Assignments

What if you were called to help NHSTA inves8gatethe Toyota sudden accelera8on safety recall?

Most of the homework assignments will be centered

around the ques8on: What could have been done to

prevent the problem?

Your study should not be focused only on Toyota,but automobiles in general.

More about the case study in a few slides.


Homework Requirements


50/52

q Homework is individualbased. Collabora8on is

encouraged, but work must be turned in byindividuals.

Acknowledge all help received.

Provide references to data and informa8on sources.


A d


51/52

Agenda





MIT OpenCourseWarehttp://ocw.mit.edu
http://ocw.mit.edu/http://ocw.mit.edu/http://ocw.mit.edu/


52/52

ESD.33 Systems Engineering

Summer 2010

For information about citing these materials or our Terms of Use, visit: http://ocw.mit.edu/terms.
http://ocw.mit.edu/termshttp://ocw.mit.edu/terms

Date post:	03-Apr-2018
Category:	Documents
Upload:	sunny-arora
View:	215 times
Download:	0 times

MITESD_33SUM10_lec01

Documents