Method and computer system for isolating and interrelating components of an application

• US 20030088643A1
• Filed: 06/04/2002
• Published: 05/08/2003
• Est. Priority Date: 06/04/2001
• Status: Abandoned Application

• Current Assignee: Sentiat Technologies Incorporated
• Original Assignee: Sentiat Technologies Incorporated
• Inventors: Swartz, Jonathan, Shupps, Eric A., Wilson, Kirk H.
• Application Number:
  US10/161,924
• Publication Number:
  US 20030088643A1
• Time in Patent Office: Days
• US Class Current: 709/218
• CPC Class Codes: G06F 11/3414 Workload generation, e.g. scripts, playback
• CPC Class Codes: G06F 11/3447 Performance evaluation by modeling
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/87 Monitoring of transactions
• CPC Class Codes: G06F 8/75 Structural analysis for program understanding

Abstract

A system and method of generating information regarding an application designed to be used over a network can be used for parsing the code of the application into its various components and determining relationships between the components, which make up the code. The code of an application can be analyzed to determine which components of the application are transactable and which are non-transactable. Furthermore, contextual and cross-contextual relationships between the components and the code of the application may be defined. The components can be portions of a document, which can in turn be part of a larger application. Information regarding the components of the application, and therefore the application as a whole, such as the functionality/performance of components and component relationships, can be determined and may be posted to a data store for later retrieval and processing.

Claims

1. A method of collecting information about an application, comprising:

parsing code of the application to identify components within the code; and

collecting data on the identified components.

2. The method of claim 1, further comprising defining relationships between the identified components.

3. The method of claim 2, further comprising further identifying any of the identified components as transactable components.

4. The method of claim 3, wherein identifying any of the identified components as transactable components further comprises reviewing each identified component against a transactable component criteria.

5. The method of claim 4, wherein each identified component has at least one of a property, method, attribute or parameter and wherein the transactable component criteria is a property criteria, a method criteria, an attribute criteria, a parameter criteria, or a combination of one or more of a property criteria, a method criteria, an attribute criteria, and a parameter criteria.

6. The method of claim 2, wherein defining the relationships between the identified components further comprises defining contextual relationships between the identified components.

7. The method of claim 2, wherein defining the relationships between the identified components further comprises defining cross contextual relationships between the identified components.

8. The method of claim 1, wherein parsing the code further comprises parsing the code using a DOM parser, and wherein the method further comprises:

returning a DOM for the code; and

querying the DOM for a component collection.

9. The method of claim 1, wherein parsing the code further comprises parsing the code using a regular expression parser, and wherein the method further comprises:

returning a parsed version of the code having a set of components; and

grouping the parsed components into a component collection.

10. The method of claim 1, wherein the application comprises a plurality of documents and each step of claim 1 is performed on each document within the application.

11. The method claim 1, further comprising retrieving the code of the application.

12. The method of claim 11, further comprising storing the collected data.

13. The method of claim 11, wherein retrieving the code further comprises issuing a request to a host for a document.

14. The method of claim 13, wherein the request is issued over a network.

15. The method of claim 14, wherein the request is issued from a client computer to a server computer.

16. The method of claim 15, wherein the request is an HTTP GET request issued by a browser.

17. The method of claim 11, wherein the code is rendered.

18. The method of claim 6, wherein the application comprises a document and wherein parsing the code further comprises returning a collection of components for the document, and wherein defining contextual relationships between the identified components further comprises:

assigning each component collection a one to one relationship with the document;

assigning each identified component within the component collection a one to one relationship to the component collection of which the identified component is a part;

assigning each identified component within the component collection a one to one relationship to the document of which the component collection is a part; and

identifying whether any of the identified components within the component collection are identical to any other identified component and, for any of the identified components that match another identified component,

assigning the matching identified component within the component collection a many to one relationship to the component collection of which the matching identified component is a part; and

assigning the matching identified component within the component collection a many to one relationship to the document of which the component collection is a part.

19. The method of claim 7, wherein the application comprises a set of documents and where parsing the code further comprises returning a collection of components for each document, and wherein defining cross contextual relationships between the identified components further comprises, for each identified component within the component collection:

