MITESD 33SUM10 Lec01

ESD.
33SystemsEngineering
Lecture1
CourseIntroduc8on
Instructors:
Dr.QiVanEikemaHommes
Mr.PatHale
Mr.DavidErickson
TeachingAssistants:
EllenCzaika
IpshitaDeepak

Agenda
WelcomeandIntroduc8onofTeachingSta
Whyarewehere?
WhatareSystems?
WhatisSystemsEngineering?
WhydowestudySystemsEngineering?
CourseScheduleandLogis8cs
Qi Van Eikema Hommes J une 8, 2010 2
Dr.QiVanEikemaHommes
ESDResearchAssociateandLecturer
8yearsofworkexperiencesinautomo8ve
companies(FordandGM)
SeniorResearchScien8statGMR&D
PowertrainSystemsEngineeratFord
Qi Van Eikema Hommes
Ph.D. and M.S. in
Mechanical Engineering
B.S. in Mechanical
Engineering
J une 8, 2010 3
MIT
University of
Kentucky
Dr.PatHale
SDMDirector,ESDSeniorLecturer
Militaryexperience:
-20yearsinU.S.Navy:submarines
Industryexperience:
-DraperLabs(Director,SystemsEngineering)
-O8sElevator(rstDirector,Systems&
ControlsEngineering)
PastINCOSEpresident
J une 8, 2010 Qi Van Eikema Hommes 4
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
Aboutme:
Productdesigner/manager,systemsengineer,
mobiletechenthusiast,amother,vocalar8standa
secondyearSDMstudent

Aboutme:
SDM08
Formermanagerofsystemsengineeringteam
Ethnographer
Athlete(numeroussports:rowing,yoga,skiing/snowboarding,
hiking,biking,sailing,surng,etc.)

WhyAreWeinThisClass?
My SLory on SysLems Lnglneerlng
Qi Van Eikema Hommes June 8, 2010
9
Image by MIT OpenCourseWare.
IsThisaSystemandWhy?
http://science.howstuffworks.com/power.htm/printable
Power grid image removed due to copyright restrictions.
Image can be found at HowStuffWorks.com.
Name
Headquarters
Security
Department
Name
Strategy
Department
Name
Finance
Department
Name
IT Department
Name
Personnel
Department
Name
Legal
Department
Name
Public Relations
Department
Name
Marketing
Department
Name
Sales
Department
Name
Research
Department
Name
Logistics
Department
Name
Production
Name
Administration
Name
Corporate Name
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
WhatTypesofSystemsHaveYou
Workedon?
Whydoyoucallthemsystems?
Deni8onofSystems
Acombina8onofinterac8ngelements
organizedtoachieveonemorestated
purposes.
Anintegratedsetofelements,subsystems,or
assembliesthataccomplishadened
objec8ve.Theseelementsincludeproducts
(hardware,sofware,rmware),processes,
people,informa8on,techniques,facili8es,
services,andothersupportelement.
Source:INCOSESEHandbook,V3.2
Characteris8csofSystems
Interac8on
Hierarchical
Emergent
Dynamic
Interdisciplinary
DigitalPhotography
Inkjet Photo Printer
PictBridge Compatible
Printers (with Direct Print)
PC Compatible
Computer
CF/SD Cards
USB Cable
USB Cable
USB Cable
(FireWire IFC-200D4/
D44 or IFC-450D4/D44
cable for EOS 1Ds Mark II
and EOS 1D Mark II)
Interface Cable
IFC-300PCU/IFC-400PCU
(EOS-1Ds Mark II, 1D Mark II,
20D, Digital Rebel XT, Digital Rebel)
CF/SD Card
Reader
PC Card Adapter
EOS Digital Cameras
(with Direct Print)
EOS-1Ds Mark II
EOS-1D Mark II
EOS-20D
EOS
Digital Rebel
EOS
Digital Rebel XT
Computers
Macintosh
Computer
Compact Photo Printer
SystemofSystems
Largescaleinterdisciplinaryproblemsinvolving
mul8ple,heterogeneous,distributedsystems.
Systemelementsoperateindependently.
Systemelementshavedierentlifecycles.
TheiniAalrequirementsarelikelytobeambiguous.
Complexityisamajorissue.
Managementcanovershadowengineering.
Fuzzyboundariescauseconfusion.
SoSengineeringisnevernished.
Source:INCOSESEHandbookV3.2
ThisClassFocus
Agenda
Whyarewehere?
WhatareSystems?
Systemsengineeringisadisciplinethatconcentratesonthe
designandapplica8onofthewhole(system)asdis8nctfrom
theparts.Itinvolveslookingataprobleminitsen8rety,taking
intoaccountallthefacetsandallthevariablesandrela8ng
thesocialtothetechnicalaspect.
Systemsengineeringisanitera8veprocessoftopdown
synthesis,development,andopera8onofarealworldsystem
thatsa8ses,inanearop8malmanner,thefullrangeof
requirementsforthesystem.
INCOSESEHandbookV3.2
Systemsengineeringisaninterdisciplinaryapproachand
meanstoenabletherealiza8onofsuccessfulsystems.It
focusesondeningcustomerneedsandrequired
func8onalityearlyinthedevelopmentcycle,documen8ng
requirements,andthenproceedingwithdesignsynthesisand
systemvalida8onwhileconsideringthecompleteproblem:
opera8ons,costandschedule,performance,trainingand
support,test,manufacturing,anddisposal.SEconsidersboth
thebusinessandthetechnicalneedsofallcustomerswiththe
goalofprovidingaqualityproductthatmeetstheuserneeds.
INCOSESEHandbookV3.2
Applica8onDomainsofSystems
Engineering
Aerospace
UrbanInfrastructure
Communica8onssystems
Dataandinforma8onsystems
Healthcaresystems
Electricpowersystems
Produc8on/construc8onsystems
Wastedisposalsystems
Transporta8onsystems
Financialsystems
Educa8onsystems

