Application portfolio assessment tool

• US 20070094281A1
• Filed: 10/26/2005
• Published: 04/26/2007
• Est. Priority Date: 10/26/2005
• Status: Abandoned Application

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Addleman, Mark, Paiko, Michael, Malloy, Michael
• Application Number:
  US11/259,920
• Publication Number:
  US 20070094281A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

An application portfolio assessment tool and related techniques are provided. The manageability and criticality of a software application implementation are determined to evaluate and compare one or more applications. Sets of application inquiries to assess the manageability and criticality of the application are provided and responses received. Each response is scaled and multiplied by a weighting associated with the corresponding application inquiry. The determined values for each inquiry directed to manageability can be used to calculate a manageability score and the determined values for each inquiry directed to criticality can be used to calculate a criticality score. The results can be graphically depicted to illustrate the relative characteristics of one or more applications. Application risk exposure assessments can also be made using application inquiries. Using the manageability and criticality scores, applications can be selected for performance profiling.

Claims

1. A method of creating rankings for applications, comprising:

providing a first set of application inquiries to assess the manageability of a first application;

receiving a response to at least one application inquiry in said first set;

determining a manageability score for said first application based on said response to said at least one application inquiry in said first set;

providing a second set of application inquiries to assess the criticality of said first application;

receiving a response to at least one application inquiry in said second set;

determining a criticality score for said first application based on said response to said at least one application inquiry in said second set; and

creating a ranking for said first application based on said manageability score and said criticality score.

2. The method of claim 1, wherein said providing a first set of application inquiries includes:

providing a plurality of weightings for said first set of application inquiries whereby each application inquiry in said first set has a corresponding weighting;

3. The method of claim 2, wherein said determining a manageability score comprises:

determining a scaled response value for each application inquiry in said first set for which a response is received;

multiplying each scaled response value by the weighting that corresponds to the application inquiry for which said scaled response value was determined, said multiplying resulting in a weighted response value for each application inquiry in said first set for which a response was received; and

determining a sum of each weighted response value for each application inquiry in said first set for which a response was received to obtain said manageability score.

4. The method of claim 3, further comprising for each application inquiry:

providing a plurality of scaled response values;

providing a corresponding range for each scaled response value of said plurality.

5. The method of claim 4, wherein said step of determining a scaled response value for each application inquiry in said first set for which a response was received comprises:

determining which of said plurality of ranges the received response corresponds to; and

determining which of said plurality of scaled response values corresponds to the determined range.

6. The method of claim 1, wherein said step of creating a ranking comprises:

providing a quadrant chart; and

determining a quadrant for said application based on said manageability score and said criticality score.

7. The method of claim 2, wherein said weightings for said set of application inquiries reflect a relative importance of each application inquiry to determining said manageability score.

8. The method of claim 1, wherein said providing a second set of application inquiries includes:

providing a plurality of weightings for said second set of application inquiries whereby each application inquiry in said second set has a corresponding weighting;

9. The method of claim 8, wherein said determining a criticality score comprises:

determining a scaled response value for each application inquiry in said second set for which a response is received;

multiplying each scaled response value by the weighting that corresponds to the application inquiry for which said scaled response value was determined, said multiplying resulting in a weighted response value for each application inquiry in said second set for which a response was received; and

determining a sum of each weighted response value for each application inquiry in said second set for which a response was received to obtain said criticality score.

10. The method of claim 9, further comprising for each application inquiry:

providing a plurality of scaled response values; and

providing a corresponding range for each scaled response value of said plurality.

11. The method of claim 10, wherein said step of determining a scaled response value for each application inquiry in said first set for which a response was received comprises:

determining which of said plurality of ranges the received response corresponds to; and

determining which of said plurality of scaled response values corresponds to the determined range.

12. The method of claim 1, further comprising:

providing a third set of application inquiries to assess a risk exposure of said first application;

receiving a response to at least one application inquiry in said third set;

providing an assessment of an availability of said first application and an assessment of a performance of said first application.

13. The method of claim 12, wherein providing a third set of application inquiries:

providing at least one first inquiry to determine downtime of said first application;

providing at least one second inquiry to determine a desired capacity of said first application; and

providing at least one third inquiry to determine an actual capacity of said first application.

19. The method of claim 1, further comprising:

providing, for at least one inquiry in said first set and at least one inquiry in said second set, information for those responding to said application inquiries on how to respond.

20. The method of claim 19, further comprising:

providing, for at least one inquiry in said first set and at least one inquiry in said second set, information for a consultant aiding those responding to said application on how to respond.

21. The method of claim 1, further comprising:

determining whether said manageability score is above a first threshold value; and

determining whether said criticality score is above a second threshold value.

22. The method of claim 21, further comprising:

