Generating a subset model from a model

• US 9,021,417 B2
• Filed: 06/12/2008
• Issued: 04/28/2015
• Est. Priority Date: 07/06/2007
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Clarke, Aidan
• Primary Examiner(s): Zhen, Li B
• Assistant Examiner(s): BODDEN, EVRAL E
• Application Number:
  US12/138,094
• Publication Number:
  US 20090013305A1
• Time in Patent Office: 2,511 Days
• Field of Search: None
• US Class Current: 717/104
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques

Abstract

A technique for identifying a minimum number of model elements associated with a model for generating a subset model of the model that includes receiving a model, a set of model elements and a set of dependency types associated with the model; assigning a collector component to each of the received model elements; locating a model element dependent on the received model element by one of the received dependency types; receiving from each collector a dependent model element, and for each dependent model element, determining whether the dependent model element has been collected by another collector with the same dependency type and updating a subset model list with the collected dependent model element to build a list of collected dependent model elements for generating a subset model in response to a negative determination.

Claims

1. An apparatus for identifying a minimum number of model elements associated with a data model for generating a subset model of the data model, the apparatus comprising:

a central processing unit; and

a storage device coupled to the central processing unit, wherein the storage device stores computer program code, and wherein the processor is configured to execute the computer program code to perform operations, wherein the operations comprise;

assigning a collector from a set of collectors to a model element from a set of model elements for the data model and a dependency type for the assigned model element from a set of dependency types that represent different types of relationships between the model elements, wherein each collector has a set of rules conforming to syntax and semantic rules of a meta-model associated with the assigned model element;

traversing, with each of the collectors, an immediate neighbourhood of the assigned model element by;

identifying an additional dependency type based on the assigned dependency type and the set of rules to identify a model element that is indirectly dependent on the assigned model element; and

for each traversed model element,

in response to determining that the traversed model element is directly dependent on the assigned model element based on the assigned dependency type, recording the traversed model element and the assigned dependency type; and

in response to determining that the traversed model element is indirectly dependent on the assigned model element based on an identified, additional dependency type, recording the traversed model element and the identified, additional dependency type; and

receiving from each of the collectors each recorded, traversed model element to form a subset model list for generating the subset model.

2. The apparatus as claimed in claim 1, wherein a collector from the collectors parses the data model at a starting point of the assigned model element.

3. The apparatus as claimed in claim 1, wherein the operations further comprise:

determining from the dependent model element and the assigned dependency type whether further dependent model elements are required to be located within the data model.

4. The apparatus as claimed in claim 3, wherein the operations further comprise:

in response to determining that further model elements require collection, assigning further collectors from the collectors to collect further dependent model elements by a dependency type.

5. The apparatus as claimed in claim 1, wherein the assigned dependency type is indicative of a relationship between a first model element and a second model element in the data model.

6. The apparatus as claimed in claim 1, wherein the operations further comprise:

maintaining a set of registered collectors, and wherein each of the registered collectors is associated with a type of model element and a dependency type.

7. The apparatus as claimed in claim 1, wherein the operations further comprise:

optimising the subset model list by parsing the subset model list to locate any duplicate dependent model elements by the recorded dependency type in order to produce an optimised list for generating the subset model.

8. A method for identifying a minimum number of model elements associated with a data model for generating a subset model of the data model, the method comprising:

assigning a collector from a set of collectors to a model element from a set of model elements for the data model and a dependency type for the assigned model element from a set of dependency types that represent different types of relationships between the model elements, wherein each collector has a set of rules conforming to syntax and semantic rules of a meta-model associated with the assigned model element;

traversing, with each of the collectors, an immediate neighbourhood of the assigned model element by;

identifying an additional dependency type based on the assigned dependency type and the set of rules to identify a model element that is indirectly dependent on the assigned model element; and

for each traversed model element,

in response to determining that the traversed model element is directly dependent on the assigned model element based on the assigned dependency type, recording the traversed model element and the assigned dependency type; and

in response to determining that the traversed model element is indirectly dependent on the assigned model element based on an identified, additional dependency type, recording the traversed model element and the identified, additional dependency type; and

receiving from each of the collectors each recorded, traversed model element to form a subset model list for generating the subset model.

9. The method as claimed in claim 8, wherein locating further comprises:

parsing the data model at a starting point of the assigned model element.

10. The method as claimed in claim 8, further comprising:

determining from the dependent model element and the assigned dependency type whether further dependent model elements are required to be located within the data model.

11. The method as claimed in claim 10, further comprising:

determining that further model elements require collection; and

receiving from each of the collectors a dependent model element assigning further collectors from the collectors to collect further dependent model elements by a dependency type.

12. The method as claimed in claim 8, wherein the assigned dependency type is indicative of a relationship between a first model element and a second model element in the data model.

13. The method as claimed in claim 8, further comprising:

maintaining a set of registered collectors, and wherein each of the registered collectors is associated with a type of model element and a dependency type.

14. The method as claimed in claim 8, further comprising:

optimising the subset model list by parsing the subset model list to locate any duplicate dependent model elements by the recorded dependency type in order to produce an optimised list for generating the subset model.

15. A computer program product comprising a non-transitory computer readable medium storing computer-readable instructions for identifying a minimum number of model elements associated with a data model for generating a subset model of the data model, wherein the computer-readable instructions, when executed on a processor of a digital computer, perform:

assigning a collector from a set of collectors to a model element from a set of model elements for the data model and a dependency type for the assigned model element from a set of dependency types that represent different types of relationships between the model elements, wherein each collector has a set of rules conforming to syntax and semantic rules of a meta-model associated with the assigned model element;

traversing, with each of the collectors, an immediate neighbourhood of the assigned model element by;

identifying an additional dependency type based on the assigned dependency type and the set of rules to identify a model element that is indirectly dependent on the assigned model element; and

for each traversed model element,

in response to determining that the traversed model element is directly dependent on the assigned model element based on the assigned dependency type, recording the traversed model element and the assigned dependency type; and

in response to determining that the traversed model element is indirectly dependent on the assigned model element based on an identified, additional dependency type, recording the traversed model element and the identified, additional dependency type; and

receiving from each of the collectors each recorded, traversed model element to form a subset model list for generating the subset model.

16. The computer program product as claimed in claim 15, comprising software code portions for performing:

parsing the data model at a starting point of the assigned model element.

17. The computer program product as claimed in claim 15, comprising software code portions for performing:

determining from the dependent model element and the assigned dependency type whether further dependent model elements are required to be located within the data model.

18. The computer program product as claimed in claim 17, comprising software code portions for performing:

determining that further model elements require collection; and

receiving from each of the collectors a dependent model element assigning further collectors from the collectors to collect further dependent model elements by a dependency type.

19. The computer program product as claimed in claim 15, wherein the assigned dependency type is indicative of a relationship between a first model element and a second model element in the data model.

20. The computer program product as claimed in claim 15, comprising software code portions for performing:

maintaining a set of registered collectors, and wherein each of the registered collectors is associated with a type of model element and a dependency type.

21. The computer program product as claimed in claim 15, comprising software code portions for performing:

optimising the subset model list by parsing the subset model list to locate any duplicate dependent model elements by the recorded dependency type in order to produce an optimised list for generating the subset model.