Presentation is loading. Please wait.

Presentation is loading. Please wait.

H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 1 Overview of Systems Engineering Fundamentals - Model-based Systems Engineering - Minneapolis.

Similar presentations


Presentation on theme: "H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 1 Overview of Systems Engineering Fundamentals - Model-based Systems Engineering - Minneapolis."— Presentation transcript:

1

2 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 1 Overview of Systems Engineering Fundamentals - Model-based Systems Engineering - Minneapolis I-Logix Inc. 3 Riverside Drive Andover MA USA tel: fax: Hans-Peter Hoffmann, Ph.D. Director and Chief Methodologist for Systems Design Systems & MicroController Division

3 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 2 1. Process Overview: Model-based System Development The V Development Process Requirements Capture (Use Cases) Systems Analysis and Architectural Design Transition to SW Design 2. Modeling Languages 3. Model-based Verification/Validation 4. Documentation in a Model-based Development Model-based Systems Engineering

4 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 3 Test Engineers System Integration & Test System Acceptance Shortcomings in System Developments The Throw-it-over-the-Fence Process Software Engineers Electrical Engineers Mechanical Engineers HW/SW Design HW/SW Implementation Module Integration & Test System Engineers Systems Analysis & Design Requirements- Analysis Costs of Design Changes Time Copyright I-Logix

5 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 4 Improving the Development Process: Concurrent Engineering System Engineers Test Engineers Mechanical Engineers Software Engineers Electrical Engineers System Engineers Test Engineers Electrical Engineers Software Engineers Mechanical Engineers System Integration & Test System Acceptance HW/SW Design HW/SW Implementation Module Integration & Test Systems Analysis & Design Requirements- Analysis Copyright I-Logix

6 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 5 Use Case Models System Acceptance System Integration & Test Module Integration & Test System Modification Model/Scenario-based System Development Test Scenarios Knowledge Base * * Configuration controlled Knowledge that is increasing in Understanding until Completion of the System: Requirements Documentation Requirements Traceability Model Data/Parameters Test Definition/Vectors Copyright I-Logix Requirements Analysis HW / SW Implementation & Unit Test HW / SW Design Systems Analysis & Design System- / Performance- Model Implementation Model The iterative Process (Micro-Cycles) Iterative Prototype Implementation Design Analysis V&V

7 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 6 Requirements Capture Basic tools for requirements capture are Use Cases and Scenarios A Use Case describes a specific usage (operational thread) of a system. It specifies the behavior as perceived by the user(s) and the message flow between the user(s) and the use case. It does not reveal the systems internal structure (black-box view) A Scenario is a specific path through a Use Case. System Acceptance System Integration & Test Module Integration & Test T E S T / P A R A M E T E R - D A T A B A S E HW / SW Implementation & Unit Test HW / SW Design Systems Analysis & Design Requirements Analysis Copyright I-Logix

8 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 7 Languages for Requirements Capture System Acceptance System Integration & Test Module Integration & Test T E S T / P A R A M E T E R - D A T A B A S E HW / SW Implementation & Unit Test HW / SW Design Systems Analysis & Design Requirements Analysis Copyright I-Logix Use Case Diagrams Sequence Diagrams capturing a specific use case scenario Statecharts capturing all possible use case scenarios Functional / Non-functional Requirements

9 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 8 Requirements Capture (Use Case Diagram) Example: Materials Handling System

10 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 9 Requirements Capture (Sequence Diagram) Example: Materials Handling System

11 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 10 Copyright I-Logix Requirements Analysis Requirements captured in use cases and respective scenarios may be incomplete, ambiguous or even wrong. Use cases may be translated into executable functional models (Executable Use Cases) which then are validated through Simulation with stimuli derived from respective use case scenarios (Sequence Diagrams / Statechart) and Formal Verification Analysis System Acceptance System Integration & Test Module Integration & Test T E S T / P A R A M E T E R - D A T A B A S E HW / SW Implementation & Unit Test HW / SW Design Systems Analysis & Design Requirements Analysis

