1 / 22

Integrating Simulink

Typical Application Scenarios. . ToolNet. 20.04.04. 3. Code Generation. Code checking. Test of communication. Model test. Hardware in the Loop. SW test. Test case elicitation. RM data base. Dynamic modelling. Software implementation. Configuration. Sample Tool Environment for System Development.

holland
Download Presentation

Integrating Simulink

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Integrating Simulink / Stateflow into a System Development Environment Frank Altheide, Heiko Dörr, RIC/SM {frank.altheide | heiko.doerr}@daimlerchrysler.com

    2. Typical Application Scenarios

    3. ToolNet 20.04.04 3 Sample Tool Environment for System Development

    4. ToolNet 20.04.04 4 Application Scenario Modelling Components Stepwise construction of model accompanied by simultaneous documentation of requirements Characteristics Model creation within Simulink Requirements specification within RM tool (e.g. Doors) Assign requirements to model elements Trace between requirements and model elements

    5. ToolNet 20.04.04 5 Application Scenario Model Documentation Relation “REALISES” Function Blocks x Software Requirements Relation “REALISES” is defined by Anchor: all elements with tag state; let Value := Attribute “name” of that element <!ELEMENT state (junction | transition | event | data | state)*> <!ATTLIST state %idAttrs; %orientationAttrs; %visibLevelAttrs; id CDATA #REQUIRED name CDATA #REQUIRED type CDATA #REQUIRED .... position CDATA #REQUIRED dstOwner IDREFS #IMPLIED srcOwner IDREFS #IMPLIED > Target: 1) let object_number_of_section be the object number of section where Attribute “Object_Heading” = “Zustand “ ++ Value 2) targets are all elements with object_number_of_section is prefix of object number AND Objekttyp = Anforderung Zur Erläuterung: Die Section-heading im Beispiel hat die Object-Number 2.3, die einzelnen Anforderungen die Object-Number 2.3.0-1 bis 2.3.0-3Relation “REALISES” is defined by Anchor: all elements with tag state; let Value := Attribute “name” of that element <!ELEMENT state (junction | transition | event | data | state)*> <!ATTLIST state %idAttrs; %orientationAttrs; %visibLevelAttrs; id CDATA #REQUIRED name CDATA #REQUIRED type CDATA #REQUIRED .... position CDATA #REQUIRED dstOwner IDREFS #IMPLIED srcOwner IDREFS #IMPLIED > Target: 1) let object_number_of_section be the object number of section where Attribute “Object_Heading” = “Zustand “ ++ Value 2) targets are all elements with object_number_of_section is prefix of object number AND Objekttyp = Anforderung Zur Erläuterung: Die Section-heading im Beispiel hat die Object-Number 2.3, die einzelnen Anforderungen die Object-Number 2.3.0-1 bis 2.3.0-3

    6. Tool Integration Goals

    7. ToolNet 20.04.04 7 Tool Integration Goals w.r.t. Data Data integration Typical EAI-application: transparent access on distributed data bases via separate (web-)client Realised by 3-layer architecture incorporating integrated data model Data / model exchange Exchange of data with common semantics (e.g. XMI for UML models, STEP AP233) Assumes common semantics implemented by each of the tools Data / model transformation Simple for data with simple semantics High efforts for models with elaborated semantics (e.g. statecharts)

    8. ToolNet 20.04.04 8 Tool Integration Goals w.r.t. Functionality Establish fixed work flow connecting the functions provided by the tools (e.g. make, Unix pipes, stepwise model transformation) User driven work flow calling fixed, additional data transformation (e.g. MTest) Concurrent operation of tools (e.g. co-simulation) Provide common and additional functionality for integrated tools

    9. ToolNet 20.04.04 9 Tool Integration Goals w.r.t. Presentation Application of common widget libraries (e.g. Swing, Athena Widgets) Common look-and-feel

    10. ToolNet 20.04.04 10 Tool Integration Goals of ToolNet Common look-and-feel Provide common and additional functionality for integrated tools Simple data integration ... based on tracing information as THE essence of integration

    11. The ToolNet Approach

    12. ToolNet 20.04.04 12 System Architecture Information Backbone Specific characteristics Data remains in tools instead of exchanging it Capture common behaviour of tools by specific group of services Encapsulate functionality relevant for integration by Facade pattern Concentrate on inter-operation Roles of tools within integration Project management Editor Presentation Data source Link management

    13. ToolNet 20.04.04 13 Detailed System Architecture – Interfaces

    14. ToolNet 20.04.04 14 How it looks

    15. ToolNet 20.04.04 15 Conclusion ToolNet V1.0 is a framework for the low-cost integration of system development tools As a sample Simulink / Stateflow has been integrated with Doors for requirements management and CTE for test case elicitation At present, pilot applications are executed Seeking for co-operation with external partners to exploit the framework capabilities to extend the set of supported tools and integration functionality

    16. Backup

    17. ToolNet 20.04.04 17 Today’s systems are Increasingly complex Highly reliable Essential for differentiation of competition Using software as integral part Development must be Efficient Integrate various development disciplines Supported by specialised tools Problem-oriented Characteristics of System Development

    18. ToolNet 20.04.04 18 User Requirements Capability Exploit data coincidences Perform automatic updates to maintain consistency Interchange data Support process and work flow Intense automation Flexibility Exchange of tools with similar functionality Simple migration to new releases Scalable deployment of sub-components Extensibility Task-oriented Tools Phases Flexible definition of IDEs for system development

    19. ToolNet 20.04.04 19 ToolNet Principles Primacy of standard / COTS tools Do not substitute functions of primary development tools Data remain in tools Apply standard tools wherever possible For development as well as for management tasks Scalable development and deployment Incremental support of tools and functionality Instantiate IDE according to specific needs Identical and independent extended API Arbitrary combinations of tools can be supported Tool and its adapter know best Decentralised responsibilities

    20. ToolNet 20.04.04 20 Application Scenario State-based Analysis of Functionality Relation “REALISES” States x System Requirements State-, function block oriented requirements specification Each requirement object is realised by state or function block Relation “REALISES” is defined by Anchor: all elements with tag state; let Value := Attribute “name” of that element <!ELEMENT state (junction | transition | event | data | state)*> <!ATTLIST state %idAttrs; %orientationAttrs; %visibLevelAttrs; id CDATA #REQUIRED name CDATA #REQUIRED type CDATA #REQUIRED .... position CDATA #REQUIRED dstOwner IDREFS #IMPLIED srcOwner IDREFS #IMPLIED > Target: 1) let object_number_of_section be the object number of section where Attribute “Object_Heading” = “Zustand “ ++ Value 2) targets are all elements with object_number_of_section is prefix of object number AND Objekttyp = Anforderung Zur Erläuterung: Die Section-heading im Beispiel hat die Object-Number 2.3, die einzelnen Anforderungen die Object-Number 2.3.0-1 bis 2.3.0-3Relation “REALISES” is defined by Anchor: all elements with tag state; let Value := Attribute “name” of that element <!ELEMENT state (junction | transition | event | data | state)*> <!ATTLIST state %idAttrs; %orientationAttrs; %visibLevelAttrs; id CDATA #REQUIRED name CDATA #REQUIRED type CDATA #REQUIRED .... position CDATA #REQUIRED dstOwner IDREFS #IMPLIED srcOwner IDREFS #IMPLIED > Target: 1) let object_number_of_section be the object number of section where Attribute “Object_Heading” = “Zustand “ ++ Value 2) targets are all elements with object_number_of_section is prefix of object number AND Objekttyp = Anforderung Zur Erläuterung: Die Section-heading im Beispiel hat die Object-Number 2.3, die einzelnen Anforderungen die Object-Number 2.3.0-1 bis 2.3.0-3

    21. ToolNet 20.04.04 21 How to apply ToolNet

    22. ToolNet 20.04.04 22 Application Scenario Distributed Engineering Co-operation between several specialists within a development project Task-oriented development environment based on single data sources Distributed data must be interconnected Data presentation must be consistent and up to date

    23. ToolNet 20.04.04 23 Currently supported Tools

More Related