Selection and assessment of software components

• US 9,170,810 B2
• Filed: 10/11/2011
• Issued: 10/27/2015
• Est. Priority Date: 10/11/2011
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Koutyrine, Oleg, Hoursanov, Andrey
• Primary Examiner(s): Mitchell, Jason
• Assistant Examiner(s): Dang, Christine
• Application Number:
  US13/271,005
• Publication Number:
  US 20130091488A1
• Time in Patent Office: 1,477 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3608 using formal methods, e.g. model checking, abstract interpretation theorem proving G06N5/013
• CPC Class Codes: G06F 8/77 Software metrics

Abstract

The present disclosure involves systems, software, and computer implemented methods for providing selection and assessment of software components. One process includes operations for identifying a software component for assessment. Dependencies associated with the software component are analyzed, wherein analyzing dependencies includes identifying at least one relevant perspective associated with the software component, identifying a scope associated with the at least one relevant perspective, and determining whether the software component is associated with at least one related infrastructure component based on the scope or at least one other software component that the software component depends on based on the scope. The software component and each of the at least one related infrastructure component or the at least one other software component are assessed against a set of criteria.

Claims

1. A computer implemented method performed by one or more processors for assessing software components, the method comprising the following operations:

identifying a software component for assessment based upon an assessment context;

analyzing dependencies associated with the software component, wherein analyzing dependencies includes;

identifying at least one relevant perspective associated with the software component, the at least one relevant perspective representing a view of software components and the relevance of the software component based upon the assessment context, wherein the assessment context includes information used to determine appropriate other software components for assessment in addition to the software component and is a particular software component use case for the software component used for identifying the at least one relevant perspective by deducing boundary conditions from obtaining relevant boundary condition aspects, wherein the boundary conditions are software requirements imposed on the particular software component;

identifying a scope associated with the at least one relevant perspective, wherein the scope can be expanded using the perspective view and boundary conditions to include multiple layers of dependencies associated with the software component; and

determining, using a transitive closure process, whether the software component is associated with at least one related infrastructure component based on the scope or at least one other software component that the software component depends on based on the scope; and

assessing the software component and each of the at least one related infrastructure component or the at least one other software component against a set of criteria.

2. The method of claim 1, wherein the set of criteria includes at least one of licensing, supportability, delivery, platform availability, or architecture assessment.

3. The method of claim 1, wherein the at least one relevant perspective includes at least one of a platform perspective, a design time perspective, or a runtime perspective.

4. The method of claim 1, wherein identifying the scope includes defining relevant criteria to include in the set of criteria for assessing the software component.

5. The method of claim 1, wherein determining whether the software component is associated with at least one other software component that the software component depends on includes identifying software components related to the software component based on transitive properties.

6. The method of claim 1, further comprising:

iteratively analyzing dependencies for each of the at least one related infrastructure component or the at least one other software component to identify additional software components or infrastructure components for assessment; and

assessing the additional software components or infrastructure components against the set of criteria.

7. The method of claim 1, further comprising extending the scope to include potential components upon which the at least one related infrastructure component or the at least one other software component depend.

8. A computer program product encoded on a non-transitory, tangible storage medium, the product comprising computer readable instructions for causing one or more processors to perform operations comprising:

identifying a software component for assessment based upon an assessment context;

analyzing dependencies associated with the software component, wherein analyzing dependencies includes;

identifying at least one relevant perspective associated with the software component, the at least one relevant perspective representing a view of software components and the relevance of the software component based upon the assessment context, wherein the assessment context includes information used to determine appropriate other software components for assessment in addition to the software component and is a particular software component use case for the software component used for identifying the at least one relevant perspective by deducing boundary conditions from obtaining relevant boundary condition aspects, wherein the boundary conditions are software requirements imposed on the particular software component;

identifying a scope associated with the at least one relevant perspective, wherein the scope can be expanded using the perspective view and boundary conditions to include multiple layers of dependencies associated with the software component; and

determining, using a transitive closure process, whether the software component is associated with at least one related infrastructure component based on the scope or at least one other software component that the software component depends on based on the scope; and

assessing the software component and each of the at least one related infrastructure component or the at least one other software component against a set of criteria.

9. The computer program product of claim 8, wherein the set of criteria includes at least one of licensing, supportability, delivery, platform availability, or architecture assessment.

10. The computer program product of claim 8, wherein the at least one relevant perspective includes at least one of a platform perspective, a design time perspective, or a runtime perspective.

11. The computer program product of claim 8, wherein identifying the scope includes defining relevant criteria to include in the set of criteria for assessing the software component.

12. The computer program product of claim 8, wherein determining whether the software component is associated with at least one other software component that the software component depends on includes identifying software components related to the software component based on transitive properties.

13. The computer program product of claim 8, wherein the operations further comprise:

iteratively analyzing dependencies for each of the at least one related infrastructure component or the at least one other software component to identify additional software components or infrastructure components for assessment; and

assessing the additional software components or infrastructure components against the set of criteria.

14. The computer program product of claim 9, wherein the operations further comprise extending the scope to include potential components upon which the at least one related infrastructure component or the at least one other software component depend.

15. A system, comprising:

memory operable to store at least one software component; and

one or more processors operable to;

identify a software component for assessment based upon an assessment context;

analyze dependencies associated with the software component, wherein analyzing dependencies includes;

identifying at least one relevant perspective associated with the software component, the at least one relevant perspective representing a view of software components and the relevance of the software component based upon the assessment context, wherein the assessment context includes information used to determine appropriate other software components for assessment in addition to the software component and is a particular software component use case for the software component used for identifying the at least one relevant perspective by deducing boundary conditions from obtaining relevant boundary condition aspects, wherein the boundary conditions are software requirements imposed on the particular software component;

identifying a scope associated with the at least one relevant perspective, wherein the scope can be expanded using the perspective view and boundary conditions to include multiple layers of dependencies associated with the software component; and

determining, using a transitive closure process, whether the software component is associated with at least one related infrastructure component based on the scope or at least one other software component that the software component depends on based on the scope; and

assess the software component and each of the at least one related infrastructure component or the at least one other software component against a set of criteria.

16. The system of claim 15, wherein the at least one relevant perspective includes at least one of a platform perspective, a design time perspective, or a runtime perspective.

17. The system of claim 15, wherein identifying the scope includes defining relevant criteria to include in the set of criteria for assessing the software component.

18. The system of claim 15, wherein determining whether the software component is associated with at least one other software component that the software component depends on includes identifying software components related to the software component based on transitive properties.

19. The system of claim 15, wherein the one or more processors are further operable to:

iteratively analyze dependencies for each of the at least one related infrastructure component or the at least one other software component to identify additional software components or infrastructure components for assessment; and

assess the additional software components or infrastructure components against the set of criteria.

20. The system of claim 15, wherein the one or more processors are further operable to extend the scope to include potential components upon which the at least one related infrastructure component or the at least one other software component depend.