iQgen Overview
Automate Repetitive Tasks and Increase Conformance to Architectural Guidelines
Usually, a system's technical software architecture is defined in prose, leading to huge documents that need to be read, understood and applied by every developer. Examples include how to persist objects, how to implement relations, how to manage life cycle, etc. This leads to a huge amount of effort required to implement functionality not only correct, but also architecture conformant. iQgen can automate most of the tasks and allows the developer to focus on the implementation of functional requirements. iQgen is not exclusively a manager's or analyst's tool. Because the templates are specified using Java ServerPages (JSP) syntax, they can be edited along-side with Java and other implementation code, enabling developers to use meta-programming for repetitive tasks.
Turn Architectural Rules Templates
iQgen allows organizations that develop enterprise applications to focus on the essential: the business domain model and the implementation of functional requirements. Architectural rules are specified as templates. iQgen applies the templates to a model and thus transforms it into implementation artifacts, preserving existing information.
Support for OMG's Model Driven Architecture
iQgen supports development according to OMG's Model Driven Architecture (MDA) initiative. You can design your Platform Independent Model (PIM) using standard CASE tools and use iQgen to transform it into a Platform Specific Model (PSM) implementation. By factoring out architectural rules into templates, changes in technology or infrastructure components can easily be incorporated - and in most cases, this can be done without touching existing models or implementation code.
Built from knowledge gained in large-scale, mission-critical development efforts
While doing consulting for major companies, innoQ has built and used several different software generators. iQgen is the tool we would have liked to have: Focusing on what is really needed, easy to integrate into a standards-based development process, and, most importantly, not taking away decisions from the project's staff by assuming to know the right architecture that works everywhere.
