Browse Prior Art Database

Object Oriented Data Management Framework

IP.com Disclosure Number: IPCOM000015572D
Original Publication Date: 2002-Apr-25
Included in the Prior Art Database: 2003-Jun-20
Document File: 5 page(s) / 141K

Publishing Venue

IBM

Abstract

The aim is to develop a data management system for a simple or complex table in a Client/Server environment. The methodology for Analysis and Design is UML and the project needs to have a low cost and a high level of quality. The Presentation, Business and Persistence issues have to be separated.

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 50% of the total text.

Page 1 of 5

Object Oriented Data Management Framework

The aim is to develop a data management system for a simple or complex table in a Client/Server environment. The methodology for Analysis and Design is UML and the project needs to have a low cost and a high level of quality. The Presentation, Business and Persistence issues have to be separated.

  The solution is to implement a Framework containing all the common data management base classes.

Applications will extend these base classes in a rather easy way.

Disclose are methods and process called "ENABLING TECHNOLOGY - PROCESS OPTIMIZATION".

  This structured framework allows the process and control serialization in data entry application development. The result is a high level of productivity and quality, with low programmers' skills.

The steps are:

* in an inception phase, an architect will define and help implement the framework.

This person will also implement the basic business model;
* human resources with limited skills and little Java knowledge, will then implement

GUI classes and Data Access components;

The framework ensures the respect of standard design and rules, as well as system logical consistency and inner coherence. It also allows to respond to specific application needs and to easily customize or refactor the Presentation Logic. The inheritance of the framework classes allows a high re-use of code, in an open fashion, supporting aggregation in a second instance together with the use of Design Patterns.

Technical Description:Framework

  The framework is based on a simplified implementation strategy of the well-known pattern Model/View/Controller (MVC). Every dialog must follow the same basic pattern, which consists of three classes:

* Model: this component groups information and its business processing rules.

The model can be stored, so its components can be re-used. In this specific case,

a persistence layer saves the data model in the physical database.
* View: this is the external layer, the end-user interface. It contains all the graphic

components (fields, lists, buttons, tables etc.).
* Controller: this layer of software interprets the actions of the end-user and acts as

a link between the View and the Model.

1

Page 2 of 5

PRESENTATION

DATA LOGIC BUSINESS LOGIC LOGIC

CONTROLLER MODEL

VIEW

PERSIST

DataBas

  The framework has a main layer, mainly consisting of interfaces. This predefines the structure and ensures that the developers follow a three-level logic (MVC). Furthermore, the framework produces some abstract classes, working as adapters, which in turn are the basis for the specific classes.

Figure 1: Three-layered Architecture

<<interface

Viewa

(from

<<interfac

Controlla

(from

<<interface>

Modela

(from

<<interface>

Persista

(from

<<abstract

AbstractVi

(from

<<abstract

AbstractContr

(from

<<abstract

AbstractMo

(from

<<abstract

AbstractPer

(from

IwsPa

(from

CRUDMach

(from

ConnectionMan

(from

1..

1

IwsVie

(from

IwsControl

(from

1

1

1

1

IwsMo

(from

IwsPers

(from

1..

1..

Figur...