Claims:1. A method for analyzing one or more incidents, said method comprising hardware processor implemented steps of:
logging one or more incident in an incident management solutionsusing an Incident Logging Module (120), wherein the incident management solutionsenables user to log one or more said incident;
storing the one or more incidents in a Database (108), wherein the Database stores information pertaining to one or more incidents, comprising one or more incident errors, one or more incident error description, incident time and incidents login information;
invoking one or more logged in incident by the incident management solutionsto a search engine module (130) wherein the search engine module is configured to collect the one or more incident errors, the one or more incident error descriptions and the time for each incident is logged to the incident management solutions;
identifying one or more identical incident functionalities pertaining to one or more incident, by the search engine module (130), wherein the identical incident functionalities are comprises of one or more solutionsfeatures developed; and receiving one or more search data from the one or more incident error logs;
listing one or more identical incidents in the incident management solutions, wherein the one or more of incidents are auto prioritized by the incident management solutionsand store one or more updated incidents in the Database (108);
categorizing the one or more identical incidents by a categorization module (140), wherein the categorizations module categorizes, one or more incidents, wherein the categorization comprises one or more functionalities and one or more sub functionalities of a third party applications;
generating the one or more identical incidents by a Generator module (150), wherein the generator module generates, one or more functionalities and one or more sub functionalities of the third party applications;
and;
displaying the one or more identical incidents by a display module (160) in the incident management solutions, wherein the display module (160) displays, one or more identical incidents of the third party applications.
2. The method of claim 1, wherein the one or more incidents comprises of one or more errors found in one or more solutionsand one or more malfunctioning in solutions behavior.

3. The method of claim 1, wherein the malfunctioning in third party application behavior comprises one or more login errors, one or more accessing errors, one or more data input errors, one or more data output errors, one or more data processing errors.

4. The method of claim 1, wherein one or more historical incidents are stored in the Database (108), wherein the Database (108) stores one or more incidents received from incident management solutions.

5. The method of claim 1, wherein the identical incidents comprise a one or more incidents are compared with the historical data to identify one or more identical matches.

6. The method of claim 1, wherein the incident management solutionsgenerates one or more suggested solution for one or more identical incidents.

7. The method of claim 1, wherein the Database (108) is updated periodically with the one or more identical incidents with plurality of suggested solution for each of the incidents.

8. A system (100) for analysis of incidents; said system (100) comprising:
a hardware processor (104);
an I/O interface (106) to receive one or more incidents;
a computer-usable medium embodying computer code, said computer-usable medium being coupled to said hardware processor (104), said computer program code comprising instructions executable by said hardware processor (104) and configured to:
log one or more incident in an incident management solutionsto an Incident Module (120), wherein the incident management solutionsenables user to log one or more said incident;
store one or more incidents to a Database (108), wherein the Database stores
information pertaining to one or more incidents, comprising one or more incident errors, one or more incident error description, incident time and incidents login information;
invoke one or more logged in incident by the incident management solutionsto a search engine module (130) wherein the search engine module is configured to collect the one or more incident errors, the one or more incident error descriptions and the time for each incident is logged to the incident management solutions;
identify one or more identical incident functionalities, pertaining to one or more incident by a search engine module (130), wherein the identical incident functionalities are comprises of one or more application features developed; and receiving one or more search data from the one or more incident error logs;
list one or more identical incidents in the incident management solutions, wherein the one or more of incidents are auto prioritized by the incident management solutionsand store one or more updated incidents in the Database (108);
categorize the one or more identical incidents by a categorization module (140), wherein the categorizations module categorizes, one or more incidents, wherein the categorization comprises one or more functionalities and one or more sub functionalities of a third party applications;
generate the one or more identical incidents by a Generator module (150), wherein the generator module generates, one or more functionalities and one or more sub functionalities of the third party applications;
and;
display the one or more incidents by a display module (160) in the incident management solutions, wherein the display module (160) displays, one or more identical incidents of the third party solutions.

9. The method of claim 9, wherein the display module (160) displays one or more of suggested solution for each of the incidents logged in to the incident management solutions.
, Description:FORM 2

THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003

COMPLETE SPECIFICATION
(See Section 10 and Rule 13)

