Software feature usage analysis and reporting

Abstract

Described is a technology for analyzing usage of a software program's features. Software instrumentation data is during actual user program usage sessions. The collected data is then processed to determine various feature usage counts and other information, cross-feature usage (e.g., among users who use a feature, how many use another feature or program), and characteristics of feature users, e.g., how long, how much, how often and how extensive feature users use a program. Session analysis may be performed to provide information about the number of sessions in which a set of features occur. Feature usage trends over time may also be determined via analysis. A user interface is described for facilitating selection of one or more features to analyze, for facilitating selection of a group of users, and/or for outputting results corresponding to the analysis.

Description

BACKGROUND

Understanding the way in which software users use software can be very valuable when working to improve the effectiveness and ease of use of software applications. Traditional ways to analyze software users include usability studies, user interviews, user surveys and the like.

Various data can be collected during actual software usage to obtain information related to how users use and otherwise interact with a software program. However, analyzing that data to obtain useful information is a difficult problem.

Moreover, cotemporary software is getting more and more sophisticated as advanced features are introduced. However, traditional usability studies only provide knowledge about feature usage that was obtained in artificial environments, which is not sufficient to understand software feature usage in real world applications.

SUMMARY

This Summary is provided to introduce a selection of representative concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used in any way that would limit the scope of the claimed subject matter.

Briefly, various aspects of the subject matter described herein are directed towards a technology by which usage of program features may be analyzed, including by determining feature usage metrics. Information representative of the feature usage metrics is output, such as in a report or the like.

Software instrumentation data is during actual user program usage sessions. The collected data is then processed to determine various feature usage counts and other information, cross-feature usage (e.g., among users who use a feature, how many use another feature or program), and characteristics of feature users, e.g., how long, how much, how often and how extensive feature users use a program. Session analysis may be performed to provide information about the number of sessions in which a set of features occur. Feature usage trends over time may also be determined via analysis.

In one example implementation, a system is described including an analyzer that processes information corresponding to the software instrumentation data recorded from user software program usage sessions to produce an output. The analyzer includes a feature usage analysis, a cross-feature usage analysis, an analysis of characteristics of feature users, a session analysis, and/or an analysis of feature usage trends. The analyzer may be coupled to a user interface for facilitating selection of one or more features, for facilitating selection of a group of users, and/or for outputting results corresponding to the analysis.

Other advantages may become apparent from the following detailed description when taken in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not limited in the accompanying figures in which like reference numerals indicate similar elements and in which:

FIG. 1 shows an example representation of recording software instrumentation data for subsequent analysis.

FIG. 2 shows a representation in a table format of example software instrumentation (e.g., software quality metrics) data saved for various program usage sessions by users of a suite of application programs.

FIG. 3 shows an example representation of a user interface and analyzer for analyzing software feature data based on the software instrumentation data.

FIG. 4 shows a representation of various example concepts related to analyzing feature usage.

FIG. 5 is a flow diagram representing various example concepts related to analyzing software feature usage and users.

FIG. 6 is an illustrative example of a general-purpose computing environment into which various aspects of the present invention may be incorporated.

DETAILED DESCRIPTION

Various aspects of the technology described herein are generally directed towards analyzing software data collected from real software users to model and recognize software users' usage of software features. Based on such feature modeling and recognition, further analysis such as analyzing characteristics of feature users, cross-feature usage, session analysis (e.g., where a session is typically from program start to finish) and so forth may be performed to gain a better understanding of feature usage.

To this end, example analyses are described herein that evaluate feature usage, generally comprising information about how many users use a feature, the average length of a feature, and so forth, as well as cross-feature usage, generally an evaluation as to which users who use a feature also use another feature or feature set. Characteristics of feature users also may be analyzed, such as to evaluate how long, how much, how often and how extensive feature users use an application. Other types of analysis include session analysis, generally comprising information about the number of sessions in which a set of features occur, and analysis of feature usage trends over time.