determining whether the identified component is a transactable component;

extracting an execution result for each transactable component;

grouping together all transactable components that have a single execution result;

examining a parentage for each group of transactable components to identify a parent document for each group of transactable elements;

for any groups of transactable components having an identical parentage, identifying a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components; and

for any groups of transactable components not having an identical parentage, identifying a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components and as having a one to many relation to a set of parent documents for the group of transactable components.

20. The method of claim 19, further comprising:

for each non-transactable component, determining whether the identified component matches any other of the identified components in the component collection;

for each matching non-transactable component, determining whether the matching components have an identical parentage; and

identifying each component of a set of matching non-transactable components that do not have identical parentage as having a one to many relation to a set of parent documents.

21. A method of defining relationship among a set of components of a document in an application, comprising:

determining if a collection of components exists for the document;

identifying individual components within the collection of components; and

defining a relationship between the identified individual components.

22. The method of claim 21, further comprising:

determining if any of the identified individual components within the collection of components are identical to one another.

23. The method of claim 21, wherein defining the relationships between the identified components further comprises defining contextual relationships between the identified components.

24. The method of claim 21, wherein defining the relationships between the identified components further comprises defining cross contextual relationships between the identified components.

25. The method of claim 23, wherein defining contextual relationships between the identified components further comprises:

assigning each component collection a one to one relationship with the document;

assigning each identified component within the component collection a one to one relationship to the component collection of which the identified component is a part;

assigning each identified component within the component collection a one to one relationship to the document of which the component collection is a part; and

identifying whether any of the identified components within the component collection are identical to any other identified component and, for any of the identified components that match another identified component,

assigning the matching identified component within the component collection a many to one relationship to the component collection of which the matching identified component is a part; and

assigning the matching identified component within the component collection a many to one relationship to the document of which the component collection is a part.

26. The method of claim 24, wherein defining cross contextual relationships between the identified components further comprises, for each identified component within the component collection:

determining whether the identified component is a transactable component;

extracting an execution result for each transactable component;

grouping together all transactable components that have a single execution result;

examining a parentage for each group of transactable components to identify a parent document for each group of transactable elements;

for any groups of transactable components having an identical parentage, identifying a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components; and

for any groups of transactable components not having an identical parentage, identifying a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components and as having a one to many relation to a set of parent documents for the group of transactable components.

27. The method of claim 26, further comprising:

for each non-transactable component, determining whether the identified component matches any other of the identified components in the component collection;

for each matching non-transactable component, determining whether the matching components have an identical parentage; and

identifying each component of a set of matching non-transactable components that do not have identical parentage as having a one to many relation to a set of parent documents.

28. The method of claim 26, wherein determining whether the identified component is a transactable component further comprises reviewing each identified component against a transactable component criteria.

29. The method of claim 28, wherein each identified component has at least one of a property, method, attribute or parameter and wherein the transactable component criteria is a property criteria, a method criteria, an attribute criteria, a parameter criteria, or a combination of one or more of a property criteria, a method criteria, an attribute criteria, and a parameter criteria.

30. The method of claim 21, wherein identifying individual components within the collection of components further comprises parsing code of the application to identify individual components within the code;

and collecting individual components the document into a collection of components.

31. The method of claim 30, wherein parsing the code of the application further comprises parsing the code using a DOM parser, and wherein the method further comprises:

returning a DOM for the code; and

querying the DOM for a collection of components.

32. The method of claim 30, wherein parsing the code further comprises parsing the code using a regular expression parser, and wherein the method further comprises:

returning a parsed version of the code having a set of components; and

grouping the parsed components into a collection of components.

33. The method of claim 30, further comprising collecting data on the identified components.

34. The method of claim 21, wherein the collection of components is either an overall collection or a collection of a specific type of component.

35. The method of claim 21, further comprising:

assigning a unique ID to each individual component; and

constructing each unique ID from properties, methods, and/or values assigned to each individual component.

36. A method of identifying a set of transactable components within an application having a set of components, comprising:

parsing code of the application to identify the set of components within the application; and

reviewing each component in the set of components against a transactable component criteria; and

