Qualtech Systems Inc. Modeling Converter Team 1702 Jay Meyer EE - - PowerPoint PPT Presentation
Qualtech Systems Inc. Modeling Converter Team 1702 Jay Meyer EE Andrew Morse EE/CSE Brandon Singleton CSE William Salguero EE 1 Overview Introduction Qualtech Systems Inc. (QSI) Project Outline XML/XSL Test Models
1
Team 1702 Jay Meyer EE Andrew Morse EE/CSE Brandon Singleton CSE William Salguero EE
▶
Introduction
▶
Qualtech Systems Inc. (QSI)
▶
Project Outline
▶
XML/XSL
▶
Test Models
▶
Proof of Concept
▶
End Goals
2
▶ Advanced proprietary modeling software (TEAMS-Designer) ▶ Models individual components as well as complex interactions ▶ Similar but inherently different from Matlab’s Simulink modeling ▶ Their customers use Simulink, they need to convert between the two
software suites
3
4
Simulink Model XML
Transforming Document
XSLT New TEAMS Model XML
Verifier Converter/ Transformer
▶ What is XML?
▶ Similar to HTML ▶ Industry standard markup language for formatting and common use ▶ Supported by both Simulink and TEAMS-Designer
▶ How do Simulink and TEAMS-Designer utilize XML?
▶ Both have the ability to import and export modeling information in XML format ▶ So what’s the problem?
▶
The two XMLs have a different structure, thus they are not mutually intelligible
5
▶ XSL
▶ XSL Transform (XSLT) ▶ XML Path Language (XPath) ▶ XSL Formatting Objects (XSL-FO)
▶ XSLT (Converter Module)
▶ The document that allows for XML transformations (conversions) ▶ Conversion programs take an XSL and XML as inputs and output a new XML in the target style ▶ The answer to our problem
6
▶ Compares 2 XML files and determine similarities and differences
▶ Either Simulink and TEAMS-Designer ▶ TEAMS-Designer and post-transform XML
▶ Will highlight differences in files
▶ Header information that does not translate from one style to the other ▶ Any issues in conversion (ie. modules not converted)
▶ Verifies module was successfully converted
▶ Informs user of any modules not translated
7
8
9
▶ Created a series of test models we will use to develop conversion process ▶ Each Simulink model has a near-exact copy in TEAMS Designer ▶ 7 basic Models, each progressively more complex than the last ▶ Small, minute differences in each model ▶ Goal was to start small and increase complexity and functionality with each model
10
11
12
13
14
15
16
17
▶
Add support for more Simulink libraries
▶
One executable file
▶
Converts to TEAMS Designer XML file
▶
Repackages in *.tmsx file that can be reopened by TEAMS Designer
▶
Informs user of untranslatable module types
18