selecting said first application for performance profiling if said manageability score is above said first threshold value and said criticality score is above said second threshold value.

23. The method of claim 21, further comprising:

selecting said first application for performance profiling if said manageability score is above said first threshold value.

24. The method of claim 23, further comprising:

performing performance profiling for said first application if said first application is selected.

25. The method of claim 24, wherein performing said performance profiling comprises:

adding functionality to a set of code for said first application.

26. The method of claim 25, wherein:

said set of code corresponds to at least one transaction; and

said adding functionality includes adding code to said set of code that activates a tracing mechanism when said at least one transaction starts and terminates said tracing mechanism when said at least one transaction completes.

27. The method of claim 26, further comprising:

determining whether an execution time of said at least one transaction exceeds a threshold trace period;

reporting said first application if said execution time of said at least one transaction exceeds said threshold trace period.

28. The method of claim 25, wherein said set of code is object code.

29. The method of claim 28, wherein said object code is Java byte code.

14. The method of claim 14, wherein said step of providing an assessment of an availability of said first application and an assessment of a performance of first said application comprises:

determining and providing an availability percentage of said first application;

determining and providing a performance capacity percentage of said first application.

15. The method of claim 14, wherein providing a third set of application inquiries further comprises:

providing at least one fourth inquiry to determine a type of said first application, said type chosen from a group of types comprising revenue generating, account origination, and service;

providing at least one fifth inquiry to determine a number of transactions for revenue generating applications;

providing at least one sixth inquiry to determine an average value of a transaction for revenue generating applications;

providing at least one seventh inquiry to determine a number of customers served for service applications;

providing at least one eighth inquiry to determine a customer value for service applications;

providing at least one ninth inquiry to determine an estimated number of customers activated for account origination applications; and

providing at least one tenth inquiry to determine a customer value for account origination applications.

16. The method of claim 15, further comprising if said first application is a revenue generating application:

receiving a response to said at least one fifth inquiry and said at least one sixth inquiry;

determining and providing a cost associated with a lack of availability based on said availability percentage, said number of transactions, and said average value of a transaction;

determining and providing a cost associated with poor performance of said application based on said performance capacity percentage, said number of transactions, and said average value of a transaction.

17. The method of claim 15, further comprising if said first application is a service application:

receiving a response to said at least one seventh inquiry and said at least one eighth inquiry;

determining and providing a cost associated with a lack of availability of said first application based on said availability percentage, said number of customers serviced by said first application, and said average customer value;

determining and providing a cost associated with poor performance of said first application based on said performance capacity percentage, said number of customers serviced by said first application, and said average customer value.

18. The method of claim 15, further comprising if said first application is an account origination application:

receiving a response to said at least one ninth inquiry and said at least one tenth inquiry;

determining and providing a cost associated with a lack of availability of said first application based on said availability percentage, said number of new customers activated, and said average customer value; and

determining and providing a cost associated with poor performance of said first application based on said performance capacity percentage, said number of new customers activated, and said average customer value.

30. One or more processor readable storage devices having processor readable code embodied on said one or more processor readable storage devices, said processor readable code for programming one or more processors to perform a method comprising:

providing a first set of application inquiries to assess the manageability of a first application;

receiving a response to at least one application inquiry in said first set;

determining a manageability score for said first application based on said response to said at least one application inquiry in said first set;

providing a second set of application inquiries to assess the criticality of said first application;

receiving a response to at least one application inquiry in said second set; and

determining a criticality score for said first application based on said response to said at least one application inquiry in said second set; and

creating a ranking for said first application based on said manageability score and said criticality score.

31. One or more processor readable storage devices according to claim 30, wherein said step of creating a ranking comprises:

providing a quadrant chart; and

determining a quadrant for said first application based on said manageability score and said criticality score.

32. One or more processor readable storage devices according to claim 30, further comprising:

providing a third set of application inquiries to assess a risk exposure of said first application;

receiving a response to at least one application inquiry in said third set; and

providing an assessment of an availability of said first application and an assessment of a performance of said first application.

33. One or more processor readable storage devices according to claim 30, further comprising:

determining whether said manageability score is above a first threshold value;

determining whether said criticality score is above a second threshold value; and

performing performance profiling for said first application if said manageability score is above said first threshold value and said criticality score is above said second threshold value.

34. One or more processor readable storage devices according to claim 33, wherein performing said performance profiling comprises:

adding functionality to a set of code for said first application.

35. One or more processor readable storage devices according to claim 34, wherein:

said set of code corresponds to at least one transaction;

said adding functionality includes adding code to said set of code that activates a tracing mechanism when said at least one transaction starts and terminates said tracing mechanism when said at least one transaction completes.

36. One or more processor readable storage devices according to claim 35, further comprising:

determining whether an execution time of said at least one transaction exceeds a threshold trace period; and

