KR101328346B1 - Method of developing application and apparatus for the same - Google Patents

Abstract

An application development method and apparatus therefor are disclosed. Extracting a state corresponding to a feature selected in the feature model from the at least one state-based diagram to generate a first instance; extracting a process corresponding to the feature selected in the feature model from the data flow diagram and extracting a second instance; Generating a first source code using the state of the first instance, and generating a second source code using the process of the second instance. Therefore, it is possible to develop application based on product line using stable architecture model, to specify architecture based on state, and to check consistency with feature model which is the result of domain analysis process.

Description

Application development method and device therefor {METHOD OF DEVELOPING APPLICATION AND APPARATUS FOR THE SAME}

The present invention relates to application development, and more particularly, to an application development method and apparatus for developing a product line application using a state-based architecture model.

The focus of software reuse technology to increase the productivity of software development has shifted from reuse of source code to reuse of software design, and from reuse of software design to reuse based on domain engineering.

The reason for the change of the software reuse technology is that the reuse of the design must be preceded in order to reuse the source code, and in order to reuse the design, the area assets commonly used in the application area must be developed through the area engineering. . Thus, software reuse research has been undertaken over the last few years with a focus on domain analysis and domain engineering.

In the study of software reuse technology, the domain engineering approach is to develop a highly reusable component through extensive analysis of the application area. In many cases, however, this approach tended to include all products in the domain, which in turn increased the cost and duration of software development.

In addition, in an effort to maximize software reusability, emphasizing the layering of software structures and encapsulation for information concealment has resulted in a problem of developing a system with poor performance. As described above, it is difficult to determine the extent of the appropriate area and the degree of reusability in attempting to reuse the software around the application area.

To solve some of the problems mentioned above, a paradigm of software product line engineering has been proposed. According to this paradigm, software reuse is a carefully planned plan for reusing specific software product lines.

That is, according to the software product line engineering, it is possible to clarify the scope of the domain analysis and the development scope of the software product line assets based on the analysis of the market situation to enter the enterprise.

Software product line engineering technology refers to the concept of securing sufficient core assets through the analysis of commonalities and differences in consideration of the functional aspects and the quality of various systems belonging to the domain and combining the assets to develop a desired system.

A feature model is an analysis model in software product line engineering that expresses the commonalities and differences between various systems in a domain in 'feature' units and expresses the relationship between features.

An architectural model refers to a pattern in architectural terms that can be found in many of the domain's systems in product line engineering. There may be various patterns depending on the type of systems.

State-based architecture model refers to an architecture model in which product line engineering can model a system based on a state-based system and integrate domain components around a state-based model.

To develop a state-based architecture model, you must first be able to model your system around a state. Representative state-based modeling tools include statechart and state diagram of unified modeling language (UML).

However, to support the product line, you need to be able to instantiate using a technique such as parameterized to the state-based architecture model written, but the above tools do not support these features.

An object of the present invention for solving the above problems is to provide an application development method method for developing a product line application using a state-based architecture model.

Another object of the present invention for solving the above problems is to provide an application development apparatus for developing a product line application using a state-based architecture model.

Application development method according to an embodiment of the present invention for achieving the above object of the present invention, by extracting a state corresponding to the feature selected in the feature model in the at least one state-based diagram to generate a first instance Extracting a process corresponding to a feature selected from the feature model in the data flow diagram, generating a second instance; generating a first source code using the state of the first instance, and generating a second instance of the second instance. Generating second source code using the process.

Application development apparatus according to an embodiment of the present invention for achieving another object of the present invention to provide at least one state-based diagram for a specific application to the state-based diagram instance generator, the at least one state-based diagram A diagram providing unit for providing a data flow diagram generated based on the data flow diagram generation unit, receiving selection feature information, and extracting a state corresponding to the selection feature information from the provided state-based diagram to generate a first instance. State based diagram instance generation unit, a data flow diagram generation unit for generating a second instance by extracting a process corresponding to the selection feature information from the provided data flow diagram, and the state of the first instance Generating a first source code by using; and generating a second source code by using the process of the second instance.

When using the application development method and apparatus therefor according to the present invention as described above, the application can be developed based on the product line using a stable architecture model, the architecture can be specified based on the state, and the domain analysis process You can check the consistency with the resulting feature model.

