MT1 OL - Systems Engineering MT1 OL I. Intro A. Systems =...

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

View Full Document Right Arrow Icon
Systems Engineering MT1 OL I. Intro A. Systems = collection of objects in one relation to another 1. Entities & Relationships a. Diamond = “is composed of” (decomposition into parts) b. Triangle = “is one of” (classification into types) c. Rectangle = entity – connected by a verb 2. Point of view: important – systems are perceived; different depending on POV 3. Function = purpose-directed activity or behavior; process=integration of functions to achieve higher-level goal 4. Functional Flow Block Diagram ( review diagram ) a. Boxes = functions b. Arrows = triggers c. “And” circles: control triggers (one thing causes another) 5. E-R diagram Format ( review diagram ) a. Box with two rows. First row = entity, Second = function 1.1, 1.2, etc. b. Boxes connected by a relationship with a verb B. Systems Engineering 1. Def: Applying principles to design of systems solutions to engineering problems…bridge gap from “cust’s text res” to disciplinary reqs that will define optimum solution to cust’s reqs. 2. Outputs: Description of a system (what it does, how it behaves, how it’s realized, tested, operated, disposed of) 3. Goals: Getting right design and getting design right 4. Emphasis: Requirements, Validation, Hierarchy, Integration C. Design Metaphors 1. Waterfall: Define, Design, Build, Test 2. Spiral: Determine objectives, ID and resolve risks, plan next iteration, develop and test 3. Divide and Conquer a. Define subsystems, define relationships, repeat for each subsystem b. Stop defining subsystem until a real component can be built/tested. c. Integrated/tested until working system is achieve & verification failure followed by design iteration d. Continuous Improvement Cycle: Plan, Do, Check, Act D. System Engineering Process a. The Gap: exits btwn value expressed in informal or natural human language and specs in terms of the parameters familiar to the many engr diciplines b. SE Process b.i. Inputs: natural language of reqs b.ii. Outputs: design specs b.iii. Define transformations between input/output using interdisciplinary/interacting parts (disciplinary subsystem designs) b.iv. Set of eval metrics (manuf/operation plans/sequences) c. Hierarchy in systems: # of lvls variers w/complexity of system (elements/sub- systems/components) E. OKK Perspective a. SE has 2 processes a.i. Technical process (engineering work supporting/specifying the product in all phases of life cycle)
Background image of page 1

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

View Full DocumentRight Arrow Icon
a.ii. Mgmt process (supports tech via resources/project planning, review/re-planning, change control) b. Core Technical Process b.i. Assess available info then: b.i.1. Define effective measures b.i.2. Create behavior model b.i.3. Create structure model b.ii. Preform tradeoff analysis. If no feasible solution, iterate to find a feasible solution. If feasible soln, create sequential build/test plan
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 11/29/2011 for the course SYSEN 5110 taught by Professor Peck during the Fall '11 term at Cornell University (Engineering School).

Page1 / 8

MT1 OL - Systems Engineering MT1 OL I. Intro A. Systems =...

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

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