MODELING AND VISUALIZING LEVEL-BASED HIERARCHIES

• US 20150193519A1
• Filed: 01/09/2014
• Published: 07/09/2015
• Est. Priority Date: 01/09/2014
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Mandelstein, Dan J., Pandit, Sushain, Palaniappan, Subramanian, Woolf, Olena, Xu, Fenglian
• Application Number:
  US14/150,808
• Publication Number:
  US 20150193519A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: G06F 16/367 Ontology

Abstract

Flexibly modeling and visualizing a level-based hierarchy. A first level set and a second level set are identified from a first data set and a second data set in a first domain and a second domain, respectively. A first relationship type to be used between the first level set and the second level set is received. A first hierarchy is formalized, including at least the first level set and the second level set joined in a hierarchical relationship according to the first relationship type.

Claims

1-8. -8. (canceled)

9. A computer program product comprising software stored on a software storage device, the software comprising:

first program instructions programmed to identify a first set of machine readable data including a first level set from a first domain;

second program instructions programmed to identify a second set of machine readable data including a second level set from a second domain;

third program instructions programmed to receive a first relationship type to be used between the first level set and the second level set; and

fourth program instructions programmed to formalize a first hierarchy, including at least the first level set and the second level set joined in a hierarchical relationship according to the first relationship type;

wherein;

the software is stored on a software storage device in a manner less transitory than a signal in transit.

10. The product of claim 9 wherein the fourth program instructions are further programmed to receive user input identifying the first relationship type.

11. The product of claim 9 further comprising:

the fourth program instructions further programmed to further formalize the first hierarchy by designating a first relationship definition specifying substance of a relationship according to the first relationship type.

12. The product of claim 11 wherein the software further comprises:

fifth program instructions programmed to render a visual image of the first hierarchy wherein the first relationship definition is implicit in the visual image.

13. The product of claim 9 wherein:

the first level set comes from a first data storage system; and

the second level set comes from a second data storage system with the second data storage system being different from the first data storage system.

14. The product of claim 11 wherein the software further comprises:

fifth program instructions programmed to identify a third set of machine readable data including a third level set;

sixth program instructions programmed to receive a second relationship type to be used between the second level set and the third level set;

seventh program instructions programmed to designate a second relationship definition specifying substance of a relationship according to the second relationship type; and

eighth program instructions programmed to further formalize the first hierarchy, including the third level set, according to the second relationship type and the second relationship definition;

wherein;

the first relationship definition has a type and/or cardinality that is different from the second relationship definition.

15. A computer system comprising:

a processor(s) set; and

a software storage device;

wherein;

the processor set is structured, located, connected and/or programmed to run software stored on the software storage device; and

the software comprises;

first program instructions programmed to identify a first set of machine readable data including a first level set from a first domain;

second program instructions programmed to identify a second set of machine readable data including a second level set from a second domain;

third program instructions programmed to receive a first relationship type to be used between the first level set and the second level set; and

fourth program instructions programmed to formalize a first hierarchy, including at least the first level set and the second level set joined in a hierarchical relationship according to the first relationship type.

16. The system of claim 15 wherein the fourth program instructions are further programmed to receive user input identifying the first relationship type.

17. The system of claim 15 wherein the software further comprises:

the fourth program instructions further programmed to further formalize the first hierarchy by designating a first relationship definition specifying substance of a relationship according to the first relationship type.

18. The system of claim 17 wherein the software further comprises:

fifth program instructions programmed to render a visual image of the first hierarchy wherein the first relationship definition is implicit in the visual image.

19. The system of claim 15 wherein:

the first level set comes from a first data storage system; and

the second level set comes from a second data storage system with the second data storage system being different from the first data storage system.

20. The system of claim 17 wherein the software further comprises:

fifth program instructions programmed to identify a third set of machine readable data including a third level set;

sixth program instructions programmed to receive a second relationship type to be used between the second level set and the third level set;

seventh program instructions programmed to designate a second relationship definition specifying substance of a relationship according to the second relationship type; and

eighth program instructions programmed to further formalize the first hierarchy, including the third level set, according to the second relationship type and the second relationship definition;

wherein;

the first relationship definition has a type and/or cardinality that is different from the second relationship definition.