JP2007156761A - Design information generation device, program development system, design information generation method, program development method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To generate design information with stereotype information from a source code and reduce a transplant term of a source code with functional improvement between different platforms. <P>SOLUTION: A source code analysis section analyzes a source code, extracts information about a class, information about a relation between classes, and information about a variable, and stores them in a class storage processing section, a relation storage processing section and, a variable storage processing section. A stereotype information providing section generates information on stereotype according to a conversion rule based on information stored in the class storage processing section and the related storage processing section, associates them with the information about the class in the class storage processing section to store. A class figure creation section uses information about the class given information on stereotype, information about relations between classes, and information about a variable as design information of a program and creates a class figure corresponding to this design information. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a design information generation apparatus that generates design information of a program from source code using a computer, a program development system using the design information generation apparatus, a design information generation method, and a program.

  As a method for porting source code of a system on a certain platform (legacy system) to source code of a system on another platform, there is conventionally a technique using a cross compiler as disclosed in Patent Document 1. However, when such a method is used, it is not possible to flexibly respond to customization requests such as function expansion and function addition that are likely to occur during porting. Therefore, at present, it is a mainstream to manually analyze the source code of the legacy system and extract design information, and then perform the porting work, which requires a long development period.

By the way, MDA (Model Driven Architecture) attracts attention as a program development technique. MDA is a development method that does not depend on a platform (a specific programming environment), models an application function using a standard modeling technique such as UML, and further automatically generates source code based on the model information. In MDA, a business process is first analyzed in a manner independent of mounting technology, and a platform independent model (PIM) is created. Subsequently, a PSM (Platform Specific Model) that is a model specialized for an individual platform is generated using a tool called a model compiler based on the PIM. Furthermore, the PIM or PSM information is converted into actual source code using a source code generation tool, and the mounting work proceeds.
JP-A-5-88908

  However, even in the MDA development method, porting of source code between different platforms still depends on manpower. That is, although MDA enables one-way generation (conversion) from PSM to source code, a mechanism for generating PSM from the opposite source code is not realized.

  Therefore, in view of such circumstances, the present invention can generate design information to which stereotype information is added from the source code, and can reduce the time required for porting the source code between different platforms. A generation apparatus, a program development system, a design information generation method, a program development method, and a program are provided.

  In order to solve the above-described problems, a design information generation apparatus according to the present invention analyzes a source code to extract information on classes, information on relationships between classes, and information on variables, and the source A class storage processing unit that stores information on the class extracted by the code analysis unit in a class storage area, and a relationship storage process that stores information on the relationship between the classes extracted by the source code analysis unit in the relation storage area A variable storage processing unit for storing information about the variable extracted by the source code analysis unit in a variable storage area, and a class based on information stored in the class storage area and the relation storage area, respectively. Conversion rule storage unit storing conversion rules for generating stereotype information to be given Generating stereotype information according to the conversion rules stored in the conversion rule storage unit based on the information stored in the class storage area and the relation storage area, respectively. A stereotype information assigning unit for storing the information in association with each other, information on the class stored in the class storage area and provided with the stereotype information, information on the relationship between the classes stored in the relation storage area, and A class diagram creating unit that creates information about the variables stored in the variable storage area as program design information and creates a class diagram corresponding to the design information.

  According to the present invention, design information in which stereotype information is assigned to a class can be generated from the source code. Also, a class diagram can be created from the generated design information and posted to a designer, for example.

  The design information generation apparatus of the present invention corrects stereotype information stored in the class storage area based on an input from a designer who refers to the class diagram created by the class diagram creation unit. It may further comprise a model correction unit.

  According to another aspect of the present invention, there is provided a program development system for converting the design information generation apparatus described above and design information of the program generated by the design information generation apparatus into design information independent of a platform. A first model compiler, a second model compiler that converts a result customized by the designer to design information obtained by the first model compiler into design information that depends on a specific platform, and the second model compiler. A source code generation unit that generates source code from design information dependent on a specific platform obtained by the model compiler.

  According to the present invention, when source code is transplanted between different platforms, necessary customization can be performed at the level of design information that does not depend on the platform. Shortening can be achieved.

  ADVANTAGE OF THE INVENTION According to this invention, the design information to which the stereotype information was provided from the source code can be produced | generated, and the shortening of the construction period of the source code between different platforms can be aimed at.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram showing a configuration of a program development system that employs a design information generation apparatus according to an embodiment of the present invention.

  The design information generation apparatus and the program development system of the present embodiment include, for example, a central processing unit (CPU) that executes a program, a read only memory (ROM), and a RAM (main memory that stores a program and data being executed). Random Access Memory), a memory storage device for storing programs and data, a storage device such as a hard disk drive, an input device such as a keyboard and a mouse, and a display device, or such a computer, This is realized by a server / client system network system configured by a plurality of organic connections through communication lines. Hereinafter, the term “unit” such as a generation unit means a function realized by a CPU executing a specific part of a program. The term “storage area” such as “class storage area” means a storage area secured in a storage device such as a memory storage device or a hard disk drive. Also, “files” such as “conversion rule definition file” are stored in a storage device such as a hard disk drive, and are loaded into the memory storage device as needed to be accessed by the CPU.

  As shown in FIG. 1, the program development system 100 of this embodiment does not depend on a platform (specific programming environment), models a function of an application using a standard modeling technique such as UML, and further stores the model information. It is composed of an MDA 200 (MDA: Model Driven Architecture) which is a development method for automatically generating source code based on the design information generating apparatus 300.

  The MDA 200 first analyzes the business process in a manner independent of the mounting technology and creates design information (hereinafter referred to as “PIM”) 11 (PIM: Platform Independent Model) 11 that is a platform-independent model. Based on this, the model compiler 12 converts the information into design information (hereinafter referred to as “PSM”) 13 (PSM: Platform Specific Model) 13 that is specialized for an individual platform. Is generated.

  The model compiler 12 includes a PIM / PSM conversion unit 12a corresponding to the second model compiler having the configuration of the present invention and a PSM / PIM conversion unit 12b corresponding to the first model compiler having the configuration of the present invention. The PIM / PSM conversion unit 12a, which is a second model compiler, has a function of converting the PIM 11 into the PSM 13. The PSM / PIM conversion unit 12b, which is the first model compiler, has a function of converting the PSMs 13 and 14 into the PIM 11. That is, the conversion from the PIM 11 to the PSM 13 in the MDA 200 is performed using the PIM / PSM conversion unit 12a of the model compiler 12.

  The design information generation apparatus 300 includes a model extraction apparatus 16 that is a main part of the design information generation apparatus 300, a source code 17 specialized for a specific platform that is an input to the model extraction apparatus 16, a conversion rule definition file 18, and a model extraction apparatus 16. It consists of PSM14 which is a product.

  The model extraction device 16 is a device that generates a PSM 14 that is program design information from a source code 17 specialized for a specific platform, using a conversion rule definition file 18. The generated PSM 14 is converted into the PIM 11 by the PSM / PIM conversion unit 12b of the model compiler 12.

  FIG. 2 is a data flow and functional blocks for explaining the configuration of the model extraction device 16.

  The model extraction device 16 includes a source code analysis unit 21, a class storage processing unit 22, a relation storage processing unit 23, a variable storage processing unit 24, a stereotype information addition unit 25, and a class diagram creation unit 26 as information processing units. . The model extraction device 16 also has a class storage area 27, a relation storage area 28, and a variable storage area 29 as storage areas used for model extraction processing.

  The source code analysis unit 21 reads and analyzes the source code 17, extracts information on classes, relationships between classes, and information on variables, and stores a class storage processing unit 22, a relationship storage processing unit 23, and a variable storage processing unit 24. To output this information. The class storage processing unit 22 performs writing, reading, and searching for the class storage area 27. The relation storage processing unit 23 writes, reads, and searches the relation storage area 28. The variable storage processing unit 24 performs writing, reading, and searching for the variable storage area 29.

  The stereotype information adding unit 25 adds to the class information stored in the class storage area 27 based on the information stored in the class storage area 27 and the relation storage area 28 and the conversion rule of the conversion rule definition file 18. Generate stereotype information.

  The class diagram creation unit 26 creates a PSM class diagram based on the information stored in the class storage area 27, the relationship storage area 28, and the variable storage area 29, and displays it on the display 30 for the user 31. To do.

  Next, the configuration of information stored in the class storage area 27, the relation storage area 28, and the variable storage area 29, which are storage areas used for model extraction processing, will be described.

  FIG. 3 is a diagram showing a configuration of information related to classes stored in the class storage area 27. As shown in the figure, the information on the class stored in the class storage area 27 includes items of class ID, class name, and stereotype. Here, the class ID is information for identifying all classes appearing in the source code. The class name is the name (name) of each class identified by the class ID. A stereotype is one of the functions of UML, and is information used to modify the role of a class, a difference in usage, and the like into model elements. Differences in class roles and usage can occur in the same model element, so such differences can be represented by stereotypes.

  FIG. 4 is a diagram showing the configuration of information related to the relationship between classes stored in the relationship storage area 28. As shown in the figure, the information related to the relationship between classes stored in the relationship storage area 28 includes a client class ID, a supplier class ID, and a relationship item. Here, the relationship is a relationship between two classes indicated by the client class ID and the supplier class ID. Types of relationships include 'relationship', 'aggregation', 'dependence', 'inheritance', and 'realization'. The client class is a class that sends a message, and the supplier class is a class that receives a message.

  FIG. 5 is a diagram showing a configuration of information regarding variables stored in the variable storage area 29. As shown in the figure, the information related to the variable stored in the variable storage area 29 includes the class ID of the class to which the field variable belongs, the field variable name, and the class ID of the field variable class. Here, the variable is a field variable of the class.

  Next, the conversion rule of the conversion rule definition file 18 will be described.

