Approach for proactive notification of contract changes in a software service

• US 7,934,221 B2
• Filed: 02/27/2007
• Issued: 04/26/2011
• Est. Priority Date: 02/27/2007
• Status: Expired due to Fees

• Current Assignee: Serena Software, Inc. (Open Text Corporation)
• Original Assignee: Serena Software, Inc. (Open Text Corporation)
• Inventors: Parker, Kevin Christopher, Shaw, Kelly Ann
• Primary Examiner(s): Sough; Hyung S
• Assistant Examiner(s): WATHEN, BRIAN W
• Application Number:
  US11/713,955
• Publication Number:
  US 20080209555A1
• Time in Patent Office: 1,519 Days
• Field of Search: 719/318
• US Class Current: 719/318
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

An approach is provided for proactive notification of contract changes in a software service. According to the approach, when the executable code of a composite application operable to access the service is generated, an initial copy of a contract that describes the service is retrieved. A baseline representation of the contract is generated based on the initial copy of the contract. When the composite application is being executed, a determination is made based on the baseline representation whether the contract has experienced any changes. In response to determining that the contract has experienced a change, a notification is sent indicating that the contract has experienced the change.

Claims

1. A computer-implemented method comprising:

generating executable code of a composite application that is operable to access a service that is external to the composite application, wherein generating the executable code of the composite application comprises retrieving an initial copy of a contract that describes the service;

based on the initial copy of the contract, generating a baseline representation of the contract;

wherein the baseline representation of the contract includes a first token that is generated based on the initial copy of the contract, wherein the initial copy of the contract specifies an input interface and an output interface of the service at the time the composite application is generated;

storing the baseline representation of the contract;

executing the composite application;

during execution of the composite application, determining, based on the baseline representation of the contract, whether the contract has experienced any changes, wherein determining whether the contract has experienced any changes comprises;

retrieving a current copy of the contract;

generating a current representation of the contract based on the current copy of the contract;

wherein the current representation of the contract includes a second token that is generated based on the current copy of the contract, wherein the current copy of the contract specifies the input interface and the output interface of the service at the time the composite application is being executed; and

comparing the current representation of the contract to the baseline representation of the contract to determine whether the contract has experienced any changes;

wherein comparing the current representation to the baseline representation comprises comparing the second token to the first token; and

in response to determining that the contract has experienced a change, sending a notification which indicates that the contract has experienced the change;

wherein the method is performed by one or more computer systems.

2. The computer-implemented method as recited in claim 1, wherein the contract includes a Web Services Description Language (WSDL) definition that describes the service.

3. The computer-implemented method as recited in claim 1, wherein the service and the composite application conform to a Service-Oriented Architecture (SOA) standard.

4. The computer-implemented method as recited in claim 1, wherein retrieving the initial copy of the contract comprises a build process making a call to the service, wherein the build process generates the executable code of the composite application.

5. The computer-implemented method as recited in claim 1, wherein determining whether the contract has experienced any changes is performed by a process that is separate from the composite application.

6. The computer-implemented method as recited in claim 1, further comprising:

periodically performing the steps of determining whether the contract has experienced any changes and sending the notification.

7. The computer-implemented method as recited in claim 1, wherein sending the notification comprises at least one of:

sending an e-mail to a user, wherein the e-mail indicates that the contract has experienced the change;

sending a message to a particular service port, wherein the message indicates that the contract has experienced the change;

storing a record in a log, wherein the record indicates that the contract has experienced the change; and

automatically opening a ticket in a defect tracking system, wherein the ticket indicates that the contract has experienced the change.

8. The computer-implemented method as recited in claim 1, further comprising:

in response to determining that the contract has experienced the change, analyzing the change to determine whether the change affects the composite application;

wherein, when analyzing the change determines that the change affects the composite application, sending the notification further comprises including first data in the notification, wherein the first data indicates how the change affects the composite application.

9. The computer-implemented method as recited in claim 8, wherein:

analyzing the change comprises analyzing the differences between the current copy of the contract and the initial copy of the contract, wherein analyzing the differences includes determining whether a current set of elements included in the current copy is the same as an initial set of elements included in the initial copy.

10. The computer-implemented method as recited in claim 1, wherein:

the composite application is operable to access a plurality of services that are external to the composite application, wherein a plurality of contracts describe the plurality of services; and

the method is performed for each service of the plurality of services.

11. A computer-implemented method comprising:

generating executable code of a composite application that is operable to access a service that is external to the composite application, wherein generating the executable code of the composite application comprises retrieving an initial copy of a contract that describes the service;

based on the initial copy of the contract, generating a baseline representation of the contract;

