Automated What's New Container Generation via Digital Footprints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
End users are not adequately informed about new features in software application updates, as existing applications often lack a 'What's New' feature due to the additional overhead and manual effort required to implement it.
Innovation Solution
An automated system that generates a 'What's New' container by analyzing digital footprints from the software development lifecycle, using natural language processing and machine learning to create an AI avatar and guided tours, which can be deployed to client devices without additional development effort.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If manual content generation is used to create 'What's New' features, then user information quality is improved, but development time and overhead increase
Solution Approach 1:
The system enables self-service by having the development process itself generate the 'What's New' content automatically. The digital footprint data from development activities is processed to auto-generate user-friendly feature descriptions, eliminating the need for separate manual content creation while maintaining information quality.
Solution Approach 2:
The patent replaces the mechanical manual content generation process with an automated system that uses digital footprint data processing. The system automatically extracts and transforms development activity data into user-friendly 'What's New' feature descriptions, substituting human effort with automated information processing.
2Loss of time
If automated system is implemented to generate 'What's New' content, then development time is reduced, but system complexity increases
Solution Approach 1:
The system achieves universality by making the development process itself serve dual purposes: both building the software functionality and generating the 'What's New' content. The same digital footprint data collected during development is reused for content generation, eliminating the need for separate specialized systems.
Solution Approach 2:
The patent introduces an intermediary processing layer that transforms digital footprint data into user-friendly content. This intermediary system sits between the development activities and the final 'What's New' presentation, automatically bridging the gap without requiring direct manual intervention.
3Loss of information
If manual feature documentation is required, then content accuracy is improved, but productivity decreases
Solution Approach 1:
The system implements feedback by continuously using the digital footprint data from development activities to automatically update and refine the 'What's New' content. The feedback loop ensures that the content remains accurate and up-to-date with the actual development work without requiring separate manual documentation processes.
Solution Approach 2:
The patent applies preliminary action by collecting and processing digital footprint data during the development process itself, before the 'What's New' content is needed for user communication. This advance preparation ensures that accurate information is ready when required, eliminating the need for post-development manual documentation.
Data Source
AI summary
Mechanisms are provided for automatically generating a user interactable what-is-new feature for an updated application. The mechanisms obtain footprint data from electronic documents generating during a software development lifecycle to generate an update to an application, where the footprint data specifies development requirements and actions performed by at least application developers during the software development lifecycle. The mechanisms further obtain test case generation data from a recording of test case generation interactions with a graphical user interface and execute computer natural language processing on the footprint data and analysis of the recording of the test case generation interactions to automatically generate a what-is-new container for the update to the application. Moreover, the mechanisms deploy the what-is-new container to a client computing device that executes a container daemon to implement a what-is-new feature for the updated application installed on the client computing device.