identifying each component in the set of components that is a transactable component.

37. The method of claim 36, wherein the transactable component criteria comprises at least one characteristic associated with transactable components, and wherein reviewing each component in the set of components against a transactable component criteria further comprises determining whether or not each component has the at least one characteristic.

38. The method of claim 37, wherein the at least one characteristic associated with a transactable component further comprises at least one of a property, method, attribute or parameter.

39. The method of claim 38, wherein the transactable component criteria further comprises at least one of a property criteria, a method criteria, an attribute criteria, a parameter criteria associated with a transactable component, or a combination of one or more of a property criteria, a method criteria, an attribute criteria, and a parameter criteria associated with a transactable component.

40. The method of claim 36, wherein identifying transactable components further comprises matching a criterion with a component.

41. The method of claim 40, wherein the criterion is one of a property, method, attribute, or parameter criteria.

42. The method claim 36, further comprising:

defining contextual and cross contextual relationships among the components.

43. The method of claim 42, wherein defining contextual relationships between the identified components further comprises:

assigning each component collection a one to one relationship with the document;

assigning each identified component within the component collection a one to one relationship to the component collection of which the identified component is a part;

assigning each identified component within the component collection a one to one relationship to the document of which the component collection is a part; and

identifying whether any of the identified components within the component collection are identical to any other identified component and, for any of the identified components that match another identified component,

assigning the matching identified component within the component collection a many to one relationship to the component collection of which the matching identified component is a part; and

assigning the matching identified component within the component collection a many to one relationship to the document of which the component collection is a part.

44. The method of claim 42, wherein defining cross contextual relationships between the identified components further comprises, for each identified component within the component collection:

determining whether the identified component is a transactable component; and

for each transactable component;

extracting an execution result for each transactable component;

grouping together all transactable components that have a single execution result;

examining a parentage for each group of transactable components to identify a parent document for each group of transactable elements;

for any groups of transactable components having an identical parentage, identifying a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components; and

for any groups of transactable components not having an identical parentage, identifying a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components and as having a one to many relation to a set of parent documents for the group of transactable components.

for each non-transactable component;

determining whether the identified component matches any other of the identified components in the component collection;

for each matching non-transactable component, determining whether the matching components have an identical parentage; and

identifying each component of a set of matching non-transactable components that do not have identical parentage as having a one to many relation to a set of parent documents.

45. A computer program stored on a tangible medium and comprising computer or machine readable program components translatable or executable to:

parse code of an application to identify components within the code; and

collect data on the components identified.

46. The computer program of claim 45, further translatable or executable to:

define relationships between the identified components.

47. The computer program of claim 46, further translatable or executable to:

further identify any of the identified components as transactable components.

48. The computer program of claim 47, further translatable or executable to:

review each identified component against a transactable component criteria to identify any of the identified components as transactable components

49. The computer program of claim 48, wherein each identified component has at least one of a property, method, attribute or parameter and wherein the transactable component criteria is a property criteria, a method criteria, an attribute criteria, a parameter criteria, or a combination of one or more of a property criteria, a method criteria, an attribute criteria, and a parameter criteria.

50. The computer program of claim 46, wherein to define the relationships between the identified components the computer program is further translatable or executable to:

define contextual relationships between the identified components.

51. The computer program of claim 46, wherein to define the relationships between the identified components the computer program is further translatable or executable to:

define cross contextual relationships between the identified components.

52. The computer program of claim 45, wherein a DOM parser is used to parse the code, and wherein the computer program is further translatable or executable to:

return a DOM for the code; and

query the DOM for a component collection.

53. The computer program of claim 45, wherein a regular expression parser is used to parse the code, and wherein the computer program is further translatable or executable to:

return a parsed version of the code having a set of components; and

group the parsed components into a component collection.

54. The computer program of claim 45, wherein the application comprises a plurality of documents and the computer program is further translatable or executable to:

perform on each document within the application.

55. The computer program of claim 45, further translatable or executable to:

retrieve the code of the application.

56. The computer program of claim 55, further translatable or executable to:

store the collected data.