FIG. 6 shows a table summarizing the conversion rules. In this way, conversion rules include
Rule 1: If the class to be processed is “ActionListener” and is stored in the supplier class ID of the relationship storage area 28 and the relationship is “realization”, the stereo of << Controller >> is set as the class of the client ID Give type. The stereotype is recorded in the class storage area 27.

  Rule 2: If the class to be processed is 'JFrame' and is stored in the supplier class ID of the relationship storage area 28, and the relationship is 'inherit', the stereo of << View >> as the class of the client ID Give type. The stereotype is stored in the class storage area 27.

  Rule 3: If the class to be processed is stored in the supplier class ID of the relation storage area and the relation is 'realization', the stereotype << interface >> is assigned to the class to be processed. The stereotype is stored in the class storage area 27.

  Rule 4: If the class to be processed is included in a package beginning with java and javax, the stereotype is not attached to the class to be processed.

  Rule 5: If the class to be processed does not correspond to any of the rules 1 to 4 and the stereotype is not attached, the stereotype << Model >> is assigned to the class to be processed. The stereotype is stored in the class storage area.

  Next, the operation of the design information generation apparatus 300 according to this embodiment will be described.

  FIG. 7 is a sequence diagram showing the overall operation of the design information generation apparatus 300 of this embodiment.

  1: The user 31 instructs the source code analysis unit 21 to model the source code 17 using an input device (not shown).

  2: The source code analysis unit 21 analyzes the source code 17 in accordance with this instruction, extracts information on classes, relationships, and variables, and stores them in the class storage processing unit 22, the relationship storage processing unit 23, and the variable storage processing unit 24. I give it. The class storage processing unit 22, the relationship storage processing unit 23, and the variable storage processing unit 24 store the information received from the source code analysis unit 21 in the class storage area 27, the relationship storage area 28, and the variable storage area 29. The operation at this time will be described later in detail with reference to FIG.

  3: The source code analysis unit 21 instructs the stereotype information giving unit 25 to give stereotype information.

  4: Upon receiving this instruction, the stereotype information adding unit 25 stores the information in the class storage area 27 based on the information stored in the class storage area 27 and the relation storage area 28 and the conversion rules of the conversion rule definition file 18. Stereotype information to be added to the information about the stored class is generated and given. The operation at this time will be described later in detail with reference to FIG.

  5: The stereotype information giving unit 25 instructs the class diagram creating unit 26 to create a class diagram.

  6: The class diagram creation unit 26 creates a PSM class diagram to which stereotype information is added based on the information stored in the class storage area 27, the relation storage area 28, and the variable storage area 29, respectively. . Details of the processing of the class diagram creation unit 26 will be described later.

  7: The class diagram creation unit 26 instructs the display 30 to display the created class diagram.

  8: The display 30 displays the class diagram given by the class diagram creation unit 26.

  Next, details of the operation of the source code analysis will be described.

  FIG. 8 is a sequence diagram relating to the operation of the source code analysis. In order to help understanding of the operation, description will be made on the assumption of specific source code. 9, FIG. 10 and FIG. 11 show excerpts of Java (registered trademark) source code, which is an example of the specific source code. Further, in order to understand the relationship between these source codes and the sequence diagram, the number of the process in the sequence diagram is attached as a code to the line of the source code targeted by each process in the sequence diagram.

  1: The user 31 instructs the source code analysis unit 21 to model the source code 17 using an input device (not shown).

  2: The source code analysis unit 21 reads the source code 17 in accordance with the modeling instruction.

  3: The source code analysis unit 21 reads the class declaration of the read source code 17.

  3.1: The source code analysis unit 21 extracts the name of the class X (class name) from the source code 17 and assigns an ID (class ID) to the class X. Then, the source code analysis unit 21 stores the class name and class ID of the class X in the class storage area 27 through the class storage processing unit 22. In the source code examples of FIGS. 9 to 11, class names such as Counter, CounterListener, and CounterView are extracted, and class IDs are assigned to the class names.

  3.2: The source code analysis unit 21 performs superclass analysis.

  3.2.1: The source code analysis unit 21 extracts the name (class name) of the superclass Y of the class X and assigns an ID (class ID) to the superclass Y. The source code analysis unit 21 stores the class name and class ID of the super class in the class storage area 27 through the class storage processing unit 22. For example, JFrame is extracted as the superclass name of the CounterView class, and a class ID is assigned to it.

  3.2.2: The source code analysis unit 21 stores the class IDs of the class X and the super class Y and the relationship between the classes in the relationship storage area 28 through the relationship storage processing unit 23. In this case, the relationship between classes is uniquely inherited. Here, the class ID of the class X is stored in the relationship storage area 28 as the client class ID, and the class ID of the super class Y is stored as the supplier class ID.

  3.3: The source code analysis unit 21 performs interface analysis.

  3.3.1: The source code analysis unit 21 extracts the name (class name) of the interface Z of class X and assigns an ID (class ID) to the interface Z. The source code analysis unit 21 stores the class name and class ID of the interface Z in the class storage area 27 through the class storage processing unit 22.

  3.3.2: The source code analysis unit 21 stores the class IDs of the class X and the interface Z and the relationship between the classes in the relationship storage area 28 through the relationship storage processing unit 23. The relationship in this case is uniquely realized. Here, the class ID of the class X is stored in the relation storage area 28 as the client class ID, and the class ID of the interface Z is stored as the supplier class ID.

  3.4: The source code analysis unit 21 analyzes the class body of the class declaration.

  3.4.1: The source code analysis unit 21 analyzes a field (each line 3.4.1 in FIGS. 9 to 11) from the analysis result of the class body of the class declaration.

  3.4.1.1: The source code analysis unit 21 extracts the name (class name) of the class W of the field variable from the analysis result of the field and assigns an ID (class ID) to the class W. Then, the source code analysis unit 21 stores the class name and class ID of the class W of the field variable in the class storage area 27 through the class storage processing unit 22.

  3.4.1.2: The source code analysis unit 21 sends the variable name a of the field variable, the class ID of the class W of the field variable, and the ID of the belonging class X to the variable storage area 29 through the variable storage processing unit 24 as information about the variable. Remember.

  3.4.1.3: The source code analysis unit 21 stores the class IDs of the belonging class X and the field variable class W and the relationship between the classes in the relationship storage area 28 through the relationship storage processing unit 23. The relationship in this case is uniquely aggregated.

  3.4.2: The source code analysis unit 21 analyzes the method declaration.