1 is a block diagram showing the configuration of an application development apparatus according to an embodiment of the present invention.
2 is a block diagram showing a configuration of a diagram providing unit of an application development apparatus according to an embodiment of the present invention.
3 is a conceptual diagram illustrating a state-based diagram received by a state-based diagram instance generator of an application development apparatus according to an embodiment of the present invention.
4 is a conceptual diagram illustrating an instance of a state-based diagram generated by a state-based diagram instance generator of an application development apparatus according to an embodiment of the present invention.
5 is a conceptual diagram illustrating an instance of a state-based diagram generated by a state-based diagram instance generator of an application development apparatus according to an embodiment of the present invention.
6 is a conceptual diagram illustrating a data flow diagram received by a data flow diagram instance generator of an application development apparatus according to an embodiment of the present invention.
7 is a conceptual diagram illustrating an instance of a data flow diagram generated by a data flow diagram instance generator of an application development apparatus according to an embodiment of the present invention.
8 is a flowchart illustrating an application development method according to an embodiment of the present invention.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention. Like reference numerals are used for like elements in describing each drawing.

The terms first, second, A, B, etc. may be used to describe various elements, but the elements should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

When a component is referred to as being "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in between. Should be. On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are to be interpreted as either ideal or overly formal in the sense of the present application Do not.

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram showing the configuration of an application development apparatus according to an embodiment of the present invention.

Referring to FIG. 1, an application development apparatus includes a diagram provider 100, a state-based diagram instance generator 110, a data flow diagram instance generator 120, an instance verifier 130, and a source code generator 140. It may be configured to include).

The diagram provider 100 may provide a state-based diagram in which the features of the feature model are bound to the state-based diagram instance generator 110, and the features of the feature model are bound to the data flow diagram instance generator 120. You can provide a data flow diagram.

The state-based diagram instance generating unit 110 receives a state-based diagram in which the features of the feature model are bound from the diagram providing unit 100, and receives selection feature information regarding the selected feature among the features of the feature model from the user.

The state-based diagram instance generator 110 may generate an instance of the state-based diagram by extracting a state corresponding to the selected feature information from the state-based diagram to which the feature of the received feature model is bound.

Here, state-based diagrams are diagrams that represent the execution of software in "state" units.

Here, the feature model is an analytical model that expresses the commonalities and differences among the various systems in the domain in software product line engineering in “feature” units and expresses the relationship between the features.

Here, the instance of the state-based diagram is a diagram included in the state-based diagram may be configured with at least one state of the state of the state-based diagram.

The state-based diagram instance generator 110 may provide an instance of the generated state-based diagram to the instance verifier 130. In this case, the state-based diagram instance generation unit 110 may convert the instance of the state-based diagram into an XML file that may be used in a neutral format and then provide it to the instance verification unit 130.

The data flow diagram instance generator 120 receives a data flow diagram to which the features of the feature model are bound from the diagram provider 100, and receives selection feature information regarding the selected feature among the features of the feature model from the user.

The data flow diagram instance generating unit 120 may generate an instance of the state-based diagram by extracting a process corresponding to the selection feature information from the data flow diagram to which the feature of the received feature model is bound.

Here, the data flow diagram is a diagram representing the execution of the software in "process" units.

Here, the instance of the data flow diagram is a diagram included in the data flow diagram and may be configured with at least one of the processes of the data flow diagram.

The data flow diagram instance generator 120 may provide an instance of the generated data flow diagram to the instance verifier 130. In this case, the data flow diagram instance generator 120 may convert the instance of the data flow diagram into an XML file that may be used in a neutral format and then provide the instance to the instance verifier 130.

The instance verifier 130 is an instance of the state-based diagram transformed into a neutral form by the state-based diagram instance generator 110 and an instance of the data flow diagram transformed into a neutral form by the data flow diagram instance generator 120. And verify the instance of the state-based diagram and the data flow diagram instance according to a predetermined consistency rule.

The source code generator 140 receives the state-based diagram instance and the data flow diagram instance verified by the instance verifier 130, generates the first source code by using the state of the received state-based diagram instance, The process of an instance of the data flow diagram can be used to generate the second source code.

