1. Implementing ATML Lessons Learned
Developing products and integration solutions that consume ATML data produced by multiple sources
Test Results
From multiple run time engines
Test Description
From legacy TPSs
From TRDs, …
Autotestcon 2010
9/15/2010

2. Problem
Format C
Format B
Format A
Variance in ATML data received from different sources (valid data)
Data items can be “legally” stored in more than one place or using more than one format
Extensions can be misused
Ambiguity in the specification
Supporting multiple versions of the standard (including future versions)
Autotestcon 2010
9/15/2010

3. Solution 1 Application Format A Converter Format B Format C
Autotestcon 2010
9/15/2010

4. Solution 2 Application Unified Data Model Loader Format A Format B
Format C
Autotestcon 2010
9/15/2010

5. Solution 2… Unified Data Model Can be objects in memory, XML, etc.
Application
Unified Data Model
Loader
Format A
Format B
Format C
Unified Data Model
Can be objects in memory, XML, etc.
Include only data items used by the application
Follow the general structure of the ATML schema
May flatten hierarchy
Autotestcon 2010
9/15/2010

6. Solution 2… Loaders Validate ATML instance document against XML schema
Application
Unified Data Model
Loader
Format A
Format B
Format C
Loaders
Validate ATML instance document against XML schema
Retrieve data from format-specific locations
Verify presence of data items that are optional according to schema but required by the application
Provide defaults for optional data items that are missing from the ATML instance document
Possibly: convert data types
Possibly: convert item identifiers to a unique format
Autotestcon 2010
9/15/2010

7. Example
Autotestcon 2010
9/15/2010

8. Conclusions Variance in ATML data is likely to require adaptation
This is a one-time integration task for each application and each producer. Amount of work is relatively small if scope is limited to data relevant for the application.
New XML processing technologies (ex. LINQ to XML, LINQ to XSD) simplify the task
Once in place, the architecture facilitates future integration of additional data producers and support for new versions of the standard
Differences should be recorded and used to improve accuracy in future versions of the ATML specifications
Autotestcon 2010
9/15/2010