JP7021990B2 - Source creator - Google Patents

Description

The present invention relates to a source creation device.

In software development, it is desired to improve the productivity of sources including source programs, such as cost reduction and shortening of delivery time. In addition, applications such as Web applications, in which processes are multi-layered on terminals and servers and GUIs (Graphical User Interface) are becoming widespread, it is important to improve the productivity of the sources of such applications.

In order to improve the productivity of the source, a system for automatically generating the source has also been proposed. For example, in Patent Document 1, an automatic generation rule storage unit that stores a source code generation rule associated with the first template. And a source file generator that generates a skeleton class source file based on the first design document and source template, and generates a component class source file based on the second design document and source code generation rules. Is disclosed.

Japanese Unexamined Patent Publication No. 2007-241346

If the configuration disclosed in Patent Document 1 is used, the source (source code) can be automatically generated. However, Patent Document 1 does not disclose a sufficient configuration for automatically generating a source of a Web application.

An object of the present invention is to provide a device for creating a source of a Web application.

A typical source creation device according to the present invention is a source creation device that creates a source including a source program, and has a function configuration information unit in which information on screen items is stored and processing information of an event generated by a screen operation. The information of the screen items stored in the functional configuration information section is applied to the event information section in which is stored, the template source information section in which the source to be the template is stored, and the source stored in the template source information section. Then, a basic source is created, and the source creation processing unit that creates the source by applying the processing information of the event stored in the event information unit to the created basic source is provided. do.

According to the present invention, it becomes possible to provide a device for creating a source of a Web application.

It is a figure which shows the example of the source making apparatus. It is a figure which shows the example of each layer. It is a figure which shows the example of the information flow between layers. It is a figure which shows the example of the screen item information. It is a figure which shows the example of the screen information. It is a figure which shows the example of the functional information. It is a figure which shows the example of a query. It is a figure which shows the example of the query information. It is a figure which shows the example of the event definition information. It is a figure which shows the example of the screen event pattern information. It is a figure which shows the example of the functional event pattern information. It is a figure which shows the example of the template source information. It is a figure which shows the example of the source creation process. It is a figure which shows the example of the presentation layer basic source creation process. It is a figure which shows the example of the application layer basic source creation process. It is a figure which shows the example of the data access layer basic source creation processing. It is a figure which shows the example of the source event process creation process. It is a figure which shows the example of the data access layer control component provision process.

Hereinafter, preferred embodiments for carrying out the present invention will be described as examples with reference to the drawings.
FIG. 1 is a diagram showing an example of a source creation device 100. The source creation device 100 may be, for example, a general computer, and includes a processor 180 and a storage device 170. The processor 180 executes a program stored in the storage device 170 and processes the data stored in the storage device 170.

In addition to the processor 180 and the storage device 170, the source creation device 100 may include an input / output device that serves as an interface with a network or a user interface (not shown). Further, the source creation device 100 may be composed of a plurality of computers connected to each other via a network.

The storage device 170 is a storage device such as a memory, a hard disk drive, or a flash memory, and may be a combination thereof. The function configuration information unit 110 is data (information), and is composed of each data of screen item information 111, screen information 112, function information 113, and inquiry information 114. The functional configuration information unit 110 will be further described later with reference to FIGS. 4A to 4E.

The event information unit 120 is data, and is composed of each data of the functional event pattern information 121, the screen event pattern information 122, and the event definition information 123. The event information unit 120 will be further described later with reference to FIGS. 5A to 5C.

The template source information unit 130 is data and includes data of one or a plurality of template source information 131. The template source information unit 130 will be described later with reference to FIG.

The source creation processing unit 140a is a program executed by the processor 180, and is composed of each program of the basic source creation unit 141a and the source event processing unit 142a.

The source creation processing unit 140a will be further described later with reference to FIGS. 7 and 9, but the basic source creation unit 141a and the source event processing creation unit 142a, respectively, have the basic source creation units 141b to 141d and the source event processing. Call each of the creation units 142b to 142d.

Each of the presentation layer source creation processing unit 140b, the application layer source creation processing unit 140c, and the data access layer source creation processing unit 140d is a program executed by the processor 180, and is a program executed by the processor 180, and is a basic source creation unit 141b to 141d and a source event processing. The program of any one of the creation units 142b to 142d is included. These programs will be further described later with reference to FIGS. 8A-8C.

The data access layer control component providing unit 150 is a program executed by the processor 180, and will be described later with reference to FIG.

