DEXlib future work
Business drivers Project structure Outputs Deliverables Marketing SOA Templates / Capabilities / DEXs Ref data AP239 DEXlib infrastructure dexlib information / Help Testing environment P28
1. Business drivers
Driven by projects and implementations
Needs to have stable "product"
2. Project structure
Funding
Project manager
Technical architect
Core team of resources
Plan
Cover all topics
Milestones
Dependencies
activities
Development of content
DEXs/capabilties
Ref data
Development of supporting infrastructure
test rallies
project management
support
review "dexs"
pushing "dexs" through standardization
maintenance of standards
list of companies that do PLCS
supporting deployments
Configuration manager
The person who is responsible for CM of dexs etc
organization umbrella
Is OASIS the right place?
Should we set up a PLCS organization to support/maintain the standard?
3. Outputs Deliverables
What should be standardized?
Capabilities
Templates
DEXs
The TOG should develop and publish the standard/generic DEXs - importantly the cpaabilities and templates
The TOG should support the publishing of the business dexs by providing guidance and infrastructure.
The business dexs are candiates for standardization.
DEXs
Publication of DEXs
Investigate OASIS publication of DEXs
DEXlib support
May require changes to DEXlib to allow OASIS publication
OASIS ??
Should we produce an OASIS standard?
Web?
Publication of capabilities
development process
Checklists
Review
Ref data
A set of Standard PLCS ref data
development process
Checklists
Review
Annotation properties
publication
Procedures for how to promote/submit reference data asa standard
Guidelines for reference data development
Examples, such as when to use reference data for fault codes.
How to develop reference data, when to use reference data, when not to
How to represent multi lingual reference data
Define a normalized form for OWL
This would included annotation propoerties
Also a standard rdf representation of OWL
Test data
Phases
Phase 0
M0
Establish project
Phase 1 - DEX development
3 months
M1
dexlib infrastructure
M2
Core capabilities ready for ballot
Core ref data
Check lists
Procedures
CM of dexlib and baselining of dexs
Coherent set of example data in capabilities
M3
Decide which DEXs for development
a pair of "Standard" DEX / Business dex
Operational feedback / Aviation maintenance dex
Task information/ specification
M4
Develop missing capabilities required for M2
M5
DEXs ready for review
M6
DEXs reviewed
M7
Software vendors / implementations identified for implementer forum participation
Phase 2 - DEX testing
M1
test data for DEXs completed in Phase 1
M2
Implementers forum established
M3
Implementations of DEXs in Phase 1
M4
First test rally established
M5
Capabilities etc from phase 1 standardized
Phase 3
Service Orientated Architecture
M1
Scope services
M2
Define webservices
Phase 4
Additional DEXs
4. Marketing
Overview paper
5. SOA
Web services tied to templates
implications for the return statement in the services - how do we return multiple values
investigate naming of templates
High level business services?
UML model
extend the template to allow definition of the web services
6. Templates / Capabilities / DEXs
Review all
Use IS version of AP239?
Use templates?
Use reference data?
Use agreed layout?
Development process
Checklist
Agree what needs to be completed
maintenance - use of scheme
Define functionality that PLCS will be capable of delivering. I.e. identify
Subtopic
7. Ref data
Process
Annotation properties
CM
Publication
harmonized set for standardization
core PLCS
multiple ontologies?
tools for developing OWL
8. AP239
technical corrigendum
Timetable?
Review of changed modules
Review
Incorporate
Address SEDS arising from pilots
Build new long form
Ballot
edition 2
Timetable?
agree and Incorporate new functionality
CM of tasks
Risk
9. DEXlib infrastructure
long form generation, express integrity
Rename business concept to business dex
Templates
Separate into files
This will allow CM
dependency of templates
SHow which capabilities are dependent on which templates
Show which templates are dependent on which templates.
Path language
options / conditions
input parameters that are instance references rather than entity
specification of uniqueness e.g. address
application context
view definition
address
Config Management
CM ref data
versioning of OWL files
Process
CM of dexs + dependencies
Define how the baseline of the DEX, capabilities, templates modules, AP, reference data, and business concepts is managed, identified and represented in an exchange contract
Document tool and baselining process
Maintain a released version of the modular AP
Implement simple to use tool to create and view baselines
GraphicalInstance
GraphicalExpress
Support test data
Display
support common block of text
review if dexlib is adequate
Search functionality
Investigate XML database
OK for publishing
Requirements gathering
10. dexlib information / Help
identify readers expectations
education programme
11. Testing environment
Establish testing forum
Procedures
frequency
Develop a suite of test files
define which templates and application must implement in order to read the test data
List the templates used to build the test file
each capability and template have a set of test data
establish business example that is implemented in the test data. E.g. Bike data
Tools
Tool support to generate test data
GraphicalInstance
P21 / P28
Programmatic
Tool to validate test data
Syntatic check Valid according to EXPRESS
Semantic check Valid according to Templates
Reference data check
Display errors
Display within DEXlib
12. P28