Browse Prior Art Database

Structure-centered data model Disclosure Number: IPCOM000016134D
Original Publication Date: 2002-Nov-01
Included in the Prior Art Database: 2003-Jun-21
Document File: 3 page(s) / 136K

Publishing Venue



Structure-Centered Data Model

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

Page 1 of 3

Structure-centered data model

Structure-Centered Data Model

1. Objective

 With most ill designed applications, new business requirements or new product introductions necessitate changes in the business logic contained within applications. Such changes require significant resources of an IT department. Because of such challenges, time to implement change or the time to market a product is of critical concern from an information technology perspective. Hence, the need for new ways of designing data model which can adapt quickly and flexibly to change is evident.

2. Benefits

 1) By adapting to change quickly, cost reduction effects are evident and is able to market new products faster than competitors.

 2) Because of its flexible structure, new forms of business logic do not impact the existing application structure.

 3) Because the method of representing logic is identical, changes in maintenance personnel can be easily managed.

4) Because the system is not restricted to a certain industry, it can be applied to all industries.

3. Current Technique

 The traditional approach of accommodating changes to business logic is to manage logic defined in programs or to manage data within database tables. Changes to logic require significant amount of time from impact analysis to implementation. The same is also true for database tables; however, database tables being static by nature only allow access through certain applications. Inevitably, accommodating changes or introducing new products requires additional resources

4. Solutions :Implement a database structure that does not change (structure-centered data model)

 1) The implemented model of the rule system must be represented in the form of structures; and not in the form of processes or objects. Process-centered models require changes to the model itself when in time of new processes or process changes. Furthermore, object-centered models which may have less impact from process changes require that each object be represented; introducing data redundancies and replications. Structure-centered models are simple and require changes only when new types of structures are introduced.