1. © McClureTech Inc 2003 1 System Engineering Applying Architectural Principles to Complex System Development

2. © McClureTech Inc 20032 Architect Role/Responsibility Homebuilding The architect speaks two languages to support the dialog between the homebuyer and the builder Lifestyle language with the homebuyers Lifestyle language with the homebuyers Plans/Designs/Specifications language with the builder Plans/Designs/Specifications language with the builder

3. © McClureTech Inc 20033 Architect Role/Responsibility Attorney Objectives/Desires language with client Objectives/Desires language with client Obligations, Terms and Conditions language with legal community Obligations, Terms and Conditions language with legal community

4. © McClureTech Inc 20034 Architect Role/Responsibility System Engineer Needs/expectations language with user/consumer Needs/expectations language with user/consumer Specifications language with engineering Specifications language with engineering

5. © McClureTech Inc 20035 Topics and Threads Engineering? System? System Engineering? Engineering? System? System Engineering? System Engineering Tools System Engineering Tools Structure in engineering endeavors Structure in engineering endeavors Program Management & System Engineering Program Management & System Engineering Why System Engineering Why System Engineering Example models Example models Implementing System Engineering Implementing System Engineering

6. © McClureTech Inc 20036 Simple Invention – Engineering? Solution of single consequence – not engineering

7. © McClureTech Inc 20037 Engineering A: the application of science and mathematics by which the properties of matter and the sources of energy in nature are made useful to people A: the application of science and mathematics by which the properties of matter and the sources of energy in nature are made useful to people B: the design and manufacture of complex products B: the design and manufacture of complex products Merriam-Webster [emphasis added]

8. © McClureTech Inc 20038 System An organized integrated whole made up of diverse but interrelated and interdependent parts Merriam-Webster

9. © McClureTech Inc 20039 Engineers Desire to create useful things – shared with the aforementioned inventor Desire to create useful things – shared with the aforementioned inventor Complex products – by definition Complex products – by definition

10. © McClureTech Inc 200310 Engineers and Complexity Complexity represents a burden and a fascination Complexity represents a burden and a fascination Fascination with complexity is an affliction Fascination with complexity is an affliction

11. © McClureTech Inc 200311 Complexity and Risk Complexity increases risk Complexity increases risk Risk potentially impacts usefulness Risk potentially impacts usefulness

12. © McClureTech Inc 200312 System Engineers – Mission Mitigate complexity (cannot eliminate) Mitigate complexity (cannot eliminate) Maximize usefulness Maximize usefulness Minimize risk Minimize risk

13. © McClureTech Inc 200313 System Engineers - Tools Structure, Structure, Structure! Structure, Structure, Structure! Clear problem statements – user language Clear problem statements – user language Architecture - Requirements decomposition Architecture - Requirements decomposition Functional allocation – Subsystem identification Functional allocation – Subsystem identification Interface specs – Detailed engineering requirements Interface specs – Detailed engineering requirements Error budgets and tolerances Error budgets and tolerances Analyses and modeling Analyses and modeling Process design Process design

14. © McClureTech Inc 200314 Structure – System Engineering Requirements Requirements Architectural definitions – subsystems Architectural definitions – subsystems Engineering specifications Engineering specifications Mechanical, electrical, thermal, optical Mechanical, electrical, thermal, optical Only at the subsystem boundaries!! Only at the subsystem boundaries!! i.e. Interface specifications Process Process Phases and milestones Phases and milestones

15. © McClureTech Inc 200315 Structure – an aside Mechanical systems – exact constraint Dr. Jack McLeod and Dr. Jack Morse Dr. Jack McLeod and Dr. Jack Morse Eastman Kodak Co. 1960s Eastman Kodak Co. 1960s 6 degrees of freedom – controlled appropriately 6 degrees of freedom – controlled appropriately

16. © McClureTech Inc 200316 System Engineering – Sweet Spot Degree of Structure (Project) Degree of Constraint (Developer)

17. © McClureTech Inc 200317 System Engineering – Relationship to Program Management System Engineering - Structure System Engineering - Structure Specifications Specifications Process Process Analyses Analyses Program Management - Discipline Program Management - Discipline Responsibility Responsibility Monitoring Monitoring Control Control

