FR3102594A1 - Application generation set, associated method and program - Google Patents

Abstract

The invention relates to an application generation assembly comprising - a configuration system which comprises:. a module for handling application usage data (4a, 4b), and comprising means for defining lists of data to be browsed; . a graphical application interface definition module comprising editable graphical elements, and list browse elements, to browse the list and implement the corresponding program requests; - an application generation system (GV) comprising modules for analyzing the data entered in the configuration system and configured to automatically implement the program requests to generate the application, characterized in that a modification modifiable graphic elements entails an implementation of the program requests according to the list and a corresponding modification of the application. The invention further relates to an associated method and program. Abstract figure: Fig. 1

Description

Application generation set, associated method and program

The present invention relates to the field of the production of applications, in particular web applications such as websites or any application using a centralized system containing in particular data regardless of the data storage technology.

The invention relates more particularly to a system and a method implemented by computer, for the production of applications such as websites.

In this area, a known solution is custom development with or without a framework. It is a question of producing a software specially designed to provide a solution adapted to the expectations for the application. It therefore requires the intervention of one or more developers who, depending on the needs, will deploy a single application specifically responding to the formulated functionalities.

In addition, the notion of framework includes a coherent set of structural software components used to create the foundations as well as the outline of all or part of a software architecture.

Thus, the creation of applications such as websites, includes several technical aspects relating to hardware and software modules, interacting digitally to achieve integration of a specific identity graphic charter, reproducible on computers via the Internet, and also includes the insertion of given information, relatively easy to find in the world through the internet.

The invention also attempts to implement solutions against known security risks.

Unfortunately, the development of these custom applications and websites is long, tedious and therefore very expensive.

Another known solution in the prior art is to use a CMS, or Content Management System, namely software specially designed for creating and editing websites. CMS systems offer a graphical interface allowing you to create your website graphically but limited to the features offered. If the user needs more features, then he is forced to switch to traditional coding.

Another solution is to use an MVC architecture (Model – View – Controller; or Model-View-Controller). This is a software architecture recommendation to allow a clear breakdown of the code.

Classically, the controller is composed of 2 parts:
- the router which is the single entry point for requests from the browser to the centralized system such as a server. This makes it possible to make common code between the different web pages.
- the specific controller managing the specificities of the web page.

In addition, the implementation of an MVC-type architecture is accompanied by a tree structure of the different files making up the code.

A first objective is to propose a system and a method making it possible to create an application such as a website quickly and easily compared to custom development.

A second objective is to propose a system and a method making it possible to produce a website having more customization possibilities with reference to systems of the CMS type, in particular by making it possible to easily set up its own functionalities.

To achieve these objectives, the invention proposes an application generation set comprising:
- a configuration system that includes:
. a module for manipulating application usage data, and comprising means for defining lists of data to be traversed;
. an application graphical interface definition module comprising modifiable graphical elements, and list traversal elements, for traversing the list and implementing the corresponding program requests;
. an event management module, configured to define for each type of event linked to the possible graphic elements the expected behavior;
. a cardinality items module configured to frame the behavior of list traversal items;
- an application generation system comprising modules for analyzing data entered in the configuration system and configured to automatically implement the program requests to generate the application.

According to a first aspect, the assembly is configured so that a modification of the modifiable graphic elements leads to an implementation of the program requests according to the list and a corresponding modification of the application.

Advantageously, the invention facilitates the declaration of these functionalities by allowing in particular easy manipulation of the data and assistance in the management of technical problems (security, access conflict).

Preferably, the assembly includes a system for using the application, allowing the user of the application to have access to the graphical interface, with management of the desired data (On the server, in memory of the workstation on which the application runs, or to the graphical interface), and with the expected dynamic behavior.

According to other aspects taken in isolation or combined according to all technically feasible combinations:
- the graphic interface definition module includes standard graphic elements such as checkboxes, text field, video, image, graphic form, date/time field, numeric field, and/or pre-made elements proposed such as menus, star ratings, and/or user-programmed items; and or
- the whole is configured so that once the cardinality element has been defined in the configuration system, then the generation system will be able to create a table in the database which will correspond to the cardinality element, and the relations of this table with the other tables in the database, also being determined from what has been entered in the configuration system; and or
- the set is configured so that an addition of a field in a cardinality element using the configuration system; may cause a column to be added to the database table by the generation system; and or
- the assembly comprises a non-conformity detection module configured to record the interface and the events that have taken place and to verify that this corresponds to the modified interface; and or
- the non-conformity detection module is configured to compare the interface obtained with a simulation of the initial interface to which the user's modifications are added.