57. The computer program of claim 55, wherein to retrieve the code the computer program is further translatable or executable to:

issue a request to a host for a document.

58. The computer program of claim 57, wherein the request is issued over a network.

59. The computer program of claim 58, wherein the request is issued from a client computer to a server computer.

60. The computer program of claim 59, wherein the request is an HTTP GET request issued by a browser.

61. The computer program of claim 53, wherein the code is rendered.

62. The computer program of claim 57, wherein the application comprises a document and wherein a parse of the code returns a collection of components for the document, and wherein to define contextual relationships between the identified components the computer program is further translatable or executable to:

assign each component collection a one to one relationship with the document;

assign each identified component within the component collection a one to one relationship to the component collection of which the identified component is a part;

assign each identified component within the component collection a one to one relationship to the document of which the component collection is a part; and

identify whether any of the identified components within the component collection are identical to any other identified component and, for any of the identified components that match another identified component,

assign the matching identified component within the component collection a many to one relationship to the component collection of which the matching identified component is a part; and

assign the matching identified component within the component collection a many to one relationship to the document of which the component collection is a part.

63. The computer program of claim 58, wherein the application comprises a set of documents and where a parse of the code returns a collection of components for each document, and wherein to define cross contextual relationships between the identified components, for each identified component within the component collection, the computer program is further translatable or executable to:

determine whether the identified component is a transactable component;

extract an execution result for each transactable component;

group together all transactable components that have a single execution result;

examine a parentage for each group of transactable components to identify a parent document for each group of transactable elements;

for any groups of transactable components having an identical parentage, identify a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components; and

for any groups of transactable components not having an identical parentage, identify a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components and as having a one to many relation to a set of parent documents for the group of transactable components.

64. The computer program of claim 63, further translatable or executable to:

for each non-transactable component, determine whether the identified component matches any other of the identified components in the component collection;

for each matching non-transactable component, determine whether the matching components have an identical parentage; and

identify each component of a set of matching non-transactable components that do not have identical parentage as having a one to many relation to a set of parent documents.

65. A computer program stored on a tangible medium and comprising computer or machine readable program components operable to define a relationship among a set of components of a document in an application, translatable or executable to:

determine if a collection of components exists for the document;

identify individual components within the collection of components; and

define a relationship between the identified individual components.

66. The computer program of claim 65, further translatable or executable to:

determine if any of the identified individual components within the collection of components are identical to one another.

67. The computer program of claim 65, wherein to define the relationships between the identified components the computer program is further translatable or executable to:

define contextual relationships between the identified components.

68. The computer program of claim 65, wherein to define the relationships between the identified components the computer program is further translatable or executable to:

define cross contextual relationships between the identified components.

69. The computer program of claim 67, wherein to define contextual relationships between the identified components the computer program is further translatable or executable to:

assign each component collection a one to one relationship with the document;

assign each identified component within the component collection a one to one relationship to the component collection of which the identified component is a part;

assign each identified component within the component collection a one to one relationship to the document of which the component collection is a part; and

identify whether any of the identified components within the component collection are identical to any other identified component and, for any of the identified components that match another identified component,

assign the matching identified component within the component collection a many to one relationship to the component collection of which the matching identified component is a part; and

assign the matching identified component within the component collection a many to one relationship to the document of which the component collection is a part.

70. The computer program of claim 68, wherein to define cross contextual relationships between the identified components, for each identified component within the component collection the computer program is further translatable or executable to:

determine whether the identified component is a transactable component;

extract an execution result for each transactable component;

group together all transactable components that have a single execution result;

examine a parentage for each group of transactable components to identify a parent document for each group of transactable elements;

for any groups of transactable components having an identical parentage, identify a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components; and

for any groups of transactable components not having an identical parentage, identify a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components and as having a one to many relation to a set of parent documents for the group of transactable components.

71. The computer program of claim 70, further translatable or executable to:

for each non-transactable component, determine whether the identified component matches any other of the identified components in the component collection;

for each matching non-transactable component, determine whether the matching components have an identical parentage; and

identify each component of a set of matching non-transactable components that do not have identical parentage as having a one to many relation to a set of parent documents.