First, the source code generator 140 extracts a state class corresponding to each state included in the state-based diagram instance, and configures the first source code by configuring the state class as at least one method included in the script of the state. Can be generated. Here, at least one method included in the state class may call at least one method included in the process class to be described later. That is, at least one method included in the script of the state may be at least one method included in the script of the process.

In addition, the source code generator 140 extracts a process class corresponding to each process included in the data flow diagram instance, and configures the process class as at least one method included in the script of the process to form the second source code. Can be generated.

2 is a block diagram showing a configuration of a diagram providing unit of an application development apparatus according to an embodiment of the present invention.

Referring to FIG. 2, the diagram providing unit 100 includes a first feature model applying unit 111, a second feature model applying unit 113, a diagram information extracting unit 115, and a consistency verification unit 117. Can be configured.

The first feature model applying unit 111 receives the candidate state-based diagram and the feature model, applies the features of the received feature model to the candidate state-based diagram, generates a state-based diagram to which the features are bound, and generates the state-based diagram. The diagram may be provided to the consistency verification unit 117.

For example, the first feature model applying unit 111 receives the candidate state-based diagram and the feature model, and is used to transition the features of the received feature model from one state of the candidate state-based diagram to another. You can apply this information to create state-based diagrams with bound features. The state-based diagram in which the feature is bound will be described in more detail with reference to FIG. 3.

The second feature model application unit 113 receives the candidate data flow diagram and the feature model, applies the features of the received feature model to the candidate data flow diagram, generates a feature-bound data flow diagram, and generates the generated data flow diagram. The diagram may be provided to the consistency verification unit 117.

For example, the second feature model applying unit 113 receives the candidate data flow diagram and the feature model, and adds the features of the received feature model to information about the data provided from the specific process of the candidate data flow diagram to another process. You can apply it to create a data flow diagram with bound features. The feature-bound data flow diagram will be described in more detail later with reference to FIG. 6.

The diagram information extraction unit 115 may receive the candidate state-based diagram, extract diagram information from the received candidate state-based diagram, and provide the extracted diagram information to the consistency verification unit 117.

For example, the diagram information extracting unit 115 receives a candidate state based diagram, and information about a state transition, for example, a transition condition, used to transition from one state to another among the states of the received candidate state based diagram. May be extracted and information about the extracted state transition may be provided to the consistency verification unit 117.

In addition, the diagram information extraction unit 115 may receive the candidate data flow diagram and extract and store diagram information from the received candidate data flow diagram. For example, the diagram information extraction unit 115 may receive the candidate data flow diagram, and extract and store information about data transmitted from one process to another process among the processes of the received candidate data flow diagram.

The consistency verification unit 117 receives a state-based diagram in which the features of the feature model are bound from the first feature model applying unit 111, and the data flow of the features of the feature model is bound from the second feature model applying unit 113. Receive the diagram. In addition, the consistency verification unit 117 receives the feature model, and receives diagram information of the state-based diagram and the data flow diagram in which the feature of the feature model is not reflected from the diagram information extraction unit 115.

Thereafter, the consistency verification unit 117 verifies the consistency of the state-based diagram in which the features of the feature model are bound and the data flow diagram in which the features of the feature model are bound based on the feature model and the diagram information.

In addition, the consistency verification unit 117 may provide a state-based diagram in which the feature of the feature model is bound to the state-based diagram instance generator 110, and provide a data flow diagram in which the feature of the feature model is bound to the data flow diagram instance. It may be provided to the generation unit 120.

3 is a conceptual diagram illustrating a state-based diagram received by a state-based diagram instance generator of an application development apparatus according to an embodiment of the present invention.

Referring to FIG. 3, the state-based diagram received by the state-based diagram instance generator 110 includes at least one state, and is a state transition used to transition from one state to another of at least one state. The information related to the transition is composed of at least one variable element of a trigger event, a condition, and an action.

In a state-based diagram, states are represented by rounded rectangles (210 and 220), and state transitions between rounded rectangles can be represented by arrows. Here, it may be displayed using an arrow connected to a painted circle to distinguish the state 210 from which the transition starts.