Title of invention:
SYSTEM AND METHOD FOR INCIDENTS ANALYSIS

Applicant:
Tata Consultancy Services Limited
A company Incorporated in India under the Companies Act, 1956
Having address:
Nirmal Building, 9th floor,
Nariman point, Mumbai 400021,
Maharashtra, India

The following specification particularly describes the invention and the manner in which it is to be performed.

FIELD OF THE INVENTION
[001] The present invention relates to a system and method for incidents analysis. More particularly, the present invention, in various specific embodiments, involves methods and systems for analyzing different error incident logged for solutions.

BACKGROUND OF THE INVENTION
[002] Incident management is an important activity in any information technology system. Incidents can rapidly impact business operations of any organization and its customers, if not effectively managed and addressed. There are numbers of Incident management software application are available for collecting and reporting incidents with respective time with sensitivity of the incidents. Many of such Incident management solutions include features to automate the approval process of an incident report. These Incident management solutions may also have the functionality to gather real time incident information such as data pertaining to time and date. Also such Incident management solutions additionally send automated notifications, assigning of tasks and may be escalations to appropriate associates depending on the incident type, priority, status etc. Administrating the incident by an administrator is one of the major challenges while configuring the Incident report forms as needed, create analysis reports and set access controls on the data. Without an effective automated incident management application, it is very difficult to analyze incidents logged by the user manually which may result in improper analysis and may require additional efforts in maintaining the incidents. There would be various types of incidents occurred where, it’s difficult to get an updated view of incidents instantly. Also there is no keyword search of incidents for easy tracking of issues. Also, identifying the recurring defects in a software product/application will be time consuming.

[003] Prior art literature illustrates various tool and functionalities, however none of them is able to help incident administrator to analyze incidents logged by the user, automated identification of recurring incidents, instant updated status view of incidents, keyword search of incidents for easy tracking of issues.

OBJECTIVE OF THE INVENTION
[004] In accordance with the present invention, the primary objective is to provide a system and method for incidents analysis.
[005] Another objective of the invention is to provide automated overview of incidents with analysis.

[006] Yet another objective of the invention is to maintain incidents logs in a repository.

[007] Yet another objective of the invention is to provide a pictorial visualization of common incidents highlighting by the system.

[008] Yet another objective of the invention is to enable accurate analysis of incidents.

[009] Yet another objective of the invention is to provide solution for the recurring issues.

[0010] Yet another objective of the invention is to search the identical functionalities used for the historical issues.

[0011] Yet another objective of the invention is to search the identical functionalities used for the issues identified

[0012] Other objectives and advantages of the present invention will be more apparent from the following description when read in conjunction with the accompanying figures, which are not intended to limit the scope of the present disclosure.

SUMMARY OF THE INVENTION
[0013] Before the present methods, systems, and hardware enablement are described, it is to be understood that this invention is not limited to the particular systems, and methodologies described, as there can be multiple possible embodiments of the present invention which are not expressly illustrated in the present disclosure. It is also to be understood that the terminology used in the description is for the purpose of describing the particular versions or embodiments only, and is not intended to limit the scope of the present invention which will be limited only by the appended claims.

[0014] The present application provides a method and system for analyzing one or more incidents.
[0015] The present application provides a computer implemented method for analyzing one or more incidents comprising hardware processor implemented steps of logging incidents in an incident management application using an Incident Logging Module. The incident management application enables user to log incidents; storing incidents in a Database (108). The Database stores information pertaining to incidents. The incident errors further comprises of one or more incident errors, one or more incident error description, incident time and incidents login information; invoking logged in incident by the incident management application to a search engine module. The search engine module is configured to collect said incident errors, the incident error descriptions and the time for each incident is logged to the incident management application; identifying identical incident functionalities pertaining to the incidents, by the search engine module. The identical incident functionalities further comprises one or more application features developed; and receiving one or more search data from the incident error logs; listing identical incidents in the incident management application. The incidents are further auto prioritized by the incident management application and store updated incidents in the Database; categorizing the identical incidents by a categorization module. The categorizations module further categorizes incidents as functionalities and sub functionalities of a third-party application; generating identical incidents by a Generator module. Then the generator module generates functionalities and sub functionalities of the third-party applications; and displaying identical incidents by a display module in the incident management application. The display module displays identical incidents of the third party applications.