The invention further relates to a method for creating an application by means of an assembly according to one of the preceding claims, comprising the following steps:
- definition of the general graphic charter of the application, including modifiable graphic elements,
- creation, naming of the application page such as a web page, its entries,
characterized by the steps
- definition of a list to browse and of a "list browse" element,
and in that a modification of the modifiable graphic elements leads to an implementation of program requests according to the list and a corresponding modification of the application.

Another object of the invention relates to a computer program product comprising portions of program code recorded on a medium usable in a control unit, to implement the modules of a set according to the invention or the steps of a method according to the invention, when executed by the control unit.

The invention will be further detailed by the description of non-limiting embodiments, and on the basis of the appended figures illustrating variants of the invention, in which:
is an overall operating diagram of a website;
is a diagram of the different steps for defining an application using the invention;
is a diagram of an MVC (model-view-controller) architecture;
is an illustration of a dependency between tables;
is a diagram of the application's page controller actions;
is a diagram of security automation.

The invention relates to the production of applications such as websites in particular, in particular by using computer means. The invention relates more particularly to a system 1 and a method implemented by computer, for the realization of applications.

The creation of applications, such as websites for example, includes several technical aspects relating to hardware and software modules, interacting digitally to achieve integration of a specific identity graphic charter, reproducible on computers via the Internet. , and also including the insertion of given information, relatively easy to find in the world through the internet.

The invention is not limited to the means presented.
- the term “Javascript” can be interchanged with another language or client code.
- “Databases” can more generally be “data management systems”
- a “Web page” can also more generally be an “HMI”.

It is possible to create a web page from a web interface, this mainly concerns the definition of the GUI elements (Ex. in web technology: HTML), and the style (Ex. in web technology: CSS).

A website is made up of:
- GUI: Client code: for example web pages: HTML + CSS + Javascript (Client code making the page more dynamic),
- Server software to manage transitions between web pages and manage data loading/savings,
- Data access queries (usually in SQL).
(One could consider other data storage systems than databases, such as files for example).

The invention details how to manage all of these activities from a web interface to:
- Generate client code and server software
- Generate the management of the loading / recording of data in the database, or any other data management system.

For this, an innovative architectural pattern and a demanding theoretical study have been implemented.

To this end, the invention relates to an assembly comprising a configuration system and a generation system. The Configuration System allows the user of the Application Configuration Tool to specify information that will be used by the build system to define the data structure. The configuration system will then allow the data to be defined in a second step.

In addition to easier development, being able to define the structure of the data (rather than the data itself) and then configure the data allows you to:
- preferably, easily manage multilingual management of the application;
- define application templates; transferable (by DB or by file) then configurable by a customer;
- connect data from different applications.

An overall operating diagram of a website is illustrated in FIG. 1. In a simplified manner, the centralized system 2 such as a web server has the task of constituting the web page, which will then be sent to the web browser 3, and therefore made available to the user 4.

Generally, it is the user 4 (Ex.: Address entered in the web browser) or the web browser (Ex.: Click on a link to another web page in a web page) who asks the centralized system 2 to provide the web page, but it is possible that the centralized system 2 sends data to the browser in the case of implementation of web socket for example.

Centralized system 2 can send the entire web page, but can also send data that will then be used by the web page's client code to update only part of the web page.

The mechanism for loading and saving a web page (including data) is preferably protected, in order to prevent a malicious person from accessing data to which he should not have access or saving data that he should not be able to record or perform any other type of malicious action (For example, a malicious hacker could overwrite all data in the database).

Indeed, it is quite possible that the attacker skews the web page sent to the centralized system 2, so a website can only be truly secure if there is protection in place at the level of the centralized system 2.

Concerning the software operation of the centralized system 2, such as a web server, the general case is detailed according to a three-tier architecture: Presentation (Browser) / Processing / Access to data:

The web browser 3 sends to the centralized system 2 data which are of two types:
- data entered by the user,
- context elements allowing the centralized system 2 to determine what it should do with the data sent.

