Difference between revisions of "OtfFeatures"

From emotive
Jump to navigation Jump to search
Line 6: Line 6:
 
| [[Image:OTF.png|64px|link=OtfUserDoc]] || '''Development Environment'''
 
| [[Image:OTF.png|64px|link=OtfUserDoc]] || '''Development Environment'''
 
''Focus on creating value and accomplishing tasks quicker with a clean, fast and powerful development environment for OTX-based tasks.''
 
''Focus on creating value and accomplishing tasks quicker with a clean, fast and powerful development environment for OTX-based tasks.''
−
* Graphical programming. Drag and drop objects directly into visual test sequences- no programming language to learn.
+
* Complete and native support for OTX 1.0 according to ISO 13209
−
* Experts can edit OTX with an text editor like a programming language with OTL, a Java like Pseudo-Code which is fully OTX compatible
+
* Support ODX 2.01, 2.1 and 2.2 according to ISO 22901-1
−
* Use self defined OTX-Templates with place holders support for quick and easy creation of special structured OTX documents
+
* Graphical creation of test sequences by simply dragging and dropping activities without programming knowledge
−
* Separate specification and implementation views enable you to capture high level sequence first and then add implementation details later
+
* Code-Editor – Editing of OTX-Sequences with OTL (Open Test sequence Language). 100 % OTX compatible programing language, similar to Java/C#.
−
* Automatically lays out nodes and routes connections for readability
+
* Self definable OTX templates (see. office templates incl. placeholders) for quick and easy creation of application-specific structured projects, documents or procedures
−
* Fast processing of very large OTX databases
+
* Comprehensive project management (file repository)
−
* Native and direct working on OTX data (no import or export!)
+
* Library concept for the creation and editing of sequences from the technical point of view of a technician
−
* Support of a fully OTX compatible convenience layer above OTX for the generation of test sequences on a high grade of abstraction
+
* Extension manager for switch ON/OFF of OTX extensions
−
* Already proven in Industrial Environments (Volkswagen, Porsche, Audi etc.)
+
* Meta-Data Manager for template based management of OTX-Meta information
 +
* Export and import of PTX-projects according to ISO 22901-1
 +
* Generation of simple generic testers (executable files * .exe)
 +
* Undo, Redo any depth
 +
* Extensive options for searching and replacing on object-level
 +
* Automatic reference adjustment with preview
 +
* Native and direct processing of OTX data (no import or export)
 +
* Industry tested (Volkswagen, Porsche, Audi, etc.)
  
 
|- style="vertical-align:top;"
 
|- style="vertical-align:top;"
Line 31: Line 38:
 
| [[Image:OTFExecuting.png|64px|link=OtfUserDoc]] || '''Execution, Debugging & Diagnostics'''
 
| [[Image:OTFExecuting.png|64px|link=OtfUserDoc]] || '''Execution, Debugging & Diagnostics'''
 
''Identify and solve issues that keep your solution from running correctly.''
 