The processor 180 that executes a program stored in the storage device 170, for example, a program called the source creation processing unit 140a, may be regarded as an object called the source creation processing unit 140a, that is, a circuit.

Further, the data stored in the storage device 170, for example, the data of the function configuration information unit 110 may be an object including a program in which the data is read / written. Then, the processor 180 that reads and writes the function configuration information unit 110 and the data to be read and written may be collectively regarded as a thing called the function configuration information unit 110, that is, a circuit.

Therefore, the source creation device 100 may be regarded as a device including three information units, four processing units, and one providing unit.

Such a source creation processing unit 140a functions by using the presentation layer source creation processing unit 140b, the application layer source creation processing unit 140c, the data access layer source creation processing unit 140d, and the data access layer control component providing unit 150. It processes the data of the configuration information unit 110, the event information unit 120, and the template source information unit 130, and outputs the source 160 of each layer.

The source 160 of each layer is composed of a presentation layer source file 161, an application layer source file 162, a data access layer source file 163, and a data access control component file 164, and these files will be described below with reference to FIG. ..

FIG. 2 is a diagram showing an example of each layer. The system shown in FIG. 2 is an example of a Web application. When the user 250 operates the terminal 214 (browser), the server 223 (Web application server) connected to the terminal 214 via a network exchanges information with the terminal 214. , Access the DB 241 of the DB server 242 connected to the server 223.

Such a Web application is a multi-layer application, and the terminal 214 has a presentation layer 210, the server 223 has an application layer 220 and a data access layer 230, and the DB server 242 has a DB layer. However, the layer is not limited to these four layers, and may be three or less layers or five or more layers.

Although the programs of each layer shown in FIG. 2 cooperate with each other, the processing contents themselves differ due to the division of processing, etc., and the source program is generally created in a programming language suitable for each processing. The language is also different.

The source program of the presentation layer 210 is created in "Language A". "Language A" is, for example, Javascript®. The source program of the application layer 220 is created in "Language B". "Language B" is, for example, C #.

The source program of the data access layer 230 is created in "Language C". "Language C" is, for example, SQL. Further, the source program of the DB layer 240 is often created in "language D", and the language of the source program is often different for each layer.

Further, apart from the productivity of the source program, there may be variations in the combination of the layer and the programming language, such as creating the source program of the data access layer 230 in "language B".

The presentation layer 210 includes static pages 211, dynamic pages 212, and scripting language 213, which are objects (codes) based on the presentation layer source file 161 shown in FIG.

However, when processed by the interpreter at the terminal 214, the object may be the source itself, or the object may be an intermediate language code. Further, the presentation layer 210 may include other objects.

The application layer 220 includes a service class 221 and a component class 222. The service class 221 is an object on which the application layer source file 162 is based. However, the application layer 220 may also include other objects.

The data access layer 230 includes a data access control class 231 and an entity class 232, and a query file 233. A part of the data access control class 231 and a part of the query file are objects based on the data access layer source file 163 and the data access control component file 164. The flow of information between the plurality of layers will be described below with reference to FIG.

FIG. 3 is a diagram showing an example of information flow between layers. Those described with reference to FIG. 2 are designated by the same reference numerals and the description thereof will be omitted. When an event occurs due to an operation of the user 250 or the like, the page at the time of occurrence becomes the event generation source page 311. The event source page 311 is a static page 211 or a dynamic page 212.

Based on the event, the source screen item information and 321 are sent from the presentation layer 210 to the application layer 220, processed by the service class 221 and become the transition source screen data 331. The transition source screen data 331 is sent from the application layer 220 to the data access layer 230 as the generation source screen item information and other 341, and is converted into the transition destination screen item data 332.

The data access layer control component 352 and the event query 351 are parts of the data access control class 231 and the query file 233 shown in FIG. 2, respectively. The data access layer control component 352 accesses the DB 241 via the control component group 353 based on the source screen item information and other information 341 and the event query 351 information, and is generated based on the information obtained from the DB 241. The previous screen item information and other 342s are sent to the application layer 220.

Here, the entity class 232 and the control component group 353 are data and objects created independently of the source creation device 100, and may be stored in advance in the server 223.

The generation destination screen item information and others 342 are processed by the service class 221 and added to the transition destination screen item data 332. The transition destination screen item data 332 is sent from the application layer 220 to the presentation layer 210 as the generation destination screen item information and 322, becomes the event generation destination page 312, and is displayed to the user 250.

