DATA MANAGEMENT SYSTEM

• US 20160085544A1
• Filed: 09/19/2014
• Published: 03/24/2016
• Est. Priority Date: 09/19/2014
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sharma, Pankaj, Berger, Alexander, Koya, Veerendra K., Weisberg, Tomer, Zimmermann, Mario, Mohapatra, Arabinda, Barad, Mangesh Ganpatrao, Denz, David M., McBride, Brent Thomas, Goyal, Hema Tulsidas, Subbaraj, AnandBalaji, Paramasivan, Harinarayan, Persegani, Ricardo, Kudryavtsev, Maxim
• Application Number:
  US14/491,753
• Publication Number:
  US 20160085544A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Systems and techniques are disclosed for improving the management of data contracts during a software development lifecycle. A system can include a data contract metadata store, components for interacting with the metadata store to support development tool integration, and interchange features for verified build processes. A service can be provided that receives a developer package from a development client application, parses the developer package to generate data contract metadata, modifies a data contract metadata store in accordance with at least one command received with the developer package, and communicates notification data, when included with the data contract metadata, to a notification service.

Claims

1. A method for managing data contracts for publishers and subscribers developed via software development applications, the method comprising:

parsing a developer package to generate contract metadata associated with a data contract;

modifying a data contract metadata store in accordance with at least one command received with the developer package; and

providing notification data, when included with the data contract metadata, to a notification service.

2. The method of claim 1, wherein the at least one command comprises a command to create a new version of the data contract.

3. The method of claim 2, wherein the new version is indicated as a draft version.

4. The method of claim 1, wherein the at least one command comprises a command to publish the data contract.

5. The method of claim 1, wherein the at least one command comprises a command to initiate a review process for the data contract.

6. The method of claim 1, wherein the at least one command comprises a command to modify a list of stakeholders to be notified about changes to the data contract metadata.

7. The method of claim 1, wherein the at least one command comprises a command to retrieve an identified version of a data contract.

8. The method of claim 7, wherein modifying the data contract metadata store in accordance with the at least one command received with the developer package comprises denoting the identified version of the data contract as having a particular subscriber.

9. The method of claim 1, wherein the notification service is a software development lifecycle service.

10. A method for improving the build reliability of a subscriber codebase, the method comprising:

receiving a request from a subscriber to validate an identified version of a data contract;

querying a data contract metadata store for the identified version of the data contract;

verifying an integrity of the identified version of the data contract against a codebase for the subscriber; and

providing verification information indicating the integrity of the identified version of the data contract.

11. The method of claim 10, wherein the verifying the integrity of the data contract comprises a build stage of a build system.

12. The method of claim 11, wherein the build stage is a compilation stage.

13. The method of claim 11, wherein the build stage is an automated test stage.

14. A system for managing data contracts, the system comprising:

one or more storage media;

at least one data contract metadata store contained on at least one of the one or more computer readable storage media, the at least one data contract metadata store having data contract metadata comprising;

one or more properties related to a data contract version;

one or more properties related to a subscriber; and

one or more properties related to one or more stakeholders for notification; and

program instructions stored on at least one of the one or more computer readable media that, when executed by a processing system, direct the processing system to;

parse a developer package to generate contract metadata associated with a data contract;

modify the data contract metadata store in accordance with at least one command received with the developer package; and

provide notification data, when included with the data contract metadata, to a notification service.

15. The system of claim 14, wherein the data contract metadata further comprises an access control list for controlling a subscriber access permission.

16. The system of claim 14, wherein the data contract metadata store communicates with a data contract discovery service.

17. The system of claim 14, wherein the at least one command comprises one or more of:

a command to create a new version of the data contract;

a command to publish the data contract;

a command to initiate a review process for the data contract;

a command to modify a list of stakeholders to be notified about changes to the data contract metadata;

a command to retrieve an identified version of a data contract.

18. The system of claim 17, wherein, in response to receiving the command to create the new version of the data contract, the program instructions direct the processing system to modify at least one of the one or more properties related to the data contract version.

19. The system of claim 17, wherein, in response to receiving the command to retrieve the identified version of the data contract, the program instructions direct the processing system to modify at least one of the one or more properties related to the subscriber to denote a particular subscriber.

20. The system of claim 17, wherein, in response to receiving the command to modify the list of stakeholders to be notified about changes to the data contract metadata, the program instructions direct the processing system to modify at least one of the one or more properties related to the one or more stakeholders for notification,

wherein the notification data comprises at least one of the one or more properties related to one or more stakeholders for notification.