Presentation of ApplicationIQ

ApplicationIQ is a simple to use tool, that allows to optimize the exploitation of your application assets. It intervenes at all periods of the life cycle.

A software is strategic when the company is heavily dependent to it. Strategic software must adapt along several axes:

  • by integrating new features,

  • by executing on new platforms,

  • by using new technologies.

ApplicationIQ responds to these issues in your development context.

Key benefits

  • Capitalization of the steady know-how integrated in projects, by specifying it independently of platforms and languages.

  • Sustainability of software investments by adapting only phases of the process which must change. For example, in the case of a portage, it is not necessary to change all the work done in the upstream stages, up to the design phase of PSM "Platform Specific Model".

  • Exploitation of a common structure for all your projects (from the documentation to the source code) for greater efficiency for your development teams.

  • Real creation of application assets of your company.

  • Facilitating the implementation and control of your projects.

  • Easier Maintenance of your projects.

  • Standardization format of communication of your projects, for a gain in efficiency, scalability, maintainability...

What you can do ...

  • Easily exploit the fondamentals of MDA (Model Driven Architecture) and MDE (Model Driven Engineering)

  • Adapt your existing projects to MDA or MDE

  • Make reverse engineering knowing "by what end" take the problem

  • Make porting from one platform to another (Ex: Windows to Cloud)

  • Make very simply analyses of impacts

  • And much more, according to your imagination...

Key features

  • Specification:

    • Specification of the processus of development

    • Specification of modeling rules

    • Specification of navigation modes

  • Exploitation:

    • Conventional navigation:

      • Cross forward (from the artifacts of an activity to another related activity downstream artifacts), for example from requirements to implementation classes (sources).

      • Cross backwards (from the artifacts of an activity to artifacts of another related activity upstream), for example from implementation classes (sources) to requirements.

    • "Completeness" navigation, very useful and very effective in reverse-engineering projects, retro-documentation projects ...

      • Forward, for example to answer to the questions of the type "what are the use cases that result only partially to an implementation (which comes to identify the use cases only partially developed)?" ; "What are the artifacts that are not followed by any entity in the following activities? '' (which means that they are not developed) », …

      • Backward, for example to answer to the question "what are the classes that are not associated to any requirement? '' (which means that they are not documented), "what are the components that are only partially documented in the requirements"...

  • Tools for model stereotyping, particularly effective and helpful in reverse engineering and for the integration of an existing project, currently independent of the standard process of the company :

    • Tool for the assignment of stereotypes to entities

    • Tool for the assignment of stereotypes to relations