ENG 203_1B

ENG 203_1B - 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 mborky@aol.com (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 1 – Course Introduction Lectures: 1A – Introduce instructor and course mechanics 1B – Discuss the nature and role of system architecture, and the skills of a system architect 1C – Define terms and fundamental concepts 1D – Some examples John M. Borky 2009 - all rights reserved
Background image of page 2
ENG 203:SYSTEM ARCHITECTURE 01/20/12 3 Lecture 1B – Nature and role of system architecture, skills of a system architect 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 What IS Architecture? 01/20/12 John M. Borky 2009 - all rights reserved 4 Architecture is the overarching description of a complex entity – “the highest level concept of a system in its environment [IEEE definition]” Typical Definitions: •The fundamental organization of a system embodied in its components, their relationships to each other and to the environment, and the principles guiding its design and evolution (ANSI-IEEE Standard 1471-2000) •The structure of components, their relationships, and the principles and guidelines governing their design and evolution over time (DoD Architecture Panel) Systems architecting is that part of systems engineering most concerned with purpose determination, concept formulation, structuring, and certification for use (M. W. Maier) Architecture is a discipline for managing complexity, especially when dealing with multiple technologies, organizations, and customer requirements Ultimately, architecture deals with three dimensions of a complex entity: Structure – how is the entity partitioned and organized; where do important interfaces occur? Behavior – how do individual sub-entities act and how do they collaborate to produce the overall behaviors that implement functionality required by users? Rules – what are the conventions (e.g., standards) that must be adhered to to achieve an operationally satisfactory solution? Architecture is fundamentally concerned with managing complexity
Background image of page 4
ENG 203:SYSTEM ARCHITECTURE What Problem Are We Trying to Solve? Perennial difficulties with information-intensive systems: Software that’s late, overrun, and fails to delivery expected capability Hardware that’s too expensive, hard to integrate, and hard to modify and upgrade Lack of interoperability within and among systems Limited ability to reuse existing and off-the-shelf products
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.

Page1 / 12

ENG 203_1B - 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