Browse Prior Art Database

Metadata Driven Application Execution

IP.com Disclosure Number: IPCOM000127316D
Original Publication Date: 2005-Aug-22
Included in the Prior Art Database: 2005-Aug-22
Document File: 3 page(s) / 39K

Publishing Venue

IBM

Abstract

Disclosed is a method of using an application model to execute a targeted application without the need for custom software development, thus saving time on programming and debugging efforts. The software tools that implement the proposed concept will utilize a new class of software, called the Application Engine

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

Metadata Driven Application Execution

Main Idea

Disclosed is a method of using an application model to execute a targeted application without the need for custom software development, thus saving time on programming and debugging efforts. The software tools that implement the proposed concept of Metadata Driven Application eXecution (MDAX) will utilize a new class of software, called the Application Engine (AE).

Novelty of the Invention

Application modeling using UML and other modeling languages has been employed for many years to document application requirements and to design software. Some modeling tools can generate code in a programming language that serves as a starting point of the application development phase. A modeling approach for enterprise applications described in the patent [*] supports code generation that may not require changes before being compiled for the execution.

The disclosed MDAX method enables execution of an application without the need for any software development or code generation. Instead, after the application model is saved in a metadata format, the AE enables application execution by interpreting this metadata.

Details of the Invention

The MDAX concept is based on the assumption that an application model saved in a metadata format (e.g. XML) can describe all functional requirements of a computer application.

Application Analyst Admin User Application User

Application Model

 Application Requirements

Meta-

Model

Modeling

Tool

Application Engine

Application Data

                    Run Time Environment Development Environment

Figure: MDAX Development and Run-Time Environment

Application Model

Application Data

External

Event

System

Event

1

[This page contains 4 pictures or other non-text objects]

Page 2 of 3

The Metadata Driven Application development phase is diagrammed on the left side of the Figure. The role of the Application Analyst in this diagram is to convert the functional requirements of a computer application into the Application Metadata. Content and syntax of the metadata often described by an XML schema for the Meta Model and may vary depending on the type of application domain. A modeling tool can provide a convenient user interface and validate the syntax of the application model.

The most common metadata elements are:
1. An Application Data Vocabulary representing the application Data Model
2. Application Processes (or workflows) representing the application Process Model
3. User Roles defining access rights to application data and processes
4. A Custom Presentation describing the User Interface of the application

The MDAX Run-time environment is described by the right part of the Figure. When the first us...