wherein the baseline representation of the contract includes the initial copy of the contract, wherein the initial copy of the contract specifies an input interface and an output interface of the service at the time the composite application is generated;

storing the baseline representation of the contract;

executing the composite application;

during execution of the composite application, determining, based on the baseline representation of the contract, whether the contract has experienced any changes, wherein determining whether the contract has experienced any changes comprises;

retrieving a current copy of the contract;

generating a current representation of the contract based on the current copy of the contract;

wherein the current representation of the contract includes the current copy of the contract, wherein the current copy of the contract specifies the input interface and the output interface of the service at the time the composite application is being executed; and

comparing the current representation of the contract to the baseline representation of the contract to determine whether the contract has experienced any changes;

wherein comparing the current representation to the baseline representation comprises comparing the current copy of the contract to the initial copy of the contract;

in response to determining that the contract has experienced a change, sending a notification which indicates that the contract has experienced the change;

wherein the method is performed by one or more computer systems.

12. A computer-implemented method comprising:

generating executable code of a composite application that is operable to access a service that is external to the composite application, wherein generating the executable code of the composite application comprises retrieving an initial copy of a contract that describes the service;

based on the initial copy of the contract, generating a baseline representation of the contract;

wherein the baseline representation of the contract includes first version information that is stored in the initial copy of the contract, wherein the first version information specifies a first executable version of the service at the time the composite application is generated;

storing the baseline representation of the contract;

executing the composite application;

during execution of the composite application, determining based on the baseline representation of the contract, whether the contract has experienced any changes, wherein determining whether the contract has experienced any changes comprises;

retrieving a current copy of the contract;

generating a current representation of the contract based on the current copy of the contract;

wherein the current representation of the contract includes second version information that is stored in the current copy of the contract, wherein the second version information specifies a second executable version of the service at the time the composite application is being executed; and

comparing the current representation of the contract to the baseline representation of the contract to determine whether the contract has experienced any changes;

wherein comparing the current representation to the baseline representation comprises comparing the second version information to the first version information;

in response to determining that the contract has experienced a change, sending a notification which indicates that the contract has experienced the change;

wherein the method is performed by one or more computer systems.

13. A computer-implemented method comprising:

generating executable code of a composite application that is operable to access a service that is external to the composite application, wherein generating the executable code of the composite application comprises retrieving an initial copy of a contract that describes the service;

based on the initial copy of the contract, generating a baseline representation of the contract;

wherein the baseline representation of the contract includes;

the initial copy of the contract, wherein the initial copy of the contract specifies an input interface and an output interface of the service at the time the composite application is generated; and

first version information that specifies a first executable version of the service at the time the composite application is generated;

storing the baseline representation of the contract;

executing the composite application;

during execution of the composite application, determining, based on the baseline representation of the contract, whether the contract has experienced any changes, wherein determining whether the contract has experienced any changes comprises;

retrieving a current copy of the contract;

generating a current representation of the contract based on the current copy of the contract;

wherein the current representation of the contract includes;

the current copy of the contract, wherein the current copy of the contract specifies the input interface and the output interface of the service at the time the composite application is being executed; and

second version information that specifies a second executable version of the service at the time the composite application is being executed; and

comparing the current representation of the contract to the baseline representation of the contract to determine whether the contract has experienced any changes;

wherein comparing the current representation to the baseline representation comprises;

comparing the second version information to the first version information; and

when the second version information is the same as the first version information, comparing the current copy of the contract to the initial copy of the contract to determine whether the contract has experienced any changes;

in response to determining that the contract has experienced a change, sending a notification which indicates that the contract has experienced the change;

wherein the method is performed by one or more computer systems.

14. A computer-implemented method comprising:

generating executable code of a composite application that is operable to access a service that is external to the composite application, wherein generating the executable code of the composite application comprises retrieving an initial copy of a contract that describes the service;

based on the initial copy of the contract, generating a baseline representation of the contract;

storing the baseline representation of the contract;

executing the composite application;

during execution of the composite application, determining, based on the baseline representation of the contract, whether the contract has experienced any changes, wherein determining whether the contract has experienced any changes comprises;

retrieving a current copy of the contract;

determining whether the baseline representation of the contract stores first version information, wherein the first version information specifies a first executable version of the service at the time the composite application is generated;

determining whether the current copy of the contract stores second version information, wherein the second version information specifies a second executable version of the service at the time the composite application is being executed;

when the baseline representation of the contract stores the first version information and the current copy of the contract stores the second version information, comparing the second version information to the first version information to determine whether the contract has experienced any changes; and

when the baseline representation of the contract does not store the first version information or when the current copy of the contract does not store the second version information, performing the steps of;

generating a current representation of the contract based on the current copy of the contract; and

