Weighted Model Change Notification System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed development environments for object models, team members with different areas of expertise often introduce errors due to lack of coordination and knowledge of each other's work, making it difficult to maintain model integrity and prevent conflicts between model elements.
Innovation Solution
A method and system for managing model development that determines model relationships, identifies interested users based on past interactions, and generates weighted notifications to ensure that relevant team members are informed of changes, thereby reducing errors and maintaining model integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple team members work on different parts of object models independently, then productivity increases, but model integrity deteriorates due to undetected errors and conflicts
Solution Approach 1:
The system implements automated feedback mechanisms by monitoring model element changes and notifying relevant team members. When a model element is modified, the system automatically identifies related elements and sends notifications to users who have previously interacted with those elements, enabling them to review and maintain model integrity without halting development workflow
Solution Approach 2:
The notification system acts as an intermediary between model elements and team members. It tracks relationships between model elements and users, and mediates communication by routing notifications from changed elements to interested parties, ensuring coordination without requiring direct team member monitoring
2Reliability
If all team members are notified of all model changes, then model integrity is maintained through comprehensive review, but information loss increases due to notification overload
Solution Approach 1:
The notification system applies local quality by customizing notifications based on individual user interests and the specific relationships between model elements. Instead of uniform notifications to all users, the system identifies and notifies only those users with relevant past interactions with the changed or related elements, making each notification targeted and meaningful
3Reliability
If comprehensive tracking of model relationships is implemented, then coordination between team members improves, but device complexity increases due to tracking infrastructure
Solution Approach 1:
The system implements self-service by automatically tracking and maintaining relationships between model elements and users without requiring manual configuration. The notification system autonomously monitors model changes, traverses relationships, identifies interested users, and generates notifications, reducing the complexity burden on the development team
Data Source
AI summary
Techniques are disclosed for managing development of a model set comprised of one or more object models by a plurality of model developers. Each model developer may be considered an interested party. For example, when a model developer changes an area of the model, that person becomes the most interested party in other changes made to the same area. An automated mechanism is provided to track changes made to the model set and informs interested parties as changes are made or after changes are made to the model based on a weighting system. In one embodiment, the weighting system may be based on a distance from the changed portions and on the amount of time since a party last made a change to the same area.