In the embodiment of FIG. 3, the state-based diagram received by the state-based diagram instance generator 110 from the diagram provider 100 is composed of State A 210 and State B 220, and State A 210. Condition and action 210a, which is information about a state transition used to transition to State B 220, is shown, and information about a state transition used to transition from State B 220 to State A 210 is shown. Conditions and actions 220a are shown.

Here, the state A 210 is filled with a circle to designate the state A 210 as the starting point of the transition from the state A 210 to the state B 220.

In addition, in the embodiment of FIG. 3, the state-based diagram received by the state-based diagram instance generator 110 from the diagram provider 100 is a state-based diagram in which the features of the feature model are bound. For example, feature F2 in the feature model is bound to Condition and Action 2, which is information about the state transition used to transition from State A 210 to State B 220 in the state-based diagram, and feature F3 in the feature model. Is bound to Event B, which is information about the state transition used to transition from State B 220 to State A 210 in a state based diagram.

At least one state of the state-based diagram includes a script that stores a function that can define an action according to the state of the state. For example, the Ready state, which makes up a state-based diagram, contains a script that stores a function that allows you to define the ready to run state for the Ready state.

The functions used in these scripts must be defined in the process of the data flow diagram described below. Scripts can be represented in various forms, and Table 1 shows examples of scripts included in the state.

4 is a conceptual diagram illustrating an instance of a state-based diagram generated by a state-based diagram instance generator of an application development apparatus according to an embodiment of the present invention.

Referring to FIG. 4, the state-based diagram instance generator 110 may generate an instance of a state-based diagram by extracting a state corresponding to a feature selected from a feature model from a state-based diagram received from the diagram provider 100. have.

The state-based diagram of FIG. 4 is an instance of the state-based diagram generated by the state-based diagram instance generator 110 by extracting a state corresponding to the selected feature F1 among the features F1 to F3 of the feature model in the state-based diagram.

The state-based diagram instance generating unit 110 extracts a state by removing information for state transition to which the features F2 and F3, which are not selected in the feature model, are bound in the state-based diagram of FIG. 3, and extracts the state using the extracted state. You can create an instance of a state-based diagram of 4.

That is, in the state-based diagram of FIG. 3, a feature F2 that is not selected in the feature model is bound to the condition and action 2, which are information about the state transition used to transition from the state A 210 to the state B 220.

Therefore, the state-based diagram instance generator 110 removes the condition and action 2 which are information related to the state transition in which the feature F2 is bound in the state-based diagram of FIG. In step 210, it is determined as Event A / Action 1 (210b) that is information about the state transition used to transition to State B (220).

Also, in the state-based diagram of FIG. 3, the event F, which is information about the state transition used to transition from the state B 220 to the state A 210, is bound to the feature F3 not selected in the feature model.

Accordingly, the state-based diagram instance generator 110 removes an event which is information related to a state transition in which the feature F3 is bound in the state-based diagram of FIG. Information about the state transition used to transition to State A 210 may be determined as Event A 220b.

5 is a conceptual diagram illustrating an instance of a state-based diagram generated by a state-based diagram instance generator of an application development apparatus according to an embodiment of the present invention.

Referring to FIG. 5, the state-based diagram instance generator 110 may generate an instance of a state-based diagram by extracting a state corresponding to a feature selected from a feature model from a state-based diagram received from the diagram provider 100. have.

The state-based diagram of FIG. 5 is an instance of the state-based diagram when the state-based diagram instance generator 110 does not have a selected feature among the features F1 to F3 of the feature model in the state-based diagram of FIG. 3.

The state-based diagram instance generating unit 110 extracts the state by removing information for the state transition to which the features F1 to F3, which are not selected in the feature model, in the state-based diagram of FIG. 3 are extracted, and uses the extracted state. As shown in FIG. 4, an instance of a state-based diagram in which only State A 210 exists may be created.

That is, the state-based diagram instance generator 110 may generate an instance of the state-based diagram of FIG. 5 by extracting a state corresponding to the feature selected from the feature model from the state-based diagram of FIG. 3.

6 is a diagram illustrating a data flow diagram received by a data flow diagram instance generator of an application development apparatus according to an embodiment of the present invention.