comparing the current representation of the contract to the baseline representation of the contract to determine whether the contract has experienced any changes;

in response to determining that the contract has experienced a change, sending a notification which indicates that the contract has experienced the change;

wherein the method is performed by one or more computer systems.

15. A non-transitory machine-readable volatile or non-volatile medium storing a composite application, wherein the composite application when executed is operable to access a service that is external to the composite application and to access a baseline representation of a contract that describes the service, wherein the baseline representation is generated from an initial copy of the contract that is retrieved at the time the executable code of the composite application is generated, wherein the baseline representation of the contract includes a first token that is generated based on the initial copy of the contract, wherein the initial copy of the contract specifies an input interface and an output interface of the service at the time the composite application is generated, the machine-readable medium storing instructions which, when performed by one or more processors, cause performance of steps comprising:

during execution of the composite application, determining, based on the baseline representation of the contract, whether the contract has experienced any changes, wherein determining whether the contract has experienced any changes comprises;

retrieving a current copy of the contract;

generating a current representation of the contract based on the current copy of the contract;

wherein the current representation of the contract includes a second token that is generated based on the current copy of the contract, wherein the current copy of the contract specifies the input interface and the output interface of the service at the time the composite application is being executed; and

comparing the current representation of the contract to the baseline representation of the contract to determine whether the contract has experienced any changes;

wherein comparing the current representation to the baseline representation further comprises comparing the second token to the first token; and

in response to determining that the contract has experienced a change, sending a notification which indicates that the contract has experienced the change.

16. The non-transitory machine-readable volatile or non-volatile medium as recited in claim 15, wherein the contract includes a Web Services Description Language (WSDL) definition that that describes the service.

17. The non-transitory machine-readable volatile or non-volatile medium as recited in claim 15, wherein the service and the composite application conform to a Service-Oriented Architecture (SOA) standard.

18. The non-transitory machine-readable volatile or non-volatile medium as recited in claim 15, wherein a build process has retrieved the initial copy of the contract by making a call to the service, wherein the build process has generated the executable code of the composite application.

19. The non-transitory machine-readable volatile or non-volatile medium as recited in claim 15, wherein the instructions that cause determining whether the contract has experienced any changes are included in a software component that is separate from the composite application.

20. The non-transitory machine-readable volatile or non-volatile medium as recited in claim 15, further comprising instructions which, when performed by the one or more processors, cause:

periodically determining whether the contract has experienced any changes and sending the notification.

21. The non-transitory machine-readable volatile or non-volatile medium as recited in claim 15, wherein the instructions that cause sending the notification further comprise instructions which, when performed by the one or more processors, cause at least one of:

sending an e-mail to a user, wherein the e-mail indicates that the contract has experienced the change;

sending a message to a particular service port, wherein the message indicates that the contract has experienced the change;

storing a record in a log, wherein the record indicates that the contract has experienced the change; and

automatically opening a ticket in a defect tracking system, wherein the ticket indicates that the contract has experienced the change.

22. The non-transitory machine-readable volatile or non-volatile medium as recited in claim 15, further comprising instructions which, when performed by the one or more processors, cause:

in response to determining that the contract has experienced the change, analyzing the change to determine whether the change affects the composite application;

wherein the instructions that cause sending the notification further comprise instructions which, when performed by the one or more processors, cause including first data in the notification when analyzing the change determines that the change affects the composite application, wherein the first data indicates how the change affects the composite application.

23. The non-transitory machine-readable volatile or non-volatile medium as recited in claim 22, wherein:

the instructions that cause analyzing the change further comprise instructions which, when performed by the one or more processors, cause analyzing the differences between the current copy of the contract and the initial copy of the contract, wherein analyzing the differences includes determining whether a current set of elements included in the current copy is the same as an initial set of elements included in the initial copy.

24. The non-transitory machine-readable volatile or non-volatile medium as recited in claim 15, wherein the composite application is operable to access a plurality of services that are external to the composite application, wherein a plurality of contracts describe the plurality of services, and wherein the plurality of services includes the service and the plurality of contracts includes the contract.

25. A non-transitory machine-readable volatile or non-volatile medium storing a composite application, wherein the composite application when executed is operable to access a service that is external to the composite application and to access a baseline representation of a contract that describes the service, wherein the baseline representation is generated from an initial copy of the contract that is retrieved at the time the executable code of the composite application is generated, wherein the baseline representation of the contract includes the initial copy of the contract, wherein the initial copy of the contract specifies an input interface and an output interface of the service at the time the composite application is generated, the machine-readable medium storing instructions which, when performed by one or more processors, cause performance of steps comprising:

during execution of the composite application, determining, based on the baseline representation of the contract, whether the contract has experienced any changes, wherein determining whether the contract has experienced any changes comprises;

