Deutsch (DE-CH-AT)English (United Kingdom)

Open Test Framework

Pro­fes­sio­nal Deve­lop­ment of gene­ric Tes­ter App­li­ca­ti­ons

The Open Test Fra­me­work is a com­ple­te deve­lop­ment envi­ron­ment for desi­gning, main­tai­ning and tes­ting a new gene­ra­tion of pro­cess-safe test app­li­ca­ti­ons that can be run on Win­dows com­pu­ters. The clear and intui­ti­ve user inter­fa­ce hel­ps the Open Test Fra­me­work work­flow aut­hors and pro­ject mana­gers to crea­te and deli­ver fas­ter com­pre­hen­si­ve and con­vin­cing tes­ter solu­ti­ons. All rele­vant stan­dards such as ISO 13209 (OTX), ISO 22900 (MVCI) and ISO 22901 (ODX) are sup­por­ted. For the adap­ta­tion to spe­ci­fic custo­mer requests the Open Test Fra­me­work can be exten­ded relea­se safe­ly to almost any level.

Open Test Framework - OTX-Designer


Are­as of app­li­ca­tion

The app­li­ca­tion are­as of open tes­ting fra­me­works ran­ge from the basic wor­king through stan­dar­di­zed test sequences to the crea­tion of fur­ther dis­tri­buta­ble tes­ter app­li­ca­ti­ons. The­re­by are current­ly app­li­ca­ti­ons in the field of off-board vehic­le dia­gno­stics to the fore. Examp­les are a uni­ver­sal and quick­ly adap­ta­ble flash tool, tool for checking the pro­to­col con­for­mi­ty of elec­tro­nic con­trol unit, sim­ple and com­plex deve­lop­ment and pro­duc­tion tes­ter or even a sim­ple scan tool in the envi­ro­ment of the OBD.


Main func­ti­ons

OTF

Deve­lop­ment Envi­ron­ment

Take advan­ta­ge of a tidy, fast, and power­ful deve­lop­ment envi­ron­ment, to focus on value crea­tion and com­ple­te tasks in less time.

  • Com­ple­te and nati­ve sup­port for OTX 1.0 accor­ding to ISO 13209
  • Sup­port ODX 2.01, 2.1 and 2.2 accor­ding to ISO 22901-1
  • Gra­phi­cal crea­tion of test sequences by sim­p­ly drag­ging and drop­ping acti­vi­ties without pro­gram­ming know­led­ge
  • Self defi­na­ble OTX tem­pla­tes (see. offi­ce tem­pla­tes incl. pla­ce­hol­ders) for quick and easy crea­tion of app­li­ca­tion-spe­ci­fic struc­tu­red pro­jects, docu­ments or pro­ce­du­res
  • Com­pre­hen­si­ve pro­ject mana­ge­ment (file repo­si­to­ry)
  • Libra­ry con­cept for the crea­tion and editing of sequences from the tech­ni­cal point of view of a tech­ni­cian
  • Export and import of PTX-pro­jects accor­ding to ISO 22901-1
  • Gene­ra­tion of sim­ple gene­ric tes­ters (exe­cuta­ble files * .exe)
  • Undo, Redo any dep­th
  • Exten­si­ve opti­ons for sear­ching and repla­cing on object-level
  • Auto­ma­tic refe­rence adjust­ment with pre­view
  • Nati­ve and direct pro­ces­sing of OTX data (no import or export)
  • Indus­try tes­ted (Volks­wa­gen, Por­sche, Audi, etc.)

OTF

Inde­pen­dence

Crea­te test sequences inde­pen­dent­ly of the under­ly­ing run­ti­me sys­tem.

  • Inde­pen­dent of the exe­cu­tion sys­tem. New run­ti­me imple­men­ta­ti­ons (eg. text block data­ba­se) can be easi­ly added
  • Inde­pen­dent of the dia­gno­stic run­ti­me sys­tem (cur­rent imple­men­ta­ti­ons of DSA PRO­DIS.MCD, VW-MCD and RA-MVCI ser­ver)

OTF

Team col­la­bo­ra­tion

Connect the deve­lop­ment team, pro­ject par­ti­ci­pants and end-users through inte­gra­ted tools that pro­mo­te col­la­bo­ra­tion.

OTF

Run, Debug & Test