12 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 11 Use Case 1: Fuel XFR and CG-Control Use Case Scenarios: Normal Operation: - Center to Feed Tank Transfer - Forward Transfers from Trim Tanks - Aft Transfers to Trim Tank Operations with Failures: - Valves failed shut - Valves failed open - Pump Failures Use Case 3: Defueling Use Case 2: Fueling Requirements Analysis Capturing Requirements via Use Cases Example: Aircraft Fuel-/Defuel System System Acceptance System Integration & Test Module Integration & Test T E S T / P A R A M E T E R - D A T A B A S E HW / SW Implementation & Unit Test HW / SW Design Systems Analysis & Design Requirements Analysis Copyright I-Logix

13 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 12 Generic Activity When the Trim Tank contains fuel and the aircraft is not in refuel or defuel mode then both Trim Tank Transfer Pumps shall be commanded ON otherwise they shall be commanded OFF. Copyright I-Logix Validation of Requirements through Executable Use Case Model USE Case: XFR_AND_CG_CONTROL (Statemate)

14 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 13 Validation of Requirements through Executable Use Case Model USE Case: XFR_AND_CG_CONTROL – Graphical User Interface (Statemate)

15 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 14 Benefits from Requirements Modeling Manage complexity by focusing on specific intended operations Understand requirements relationship Generate Derived Requirements Perform preliminary validation of requirements, e.g. Eliminate ambiguities through model execution System Acceptance System Integration & Test Module Integration & Test T E S T / P A R A M E T E R - D A T A B A S E HW / SW Implementation & Unit Test HW / SW Design Systems Analysis & Design Requirements Analysis Copyright I-Logix

16 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 15 System Acceptance System Integration & Test Module Integration & Test Requirements Analysis Use Case Models System Modification System- / Performance- Model Test Scenarios Model/Scenario-based System Development HW / SW Implementation & Unit Test HW / SW Design Systems Analysis & Design Implementation Model Knowledge Base Test Scenarios Validated Requirements incl. executable Use Case Prototypes From Requirements Analysis to Systems Analysis & Design Copyright I-Logix

17 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 16 V&V Cycle Conceptual Model: Functional Decomposition down to the Hierarchy Level where related System States are captured ( Level 3) System Functional Design if System Architecture tbd HW Design & BuildSW Design & Implementation Requirements V&V Cycle incl. RAPID PROTOTYPING V&V Cycle Subsystem Design * HW/SW Partitioning Subsystem Analysis of HW/SW Collaboration Definition of Subsystem Interfaces V&V Cycle Use Case Scenarios Requirements Capture and V&V through executable Use Case Models Requirements Analysis Use Cases Assignment to Subsystems Subsystem Functional Design * Subsystem Requirements Document HW/SW Requirements Specification Document The Top-Down System Design Process in Aerospace/Defense * Concurrent Engineering Task Grouping of Functionality System-Level COTS Analysis Partitioning into Subsystems System Design * Copyright I-Logix System Requirements Document Links providing Traceability of Specs to original Requirements Test Scenarios / Test Vectors

18 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 17 Functional Decomposition The Top-Down Approach Hierarchy Level 0 ( Context-Diagram ) External Data Sink External Data Source Hierarchy Level 1 Top-Down Hierarchy Level 2 Copyright I-Logix

19 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 18 Subsystem Functional Design The Subsystem Design Process HW/SW Partitioning (Statemate) V&V Cycle incl. Rapid Prototyping Subsystem Functional Design Subsystem Design V&V Cycle Subsystem Design: Definition of Subsystem Interfaces Interface to other Subsystems * Subsystem Design: HW/SW Partitioning Analysis of HW/SW Collaboration * * may have to be partitioned Copyright I-Logix

20 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 19 Power Mirror Power Window Seat Heating Memory Store/Recall Platform independent Feature Library Feature Models F Feature Models F Feature Models F Feature Models Process Buffer Vehicle System... Test Scenarios derived from Requirements Recorded System Behavior Feature-based System Design Approach (Automotive) Capturing Vehicle-specific Features in a Conceptual System Model Functional Requirements HPMS KBXL... Feature Models F Feature Models F Feature Models F Feature Interaction Models Exterior Light ( Front, Back, Fog, Wiper/Washer ) Seat Control ( Positioning, Heating, Venting ) Copyright I-Logix

