Event Broker for Software Development Notification Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In modern software development processes, especially in agile methodologies, the complexity and geographical distribution of teams make it difficult for stakeholders to timely and efficiently track changes in development artifacts and events, leading to challenges in collaboration and communication.
Innovation Solution
A publish/subscribe pattern-based system is implemented to facilitate event-based information flow, allowing stakeholders to subscribe to and receive notifications about creation, deletion, and updates of development artifacts through a notification system that aggregates and routes event messages across the software development environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If conventional communication methods (in-person discussions, phone calls, email) are used to notify team members about artifact modifications, then team members can be informed of changes, but the timeliness and efficiency of information flow deteriorates due to geographical distribution and manual coordination overhead
Solution Approach 1:
The patent introduces an event broker as an intermediary component that mediates between artifact modification events and stakeholder subscriptions. The event broker receives notifications about artifact changes, processes subscription requests, and automatically routes relevant information to subscribed stakeholders, eliminating the need for manual coordination and significantly improving information flow timeliness across distributed teams
Solution Approach 2:
The system enables stakeholders to independently subscribe to and unsubscribe from specific artifact modification events based on their needs. This self-service mechanism allows team members to automatically receive relevant notifications without requiring manual intervention from others, reducing coordination overhead and improving efficiency
2Productivity
If manual tracking methods are used to monitor development artifact changes, then team members can stay informed, but the time and effort required to track modifications increases significantly
Solution Approach 1:
The patent implements preliminary action by having stakeholders pre-register their subscription interests in specific artifact types and modification events before changes occur. The system maintains a subscription registry that maps stakeholders to their desired notifications, enabling automatic routing of relevant change information without requiring real-time manual tracking or monitoring efforts
Solution Approach 2:
The system establishes a feedback loop where artifact modification events automatically trigger notifications to subscribed stakeholders through the event broker. This automated feedback mechanism ensures that stakeholders receive timely information about relevant changes without manually checking or tracking modifications, significantly reducing the time spent on monitoring while maintaining high collaboration efficiency
Data Source
AI summary
A method including receiving a plurality of event descriptors, each event descriptor of the plurality of event descriptors corresponding to a respective event relevant to a software development process, transmitting the plurality of event descriptors to a subscriber; and receiving a subscription message from a subscriber, the subscription message including an indication of an event descriptor selected from the plurality of event descriptors.