Iden­tify and resol­ve pro­blems through which the sequences are not exe­cu­ted cor­rect­ly.

  • Gene­ra­tion and com­pi­la­tion of exe­cuta­ble C# code on the fly (any other lan­gua­ges ​can be exten­ded)
  • Inte­gra­ted visual debug­ger wat­ch win­dow to chan­ge decla­ra­ti­ons in single-step mode
  • Set­ting break­points, opti­mi­zing pro­ces­ses and sol­ving errors
  • Simu­la­tion of ECU com­mu­ni­ca­tion (at the level of D-PDU-API) for the deve­lop­ment of sequences without vehic­le com­mu­ni­ca­tion
  • Gene­ric Screen: gene­ric crea­tion of win­dows for out­put (HMI)
  • Screen Map­ping: map­ping of OTX varia­bles to Win­dows Forms app­li­ca­ti­ons for out­put (HMI)
  • Devi­ce Map­ping: map­ping of devi­ce signa­tu­res (Mea­su­re) to DLLs to inter­act with any exter­nal devi­ces
  • Con­text Map­ping: map­ping of con­text varia­bles to iden­ti­fi­ca­tion rou­ti­nes
  • Inte­gra­ted text block libra­ry incl. Edi­tor (I18N)
  • Con­ve­ni­ent con­fi­gu­ra­tion and gene­ra­tion of log files (log­ging)
  • Sup­port defi­ned in ODX units (UNIT-SPEC) for Quan­ti­ty

OTF

Ensu­ring qua­li­ty

Advan­ced tes­ting tools ensu­re the qua­li­ty over the who­le life cycle and ena­ble high qua­li­ty soft­wa­re.

  • Veri­fi­ca­tion of data con­sis­ten­cy and dis­play­ing errors and war­nings on the fly
  • OTX checker vali­da­ti­tion of OTX sequences at desi­gn time

OTF

Relea­se mana­ge­ment

Dis­tri­bu­te your solu­tion to others with tools that redu­ce the cycle time and impro­ve the deploy­ment pro­cess.

  • Mana­ge­ment of relea­sed infor­ma­tion (in ODX defi­ned ADMIN-DATA) in the built-in edi­tor
  • Gene­ra­tion of setup instal­la­tion pro­jects (MSI) for the dis­tri­bu­tion exe­cuta­ble OTX app­li­ca­ti­ons (optio­nal­ly with inte­gra­ted OTX run­ti­me)
  • Trans­fer of OTX pro­jects incl. OTX-View­er for gra­phi­cal repre­sen­ta­tion and ana­ly­sis in the brow­ser (Fire­fox)

OTF

Exten­si­bi­li­ty

Com­ple­te new deve­lop­ment with an open soft­wa­re archi­tec­tu­re for easy exten­si­bi­li­ty on almost eve­ry level.

  • Sup­port various new OTX exten­si­ons like File, XML, Diag­Da­ta­B­row­sing+, Core+, Event­Hand­ling+ and Data­Ba­se (EMO­TI­VE is active­ly invol­ved in the stan­dar­di­za­tion in the field OTX)
  • Exten­sion of stan­dar­di­zed checker rules (eg. to ensu­re the ODX/OTX data con­sis­ten­cy)
  • Stand-alo­ne OTX API and OTX Runti­me API (both incl. OTX checker) for inte­gra­tion into own envi­ron­ments

Details

Sup­por­ted dia­gno­se stan­dards

  • MVCI Ser­ver API (ISO 22900-3, ASAM MCD-3D Ser­ver)
  • ODX (ISO 22901-1, ASAM MCD-2D, 2.0.1, 2.0.2, 2.1.0, 2.2.0)
  • OTX (ISO 13209)
  • D-PDU-API (ISO 22900-2)
  • CAN (ISO 11898)
  • UDS (ISO 14229)

Sup­por­ted hard­wa­re (Vehic­le Com­mu­ni­ca­tion Inter­fa­ce)

  • Bosch MDI
  • DSA MDI-G
  • sam­tec HSX, HS+, HSlight
  • Vec­tor CAN­CardXL, CAN­Ca­seXL, CAN­BoardXL
  • Others with stan­dar­di­zed D-PDU-API inter­fa­ce (ISO 22900-2)

PC requi­re­ments

  • PC with Win­dows XP SP2 or hig­her (also 64-Bit)
  • .NET Fra­me­work 4.0

Sco­pe of deli­ve­ry

Licen­ses

  • Deve­lop­ment licen­se stan­dard or pro­fes­sio­nal edi­tion is requi­red, see fea­tu­re matrix
  • 30 days eva­lua­tion licen­se on request

Instal­la­tion packa­ges


  • Erstellt
    25 October 2014
  • Version
    19
  • Geändert
    17 March 2016
  • Zugriffe
    10249