[0016] The present application provides a computer implemented system for analyzing one or more incidents. The system comprising a hardware processor (104); a I/O interface (106) to receive one or more incidents; a computer-usable medium embodying computer code, said computer-usable medium being coupled to said hardware processor (104), said computer program code comprising instructions executable by said hardware processor (104) and configured to: log incident in an incident management application to an Incident Module (120). The incident management application enables user to log one or more said incident; store one or more incidents to a Database (108). The Database stores information pertaining to the incidents. The incident comprises incident errors, incident error description, and incident time and incidents login information; invoke logged in incident by the incident management application to a search engine module (130). The search engine module is configured to collect incident errors, incident error descriptions and the time for each incident is logged to the incident management application; identify identical incident functionalities, pertaining to the incidents by a search engine module (130). The identical incident functionalities further comprises of application features developed; and receiving search data from the one or more incident error logs; list identical incidents in the incident management application. The incidents are further auto prioritized by the incident management application and store one or more updated incidents in the Database (108); categorize identical incidents by a categorization module (140). The categorizations module categorizes the incidents. The categorization comprises one or more functionalities and one or more sub functionalities of a third party application; generate identical incidents by a Generator module (150). The generator module generates, one or more functionalities and one or more sub functionalities of the third party applications; and; display one or more incidents by a display module (160) in the incident management application. The display module (160) displays, one or more identical incidents of the third party applications.

BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The foregoing summary, as well as the following detailed description of preferred embodiments, are better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings exemplary constructions of the invention; however, the invention is not limited to the specific methods and system disclosed. In the drawings:

[0018] FIG. 1 shows a system diagram illustrating architecture of a system and method for incidents analysis in accordance with an embodiment of the invention;

[0019] FIG. 2 shows a flow diagram illustrating steps involved in analyzing error incidents for a software in accordance with an embodiment of the invention;

[0020] FIG. 3 shows a flow diagram illustrating flow of incidents raised and stored in the database in accordance with an embodiment of the invention;

[0021] FIG. 4 shows a system illustrating a pictorial view of Incidents dashboard matrix in accordance with an embodiment of the invention;

[0022] FIG. 5A shows a system illustrating searching of an incident using reference number in accordance with an embodiment of the invention;

[0023] FIG. 5B shows a system illustrating an incident highlighted in the branched linked on one of the incident categories in accordance with an embodiment of the invention;

[0024] FIG. 5C shows a illustrative example of a projection of incidents in various months in accordance with an embodiment of the invention;

[0025] FIG. 6 shows an illustrating detailed view list of incidents and all the descriptions associated with the incidents in accordance with an embodiment of the invention;

[0026] FIG. 7 shows a flow diagram illustrating automated incident analysis and automated known error database creation in accordance with an embodiment of the invention;

[0027] FIG. 8 shows a flow diagram illustrating the detection of identical functionalities from the issue logged.

DETAILED DESCRIPTION OF THE INVENTION
[0028] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0029] The words “comprising,” “having,” “containing,” and “including,” and other forms thereof, are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items.

[0030] It must also be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise. Although any systems and methods similar or equivalent to those described herein can be used in the practice or testing of embodiments of the present disclosure, the preferred, systems and methods are now described.

[0031] Some embodiments of this disclosure, illustrating all its features, will now be discussed in detail. The disclosed embodiments are merely exemplary of the disclosure, which may be embodied in various forms.

[0032] Before setting forth the detailed explanation, it is noted that all of the discussion below, regardless of the particular implementation being described, is exemplary in nature, rather than limiting.

[0033] Referring now to the drawings, and more particularly to FIG. 1 through 8, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments and these embodiments are described in the context of the following exemplary systems and/or methods.

