Feature Change Notification Service for Software Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software applications face challenges in timely detection and notification of feature changes to affected users, especially during large-scale rollouts, due to limitations in determining which modifications require notification and how to communicate them effectively.

Innovation Solution

An enhanced notification service that maintains a database of features and users, automatically detects feature modifications, identifies affected users, and generates notifications based on user preferences, using a flighting system to flag major changes and communicate through preferred channels like email, web portal, or mobile applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If manual case-by-case determination of feature modifications and affected users is used, then notification accuracy for small-scale changes is maintained, but notification timeliness and efficiency deteriorate during large-scale rollouts

Engineering Contradiction:
Improvenotification timelinessVSAvoidsystem complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The notification system automatically detects feature modifications, identifies affected users, and generates notifications without requiring manual intervention. The system self-manages the entire notification workflow by querying the database for feature-user relationships and automatically determining which users should be notified based on the modified features.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The database pre-stores the relationships between features and affected users before modifications occur. This preliminary organization of data enables the system to quickly identify notification recipients when a feature change is detected, eliminating the need for manual case-by-case analysis during actual rollouts.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If comprehensive notifications are sent to all users for all feature changes, then information completeness is improved, but user information overload and notification relevance deteriorate

Engineering Contradiction:
Improveinformation completenessVSAvoidnotification relevance
Core Design Contradiction:
Loss of informationVSObject-affected harmful factors

Solution Approach 1:

The system sends notifications with localized relevance to each user based on their specific relationship to the modified feature. By querying the database for users associated with the particular modified feature, the system ensures each user receives only notifications relevant to their usage context, avoiding generic mass notifications.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

Instead of notifying all users about all feature changes, the system applies partial action by selectively notifying only those users who are actually affected by the specific feature modification. This targeted approach prevents information overload while maintaining completeness for relevant users.

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If automated notification systems are implemented, then notification efficiency and timeliness are improved, but system complexity and implementation difficulty increase

Engineering Contradiction:
Improvenotification efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The database serves multiple functions: it stores feature information, maintains user-feature relationships, and enables automated notification generation. This multi-functional design consolidates what could be separate complex systems into a unified structure, improving efficiency without proportionally increasing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system continuously monitors for feature modifications and automatically triggers notification processes based on detected changes. This feedback mechanism ensures timely notifications while using existing database structures to minimize implementation complexity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10652037B2Notifying affected users of feature changes in a software application
Publication Date: 2020.05.12 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10652037B2 patent drawing
  • US10652037B2 patent drawing
  • US10652037B2 patent drawing

AI summary

Systems, methods, and software are disclosed herein for operating a notification service for notifying affected users of modifications made to features in a software application. The notification service maintains a database comprising a list of the features in the software application and a list of users associated with each of the features. The notification service detects at least a modification to a feature in the software application that requires affected users to be notified. In response to detecting the modification to the feature, the notification service queries the database based at least on an identify of the feature associated with the modification to identify the affected users. Notifications are then generated and communicated to the affected users indicative of at least the modification to the feature in the software application.