System and method for event-based information flow in software development processes

• US 8,146,100 B2
• Filed: 03/21/2006
• Issued: 03/27/2012
• Est. Priority Date: 03/21/2006
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kilian-Kehr, Roger
• Primary Examiner(s): Dam, Tuan
• Assistant Examiner(s): Wei, Zheng
• Application Number:
  US11/386,335
• Publication Number:
  US 20070226755A1
• Time in Patent Office: 2,198 Days
• Field of Search: None
• US Class Current: 719/318
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

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.

Claims

1. A method comprising:

receiving a first plurality of event descriptors from a first event producer, each event descriptor of the first plurality of event descriptors corresponding to a respective event relevant to a software development process, the respective event occurring at the first event producer;

receiving a second plurality of event descriptors from a second event producer, each event descriptor of the second plurality of event descriptors occurring at the second event producer;

transmitting the first plurality of event descriptors and the second plurality of event descriptors to a subscriber;

receiving a subscription message from a subscriber, the subscription message including an indication of a first event descriptor selected from the first plurality of event descriptors and a second event descriptor selected from the second plurality of event descriptors; and

transmitting a first producer subscription message to the first event producer, the first producer subscription message including an indication of the first event descriptor, and transmitting a second producer subscription message to the second event producer, the second producer subscription message including an indication of the second event descriptor, the first producer subscription message including an expiration timestamp indicating an expiration of a subscription initiated based on the first producer subscription message.

2. The method of claim 1, wherein the subscription message further includes an identification of an event consumer.

3. The method of claim 2 further comprising transmitting a notification module subscription message to a notification module, the notification module subscription message including (a) an identification of the event consumer and (b) an identification of the first event descriptor and the second event descriptor included in the subscription message.

4. The method of claim 1 wherein the first plurality of event descriptors includes another event descriptor corresponding to a modification of a file system.

5. The method of claim 1 wherein the first plurality of event descriptors includes another event descriptor corresponding to a modification of a database table.

6. The method of claim 1 wherein the first plurality of event descriptors includes another event descriptor corresponding to a modification of a collection of database tables.

7. The method of claim 1 wherein the first plurality of event descriptors includes another event descriptor corresponding to a modification of the content of a source code control system repository.

8. The method of claim 1 wherein the first plurality of event descriptors includes another event descriptor corresponding to a modification of a software development environment with respect to an artifact controlled by the software development environment.

9. The method of claim 1 wherein the first plurality of event descriptors includes another event descriptor corresponding to a transmission of a file between computers.

10. The method of claim 1 wherein the first plurality of event descriptors includes another event descriptor corresponding to an occurrence of an event within a software build process.

11. The method of claim 1 wherein the first plurality of event descriptors includes another event descriptor corresponding to an occurrence of an event within a software model transformation process.

12. The method of claim 1 wherein the first plurality of event descriptors includes another event descriptor corresponding to a modification of a file system with respect to a file, the file being useable by a software requirements tracking system for storing requirements information.

13. The method of claim 1 wherein the first plurality of event descriptors includes another event descriptor corresponding to a modification of a file system with respect to a file, the file being useable by a software project management system for storing software project information.

14. A method comprising:

receiving at an event producer, from a subscription module, a producer subscription message, the producer subscription message including an indication of an event descriptor selected from 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, the producer subscription message including an expiration timestamp indicating an expiration of a subscription initiated based on the producer subscription message.

15. A machine comprising:

a network interface; and

a processor programmed to;

receive a first plurality of event descriptors from a first event producer via the network interface, each event descriptor of the first plurality of event descriptors corresponding to a respective event relevant to a software development process, the respective event occurring at the first event producer;

receive a second plurality of event descriptors from a second event producer via the network interface, each event descriptor of the second plurality of event descriptors occurring at the second event producer;

transmit the first plurality of event descriptors and the second plurality of event descriptors to a subscriber via the network interface;

receive a subscription message from a subscriber via the network interface, the subscription message including an indication of a first event descriptor selected from the first plurality of event descriptors and a second event descriptor selected from the second plurality of event descriptors; and

transmit a first producer subscription message to the first event producer via the network interface, the first producer subscription message including an indication of the first event descriptor, and transmit a second producer subscription message via the network interface to the second event producer, the second producer subscription message including an indication of the second event descriptor, the first producer subscription message including an expiration timestamp indicating an expiration of a subscription initiated based on the first producer subscription message.

16. The machine of claim 15 wherein the subscription message further includes an indication of an event consumer.

17. The machine of claim 16 wherein the processor is further programmed to transmit a notification module subscription message to a notification module via the network interface, the notification module subscription message including (a) an indication of the event consumer and (b) an indication of the first event descriptor and the second event descriptor included in the subscription message.

