# US 2002/0054155 A1 · Data module design system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2002/0054155 A1
- Document ID: US20020054155A1
- Status: Published application
- Kind: A1
- Application number: 09/906,401
- Filed: 2001-07-16
- Published: 2002-05-09
- Earliest claimed: 2000-07-14
- Assignees: Borland Software Corporation
- Inventors: John Edward Churchill; Rick Nadler; Charles Jazdzewski
- Web page: https://patentgrep.com/patent/US20020054155A1

## CPC

- G06F 3/0481: based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G09G 5/14: Display of multiple viewports
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G09G: ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION (arrangements for transferring data between digital computers and displays G06F3/14; static indicating arrangements comprising an association of a number of separate sources or light control cells G09F9/00; static indicating arrangements comprising integral associations of a number of light sources H01J, H01K, H10H, H05B33/12; scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission, details thereof H04N1/00)

## Abstract

A method for designing a data module presents a series of components in a parentage view of a window on a display, the parentage view being hierarchically arranged with each component occupying a respective position in the hierarchy. A user is enabled to drag one or more of the components displayed in the parentage view into a new position within the hierarchy. As a result, the relationship data among the components in the data module are automatically rearranged once the components are dropped into their respective new positions in the hierarchy.

## Claims

### Claim 1

A method for designing a data module, comprising the steps of:
a) presenting each of a series of components of a data module in a parentage view presented within a window on a display, said parentage view being hierarchically arranged, with each component occupying a respective position in said hierarchy;
b) enabling one or more of said components in the parentage view to be dragged by a user into a new position within the hierarchy; and
c) rearranging automatically the relationship data among said components in the data module once dropped into the new position in the hierarchy.

### Claim 2 (depends on 1)

The method as in claim 1, wherein the parentage view is presented in a first pane of the window and wherein the window comprises at least one additional view.

### Claim 3 (depends on 2)

The method as in claim 2, wherein the additional view is a component view which presents database elements that can be included in the hierarchy.

### Claim 4 (depends on 3)

The method as in claim 3, including the additional step of populating the hierarchy with the database elements.

### Claim 5 (depends on 1)

The method as in claim 1, including the additional step of confirming that the parentage change that would result from dropping one or more of the components into the new position is appropriate, prior to the step of rearranging the relationship data.

### Claim 6 (depends on 1)

The method as in claim 1, including the additional steps of providing the user with a textual description of the data module and permitting a manual edit of a file containing a textual description of the data module that corresponds to the visual presentation of the parentage view.

### Claim 7 (depends on 1)

The method as in claim 1, wherein the data module is a remote data module compatible with an application that includes three or more tiers.

### Claim 8 (depends on 2)

The method as in claim 2, wherein the additional view is a data diagram view which presents a data diagram of database elements.

### Claim 9 (depends on 8)

The method as in claim 8, including the additional step of populating the data diagram with database elements.

### Claim 10 (depends on 9)

The method as in claim 9, wherein the population step is by a drag and drop operation from the parentage view into the data diagram.

### Claim 11 (depends on 8)

The method as in claim 8, wherein the database elements have relationships and dependencies, the relationships and dependencies being graphically represented in the data diagram.

### Claim 12 (depends on 11)

The method as in claim 11, wherein the relationships and dependencies of the database elements are created and deleted by editing the graphic representations.

### Claim 13 (depends on 9)

The method as in claim 9, wherein the database elements have relationships and dependencies, the relationships and dependencies being graphically represented in the data diagram.

### Claim 14 (depends on 13)

The method as in claim 13, wherein the relationships and dependencies of the database elements are created and deleted by editing the graphic representations.
