COMPONENT MANAGEMENT PLATFORM

• US 20190042231A1
• Filed: 09/25/2017
• Published: 02/07/2019
• Est. Priority Date: 08/02/2017
• Status: Active Grant

• Current Assignee: Accenture Global Solutions Limited (Accenture PLC)
• Original Assignee: Accenture Global Solutions Limited (Accenture PLC)
• Inventors: Kolhe, Ashish, Dalal, Dhanashree, Maniar, Parikshit, Rajgopalan, Shridhar D.
• Granted Patent: US 10,503,495 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/3692 for test results analysis
• CPC Class Codes: G06F 16/2246 Trees, e.g. B+trees
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 8/77 Software metrics

Abstract

A component management platform includes a component library that stores software components to be incorporated into applications, such as components that have been optimized for efficient performance, reliability, and/or other aspects. The platform also provides a workspace that is accessed to create an application that includes component(s) stored in the component library. In some instances, a developer modifies component when incorporating the component into their application. The platform enables the developer to upload the modified version of the component, which is stored in the component library and published, through the platform, to enable others to incorporate the modified version of the component into their application projects. In some implementations, the modified version is tested for backward compatibility with previous versions of the component, and to verify that the modified version does not include any bugs.

Claims

1. A system comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor, the memory storing instructions which, when executed by the at least one processor, cause the at least one processor to perform operations comprising;

accessing a component library that stores at least one version of each of a plurality of software components;

publishing a first version of a software component from the component library to a plurality of workspaces that provide a software development environment, the first version being included in at least one application that is created using at least one of the plurality of workspaces;

receiving a second version of the software component that includes at least one modification to the first version; and

performing at least one test to verify that the second version is compatible with the first version and, based on verifying that the second version is compatible with the first version;

storing the second version in the component library;

publishing the second version from the component library to the plurality of workspaces; and

updating the at least one application to include the second version.

2. The system of claim 1, wherein updating the at least one application to include the second version includes:

automatically updating the at least one application to include the second version, based at least partly on determining that the at least one application is registered to receive updates to the software component.

3. The system of claim 1, wherein updating the at least one application to include the second version includes:

automatically updating the at least one application to include the second version, based at least partly on determining that at least a threshold number of applications have been updated to include the second version.

4. The system of claim 1, wherein updating the at least one application to include the second version includes:

sending a notification indicating that the second version of the software component is available in the component library; and

updating the at least one application to include the second version, based at least partly on receiving an update request.

5. The system of claim 1, wherein publishing a first version of a software component from the component library to the plurality of workspaces includes providing, for presentation in the plurality of workspaces, an adoption statistic that indicates a number of applications that have been previously created in the plurality of workspaces to include the first version of the software component.

6. The system of claim 1, wherein updating the at least one application includes sending a notification to at least one user associated with the at least one application, the notification describing the at least one modification made to the first version to generate the second version.

7. The system of claim 1, the operations further comprising:

creating a tree structure that stores information describing available versions of the software component, including the first version and the second version, wherein the tree structure includes a plurality of nodes that each corresponds to a respective version of the software component.

8. The system of claim 7, the operations further comprising:

reducing a width of the tree structure by merging at least two of the available versions of the software component, the merging based at least partly on a relative weight of the at least two available versions.

9. The system of claim 7, the operations further comprising:

reducing a width of the tree structure by indicating that at least one of the available versions of the software component is deprecated, based at least partly on a relative weight of the at least one available version compared to other available versions of the software component.

10. A computer-implemented method performed by at least one processor, the method comprising:

accessing, by the at least one processor, a component library that stores at least one version of each of a plurality of software components;

publishing, by the at least one processor, a first version of a software component from the component library to a plurality of workspaces that provide a software development environment, the first version being included in at least one application that is created using at least one of the plurality of workspaces;

receiving, by the at least one processor, a second version of the software component that includes at least one modification to the first version; and

performing, by the at least one processor, at least one test to verify that the second version is compatible with the first version and, based on verifying that the second version is compatible with the first version;

storing, by the at least one processor, the second version in the component library;

publishing, by the at least one processor, the second version from the component library to the plurality of workspaces; and

updating, by the at least one processor, the at least one application to include the second version.

11. The method of claim 10, wherein updating the at least one application to include the second version includes:

automatically updating the at least one application to include the second version, based at least partly on determining that the at least one application is registered to receive updates to the software component.

12. The method of claim 10, wherein updating the at least one application to include the second version includes:

automatically updating the at least one application to include the second version, based at least partly on determining that at least a threshold number of applications have been updated to include the second version.

13. The method of claim 10, wherein updating the at least one application to include the second version includes:

sending a notification indicating that the second version of the software component is available in the component library; and

updating the at least one application to include the second version, based at least partly on receiving an update request.

14. The method of claim 10, wherein publishing a first version of a software component from the component library to the plurality of workspaces includes providing, for presentation in the plurality of workspaces, an adoption statistic that indicates a number of applications that have been previously created in the plurality of workspaces to include the first version of the software component.

15. The method of claim 10, wherein updating the at least one application includes sending a notification to at least one user associated with the at least one application, the notification describing the at least one modification made to the first version to generate the second version.

16. The method of claim 10, further comprising:

creating, by the at least one processor, a tree structure that stores information describing available versions of the software component, including the first version and the second version, wherein the tree structure includes a plurality of nodes that each corresponds to a respective version of the software component.

17. The method of claim 16, further comprising:

reducing, by the at least one processor, a width of the tree structure by merging at least two of the available versions of the software component, the merging based at least partly on a relative weight of the at least two available versions.

18. The method of claim 16, further comprising:

reducing, by the at least one processor, a width of the tree structure by indicating that at least one of the available versions of the software component is deprecated, based at least partly on a relative weight of the at least one available version compared to other available versions of the software component.

19. One or more computer-readable storage media storing instructions which, when executed by at least one processor, cause the at least one processor to perform operations comprising:

accessing a component library that stores at least one version of each of a plurality of software components;

publishing a first version of a software component from the component library to a plurality of workspaces that provide a software development environment, the first version being included in at least one application that is created using at least one of the plurality of workspaces;

receiving a second version of the software component that includes at least one modification to the first version; and

performing at least one test to verify that the second version is compatible with the first version and, based on verifying that the second version is compatible with the first version;

storing the second version in the component library;

publishing the second version from the component library to the plurality of workspaces; and

updating the at least one application to include the second version.

20. The one or more computer-readable storage media of claim 19, wherein updating the at least one application to include the second version includes:

automatically updating the at least one application to include the second version, based at least partly on determining that at least a threshold number of applications have been updated to include the second version.