3.4.2.1: The source code analysis unit 21 extracts the name (class name) of the result type class U and assigns an ID (class ID) to the class U. Then, the source code analysis unit 21 stores the class name and class ID of the result type class U in the class storage area 27 through the class storage processing unit 22.

  3.4.2.2: The source code analysis unit 21 stores the class ID of the result type class U and the belonging class X and the relationship thereof in the relationship storage area 28 through the relationship storage processing unit 23. The relationship in this case is uniquely dependent. Here, the class ID of the result type class U is stored in the relationship storage area 28 as the client class ID, and the class ID of the belonging class X is stored as the supplier class ID.

  3.4.3: The source code analysis unit 21 analyzes the method body.

  3.4.3.1: The source code analysis unit 21 extracts the name (class name) of the class V of the local variable used in the block from the analysis result of the method body, and also assigns an ID (class ID) to the class V of the local variable. ). Then, the source code analysis unit 21 stores the class name and class ID of the class V of the local variable in the class storage area 27 through the class storage processing unit 22.

  3.4.3.2: The source code analysis unit 21 stores the IDs of the belonging class X and the local variable class V and the relationship between the classes in the relationship storage area 28 through the relationship storage processing unit 23. The relationship in this case is uniquely dependent. Here, the class ID of the local variable class V is stored in the relation storage area 28 as the client class ID and the class ID of the belonging class X is stored as the supplier class ID.

  As described above, the information obtained by analyzing the source code 17 is stored in the class storage area 27, the relation storage area 28, and the variable storage area 29, respectively.

  FIG. 12 is an example of information on classes stored in the class storage area 27 from the source code 17 including the source codes of FIGS. 9 to 11 by the above analysis. In this way, the class IDs and class names of all classes described in the source code 17 are stored in the class storage area 27. All items of stereotype information are blank.

  FIG. 13 also shows an example of information related to the relationship between classes stored in the relationship storage area 28 from the source code 17 by the above analysis. In this way, the relationships (relationship, aggregation, dependence, inheritance, realization, etc.) between all classes described in the source code 17 are stored in the relationship storage area 28.

  FIG. 14 also shows an example of information relating to field variables stored in the variable storage area 29 by the above analysis from the source code 17. In this way, all field variables and the like described in the source code 17 are stored in the relation storage area 28.

  Next, details of the operation relating to the provision of stereotype information will be described.

  FIG. 15 is a sequence diagram relating to the operation of adding stereotype information.

  1: The stereotype information adding unit 25 receives an instruction to add stereotype information from the source code analyzing unit 21.

  1.1: Upon receiving this stereotype information addition instruction, the stereotype information addition unit 25 reads the conversion rule definition file 18.

  1.2: Stereotype information assigning unit 25 assigns stereo to all classes stored in class storage area 27 (FIG. 12) in accordance with the conversion rules (FIG. 6) described in conversion rule definition file 18 that has been read. Processing for determining type information is started.

  1.2.1: First, the stereotype information giving unit 25 reads the correspondence relationship between the class IDs and class names of all classes stored in the class storage area 27.

  1.2.2: Stereotype information giving unit 25 is a combination of client class ID and supplier class ID, which is a combination of all related classes stored in relation storage area 28 (FIG. 13), and these classes. Read the relationship between.

  1.2.3: The stereotype information giving unit 25 reads the conversion rule, the correspondence between the class ID and the class name, the combination of the related classes and the class to which the stereotype information is given based on the relation. And stereotype information to be given.

  1.2.3.1: The stereotype information adding unit 25 stores the determined stereotype information in the class storage area 27 in association with the corresponding class.

  1.3: The stereotype information giving unit 25 instructs the class diagram creating unit 26 to create a class diagram when all the stereotype information has been given to the necessary classes.

  FIG. 16 is a diagram showing a result of adding stereotype information to the class storage area 27. Here, how the stereotype information shown in the figure is specifically determined will be described.

  The stereotype << View >> assigned to the class in the first row of the class storage area 27 is based on rule 2 in the conversion rules shown in FIG. The information stored in the relationship storage area 28 that matches the rule 2 condition is the information on the first line. Based on the action of the rule 2, the class of CounterView class 0 is << The View >> stereotype is assigned.

  The stereotype << Model >> assigned to the class in the third row of the class storage area 27 is based on the rule 5 in the conversion rules shown in FIG.

  The stereotype << Controller >> assigned to the class in the ninth line of the class storage area 27 is based on the rule 1 in the conversion rules shown in FIG.

  The stereotype << interface >> assigned to the class in the 10th line of the class storage area 27 is based on the rule 3 in the conversion rule shown in FIG. The information stored in the relation storage area 28 that matches the rule 3 condition is the information on the 9th line. Based on the action of the rule 3, the class of ActionListener with class ID 9 is << interface>. Stereotype information of> is added.

  Further, stereotype information is not given to the classes in the second, fourth to eighth, and eleventh lines of the class storage area 27. This is a result based on rule 4 in the conversion rules shown in FIG.

  Next, class diagram creation / display processing by the class diagram creation unit 26 will be described.

  FIG. 17 is a sequence diagram relating to the creation / display processing of this class diagram.

  1: An instruction to create a class diagram is given from the stereotype information adding unit 25 to the class diagram creating unit 26.

  1.1: Upon receiving an instruction to create a class diagram from the stereotype information adding unit 25, the class diagram creating unit 26 reads the class name and stereotype information for each class ID from the class storage area 27.

  1.2: The class diagram creation unit 26 reads the field variable name for each class ID from the variable storage area 29.

  1.3: The class diagram creating unit 26 creates a class diagram excluding the relationship line between classes from the class name, stereotype information, and field variable name read up to here.

  1.3.1: The class diagram creation unit 26 instructs the display 30 to display a class diagram excluding the created relationship lines between classes.

  2: Subsequently, the class diagram creating unit 26 reads the related class ID combination (client class ID and supplier class ID) and the relationship from the relationship storage area 28.

  3: The class diagram creation unit 26 reads the class name corresponding to the class ID (client class ID and supplier class ID) read from the relation storage area 28 from the class storage area 27.

  4: The class diagram creation unit 26 creates a relationship line between classes based on the information read in 2: and 3 :.

  4.1: The class diagram creation unit 26 instructs the display 30 to display the created relationship lines between classes.

  FIG. 18 is an example of the created class diagram.

  Here, (7-1) to (7-11) are classes, and (7-12) to (7-21) are relationship lines. Class notation consists of upper, middle and lower levels. For example, taking the ActionListener class (7-10) as an example, reference numeral 33 is the upper stage, 34 is the middle stage, and 35 is the lower stage. In the upper part, the class name and stereotype are described, and the stereotype is described above the class name. Field variables (attributes) are described in the middle (not shown in the figure). The lower part describes the method (operation) (omitted in the figure). The relationship line between classes represents the type of relationship by the line type and the shape of the end.

  FIG. 19 shows the correspondence between the class in the class diagram of FIG. 18 and the information in the class storage area 27, and FIG. 20 shows the correspondence between the relation line in the class diagram of FIG. 18 and the information in the relation storage area 28. .

  As described above, according to the design information generation apparatus 300 of this embodiment, design information in which stereotype information is assigned to a class can be generated from the source code 17 specialized for a specific platform. In addition, a class diagram can be created from the generated design information and posted to the designer. Furthermore, according to the program development system 100 of the present embodiment, when source code is ported between different platforms, necessary customization can be performed at the level of design information that does not depend on the platform. Can shorten the source code porting period.

  Next, it is a data flow and functional block for demonstrating the structure of the model extraction apparatus 116 in the design information generation apparatus which is the 2nd Embodiment of this invention.

  FIG. 21 is a data flow and functional blocks for explaining the configuration of the model extraction device 116 in the design information generation device according to the second embodiment.

  The model extraction device 116 in this embodiment is obtained by adding a model correction unit 41 to the model extraction device 16 of the first embodiment shown in FIG.

  The model correction unit 41 receives a correction command input through the input unit from the user 31 referring to the class diagram displayed on the display 30 by the class diagram creation unit 26, and sends the correction contents to the class storage processing unit 22 and the relationship. This is means for reflecting the information in the class storage area 27, the relation storage area 28, and the variable storage area 29 through the storage processing section 23 and the variable storage processing section 24. The correction contents of the class storage area 27, the relation storage area 28, and the variable storage area 29 are reflected on the class diagram displayed on the display 30 by the class diagram creation unit 26.

  FIG. 22 is a diagram showing a correction example of the class diagram of FIG. In this correction example, only << Model >> is assigned as the stereotype to the Counter class of (7-3), but in addition to the stereotype of << Service >> as determined by the user 31 The result of giving information is shown.

  It should be noted that the present invention is not limited to the above-described embodiment, and it is needless to say that various updates can be added without departing from the gist of the present invention.