For purposes of understanding, the technology is described herein by use of examples, including those that operate in various environments, such as internal users (e.g., corresponding to employees of the enterprise that is analyzing the software) and external users. Further, the programs exemplified herein are generally a suite of application programs such as those provided as part of the Microsoft® Office software product suite. However, as will be understood, these are only non-limiting examples, and the technology is applicable to different user environments and different software products, including individual application programs and operating system components.

As such, the present invention is not limited to any particular embodiments, aspects, concepts, structures, functionalities or examples described herein. Rather, any of the embodiments, aspects, concepts, structures, functionalities or examples described herein are non-limiting, and the present invention may be used various ways that provide benefits and advantages in computing in general.

Turning to FIG. 1, there is shown a mechanism for collecting software instrumentation data 102, including a session recorder 104 that collects various data from one or more application instances 106 corresponding to various users 108₁-108_n, where n represents any practical number of users. The session recorder 104 may be per application instance/user, or may be a mechanism such as an agent on each computing device of a network that communicates with at least one data collection server component running on a network server or the like. A user interface 110 allows an test operator or the like to set collection parameters, such as from which program or programs to collect the instrumentation data, from which users to collect data, how long a collection session should last (if the program is not ended by the user within that time limit) and so forth.

In general, the instrumentation data 102 comprise data collected from each user session, where a session corresponds to actual usage by a user of an executing program. A typical session starts from the application start (e.g., by double clicking on the application executable or a document that launches the application executable, or by choosing the application from a start menu), and ends when the application is closed (e.g., by choosing “Exit” in the application or closing the application window). Sessions can also be time limited, e.g., if a session exceeds twenty-four hours, the session is ended and the instrumentation data to that point recorded (the application continues to run). Sessions can also end by non-normal termination of a program, e.g., because of program or system crashes.

FIG. 2 provides an example of one type of software instrumentation data 102, with some of the data (arranged in columns) collected for some number of sessions (arranged in rows); it is equivalent to have the sessions be in the columns and the rows represent the data. In one example implementation, each session is associated with some or all of the information shown in FIG. 2, including a session ID, a user ID, and an application name. Other information that is typically recorded includes the application version/build, a start time, an end time, the commands used during the session and still other data, such as the number of files opened and so forth. Note that in actual implementations, the instrumentation data 102 may be many thousands of dimensions.

Software features can be modeled and recognized from software instrumentation data. Based on feature modeling and recognition, further analysis such as analyzing characteristics of feature users, cross-feature usage, session analysis and so forth may be performed to gain an understanding of feature usage. From feature recognition, the sessions in which a feature occurred are obtained.

In general, feature recognition provides rich statistical information on how a feature is used, including for example, feature occurrence, feature command count, average length and so on. The information can be filtered and formatted for feature usage analysis and reporting.

To analyze software feature usage, the software instrumentation data 102 is processed, such as to measure the overall usage of a feature by a group of users. FIG. 3 shows example analysis components, including an analyzer 332 that generates an output report 334 from some set of feature data 336. Note that the data 336 may be first pre-processed into any suitable data structure or set of data structures, and/or the features recognized therein, such as described in the aforementioned U.S. patent application Ser. Nos. entitled “Multidimensional Analysis Tool for High Dimensional Data,” “Efficient Data Infrastructure for High Dimensional Analysis” and “Software Feature Modeling and Recognition.” Further, the data may be accessed via a client/service architecture, such as described in the aforementioned U.S. patent application Ser. No. entitled “Analyzing Software Usage with Instrumentation Data,” in which a data explorer system manages the data for the analysis and provides access to the data via APIs.

A user interface 336 establishes the parameters, criteria and which metrics are used to analyze the feature data 334. FIG. 3 shows an example UI and implementation of such an analysis. As can be seen, given the set of feature data 336 (e.g., with application and version/build information included in the feature selection), filters such as a source of users and whether to exclude outliers can be specified, (outliers are described below).