18. A machine comprising:

a network interface; and

a processor programmed to receive via the network interface at an event producer, from a subscription module, a producer subscription message, the producer subscription message including an indication of an event descriptor selected from 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, the producer subscription message including an expiration timestamp indicating an expiration of a subscription initiated based on the producer subscription message.

19. A system comprising:

a processor-implemented subscription module to;

receive a first plurality of event descriptors from a first event producer, each event descriptor of the first plurality of event descriptors corresponding to a respective event relevant to a software development process, the respective event occurring at the first event producer;

receive a second plurality of event descriptors from a second event producer, each event descriptor of the second plurality of event descriptors occurring at the second event producer;

transmit the first plurality of event descriptors and the second plurality of event descriptors to a subscriber;

receive a subscription message from a subscriber, the subscription message including an indication of a first event descriptor selected from the first plurality of event descriptors and a second event descriptor selected from the second plurality of event descriptors; and

transmit a first producer subscription message to the first event producer, the first producer subscription message including an indication of the first event descriptor, and transmit a second producer subscription message to the second event producer, the second producer subscription message including an indication of the second event descriptor, the first producer subscription message including an expiration timestamp indicating an expiration of a subscription initiated based on the first producer subscription message.

20. The system of claim 19 wherein the subscription message further includes an identification of an event consumer.

21. The system of claim 19 wherein the subscription message further includes an indication of an event consumer and the subscription module is further to transmit a notification module subscription message to a notification module, the notification module subscription message including (a) an identification of the event consumer and (b) an indication of the first event descriptor and the second event descriptor included in the subscription message.

22. A system comprising:

means for receiving a first plurality of event descriptors from a first event producer, each event descriptor of the first plurality of event descriptors corresponding to a respective event relevant to a software development process, the respective event occurring at the first event producer;

means for receiving a second plurality of event descriptors from a second event producer, each event descriptor of the second plurality of event descriptors occurring at the second event producer;

means for transmitting the first plurality of event descriptors and the second plurality of event descriptors to a subscriber;

means for receiving a subscription message from a subscriber, the subscription message including an indication of a first event descriptor selected from the first plurality of event descriptors and a second event descriptor selected from the second plurality of event descriptors; and

means for transmitting a first producer subscription message to the first event producer, the first producer subscription message including an indication of the first event descriptor, and means for transmitting a second producer subscription message to the second event producer, the second producer subscription message including an indication of the second event descriptor, the first producer subscription message including an expiration timestamp indicating an expiration of a subscription initiated based on the first producer subscription message.

23. The system of claim 22 wherein the subscription message further includes an identification of an event consumer.

24. The system of claim 22 wherein the subscription message further includes an indication of an event consumer and the subscription module has means for transmitting a notification module subscription message to a notification module, the notification module subscription message including (a) an identification of the event consumer and (b) an indication of the first event descriptor and the second event descriptor included in the subscription message.

25. A non-transitory computer-readable storage medium embodying instructions, which when executed by machine, cause the machine to perform operations comprising:

receiving a first plurality of event descriptors from a first event producer, each event descriptor of the first plurality of event descriptors corresponding to a respective event relevant to a software development process, the respective event occurring at the first event producer;

receiving a second plurality of event descriptors from a second event producer, each event descriptor of the second plurality of event descriptors occurring at the second event producer;

transmitting the first plurality of event descriptors and the second plurality of event descriptors to a subscriber;

receiving a subscription message from a subscriber, the subscription message including an indication of a first event descriptor selected from the first plurality of event descriptors and a second event descriptor selected from the second plurality of event descriptors; and

transmitting a first producer subscription message to the first event producer, the first producer subscription message including an indication of the first event descriptor, and

transmitting a second producer subscription message to the second event producer, the second producer subscription message including an indication of the second event descriptor, the first producer subscription message including an expiration timestamp indicating an expiration of a subscription initiated based on the first producer subscription message.

26. The non-transitory computer-readable storage medium of claim 25 wherein the subscription message further includes an identification of an event consumer.

27. The non-transitory computer-readable storage medium of claim 26, further embodying instructions, which when executed by machine, cause the machine to perform operations comprising:

transmitting a notification module subscription message to a notification module, the notification module subscription message including (a) an identification of the event consumer and (b) an identification of the first event descriptor and the second event descriptor included in the subscription message.

28. A non-transitory computer-readable storage medium embodying instructions, which when executed by machine, cause the machine to perform operations comprising:

receiving at an event producer, from a subscription module, a producer subscription message, the producer subscription message including an indication of an event descriptor selected from 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, the producer subscription message including an expiration timestamp indicating an expiration of a subscription initiated based on the producer subscription message.