Browse Prior Art Database

Methods and Technique to find frequently used features and usecases by analysing production logs for applications and cloud based solutions

IP.com Disclosure Number: IPCOM000249573D
Publication Date: 2017-Mar-03
Document File: 4 page(s) / 39K

Publishing Venue

The IP.com Prior Art Database

Abstract

A comprehensive report of the frequently used features or a use cases for a product that are used by the customers are difficult. Also, there are very few tools that are used, have the flexibility to collect the use case success and failure rates automatically. This provides details about the automated methodology that can be used by a product development team to find out the features and use cases that are frequently used by the customers and to analyze the success and failure rates of each usecase.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 44% of the total text.

1

Methods and Technique to find frequently used features and usecases by analysing production logs for applications and cloud based solutions

Description

A software product is designed with features to help users perform their task with ease. Not necessary that all the features that are added in the product are effectively used by the users of the product. Some users use specific set of features while some other use a different set of features. Over a period of time the number of features and enhancements are added to the software product.

Mostly to figure out which features are frequently used and which are least used the product team gather these information either by interacting with end users/customers and getting their feedback on the features used by them, especially for applications/products installed on premise.

Currently there is no mechanism available to automatically find out the most and least used features of a product and also the failure rate of features/use cases.

This document describes about an automated mechanism for identifying the usage of a feature by an end user in a software product by analyzing the logs. A log analyzer tool is added in the production system and logs are analyzed on a periodic basis. The proposed method analyses the logs and provide the details and frequency of the feature usage, usecase failure rate, and so on. The analysis done in this method helps the product team to find out the features that are most and least used by users, thereby enhance the product and propose or provide more features around the most commonly used features. You can use this analysis to educate the users about the other features available in the product which are not used by them. Thereby, the product usability, accessibility of the product, and overall user experience can be enhanced. This is also useful in scenarios where the feature in the product is released as 'Tech Preview' ,and the team can find out whether the user is using these features or not.

The method mentioned above also analyze and find out the failure rate for every use case and feature of the software application in a production environment.

The proposed solution is a software based methodology, to analyze the software usage and thereby create a usage metrics of each usecase and feature. This methodology can eliminate the need of customer interaction to understand the most used features by customers. This solution also analyses the failure rate for every use case and feature of the software application in a production environment. The failure rate and each failure scenario with input data are collected and this helps in adding extra test cases to cover the failure or escaped test scenarios for the feature in future development.

Implementation

2

A separate log and format is created so that the log analyzer could analyze the logs and generate the details. The log data are added every time the use case is executed.

A sample format is below

Time Stamp : FeatureNam...