In addition to the above description, individual processing or dedicated processing in each layer such as the component class 222 in the application layer 220 may be included. In FIGS. 2 and 3, the relationship with the source 160 of each layer created by the source creation device 100 has been mainly described, but since the operation of the object (code) in the Web application is the same as that of the general one, it is detailed. The explanation is omitted.

FIG. 4A is a diagram showing an example of screen item information 111. As shown in FIG. 4A, the screen item information 111 includes many items and information (data), and each item is divided into static attribute information 411 and dynamic attribute information 412.

The static attribute information 411 is information set by the source creation processing unit 140a before the start of creation of the source 160 of each layer. The source creation processing unit 140a incorporates the information set in the static attribute information 411 into the source file of the source 160 of each layer, for example, the source program or the data area read by the source program.

The dynamic attribute information 412 is information input on the event generation source page 311 by the operation of the user 250. The source creation processing unit 140a defines the items set in the dynamic attribute information 412 as variables and incorporates them into the source file of the source 160 of each layer.

For example, when the query information created from the query information 114 is dynamic information and includes a control statement such as conditional branching or repetition, the variables defined from the items set in the dynamic attribute information 412 are controlled. It may be incorporated into the sentence. The information set in the static attribute information 411 may be incorporated in the control statement.

FIG. 4B is a diagram showing an example of screen information 112, and FIG. 4C is a diagram showing an example of functional information 113. In the example shown in FIG. 4C, one "template source 1" is associated with both "user maintenance" and "card maintenance" whose "function name" is "template source".

In this way, even if the function names are different, only the item information on the screen is different, and if the screen structure or transition is the same, the same template source can be used, so 1 for 2 or more function names. Two template sources may be associated.

FIG. 4D is a diagram showing an example of inquiry information 114. The "query name" of the query information 114 is information indicating the query information, which is "Q001" in the example of FIG. 4D, and an example of the query information 421 of "Q001" is shown in FIG. 4E.

The query information 421 shown in FIG. 4E is an example of the query information written in SQL. The query information 421 may be in a language other than SQL, and query information having the same content may be created in a plurality of different languages.

Query information is created by presetting templates for each content and language, selecting templates according to the specified content and language, and changing them according to static attribute information 411 or dynamic attribute information 412. May be done.

The screen information 112, the function information 113, and the inquiry information 114 shown in FIGS. 4B to 4D may also include static attribute information and dynamic attribute information.

FIG. 5A is a diagram showing an example of event definition information 123. The event definition information 123 is information that defines the event processing itself, and as shown in FIG. 5A, the processing of each layer is defined for each event. A sub-event may be defined for an event, and if multiple events have the same processing, the processing may be defined in a common sub-event, and even if the same processing is performed in multiple layers, it is common. The process may be defined in the sub-event.

The description of event and sub-event processing consists of three types of lines: a control statement such as conditional branching or repetition, an instruction statement that actually performs processing, and a reference statement that reads other event processing. The instruction statement and the reference instruction statement may include the attribute information defined in the function configuration information unit 110 as a variable. Further, the static attribute information defined by the function configuration information unit 110 may be used as the control statement.

Further, the processing of the event and the sub-event may be described for each programming language. For example, when the source program of the data access layer is described in "Language B" or "Language C" as described with reference to FIG. 2, the data access layer of the event is described in the process by "Language B" and "Language". The description of the process according to "C" may be arranged in a selectable manner.

FIG. 5B is a diagram showing an example of the screen event pattern information 122. The screen event pattern information 122 includes information in which event information is patterned and stored in a database for each screen. Further, FIG. 5C is a diagram showing an example of the functional event pattern information 121. The function event pattern information 121 includes information in which event information is patterned and stored in a database for each function.

FIG. 6 is a diagram showing an example of template source information 131. In the template source information 131, the source that is the base for creating the source for each layer is defined. Therefore, although the example of the information of the application layer 220 is shown in FIG. 6, the information of the presentation layer 210 and the data access layer 230 is also included.

The source (program) defined in the template source information 131 may include a control statement such as conditional branching or repetition, an instruction statement that actually performs processing, a class or property, and a declaration statement that defines a method. Each of these statements may include the attribute information defined by the functional configuration information unit 110 as a variable, and in particular, the static attribute information defined by the functional configuration information unit 110 may be used as the control statement.

Further, the source defined in the template source information 131 may be described for each programming language. For example, when the source program of the data access layer is described in "Language B" or "Language C" as described with reference to FIG. 2, the template source of the data access layer is a template for describing the processing in "Language B". A source and a template source for describing the processing in "Language C" may be included and selected.