Source: Blanchard, Fabrycky, Systems Engineering and Analysis, 5
th
ed.
WaterfallProcessModel
Introduced by Royce
in 1970, initially for
software
development.
th
ed.
Requirements
Analysis
Specifications
Design
Implementation
Test
Maintenance
F
E
E
D
B
A
C
K
SpiralProcessModel
Boehm,1986.
Adaptedfrom
Waterfallmodel
Itera8ve
Prototyping
th
ed.
Need
S
y
s
te
m
R
e
q
u
ir
e
m
e
n
ts
D
e
te
r
m
in
a
tio
n
F
u
n
c
tio
n
D
e
f
in
itio
n
D
e
ta
il
R
e
q
u
ir
e
m
e
n
ts
F
e
a
s
i
b
i
l
i
t
y
A
n
a
l
y
s
i
s
R
e
q
u
i
r
e
m
e
n
t
s
A
l
l
o
c
a
t
i
o
n
C
o
m
p
o
n
e
n
t
D
e
s
i
g
n
C
o
m
p
o
n
e
n
t
s
System
Analysis
S
y
s
t
e
m
S
p
e
c
i
f
i
c
a
t
i
o
n
S
e
l
e
c
t
D
e
s
i
g
n
E
q
u
i
p
m
e
n
t
D
e
f
i
n
i
t
i
o
n
Trade-Off
Studies
Evaluation and
Optimization
C
onceptual R
eview
T
est and
R
eview
Form
al D
esign R
eview
O
p
e
r
a
t
i
o
n
a
l
P
r
o
t
o
t
y
p
e
S
y
n
t
h
e
s
i
s
S
y
s
t
e
m
P
r
o
t
o
t
y
p
e
Im
plem
entation
Purchase, Operate
& Maintain
Disposal
Vehicle
Verification
Production
System
Verification
Vehicle Level I nputs
Purchase / Owner / Operator
Regulatory (FMVSS, EPA, ...)
Corporate (WCR, ABS, Manuf, ...)
Vehicle Attributes
Vehicle SystemSpecification - VDS
Vehicle Level Requirements
System&
SubsystemDesign Specification- SDS
System / Subsystem Level
Component Design Specification - CDS
Part / Component Fabrication /
Verification
Part / Component Design
Customer
Satisfaction
Corporate
Knowledge
Generic VDS &
SDS
Competitive
Benchmark
Data
Reusability
Constraints &
Data
Product
Knowledge
Manufacturing
Knowledge &
Reusability
Technology
Warranty Data
Models
Highly Iterative Mostly Serial
KO SI SC PA PR J 1
Purchase, Operate
& Maintain
Disposal
Vehicle
Verification
System
Verification
Vehicle Level I nputs
Purchase / Owner / Operator
Regulatory (FMVSS, EPA, ...)
Corporate (WCR, ABS, Manuf, ...)
Vehicle Attributes
Vehicle SystemSpecification - VDS
Vehicle Level Requirements
System&
SubsystemDesign Specification- SDS
System / Subsystem Level
Component Design Specification - CDS
Part / Component Fabrication /
Verification
Customer
Satisfaction
Customer
Musts / Wants
Corporate
Knowledge
Generic VDS &
SDS
Competitive
Benchmark
Data
Reusability
Constraints &
Data
Product
Knowledge
Manufacturing
Knowledge &
Reusability
Technology
Warranty Data
Models
Highly Iterative Mostly Serial
KO SI SC PA PR J 1
Requirements
Cascades
Requirements
Cascade
Requirements
Cascade
Feasibility
Feedback
Feasibility
Feedback
Feasibility
Feedback
Customer
Requirements
DVM / DVP
DVM / DVP
Customer Focus
Customer Experience & Feedback
System Engineering Implemented in FPDS
Production
INCOSEVEEModel
IsThereaWinner?
Itisobservedthatpreferencesexpressedby
individualsandgroupsforoneofthesystem
modelsissubjec8ve.
Researchisneededtoseewhichmodelts
whatsitua8onbemer.
ClassDiscussion:
Whatarecommonamongtheseprocesses?
IsSystemsEngineeringthesamefromProduct
Development?
SystemsEngineeringvs.ProductDevelopment
Planning
Concept
Development
System-Level
Design
Detail
Design
Testing and
Refinement
Production
Ramp-Up
Mission
Approval
Concept
Review
System Spec
Review
Critical Design
Review
Production
Approval
Product Development Process (Ulrich and Eppinger)
J une 8, 2010
Purchase, Operate
& Maintain
Disposal
Vehicle
Verification
Production
System
Verification
VehicleLevel I nputs
Purchase/ Owner / Operator
Regulatory(FMVSS, EPA, ...)
Corporate(WCR, ABS, Manuf, ...)
VehicleAttributes
VehicleSystemSpecification- VDS
VehicleLevel Requirements
System&
SubsystemDesignSpecification- SDS
System/ SubsystemLevel
Component DesignSpecification- CDS
Part / Component Fabrication/
Verification
Customer
Satisfaction
Corporate
Knowledge
GenericVDS&
SDS
Competitive
Benchmark
Data
Reusability
Constraints&
Data
Product
Knowledge
Manufacturing
Knowledge&
Reusability
Technology
WarrantyData
Models
HighlyIterative MostlySerial
KO SI SC PA PR J 1
Purchase, Operate
& Maintain
Disposal
Vehicle
Verification
System
Verification
VehicleLevel I nputs
Purchase/ Owner / Operator
Regulatory(FMVSS, EPA, ...)
Corporate(WCR, ABS, Manuf, ...)
VehicleAttributes
VehicleSystemSpecification- VDS
VehicleLevel Requirements
System&
SubsystemDesignSpecification- SDS
System/ SubsystemLevel
Component DesignSpecification- CDS
Part / Component Fabrication/
Verification
Customer
Satisfaction
Customer
Musts/ Wants
Corporate
Knowledge
GenericVDS&
SDS
Competitive
Benchmark
Data
Reusability
Constraints&
Data
Product
Knowledge
Manufacturing
Knowledge&
Reusability
Technology
WarrantyData
Models
HighlyIterative MostlySerial
KO SI SC PA PR J 1
Requirements
Cascades
Requirements
Cascade
Requirements
Cascade
Feasibility
Feedback
Feasibility
Feedback
Feasibility
Feedback
Customer
Requirements
DVM / DVP
DVM / DVP
Customer Focus
Customer Experience& Feedback
System Engineering Implemented in FPDS
Production
Agenda
Whyarewehere?
WhatareSystems?