18. © McClureTech Inc 200318 System Engineering - Navigation System Engineering - Navigation Charting the course Program Management - Command Program Management - Command Sailing the ship System Engineering – Relationship to Program Management

19. © McClureTech Inc 200319 Heard in Troubled-Program Hallways We need more conference rooms!

20. © McClureTech Inc 200320 Heard in Troubled-Program Hallways We need more conference rooms. It is the responsibility of System Engineers to establish the vehicle for communications among the program participants. System Engineers accomplish this by providing structure in both product and process definition.

21. © McClureTech Inc 200321 Heard in Troubled-Program Hallways Are you working through the holiday? Good System Engineering manages risk, thereby relieving stress on schedule, cost, and performance.

22. © McClureTech Inc 200322 Heard in Troubled-Program Hallways What Tiger-team are you on? Good System Engineering obviates the need for the best people to salvage programs in later phases.

23. © McClureTech Inc 200323 System Engineering Models Waterfall (problematic) Waterfall (problematic) V-Diagram V-Diagram Waterfall with feedback Waterfall with feedback Easily understood Easily understood Architecture Based Development Architecture Based Development Manage to the interfaces Manage to the interfaces Easy technology insertion Easy technology insertion Model Based Development Model Based Development Applying math is cheaper than bending metal Applying math is cheaper than bending metal

24. 24 V-Diagram SE Model *Configuration controlled Knowledge of the system Requirements Documentation Requirements Traceability Design Documentation Test Definition Requirements Capture & Analysis System Analysis & Design HW/SW Design HW/SW Implementation & Unit Testing Module Integration & Test System Integration & Test System Acceptance & Deployment Knowledge Base* User Model Conceptual/Architectural System Model Implementation Model Test Scenarios System Modification [Various sources]

25. © McClureTech Inc 200325 Common Elements – all models Phases Phases Requirements Requirements Definition (Design) Definition (Design) Implementation Implementation Test Test Deployment Deployment Retirement Retirement Phase products Phase products Documents Documents Increasing detail Increasing detail Process definition Process definition Components Components The Product The Product

26. © McClureTech Inc 200326 Companion Activities Configuration management Configuration management Document control, versioning, release, etc. Document control, versioning, release, etc. Vault/librarian activity Vault/librarian activity Component compatibility/interchangeability Component compatibility/interchangeability Analyses Analyses Risk analysis/management Risk analysis/management -ilities (see next slide) -ilities (see next slide) Performance analyses/improvement Performance analyses/improvement Error budgeting Error budgeting Contingency planning Contingency planning

27. © McClureTech Inc 200327 Companion Activities, cont. Important Analyses – the -ilities Important Analyses – the -ilities Usability Usability Reliability Reliability Manufacturability Manufacturability Serviceability Serviceability Maintainability Maintainability Supportability Supportability …

28. © McClureTech Inc 200328 System Engineering – Effects Strong Architecture Strong Architecture Mitigates complexity Solid Requirements Statements Solid Requirements Statements Maximizes usefulness Robust Process Robust Process Minimizes risk

29. © McClureTech Inc 200329 McClure Precepts Requirements statements - User Language Requirements statements - User Language Best minds application – still an art Best minds application – still an art Conceptual models Conceptual models Technology selection Technology selection Architecture Architecture Discipline Discipline Stick to the Process!! Stick to the Process!! Steps may be postponed to a more expensive phase – but they cannot be eliminated! Steps may be postponed to a more expensive phase – but they cannot be eliminated! Assess and improve the process Assess and improve the process

30. © McClureTech Inc 200330 SE Implementation Establish executive sponsorship Establish executive sponsorship Pick an SE model Pick an SE model Adapt to your need Adapt to your need Acquire, develop, assign staff Acquire, develop, assign staff Select a pilot program Select a pilot program Monitor progress Monitor progress Roll-out to new/existing programs Roll-out to new/existing programs

31. © McClureTech Inc 200331 Contact McClureTech Inc 303 350-1152 Voice 303 350-1154 FAX http://www.mccluretech.com info@mccluretech.com