As generally represented in FIG. 3, the source of users can be specified. Some examples include all users from whom instrumentation data have been collected (All), users who are external customers and not employees of the company conducting the analysis (External), users who are employees (Internal), users who are from a particular group that has been set up to collect data (Study ID, for example, the beta participants of a next software release), or a custom group. Note that such custom groups are described in the aforementioned U.S. patent application Ser. No. entitled “Analyzing Software Users with Instrumentation Data and User Group Modeling and Analysis.”

With respect to outliers, a type of user is a potential outlier if his or her use of a feature is substantially different from those of most other users. Various criteria can be used to determine an outlier, such as the entropy of the occurrence distribution of each feature. The smaller the entropy, the more unevenly distributed the occurrence of the feature among the set of all users. For example, if the entropy is less than one-half (0.5), a first criterion is met. Additionally, the average occurrence per session of the feature by this user may be considered, e.g., the total occurrence of the feature divided by application session count of the user. If the average occurrence per session is greater than some number, such as one-hundred, the second criterion is met. In this example, any user who meets the two criteria can be grouped and reported; in this example, the user is an outlier that is likely using automation.

In this manner, given a set of software instrumentation data, which for analyzing program is sometimes referred to as Software (or Service) Quality Metrics (SQM) data, feature usage may be analyzed. FIG. 4 shows various example components for processing and analyzing SQM data (or similar data) with respect to feature usage and types of analysis. Note that the SQM data 102 may first be filtered and otherwise pre-processed (block 402), e.g., so that only the commands used in features are efficiently accessed, as represented by the block labeled 404. Further, some commands in a sequence of commands are not part of feature usage, and are referred to as noise; one or more noise models 406 described below may be applied to modify the command sequence data (block 408) such as to eliminate such commands.

As described in the aforementioned U.S. patent application Ser. No. entitled “Software Feature Modeling and Recognition,” a visual modeling tool 420 allows an operator of the analysis to define aspects of feature analysis. A compiler 422 compiles the output of the modeling tool 420 into a finite state machine 424. A recognition process 428 uses the finite state machine to locate feature usage. Data 430 corresponding to the recognized feature usage and commands may then be analyzed (block 432) and output as information in some way, such as in one or more reports 434. Note that the analyzer 332 and output 334 of FIG. 3 may correspond to blocks 432 and 434 of FIG. 4, respectively.

As described below, given information corresponding to a set of instrumentation data, various types of analyses may be performed. Some of these types are exemplified in FIG. 4, namely feature recognition (and instrumentation data) analysis 441, cross-feature analysis 442, feature users analysis 443, feature user characteristics analysis 444, session analysis 445, and trend analysis 446. One or more other types of feature analysis are feasible, but are not shown in FIG. 4 for purposes of simplicity.

Information from feature recognition and instrumentation data (block 441), such as the total number of users of the application (a given version/build), can be used to obtain the following information:

Percentage   Percentage of application users who use the
of feature   feature.
users
Percentage   Percentage of application sessions in which
of feature   the feature occurred.
sessions:
Feature      Total number of times the feature occurred in
occurrence   analysis data. (Analysis data is the data set
             for analysis, e.g., the set of data given the
             source of users, application and
             version/build. Feature occurrence includes
             exact matches and matches with noise, e.g.,
             with unnecessary steps such as menu browsing
             in the middle of the feature.)
Feature      Total number of clicks of necessary commands
controls     (i.e. those defined in the feature) in
click count  occurrences of the feature.
Noise click  Total number of clicks of unnecessary
count        commands (such as menu browsing) in
             occurrences of the feature
Average      Average number of feature control clicks and
feature      noise clicks per feature occurrence.
length
Feature      Ratio of the sum of feature controls click
clicks-total count and noise click count to the total
clicks ratio number of clicks for the application.
Feature      Click count of each command and enum in the
clicks       feature (the Enum element models a set of
details      commands; each Enum has a unique name, and it
             can be called by a Feature, Procedure or
             another Enum. In execution, only one of the
             child elements is executed).