[0034] FIG. 1 is a block diagram of an incident analysis system 100 for analysis of incidence for software according to an embodiment of the present disclosure. The terms “incident analysis system and” and “system” may be interchangeably used herein after. The system 100 may for example, is an incident management software application. The system 100 comprises a memory 102, a hardware processor 104, an input/output (I/O) interface 106 and a database 108. Although the exemplary block diagram and the associated description refer to a memory and a hardware processor, it may be understood that one or more memory units and one or more hardware processors may be comprised in the incident analysis system 100. The memory 102 further includes one or more functional modules 110. The memory 102, the hardware processor 104, the input/output (I/O) interface 106, the database 108 and/or the modules 110 may be coupled by a system bus or a similar mechanism. The incident analysis system 100 generates incident reports based on one or more incidents logs received from one or more sources. The one or more sources may comprise, for example but are not limited to, software incident logs, user incident logs, and the like. The one or more incidents are been tracked by the incident analysis system and generate one or more incident error reports.

[0035] The memory 102, may store instructions, any number of pieces of information, and data, used by a computer system, for example the system 100 to implement the functions of the system 100. The memory 102 may include for example, volatile memory and/or non-volatile memory. Examples of volatile memory may include, but are not limited to volatile random access memory (RAM). The non-volatile memory may additionally or alternatively comprise an electrically erasable programmable read only memory (EEPROM), flash memory, hard drive, or the like. Some examples of the volatile memory includes, but are not limited to, random access memory, dynamic random access memory, static random access memory, and the like. Some example of the non-volatile memory includes, but are not limited to, hard disks, magnetic tapes, optical disks, programmable read only memory, erasable programmable read only memory, electrically erasable programmable read only memory, flash memory, and the like. The memory 102 may be configured to store information, data, instructions or the like for enabling the system 100 to carry out various functions in accordance with various example embodiments.

[0036] Additionally or alternatively, the memory 102 may be configured to store instructions which when executed by the hardware processor 104 causes the system 100 to behave in a manner as described in various embodiments. The memory 102 stores the functional modules and information, for example, incident details received from the one or more sources (not shown in FIG. 1) incident analysis system 100.

[0037] The hardware processor 104 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Further, the hardware processor 104 may comprise a multi-core architecture. Among other capabilities, the hardware processor 104 is configured to fetch and execute computer-readable instructions or modules stored in the memory 102. The hardware processor 104 may include circuitry implementing, among others, audio and logic functions associated with the communication. For example, the hardware processor 104 may include, but are not limited to, one or more digital signal processors (DSPs), one or more microprocessor, one or more special-purpose computer chips, one or more field-programmable gate arrays (FPGAs), one or more application-specific integrated circuits (ASICs), one or more computer(s), various analog to digital converters, digital to analog converters, and/or other support circuits.

[0038] The hardware processor 104 thus may also include the functionality to encode messages and/or data or information. The hardware processor 104 may include, among others a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the hardware processor 104. Further, the hardware processor 104 may include functionality to execute one or more software programs, which may be stored in the memory 102 or otherwise accessible to the hardware processor 104.

[0039] FIG. 2, with reference to FIG. 1, is a flow diagram illustrating a method of analyzing one or more incidents in the incident analysis system 100 according to an embodiment of the present disclosure. The steps of the method of the present disclosure will now be explained with reference to the components of the system 100 as depicted in FIG. 1. The hardware processor 104 is configured by the instructions stored in the memory 102. The hardware processor 104 when configured by the instructions to log one or more incidents as described hereinafter. In an embodiment, at step 202, the hardware processor 104 receives one or more incident logs. In an embodiment, each of the one or more incidents comprises one or more category, one or more subcategory and incident descriptions.

[0040] At step 204, the plurality incidents are stored in to a database. In an embodiment, the incidents are stored in a pre-defined tabular format. In an embodiment, the tabular format comprises one or more reference number, the one or more category, the one or more sub category the one or more incident description, one or more solution to the incidents and incident logged date. When a new feature is implemented in system, the hardware processor generates the one or more category and one or more subcategory with respect to one or more new functionality, then the one or more new functionality are stored it in the database.

[0041] At step 206, the hardware processor 104 invokes the one or more incidents to a search engine module. In an embodiment, the search engine module is configured to search the one or more incidents from the database 108. At step 208, the search engine module identifies plurality of identical incidents and non-identical incidents. At the step 210, the identical incident comprises historical logged incidents, wherein the identical and non-identical incidents are stored in the database 108.

