Proactive performance management for multi-user enterprise software systems

• US 8,250,525 B2
• Filed: 03/02/2007
• Issued: 08/21/2012
• Est. Priority Date: 03/02/2007
• Status: Active Grant

• Current Assignee: Pegasystems Incorporated
• Original Assignee: Pegasystems Incorporated
• Inventors: Khatutsky, Victor E.
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): KRETZMER, ERIKA A
• Application Number:
  US11/681,269
• Publication Number:
  US 20080216055A1
• Time in Patent Office: 1,999 Days
• Field of Search: 717/111, 703/22
• US Class Current: 717/111
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3438 monitoring of user actions tracking the activity of the user H04L67/535
• CPC Class Codes: G06F 11/3442 for planning or managing the needed capacity
• CPC Class Codes: G06F 11/3447 Performance evaluation by modeling
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/86 Event-based monitoring

Abstract

The invention provides, in some aspects, systems for proactive management of development and performance of a software application based on monitoring it (and/or one or more of its components) during the course of development or execution. Those systems signal alerts upon determining that actual or expected usage of the application (or its components) by users of like classes (or roles) is anticipated to, or does, exceed quotas, when the application is placed in production mode.

Claims

1. A system for proactive management of performance of a software application, comprising:

A. a first digital data processor executing a software development environment,

B. a second digital data processor executing a performance monitor in communications coupling with the software development environment, wherein the first digital data processor and the second digital data processor may overlap, the performance monitor obtains a specific of an application-in-development the software development environment, and

C. the performance monitor applying the specific of the application-in-development to a model that defines one or more quotas for a user, wherein the one or more quotas are defined in accordance with a class to which the user belongs, and

D. the performance monitor signaling an alert upon determining that, based on the results obtained in step (C), execution of the application-in-development and/or a component thereof by the user and/or consumption of digital data processing resources during such execution is anticipated to exceed the one or more quotas for the user as defined by the model, wherein steps (A), (B), (C) and (D) are performed in real-time in order to provide proactive and immediate feedback regarding expected application performance.

2. The system of claim 1, wherein the performance monitor signals the alert to a developer and/or a centralized monitoring environment.

3. The system of claim 1, wherein the performance monitor estimates consumption of the one or more resources based on prior monitoring of actual consumption during execution of the application.

4. The system of claim 1, in which the model defines a relationship between (i) users in each of one or more classes and (ii) estimated consumption of resources by such users during execution of the application.

5. The system of claim 4, wherein those resources include any of processing capacity, memory capacity and/or network bandwidth.

6. The system of claim 4, in which the model defines quotas for usage of the application and/or one or more components thereof in production mode by users in each of one or more classes.

7. The system of claim 4, in which the model defines quotas for consumption of resources during usage of the application and/or one or more components thereof in production mode by users in each of one or more classes.

8. The system of claim 4, wherein the model defines such quotas on the basis of individual and multiple users in such classes.

9. The system of claim 4, wherein the quotas include any of (i) maximum permitted usage of the application by users in each of one or more classes, and (ii) expected usage of the application by users in each of one or more classes.

10. A method for proactive management of performance of a software application, comprising:

A. obtaining, by a digital data processor, a specific of an application-in-development in a software development environment,

B. applying the specific of the application-in-development to a model that defines one or more quotas for a user, wherein the one or more quotas are defined in accordance with a class to which the user belongs,

C. signaling an alert upon determining that, based on the results obtained in step (B), execution of the application-in-development and/or a component thereof by a user and/or consumption of digital data processing resources during such execution is anticipated to exceed the one or more quotas for the user as defined by the model, wherein steps (A), (B), and (C) are performed in real-time in order to provide proactive and immediate feedback regarding expected application performance.

11. The method of claim 10, comprising signaling the alert to a developer and/or a centralized monitoring environment.

12. The method of claim 10, comprising consumption of the one or more resources based on prior monitoring of actual consumption during execution of the application.

13. The method of claim 10, wherein the model defines a relationship between (i) users in each of one or more classes and (ii) estimated consumption of resources by such users during execution of the application.

14. The method of claim 13, wherein those resources include any of processing capacity, memory capacity and/or network bandwidth of the one or more digital data processing resources.

15. The method of claim 13, in which the model defines quotas for execution of the application and/or one or more components thereof by users in each of one or more classes.

16. The method of claim 15, in which the model defines quotas for consumption of resources during execution of the application and/or one or more components thereof by users in each of one or more classes.

17. The method of claim 13, in which the model defines such quotas on the basis of individual and multiple users in such classes.

18. The method of claim 13, wherein the quotas include any of (i) maximum permitted usage of the application by users in each of one or more classes, and (ii) expected usage of the application by users in each of one or more classes.

19. The method of claim 10 comprising responding to signaling in step (C) by one or more of altering (i) implementation of the application, (ii) allocation of time for such implementation, (iii) quotas defined for the respective classes, (iv) allocation of resources to the application, and/or (v) definition of the relationships defined in the model.

20. The method of claim 19, wherein the responding step includes at least initiating communications among personnel responsible for any of development, management and/or procurement of the application in regard to potential implementation of one or more such alterations.