ENG 203_2B

ENG 203_2B - 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 2 – UML/SysML Methodology Lectures: 2A – Object Oriented System Engineering 2B – Methodology Overview – Operational, Logical and Physical Views 2C – Structure, Behavior and Data Modeling 2D –Introduction to Architecture Modeling in Rhapsody TM John M. Borky 2009 - all rights reserved
Background image of page 2
ENG 203:SYSTEM ARCHITECTURE 01/20/12 3 Lecture 2B – Overview of the Architecture- Centric OOSE Methodology 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 Why Do Modeling? Helps ensure a comprehensive, consistent and optimized architecture is defined and documented Creates executable objects from which behavior can be computed Creates unambiguous architecture representation – far more precise than words Facilitates dialog with system users, including the technically unsophisticated Provides traceability from performance requirements to system elements – allows “cost of function” or “cost as an independent variable” trades Supports effective system integration and test planning Supports clear definition of functions and system elements in each cycle of an evolutionary spiral development Operational Process Logical Physical Modeling Is the core method of architecture-centric OOSE
Background image of page 4
ENG 203:SYSTEM ARCHITECTURE Physical Prototype (e.g., System Integration Lab) Virtual Prototype – Modeling Primary path for interaction among Views 01/20/12 5 Basic Methodology John M. Borky 2009 - all rights reserved Whatever is known about customer needs/desires/constraints Captured in a requirements management tool Transform requirements into an architectural context Define system boundary and context, top-level partitioning Map requirements to Domains and Use Cases Begin discovery of both external and internal (Domain) services Develop functional system
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 / 14

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