Component management platform

• US 10,503,495 B2
• Filed: 09/25/2017
• Issued: 12/10/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.
• Primary Examiner(s): Patel, Hiren P
• Application Number:
  US15/714,282
• Publication Number:
  US 20190042231A1
• Time in Patent Office: 806 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, by a server-based workbench that supports a plurality of client-based workspaces that each provide a software development environment, a component library that stores at least one version of each of a plurality of software components that have been created by respective developers using the client-based workspaces;

publishing, by the server-based workbench, a first version of a particular software component from the component library to the plurality of workspaces that each provide the software development environment, the first version of the particular software component later being modified by a particular developer associated with a particular workspace into a second version of the particular software component that is incorporated into at least one application that is created using the particular workspace;

after the first version of the particular software component is modified by the particular developer into the second version of the particular software component using the particular workspace, receiving, by the server-based workbench and from the particular workspace, the second version of the software component that was modified by the particular developer; and

performing at least one test to verify that the second version of the particular software component that was modified by the particular developer is backward compatible with the first version of the particular software component and, based on verifying that the second version is backward compatible with the first version of the particular software component;

storing, by the server-based workbench, the second version of the particular software component in the component library; and

determining that a different developer of another existing application that incorporates the first version of the particular software component has opted in to automatic updates of software components that are incorporated into the another existing application, then (i) sending a notification of an availability of the second version of the particular software comment to other software developers that have not opted in to automatic updates of software components, and (ii) publishing, by the server-based workbench, the second version of the particular software component from the component library to a respective workspace that provides the software development environment for automatically updating the another existing application that incorporates the first version of the particular software component to incorporate the second version of the particular software component, without first sending a notification of an of the availability of the second version of the particular software component to the different developer.

2. The system of claim 1, wherein publishing 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 publishing 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 publishing a first version 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.

5. The system of claim 1, wherein, the notification sent to the other software developers describes the at least one modification made to the first version to generate the second version.

6. 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.

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

reducing a width of the tree structure based at least partly on a relative weight of the at least two available versions.

8. The system of claim 6, 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.

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

accessing, by a server-based workbench that supports a plurality of client-based workspaces that each provide a software development environment, a component library that stores at least one version of each of a plurality of software components that have been created by respective developers using the client-based workspaces;

publishing, by the server-based workbench, a first version of a particular software component from the component library to the plurality of workspaces that each provide the software development environment, the first version of the particular software component later being modified by a particular developer associated with a particular workspace into a second version of the particular software component that is incorporated into at least one application that is created using the particular workspace;

after the first version of the particular software component is modified by the particular developer into the second version of the particular software component using the particular workspace, receiving, by the server-based workbench and from the particular workspace, the second version of the software component that was modified by the particular developer; and

performing at least one test to verify that the second version of the particular software component that was modified by the particular developer is backward compatible with the first version of the particular software component and, based on verifying that the second version is backward compatible with the first version of the particular software component;

storing, by the server-based workbench, the second version of the particular software component in the component library; and

determining that a different developer of another existing application that incorporates the first version of the particular software component has opted in to automatic updates of software components that are incorporated into the another existing application, then (i) sending a notification of an availability of the second version of the particular software comment to other software developers that have not opted in to automatic updates of software components, and (ii) publishing, by the server-based workbench, the second version of the particular software component from the component library to a respective workspace that provides the software development environment for automatically updating the another existing application that incorporates the first version of the particular software component to incorporate the second version of the particular software component, without first sending a notification of the availability of the second version of the particular software component to the different developer.

10. The method of claim 9, wherein publishing 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.

11. The method of claim 9, wherein publishing 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.

12. The method of claim 9, wherein publishing a first version 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.

13. The method of claim 9, wherein, the notification sent to the other software developers describes the at least one modification made to the first version to generate the second version.

14. The method of claim 9, 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.

15. The method of claim 14, further comprising:

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

16. The method of claim 14, 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.

17. One or more non-transitory, 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, by a server-based workbench that supports a plurality of client-based workspaces that each provide a software development environment, a component library that stores at least one version of each of a plurality of software components that have been created by respective developers using the client-based workspaces;

publishing, by the server-based workbench, a first version of a particular software component from the component library to the plurality of workspaces that each provide the software development environment, the first version of the particular software component later being modified by a particular developer associated with a particular workspace into a second version of the particular software component that is incorporated into at least one application that is created using the particular workspace;

after the first version of the particular software component is modified by the particular developer into the second version of the particular software component using the particular workspace, receiving, by the server-based workbench and from the particular workspace, the second version of the software component that was modified by the particular developer; and

performing at least one test to verify that the second version of the particular software component that was modified by the particular developer is backward compatible with the first version of the particular software component and, based on verifying that the second version is backward compatible with the first version of the particular software component;

storing, by the server-based workbench, the second version of the particular software component in the component library; and

determining that a different developer of another existing application that incorporates the first version of the particular software component has opted in to automatic updates of software components that are incorporated into the another existing application, then (i) sending a notification of an availability of the second version of the particular software comment to other software developers that have not opted in to automatic updates of software components, and (ii) publishing, by the server-based workbench, the second version of the particular software component from the component library to a respective workspace that provides the software development environment for automatically updating the another existing application that incorporates the first version of the particular software component to incorporate the second version of the particular software component, without first sending a notification of the availability of the second version of the particular software component to the different developer.

18. The one or more computer-readable storage media of claim 17, wherein publishing 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.