ENG 203_8C

ENG 203_8C - ENG 203:SYSTEM ARCHITECTURE 01/20/12 1 System...

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

View Full Document Right Arrow Icon

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

View Full DocumentRight Arrow Icon

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

View Full DocumentRight Arrow Icon

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

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

Unformatted text preview: 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 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 ENG 203:SYSTEM ARCHITECTURE 01/20/12 3 Lecture 8C Applying the Methodology to a System of Systems John M. Borky 2009 - all rights reserved ENG 203:SYSTEM ARCHITECTURE Tailoring the Methodology John M. Borky 2009 - all rights reserved System Prototype System Build Integration & Test Capabilities Database Operational View Logical View Physical View Enterprise Requirements Enterprise Processes and Workflows Enterprise Data Models Enterprise Services Enterprise Domains/ Systems Enterprise Use Cases/ Mission Threads Enterprise Data Models Enterprise Services Participating Systems Allocated Functions Enterprise Processes/ Workflows Enterprise Logical Data Models Enterprise Functional Interfaces Timing, QoS, & Other Constraints Participating Systems Networks/Interconnects Service Level Agreements Enterprise Standards Profile Enterprise Physical Data Model 01/20/12 4 The architecture development flow is basically the same Participating systems become the subsystems of the Node or Enterprise Primary interconnects are now the networks and channels of the Enterprise Must account for enterprise-level behaviors and events ENG 203:SYSTEM ARCHITECTURE 01/20/12 5 Organization, Roles and Responsibilities John M. Borky 2009 - all rights reserved Matters are often complicated by the independence of participating systems priorities, schedules, technical standards, etc. The enterprise needs both program and management structures that can harmonize divergent agendas to meet overall goals the Chief Architect may be the Chief Diplomat, but there must be an issue resolution process Typical mechanisms include: Integrated Master Plan/Schedule (IMP/IMS) synchronize and coordinate individual system/program activities Enterprise-level architecture methodology to deal with trades, requirements allocation, interface control, process definition, user roles, and many others Enterprise board structure as a forum for collective decisions Enterprise integration and test (I&T) process as a framework for an orderly sequence of builds and releases ENG 203:SYSTEM ARCHITECTURE 01/20/12 6 Capabilities and Requirements John M. Borky 2009 - all rights reserved Key challenge is to capture and obtain stakeholder agreement on enterprise-level functions, processes and requirements...
View Full 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 / 17

ENG 203_8C - ENG 203:SYSTEM ARCHITECTURE 01/20/12 1 System...

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

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