# US 2018/0024814 A1 · Automated enterprise software development

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0024814 A1
- Document ID: US20180024814A1
- Status: Published application
- Kind: A1
- Application number: 15/675,238
- Filed: 2017-08-11
- Published: 2018-01-25
- Earliest claimed: 2009-10-14
- Assignees: Vermeg Services SARL
- Applicants: Vermeg Services SARL
- Inventors: Badreddine Ouali
- Web page: https://patentgrep.com/patent/US20180024814A1

## CPC

- G06F 8/20: Software design
- G06F 8/10: Requirements analysis; Specification techniques
- G06F 8/35: model driven
- G06F 11/36: Prevention of errors by analysis, debugging or testing of software
- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- G06F 11/3696: {Methods or tools to render software testable}
- G06F 8/36: Software reuse
- G06F 11/3636: {by tracing the execution of the program}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The preferred embodiment provides a system and method for automatically generating enterprise software applications with minimal level of manual coding. The preferred embodiment provide a graphical design tool that models an application using Unified Model Language (UML), validate the UML model, and automatically generate deployable application The preferred embodiment also provides a framework of libraries that the target application ca be build from.

## Claims

### Claim at position 1

1-13. (canceled)

### Claim 14

A method for generating a software application using a computer system, comprising the steps of:
modeling business processes in a graphical modeling design tool, the graphical modeling and design tool being a layer that sits on top of a unified model language (UML) visual modeling tool;
creating a UML model by using tagged values a data model to define an exclusive dependency between a current field and another field in a same entity type of the data model or in another entity type of the data model with a relation;
(c) validating the UML model.

### Claim 15 (depends on 14)

The method of claim 14, further comprising determining whether the UML model conforms to pre-defined rules of the graphical modeling and design tool.

### Claim 16 (depends on 15)

The method of claim 15, wherein the determining whether the UML model conforms to pre-defined rules further comprises validating initial values, multiplicities, and/or types.

### Claim 17 (depends on 14)

The method of claim 14, further comprising transforming the validated UML model into metadata.

### Claim 18 (depends on 17)

The method of claim 17, further comprising using the metadata to generate functional and non-functional aspects of the software application.

### Claim 19 (depends on 17)

The method of claim 17, wherein related elements of the graphical modeling and design tool are added to the metadata.

### Claim 20 (depends on 14)

The method of claim 14, further comprising generating a trace in a specific file to analyze tasks performed and/or to log technical problems.

### Claim 21 (depends on 20)

The method of claim 20, further comprising determining a location, a size, and a name of a file to be generated to store the trace.

### Claim 22

A method for generating a software application using a computer system, comprising the steps of:
modeling business processes in a graphical modeling design tool the graphical modeling and design tool being a layer that sits on top of a unified model language (UML) visual modeling tool;
creating a UML model to formalize the modeled business processes;
validating the UML model;
generating code automatically by:
converting the UML model into an XML file;
using the XML file to generate Java source code; and
compiling the generated Java source code using a compiler and creating at least one Java Archive (JAR) file.

### Claim 23 (depends on 22)

The method of claim 22, further comprising determining whether the UML model conforms to pre-defined rules of the graphical modeling and design tool.

### Claim 24 (depends on 23)

The method of claim 23, wherein the determining whether the UML model conforms to pre-defined rules further comprises validating initial values, multiplicities, and/or types.

### Claim 25 (depends on 22)

The method of claim 22, further comprising transforming the validated UML model into metadata.

### Claim 26 (depends on 25)

The method of claim 25, further comprising using the metadata to generate functional and non-functional aspects of the software application.

### Claim 27 (depends on 25)

The method of claim 25, wherein related elements of the graphical modeling and design tool are added to the metadata.

### Claim 28 (depends on 22)

The method of claim 22, further comprising generating a trace in a specific file to analyze tasks performed and/or to log technical problems.

### Claim 29

A method for generating a software application using a computer system, comprising the steps of:
modeling business processes in a graphical modeling design tool, the graphical modeling and design tool being a layer that sits on top of a unified model language (UML) visual modeling tool;
creating a UML model by using tagged values in a data model to define an exclusive dependency between a current field and another field in a same entity type of the data model or in another entity type of the data model with a relation;
validating the UML model; and,
generating code automatically by:
converting the UML model into an XML file;
using the XML file to generate Java source code; and
compiling the generated Java source code using a compiler and creating at least one Java Archive (JAR) file.

### Claim 30 (depends on 29)

The method of claim 29, further comprising determining whether the UML model conforms to pre-defined rules of the graphical modeling and design tool.

### Claim 31 (depends on 30)

The method of claim 30, wherein the determining whether the UML model conforms to pre-defined rules further comprises validating initial values, multiplicities, and/or types.

### Claim 32 (depends on 29)

The method of claim 29, further comprising transforming the validated UML model into metadata.

### Claim 33 (depends on 32)

The method of claim 32, further comprising using the metadata to generate functional and non-functional aspects of the software application.