Enum/command Click count of each command and enum broken
details      down by command properties.
Noise        Exact match occurrence and noise click count.
details
Feature path Top n (e.g., ten) paths of the feature,
details      including the total occurrence and commands
             that make up the path. Each path is a way the
             feature may be executed.
Feature      Distribution of feature length.
length
distribution

Cross-feature usage analysis 442 answers questions such as how many users who use a certain feature also use another feature, and for a group of features, how many users use all (or some other specified set) of the features in the group. Based on feature recognition results, cross-feature usage can be measured by users who use all (or some specified set of) the features, usage of features by users who use all (or some specified set of) the features, and percentage of <feature name 1> users who use <feature name 2>.

Users who use all (or some specified set of) the features (note: may be repeated for each application):

User count    Number of users who use the specified
              (e.g., all) features.
Users who use Number of users who use all the
all the       applications to which the features belong.
applications  For example, if two features are chosen for
              this analysis, one is a Word 2003 (SP1)
              feature and the other is a PowerPoint 2003
              (Office 2003 Important Builds) feature,
              this refers to the number of users who use
              both Word 2003 (SP1) and any of the
              important builds (RTM, SP1 and SP2) of
              PowerPoint 2003.
Percentage    Ratio of User count to Users who use all
              the applications.

Usage of features by users who use all (or some specified set of) the features (block 443; note: may be repeated for each feature):

<feature    Total occurrence of the feature by users
name> total who use the specified (e.g., all) features
occurrence

<feature name> users (repeat for each feature):

Feature user Number of users who use the feature.
count
<application Number of users who use the application (of
name>        the specified builds).
(builds)
user count
Percentage   Ratio of feature user count to the
             <application name> (builds) user count.
Occurrence   Total occurrence of the feature by feature
             users.

Percentage of <feature name 1> users who use <feature name 2> (repeat for each remaining feature, and then repeat for each feature):

Percentage of        Percentage of <feature name 1> users
<feature name 1>     who use <feature name 2>.
users who use
<feature name 2>
Usage of <feature    Total occurrence of <feature name 1>
name 1> (occurrence) by these users.
Usage of <feature    Total occurrence of <feature name 2>
name 2> (occurrence) by these users.

Feature user characteristics analysis 443 is directed towards resolving questions such as how often and how much do feature users use an application, and what types of users they are when using an application. Feature users may be users who use all of the features specified, any one of the features specified, or none of the features specified. Based on feature recognition results, characteristics of these users can be measured by:

Average   Average number of application sessions by these
session   users. This indicates on average, how much the
count     users have been using the application during a
          time period. One suitable calculation is: get
          the session count (total number of application
          sessions) of each user, and average across all
          the users in the group.
Average   Average time between consecutive sessions by
session   users. This indicates on average, how frequent
frequency the users use the application. One suitable
          calculation is: get the session elapse time
          (the time between the end of the last session
          and the end of the first session) of each user,
          get the session frequency (session elapse time
          divided by session count) of each user, average
          across some set of (e.g., all) users.
Average   Average total session time by users. This is
total     another indication of on average, how much the
running   analysis users have been using the application.
time      One suitable calculation is: get the total
          running time (sum of all session time) of each
          user, average across the users.
Average   Average session time by users. This indicates
session   on average, how much time users spend in each
length    session using the application. One suitable
          calculation is: get the average session length
          (total running time divided by session count)
          of each user, average across the users.
Average   Average percentage of total commands of the
depth of  application used by users. This indicates how
usage     deep users use the application. One suitable
          calculation is: get the depth of usage
          (percentage of total application commands used
          by the user, where total application commands
          is the total number of distinct commands found
          in the command stream of the application so
          far, and used by the user is defined as the
          command found at least once in the command
          stream of the user) of each user, average
          across the users. For example, users can be
          characterized as beginner, intermediate,
          advanced and expert users depending on their
          depth of usage.

