System and process for constructing and analyzing profiles for an application

• US 20030040887A1
• Filed: 06/04/2002
• Published: 02/27/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,845
• Publication Number:
  US 20030040887A1
• Time in Patent Office: Days
• US Class Current: 702/187
• 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 process can generate prospective information regarding application. In one example, rendered source code for the application could be received by a client computer from a server computer. The process can comprise retrieving data regarding historical information for the application and generating prospective information regarding the application based at least in part on the historical information. Examples of prospective information can comprise scenario modeling, predictive analysis, forecasting, scalability estimation, combinations thereof, derivations thereof, or the like. In many embodiments, the process can further comprise parsing the application to identify components within the application. At least some of the components can be part, but not all, of a document. The process can still further comprise testing the components to generate the historical information for the components. The profile construction and analysis may be performed for a group of applications.

Claims

1. A process for generating prospective information regarding an application, the process comprising:

retrieving data regarding historical information for the application; and

generating prospective information regarding the application based at least in part on the historical information.

2. The process of claim 1, further comprising:

identifying components within the application and component relationships, wherein at least some of the components are part, but not all, of a document; and

testing the application to generate the historical information for the components.

3. The process of claim 2, further comprising sorting the historical information by component type.

4. The process of claim 3, wherein the historical information comprises functional and performance data for the components.

5. The process of claim 3, further comprising tracking a change in a pattern for at least one of the components.

6. The process of claim 2, further comprising sorting the historical information by relationship type.

7. The process of claim 6, further comprising tracking a change in a pattern for a relationship between components.

8. The process of claim 2, wherein the historical information includes metadata that describes how object data were collected when used by the application.

9. The process of claim 8, further comprising tracking a change in a pattern for at least part of the metadata.

10. The process of claim 2, wherein generating prospective information is performed using an analysis selected from:

scenario modeling;

predictive analysis;

forecasting;

scalability estimation;

a combination thereof; and

a derivation thereof.

11. The process of claim 1, further comprising constructing a profile of the application by combining pattern data that includes an object pattern and a metadata pattern for a test profile.

12. The process of claim 1, wherein the historical information includes statuses and statistics for components.

13. The process of claim 12, wherein a type of the statistics is selected from component size, load time, and number of errors.

14. The process of claim 1, wherein the historical information includes pass/fail information and alert information for components.

15. The process of claim 1, wherein generating prospective information is performed using an analysis selected from:

scenario modeling;

predictive analysis;

forecasting;

scalability estimation;

a combination thereof; and

a derivation thereof.

16. A data processing system readable medium having first code embodied therein, the code is designed to generate information regarding an application, the code comprising:

an instruction for retrieving data regarding historical information for the application; and

an instruction for generating prospective information regarding the application based at least in part on the historical information.

17. The data processing system readable medium of claim 16, wherein the code further comprises:

an instruction for identifying components within the application and component relationships, wherein at least some of the components are part, but not all, of a document; and

an instruction for testing the application to generate the historical information for the components.

18. The data processing system readable medium of claim 17, wherein the code further comprises an instruction for sorting the historical information by component type.

19. The data processing system readable medium of claim 18, wherein the historical information comprises functional and performance data for the components.

20. The data processing system readable medium of claim 18, wherein the code further comprises an instruction for tracking a change in a pattern for at least one of the components.

21. The data processing system readable medium of claim 17, wherein the code further comprises an instruction for sorting the historical information by relationship type.

22. The data processing system readable medium of claim 21, wherein the code further comprises an instruction for tracking a change in a pattern for a relationship between components.

23. The data processing system readable medium of claim 17, wherein the historical information includes metadata that describes how object data were collected when used by the application.

24. The data processing system readable medium of claim 23, wherein the code further comprises an instruction for tracking a change in a pattern for at least part of the metadata.

25. The data processing system readable medium of claim 17, wherein the instruction for generating prospective information is performed using an analysis selected from:

scenario modeling;

predictive analysis;

forecasting;

scalability estimation;

a combination thereof; and

a derivation thereof.

26. The data processing system readable medium of claim 16, wherein the code further comprises an instruction for constructing a profile of the application by combining pattern data that includes an object pattern and a metadata pattern for a test profile.

27. The data processing system readable medium of claim 16, wherein the historical information includes statuses and statistics for components.

28. The data processing system readable medium of claim 27, wherein a type of the statistics is selected from component size, load time, and number of errors.

29. The data processing system readable medium of claim 16, wherein the historical information includes pass/fail information and alert information for components.

30. The data processing system readable medium of claim 16, wherein the instruction for generating prospective information is performed using an analysis selected from:

scenario modeling;

predictive analysis;

forecasting;

scalability estimation;

a combination thereof; and

a derivation thereof.