The figure which shows the structure of the program development system which employ | adopted the design information generation apparatus concerning one Embodiment of this invention. The data flow and functional block diagram for demonstrating the structure of the model extraction apparatus which is the principal part of the design information generation apparatus of FIG. The figure which shows the structure of the information regarding the class memorize | stored in a class storage area. The figure which shows the structure of the information regarding the relationship between the classes memorize | stored in a relationship storage area. The figure which shows the structure of the information regarding the variable memorize | stored in a variable memory area. A chart showing the contents of a conversion rule definition file. FIG. 3 is a sequence diagram illustrating an overall operation of the design information generation apparatus in FIG. 2. FIG. 8 is a sequence diagram relating to the operation of source code analysis in FIG. 7. The figure which shows the example of a source code. The figure which shows the example of a source code. The figure which shows the example of a source code. The figure which shows the specific example of the information regarding the class memorize | stored in the class storage area. The figure which shows the specific example of the information regarding the relationship between the classes memorize | stored in the relationship memory area. The figure which shows the specific example of the information regarding the field variable memorize | stored in the variable memory area. The sequence diagram regarding the operation | movement of provision of stereotype information. The figure which shows the result as which the stereotype information was provided to the class storage area. The sequence diagram regarding creation / display processing of a class diagram. The figure which shows the example of the created class diagram. The figure which shows the correspondence of the class of FIG. 18, and the information of a class storage area. The figure which shows the correspondence of the relationship line in the class diagram of FIG. 18, and the information of a relationship storage area. The data flow and functional block diagram for demonstrating the structure of the model extraction apparatus in the design information generation apparatus which is 2nd Embodiment. The figure which shows the correction example of the class diagram of FIG.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 12 ... Model compiler, 12a ... PIM / PSM conversion part, 12b ... PSM / PIM conversion part, 16 ... Model extraction apparatus, 18 ... Conversion rule definition file, 19 ... Source code generation part, 21 ... Source code analysis part, 22 ... Class storage processing unit, 23... Relationship storage processing unit, 24... Variable storage processing unit, 25... Stereotype information adding unit, 26. Area 41... Model correction unit 100 100 program development system 116 model extraction device 300 design information generation device