The distribution of the above measures can also be obtained by counting how many or percentage of users whose values fall within an interval. The application and version/build for which the analysis is being conducted can also be specified.

Session analysis 445 is directed to answering questions such as how many users use a set of features in the same session, and how frequent these sessions are. Based on feature recognition results, session analysis may include:

<application Total number of sessions of the application.
name>
session
count:
Sessions in  Total number of sessions in which some
which        specified set of (e.g., all) the features
features     occurred in the session.
occurred
Percentage   Percentage of application sessions in which
of sessions  some specified set of (e.g., all) the
             features occurred, i.e. the ratio of the two
             numbers above.
<application Total number of application users.
name > user
count
Users who    Total number of users who use some specified
use the      set of (e.g., all) the features in the same
features in  session.
the same
session
Percentage   Percentage of application users who use some
of users     specified set of (e.g., all) the features in
             the same session, i.e. the ratio of the two
             numbers above.
Frequency    Frequency of sessions by users. Shows how
distribution many and the percentage of users who use some
             specified set of (e.g., all) the features in
             the same session whose frequency of such
             sessions (i.e. ratio of the number of
             sessions in which some specified set of
             (e.g., all) the features occurred in the same
             session and total session count of the user)
             falls within an interval.

Session analysis also may include basic information of each feature such as the session count and user count of each feature. Feature <feature name> (repeat for each feature):

Session     Total number of sessions in which the feature
count       occurred.
User count  Total number of users who used the feature.
Percentage  Percentage of application sessions in which
of sessions the feature occurred.
Percentage  Percentage of application users who used the
of users    feature.

Trend analysis 446 of feature usage is directed towards resolving questions such as whether the percentage of users who use a feature changed since the launch of the newest version/build of a software product. Based on feature recognition results, the trend of using a feature, e.g., usage of a feature over time, can be measured. The feature and the source of users can be specified, as can the period to analyze and reporting interval can also be specified. For example, the period to analyze can be an absolute period such as the time period from a start date to an end date, or a relative period, for example, each user's enrollment length which refers to the time period from a user's first session to the last session. A reporting interval is the interval to report the measures. This may be monthly, weekly, daily, or another interval.

The following table sets for some example data that can be used to analyze feature usage trends:

Feature User Count Total number of users using the feature
                   during a reporting interval.
Feature Session    Total number of sessions in which the
Count              feature occurred during a reporting
                   interval.
Feature Occurrence Total number of times the feature
                   occurred during a reporting interval.
Feature            Feature occurrence divided by feature
Occurrence/User    user count during a reporting interval.
Feature            Feature occurrence divided by feature
Occurrence/Session session count during a reporting
                   interval.
Application Count  Total number of users using the
                   application during a reporting
                   interval.
Percentage of      Feature user count divided by
Users              application user count during a
                   reporting interval.
Application        Total number of sessions of the
Session Count:     application during a reporting
                   interval.
Percentage of      Feature session count divided by
Sessions           application session count during a
                   reporting interval.
Cumulative Feature Total number of times the feature
Occurrence         occurred from the start time of the
                   period to analyze to the end of each
                   reporting interval.
Cumulative         Percentage of users from the start time
Percentage of      of the period to analyze to the end of
Users              each reporting interval.
Cumulative         Percentage of sessions from the start
Percentage of      time of the period to analyze to the
Sessions           end of each reporting interval.

FIG. 5 summarizes an overall example process, beginning at step 502 which represents collecting the software instrumentation data. As is readily understood, the software instrumentation data may be collected at any previous time, not necessarily just prior to analysis.