''Identify and solve issues that keep your solution from running correctly.''
−
* On-the-fly code generation and compilation for execution of test sequences with best performance (C#, arbitrary target languages can be added)
+
* On-the-fly code generation for execution of test sequences (C#, Java, Lua, arbitrary target languages can be added)
−
* Integrated visual debugger with watch window support
+
* Integrated visual debugger with watch window support Set breakpoints, optimize your code and resolve errors
−
* Set breakpoints, optimize your code and resolve errors
+
* Offline-Execution for development of sequences without ECU communication
−
* Simulation of vehicle diagnostics communication lets you execute and debug your sequences - even before vehicle communication is added
+
* Generic-Screen – Generic creation of OTX screens (HMI)
−
* Complete support of auto generated generic screens and/or support of mapping to self-designed GUI (Windows Forms)
+
* Screen-Mapping – Mapping of OTX-Variables to controls within a Windows Forms application (HMI)
 +
* Device-Mapping – Mapping of Device-Signatures (Measure) to DLL's for interaction with arbitrary external devices
 +
* Context-Mapping – Mapping of Context-Variables to identification routines (public static method of a DLL)
 +
* Integrated Text block library incl. Editor (I18N)
 +
* Convenient configuration and generation of log files (Logging)
 +
* Support of ODX units (UNIT-SPEC) for Quantity
  
 
|- style="vertical-align:top;"
 
|- style="vertical-align:top;"
Line 48: Line 60:
 
* Complete integration of workflow control and release management system (Admin-Data)
 
* Complete integration of workflow control and release management system (Admin-Data)
 
* Deploy your solution with integrated MSI-Installer
 
* Deploy your solution with integrated MSI-Installer
−
* OTX-Viewer for graphically view and analyze OTX in a Browser (Firefox)
+
* [[OtxViewerUserDoc|OTX Viewer]] for graphically view and analyze OTX in a Browser (Firefox)
  
 
|- style="vertical-align:top;"
 
|- style="vertical-align:top;"
Line 54: Line 66:
 
''Completely new development with an open software architecture for a simple extensibility at almost each layer.''
 
''Completely new development with an open software architecture for a simple extensibility at almost each layer.''
 
* Support of various new extensions like File, XML, DiagDataBrowsing+, Core+, EventHandling+ and DataBase (EMOTIVE is initiator and driver of a new ASAM work group for the standardization of further OTX extensions)
 
* Support of various new extensions like File, XML, DiagDataBrowsing+, Core+, EventHandling+ and DataBase (EMOTIVE is initiator and driver of a new ASAM work group for the standardization of further OTX extensions)
−
* Stand-alone OTX-API and OTX-Runtime-API for integration in own tools
+
* Extension of standardized Checker rules (e.g. for ODX/OTX data consistency)
−
* A new OTX runtime environment for Java and for the execution in embedded systems (Lua-Script) is currently under construction
+
* Stand-alone [http://www.emotive.de/DeveloperReference/OtxApi/html/17566ff9-8c18-4795-ab2e-b269c81b721f.htm OTX-API] and [http://www.emotive.de/DeveloperReference/OtxRuntime/html/17566ff9-8c18-4795-ab2e-b269c81b721f.htm OTX-Runtime API] for integration in own tools
  
 
|}
 
|}

Revision as of 17:46, 25 March 2015

Explore all the features of Open Test Framework.

OTF.png Development Environment

Focus on creating value and accomplishing tasks quicker with a clean, fast and powerful development environment for OTX-based tasks.

  • Complete and native support for OTX 1.0 according to ISO 13209
  • Support ODX 2.01, 2.1 and 2.2 according to ISO 22901-1
  • Graphical creation of test sequences by simply dragging and dropping activities without programming knowledge
  • Code-Editor – Editing of OTX-Sequences with OTL (Open Test sequence Language). 100 % OTX compatible programing language, similar to Java/C#.
  • Self definable OTX templates (see. office templates incl. placeholders) for quick and easy creation of application-specific structured projects, documents or procedures
  • Comprehensive project management (file repository)
  • Library concept for the creation and editing of sequences from the technical point of view of a technician
  • Extension manager for switch ON/OFF of OTX extensions
  • Meta-Data Manager for template based management of OTX-Meta information
  • Export and import of PTX-projects according to ISO 22901-1
  • Generation of simple generic testers (executable files * .exe)
  • Undo, Redo any depth
  • Extensive options for searching and replacing on object-level
  • Automatic reference adjustment with preview
  • Native and direct processing of OTX data (no import or export)
  • Industry tested (Volkswagen, Porsche, Audi, etc.)
OTFIndependence.png Independence

Build test sequences, independent from the underlying system.

  • Independent of the underlying runtime system environment. New special run-time systems can be easily added.
  • Independent of vehicle diagnostic runtime system (ASAM server, MVCI-Server). Currently three implementations are supported: VW-MCD, Porsche MVCI-Server and RA-MVCI-Server.
OTFTeam.png Team Collaboration

Connect the development team through integrated tools that foster collaboration.

  • Integrated SVN Version Control (TortoiseSVN)
  • Differ, Merger etc.
OTFExecuting.png Execution, Debugging & Diagnostics

Identify and solve issues that keep your solution from running correctly.

  • On-the-fly code generation for execution of test sequences (C#, Java, Lua, arbitrary target languages can be added)
  • Integrated visual debugger with watch window support Set breakpoints, optimize your code and resolve errors
  • Offline-Execution for development of sequences without ECU communication
  • Generic-Screen – Generic creation of OTX screens (HMI)
  • Screen-Mapping – Mapping of OTX-Variables to controls within a Windows Forms application (HMI)
  • Device-Mapping – Mapping of Device-Signatures (Measure) to DLL's for interaction with arbitrary external devices
  • Context-Mapping – Mapping of Context-Variables to identification routines (public static method of a DLL)
  • Integrated Text block library incl. Editor (I18N)
  • Convenient configuration and generation of log files (Logging)
  • Support of ODX units (UNIT-SPEC) for Quantity
OTFValidation.png Ensure Quality

Advanced testing tools assure quality throughout the lifecycle of your solution, enabling high quality software.

  • On-the-Fly design time validation of all standard and new defined checker rules
  • On-the-Fly dead link validation for ODX databases
OTXDeployment.png Release Management

Deploy your solution for any environment with tools that reduce your cycle time and improve your delivery process.

  • Complete integration of workflow control and release management system (Admin-Data)
  • Deploy your solution with integrated MSI-Installer
  • OTX Viewer for graphically view and analyze OTX in a Browser (Firefox)
OTXExtensibility.png Extensibility

Completely new development with an open software architecture for a simple extensibility at almost each layer.

  • Support of various new extensions like File, XML, DiagDataBrowsing+, Core+, EventHandling+ and DataBase (EMOTIVE is initiator and driver of a new ASAM work group for the standardization of further OTX extensions)
  • Extension of standardized Checker rules (e.g. for ODX/OTX data consistency)
  • Stand-alone OTX-API and OTX-Runtime API for integration in own tools
Retrieved from "http://emotive.de/wiki/index.php?title=OtfFeatures&oldid=2963"