FIELD OF THE INVENTION

In general, the present invention relates to a method, system and program product for estimating transaction response times. Specifically, the present invention provides a way to estimate response times for application transactions occurring in a network environment such as within an enterprise architecture.

BACKGROUND OF THE INVENTION

Under current day information technology (IT) , applications are often deployed in a network environment. For example, an organization might have an enterprise architecture in which applications are deployed for use by tens of thousands of users. Such applications might go through numerous phases and/or releases. In many cases, these applications run into performance challenges such as stability issues, bottlenecks, etc.

An important part of resolving such issues is to understand and quantify the nature of transactions occurring throughout the enterprise architecture. Unfortunately, no existing system provides a way to accurately perform such a task. That, is no existing system has even considered how to define performance characteristics from a client-server nature within the enterprise architecture. Moreover, no existing system has realized that such performance challenges can vary among geographic regions. Still yet, no existing system has attempted to comprehend the underlying business processes when resolving such performance characteristics .

In view of the foregoing, there exists a need for a method, system and program product for profiling an application within an enterprise architecture. Specifically, a need exists for a method, system and program product for estimating transaction response times.

SUMMARY OF THE INVENTION

In general, the present invention provides a method, system and program product for profiling an application within an enterprise architecture. Specifically, the present invention provides for a method,

system and program product for estimating transaction response time(s). Under the present invention, components of an enterprise architecture are first identified. This process not only involves hardware, software and topographic identification, but also includes developing and documenting an understanding of the business processes occurring within the enterprise architecture. Based on this analysis, an enterprise architecture profile is developed. Thereafter, transactions that occur within the enterprise architecture are identified, and data related thereto is collected for different geographic regions. In general, a transaction involves a set (e.g., one or more) of steps (e.g., "clicks") within an application of the enterprise architecture. For each such step, data is collected. Based on the data collection one or more transaction class profiles are developed. Using these profile (s) and the enterprise architecture profile, transaction response time(s) can be estimated.

A first aspect of the present invention provides a method for estimating a transaction response time, comprising: identifying components of an enterprise architecture; developing an enterprise architecture profile based on the identified components; collecting data based upon a set of transactions for different geographic regions within the enterprise architecture; developing at least one transaction class profile based upon the data; and estimating the transaction response time based upon the enterprise architecture profile and the at least one transaction class profile .

A second aspect of the present invention provides a system for estimating a transaction response time, comprising: a system for identifying components of an enterprise architecture; a system for developing an enterprise architecture profile based on the identified components; a system for collecting data based upon a set of transactions for different geographic regions within the enterprise architecture; a system for developing at least one transaction class profile based upon the data; and a system for estimating the transaction response time based upon the enterprise architecture profile and the at least one transaction class profile.

A third aspect of the present invention provides a program product stored on a computer readable medium for estimating a transaction response time, the computer readable medium comprising program code for performing the following steps: identifying components of an enterprise architecture; developing an enterprise architecture profile based on the identified components; collecting data based upon a set of transactions for different

geographic regions within the enterprise architecture; developing at least one transaction class profile based upon the data; and estimating the transaction response time based upon the enterprise architecture profile and the at least one transaction class profile.

Preferably, the program product further comprises, wherein the identifying step comprises identifying hardware and software elements of the enterprise architecture, and documenting any business processes occurring within the enterprise architecture.

Preferably, the program product further comprises, wherein the collecting step comprises collecting resources required for the set of transactions .

Preferably, the program product further comprises, wherein each of the set of transactions comprises a set of steps in an application of the enterprise architecture, and wherein the collecting step comprises collecting data for each of the set of steps.

Preferably, the program product further comprises, wherein the collecting step comprises collecting a bandwidth requirement for each of the set of transactions.

Preferably, the program product further comprises, wherein the computer readable medium further comprises program code for generating a report that includes the transaction response time, wherein the transaction response time is arranged in the report base upon a corresponding geographic region.

Preferably, the program product further comprises, wherein the at least one transaction class profile details a business scenario, a set of steps, a transaction number, a duration, a bandwidth requirement and a number of application turns for the each of the set of transactions.