Step 504 represents obtaining the analysis criteria (e.g., feature usage, trend analysis and/or others), and obtaining the user set, which may be all, external, internal, a user group and so forth as set above. Step 506 generates a query from the operator-input analysis and/or user filtering criteria.

Step 508 represents submitting the query against the software feature data (in any appropriate format), with step 510 representing receiving the query results. Step 512 represents generating the report, which may include performing calculations on the results as needed to match the operator's requirements. For example, as described above, some of the report can include information that is not directly measured but is computed from a combination of two or more measured sets of data.

Exemplary Operating Environment

FIG. 6 illustrates an example of a suitable computing system environment 600 on which some or all of the various components (e.g., represented in FIG. 4) may be implemented. The computing system environment 600 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing environment 600 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment 600.

The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to: personal computers, server computers, hand-held or laptop devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.

The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and so forth, which perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in local and/or remote computer storage media including memory storage devices.

With reference to FIG. 6, an exemplary system for implementing various aspects of the invention may include a general purpose computing device in the form of a computer 610. Components of the computer 610 may include, but are not limited to, a processing unit 620, a system memory 630, and a system bus 621 that couples various system components including the system memory to the processing unit 620. The system bus 621 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus.

The computer 610 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by the computer 610 and includes both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by the computer 610. Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media.

The system memory 630 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 631 and random access memory (RAM) 632. A basic input/output system 633 (BIOS), containing the basic routines that help to transfer information between elements within computer 610, such as during start-up, is typically stored in ROM 631. RAM 632 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 620. By way of example, and not limitation, FIG. 6 illustrates operating system 634, application programs 635, other program modules 636 and program data 637.

The computer 610 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only, FIG. 6 illustrates a hard disk drive 641 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive 651 that reads from or writes to a removable, nonvolatile magnetic disk 652, and an optical disk drive 655 that reads from or writes to a removable, nonvolatile optical disk 656 such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive 641 is typically connected to the system bus 621 through a non-removable memory interface such as interface 640, and magnetic disk drive 651 and optical disk drive 655 are typically connected to the system bus 621 by a removable memory interface, such as interface 650.

The drives and their associated computer storage media, described above and illustrated in FIG. 6, provide storage of computer-readable instructions, data structures, program modules and other data for the computer 610. In FIG. 6, for example, hard disk drive 641 is illustrated as storing operating system 644, application programs 645, other program modules 646 and program data 647. Note that these components can either be the same as or different from operating system 634, application programs 635, other program modules 636, and program data 637. Operating system 644, application programs 645, other program modules 646, and program data 647 are given different numbers herein to illustrate that, at a minimum, they are different copies. A user may enter commands and information into the computer 610 through input devices such as a tablet, or electronic digitizer, 664, a microphone 663, a keyboard 662 and pointing device 661, commonly referred to as mouse, trackball or touch pad. Other input devices not shown in FIG. 6 may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 620 through a user input interface 660 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor 691 or other type of display device is also connected to the system bus 621 via an interface, such as a video interface 690. The monitor 691 may also be integrated with a touch-screen panel or the like. Note that the monitor and/or touch screen panel can be physically coupled to a housing in which the computing device 610 is incorporated, such as in a tablet-type personal computer. In addition, computers such as the computing device 610 may also include other peripheral output devices such as speakers 695 and printer 696, which may be connected through an output peripheral interface 694 or the like.

The computer 610 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 680. The remote computer 680 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 610, although only a memory storage device 681 has been illustrated in FIG. 6. The logical connections depicted in FIG. 6 include one or more local area networks (LAN) 671 and one or more wide area networks (WAN) 673, but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.

When used in a LAN networking environment, the computer 610 is connected to the LAN 671 through a network interface or adapter 670. When used in a WAN networking environment, the computer 610 typically includes a modem 672 or other means for establishing communications over the WAN 673, such as the Internet. The modem 672, which may be internal or external, may be connected to the system bus 621 via the user input interface 660 or other appropriate mechanism. A wireless networking component 674 such as comprising an interface and antenna may be coupled through a suitable device such as an access point or peer computer to a WAN or LAN. In a networked environment, program modules depicted relative to the computer 610, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation, FIG. 6 illustrates remote application programs 685 as residing on memory device 681. It may be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