Claims (8)

A source code analysis unit that analyzes source code and extracts information about classes, information about relationships between classes, and information about variables,
A class storage processing unit that stores information on the class extracted by the source code analysis unit in a class storage area;
A relationship storage processing unit that stores information on the relationship between the classes extracted by the source code analysis unit in a relationship storage area;
A variable storage processing unit that stores information on the variable extracted by the source code analysis unit in a variable storage area;
A conversion rule storage unit that stores conversion rules for generating stereotype information to be given to a class based on information stored in the class storage area and the relation storage area;
Generating stereotype information according to the conversion rules stored in the conversion rule storage unit, and storing the stereotype information in association with the class storage area information related to the class;
Information related to the class stored in the class storage area and provided with the stereotype information, information related to the relationship between the classes stored in the relation storage area, and information related to the variable stored in the variable storage area And a class diagram creation unit for creating a class diagram corresponding to the design information.   The apparatus further comprises a model correction unit for correcting stereotype information stored in the class storage area based on an input from a designer referring to the class diagram created by the class diagram creation unit. The design information generating apparatus according to claim 1. A design information generating apparatus according to claim 1;
A first model compiler that converts design information of the program generated by the design information generation device into platform-independent design information;
A second model compiler that converts a result customized by the designer with respect to the design information obtained by the first model compiler into design information that depends on a specific platform;
A program development system comprising: a source code generation unit configured to generate a source code from design information dependent on a specific platform obtained by the second model compiler. A step of analyzing the source code by the source code analysis unit to extract information on classes, information on relationships between classes, and information on variables;
Storing information on the class extracted by the source code analysis unit in a class storage area;
Storing information on the relationship between the classes extracted by the source code analysis unit in a relationship storage area;
Storing information on the variable extracted by the source code analysis unit in a variable storage area;
The stereotype information adding unit generates stereotype information according to a predetermined conversion rule based on information stored in the class storage area and the relation storage area, and relates to the class in the class storage area. Storing in association with information;
In the class diagram creation unit, information on the class stored in the class storage area and provided with the stereotype information, information on the relationship between the classes stored in the relation storage area, and the variable storage area And a step of creating a class diagram corresponding to the design information using the information on the variables stored in the program as design information of the program.   The model correction unit further includes a step of correcting stereotype information stored in the class storage area based on an input from a designer who refers to the class diagram created by the class diagram creation unit. The design information generation method according to claim 4, wherein: Converting the design information of the program generated by the design information generation method of claim 4 into design information independent of a platform by a first model compiler;
Converting a result customized by a designer with respect to the design information obtained by the first model compiler into design information depending on a specific platform by the second model compiler;
Generating a source code from design information depending on a specific platform obtained by the second model compiler in a source code generation unit. Computer
A source code analysis unit that analyzes the source code and extracts information about classes, information about relationships between classes, and information about variables,
A class storage processing unit that stores information on the class extracted by the source code analysis unit in a class storage area;
A relationship storage processing unit that stores information on the relationship between the classes extracted by the source code analysis unit in a relationship storage area;
A variable storage processing unit that stores information on the variable extracted by the source code analysis unit in a variable storage area;
A conversion rule storage unit that stores conversion rules for generating stereotype information to be given to a class based on information stored in the class storage area and the relation storage area;
Generate stereotype information according to the conversion rules stored in the conversion rule storage unit based on the information stored in the class storage area and the relation storage area, and correspond to the information about the class in the class storage area A stereotype information adding unit for storing information;
Information related to the class stored in the class storage area and provided with the stereotype information, information related to the relationship between the classes stored in the relation storage area, and information related to the variable stored in the variable storage area The program is made to function as a class diagram creation unit that creates a class diagram corresponding to the design information.   The computer also functions as a model correction unit that corrects stereotype information stored in the class storage area based on an input from a designer who refers to the class diagram created by the class diagram creation unit. The program according to claim 7, wherein:

Images