An exemplary method for reducing complexity of at least one user task includes steps of calculating a complexity metric for the at least one user task; identifying one or more usability issues having a measurable impact on the complexity metric for the at least one user task; determining one or more recommendations for addressing at least one of the one or more usability issues; and displaying a representation of at least one of the one or more usability issues and of at least one of the one or more recommendations. In an illustrative embodiment, implementing any one of the one or more recommendations reduces the impact of the usability issue on the complexity metric of the at least one user task and thereby reduces a complexity of the at least one user task.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method comprising the steps of: deploying and executing a plurality of different versions of a software system on one or more computer nodes of a computer network; executing a computerized process to generate and display a representation of complexity metrics for one or more software tasks corresponding to the different versions of said software system executing on the one or more computer nodes, wherein the computerized process comprises: capturing user interaction data corresponding to user interactions with graphical user interfaces of the different versions of the software system by one or more users performing the one or more software tasks using the different versions of the software system, wherein the user interaction data comprises an analysis of information with regard to at least one of (i) user navigation flows through the software system when performing the one or more software tasks, (ii) user input of parameter values when performing the one or more software tasks, and (iii) output data generated by the software system in response to actions taken by the one or more users when performing the one or more software tasks; processing the captured user interaction data to compute a complexity metric for a same software task in each of a plurality of different implementations of the same software task for each of the different versions of the software system, and thereby obtain a plurality of complexity metrics for the same software task for the plurality of different implementations of the same software task in each of said different versions of said software system; and generating, and displaying a representation of the complexity metrics for the one or more software tasks corresponding to the different versions of said software system; wherein the representation provides a comparison of respective ones of the plurality of complexity metrics for the same software task corresponding to respective ones of the plurality of different implementations of the same software task in each of said different versions of said software system.
The invention is a method for comparing the complexity of software tasks across different versions of the same software. It involves running different versions of a software system, capturing user interaction data (navigation, input parameters, output data) as users perform the same task on each version. This interaction data is processed to compute a "complexity metric" for each version. Finally, the complexity metrics are displayed in a way that allows for direct comparison of the different software versions and their implementations of the same task. The complexity metric reflects how easily users can perform the task on each version.
2. The method of claim 1 , further comprising the step of determining at least one value proposition for at least a first implementation of the plurality of different implementations relative to at least a second implementation of the plurality of different implementations based at least in part on the comparison of the complexity metric for the same software tusk in the first implementation and the complexity metric for the same software task in the second implementation.
The method for comparing software task complexity from the previous description further includes determining a "value proposition" for one software implementation compared to another. This value proposition is based, at least in part, on comparing the complexity metrics of the same software task across different implementations. For example, if implementation A has a lower complexity metric than implementation B for the same task, this suggests a better user experience and a higher value proposition for implementation A.
3. The method of claim 1 , Wherein the plurality of different implementations of the same software task represent implementations of the same software task in different versions of the same software system of a given vendor.
The method for comparing software task complexity described earlier has a variation where the different implementations being compared are different versions of the same software system, produced by the same vendor. For example, comparing how a specific feature works in version 1.0 versus version 2.0 of the same software, both created by Company X. The complexity metric helps understand if the new version simplifies or complicates the user experience for that specific task.
4. The method of claim 1 , wherein the plurality of different implementations of the same software task represent implementations of the same software task in different versions of a given software system from different vendors.
The method for comparing software task complexity described earlier has a variation where the different implementations being compared come from different vendors' software systems. This means comparing the same task performed in competing software products. For example, comparing how creating a chart works in Microsoft Excel versus Google Sheets. The complexity metric helps determine which software offers a simpler and more efficient user experience for the same functionality.
5. An apparatus, comprising: at least one processor; and at least one memory comprising stored program instructions, which is coupled to the at least one processor; wherein the at least one processor is operative to execute the stored program instructions to perform a process comprising: deploying and executing a plurality of different versions of a software system on one or more computer nodes of a computer network; executing a computerized process to generate and display a representation of complexity metrics for one or more software tasks corresponding to the different versions of said software system executing on the one or more computer nodes, wherein the computerized process comprises: capturing user interaction data corresponding to user interactions with graphical user interfaces of the different versions of the software system by one or more users performing the one or more software tasks using the different versions of the software system, wherein the user interaction data comprises an analysis of information with regard to at least one of (i) user navigation flows through the software system when performing the one or more software tasks, (ii) user input of parameter values when performing the one or more software tasks, and (iii) output data generated by the software system in response to actions taken by the one or more users when performing the one or more software tasks; processing the captured user interaction data to compute a complexity metric for a same software task in each of a plurality of different implementations of the same software task for each of the different versions of the software system, and thereby obtain a plurality of complexity metrics for the same software task for the plurality of different implementations of the same software task in each of said different versions of said software system; and generating and displaying a representation of the complexity metrics for the one or more software tasks corresponding to the different versions of said software system; wherein the representation provides a comparison of respective ones of the plurality of complexity metrics for the same software task corresponding to respective ones of the plurality of different implementations of the same software task in each of said different versions of said software system.
The invention is an apparatus (computer system) with a processor and memory, programmed to compare the complexity of software tasks across different versions of the same software. The system runs different versions of software, captures user interaction data from GUIs (navigation, input parameters, output data) as users perform tasks. This data is processed to calculate a complexity metric for each version. The system generates and displays a comparison of these metrics for the same task across different versions, showing which versions make the task easier or harder for the user.
6. The apparatus of claim 5 , wherein the at least one processor is operative to perform the step of determining at least one value proposition for at least a first implementation of the plurality of different implementations relative to at least a second implementation, of the plurality of different implementations based at least in part on the comparison of the complexity metric for the same software task in the first implementation and the complexity metric for the same software task in the second implementation.
The apparatus (computer system) from the previous description is further programmed to determine a "value proposition" for one software implementation compared to another. This comparison is based on the complexity metrics calculated for each implementation of the same software task. For example, if one implementation has a significantly lower complexity metric, it suggests it offers a better and more efficient user experience, thus providing a higher value to the user.
7. The apparatus of claim 5 , Wherein the plurality of different implementations of the same user task represent implementations of the same software task in different versions of the same software system of a given vendor.
The apparatus (computer system) for comparing software task complexity described earlier has a variation where the different implementations being compared are different versions of the same software system, produced by the same vendor. For example, comparing how a specific feature works in version 1.0 versus version 2.0 of the same software, both created by Company X. The complexity metric helps understand if the new version simplifies or complicates the user experience for that specific task.
8. The apparatus of claim 5 , wherein the plurality of different implementations of the same user task represent implementations of the same user task in different versions of a given software system from different vendors.
The apparatus (computer system) for comparing software task complexity described earlier has a variation where the different implementations being compared come from different vendors' software systems. This means comparing the same task performed in competing software products. For example, comparing how creating a chart works in Microsoft Excel versus Google Sheets. The complexity metric helps determine which software offers a simpler and more efficient user experience for the same functionality.
9. A computer program product comprising a non-transitory computer readable recordable storage medium including computer usable program code, the computer program product comprising; computer usable program code for deploying and executing a plurality of different versions of a software system on one or more computer nodes of a computer network; computer usable program code for executing a computerized process to generate and display a representation of complexity metrics for one or more software tasks corresponding to the different versions of said software system executing on the one or more computer nodes, wherein the computer usable program code for executing the computerized process comprises: computer usable program code for capturing user interaction data corresponding to user interactions with graphical user interfaces of the different versions of the software system by one or more users performing the one or more software tasks using the different versions of the software system, wherein the user interaction data comprises an analysis of information with regard to at least one of (i) user navigation flows through the software system when performing the one or more software tasks, (ii) user input of parameter values when performing the one or more software tasks, and (iii) output data generated by the software system in response to actions taken by the one or more users when performing the one or more software tasks; computer usable program code for processing the captured user interaction data to compute a complexity metric for a same software task in each of a plurality of different implementations of the same software task for each of the different versions of the software system, and thereby obtain a plurality of complexity metrics for the same software task for the plurality of different implementations of the same software task in each of said different versions of said software system; and computer usable program code for generating and displaying a representation of the complexity metrics for the one or more software tasks corresponding to the different versions of said software system; wherein the representation provides a comparison of respective ones of the plurality of complexity metrics for the same software task corresponding to respective ones of the plurality of different implementations of the same software task in each of said different versions of said software system.
The invention is a computer program stored on a non-transitory medium that, when executed, compares the complexity of software tasks across different versions of the same software. The program deploys and runs different versions of the software system, captures user interaction data (navigation, input parameters, output data) as users perform the same task on each version. This data is processed to compute a "complexity metric" for each version. The program then generates and displays a comparison of these metrics, showing which versions make the task easier or harder to accomplish.
10. The computer program product of claim 9 , further comprising computer usable program code for determining at least one value proposition for at least a first implementation of the plurality of different implementations relative to at least a second implementation of the plurality of different implementations based at least in part on the comparison of the complexity metric for the same software task in the first implementation and the complexity metric for the same software task in the second implementation.
The computer program from the previous description further includes code for determining a "value proposition" for one software implementation compared to another. This value proposition is determined, at least in part, by comparing the complexity metrics for the same task across the different implementations. For example, if implementation A has a lower complexity metric than implementation B, the program infers that implementation A offers a better and more efficient user experience, and is therefore more valuable.
11. The computer program product of claim 9 , wherein the plurality of different implementations of the same software task represent implementations of the same software task in different versions of the same software system of a given vendor.
The computer program for comparing software task complexity described earlier has a variation where the different implementations being compared are different versions of the same software system, produced by the same vendor. This means the program is comparing how a specific feature works in version 1.0 versus version 2.0 of the same software, both created by Company X. The complexity metric helps understand if the new version simplifies or complicates the user experience for that specific task.
12. The computer program product of claim 9 , wherein the plurality of different implementations of the same software task represent implementations of the same software task in different versions of a Oven software system from different vendors.
The computer program for comparing software task complexity described earlier has a variation where the different implementations being compared come from different vendors' software systems. This means the program compares the same task performed in competing software products. For example, comparing how creating a chart works in Microsoft Excel versus Google Sheets. The complexity metric helps determine which software offers a simpler and more efficient user experience for the same functionality.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
October 12, 2015
August 22, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.