The generation system is used to generate the interface between the application and a centralized system. The structuring of the data at the level of the configuration system also makes it possible to provide enough information to be able to generate these contextual elements.

The centralized system 2 determines the processing to be carried out concerning the data received from the browser 3. In particular, checks take place to ensure the integrity of the recorded data.

The centralized system 2 applies the determined processing; in particular, this may be the recording of data sent to the server.

The centralized system 2 determines the processing to be carried out to provide the information to the browser 3 in return.

The centralized system 2 applies the processing determined above, with the possible recovery of the data.

The information is sent to the browser 3. It is of 2 types:
- the data used for the web page: HTML, CSS, Client Code, and Data
- the use context elements making it possible to indicate to the web browser 3 how to use the data in the web page.

The use of context elements is particularly true when it comes to updating only part of the web page. In the case of a passage from one page to another, the context elements correspond to the name of the source page, and the destination page as well as its input data.

Figure 2 illustrates an MVC (model-view-controller) architecture.

A website development standard consists in applying a so-called MVC architecture:
- V: A view contains the presentation of the user interface, in particular the graphic aspect.
- C: A controller contains the logic concerning the actions carried out by the user. For better management, the controller is composed of two parts:
. The router, which is the single entry point for requests from the browser to the centralized system 2. This makes it possible to make common code between the different web pages.
. The specific controller managing the specifics of the web page.
- M: A model contains the data and the processing to be performed on the models (Object programming is therefore well suited to this exercise). The models represent the concepts used in the application (Users, email, etc.).

Once the application is generated and used, the data flow is always the same. In a simplified way: the page is loaded with the data from the database, and the data entered by the user of the application is saved in the database.

The particularity of the invention is to add during the description of the view:
- list traversal elements,
- the elements of the cardinalities,
- mappings on saving and loading.

This makes it possible to define tables in the database, their relationships (which is a fundamental element of relational databases), as well as the requests for saving and loading data.

Figure 3 illustrates different steps for defining an application such as a website using the invention. Steps with a bold border are specific to the invention.

CMS are sites that come with ready features with the ability to customize them to some extent. The invention preferably does not fit into this approach: the objective is to provide a tool to simplify and accelerate the development of a tailor-made website.

The general principle of the invention consists in adding additional information from the view configuration system to then allow the entire application to be generated, for example a website, server side and client side.

However, this simplification will use facilitating methods implemented for example by the CMS:
- the use of graphical interfaces and in particular WYSIWYG (“whatyouseeiswhatyouget”);
- the automation of the realization of a certain number of technical processing on the server and browser side.

The graph in Figure 3 explains the different steps for defining an application using the invention.

The HTML/CSS, javascript processing (=Client code), server processing and database model are classic elements mentioned below. "javascript" is an example of a programming language. Other languages could be used in the context of the invention such as Angular.

Attention should be paid to these columns in Figure 3:
- VIEW model: It allows the creator of the web page to indicate what is the data structure of the web page. It is this knowledge that will be used to define the data model of the centralized system, and the software model of the local data of the generated application.
- Software model (client code/javascript): Using the local memory of the user's machine, it allows the web page to manipulate data, such as for example to load data from the database.

The steps for creating an application using the invention are:
- E1/ Definition of the application's general graphic charter. This is a classic CMS function.
- E2/ Creation, naming of the application page such as a web page, and its entries.
- E3/ Indication of authorization to connect directly to the page (ie by entering the URL of the web page).
- E4/ Definition of the list to be browsed and of the “list browsing” element. This is a concept specific to this invention.
- E5/ The behaviors of list traversal elements must also be defined, in particular in the case of default opening, and in terms of default closing processing.
- E6/ The cardinality element is an element making it possible to process different types of operation when traversing the list. This is a concept specific to this invention.
- E7/ Thanks to the introduction of the two previous items, it is possible to automatically generate the tables in the database, as well as the relations linking them, and preferably to make declarations of functional keys. This differs from CMSs which simply associate a table with a form (=Write). This is to be able to model and use any type of data structure by level of cardinality (= System data model), for use both in reading and writing data. This data format is also reported for storing and managing data in the web browser (=Software model).
- E8/ This concerns the declaration of E8a blocks and E8 fields, ie HMI elements such as HTML and CSS, in particular in the form of a WYSIWYG interface.
- E9/ This block is used to link view data to database data. There can also be a mapping with associable objects. The innovation comes from E4/ E6/ and E9/ in particular which make it possible to define any type of data structure; and therefore allows you to create any type of application.
- E10/ The previous item allows, through an automatic generation mechanism, to complete the tables with the linked fields (in particular by adding, modifying, or deleting columns), but also to create requests for data recovery, updating , or deleting an item from the database.
- E11/ Declaration of behavior in the event of non-compliance, management of access conflict, and attempted fraud on the browser and server side, as well as the processing on the browser and server side. The invention proposes a generic detection method for this type of problem.
E12/ The last part consists in defining processes associated with events on the web page (= Actions on the web page mainly by the user or reception of external signals by websocket for example).

