Software development using re-usable software components

• US 9,870,207 B2
• Filed: 12/22/2015
• Issued: 01/16/2018
• Est. Priority Date: 12/22/2015
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Mathias, Elton, Montagnon, Gilles, Arsac, Wihem, Hebert, Cedric, Sendor, Jakub
• Primary Examiner(s): Rampuria, Satish
• Application Number:
  US14/978,725
• Publication Number:
  US 20170177310A1
• Time in Patent Office: 756 Days
• Field of Search: 717110-113, 717168-178
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A component selector may select a first software component stored in a software component library in conjunction with a first annotation, the first annotation being linked to a second annotation of a second software component via a link. An evaluation engine may evaluate a property expressed by the first annotation relative to a requirement expressed by the second annotation, and thereby verify compliance of the first software component and the second software component for inclusion within a software application being developed. A component update monitor may re-verify the compliance, based on an update to at least one of the first software component and the second software component.

Claims

1. A computer program product, the computer program product being tangibly embodied on a non-transitory computer-readable storage medium and comprising instructions that, when executed, are configured to cause at least one computing device to:

access a previously created software component library in which each software component is associated with a respective annotation describing properties, requirements and dependencies of the software component as determined from a respective knowledge base, wherein a first software component having a first annotation is linked to a second software component having a second annotation based on a semantic relationship between a property of the first software component and a property of the second software component;

import the first software component into a current software application under development and verify a first compliance of the first software component with the current software application architecture;

verify a second compliance of the first software component with the second software component in the previously created software component library;

include the second software component within the current software application under development, based on the second compliance; and

generate a graphical user interface displaying a software architecture diagram for the current software application under development, wherein the first software component and the second software component are represented in the software architecture diagram and selectable therefrom for inclusion from the previously created software component library and for verification of the first and second compliances.

2. The computer program product of claim 1, wherein the second annotation characterizes a second property of the second software component.

3. The computer program product of claim 1, wherein the second annotation characterizes a requirement of the second software component, and further wherein the compliance includes a verification that the first property satisfies the requirement.

4. The computer program product of claim 1, wherein the instructions, when executed, are configured to cause the at least one computing device to:

select the second software component, the second annotation, and the requirement; and

search for a matching property within a software component of a software architecture of the current software application under development that fulfills the requirement.

5. The computer program product of claim 1, wherein the instructions, when executed, are configured to cause the at least one computing device to:

generate the graphical user interface with the first software component and the second software component represented in the software architecture diagram and selectable therefrom for providing the first annotation and the second annotation, respectively.

6. The computer program product of claim 1, wherein the instructions, when executed, are configured to cause the at least one computing device to:

determine an application requirement of the current software application under development; and

search a software architecture of the current software application under development and the previously created software component library for a software property matching the application requirement.

7. The computer program product of claim 1, wherein the instructions, when executed, are configured to cause the at least one computing device to:

include the first software component including adding the first software component within a software architecture of the current software application under development;

determine an update to the first software component at the previously created software component library; and

provide a notification of the update in the context of the software architecture.

8. The computer program product of claim 1, wherein the instructions, when executed, are configured to cause the at least one computing device to:

compare the first software component within the software architecture of the current software application under development with the updated first software component at the previously created software component library; and

identify a potential change to the first software component within the software architecture, based on the comparison.

9. The computer program product of claim 1, wherein the first annotation describes one or more of a type of programming language or library used by the first software component, requirements whether the first software component requires data to be validated at a particular time or in a particular manner, requirements on a configuring a firewall or an encryption algorithm utilized for the first software component, whether multi tenancy is supported by the first software component, and types of data that are stored, or techniques for associated data storage for the first software component.

10. A computer-implemented method for executing instructions stored on a non-transitory computer readable storage medium, the method comprising:

accessing a previously created software component library in which each software component is associated with a respective annotation describing properties, requirements and dependencies of the software component as determined from a respective knowledge base, wherein a first software component having a first annotation is linked to a second software component having a second annotation based on a semantic relationship between a property of the first software component and a property of the second software component;

importing the first software component into a current software application under development and verify compliance of the first software component with the current software application architecture;

verifying compliance of the first software component with the second software component in the previously created software component library;

including the second software component within the current software application under development, based on the compliance; and

generate a graphical user interface displaying a software architecture diagram for the current software application under development, wherein the first software component and the second software component are represented in the software architecture diagram and selectable therefrom for inclusion from the previously created software component library and for verification of the first and second compliances.

11. The method of claim 10, wherein the second annotation characterizes a requirement of the second software component, and further wherein verifying the compliance includes verifying that the property of the first software component satisfies the requirement.

12. The method of claim 10, wherein importing the first software component includes:

adding the first software component within a software architecture of the current software application under development;

determining an update to the first software component at the previously created software component library; and

providing a notification of the update in the context of the software architecture.

13. The method of claim 10, further comprising:

comparing the first software component within the software architecture with the updated first software component at the previously created software component library; and

identifying a potential change to the first software component within the software architecture, based on the comparison.

14. The method of claim 10, wherein the first annotation describes one or more of a type of programming language or library used by the first software component, requirements whether the first software component requires data to be validated at a particular time or in a particular manner, requirements on configuring a firewall or an encryption algorithm utilized for the first software component, whether multi tenancy is supported by the first software component, and types of data that are stored, or techniques for associated data storage for the first software component.

15. A system including instructions recorded on a non-transitory computer-readable storage medium, and executable by at least one processor, the system comprising:

a component selector configured to access a previously created software component library in which each software component is associated with a respective annotation describing properties, requirements and dependencies of the software component as determined from a respective knowledge base, wherein a first software component having a first annotation is linked to a second software component having a second annotation based on a semantic relationship between a property of the first software component and a property of the second software component, the component selector further configured to import the first software component into a current software application under development and verify compliance of the first software component with the current software application architecture;

an evaluation engine configured to verify compliance of the first software component with the second software component in the previously created software component library and include the second software component within the current software application under development, based on the compliance;

a component update monitor configured to re-verify the compliance, after an update to at least one of the first software component and the second software component in the previously created software component library; and

a component configured to generate a graphical user interface displaying a software architecture diagram for the current software application under development, wherein the first software component and the second software component are represented in the software architecture diagram and selectable therefrom for inclusion from the previously created software component library and for verification of the first and second compliances.

16. The system of claim 15, wherein the component selector is configured to modify the first annotation, based on a selection of the first software component from within a software architecture diagram of the software application under development.

17. The system of claim 15, wherein the evaluation engine is further configured to:

determine a second requirement of the second software component;

search software components of the software application under development and the previously created software component library for a matching property the fulfills the second requirement; and

determine whether the second requirement can be fulfilled by one or more properties of the software components of the software application under development and the previously created software component library, based on the search.

18. The system of claim 15, wherein the component update monitor is further configured to:

detect the update as an update to the first software component within the previously created software component library;

compare the updated first software component within the previously created software component library to the first software component imported within the software application under development; and

determine whether a corresponding update to the first software component as imported within the software application under development is required, based on the comparison.

19. The system of claim 15, wherein the first annotation describes one or more of a type of programming language or library used by the first software component, requirements whether the first software component requires data to be validated at a particular time or in a particular manner, requirements on configuring a firewall or an encryption algorithm utilized for the first software component, whether multi tenancy is supported by the first software component, and types of data that are stored, or techniques for associated data storage for the first software component.