ENG 203_3C

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

Info iconThis preview shows pages 1–6. 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 3 Operational View Lectures: 3A Requirements and Context 3B Structural Perspective 3C Behavioral Perspective 3D Data and Services Perspectives John M. Borky 2009 - all rights reserved ENG 203:SYSTEM ARCHITECTURE 01/20/12 3 Lecture 3C Creating the Artifacts of the Behavioral Perspective John M. Borky 2009 - all rights reserved ENG 203:SYSTEM ARCHITECTURE 01/20/12 4 Behavior in the Operational View John M. Borky 2009 - all rights reserved Structure and Behavior are complementary and should be worked together Behavioral Diagrams are the natural counterpart in the architecture of Functional Requirements: Every FR must have one or more associated behaviors that satisfy it Behaviors can be composed into Threads that represent complete sequences that meet system operational objectives A complete set of behaviors is the architectural equivalent of a CONOPS Structure and Behavior come together in the OV as the first rigorous confirmation that a valid architecture baseline has been established Start with Use Cases, develop Activity Diagrams, and perhaps others, to model and demonstrate how they work ENG 203:SYSTEM ARCHITECTURE 01/20/12 5 Use Case Diagram Format John M. Borky 2009 - all rights reserved Primary Use Cases capture the major areas of system performance can be linked to the top level of the Requirements Database typically 6-12 Decompose using <<include>> dependencies to a level appropriate for activity modeling: Usually 1, sometimes 2, levels of Use Case decomposition Can also indicate subordinate Use Cases occurring in multiple primary Use Cases Show optional behaviors using...
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 / 12

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

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