TheValueofSystemsEngineering
TheValueofSystemsEngineering
Systemsengineeringeortsreducecostand
scheduleoverrun.
Classdiscussion:Why?Thinkbackaboutthe
characteris8csofsystems.
Interac8on
Hierarchical
Emergence
Dynamic
Interdisciplinary
HistoryofSystemsEngineering
TheMachine
Age
1940s
TheSystems
Age

TheMachineAge
Reduc9onismEverythingcanbereduced,decomposed,or
disassembledtosimpleindivisibleparts.
Analy9calwayofthinking
Takeapartwhatistobeexplained
Explainthesmallerparts.
Thewholeisthesumofitsparts.
Mechanism
Causeandeect,determinis8cthinking
ClosedSystemThinkingignoretheenvironmenta
phenomenonisin.
Mechaniza9on
Industrialrevolu8on(1819
th
century)
Machinesubs8tutepeopleforphysicalwork
Dehumaniza8onofwork
ExamplesofMachineAgeThinking
Ancientroots
Aristotle(Physicsre,earth,air,water,aether)
Archimedes
Biology
Studyofcellsandorgans
Physics
Studyofatoms
F.W.TaylorScien8cManagement
ClassDiscussionPoints
Yourexamples?
StrengthandWeaknessofMachineAge
Thinking
TheSystemAge
Circa1940s
Supplemen8ngtheMachineAgethinking
Expansionism
Allobjectsandevents,andallexperienceofthemaspartsoflarger
wholes.
Stochas8cviewofthesystems.
Synthe9cThinking(SystemsThinking)
Insteadoffocusingonexplainingthewholebuttakingitapart,
synthe8cthinkingfocusesonexplainingsomethingintermsofitsrole
inthelargersystem.
Thewholeisnotequaltothesumofitspartssome8mesmore,
some8mesless.
Teleologicallyoriented
Systemshavepurposes
Morefocusesonthehumanaspectoforganiza8ondesignand
management.
MachineAgevs.SystemsAge
MachineAgeThinking SystemsAgeThinking
Reduc8onism Expansionism
Analy8calthinking Synthe8cthinking
Mechaniza8on TeleologicallyOriented
These two eras show continuous human inquiry to
understand the world.
They are complementary, not contradictory.
System Engineering is a more recent phenomenon.
Understanding the history helps us to think critically.
INCOSE
TheInterna8onalCouncilonSystemsEngineering(INCOSE)is
anotforprotmembershiporganiza8onfoundedtodevelop
anddisseminatetheinterdisciplinaryprinciplesandprac8ces
thatenabletherealiza8onofsuccessfulsystems.
Mission:Share,promoteandadvancethebestofsystems
engineeringfromacrosstheglobeforthebenetofhumanity
andtheplanet.
Vision:Theworld'sauthorityonSystemsEngineering.
hmp://www.incose.org/
Agenda
Whyarewehere?
WhatareSystems?