retrieving a current copy of the contract;

generating a current representation of the contract based on the current copy of the contract;

wherein the current representation of the contract includes the current copy of the contract, wherein the current copy of the contract specifies the input interface and the output interface of the service at the time the composite application is being executed; and

comparing the current representation of the contract to the baseline representation of the contract to determine whether the contract has experienced any changes;

wherein comparing the current representation to the baseline representation further comprises comparing the current copy of the contract to the initial copy of the contract;

in response to determining that the contract has experienced a change, sending a notification which indicates that the contract has experienced the change.

26. A non-transitory machine-readable volatile or non-volatile medium storing a composite application, wherein the composite application when executed is operable to access a service that is external to the composite application and to access a baseline representation of a contract that describes the service, wherein the baseline representation is generated from an initial copy of the contract that is retrieved at the time the executable code of the composite application is generated, wherein the baseline representation of the contract includes first version information that is stored in the initial copy of the contract, wherein the first version information specifies a first executable version of the service at the time the composite application is generated, the machine-readable medium storing instructions which, when performed by one or more processors, cause performance of steps comprising:

during execution of the composite application, determining, based on the baseline representation of the contract, whether the contract has experienced any changes, wherein determining whether the contract has experienced any changes comprises;

retrieving a current copy of the contract;

generating a current representation of the contract based on the current copy of the contract;

wherein the current representation of the contract includes second version information that is stored in the current copy of the contract, wherein the second version information specifies a second executable version of the service at the time the composite application is being executed; and

comparing the current representation of the contract to the baseline representation of the contract to determine whether the contract has experienced any changes;

wherein comparing the current representation to the baseline representation further comprises comparing the second version information to the first version information;

in response to determining that the contract has experienced a change, sending a notification which indicates that the contract has experienced the change.

27. A non-transitory machine-readable volatile or non-volatile medium storing a composite application, wherein the composite application when executed is operable to access a service that is external to the composite application and to access a baseline representation of a contract that describes the service, wherein the baseline representation is generated from an initial copy of the contract that is retrieved at the time the executable code of the composite application is generated, wherein the baseline representation of the contract includes the initial copy of the contract, wherein the initial copy of the contract specifies an input interface and an output interface of the service at the time the composite application is generated, and first version information that specifies a first executable version of the service at the time the composite application is generated, the machine-readable medium storing instructions which, when performed by one or more processors, cause performance of steps comprising:

during execution of the composite application, determining, based on the baseline representation of the contract, whether the contract has experienced any changes, wherein determining whether the contract has experienced any changes comprises;

retrieving a current copy of the contract;

generating a current representation of the contract based on the current copy of the contract;

wherein the current representation of the contract includes;

the current copy of the contract, wherein the current copy of the contract specifies the input interface and the output interface of the service at the time the composite application is being executed; and

second version information that specifies a second executable version of the service at the time the composite application is being executed; and

comparing the current representation of the contract to the baseline representation of the contract to determine whether the contract has experienced any changes;

wherein comparing the current representation to the baseline representation further comprises;

comparing the second version information to the first version information; and

when the second version information is the same as the first version information, comparing the current copy of the contract to the initial copy of the contract to determine whether the contract has experienced any changes;

in response to determining that the contract has experienced a change, sending a notification which indicates that the contract has experienced the change.

28. A non-transitory machine-readable volatile or non-volatile medium storing a composite application, wherein the composite application when executed is operable to access a service that is external to the composite application and to access a baseline representation of a contract that describes the service, wherein the baseline representation is generated from an initial copy of the contract that is retrieved at the time the executable code of the composite application is generated, the machine-readable medium storing instructions which, when performed by one or more processors, cause performance of steps comprising:

during execution of the composite application, determining, based on the baseline representation of the contract, whether the contract has experienced any changes, wherein determining whether the contract has experienced any changes comprises;

retrieving a current copy of the contract;

determining whether the baseline representation of the contract stores first version information, wherein the first version information specifies a first executable version of the service at the time the composite application is generated;

determining whether the current copy of the contract stores second version information, wherein the second version information specifies a second executable version of the service at the time the composite application is being executed;

when the baseline representation of the contract stores the first version information and the current copy of the contract stores the second version information, comparing the second version information to the first version information to determine whether the contract has experienced any changes; and

when the baseline representation of the contract does not store the first version information or when the current copy of the contract does not store the second version information, performing the steps of;

generating a current representation of the contract based on the current copy of the contract; and

comparing the current representation of the contract to the baseline representation of the contract to determine whether the contract has experienced any changes;

in response to determining that the contract has experienced a change, sending a notification which indicates that the contract has experienced the change.