Applying MDA in the ATM: A practical approach Teodora Bozheva, Terry Bailey (ESI) Julia Reznik, Tom Ritter (Fraunhofer FOKUS)

ECMDA-FA, 11 July 2006, Bilbao The ATM Domain today and tomorrow Complexity of ATM Systems  command, control, communication and intelligence applications  distributed  safety critical  operate in open and dynamic environments  difficult to identify the full picture of system interactions  large amount of data, different formats  relationship between pilots and controllers is extremely complicated Expectations  number of flights in 2020 will be more than twice the number in 2000  more complex operational conditions in a more congested airspace

ECMDA-FA, 11 July 2006, Bilbao The ATM Domain today and tomorrow Target  ATM Systems need to accommodate an increasing traffic Requires  cost- and time-effective gaining Applying MDA for ATM System Development  reuse  high degree of automation  solving of integration and interoperability problems  produced data are format-independent

ECMDA-FA, 11 July 2006, Bilbao Some MDA Challenges How to start applying it? How to organise an MDA project? How can the development process be automated?

ECMDA-FA, 11 July 2006, Bilbao The AD4 System Provides the controllers with an ability to use 3D data about the air traffic/airport space in real time Extends D 3 - a 3D Virtual Reality System which manages a 3D visualisation and navigation Requirements based on observations and in-depth analysis of the work practices and strategies used by air traffic controllers A distributed component based system, reusing the existing D 3 components and providing integration with external, pre-selected platforms

ECMDA-FA, 11 July 2006, Bilbao AD4 Development Life Cycle Constraints AD4 project  Is based on the D 3 software, which includes a number of components, to be reused  Is developed by a distributed team of experts in the ATM domain and in software development  Involves exploration of the new MDA technology. AD4 development life cycle  Support component-based development  Support model-based development  Be iterative  Support collaboration of distributed teams  Support learning from experience.

ECMDA-FA, 11 July 2006, Bilbao AD4 Development Life Cycle Preparation phase  4DHMI reqs  AD4 PIM  AD4 tool chain development  Retrospective workshop 1st/ 2nd/ 3rd release  Select & validate reqs  PIM - PSM transformation  Code generation  Test and verify the system  Retrospective workshop Demonstrator  Scenario definition  Test cases definition  On-site integration and testing  System validation  Retrospective workshop Def/update system req. Def/update sys. architecture Generate code monitor analyse AD4 requirements analyse AD4 tech. req. 1month long iterations Periodic reviews Dev/update AD4 PIM Test and deploy

ECMDA-FA, 11 July 2006, Bilbao AD4 Tool Chain A set of model driven engineering and development tools  based on MDA approach  truly integrated with software systems construction process  supports planning, design and realization phases of the construction of ATM systems with different tools, but in one integrated environment Building artefacts:  Platform: CCM  Metamodels&Repositories: eUML and CCM  Transformers  Profiles

ECMDA-FA, 11 July 2006, Bilbao AD4 Tool Chain Architecture eUML Modeller  PIM specification of AD4 system  EA Plug-In CCM Plug-In  PSM specification and refinement  Eclipse Plug-In AD4 control application  management and control of various components of the tool chain  GUI implementation Qedo Tool suite  CCM implementation

ECMDA-FA, 11 July 2006, Bilbao System development with AD4 Tool Chain AD4 system specification with the eUML Modeler based on customized Enterprise Architect (manual step) model transform deploy generate transformation into the CCM applying AD4 model transformers (automated step) if needed, refine model code generation applying Qedo (automated step) add your business code (manual step) create system components (automated step) deploy on the execution framework (automated step) Rapid creation of the ATM systems in a well structured, consistent and automated way:

ECMDA-FA, 11 July 2006, Bilbao Conclusions How to start applying MDA?  Existing software engineering know-how and application domain knowledge How to organise an MDA project?  Short iterations  Learning from experience  Focus on delivering running software How can the development process be automated?  Tool chain

ECMDA-FA, 11 July 2006, Bilbao Lessons Learned in AD4 More development time for tool chain, but it’s worth!  Less development time for AD4 system  Huge amount of IDLs can be easily managed and reused Ad4 Tool Chain support for requirement engineering is needed  complex nature of controller activities  heterogeneity and availability of operational systems

ECMDA-FA, 11 July 2006, Bilbao Contacts Teodora Terry Bailey: Julia Tom Ritter: