VISUAL TOOL FOR REVERSE ENGINEERING SOFTWARE COMPONENTS

• US 20160132327A1
• Filed: 11/06/2014
• Published: 05/12/2016
• Est. Priority Date: 11/06/2014
• Status: Abandoned Application

• Current Assignee: General Motors LLC (General Motors Company)
• Original Assignee: General Motors LLC (General Motors Company)
• Inventors: Aggarwal, Aditya, Tehrani, Saeid, Dessert, Michael L.
• Application Number:
  US14/534,877
• Publication Number:
  US 20160132327A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/74 Reverse engineering; Extracting design information from source code

Abstract

A system and method of displaying a software application using a software architecture tool that includes: receiving a portion of an existing software application at the software architecture tool; identifying one or more software components of the existing software application from the received portion; automatically identifying a tier and layer location for each standard software component; and presenting one or more images that each represent the standard software component to a user, wherein the images visually identify a tier and layer location of each standard software component.

Claims

1. A method of displaying a software application using a software architecture tool, comprising the steps of:

(a) receiving a portion of an existing software application at the software architecture tool;

(b) identifying one or more software components of the existing software application from the received portion based on content accessed from an information technology (IT) standard catalog identifying software components that are recognized as being acceptable for use in vehicles;

(c) automatically identifying a tier and layer location for each standard software component of the existing software application; and

(d) presenting one or more images that each represent the standard software component to a user, wherein the images visually identify a tier and layer location of each standard software component.

2. The method of claim 1, further comprising the step of presenting one or more images that each represent an identified non-standard software component to a user, wherein the images visually identify a tier and layer location of each software component.

3. The method of claim 1, further comprising the step of presenting one or more images depicting a software component that belongs to more than one layer.

4. The method of claim 1, further comprising the step of receiving at the software architecture tool an IT bill of materials (IT BOM) that identifies one or more software components in the existing software application.

5. The method of claim 1, further comprising the step of receiving at the software architecture tool a deployment descriptor of the existing software application.

6. The method of claim 1, further comprising the step of identifying the tier and layer location of each software component by color.

7. The method of claim 1, further comprising the step of identifying the one or more software components as non-standard or standard according to color.

8. The method of claim 1, further comprising the step of generating a new skeletal software application that includes one or more identified software components and one or more user-selected software components.

9. The method of claim 8, further comprising the step of generating an information technology (IT) bill of materials (IT BOM) for the new skeletal software application.

10. The method of claim 8, further comprising the step of generating an incompatibility report for the new skeletal software application.

11. The method of claim 1, further comprising the step of displaying compatibility features between one or more software components of the existing software application and one or more user-selected software components according to color.

12. The method of claim 1, further comprising the step of receiving a software tier selection from the user for each identified software component of the existing software application.

13. The method of claim 1, further comprising the step of determining a software layer selection automatically for each identified software component of the existing software application.

14. The method of claim 1, further comprising the step of building a vehicular software application from the one or more software components of the existing software application.

15. The method of claim 14, further comprising the step of installing the vehicular software application on a vehicle.

16. A method of displaying a software application using a software architecture tool, comprising the steps of:

(a) receiving a portion of an existing software application at a software architecture tool;

(b) accessing an information technology (IT) standard catalog identifying software components as being acceptable for use in vehicles;

(c) identifying one or more software components of the existing software application from the received portion;

(d) determining whether software components are standard or non-standard and acceptable for use in vehicles;

(e) automatically identifying a tier and layer location for each standard software component;

(f) receiving one or more software selections from a user for non-standard components or when a software component belongs to a plurality of layers; and

(g) presenting one or more images to a user that each represent an identified software component, wherein the presented images identify a location within a tier and a layer.

17. The method of claim 16, further comprising the step of receiving at the software architecture tool a deployment descriptor of the existing software application.

18. The method of claim 16, further comprising the step of identifying the tier and layer of each software component or software selection by color.

19. The method of claim 16, further comprising the step of identifying the one or more software components or software selections as non-standard or standard according to color.

20. The method of claim 16, further comprising the step of building a vehicular software application from the one or more software components of the existing software application and one or more software components corresponding to the software selections.