21 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 20 started/ SH_S1_CMD:=SH_LVL1_CMD; SH_S2_CMD:=SH_LVL2_CMD; SH_LOW_VOLTG:=KL30_LOW_VOLTG;; -- ch(SH_LVL1_CMD) or ch(SH_LVL2_CMD) or fs(KL15C or KL15X or KL30_HIGH_VOLTG or KL30_LOW_VOLTG)/ if not KL15C and not KL15X and not KL30_HIGH_VOLTG and not KL30_LOW_VOLTG then SH_S1_CMD:=SH_LVL1_CMD; SH_S2_CMD:=SH_LVL2_CMD; SH_LOW_VOLTG:=KL30_LOW_VOLTG end if;; -- tr(KL15C or KL15X or KL30_HIGH_VOLTG or KL30_LOW_VOLTG)/ fs!(SH_S1_CMD); fs!(SH_S2_CMD); SH_LOW_VOLTG:=KL30_LOW_VOLTG;; Feature Model (Statemate): Seat Heating Copyright I-Logix

22 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 21 Feature Interaction Model (Statemate): Seat Controller Copyright I-Logix

23 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page Process Buffer Vehicle System HPMS... K B X L Test Scenarios derived from Requirements ProcessBuffer ECU_1 Functions ECU_N Functions Vehicle System ECU Test Vector Recording Feature-based System Design Approach System Partitioning, Parsing of Features/Feature Sub-Functions, and Validation of logical Interfaces B KHXHM... Copyright I-Logix

24 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page Process Buffer Vehicle System Input Filter Output Filter Process Buffer Bus Interface ECU_N Test Scenarios derived from Requirements Definition of HW Interfaces and Validation through Rapid Prototyping ECU_1 Functions B K H ECU_N Functions X H M X H M H/W Test Vectors derived from recorded logical ECU Test Vectors Copyright I-Logix

25 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 24 System Acceptance System Integration & Test Test Scenarios System Modification HW/SW Requirements Specification Test Scenarios Requirements Analysis TESTDBTESTDB Systems Analysis & Design function/data-oriented Systems Engineering Requirements Specification A-D-I-T Cycles From Function/Data-oriented Systems Engineering to Object-oriented SW Design A-D-I-T : Analysis-Design-Implementation-Testing Design Implementation Testing Mechanistic Design Detailed Design Coding Unit Testing Integration Testing Validation Testing Iterative Prototypes object-oriented SW Design

26 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page Process Overview: Model-based System Development The V Development Process Requirements Capture (Use Cases) Systems Analysis and Architectural Design Transition to SW Design 2. Modeling Languages 3. Model-based Verification/Validation 4. Documentation in a Model-based Development Model-based Systems Engineering

27 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 26 User Interface View Panel Use Case View Use Case Diagram Use Case Scenario View Sequence Diagram Time-continuous Behavioral View Time-continuous Diagram State-based Behavioral View Statechart Copyright I-Logix Statemate Functional / Architectural View Activity Chart Modeling Languages (Statemate) The different Views to a System

28 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 27 + Hierarchy: Structure: A state may consist of states which consist of states … Priority rule for transitions: Priority is given to the transition whose source and target states have a higher common ancestor state. Modeling Languages Definition of Statecharts Finite State Machine (FSM): A virtual machine that can be in any one of a set of finite states and whose next states and outputs are functions of input and current states. + Concurrency: Description of independent - or almost independent – parts of system behavior (e.g. subsystems) in a single Statechart. Synchronization through Broadcasting. Copyright I-Logix

29 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 28 The Statechart Language Describing Interrupt Priorities through Hierarchies

30 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 29 Modeling Languages Functional Description through Activity Charts Activity Chart Statechart Copyright I-Logix

31 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 30 Activity Charts Encapsulation of Activities Statechart Activity Chart Copyright I-Logix

32 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 31 Activity Charts Describing Basic Function-Blocks (Basic Activities) Mini-Spec Continuous Diagrams Truthtables (Legacy) C-Code Statemachines (Statechart) Copyright I-Logix