A fourth aspect of the present invention provides a method for deploying an application for estimating a transaction response time, comprising: deploying a computer infrastructure being operable to: identify components of an enterprise architecture; develop an enterprise architecture profile based on the identified components; collect data based upon a set of transactions for different geographic regions within the enterprise architecture; develop at least one transaction class profile based upon the data; and estimate the transaction response time

based upon the enterprise architecture profile and the at least one transaction class profile.

A fifth aspect of the present invention provides computer software embodied in a propagated signal for estimating a transaction response time, the computer software comprising instructions for causing a computer system to perform the following functions: identify components of an enterprise architecture; develop an enterprise architecture profile based on the identified components; collect data based upon a set of transactions for different geographic regions within the enterprise architecture; develop at least one transaction class profile based upon the data; and estimate the transaction response time based upon the enterprise architecture profile and the at least one transaction class profile .

A sixth aspect of the present invention provides a business method for estimating a transaction response time.

Therefore, the present invention provides a method, system and program product for estimating a transaction response time.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features of this invention will be more readily understood from the following detailed description of the various aspects of the invention taken in conjunction with the accompanying drawings that depict various embodiments of the invention, in which:

Fig. 1 depicts an illustrative system for estimating a transaction response time.

Fig. 2 depicts an illustrative transaction class profile according to the present invention.

Fig. 3 depicts an illustrative report containing estimated transaction response times according to the present invention.

Fig. 4 depicts a method flow diagram of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION

I. General Description

As indicated above, the present invention provides a method, system and program product for profiling an application within an enterprise architecture. Specifically, the present invention provides for a method, system and program product for estimating transaction response time(s). Under the present invention, components of an enterprise architecture are first identified. This process not only involves hardware, software and topographic identification, but also includes developing and documenting an understanding of the business processes occurring within the enterprise architecture. Based on this analysis, an enterprise architecture profile is developed. Thereafter, transactions that occur within the enterprise architecture are identified, and data related thereto is collected for different geographic regions. In general, a transaction involves a set (e.g., one or more) of steps (e.g., "clicks") within an application of the enterprise architecture. For each such step, data is collected. Based on the data collection one or more transaction class profiles are developed. Using these profile (s) and the enterprise architecture profile, transaction response time(s) can be estimated.

Referring now to Fig. 1, a system 10 for estimating transaction response time(s) for an enterprise architecture 16 is shown. As depicted, system 10 includes a computer infrastructure 12 including a computer system 14 that communicates with enterprise architecture 16. Enterprise architecture 16 generally includes various hardware 60 (e.g., clients, servers, routers, databases etc.) and software 62 (e.g. applications, operating systems, etc.) elements. To this extent, enterprise architecture 16 is typically implemented in a network environment over multiple geographic areas. Computer system 14 is shown within an infrastructure 12 that is separate from enterprise architecture 16 to illustrate that the present invention could be carried out by a party who is independent of enterprise architecture 16, such as a service provider or the like. However, it should be understood that computer system 14 could be deployed within enterprise architecture 16 (e.g., by a service provider or by an owner/operator of enterprise architecture 16) and still perform the functions of the present invention.

