ENG 203_5D

ENG 203_5D - 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 [email protected] (Cell) 505 453-0496 © John M. Borky 2009 – all rights reserved ENG 203:SYSTEM ARCHITECTURE 01/20/12 2 Session 5 – Physical View Lectures: • 5A – Products and Standards • 5B – Infrastructure and Integration • 5C – Completing the Physical View • 5D – Modeling with SysML John M. Borky 2009 - all rights reserved ENG 203:SYSTEM ARCHITECTURE 01/20/12 3 Lecture 5D – Using the Features of the System Modeling Language (SysML) John M. Borky 2009 - all rights reserved ENG 203:SYSTEM ARCHITECTURE SysML Profile of UML 2 (1) • Extends UML to deal more effectively with the needs of system engineers: – Requirements – modeling and mapping to model elements – System structure – expands Structured Classes with ports, flows, and other elements and semantics – Functional behavior – full power of activity modeling plus a new mechanisms for linking mathematics into behavior – Allocations – associate requirements, test conditions, behaviors, etc. – Basic testing – allocate test points to system elements – Basic trade studies during the specification and design phases of systems engineering • SysML is particularly useful when dealing with: – Rigorous treatment of requirements in the architecture context, including analysis and allocation to elements of the solution – Capture of analytical content such as algorithms and functions in the architecture – Complex hardware and software configurations where structural details are important – Attention to the details of physical structure, including not just computers and networks but things like power and cooling, controls and actuators – Accounting for information and physical item flows among model elements 01/20/12 4 John M. Borky 2009 - all rights reserved ENG 203:SYSTEM ARCHITECTURE 01/20/12 5 SysML Profile of UML 2 (2) John M. Borky 2009 - all rights reserved SysML UML UML4SysML Model Elements Not Used by SysML Common Elements Model Elements Added or Modified by SysML ENG 203:SYSTEM ARCHITECTURE SysML Profile of UML 2 (3) req [package] VehicleSpecifications [Requirements Diagram - Braking Requirements] Braking Subsystem Specification Vehicle System Specification VerifiedBy «interaction»MinimumStop pingDistance id: 102 text: The vehicle shall stop from 60 mph within 150 ft on a clean dry surface. «requirement» StoppingDistance SatisfiedBy «block»Anti-LockController id: 337 text: Braking subsystem shall prevent wheel lockup under all braking conditions. «requirement» Anti-LockPerformance «traceReqt» par [constraintBlock] StraightLineVehicleDynamics «constraint» Accelleration Equation [F = ma] «constraint» VelocityEquation [a = dv/dt] «constraint» DistanceEquation [v = dx/dt] «constraint» BrakingForce Equation [f = (tf*bf)*(1-tl)] tf bf tl f F m a a v v x «value»...
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 / 21

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