Referring to FIG. 6, the data flow diagram received by the data flow diagram instance generator 120 from the diagram provider 100 may include a state-based diagram identifier 500, an external system 510, Process 520, Repository 530, and data, which may be provided as a process in an external system, may be provided as a repository in a process, or the process of constructing a data flow diagram It may be provided from one process to another process.

In the embodiment of FIG. 6, the data flow diagram received by the data flow diagram instance generator 120 from the diagram provider 100 is a data flow diagram to which the features of the feature model are bound. For example, feature F1 of the feature model is bound to data B provided to Process B 540 in Process A 520 of the data flow diagram, bound to Process B 540, and Process B 540 It is bound to data C provided in.

At least one process of constructing a data flow diagram includes scripts that serve as functions or play an important role in connecting and integrating pre-developed reusable components.

The classification of the script components is shown in <Table 2>.

Referring to Table 2, the components of the script consist of Input, Output, Var, Algorithm, and Native Statements. Input specifies the type of input data, Output specifies the type of output data, and Var can specify the type of variable to be used in the process in advance.

In addition, Algorithm can describe an algorithm using input data specified in Input, output data specified in Output, and internal variable specified in Var. Native statements can use the syntax of a specific programming language as internal parts that can be included in the algorithm part. Can be.

The grammatical elements of these scripts can be freely defined. <Table 3> is a simple example of a script implemented by reflecting the above elements.

As shown in Table 3, the variable time representing the input data is designated as Input, the variable velocity indicating the velocity as the output data is designated as the Output, and the internal variable g to be used at the Algorithm is specified as Var. have.

Algorithm is assigned 9.81 to the variable g, and the variable velocity representing the velocity is multiplied by the variable time representing time and 9.81, the value of g. Native Statements uses the syntax of Java, and creates an instance p to square the speed variable, and calls the calculatePow () function of the instance p to square the speed of the variable velocity. Then, an algorithm is described that outputs a variable velocity indicating the calculated velocity.

7 is a diagram illustrating an instance of a data flow diagram generated by a data flow diagram instance generator of an application development apparatus according to an embodiment of the present invention.

Referring to FIG. 7, the data flow diagram instance generator 120 may generate an instance of a data flow diagram by extracting a process corresponding to a feature selected from a feature model from a data flow diagram received from the diagram provider 100. have.

The data flow diagram of FIG. 7 is an instance of the data flow diagram generated by the data flow diagram instance generator 120 by extracting a process corresponding to a feature selected among the features of the feature model from the data flow diagram of FIG. 5.

The data flow diagram instance generating unit 120 extracts a process by removing information for data transmission to which the feature F1, which is not selected in the feature model, is extracted from the data flow diagram of FIG. 5, and extracts a process using the extracted process. You can create an instance of a state-based diagram.

That is, in the data flow diagram of FIG. 7, the feature B, which is not selected in the feature model, is bound to the data B provided by the processor A to the process B 540, and the data C provided to the process B 540 and the process B 540. As such, the data flow diagram instance generator 120 may generate an instance of the data flow diagram of FIG. 7 by removing data B to which the feature F1 is bound from the data flow diagram of FIG. 6.

8 is a flowchart illustrating an application development method according to an embodiment of the present invention.

Referring to FIG. 8, the application development apparatus may generate an application using at least one state-based diagram for a specific application, a feature model and a data flow diagram generated based on the at least one state-based diagram.

The application development apparatus extracts a state corresponding to the feature selected in the feature model from at least one state-based diagram to generate an instance of the state-based diagram (S710), and extracts a process corresponding to the feature selected in the feature model in the data flow diagram. By generating an instance of the data flow diagram (S720).

Here, the application development apparatus may store, in the diagram information storage table, information about a state transition used to transition from a state of a state-based diagram to another state and information about data transmitted from another process to another process in the data flow diagram.

The application development apparatus receives the stateful diagram instance and the data flow diagram instance, generates the first source code using the state of the received stateful diagram instance, and uses the process of the instance of the data flow diagram to generate the second source code. It may be generated (S730).

First, the application development apparatus may extract a state class corresponding to each state included in the state-based diagram instance, and generate the first source code by configuring the state class with at least one method included in the script of the state. . Here, at least one method included in the state class may call at least one method included in the process class to be described later. That is, at least one method included in the script of the state may be at least one method included in the script of the process.