FIG. 7 is a diagram showing an example of the source creation process. This source creation process may be a process in which the processor 180 executes the program of the source creation processing unit 140a. In particular, steps 701 to 703 are the basic source creation unit 141a, and step 704 is the source event processing creation unit 142a. Therefore, the description whose subject is each part such as the source creation processing unit 140a may be replaced with the description whose subject is the processor 180.

First, the information of the source to be created is set. As the information to be set, the information of the function name may be included, or the information of the language type of the source program for each layer may be included. The setting of this information may be set in a table (not shown) or may be set via a user interface.

Then, according to these set information, the source creation processing unit 140a (basic source creation unit 141a) identifies the processing of the template source or the event (sub-event) and uses it in the following processing.

In step 701, the source creation processing unit 140a creates the basic source of the presentation layer 210. For this creation, the presentation layer source creation processing unit 140b (basic source creation unit 141b) is called, which will be described later with reference to FIG. 8A. Here, the basic source is a source that does not incorporate event processing.

In step 702, the source creation processing unit 140a creates the basic source of the application layer 220. For this creation, the application layer source creation processing unit 140c (basic source creation unit 141c) is called, which will be described later with reference to FIG. 8B.

In step 703, the source creation processing unit 140a creates the basic source of the data access layer 230. For this creation, the data access layer source creation processing unit 140d (basic source creation unit 141d) is called, which will be described later with reference to FIG. 8C.

When the creation of the basic source of each layer is completed, in step 704, the source creation processing unit 140a (source event processing creation unit 142a) incorporates the source related to the event into the basic source of each layer. This will be described later with reference to FIG.

Finally, in step 705, the source creation processing unit 140a performs the provision processing of the data access layer control component. A data access layer control component provider 150 is called for this provision, which will be described later with reference to FIG. By the above processing, the source 160 of each layer is created.

FIG. 8A is a diagram showing an example of a presentation layer basic source creation process. In step 801 the presentation layer source creation processing unit 140b (basic source creation unit 141b) reads the function information 113, the screen information 112, and the screen item information 111 of the function configuration information unit 110.

In step 802, the presentation layer source creation processing unit 140b reads the template source information 131 from the template source information unit 130 based on the information of the read functional configuration information unit 110.

Here, the template source information 131 to be read is a template source corresponding to the presentation layer 210, but when the programming language of the presentation layer 210 is specified, it is a template source further corresponding to the designated programming language.

In step 803, the presentation layer source creation processing unit 140b refers to the information of the function configuration information unit 110 and the template source information 131, and processes the control statement included in the template source based on the attribute value of the function configuration information unit 110. Create a source containing statements and declarations while setting.

If the instruction statement and the declaration statement include change information in this creation, the attribute value of the function configuration information unit 110 is embedded according to the change information.

In step 804, the presentation layer source creation processing unit 140b creates a source that defines the screen layout information using the screen item information 111, and in step 805, the created source is used as a name in the interface of each source file. , Set the key information (screen item name) for specifying the screen item of the screen item information 111. The source created as described above is used as the basic source for the presentation layer.

FIG. 8B is a diagram showing an example of an application layer basic source creation process. Steps 811 to 813 executed by the application layer source creation processing unit 140c (basic source creation unit 141c) are the same as steps 801 to 803, but the template source corresponding to the application layer 220 is read instead of the presentation layer 210. ,used.

Further, when the programming language of the application layer 220 is specified, it is a template source further corresponding to the specified programming language.

Next, since the property may be required for the data interface between the presentation layer 210 and the application layer 220 depending on the event, in step 814, the application layer source creation processing unit 140c reads the information of the event information unit 120. , The property for the interface is set in the source using the information of the read event and the information of the screen item information 111.

Here, the application layer source creation processing unit 140c may define a new class and define the property to be created in the class when there are many variables of the property for the interface.

The property for the interface is set with the information for specifying the object by the key information (screen item name) of the screen item information 111 regardless of whether it is defined by the property or the class.

The property for the interface may be, for example, a property such as the source screen item information and 321 shown in FIG. The source created as described above is used as the application layer basic source.

FIG. 8C is a diagram showing an example of a data access layer basic source creation process. Steps 821 to 823 executed by the data access layer source creation processing unit 140d (basic source creation unit 141d) are the same as steps 801 to 803, but instead of the presentation layer 210, the template source corresponding to the data access layer 230 is used. Loaded and used.