Alternatively or in combination, the realization of the application can be made on the basis of one or more models (template) predeveloped or produced according to the steps of the method of the invention. We can talk about model data. The modifications are then made from the view of the model in question.

The creation of the application is implemented by a set of particular systems (or kit). The invention is implemented in a centralized system 2 such as a web server connected to control units such as application user computers.

The set includes an application configuration system, which includes:
- a data manipulation module. This data may be located when using the application on a centralized system such as a server, at the application user's workstation, or directly entered in the user's graphical interface. . This module can be used, among other things, to define the data to be browsed,
- a module for defining the modifiable site graphical interface, allowing you to define several types of elements:
o standard graphic elements (e.g. check boxes, text field, video, image, etc.);
o pre-made elements offered by the website (Ex.: Menu, rating by stars, etc.);
o list browsing elements, to browse the list and implement the corresponding program requests;
o cardinality elements, which will be called by the list traversal elements wisely according to their characteristics;
- An event management module, allowing the expected behavior to be defined for each type of possible event (Ex. Click on a button).

Thus, the invention facilitates the declaration of these functionalities by allowing in particular easy manipulation of the data, assistance in the management of technical problems (security, access conflict).

The set also includes an application generation system:

Analyzing the data entered into the application configuration system automatically implements several things, including:
- the structure and the requests for access to the database,
- the interface between the application and the server,
- the controller.

The set also includes a system for using the application:

The system then makes it possible to use the system so that the user of the application has access to the graphical interface, with the desired data management (on the centralized system 2, at the level of the station on which the application operates, or to the graphical interface), and with the expected dynamic behavior.

The invention is based on computer modules for website production, making it possible to optimize said production in terms of time savings compared to custom development, and in terms of customization capacity compared to conventional CMS systems.

Among these modules, the invention comprises a module for configuring data of modifiable views to be displayed. This module makes it possible to implement a definition of the general graphic charter of the application. These are in particular the keyboard and mouse 4a, and the server code and application data 4b.

This module may further comprise means for creating and naming the web page, its entries.

In addition, this module may also include means for indicating the authorization to connect directly to the web page (i.e. by entering the URL of the web page).

The invention includes a view module for displaying an editable graphical interface. The interface will be further detailed below.

The invention further comprises a browse list module, for defining data to browse, and associating it with corresponding program requests.

These modules are part of the configuration system.

The invention further includes a data management system such as a relational database, for associating view list data with corresponding server list data,

The invention further comprises a list traversal module, for traversing the list and implementing the corresponding program requests.

The List and To-Go List Parsing Module and Cardinality Element Module were designed to implement a system to uniquely identify data on a web page, regardless of functionality. of the app. The implementation of this system will then make it possible to manage the reading/writing of data from the view to the database.

The classic constitutions of database queries raise certain uncertainties and ambiguities. In particular, in the case of a hotel reservation site with an SQL query to retrieve data in order to associate a note with its reservation would be of the type:
“ SELECT
hotel.address ,
reservation.datereservation ,
reservation.note
FROM booking
JOIN hotel ON hotel.id = reservation.hotel _id
WHERE reservation.user_id = < my technical user id> ”.

The analysis of the SQL query does not make it possible to determine to which functional data(s) the note on the reservation relates: the hotel, the reservation, or both (In our case, the note on the reservation naturally refers to the reservation).

The invention proposes to remove this ambiguity, so that the user does not have to declare, in the SQL query, the way of retrieving the informative data, but just to define the data to be browsed: This is the list to browse.

In the previous example, this would yield the following database query:
"SELECT id FROM reservation WHERE user_id = <my technical user id> ".