[0042] At step 212, of identical incidents and non-identical incidents are categorized by a categorization module. In an embodiment, the identical incidents and non-identical incidents are categorized such as reference number if the identical and non-identical incidents, description of the identical and non-identical incidents and the like. At step 214, the plurality of identical incidents and the plurality of non-identical incidents are generated by a generator module. At step 216, one or more solutions are displayed to the user based on the grouping of the plurality of identical incidents and the plurality of non-identical incidents.

[0043] FIG. 3 is an exemplary workflow of incident analysis, wherein user logs one or more incident to the system. In an embodiment the one or more incidents are logged by the user to the incident management system by selecting a category for example a Railway Ticket Management System, a subcategory for Example Booking a Ticket, and a description for Example Availability of Train is not getting displayed, for the incident. The hardware processor 104 is configured to display one or more options of the description for the incidents chosen. For some of the incidents, hardware processor 104 may not display description. For these incidents, the hardware processor 104 is configured to update a master table stored in the database, wherein the master table comprises a history list of incidents, a history list of category, a history list of sub category and history list of description corresponding to the one or more incidents.

[0044] In another embodiment, the hardware processor 104 is configured to generate, a unique reference number for the one or more incidents raised in the system. All the associated details (e.g. incidents details, incident category and sub category and the like) are tag to the unique reference number. Also the unique reference number is used to track, follow, closure etc. by the system.

[0045] In another embodiment, at the step 302, a user logged in to the incident analysis system. At the step 304 the user raises an incident while selecting the category, subcategory, description, solution and logged date. The hardware processor 104 is configured to send the incident details (e.g. The category, the subcategory, the description, the solution and the logged date) to the database 108. At the step 306, the hardware processor is configured to extract incident details from the database 108 to a support user. The support user receives an automated notification from the system. The hardware processor is configured to alert appropriate solution to one or more incident. The solutions are known incidents are retrieved from the database 108. The system is also act as a known error database. For one or more new incidents, whose incidents are not listed in the master sheet, the support user closes the incident by providing a solution. At the step 308, the one or more new incident details are updated in the database 108.

[0046] FIG. 4 is an exemplary incidents dashboard matrix of incidents 400, wherein the incident matrix are maintained in the database 108. In an embodiment, the dashboard matrix displays the number of incidents raised in one or more months in a calendar year. In an embodiment, the incidents dashboard matrix shows the variation of number of incidents in the one or more month in the calendar year. (E.g. the month of the calendar year starts form January (Jan) to December (Dec). the hardware processor is configured to extract the data month wise form the database 108. A specific (e.g. Feb) month shows the number of incidents logged in to the system. On the other hand the hardware processor is configured to displays the probable solution to the incidents for the month (Feb)).

[0047] In another embodiment, the master list displays one or more incident category and count of incidents in each category. Further the one or more sub category is also liked to the respective incident category. On the other hand the incident descriptions are also description linked with the one or more subcategory and the one or category. The incident descriptions are linked with the one or more subcategory and the one or category like branches, wherein the number of branches increases with the increase of incidents in one or more category. The hardware processor 104 is configured to identify the category where the maximum incidents are logged to the system.

[0048] On the other hand, the hardware processor is configured to allow user to scroll and select one or more respective months to view the analysis of incidents raised on that particular month in the selected calendar year. Further, the hardware processor 104 is configured to search the one or more incidents with the reference number. Then if the match for the reference number is found in the system and then the one or more incidents will be highlighted in the branch, wherein the incidents are linked to the subcategory. The hardware processor is configured to display the one or more incidents category or subcategory with color code, wherein the color codes are classified as “High”, ”Medium”, and “Low”. The Black color indicates high volume of tickets, The Grey color indicates medium volume of tickets and Light grey color indicates low volume of tickets. Further the color code enables user to identify the areas where immediate action is required. Further the system is configured to show the count of the one or more incidents on month in a specific calendar.

