With the maturing of programming models and the need for absolute AGILITY in the business environment, it has become of paramount importance to separate the database layer (Model), the User Interface/User Experience (View) and business unique logic (Controller), to facilitate very rapid response to maintenance requests.
In old style heritage applications, all three these elements were present in large, monolithic programs, which made maintenance quite complex, slow and error prone. This approach also caused business unique functionality, which very often provided competitive advantage, to be “lost” in the code, due the sheer size of these programs. These programs, although providing tremendous functionality, have become extremely difficult to maintain.
Another fundamental consideration is that single instances of discrete functionality should be available for re-use. In heritage applications a lot of duplication of core business rules occurred (for example, VAT calculations, handling fee calculations, etc.), simply due to constraints in early programming models. Identifying all these occurrences and maintaining them cohesively is extremely time consuming and error prone.
Separating the database functions, leveraging latest database technology (data validations, constraints, triggers), from delivery channels (UI/UX) and encapsulating business unique rules delivers a highly AGILE application, whilst unleashing the “hidden” value of the investment in heritage systems.
As a result of this separation and encapsulation process, IT development teams can become dramatically more responsive to business changes, supporting their business in becoming more AGILE and competitive.
It is very important to understand that with the AO technology and Roadmap we believe that two initiatives hold incredible promise for the platform: ROA (Rational Open Access for RPG) and the OA Metadata Open Standard.
By enriching the underlying Metadata, attributes such as standard icons, behaviour, URL’s, fonts, colours, etc. can be gradually added to the Metadata and gradually populated throughout the database and be dynamically used to improve the UI/UX, including reporting, etc. Again this provides for dramatic improvement in productivity, facilitating a much more AGILE delivery platform.
The AO Product and Roadmap facilitates the leveraging of the Open Access philosophy.