CourseLearningObjec8ves
Thiscourseintendstohelpyoudevelopthecapabilityofsystemsthinkingby
introducingclassicalandadvancedsystemsengineeringtheory,methods,and
tools.Afertakingthisclass,youshouldbeableto:
Developasystemsengineeringplanforarealis8cproject.
Judgetheapplicabilityofanyproposedprocess,strategy,ormethodologyfor
systemsengineeringusingthefundamentalconceptsfromdisciplinessuchas
ofprobability,economics,andcogni8vescience.
Understandsystemengineersroleandresponsibili8es.Understandtherole
oforganiza8ons.
Applysystemsengineeringtools(e.g.,requirementsdevelopmentand
management,robustdesign,DesignStructureMatrix)torealis8cproblems;
Recognizethevalueandlimita8onsofmodelingandsimula8on.
Formulateaneec8veplanforgatheringandusingdata.
Knowhowtoproac8velydesignforandmanagesystemlifecycletargets.
CM and ulSS

Qi Van Eikema Hommes June 8, 2010
44
Lecture4
StakeholderAnalysisand
RequirementsDeni8on
Lecture2
SystemsEngineering
AsHumanAc8vity
Lecture13
DesignVerica8on
and
Valida8on,Lifecycle
Management
Lecture5 innova8onin
SystemsEngineering
Lecture6
Axioma8c
DesignandDMDSM
Method
Lecture8
TradeSpaceExplora8on
ConceptSelec8on
Lecture10
:Experiments
Lecture11
Lecture12:
:RobustDesignI
RobustDesignII
CourseLayout
CourseMaterials
Textbooks:
INCOSESystemsEngineeringHandbook,V3.2.
40Principles
QBQ
Referencebooks:
Stronglyrecommended:Blanchard,B.S.,and
Fabrycky,W.J.,SystemsEngineeringandAnalysis,
5
th
edi8on,Pren8ceHall,2010.
CoursePolicies
Readingpleasebepreparedforclass
discussions
Classsessions
2 sessions/week, 2 hours/session
Session 3,3 hours,projectproposal
Sessions 19 and 20,4 hours,nal
presenta8ons.
Amendanceandclasspar8cipa8on
Instructorwillrandomlypickstudentnamesfor
classdiscussion
ClassTimeCommitment
CourseisH306
Thisisa9unitsclassinanormalsemester(14
weeks).
Summeris10weeks,whichmeansthiscourse
requires12.6hoursofworkperweek.
12.6hours=4hoursinclass+8.6hours
outside
8.6hoursincludereading,homework
assignments,andprojectwork.
Grading
Project(presenta8onsandreports):
IndividualProjectproposal(presenta8onand1page)10%
Midterm(grouppresenta8on)10%
Final(grouppresenta8on)20%
HomeworkAssignments10%x5
Therstfourareindividualassignments10%x4
Thefhisagrouppresenta8on10%
Amendanceandclasspar8cipa8on10%
Eachclassunamendedwithoutinstructorspermission
reduces1%ofthegrade
Pleaselettheinstructorknowifyouareunabletoamend
theclass.
TermProject
Thegoalistoapplythesystemsengineering
methodsandtoolstoatopicthattsyourinterest/
yourindustry.
Acceptabletopicexamples:
Designofanewsystem(technical,organiza8onal,
enterpriselevel,etc.).Theprojectmusthave
enoughdetailsothatitcandemonstratetheuse
ofthemethodsandtoolstaughtintheclass.
Indepthinves8ga8onofasuccessfulorfailed
project
Chooseaprojectthatyouhaveaccesstoinforma8on
anddata.
TermProjectDeliverables
Proposal(Session 3)
Individualstudentsproposeprojecttopics
Voluntarilyformteamsof35.Four
memberteamsarestronglyencouraged.
Submitteamforma8onreportby Session 5.
Midtermpresenta8on(Session 9)
Finalpresenta8on(Sessions 19 and 20)
HomeworkAssignments
WhatifyouwerecalledtohelpNHSTAinves8gate
theToyotasuddenaccelera8onsafetyrecall?
Mostofthehomeworkassignmentswillbecentered
aroundtheques8on:Whatcouldhavebeendoneto
preventtheproblem?
YourstudyshouldnotbefocusedonlyonToyota,
butautomobilesingeneral.
Moreaboutthecasestudyinafewslides.
HomeworkRequirements
Homeworkisindividualbased.Collabora8onis
encouraged,butworkmustbeturnedinby
individuals.
Acknowledgeallhelpreceived.
Providereferencestodataandinforma8onsources.
Agenda
Whyarewehere?
WhatareSystems?

MIT OpenCourseWare
http://ocw.mit.edu
ESD.33 Systems Engineering
Summer 2010
For information about citing these materials or our Terms of Use, visit: http://ocw.mit.edu/terms.

MITESD 33SUM10 Lec01

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

MITESD 33SUM10 Lec01

Hochgeladen von

Copyright:

Verfügbare Formate

ESD.

J une 8, 2010 Qi Van Eikema Hommes 6

J une 8, 2010 Qi Van Eikema Hommes 7

J une 8, 2010 Qi Van Eikema Hommes 30

J une 8, 2010 Qi Van Eikema Hommes 42

J une 8, 2010 Qi Van Eikema Hommes 53

Das könnte Ihnen auch gefallen