[0049] FIG. 5A depicts user interface 500, to search the one or more incident using reference number 502, wherein the hardware processor is configured to generate a reference number while logging an incident in the incident analysis system. The reference numbers are unique values which are tagged to the incident number. FIG. 5B, displays the one or more incidents highlighted Incidents highlighted in the branched linked 510, as Black thick line 512 to the one or more subcategory. FIG. 5C, displays shows an exemplary the projection 520, of the one or more incidents from left to right, wherein the one or more incidents are represented from with the search incident on the left tagged with the month and moving to the right. Further the system displays the plurality of identical incidents, which were logged earlier by the users on one or more previous months. The hardware process is configured to display a solution 522, while selecting a reference number for a specific month (e.g. March, ref 1). The hardware processor is configured to alert user indicating the solution for the new incident raised, wherein the new incidents raised could match to the historical incident type and the solution provided.

[0050] FIG. 6 illustrates an exemplary view of view list of the one or incidents and all the descriptions associated with the one or more incidents. The hardware processor is configured to extract the description for one or more category type. Further the system allows user to select and view description for the one or more category.

[0051] FIG. 7 depicts a flowchart of the automated incident analysis and automated known error database 700. An incident is raised by a user in an incident management application. The one or more incidents will be stored in the database. Then incident management application automatically assigns one or more incidents to one or more support user. One or more incidents will be processed and automated solution will be provided by the incident management application though the support user, which is then stored in the database. The one or more incident details with respective solutions are analyzed through an automated system which enables the system to present the data in a pictorial way.

[0052] FIG. 8 depicts the flow of one or more incident error when it is logged in the system. The system is also enabled to identify one or more functionalities where the probability of occurrence of the issue is high 800, wherein the hardware processor is configured to associate the incidents logged with the respective error logs generated in the system. The system determines the one or more functionality where the actual error has happened. In an embodiment, the search engine module is configured to search the same logic through the entire system for identifying the plurality of identical incidents that occur in system. Further the system allows the user to provide a suitable solution to the affected areas.

[0053] The written description describes the subject matter herein to enable any person skilled in the art to make and use the embodiments. The scope of the subject matter embodiments is defined by the claims and may include other modifications that occur to those skilled in the art. Such other modifications are intended to be within the scope of the claims if they have similar elements that do not differ from the literal language of the claims or if they include equivalent elements with insubstantial differences from the literal language of the claims.

[0054] It is, however to be understood that the scope of the protection is extended to such a program and in addition to a computer-readable means having a message therein; such computer-readable storage means contain program-code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The hardware device can be any kind of device which can be programmed including e.g. any kind of computer like a server or a personal computer, or the like, or any combination thereof. The device may also include means which could be e.g. hardware means like e.g. an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. Thus, the means can include both hardware means and software means. The method embodiments described herein could be implemented in hardware and software. The device may also include software means. Alternatively, the embodiments may be implemented on different hardware devices, e.g. using a plurality of CPUs.

[0055] The embodiments herein can comprise hardware and software elements. The embodiments that are implemented in software include but are not limited to, firmware, resident software, microcode, etc. The functions performed by various modules described herein may be implemented in other modules or combinations of other modules. For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can comprise, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

[0056] The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-R/W), BLU-RAY, and DVD.

[0057] A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.

[0058] Input/output (I/O) devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters.

[0059] A representative hardware environment for practicing the embodiments may include a hardware configuration of an information handling/computer system in accordance with the embodiments herein. The system herein comprises at least one processor or central processing unit (CPU). The CPUs are interconnected via system bus to various devices such as a random access memory (RAM), read-only memory (ROM), and an input/output (I/O) adapter. The I/O adapter can connect to peripheral devices, such as disk units and tape drives, or other program storage devices that are readable by the system. The system can read the inventive instructions on the program storage devices and follow these instructions to execute the methodology of the embodiments herein.

[0060] The system further includes a user interface adapter that connects a keyboard, mouse, speaker, microphone, and/or other user interface devices such as a touch screen device (not shown) to the bus to gather user input. Additionally, a communication adapter connects the bus to a data processing network, and a display adapter connects the bus to a display device which may be embodied as an output device such as a monitor, printer, or transmitter, for example.

[0061] The preceding description has been presented with reference to various embodiments. Persons having ordinary skill in the art and technology to which this application pertains will appreciate that alterations and changes in the described structures and methods of operation can be practiced without meaningfully departing from the principle, spirit and scope.