e DEP User Group e DEP Development Mike

  • Slides: 12
Download presentation
e. DEP User Group e. DEP Development Mike Vere, Graffica Ltd © Graffica Ltd

e. DEP User Group e. DEP Development Mike Vere, Graffica Ltd © Graffica Ltd

Who we are Graffica founded in 2000 n Based in Malvern, UK n Grown

Who we are Graffica founded in 2000 n Based in Malvern, UK n Grown to 15 employees n First class software development skills n Broad range of ATM knowledge n Pioneered outsourcing concept at EEC n Specialise in ATM systems n 2

e. DEP Objectives Light weight portable ATM platform n Scaleable n Extensible and flexible

e. DEP Objectives Light weight portable ATM platform n Scaleable n Extensible and flexible n Reliable n Reusable n Shared software base n Cost effective n Project synergy n 3

Development of e. DEP FLIGHT SIM AVT e. COCKPIT STORIA /SAT e. DEP Air

Development of e. DEP FLIGHT SIM AVT e. COCKPIT STORIA /SAT e. DEP Air SPD ECHOES CORA GSDK Prototype e. DEP AEG e. DEP Ground e. DEP TWR NATS OCEANIC CIMACT HMI IANS PTT/RST FASTI LARA TCT ITWP 1999 2000 2001 2002 2003 2004 TCAS DMAN 2005 2006 2007 TOWSIM 3 D 2008 2009 4

Tools and current developments PVT n STORIA SAT n Map editor n Resource editor

Tools and current developments PVT n STORIA SAT n Map editor n Resource editor n Microsoft Flight Simulator n Project Management Tools, TMS n Automatic testing tools, Hudson n 5

Project Management Objectives n Manage software growth On site Level 1 support provided at

Project Management Objectives n Manage software growth On site Level 1 support provided at EEC n Regular delivery cycle, and Level 2 support n Regression and automated testing n n Exploit existing software base Develop software to be reusable n Constant improvement and redesign n n Remain responsive, look for feedback Short development cycle n Regular intermediate deliveries, prototypes n 6

Layered Software Structure Experiment Trainer Concept Prototype Operational e. DEP Graphics/Live/Extension Modules (CWP/PWP/Recording/BADA/ARTAS) e.

Layered Software Structure Experiment Trainer Concept Prototype Operational e. DEP Graphics/Live/Extension Modules (CWP/PWP/Recording/BADA/ARTAS) e. DEP Core ATC Modules (Airspace/FDPS/RDPS/Air/Datalink/ADSB/Tools) Graffica System Development Kit (Simulation Kernel, Events, Graphics, Middleware) Java Platform API Operating System (Linux, Windows, HP/ux, Solaris, Mac) 7

Development Lifecycle n n Premise: Requirements will change Task driven incremental software development n

Development Lifecycle n n Premise: Requirements will change Task driven incremental software development n n n n n Project plan Initial design and test plan Initial development Create test scripts Re-plan Review design (software and tests) Software re-code and re-factoring Regression test Update documentation Incremental Delivery Client Feedback 8

Relationship with ESCAPE n Complementary platforms n n n Benefits to ESCAPE n n

Relationship with ESCAPE n Complementary platforms n n n Benefits to ESCAPE n n n Early evaluation of concept Small scale trials Iterative approach to concept development Results fed into ACE component development ACE/e. DEP Gateway: AEG n n ACE hi fidelity – but long development cycle e. DEP low fidelity – but functional, short development cycle Hi fidelity calculations from ACE Prototyped HMI using e. DEP Interoperable components – TCT server Support to ESCAPE n n ACE lifecycle upgrades Wrapping e. DEP components using ACE API 9

Project Synergy n Shared, open software base enables n n Core software and thin

Project Synergy n Shared, open software base enables n n Core software and thin projects n n n Clients to trust software Projects to share common costs Produce a very wide functional capability Core software developed once Configured for different clients Projects contribute to core development e. DEP community benefits Examples: STORIA, RST, TCT, CIMACT 10

Issues n How to keep software in step Multiple projects sharing same code base

Issues n How to keep software in step Multiple projects sharing same code base n Careful planning n Synchronisation of clients’ requirements n Review of client timescales and objectives n n Management of diverse requirements Rapid prototyping n Medium scale simulation n Certificated training n Operational systems n 11

Conclusion n e. DEP works because clients contribute n n n Development needs client

Conclusion n e. DEP works because clients contribute n n n Development needs client feedback Progress is easily reported back to clients Possibility to re-use software across different projects Rapid concept development possible Software reuse across different projects User group can provide visibility for n n New components Additional functionality Supplementary tools Gateways to third party software 12