reporting said first application if said execution time of said at least one transaction exceeds said threshold trace period.

37. One or more processor readable storage devices according to claim 34, wherein said set of code is object code.

38. One or more processor readable storage devices according to claim 34, wherein said object code is Java byte code.

39. A method of evaluating applications, comprising:

receiving at least one response to a first set of application inquiries, said first set of application inquiries directed to assessing manageability of a first application and including a weighting for each application inquiry in said first set;

receiving at least one response to a second set of application inquiries, said second set of application inquiries directed to assessing criticality of said first application and including a weighting for each application inquiry in said second set;

determining a manageability score for said first application based on said at least one response to said first set of application inquiries;

determining a criticality score for said first application based on said at least one response to said second set of application inquiries; and

creating a graphical representation based on said manageability score and said criticality score.

40. The method of claim 39, further comprising:

providing said first set of application inquiries and said weighting for each application inquiry in said first set; and

providing said second set of application inquiries and said weighting for each application inquiry in said second set.

41. The method of claim 40, wherein:

said step of determining said manageability score includes determining at least one scaled response value from said at least one response to said first set of application inquiries and multiplying said at least one scaled response value by a corresponding application inquiry weighting;

said step of determining said criticality score includes determining at least one scaled response value from said at least one response to said second set of application inquiries and multiplying said at least one scaled response value by a corresponding application inquiry weighting.

42. The method of claim 39, further comprising:

receiving at least one response to a third set of application inquiries, said third set of application inquiries directed to assessing risk exposure of said first application;

determining an availability percentage of said first application from said at least one response to said third set of application inquiries;

determining an availability cost of said first application from said at least one response to said third set of application inquiries;

determining a performance percentage of said first application from said at least one response to said third set of application inquiries;

determining a performance cost of said first application from said at least one response to said third set of application inquiries.

43. The method of claim 39, further comprising:

providing a quadrant chart having at least four quadrants.

44. The method of claim 43, wherein creating a graphical representation comprises:

plotting said first application in a first quadrant of said quadrant chart if said manageability score is above a first threshold value and said criticality score is above a second threshold value;

plotting said first application is a second quadrant of said quadrant chart if said manageability score is above said first threshold value and said criticality score is at or below said second threshold value;

plotting said first application in a third quadrant of said quadrant chart if said manageability score is at or below said first threshold value and said criticality score is above said second threshold value; and

plotting said first application in a fourth quadrant of said quadrant chart if said manageability score is at or below said first threshold value and said criticality score is at or below said second threshold value.

45. The method of claim 44, further comprising:

selecting said first application for performance profiling if said manageability score is above said first threshold value or said criticality score is above said second threshold value.

46. The method of claim 45, further comprising:

performing said performance profiling for said first application if said first application is selected.

47. The method of claim 46, wherein performing said performance profiling comprises:

adding functionality to a set of code for said first application.

48. The method of claim 47, wherein:

said set of code corresponds to at least one transaction; and

said adding functionality includes adding code to said set of code that activates a tracing mechanism when said at least one transaction starts and terminates said tracing mechanism when said at least one transaction completes.

49. The method of claim 48, further comprising:

determining whether an execution time of said at least one transaction exceeds a threshold trace period; and

reporting said first application if said execution time of said at least one transaction exceeds said threshold trace period.

50. The method of claim 47, wherein said set of code is object code.

51. The method of claim 47, wherein said object code is Java byte code.

52. A method of creating rankings for applications, comprising:

receiving at least one response to a first set of application inquiries, said first set of application inquiries directed to assessing manageability of a first application and including a weighting for each application inquiry in said first set;

receiving at least one response to a second set of application inquiries, said second set of application inquiries directed to assessing criticality of said first application and including a weighting for each application inquiry in said second set;

determining a manageability score for said first application based on said at least one response to said first set of application inquiries;

determining a criticality score for said first application based on said at least one response to said second set of application inquiries; and

performing performance profiling on said first application if said manageability score is above a first threshold value.

53. The method of claim 52, wherein said performance profiling is performed only if said manageability score is above a first threshold value and said criticality score is above a second threshold value.

54. The method of claim 52, wherein performing performance profiling comprises:

adding functionality to a set of code for said first application.

55. The method of claim 54, wherein:

said set of code corresponds to at least one transaction; and

said adding functionality includes adding code to said set of code that activates a tracing mechanism when said at least one transaction starts and terminates said tracing mechanism when said at least one transaction completes.

56. The method of claim 55, further comprising:

determining whether an execution time of said at least one transaction exceeds a threshold trace period; and

reporting said first application if said execution time of said at least one transaction exceeds said threshold trace period.

57. The method of claim 54, wherein said set of code is object code.

58. The method of claim 54, wherein said object code is Java byte code.