The implementation of the invention provides a graphical interface for defining SQL queries; and an additional system allowing to define the way of retrieval of the additional informative elements requiring to solicit other tables (which allowed the join with the JOIN deleted in the example). This system will be described below.

In addition, a means is put in place to be able to browse the defined list, but also to be able to cover the real needs for performing a join: This is the list traversal element.

For example, in the case where the fields of a web page are associated with the elements of the following query:
« SELECT list1.id , list2.id
FROM name AS list1
JOIN date AS list2 ON list 2 .value = list 1 .datecreation
WHERE list1.text LIKE '%a%' AND list2.value >'2019-01-02' ”;

So, this will be defined in the invention with this type of form:
“ List traversal item named list 1 ” such as “ list 1: SELECT id FROM name WHERE name. text LIKE ' %a%' "
" List traversal element named list 2 " such as " list 2: SELECT id FROM date WHERE date.value >'2019-01-02' ANDdate.value = list1.datecreation "

It is therefore possible here to call on the data from list 1 or list 2 while having a dependency between list 1 and list 2.

The user defines the data retrieval as 2 queries rather than just one. On the other hand, the implementation of the 2 requests can be done in a single request (which is much more efficient in computation time).

As mentioned previously, it is necessary to be able to determine which are the identifiers of a list to be traversed, in order to then be able to identify the cardinality elements which will be associated with the list element to be traversed.

Thus, it is necessary to know the different possible forms of constitution of the lists to be scanned to determine the identifier of the list.

Generally, the identifier of a list to browse is an identifier of a table; but there are some singularities for example:
- Using UNION requires distinguishing the query
- The use of GROUP BY means that the identifiers are the elements used in the "GROUP BY". Except if the query is of the "SELECT MAX/MIN(identifier) FROM table WHERE … GROUP BY …" type, where in this specific case the identifier is of the table identifier type
- It is possible to build a list mathematically or algorithmically: for example all the elements ranging from 1 to 10.

In summary, the determination of the functional identifiers of a cardinality element is obtained thanks to the knowledge of the following data:
- The definition and analysis (detailed below) of the tree structure of elements to browse and cardinality elements;
- The functional identifiers of the lists of elements to browse;
- The obligation or not to associate the cardinality element with its writer;
- The obligation or not to associate the cardinality element with its recording time;
- The cardinality of the cardinality element (detailed below).

This therefore allows you to:
- Uniquely identify each cardinality element called in the web page; so all the elements contained in the cardinality elements (i.e. all the elements on the page);
- Define the database tables as well as the "functional keys" type links;
- Identify in the database the element to read, update, or delete.

The system further includes a cardinality element module to specify the behavior of fields contained in the list traversal module.

When browsing the different elements of the list, it may be interesting to specify the behavior of the fields contained in the list browsing element.

In a variant, there is a hierarchical alternation between the list traversal elements and the cardinality elements. Thus, list traversal elements can contain cardinality elements, and cardinality elements can contain list traversal elements.

Thus, several possible behaviors can be distinguished. These behaviors will be defined using new blocks: these are the cardinality elements.

The different behaviors of cardinality elements are:
- The block is only called once AND only if there is at least one element in the list to browse;
- The block is only called once AND only if there is no element in the list to browse;
- The block is only called once (regardless of the number of elements in the list to browse);
- The block is called once per element of the list to browse;
- The block is called once per element of the list to browse or once if there are no elements in the list to browse.

These mechanisms make it possible to give latitude to manage the different functionalities that one might need.

The invention aims to dissociate the data access requests between those which define the data to be traversed and the traversal of the structure of the data table in order to be able to retrieve information.

Take as an example an application containing
- A list traversal element named listeA associated with a mathematically constructed list ranging from 1 to 10 in steps of 1; containing a cardinality element named cardinaliteA of type "call to each element of the list to browse"; itself containing an HMI block named textA of the "text to enter"type;
- A list traversal element named listeD; containing a cardinality element named cardinaliteD of type “call to each element of the list to browse”; itself containing an HMI block named textD of the "text to enter" type,
- A list traversal element named listeE; containing a cardinality element named cardinaliteE of type "call to each element of the list to browse"; itself containing an HMI block named textE of the "text to enter" type.