Further, when the programming language of the data access layer 230 is specified, it is a template source further corresponding to the specified programming language.

Next, in step 824, the data access layer source creation processing unit 140d reads the query information 114 of the function configuration information unit 110 and creates the query information 421 as shown in FIG. 4E. When the query information itself is defined in advance other than the query information 114, the predefined query information may be the query information 421. The source created as described above is used as the data access layer basic source.

FIG. 9 is a diagram showing an example of a source event process creation process. The source creation processing unit 140a (source event processing creation unit 142a) calls step 704 shown in FIG. 7, and execution starts from step 901.

In step 902, the source creation processing unit 140a extracts information about the events included in the read functional configuration information unit 110 one by one, and based on the extracted information, the event of the event definition information 123 of the event information unit 120 Read one by one from the process.

In step 902, the source creation processing unit 140a determines whether the processing of the read event includes the sub-event processing, and if it determines that the processing of the read event does not include the sub-event processing, the process proceeds to step 904, and the processing of which layer is performed. Is determined.

When the determination result of step 904 is the presentation layer, the source creation processing unit 140a proceeds to step 905, calls the source event processing creation unit 142b of the presentation layer source creation processing unit 140b, and the determination result of step 904 is the application. If it is a layer, the process proceeds to step 906, and the source event processing creation unit 142c of the application layer source creation processing unit 140c is called.

If the determination result in step 904 is the data access layer, the source creation processing unit 140a proceeds to step 907 and calls the source event processing creation unit 142d of the data access layer source creation processing unit 140d.

Then, in step 908, the source creation processing unit 140a has as long as the processing of the event that has not been read in the event definition information 123 remains, or as long as the information regarding the unextracted event remains in the function configuration information unit 110. Return to step 904 and perform the next extraction.

When the extraction of all the information related to the event is completed, in step 909, the source creation processing unit 140a determines whether the processing of steps 902 to 908 is the sub-event processing started from step 911, and is not the sub-event processing. If it is determined, the process proceeds to step 910 and the event processing is terminated.

If the source creation processing unit 140a determines in step 903 that the sub-event processing is included, the process proceeds to step 912, the dotted line from the event to the sub-event shown in FIG. 5A is followed, and the sub-event processing is executed. The sub-event processing of step 912 starts from step 911.

In steps 902 and 908 in the sub-event processing, the source creation processing unit 140a reads one by one from the sub-event processing instead of reading one by one from the event processing of the event definition information 123.

If the source creation processing unit 140a determines in step 909 that the sub-event processing has occurred, the process proceeds to step 913, the sub-event processing is terminated, the process returns to step 912, and the process proceeds from step 912 to step 908.

Each of the source event processing creation units 142b to 142d copies the event processing read from the event definition information 123 to the basic source of each layer. Here, one or more lines of the event definition information 123 may be copied.

When the processing of the read event is a control statement, conditional branching or repetitive processing may be set according to the attribute value of the function configuration information unit 110. Further, when the processing of the read event is a reference instruction statement, the event processing of the referenced event may be set.

Further, as a data interface to different layers, a combination of the dynamic attribute information of the function configuration information unit 110 and the key attribute that can identify the dynamic attribute information may be set for each event.

FIG. 10 is a diagram showing an example of a data access layer control component providing process. Due to some restrictions such as the framework of the server 223, the SQL statement may not be issued to the DB 241 by using the event query 351 in the data access layer 230. For this case, a control component for issuing an SQL statement to the DB 241 based on the information of the interface from the application layer 220 to the data access layer 230 is provided.

In step 951, the data access layer control component providing unit 150 reads the screen item information 111 of the function configuration information unit 110, identifies the information received from the application layer 220, and when the information is received from the application layer 220, goes to the DB 241. Create a fixed part class to execute the query.

As described above, since the source can be created based on the screen item information and the event information, it is possible to create the source of the application using the GUI in particular. In addition, the same template can be used when creating an application with the same screen transitions and controls even if the functions are different, and screen items and event information can be set according to each function.

Furthermore, even if an application consists of multiple layers, especially an application in which different layers are arranged in different devices and the programming language of the source is different for each layer, a source corresponding to the programming language of the source for each layer is created. Will be possible. Since it becomes possible to create the source of such an application, it becomes possible to create the source of a Web application in particular through a plurality of layers.

