VISUAL TOOL AND ARCHITECTING LOGICAL LAYERS OF SOFTWARE COMPONENTS

• US 20160098256A1
• Filed: 10/03/2014
• Published: 04/07/2016
• Est. Priority Date: 10/03/2014
• Status: Abandoned Application

• Current Assignee: General Motors LLC (General Motors Company)
• Original Assignee: General Motors LLC (General Motors Company)
• Inventors: Tehrani, Saeid, Aggarwal, Aditya, Dessert, Michael L.
• Application Number:
  US14/505,608
• Publication Number:
  US 20160098256A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• 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 system and method of generating a software application using a software architecture tool includes: receiving a plurality of software component selections from a user via a computer; accessing one or more repositories stored on a computer-readable medium that define a plurality of software specifications; comparing the selected software components to the software specifications in the repositories; identifying compatibility features between the selected software components and the software specifications in the repositories; displaying the compatibility features of the selected components via a peripheral of the computer; and building a skeletal software application that includes the selected software components and one or more software components added based on compatibility features using one of the repositories stored on a computer-readable medium.

Claims

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

(a) receiving a plurality of software component selections from a user via a computer;

(b) accessing one or more repositories stored on a computer-readable medium that define a plurality of software specifications;

(c) comparing the selected software components to the software specifications in the repositories;

(d) identifying compatibility features between the selected software components and the software specifications in the repositories;

(e) displaying the compatibility features of the selected components via a peripheral of the computer; and

(f) building a skeletal software application that includes the selected software components and one or more software components added based on compatibility features using one of the repositories stored on a computer-readable medium.

2. The method of claim 1, further comprising the step of generating an IT bill of materials (IT BOM) that identifies each component in a software application.

3. The method of claim 2, wherein the IT BOM includes non-selected software components that depend on selected software components.

4. The method of claim 1, further comprising the step of generating an incompatibility report.

5. The method of claim 1, further comprising the step of displaying compatibility features according to color.

6. The method of claim 1, wherein the compatibility features include a standard software component and a non-standard software component.

7. The method of claim 1, further comprising the step of verifying the plurality of software component selections for conflicts.

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

9. The method of claim 1, further comprising the step of determining a software layer selection automatically for each software component selection or by user input that is constrained by an enterprise component template repository.

10. The method of claim 1, further comprising the step of building a vehicular software application.

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

12. A method of generating a software application using a software architecture tool, comprising the steps of:

(a) receiving a tier selection and a software component selection from a user;

(b) determining whether the software component selection is standard or non-standard based on data accessed from an IT standard catalog;

(c) identifying dependencies between the software component selection and other software components in an enterprise component specification knowledge base; and

(d) building a skeletal software application based on the identified dependencies, wherein the skeletal software application includes data from an enterprise component binary repository.

13. The method of claim 12, further comprising the step of generating an IT bill of materials (IT BOM) that identifies each component in a software application.

14. The method of claim 13, wherein the IT BOM includes non-selected software components that depend on selected software components.

15. The method of claim 12, further comprising the step of generating an incompatibility report.

16. The method of claim 12, further comprising the step of displaying the identified dependencies according to color.

17. The method of claim 12, further comprising the step of generating an incompatibility report.

18. The method of claim 12, further comprising the step of incorporating the skeletal software application into a vehicular software application.

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