ENG 203_8D

ENG 203_8D - ENG 203:SYSTEM ARCHITECTURE System Engineering...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
ENG 203:SYSTEM ARCHITECTURE 01/20/12 1 System Engineering in an Acquisition Context John M. Borky 2009 - all rights reserved Engineering 203 System Architecture Dr. Mike Borky [email protected] (Cell) 505 453-0496 © John M. Borky 2009 – all rights reserved
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ENG 203:SYSTEM ARCHITECTURE 01/20/12 2 Session 8 – Architecting the Enterprise Lectures: 8A – Nature and Challenges of a System-of-Systems 8B – Networking Fundamentals 8C – Enterprise Architecture Methodology 8D – Issues and Concerns in Enterprise Architecture John M. Borky 2009 - all rights reserved
Background image of page 2
ENG 203:SYSTEM ARCHITECTURE 01/20/12 3 Lecture 8D – Additional Issues Associated with an SoS John M. Borky 2009 - all rights reserved
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ENG 203:SYSTEM ARCHITECTURE 01/20/12 4 Adaptive and Emergent Behavior John M. Borky 2009 - all rights reserved An SoS can reach levels of complexity where: High levels behaviors can occur that are not available with individual systems Some behaviors may not be predictable in advance – the beginnings of chaos Self-organization allows the enterprise to configure itself and select resources to perform tasks, depending on the situation Interfaces are more complex than the resources behind them Basic approaches to manage complexity in an SoS: Build a little, try a little – incrementally assemble the SoS and exercise it to determine its behaviors and responses at each stage, with provisions to correct or limit unacceptable behaviors before adding the next system(s) Modeling and simulation – build high fidelity simulations or emulations of systems, networks, operators (including human-in-the-loop simulation), and environments; explore the range of environments and behaviors Design for stability – incorporate generous margins, stress loose coupling among systems, and seek to establish stable operating points
Background image of page 4
ENG 203:SYSTEM ARCHITECTURE 01/20/12 5 Interoperability John M. Borky 2009 - all rights reserved An enterprise or SoS can only function if its constituent systems
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 01/20/2012 for the course ENGR 203 taught by Professor Borky during the Summer '10 term at UCLA.

Page1 / 12

ENG 203_8D - ENG 203:SYSTEM ARCHITECTURE System Engineering...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online