Browse Prior Art Database

A Top-down Solution Oriented Pattern Driven Database Design Methodology

IP.com Disclosure Number: IPCOM000199130D
Publication Date: 2010-Aug-26
Document File: 3 page(s) / 72K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for a top-down solution-oriented database design approach which captures, describes, and enforces the inter-relationships and constraints explicitly at the solution runtime level. This reduces the errors and inconsistencies associated with the component-centric bottom-up approach of traditional database design.

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

A Top-down Solution Oriented Pattern Driven Database Design Methodology

With service-oriented architecture (SOA), companies usually offer families of stacked or

related products (p). Each product in the stack consists of a number of related

components (c). Many components are required to support a number of databases (d). Generally, each product and component is owned by different teams, where each team

designs the component database in their own way. As a result, developers could end up

repeating the same database design process for many times in the order of Σ(p,c,d). This repetitive development style causes problems such as:
• huge productivity losses
• inconsistent database supports across components and products
• inconsistency within a single component database design


A solution runtime environment usually contains a number of related database

components. Those database components usually obey certain rules regarding their

inter-relationships, dependencies and constraints bound by the system. Those rules

dictate how the component databases can be created, grouped and sliced. Traditionally the database design is component centric; i.e. each component designs

and configures the database individually from the bottom up. As a result, the constraints

and relationships among the database components are not captured, described, and

enforced explicitly. This component level bottom-up approach not only makes the

database design and configuration tedious and lengthy but also could leave database

components in the system in erroneous, incoherent and inconsistent states.

This invention describes a new top-down solution-oriented database design approach

which is able to capture, describe, and enforce the inter-relationships and constraints

explicitly at the solution runtime level. To avoid the duplicate and inconsistent methods

of database design and consumption in a product family, the invention introduces the

generic metadata driven database support framework which allows each component to

declare and describe its supported databases in metadata xml consistently across

components and products in a family. Hence database designs can be supported by the

framework consistently for each component and shared by all c...