In addition, the application development apparatus may extract a process class corresponding to each process included in the data flow diagram instance, and configure the process class as at least one method included in the script of the process to generate the second source code. .

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the present invention as defined by the following claims It can be understood that

100: diagram provider
111: first feature model application unit 113: second feature model application unit
115: diagram information extraction unit 117: consistency verification unit
110: state-based diagram instance generator
120: data flow diagram instance generator
130: instance verification unit 140: source code generation unit

Claims (17)

A method performed in an application generating apparatus using at least one state based diagram for a specific application and a feature model and a data flow diagram generated based on the at least one state based diagram,
Receiving a candidate state based diagram and the feature model and generating the state based diagram by applying a feature of the feature model to the received candidate state based diagram;
Receiving a candidate data flow diagram and the feature model and generating the data flow diagram by applying a feature of the feature model to the received candidate data flow diagram;
Generating a first instance by extracting a state corresponding to a feature selected in the feature model from the at least one state-based diagram;
Extracting a process corresponding to a feature selected from the feature model in the data flow diagram to create a second instance; And
Generating first source code using the state of the first instance, and generating second source code using the process of the second instance. The method of claim 1, wherein the first source code,
Is generated by extracting a first class corresponding to each state included in the first instance,
The first class is an application generation method, characterized in that composed of at least one method included in the script of the state. The method of claim 2, wherein the at least one method included in the first class includes:
Calling at least one method included in the first class. The method of claim 1, wherein the second source code,
Is generated by extracting a second class corresponding to each process included in the second instance,
And wherein the second class comprises at least one method included in a script of the process. delete The method of claim 1, wherein generating the state based diagram comprises:
Extracting state based diagram information from the candidate state based diagram,
The extracted state-based diagram information is information about a state transition used to transition from a specific state to another state of a candidate state-based diagram, and is used to check the consistency of the candidate state-based diagram. The method of claim 1, wherein generating the data flow diagram comprises:
Extracting data flow diagram information from the candidate data flow diagram,
The extracted data flow diagram information is information about data transmitted from another process in the candidate data flow diagram, and is used to check the consistency of the candidate data flow diagram. The method of claim 1,
After creating the second instance,
Verifying the consistency of the first instance and the second instance according to a predetermined consistency rule. A diagram providing unit providing at least one state based diagram for a specific application to a state based diagram instance generator and providing a data flow diagram generated based on the at least one state based diagram to a data flow diagram generator;
A state-based diagram instance generation unit for receiving selection feature information and extracting a state corresponding to the selection feature information from the state-based diagram to generate a first instance;
A data flow diagram generator for extracting a process corresponding to the selection feature information from the data flow diagram to generate a second instance; And
A source code generator configured to generate first source code using a state of the first instance and generate second source code using a process of the second instance;
The diagram providing unit,
Receiving a candidate state-based diagram, a candidate data flow diagram, and a feature model, and providing the state-based diagram instance generated by applying the feature of the feature model to the candidate state-based diagram to the state-based diagram instance generator;
And providing the data flow diagram generated by applying the feature of the feature model to the candidate data flow diagram to the data flow diagram instance generator. The method of claim 9, wherein the first source code,
Is generated by extracting a first class corresponding to each state included in the first instance,
The first class is an application generating device, characterized in that composed of at least one method included in the script of the state. The method of claim 10, wherein the at least one method included in the first class includes:
App generating device, characterized in that for calling at least one method included in the first class. The method of claim 9, wherein the second source code,
Is generated by extracting a second class corresponding to each process included in the second instance,
And wherein the second class comprises at least one method included in a script of the process. delete The method of claim 9, wherein the diagram providing unit,
Extracting first diagram information from the candidate state based diagram, extracting second diagram information from the candidate data flow based diagram,
And extracting the first diagram information and the second diagram information, respectively, to check the consistency of the candidate state-based diagram and the candidate data flow diagram. The method of claim 14, wherein the first diagram information,
And information about a state transition used to transition from one state to another state of the candidate state based diagram. The method of claim 14, wherein the second diagram information,
And information about data transmitted from the process of the candidate data flow diagram to another process. The method of claim 9,
And a verification unit which verifies the consistency of the first instance and the second instance according to a predetermined consistency rule.

Images