An auxiliary subsystem 699 (e.g., for auxiliary display of content) may be connected via the user interface 660 to allow data such as program content, system status and event notifications to be provided to the user, even if the main portions of the computer system are in a low power state. The auxiliary subsystem 699 may be connected to the modem 672 and/or network interface 670 to allow communication between these systems while the main processing unit 620 is in a low power state.

Conclusion

While the invention is susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described above in detail. It should be understood, however, that there is no intention to limit the invention to the specific forms disclosed, but on the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of the invention.

Claims

1. In a computing environment, a method comprising: analyzing information corresponding to software instrumentation data collected from user sessions corresponding to one or more programs, including determining feature usage metrics; andoutputting information representative of at least one of the feature usage metrics.

2. The method of claim 1 further comprising, collecting the instrumentation data during actual user sessions.

3. The method of claim 1 wherein determining the feature usage metrics comprises determining for a set of users at least one of: percentage of feature users information corresponding to a percentage of program users who use the feature, percentage of feature sessions information corresponding to a percentage of program sessions in which the feature occurred, feature occurrence information corresponding to a number of times the feature occurred, feature controls count information corresponding to a number of uses of necessary commands, noise count information corresponding to a number of uses of unnecessary commands, feature length information corresponding to the a number of feature control clicks and noise clicks per feature occurrence, feature ratio information corresponding to ratio of the sum of feature controls count and noise count to total click count, feature details information corresponding to a count of each command in the feature, command details information corresponding to a count of each command broken down by command properties, noise details information corresponding to exact match occurrence and noise click count, feature path details information corresponding to a number of paths of the feature, including total occurrence and commands that make up the path, or feature length distribution information, or any combination of percentage of feature users information, percentage of feature sessions information, feature occurrence information, feature controls count information, noise count information, feature length information, feature ratio information, feature details information, command details information, noise details information, feature path details information, or feature length distribution information.

4. The method of claim 1 wherein determining the feature usage metrics comprises determining cross-feature usage for a set of users and a specified set of one or more features, or a specified set of one or more programs, or a specified set of one or more features and a specified set of one or more programs.

5. The method of claim 4 wherein determining the cross-feature usage comprises determining information corresponding to at least one of: user count information corresponding to a number of users who use all or a specified set of the specified features, program usage information corresponding to a users who use all the specified programs, feature usage corresponding to occurrence of the feature by users who use all or a specified set of the specified features, feature user count corresponding to a number of users who use the feature, program user count corresponding to a number of users who use the application, or occurrence information corresponding to a count of occurrence of the feature by feature users, or any combination of user count information, program usage information, feature usage, feature user count, program user count, or occurrence information.

6. The method of claim 1 wherein determining the feature usage metrics comprises determining feature user characteristics for a set of users, including determining at least one of: session count information corresponding to a number of application sessions by the users, session frequency information corresponding to a time between consecutive sessions by users, running time information corresponding to a session time by users, session length information corresponding to session time by users, depth of usage information corresponding to a percentage of total commands of the application used by users.

7. The method of claim 1 wherein determining the feature usage metrics comprises performing a session analysis for a specified set of one or more features, comprising determining at least one of: session count information corresponding to a number of program sessions by users, occurrence information corresponding to a number of sessions in which the specified feature or features occurred in the session, percentage of sessions information corresponding to a percentage of application sessions in which the specified feature or features occurred, user count information corresponding to a total number of program users, user same session information corresponding to a number of users who used the specified feature or features in the same session, percentage of users information corresponding to a percentage of program users who use the specified feature or features in the same session, frequency of sessions by users information, or distribution information corresponding to a number and percentage of users who use specified feature or features in the same session whose frequency of such sessions falls within each interval, or any combination of session count information, occurrence information, percentage of sessions information, user count information, user same session information, percentage of users information, frequency of sessions by users information, or distribution information.