72. The computer program of claim 70, wherein to determine whether the identified component is a transactable component the computer program is further translatable or executable to:

review each identified component against a transactable component criteria.

73. The computer program of claim 72, wherein each identified component has at least one of a property, method, attribute or parameter and wherein the transactable component criteria is a property criteria, a method criteria, an attribute criteria, a parameter criteria, or a combination of one or more of a property criteria, a method criteria, an attribute criteria, and a parameter criteria.

74. The computer program of claim 65, wherein to identify individual components within the collection of components the computer program is further translatable or executable to:

parse code of the application to identify individual components within the code; and

collect individual components of the document into a collection of components.

75. The computer program of claim 74, wherein a DOM parser is used to parse the code, and wherein the computer program is further translatable or executable to:

return a DOM for the code; and

query the DOM for a collection of components.

76. The computer program of claim 74, wherein a regular expression parser is used to parse the code, and wherein the computer program is further translatable or executable to:

return a parsed version of the code having a set of components; and

group the parsed components into a collection of components.

77. The computer program of claim 74, further translatable or executable to collect data on the identified components.

78. The computer program of claim 65, wherein the collection of components is either an overall collection or a collection of a specific type of component.

79. The computer program of claim 65, further translatable or executable to:

assign a unique ID to each individual component; and

construct each unique ID from properties, methods, and/or values assigned to each individual component.

80. A computer program stored on a tangible medium and comprising computer or machine readable program components operable to identify a set of transactable components within an application having a set of components, translatable or executable to:

parse code of the application to identify the set of components within the application; and

review each component in the set of components against a transactable component criteria; and

identify each component in the set of components that is a transactable component.

81. The computer program of claim 80, wherein the transactable component criteria comprises at least one characteristic associated with transactable components, and wherein to reviewing each component in the set of components against a transactable component criteria the computer program is further translatable or executable to:

determine whether or not each component has the at least one characteristic.

82. The computer program of claim 81, wherein the at least one characteristic associated with a transactable component further comprises at least one of a property, method, attribute or parameter.

83. The computer program of claim 82, wherein the transactable component criteria further comprises at least one of a property criteria, a method criteria, an attribute criteria, a parameter criteria associated with a transactable component, or a combination of one or more of a property criteria, a method criteria, an attribute criteria, and a parameter criteria associated with a transactable component.

84. The computer program of claim 80, wherein to identify transactable components the computer program is further translatable or executable to match a criterion with a component.

85. The computer program of claim 84, wherein the criterion is one of a property, method, attribute, or parameter criteria.

86. The computer program of claim 80, further translatable or executable to:

define contextual and cross contextual relationships among the components.

87. The computer program of claim 86, wherein to define contextual relationships between the identified components the computer program is further translatable or executable to:

assign each component collection a one to one relationship with the document;

assign each identified component within the component collection a one to one relationship to the component collection of which the identified component is a part;

assign each identified component within the component collection a one to one relationship to the document of which the component collection is a part; and

identify whether any of the identified components within the component collection are identical to any other identified component and, for any of the identified components that match another identified component,

assign the matching identified component within the component collection a many to one relationship to the component collection of which the matching identified component is a part; and

assign the matching identified component within the component collection a many to one relationship to the document of which the component collection is a part.

88. The computer program of claim 87, wherein to define cross contextual relationships between the identified components, for each identified component within the component collection the computer program is further translatable or executable to:

determine whether the identified component is a transactable component; and

for each transactable component;

extract an execution result for each transactable component;

group together all transactable components that have a single execution result;

examine a parentage for each group of transactable components to identify a parent document for each group of transactable elements;

for any groups of transactable components having an identical parentage, identify a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components; and

for any groups of transactable components not having an identical parentage, identify a child document associated with each transactable element execution result as having a one to many relation to the group of transactable components and as having a one to many relation to a set of parent documents for the group of transactable components.

for each non-transactable component;

determine whether the identified component matches any other of the identified components in the component collection;

for each matching non-transactable component, determine whether the matching components have an identical parentage; and

identify each component of a set of matching non-transactable components that do not have identical parentage as having a one to many relation to a set of parent documents.