MT2 OL - Systems Engineering MT2 OL I. Functional Design A....

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

View Full Document Right Arrow Icon
Systems Engineering MT2 OL I. Functional Design A. Discovering Fctl Reqs a. Functional detailing a.i. Aka “functional decomp” – describes hi-lvl fct by means of lo-lvl fcts that working together can achieve hi-lvl fct a.ii. Informal ,intuitive, automatic activity. Basis for concept generation. Formalized for b. Functional abstraction [opposite of detail] b.i. generally o a fctn to include wider design possibilities (eg PENS – ink to paper -> transfer substance to paper > capture strokes > enable strokes in a display medium) b.ii. Abstraction allows for innovation; fresh start, enlarge solution space B. Diagrams/Tools a. Fctl Flo Block Diagram (FFBD): shows fcts that system is to perform & order; control is specified but flow of data is not. a.i. Shows syst fcts in order in which they are enabled/performed. Enabled via reference nodes before it; nodes at end = what functions enabled next. a.ii. Shows completion criterion for functions (eg exits for multi exit fct) a.iii. Template b. IDEF0: shows data flow but doesn’t show sequence/concurrency/control b.i. Template b.ii. Components b.ii.1. Function box w/function name (verb expressing system capability) b.ii.2. Unique identifier (A0 default) b.ii.3. Inputs (material, energy, data; arrows w/nouns enter left) b.ii.4. Outputs (material, energy, info; arrows w/nouns exit right) b.ii.5. Controls/Constraints (info input to function that influences activity ie targets, user decisions; arrows w/nouns enter top) b.ii.6. Resources/Mech (entity used by function but not consumed=resource like maint crew; subsidiary fct not analyzed
Background image of page 1

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

View Full DocumentRight Arrow Icon
further=mechanism like algo; arrows w/nouns enter bottom) b.iii. Pages b.iii.1. Series of pages describing fctl detailing of capability requirement. b.iii.2. First pg is A-0 with single function A0 (capability req). Next pges present detail of single fct from earlier page (arranged in waterfall w/<=6 fcts/pg) b.iii.3. Pages contain diagram/title w/text descript. Must ID model’s POV in text/title of page A-0 II. Structural Design A. Use Case Diagrams a. Show human-initiated functionality – doesn’t provide all fcts needed in interface mgmt. or show scenario def/analysis b. Provides common understanding among cust/user + engrs c. Actors : Stick figures (don’t interact), connect actors to use cases d. Extends : some use cases extendd another (dashed line w/<<extend>>) e. Includes : two+ use cases include flow of another use case (dashed line w/<<include>>) B. Use Case to Functions a. Start w/context diagram (ER diagram) to provide initial description of context b. Brainstorm then prioritize use cases of how likely to provide fctl reqs c. Describe use-case behaviors – use perspective of actors (need initiating event + fctl req + terminating event) d. All this leads to an expanded context diagram. Then capture reqs from use-case behaviors e. Repeat for secondary use cases and further evolve context diagram. C. Process for Structural Design
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.

Page1 / 8

MT2 OL - Systems Engineering MT2 OL I. Functional Design A....

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