Then a list traversal element named listB associated with a list to traverse consisting of data from the cardinality element cardinalityA. listB contains a cardinality element named cardinalityB of type "call each element of the list to iterate".

The cardinality element cardinalityB contains:
-an HMI block named textB of type text to enter.
- a list traversal element named listeC associated with an SQL-type traversal list using a "GROUP BY" grouped with a textF field and with a field named maxdate from an aggregate function in the SQL query. listeC contains a cardinality element named cardinalitéC of type “call to each element of the list to browse”.

The cardinality element cardinaliteC contains both
- an HMI block named textC of type text to enter;
- an IHM block named lienD of type link to an element of cardinality referring an element to the element of cardinality D;
- an HMI block named listederoulanteE of drop-down list type depending on E of the type.

The table below details the data available from the C cardinality element: no. Accessible table Item available Accessible attributes 1 B textB "value" (Except for graduation and icur)
If present Creation date, last modification date, and user who created the information
Other HTML characteristics of the control (disabled hidden, …) if existing and present in the WEB page 2 B.course=>A textA 3 B.path=>A.path graduation 4 VS textC 5 C. course textF 6 C. course maxdate 7 C.linkD=>D textD 8 VS rolling list 9 C.dropdown listE=>E textE 10 VS here 11 B here

The reasons for accessing the data are:
- n°4 and 8: The data is present in the cardinality element;
- n°7: Links to other tables are defined in the cardinality element;
- n°9: The drop-down list refers to this table;
- Nos. 5 and 6: These are the data associated with the item browsed;
- n°1: It is possible to obtain the data present in the upstream cardinality elements;
- n°2: The data associated with the elements traversed upstream are accessible;
- n°3: Ability to progress in the structure (Sequence of ".parcours"), and the recovery of list type data constituted with the dedicated name "graduation";
- n°10 and 11: The increment numbers of the lists traversed within a block of cardinality.

Thus, the link to the data is very adherent to the view, which shows once again that the data model schema (including the database) is therefore completely defined by the form of the view in this invention, and makes it possible to navigate easily within this data model.

It is possible if necessary to insert requests to read data if necessary to retrieve other information.

The graph in Figure 4 shows that it is possible to uniquely associate:
- an element of table A to an element of table B by following the link from B to A (Browse, link, drop-down list), see top arrow in figure 4, possible for all data from B pointing to the table A;
- AND An element of table C with an element of table B if uniqueness is ensured: an element C can only be associated with a single element B cf bottom arrow in figure 4, where table C n is associated only with the technical identifier of B (= 1 unique key and no backup per user or per record).

A mapping of the data in the database is carried out.

