Date post: | 13-Jan-2016 |
Category: |
Documents |
Upload: | clara-morton |
View: | 215 times |
Download: | 0 times |
Colin A. White | Chief Technology Officer | Enterprise Architectwww.colinwhite.net | [email protected] | Dec 08
Thesecond guide to
30Systems Engineering
00:00
Q: What IS Systems Engineering?
00:02
Q: What IS Systems Engineering?
A: there is no universally accepted definition…
00:04
… but generally accepted to mean
“ A multi-disciplinary approach to building BIG complex things”
00:06
A prescriptive,
method-orientedway to
manage complexity
00:08
The Systems Engineering Lifecycle uses rigorous, structured processes
00:10
It has many similarities to theProject Management Lifecycle and PMBOK processes.
00:12
Systems Engineering includes factors like
cost and risk management
00:04
Specific techniques and methods vary between industries
(e.g. UML, IDEF0, DFD etc)
00:16
Rooted in the 1960s approaches to engineering… but around since the 1940s.
00:18
Used widely in Aerospace,Civil Engineering and
Federal Agencies(particularly NASA and DoD)
00:20
… and also popular with academic institutions00:22
considered by private industry
to be ‘old fashioned’ and ‘too linear’
and not widely understood.
00:24
The Systems Engineering lifecycle is very requirements oriented…
00:26
… and generally
incompatible with highly iterative, discovery oriented approaches
like Agile development and R&D.
00:28
Main professional body for systems engineers is
INCOSE founded in 1990.
www.incose.org
00:30
Colin A. White | Chief Technology Officer | Enterprise Architectwww.colinwhite.net | [email protected] | Dec 08
For further discussion, contact me.
Systems
Engineer