Key Learning Objectives

0.  Introduction – Architectural Design Within Systems Engineering

• The business case for a systems approach to design
• Definition of terms
• Design interactive exercise – basic
• Systems engineering process overview – the football diagram
• Design within a systems engineering process model

1. Design-Related Principles of Engineering

• System views
• Workshop 1 – design-related principles

2. System Development Strategies

• The solution domain: key concepts, relationships, and work products
• Waterfall, incremental, evolutionary, spiral and agile development approaches
• Workshop 2 – solution development strategies for a product

3. Concepts of Architecture and Detailed Design – Physical and Logical

• Physical architecture (structural view) – basic concepts
• Logical architecture – basic concepts
• Logical architecture related to physical architecture
• Useful forms of logical representation – functional, state-based, mathematical, hybrid, … with examples
• Model-based design in practice – MBSE/MBA/MBD/MDA/MDD

4. Initial Physical Conceptualization

• The role of technology and innovation
• Architectural design driver requirements
• Workshop 3 – identification of architectural design driver requirements
• Techniques for stimulating innovation: brainstorming, TRIZ
• Perspiration engineering: configuration items
• Criteria for selecting configuration items
• Design complexity trade-off
• Relationship of CI definition to system integration
• Interactive exercise – a simple physical design
• Workshop 4 – physical conceptualization of solution
• Reconstitution (Aggregation)

5. Functional Design

• Functional analysis in design – how to do it
  
  • Functional analysis/architecture process
  • Item flow and control flow
  • Un-allocatable and allocatable functions
  • Pitfalls in defining functions
  • Common pitfalls in functional design
  • Interactive exercise – a simple functional design
  • Workshop 5 – physical and functional design, part A
  • Workshop 5 – physical and functional design, part B (optional)
  • Coupling, cohesion, connectivity
  • Failure Modes and Effects Analysis (FMEA)/Failure Modes, Effects and Criticality Analysis (FMECA) in design
  • Performance thread analysis
  • Allocation of functionality between hardware and software
• Fault Tree Analysis
• Event Tree Analysis
• Behavior modeling languages
• Other languages incorporating functional modeling: SysML, …
• Software tools supporting functional and physical design
• Pitfalls in functional design

6. State-Based Design

• State-based design – how to do it
  
  • Workshop 6 – a simple state-based design
  • Relationship to object orientation
• SysML, and alternative languages incorporating state-based modeling
• Software tools supporting state-based design
• Pitfalls in state-based design

7. Object Process Methodology (OPM)

• Background to OPM
• OPM description
• Software tools supporting OPM

8. Design Decision-Making and Optimization – Trade-Off Studies

• Designing for feasibility
• Designing for effectiveness: approach to design optimization
  
  • The role of MOEs and goals
  • The origin of a system effectiveness model
  • Designing for the company versus designing for the customer – handling common interest and conflict of interest
• Using a system effectiveness model
  
  • Taking account of risk relating to goals
  • Taking account of risk relating to satisfaction of requirements
  • Event-based uncertainty
  • Risk aversion
  • Exercise – using a system effectiveness model
  • Cost/capability, return on investment and like concepts
    
    • Iterative optimization of design – a very effective methodology
• Other techniques – Quality Function Deployment
• Software tools supporting design decision-making
• Some common pitfalls in design decision-making

9. Design For Six-Sigma (DFSS)

• What is Six-Sigma?
• DMADV (DFSS)

10. Return to Physical Design

• Functional to physical allocation
• Facilities, procedures, people, and other types of system element
• System elements not designated as configuration items
• Some common pitfalls in developing system physical architecture
• Use of architectural design driver requirements
• Adding the detail to the design
• Design creates requirements – the duality of requirements and design
• Interface engineering
• Interface requirements specifications versus interface design descriptions/ICDs
• The OSI 7-Layer Model and similar communication protocol models in interface engineering
• Relationship to system integration
• Evolution of interfaces in systems having levels of structure
• Some common pitfalls in interface engineering
• Major artifacts created in design

11. Engineering Specialty Integration (ESI)

• What makes an engineering specialty special?
• Common engineering specialties
• A generic approach to ESI
• Organizational issues of ESI
• Pitfalls, and specialty engineering examples

12. Concurrent (Simultaneous) Engineering

• System of interest – enabling system relationships
• Why concurrent (simultaneous) engineering
• Organizational aspects of implementation
• Process aspects of implementation
• Pitfalls in implementation

13. Summary and Key Points

• Action plan