33 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 32 started/ ACCEL_CMD:=GAIN_ACC*ACCEL_DEFLECTION;; tm(wr(ACCEL_CMD),0.1)/ ACCEL_CMD:=GAIN_ACC*ACCEL_DEFLECTION;; PI_Controller Modeling Languages (Statemate) Hybrid ( = state-based & time-continuous/time-discrete) Modeling (Example: Simplified Model of a Cruise Control ) Vehicle_Dynamics_Kinematics Copyright I-Logix

34 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page Process Overview: Model-based System Development The V Development Process Requirements Capture (Use Cases) Systems Analysis and Architectural Design Transition to SW Design 2. Modeling Languages 3. Model-based Verification/Validation 4. Documentation in a Model-based Development Model-based Systems Engineering

35 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 34 Executable Specification (Statemate) Example: Mission Computer Symbol Generator (UFCP) Copyright I-Logix

36 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 35 Seat-Heating Module (Functional Model) Test-Data Generation via GUI Model Verification / Validation through Simulation (Statemate) Simulation Output: Waveform Diagram Requirements Scenario SH-005 Copyright I-Logix

37 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 36 Model Verification / Validation Test-Script Generation and Re-Use of Tests S/W Requirements Specification Test Patterns 1. FUNCTIONAL DESCRIPTION 2. BEHAVIORAL DESCRIPTION Requirements related Test-Vectors ( Playback File) Actual Output Analysis ECU RQ Output Test Input Testbench for Unit-Test i.e. HP ECUTEST Copyright I-Logix

38 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 37 Model Verification / Validation Extended System Analysis A system specified by means of a Formal Specification Language, may be amenable to Formal Verification. Formal Verification increases the safety of a design by mathematically Proving that disastrous situations never happen Based on the description of an unwanted situation the algorithm will check for the respective safety bug Ensuring expected situations are reachable Drive to State / Drive to Configuration Formal Verification may also be used to automatically generate test cases for unit, module, and integration testing

39 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 38 Model Verification / Validation Code Generation A system specified by means of a Formal Specification Language may be amenable to Code Synthesis, e.g. C-Code or VHDL-Code During the Requirements Analysis Phase a Soft Prototype together with a graphical User Interface may be used as a first Proof of Concept or for marketing purposes During the System Design Phase, code generation may help to Validate Hardware/Software partitioning (Hardware/Software Co-Design) Validate the design in its real environment by porting it to some prototyping hardware (Rapid Prototyping) Copyright I-Logix

40 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 39 MIL 1553B parallel/ serial TCP/IP Model (Back-) Animation UNIX / NT Prototype Target Unit Statemate MAGNUM generated code running on RTOS (e.g. VxWorks) Functional Model Verification / Validation Rapid Prototyping Copyright I-Logix

41 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page Process Overview: Model-based System Development The V Development Process Requirements Capture (Use Cases) Systems Analysis and Architectural Design Transition to SW Design 2. Modeling Languages 3. Model-based Verification/Validation 4. Documentation in a Model-based Development Model-based Systems Engineering

42 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 41 Documentation in a Model-based Development A system specified by means of a Formal Specification Language implies a paradigm shift in documentation. Since by definition the system under design is described unambiguously, no additional descriptive text is needed. The additional information should be restricted to remarks like Quality of Service Requirements or Requirements Traceability information.

43 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 42 Model Documentation (Statemate) Example: STORES MANAGEMENT SYSTEM hierarchical order of Activity Charts Copyright I-Logix

44 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 43 Model Documentation (Statemate) Example: STORES MANAGEMENT SYSTEM alphabetical order of Statecharts Copyright I-Logix

45 H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 44 Model Documentation (Statemate) Example: STORES MANAGEMENT SYSTEM Optional: alphabetical order Copyright I-Logix


Download ppt "H-P Hoffmann, Ph.D. Model-based Systems Engineering Page 1 Overview of Systems Engineering Fundamentals - Model-based Systems Engineering - Minneapolis."

Similar presentations


Ads by Google