Code builder

Patent metadata

Field	Value
Publication number	US-12079596-B1
Application number	US-202217731954-A
Country	US
Kind code	B1
Filing date	Apr 28, 2022
Priority date	Apr 28, 2022
Publication date	Sep 3, 2024
Grant date	Sep 3, 2024

Abstract

As the number of software tools and standards have greatly expanded, it has become more difficult for programmers to learn and implement the various tools and standards they may encounter on a daily basis in an efficient and effective manner. Significant work-hours, training, and trial and error may be involved when adopting each new tool and/or standard. The present disclosure relates to a code generator that may receive a variety of inputs, such as user-generated code, software descriptions, software standards, software blueprints, and so on, and generate code based on the inputs.

First claim

The invention claimed is:

1. A method comprising:
presenting a code generator graphical user interface (GUI);
receiving, at the code generator GUI, input comprising a file comprising user-generated code written in a first standard, an indication of a software blueprint and a desired software component to add, wherein the input comprises software descriptions, the software descriptions comprising a project type, project metadata, group names, artifact identifiers, package names, project names, context roots, and team email descriptions;
determining, based upon the software blueprint, a framework for machine generation of project source code that conforms to a second standard defined by the software blueprint, wherein the second standard is different from the first standard;
generating, based on the input comprising the user-generated code and the desired software component to add, one or more blocks of code;
generating and outputting, based on the one or more blocks of code and the user-generated code, the project source code in accordance with the framework, wherein generating the project source code comprises converting the user-generated code from the first standard to the second standard; and
exporting the project source code to a code repository.

2. The method of claim 1 , wherein available software components for selection as the desired software component comprise web client data, security components, utility components, persistence components, resiliency components, logger components, testing components, and messaging components.

3. The method of claim 2 , wherein the persistence components comprises a Java Persistence application programming interface (API).

4. The method of claim 2 , wherein the resiliency components comprise a Java Resilience4j fault tolerance library.

5. The method of claim 1 , comprising organizing, sequencing, and standardizing of the user-generated code, the generated project source code, or both, based on the software blueprint.

6. The method of claim 5 , wherein the software blueprint is determined dynamically.

7. The method of claim 1 , wherein the project source code comprises a plurality of files, the plurality of files comprising at least a build automation tool configuration file, a generated test case file, a security configuration file, and an exception handling file.

8. One or more tangible, non-transitory, machine-readable media comprising machine-readable instructions, wherein the instructions, when executed by at least one processor, cause the at least one processor to:
present a code generator graphical user interface (GUI);
receive, at the code generator GUI, input comprising a file comprising user-generated code written in a first standard, software blueprints, software components, or any combination thereof, wherein available software components for selection as the software components comprise web client data, security components, utility components, persistence components, resiliency components, logger components, testing components, and messaging components;
determine, based upon the software blueprints, a framework for machine generation of project source code that conforms to a second standard defined by the software blueprint, wherein the second standard is different from the first standard;
generate, based on the input comprising the file comprising the user-generated code, the software blueprints, the software components, or any combination thereof, one or more blocks of code;
generate and output, based on the one or more blocks of code and the user-generated code, the project source code in accordance with the framework, wherein generating the project source code comprises converting the user-generated code from the first standard to the second standard; and
export the project source code to a code repository.

9. The one or more tangible, non-transitory, machine-readable media of claim 8 , wherein the input comprises software descriptions, the software descriptions comprising a project type, project metadata, group names, artifact identifiers, package names, project names, context roots, and team email descriptions.

10. The one or more tangible, non-transitory, machine-readable media of claim 8 , wherein the project source code comprises a plurality of files, the plurality of files comprising at least a build automation tool configuration file, a generated test case file, a security configuration file, and an exception handling file.

11. A computer-implemented method, comprising:
receiving, at a code generator graphical user interface, a file comprising user-generated code written in a first standard, and inputs comprising software blueprints and software components, wherein the inputs comprise software descriptions, the software descriptions comprising a project type, project metadata, group names, artifact identifiers, package names, project names, context roots, and team email descriptions;
authenticating, authorizing, configuring, or any combination thereof, the user-generated code based on inputs comprising the software blueprints, the software components, or both;
determining, based upon the software blueprints, a framework for project source code that conforms to a second standard defined by the software blueprint, the second standard different from the first standard;
generating the project source code in accordance with the framework based on the file comprising the user-generated code, the inputs, or both, wherein generating the project source code comprises converting the user-generated code from the first standard to the second standard;
configuring an application profile;
performing input validation, business rules requirements code, business rules requirements testing, or any combination thereof for automated testing setup;
transforming one or more database objects to a business object base;
implementing a database connection, a database configuration code, or both; and
performing validation, null check, security testing, or any combination thereof on the generated code.

12. The computer-implemented method of claim 11 , wherein configuring the application profile comprises generating a testing environment.

13. The computer-implemented method of claim 11 , comprising performing setup on one or more application programming interface (API) tools.

14. The computer-implemented method of claim 13 , wherein the one or more API tools comprise a cloud security platform and a build automation tool.

Assignees

• Usaa

Inventors

• Walther Thomas

Classifications

• G06F8/36

  Software reuse · CPC title

• G06F8/34

  Graphical or visual programming · CPC title

• G06F8/30 Primary

  Creation or generation of source code · CPC title