In any event, for the embodiment shown in Fig. 1, computer system 14 can communicate with enterprise architecture 16 (or the components thereof) over a network (e.g., the Internet, a wide area network (WAN), a local area network (LAN), a virtual private network (VPN), etc. In such a case, communication between computer system 14 and enterprise architecture

16 can occur via any combination of various types of communications links. For example, the communication links can comprise addressable connections that may utilize any combination of wired and/or wireless transmission methods. Where communications occur via the Internet, connectivity could be provided by conventional TCP/IP sockets-based protocol, and an Internet service provider could be used to establish connectivity to the Internet.

Computer system 14 is shown including a processing unit 20, a memory 22, a bus 24, and an input/output (I/O) interfaces 26. Further, computer system 14 is shown in communication with external I/O devices/resources 28 and storage system 30. In general, processing unit 20 executes computer program code, such as estimation system 40, which is stored in memory 22 and/or storage system 30. While executing computer program code, processing unit 20 can read and/or write data, to/from memory 22, storage system 30, and/or I/O interfaces 26. Bus 24 provides a communication link between each of the components in computer system 14. External devices 28 can comprise any devices (e.g., keyboard, pointing device, display, etc.) that enable a user to interact with computer system 14 and/or any devices (e.g., network card, modem, etc.) that enable computer system 14 to communicate with one or more other computing devices, such as enterprise architecture 16.

Computer infrastructure 12 is only illustrative of various types of computer infrastructures for implementing the invention. For example, in one embodiment, computer infrastructure 12 comprises two or more computing devices (e.g., a server cluster) that communicate over a network to perform the various process steps of the invention. Moreover, computer system 14 is only representative of various possible computer systems that can include numerous combinations of hardware. To this extent, in other embodiments, computer system 14 can comprise any specific purpose computing article of manufacture comprising hardware and/or computer program code for performing specific functions, any computing article of manufacture that comprises a combination of specific purpose and general purpose hardware/software, or the like. In each case, the program code and hardware can be created using standard programming and engineering techniques, respectively. Moreover, processing unit 20 may comprise a single processing unit, or be distributed across one or more processing units in one or more locations, e.g., on a client and server. Similarly, memory 22 and/or storage system 30 can comprise any combination of various types of data storage and/or transmission media that reside at one or more physical locations. Further, I/O interfaces 26 can comprise any system for exchanging information with one or more external devices 28. Still

further, it is understood that one or more additional components (e.g., system software, math co-processing unit, etc.) not shown in Fig. 1 can be included in computer system 14. However, if computer system 14 comprises a handheld device or the like, it is understood that one or more external devices 28 (e.g., a display) and/or storage system(s) 30 could be contained within computer system 14, not externally as shown.

Storage system 30 can be any type of system (e.g., a database) capable of providing storage for information under the present invention. To this extent, storage system 30 could include one or more storage devices, such as a magnetic disk drive or an optical disk drive. In another embodiment, storage system 30 includes data distributed across, for example, a local area network (LAN) , wide area network (WAN) or a storage area network (SAN) (not shown) . Although not shown, additional components, such as cache memory, communication systems, system software, etc., may be incorporated into computer system 14. Moreover, although not shown for brevity purposes, enterprise architecture 16 will likely contain computerized components similar to computer system 14.

Shown in memory 22 of computer system 14 is estimation system 40. In general, estimation system 40 will estimate transaction response times for transactions occurring within enterprise architecture 16. As shown, estimation system 40 includes component identification system 42, enterprise architecture profiling system 44, transaction data system 46, transaction profiling system 48 and transaction response time system 50. In general, estimation system 40 will take the following approach to estimate transaction response times:

(1) Develop a good understanding of traffic patterns of application 62 including the impact of network latency and acceptable response times as determined by users 64.

(2) Identify categories of users 64 based on characteristics such as type access, quantity, geographic region, etc.

(3) Identify appropriate connectivity strategies for each category of user 64 in each region based o their requirements and traffic volumes.

(4) Identify strategy for deploying application back-end components based on client traffic patterns and other requirements.

(5) Identify bandwidth requirements for the global core network to support transactions required by applications 62 and meet end users' 64 expectations or corporate response time standards. Typical factors in gauging bandwidth requirements include: identification and measurement of a typical usage pattern; understanding the types of user 64 (e.g., sales, management, etc.) and who is invoking which functions and the size of attachments; understanding the frequency of transactions; user concurrency from each site that would concurrently use the application; and response time service level requirements.

II. Enterprise Architecture Profiling

When attempting to estimate a transaction response time for enterprise architecture 16, component identification system 42 will first identify the components thereof. Identification of components under the present invention goes beyond identification of hardware 60 and software 62 elements. It also includes developing an understanding of any business processes occurring within enterprise architecture 16 through the use of applications 62. That is, users 64 will conduct a set (e.g., one or more) of transactions by taking certain actions/steps (e.g., "clicks") within applications 62. As will be shown below, such steps and transactions are identified and understood by the present invention to accurately gauge response times. To this extent, component identification system 42 can be programmed to analyze enterprise architecture 16 to make such identifications. In addition, component identification system 42 can be programmed to receive data corresponding to the components of enterprise architecture 16 such as data manually input (e.g., by an administrator). To this extent, component identification system 42 should be understood to provide any needed interface pages so that all pertinent data can be collected and components identified.

In a typical embodiment, component identification system 42 will gather certain pieces of information about enterprise architecture 16 itself. For example, component identification system 42 will gather information about: hardware 60 and software 62 present in enterprise architecture 16; global wide area network details of enterprise architecture 16, including topology, technologies and latencies experienced between global sites and data centers; response times Service Level Agreements and Service Level Objectives; features and functions of enterprise architecture 16; and client strategy and ownership standards. In addition, as indicated above, component identification system 42 will be used to identify/document any business processes occurring within

enterprise architecture 16. In general, this involves developing a list of any transactions associated with any business processes for various roles/responsibilities of users 64. In documenting the business processes of enterprise architecture, component identification system 42 could be programmed to monitor user 64 interactions with applications. In addition, component identification system 42 could be programmed to "parse" each application to determine the possible steps that could be taken by a user 64. Still yet, as mentioned above, component identification system 42 could provide one or more interface pages into which data for the business processes could be input (e.g., by an administrator or the like) . Regardless of the implementation, an understanding of the business processes carried out using enterprise architecture 16 can be developed and documented.

After the components of enterprise architecture have been identified in this manner, enterprise architecture profiling system 44 will develop an enterprise architecture profile based thereon. The profile can take any type of format now known or later developed. For example, the enterprise architecture profile can include a graphical architectural diagram depicting the hardware and software components as well as any interconnections therebetween. Moreover, such a profile can depict or "trace" the transactions that can occur between the components. Alternatively, the enterprise architecture profile could have a tabular format that includes all of the information discussed above.

III. Transaction Class Profiling

In any event, once the components of enterprise architecture 16 have been identified and profiled, transaction data system 46 will collect data for each identified transaction and step/click. In performing this task, transaction data system 46 can ensure (or request) that any prerequisites are met. Under a typical embodiment of the present invention, prerequisites can include the following: transaction data is collected in a LAN environment; transaction data collection occurs between web clients and web servers, and between application servers and databases of enterprise architecture 16; any load-balancing present in enterprise architecture 16 is taken offline; network switch ports are mirrored for clients and web servers; and any servers in enterprise architecture 16 not related to the transaction testing are taken offline.

Transaction data collection under the present invention can involve several distinct elements. For example, transaction data system 46 can

execute each transaction, and for each transaction and/or underlying step/click, determine the resources required such as: bytes transmitted and received; application turns, TCP turns, time to perform each transaction and/or turn; and delays/latency time (transaction, network propagation, Protocol, etc.)- To determine this data, transaction data system 46 could trace a set of business scenarios that a user would normally execute on a workday and monitor the interactions to determine the needed information such as the total bytes sent and received, average bps/user (bandwidth requirement), etc. In addition, transaction data system 46 will typically collect such data for different geographic regions within enterprise architecture 16. One issue not addressed by previous systems is the difference in transaction data for different geographic regions. For example, it could be the case that one geographic region has a latency that another geographic region does not. To this extent, a transaction between geographic regions A and B could yield a completely different transaction response time than would a transaction between geographic regions A and C. Still yet, transaction data system 46 can collect transaction data based on the types of users executing the transactions, their usage patterns as well as data on the transactions themselves. Along these lines, the transaction data could also include a size of each step or turn, a size of any attachments, a frequency of transactions, steps/clicks and/or turns (e.g., how many times in an hour a transaction is executed), etc.

Once all pertinent transaction data has been collected, transaction profiling system 48 will develop at least one transaction class profile based upon the data. In a typical embodiment the transaction class profile developed details a business scenario, a set of steps, a transaction number, a transaction duration, a bandwidth requirement and a number of application turns for the each of the set of transactions. Referring to Fig. 2, an illustrative transaction class profile 70 is depicted. Four different transactions 72A-D are shown. Each transaction 72A-D is accompanied by a business scenario/class 74, a transaction description 76, a transaction number 78, a duration 80, a number of byes 82 and a number of application turns 84. Furthermore, each transaction 72A-D can include one or more steps/clicks. For example, transaction 72A includes the steps 76 of "click on binoculars," and "click the find button . "

IV. Estimation of Transaction Response Time(s)

Referring back to Fig. 1, after transaction profile 70 (Fig. 2) has been developed, transaction response time system 50 will estimate a transaction response time for each transaction based upon the enterprise architecture profile and transaction class profile. Specifically, the transaction response times are typically based on geographic regions, and involve a baseline time, a network propagation time and a data transmission time. When summed, these times generally represent the entire estimated transaction response time. Transaction response time system 50 will then generate a report containing these times by geographic region .

Referring to Fig. 3, an illustrative report 100 is shown. In general, report 100 will show each step/click in each transaction and its corresponding times. The example shown in Fig. 3 is for a "navigate to accounts screen" step of a transaction, as noted under column 102. As can be seen, times for this step are shown for different geographic regions under column 104. Baseline times, network propagation times, data transmission times and total times are shown under columns 106, 108, 110 and 112, respectively. In viewing report 100, it can be seen that for the step of "navigating to accounts screen," between Brussels and Portsmouth, the baseline time was 10.215 seconds (the baseline time was the same for all regions for this step), the network propagation time was 0.13754 seconds, and the data transmission time was 0.00583 seconds. These values yielded a total estimated transaction response time of 10.35837 seconds.

Referring now to Fig. 4, an illustrative method flow diagram 110 is shown. As shown, first step Sl of method 100 is to identify components of an enterprise architecture. Second step S2 is to develop an enterprise architecture profile based on the identified components. Third step S3 is to collect data based upon a set of transactions for different geographic regions within the enterprise architecture. Fourth step S4 is to develop at least one transaction class profile based upon the data. Fifth step S5 is to estimate a transaction response time based upon the enterprise architecture profile and the at least one transaction class profile.

While shown and described herein as a method and system for estimating a transaction response time, it is understood that the invention further provides various alternative embodiments. For example, in one embodiment, the invention provides a computer-readable medium that includes computer program code to enable a computer infrastructure to a estimate transaction response time. To this extent, the computer-readable medium includes program code that implements each of the various process

steps of the invention. It is understood that the term "computer-readable medium" comprises one or more of any type of physical embodiment of the program code. In particular, the computer-readable medium can comprise program code embodied on one or more portable storage articles of manufacture (e.g., a compact disc, a magnetic disk, a tape, etc.), on one or more data storage portions of a computing device, such as memory 22 (Fig. 1) and/or storage system 30 (Fig. 1) (e.g., a fixed disk, a read-only memory, a random access memory, a cache memory, etc.), and/or as a data signal (e.g., a propagated signal) traveling over a network (e.g., during a wired/wireless electronic distribution of the program code) .

In another embodiment, the invention provides a business method that performs the process steps of the invention on a subscription, advertising, and/or fee basis. That is, a service provider, such as a Solution Integrator, could offer estimate a transaction response time. In this case, the service provider can create, maintain, support, etc., a computer infrastructure, such as computer infrastructure 12 (Fig. 1) that performs the process steps of the invention for one or more customers. In return, the service provider can receive payment from the customer (s) under a subscription and/or fee agreement and/or the service provider can receive payment from the sale of advertising content to one or more third parties .

In still another embodiment, the invention provides a method for estimating a transaction response time. In this case, a computer infrastructure, such as computer infrastructure 12 (Fig. 1), can be provided and one or more systems for performing the process steps of the invention can be obtained (e.g., created, purchased, used, modified, etc.) and deployed to the computer infrastructure. To this extent, the deployment of a system can comprise one or more of (1) installing program code on a computing device, such as computer system 14 (Fig. 1), from a computer-readable medium; (2) adding one or more computing devices to the computer infrastructure; and (3) incorporating and/or modifying one or more existing systems of the computer infrastructure to enable the computer infrastructure to perform the process steps of the invention.

As used herein, it is understood that the terms "program code" and "computer program code" are synonymous and mean any expression, in any language, code or notation, of a set of instructions intended to cause a computing device having an information processing capability to perform a particular function either directly or after either or both of the following: (a) conversion to another language, code or notation; and/or

(b) reproduction in a different material form. To this extent, program code can be embodied as one or more of: an application/software program, component software/a library of functions, an operating system, a basic I/O system/driver for a particular computing and/or I/O device, and the like.