Using the field named textC in the previous example, the default mapping would have the form shown below; but it would be possible to specify the operation differently as shown in the second block below:
Default mapping
“ Saving and loading: C.texteC
Default value if indefinite loading: """
“ Record : C.texteC
Loading : B .textB
Default value if indefinite loading: "Hello" »

List traversal, cardinality, and UI (e.g. HTML) elements can be used to make arrays. The easier navigation of data therefore makes it possible to approach an operation proposed by office spreadsheets.

At least 5 functionalities are made available to be able to reconstruct an operation approaching that proposed by spreadsheets:
- Know the current increment values within the element;
- Browse data within the data structure;
- Define variables that can be arrays of values;
- Provide list manipulation functions to be able to manipulate the view (Adding an item to a list by specifying the index, dimension of a list, deleting an item from a list);
- Perform permanent calculations, and also on tables of values.

By calling " icur  » the increment number in the list traversed by the element of cardinality, in the previous example: the reference « C.texteC » is actually an abbreviation of « C[ B .icur , C.icur ]. textC ".

With this type of redaction, it becomes possible to refer to the previous element in this way:
“C[B.icur - 1 , C.icur ].textC”

But, it would also be possible to call on all the elements surrounding the value (If table view):
C[ From (B.icur-1) to (B.icur+1) , From (C.icur-1) to (C.icur+1) ].textC

More generally, it is possible that the retrieval of software model elements can be performed by lists so as not to limit the use of data:

Array = List browse element [ <List 1 to define> , <List 2 to define> ]

Concerning the manipulation of the elements of the view, given the principle of the block traversal elements, the addition of an element in a list has the consequence of adding elements in the view.

In an example like:
- date="01/01/2019;02/01/2019;03/01/2019;04/01/2019"
- name = "Alfred;Bob;Gerard;Roger"

The corresponding table is as follows: Date 01/01/19 01/02/19 01/03/19 01/04/19 Name Alfred ________ ________ ________ ________ Bob ________ ________ ________ ________ Gerard ________ ________ ________ ________ roger ________ ________ ________ ________

Added value in:
- the "name" list results in adding a line to the table;
- the "date" list results in adding a column to the table.

So, if:
-date="01/01/2019;01/02/2019;01/03/2019;01/04/2019;01/05/2019"
-name = "Alfred;Bob;Gerard;Roger;Neo"

Then the table will become: Date 01/01/19 01/02/19 01/03/19 01/04/19 01/04/19 Name Alfred ________ ________ ________ ________ _______ Bob ________ ________ ________ ________ ________ Gerard ________ ________ ________ ________ ________ roger ________ ________ ________ ________ ________ Neo ________ ________ ________ ________ ________

Moreover, as for some javascript frameworks (AngularJS or others), it is possible to define a formula for a field and an automatic update in the event of a change to an input data.

It is important that calculations be possible on data of the table of values type. We can talk about permanent calculation.

As part of the creation of the web page, the system includes a complete graphical interface.

This interface allows:
- (in a classic way for CMS) to define HTML, CSS, and the graphic charter of the application;
- (in a classic way for the frameworks of the client codes of the web browser) to define the calculation fields based on the data of the web page and updated in real time.

But the invention also proposes to define from a graphical interface:
- New elements: In particular the “Elements of course” and the “Elements of cardinality”, detailed above,
- Database queries,
- Client code functions (e.g. javascript),
- To associate a process with an event of the web page (Arrival of a flow or user action). Note that block initialization is an event as such.
- Preferably, in order to facilitate the use of the tool, the use of pictogram button or numeric keypad is implemented.

The advantages of a graphic use are multiple. This allows to :
- Structure the code naturally, which makes it easier to link and find what is associated with a given UI functionality (for example HTML/CSS/Javascript/SQL/Server code);
- Check user input. Thus, the tool is more intuitive, therefore easier to handle and with less possibility of typos in the code;
- Make the information more readable and take charge of the technical syntax writing tool, so that the training time is reduced.

The tool can allow the user to write code directly so that the possibilities offered by the tool do not limit the usable functionalities.

Figure 5 details the possible actions of the web page controller.

Based on events, signals, timers, view data, controller C sends centralized system a request to load a page to centralized system 2 (S1);

The saved data is then loaded locally on the client side (S2);

The local browser sends a call to the view generator G.V.(S3) which performs a change in the characteristics of the view V(S4);

The corresponding change in data is recorded locally (S5), then transmitted to the centralized system 2 to be recorded there (S6);

This is followed by a call to perform a server-side calculation (S7).

The controller has 2 main functions.

Its first function is to set up the technical base, and thus reduce the amount of code to be produced by the developer using the tool:
- Set up a data structure resulting from the recovery of data in the database in particular;
- Call the view generator to use this data and display the view;
- Use existing technical functions (detection of non-conformity for example).

Its second main function is to bring together all the functional processes defined by the web developer:
- Processing on the browser side in the event of an obligation to enter data;
- Browser-side processing in the event of data entry non-compliance;
- Processing in the event of events, in particular it is possible to:
o Modify data by calling new loads from the database or modifying data already loaded internally;
o Update elements of the view (In particular cardinality elements);
o Provide the database during a save with the data to synchronize with the local data. In particular, this involves indicating which data constitutes the local data of the web page;
o The page load request is handled in a special way. Indeed, it is possible to leave the page during data entry.

Thus, the tool offers a dedicated start/page load processing, in order to avoid code repetition.

Figure 6 illustrates security automation.

A fraud attempt from the application consists of a user doing something that he could not do by using the web page normally (=Use of the keyboard mouse conventionally within the web page).

Thus, the general idea is to record the events caused by keyboard/mouse manipulations on the view and to ensure that the received form corresponds to these operations. We can speak of a non-compliance detection module.

Different ways of doing things are possible, figure 6 specifies one of them.

The steps are:
- C1/ Sending the web page to the browser. Centralized System 2 saves a backup of the web page. A database is associated.
- C2/ Events occur on the page and are recorded at the browser level. In the view there is in particular visibility, transferability, restriction of value. The event history is recorded.
- C3/ When sending the web page to the centralized system, the centralized system checks that there is no problem. Notably :
o Attempt to force data
o Access conflict (Checking if there was a data save during user input)

The proposed invention makes it possible to carry out applications such as websites.

In particular, user data is filled in from lists.

Thus, it is possible to generate applications that could be copied or cloned, and customize using user data intelligence.

In other words, the proposed tool makes it possible to generate applications such as application websites, but also SAAS type websites.

The invention will propose a system for optimizing functional keys in the case where there is a sequence of list traversal elements.

For example: Case 1: We want to build a view to enter the total product sales per day, per salesperson.

In this case, it is essential to refer to the day and to the salesperson in order to be able to record the data (= Entry of the sales total).

Case 2: We want to create a view with one block per store, which will contain the list of sellers in the store. It is possible to associate a free comment for each seller.

Here, it would not be relevant to refer to the store and the seller to record the data (=Entering the comment), because knowing the seller makes it possible to find the store information. It would be a problem to do so, because it amounts to creating duplicate information, which then complicates data management, or even creates inconsistencies (if the 2 pieces of information contradict each other).

Thus, an additional analysis is made, in order to determine the essential keys, and to identify the potentially redundant keys.

Here is an example of a process:
1/ "Naive" determination of all the keys
Case 1: list key1: Vendor identifier / list key2: Value of the day;
Case 2: List key 1: Store ID / List key 2: Vendor ID;
2/ Verification by going up the lists, that the system does not refer to a key from a list further upstream.
In case 2, a seller can be associated with a store (We find the key of list 1 by going back to the identifiers of list 2). Thus, "store" is a potentially redundant reference.

More generally, the invention implemented makes it possible to obtain the very probable reference characteristics (which in particular makes it possible to constitute a data model structure without having real skills in the matter); but it remains possible for a user of the configuration system to remove or add references if he wishes to keep total freedom on the model.

Claims (8)

Computer-implemented application generation set comprising

• a configuration system that includes
  . an application usage data manipulation module (4a, 4b), and comprising means for defining lists of data to be traversed;
  . a definition module (E1) of the graphic application interface comprising modifiable graphic elements, and list traversal elements (E4), for traversing the list and implementing the corresponding program requests;
  . an event management module, configured to define, for each type of event linked to the possible graphic elements, the expected behavior (E5, E7);
  . a cardinality items module (E6, E7) configured to frame the behavior of list traversal items;
  
• an application generation system (C, GV) comprising modules for analyzing the data entered in the configuration system and configured to automatically implement the program requests to generate the application,

characterized in that the assembly is configured so that a modification of the modifiable graphic elements leads to an implementation of the program requests according to the list and a corresponding modification of the application. Generation set according to the preceding claim, in which the graphic interface definition module (E1) comprises standard graphic elements such as check boxes, text field, video, image, graphic form, date/time field, numeric field and/or suggested pre-made items such as menus, star ratings, and/or user-programmed items. Generation set according to one of the preceding claims configured so that once the cardinality element has been defined in the configuration system, then the generation system will create a table in database table which will correspond to the element of cardinality, and the relationships of this table to other tables in the database, also being determined from what has been entered into the configuration system. Generation set according to one of the preceding claims configured so that an addition of a field in a cardinality element using the configuration system; will cause a column to be added to the database table by the generation system. Generation set according to one of the preceding claims, comprising a non-conformity detection module configured to record the interface and the events that have taken place and to verify that this corresponds to the modified interface. Generation set according to the preceding claim, in which the non-compliance detection module is configured to compare the interface obtained with a simulation of the initial interface to which the user's modifications are added. Method of creating an application by means of a computer-implemented application generation assembly according to one of the preceding claims comprising the following steps
(E1) Definition of the general graphic charter of the application, including modifiable graphic elements,
(E2) Creation, naming of the application page such as a web page, its entries,
characterized by the steps
(E4) Definition of a list to browse and a "list browsing" element,
and in that a modification of the modifiable graphic elements leads to an implementation of program requests according to the list and a corresponding modification of the application. Computer program product comprising portions of program code recorded on a medium usable in a control unit, to implement the modules of a set according to one of Claims 1 to 6, or a method according to the preceding claim , when executed by the control unit.