100 Source creation device 110 Function configuration information unit 120 Event information unit 130 Template source information unit 140a Source creation processing unit 140b Presentation layer Source creation processing unit 140c Application layer Source creation processing unit 140d Data access layer Source creation processing unit 150 Data access layer control Parts provider 160 Source of each layer

Claims (6)

A source creation device that creates sources including source programs.
The function configuration information section that stores screen item information and
The event information section that stores the processing information of events that occur due to screen operations, and
The template source information section that stores the template source,
A basic source is created by applying the information of the screen items stored in the functional configuration information section to the source stored in the template source information section, and the created basic source is stored in the event information section. The source creation processing unit that creates the source by applying the processing information of the event
Equipped with
The functional configuration information unit is
Function information associated with two or more function names and one source stored in the template source information unit is further stored.
The source creation processing unit
When the function name is specified, the source associated with the specified function name is specified in the template source information unit, and the information of the screen item stored in the function configuration information unit is sent to the specified source. To create a basic source by applying
A source creation device featuring. A source creation device that creates sources including source programs.
The function configuration information section that stores screen item information and
The event information section that stores the processing information of events that occur due to screen operations, and
The template source information section that stores the template source,
A basic source is created by applying the information of the screen items stored in the functional configuration information section to the source stored in the template source information section, and the created basic source is stored in the event information section. The source creation processing unit that creates the source by applying the processing information of the event
Equipped with
The event information unit
Event processing information corresponding to a plurality of programming languages of the source program is stored.
The template source information unit is
Sources corresponding to multiple programming languages of the source program are stored.
The source creation processing unit
When the program language is specified, the source corresponding to the specified program language is specified from the template source information unit, and the processing information of the event corresponding to the specified program language is specified from the event information unit. Then, apply the information of the screen items stored in the functional configuration information section to the specified source to create the basic source, and apply the processing information of the specified event to the created basic source. , A source creation device characterized by creating a source. The source creation device according to claim 2 .
The source is a layer-by-layer source for multi-layer processing.
The layer-by-layer source contains the layer-by-layer source program.
The event information department
Event processing information corresponding to a plurality of programming languages for each layer of the source program is stored.
The template source information unit is
Sources corresponding to multiple programming languages for each layer of the source program are stored.
The source creation processing unit
When the program language for each layer is specified, the source corresponding to the specified program language is specified for each layer from the template source information section, and the processing information of the event corresponding to the specified program language is the event. Specify for each layer from the information section, apply the information of the screen items stored in the functional configuration information section to the source specified for each layer, create a basic source for each layer, and create each layer. A source creation device characterized in that a source for each layer is created by applying processing information of an event specified for each layer to the created basic source. The source creation device according to claim 3 .
The template source information unit is
In addition, the source with the statement and declaration containing the change information is stored.
The source creation processing unit
The basic source for each layer is obtained by embedding the information stored in the functional configuration information unit in the source specified for each layer according to the change information contained in the statement and declaration of the source specified for each layer. A source creation device characterized by creating. The source creation device according to claim 4 .
The source is a source creating device, characterized in that the source is a source of a presentation layer in a terminal, a source of an application layer in a Web application server, and a source of a data access layer. The source creation device according to claim 5 .
The functional configuration information unit is
More query information or query information is stored,
The source creation processing unit
When the programming language of each of the presentation layer, application layer, and data access layer is specified, the source corresponding to the specified programming language is specified for each layer from the template source information section, and the specified programming language is used. The processing information of the corresponding event is specified for each layer from the event information section, and the processing information is specified for each layer.
According to the change information contained in the statement and declaration of the source specified as the presentation layer, the information stored in the functional configuration information unit is embedded in the source specified as the presentation layer and stored in the functional configuration information unit. Create a basic source for the presentation layer by creating screen layout information based on the information provided.
The information stored in the functional configuration information unit is embedded in the source specified as the application layer and stored in the event information unit according to the change information contained in the instruction statement and the declaration statement of the source specified as the application layer. Create the basic source of the application layer by creating the properties for the interface with other layers based on the information and the information stored in the functional configuration information section.
According to the change information included in the statement and declaration of the source specified as the data access layer, the information stored in the functional configuration information unit is embedded in the source specified as the data access layer, and the functional configuration information unit is used. Create the query information based on the query information stored in, or create the basic source of the data access layer by using the query information stored in the functional configuration information section.
Applying event processing information identified for each presentation layer, application layer, and data access layer to the basic sources created for each presentation layer, application layer, and data access layer, the presentation layer, application layer, and data access layer. A source creation device characterized by creating a source for each data access layer.

Images