Paradigms / We will use common paradigms for the design of your software. There is no good, bad, ideal or generally applicable programming paradigm. We follow a pragmatic approach and will use the most suitable paradigm for the respective problem area and the relevant software environment in agreement with our customer.

When the solution approach allows for alternatives, we will discuss those with you. When different solutions provide equivalent advantages, we will tend to prefer object-orientated, declarative and generic approaches.

Quality assurance / Each project is different and has its own dynamics and safety relevance. We will select the appropriate methods and procedures for quality assurance and combine them in an integrated package. The implementation of extensive software tests, including test-driven development, is relatively expensive, but your investment in our selection of quality-building measures will be worthwhile: follow-up costs for the removal of faults at the end of the development process are reduced and resource planning becomes significantly more reliable.

Our frequent participation in projects in the defence environment has made us familiar with the use of standardised quality models (V-models) to achieve high and exceptionally high requirements regarding fault-free software. This may, on the other hand, improve innovative developments in a project when the less safety-critical components are not developed in a test-centred manner.

Technologies / Our specialists have been working on projects in various industrial sectors for over 15 years.

We are therefore familiar with all common and popular technologies that were used in the last one-and-a-half decades. But for us, this is not a reason to relax. We use our solid technological competence as a basis to explore the future. We stay current through focused study of all important, current trends in software technology. We regularly test new developments to determine whether they might be of use in our software projects.

Here is one example: we decided to use the Open Architecture Ware platform instead of the common XML processors in the A400M project and have managed to establish the automated generation of models (controllers, sensors, etc.) from XML-based interface descriptions with a high level of reusability.

Languages / The anyvex development team focuses on object-oriented and declarative languages. Intuitive GUIs are preferably created with Qt4 or C# (Windows .NET). Recent applications in the Java environment used application frameworks.

Our customer EADS uses the TSD (Tactical Scenario Display) developed by anyvex for the simulation of flight manoeuvres. It allows a view of the manoeuvre on loadable map material, similar to Google Earth. We managed to provide the TSD within a relatively short period, as we based it on the ANYCLIPSE framework, which was also developed by us and in turn builds on the Eclipse Rich Client Platform.