8. The method of claim 1 further comprising, analyzing the information corresponding to the software instrumentation data to determine at least one feature usage trend over time.

9. The method of claim 8 wherein analyzing the information corresponding to the software instrumentation data to determine at least one feature usage trend over time comprises determining information corresponding to at least one of: feature user count information corresponding to a number of users using a feature during a reporting interval, feature session count information corresponding to a number of sessions in which a feature occurred during a reporting interval, feature occurrence information corresponding to a number of times a feature occurred during a reporting interval, feature occurrence and user information corresponding to the feature occurrence divided by the feature user count during a reporting interval, feature occurrence and session information corresponding to the feature occurrence divided by the feature session count during a reporting interval, program count information corresponding to a number of users using a program with the feature during a reporting interval, percentage of users information corresponding to the feature user count divided by the program count during a reporting interval, program session count information corresponding to a number of sessions of a program with the feature during a reporting interval, percentage of sessions information corresponding to the feature session count divided by the program session count during a reporting interval, cumulative feature occurrence information corresponding to a number of times a feature occurred from a start time of a period to analyze to an end of each reporting interval, cumulative percentage of users information corresponding to a percentage of feature users from a start time of a period to analyze to an end of each reporting interval, or cumulative percentage of sessions information corresponding to a percentage of feature sessions from a start time of a period to analyze to an end of each reporting interval, or any combination of feature user count information, feature session count information, feature occurrence information, feature occurrence and user information, feature occurrence and session information, program count information, percentage of users information, program session count information, percentage of sessions information, cumulative feature occurrence information, cumulative percentage of users information, or cumulative percentage of sessions information.

10. The method of claim 1 further comprising, analyzing the information corresponding to the software instrumentation data to determine at least potential outlier corresponding to feature usage that appears different from feature usage by other users.

11. A computer-readable medium having computer executable instructions, which when executed perform steps comprising, processing information related to software instrumentation data collected during program usage sessions to analyze feature usage by at least some users during at least some of the program usage sessions; and outputting results of the analysis.

12. The computer-readable medium of claim 11 wherein processing the information comprises performing one or more of: a feature usage analysis, a cross-feature usage analysis, an analysis of characteristics of feature users, a session analysis, or an analysis of feature usage trends.

13. The computer-readable medium of claim 11 wherein outputting the results of the analysis comprises outputting a report to a user interface.

14. The computer-readable medium of claim 11 having further computer-executable instructions comprising, receiving analysis parameters via a user interface, including receiving a selection of at least one feature or receiving a selection of a user source, or receiving a selection of at least one feature and receiving a selection of a user source.

15. In a computing environment, a system comprising, an analyzer that processes information corresponding to software instrumentation data recorded from user software program usage sessions to produce an output, the analyzer including means for performing a feature usage analysis, means for performing a cross-feature usage analysis, means for performing an analysis of characteristics of feature users, means for performing a session analysis, or means for performing an analysis of feature usage trends, or any combination of means for performing a feature usage analysis, means for performing a cross-feature usage analysis, means for performing an analysis of characteristics of feature users, means for performing a session analysis, or means for performing an analysis of feature usage trends.

16. The system of claim 15 further comprising a user interface coupled to the analyzer for facilitating selection of one or more features.

17. The system of claim 16 wherein the user interface further facilitates selection of a group of users.

18. The system of claim 15 further comprising a user interface coupled to the analyzer for outputting results corresponding to the analysis.

19. The system of claim 15 further comprising means for filtering at least some of the information corresponding to the software instrumentation data.

20. The system of claim 15 wherein the analyzer is coupled to a recognition process that recognizes features from the information corresponding to the software instrumentation data.