JP2007200125A - Coding agreement selection program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a coding protocol selection program capable of properly selecting a coding protocol applied to a source code of an application. <P>SOLUTION: This coding protocol selection program makes a computer execute: a file configuration decision procedure for deciding the kind of the application on the basis of a file configuration of a project defined as development environment of the application; a project kind decision procedure (S201) for deciding the kind of the application on the basis of the kind of the project; and an application protocol decision means deciding the coding protocol applied to the source code of the application on the basis of a protocol correspondence information defined with the coding protocol applied to the source code of the application according to the kind of the application, and the kind of the application specified by at least one decision result in the file configuration decision procedure and the project kind decision procedure. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a coding rule selection program, and more particularly to a coding rule selection program for determining a coding rule to be applied to source code created in an application development environment.

  When developing a program, coding conventions are often defined within a development project. As each developer performs coding in accordance with the coding standards, a uniform source code is created as a whole, and improvement of program maintainability is expected. However, simply defining coding rules does not guarantee that each source code is created according to the rules. Therefore, conventionally, software for checking whether the source code conforms to the coding standard has been provided.

On the other hand, in recent years, the types of applications such as client applications, libraries, applets, Web services, Web applications, and EJB (registered trademark) (Enterprise JavaBeans (registered trademark)) are abundant in accordance with the development of the Internet and the like. It has become a thing. Coding restrictions may differ depending on the type of application. In view of this point, it is desirable that the coding rules are determined and checked according to the type of application.
Japanese Patent Laid-Open No. 08-101771

  However, conventionally, software that checks coding standards has often existed as a separate product from software that provides a software development environment (software that supports coding, compilation, linking, and the like). In that case, in order to check the coding conventions for the source code described in the development environment, the coding convention check software is started separately from the development environment, and the source code storage location and application The user has to input information such as type.

  In addition, some check software is called from the development environment and automatically starts, but the development environment simply passes the storage location of the source code, etc. I had to judge.

  The present invention has been made in view of the above points, and an object thereof is to provide a coding rule selection program capable of appropriately selecting a coding rule to be applied to an application source code.

  In order to solve the above problems, the present invention provides a computer based on a file configuration determination procedure for determining the type of the application based on the file configuration of the project defined as an application development environment, and on the type of the project. A project type determination procedure for determining the type of the application; a rule correspondence information in which a coding rule applied to the source code of the application is defined according to the application type; the file configuration determination procedure; and the project type determination. Based on at least one of the determination results in the procedure, the application rule determination procedure for determining the coding rule applied to the source code of the application is executed. And wherein the door.

  In such a coding rule selection program, it is possible to appropriately select a coding rule to be applied to the application source code.

  ADVANTAGE OF THE INVENTION According to this invention, the coding rule selection program which can select appropriately the coding rule applied to the source code of an application can be provided.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a hardware configuration example of a software development support apparatus according to an embodiment of the present invention.

  The software development support device 10 of FIG. 1 includes a drive device 100, an auxiliary storage device 102, a memory device 103, an arithmetic processing device 104, a display device 105, and an input device 106 that are mutually connected by a bus B. And so on.

  A program for realizing processing in the software development support apparatus 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 on which the program is recorded is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. The auxiliary storage device 102 stores the installed program and various data necessary for processing the program.

  The memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The arithmetic processing device 104 executes functions related to the software development support device 10 in accordance with a program stored in the memory device 103. The display device 105 displays a GUI (Graphical User Interface) or the like by a program. The input device 106 includes a keyboard and a mouse, and is used for inputting various operation instructions.

  FIG. 2 is a diagram illustrating a functional configuration example of the software development support apparatus according to the embodiment of the present invention.

  In FIG. 2, the software development support apparatus 10 includes a development environment providing unit 11 and various build tools 12.

  The development environment providing unit 11 is software for providing an application development environment. For example, the development environment providing unit 11 provides an integrated environment for supporting application design, coding, debugging, testing, and the like by a user-friendly GUI. The development environment providing unit 11 manages the development environment of the application to be created in units of “projects”. When creating an application, the user defines a project as a development environment of the application using the development environment providing unit 11 and edits the source code and the like in the project. In the present embodiment, information necessary for building an application created in a project is referred to as a project asset 111.

  The project asset 111 includes, for example, a source file and various definition files (for example, a file in which a correspondence relationship between files is defined, a make file, etc.). The build refers to generating an execution code of an application based on the project asset 111, and generally refers to processing including processes such as compiling and linking.

  The build tool 12 is a tool (program) such as a compiler for building an application based on the project asset 111. In the present embodiment, a rule check tool 12c is included as one of the build tools. The rule check tool 12c is a tool for checking whether or not the source code of the application conforms to a predetermined coding rule (also referred to as “coding rule”).

  FIG. 3 is a diagram illustrating a functional configuration example of the convention check tool according to the embodiment of the present invention. In FIG. 3, the rule check tool 12 c is mainly composed of a rule selection unit 121 and a rule check unit 122.

  Based on the project asset 111, the contract selection unit 121 determines the type of application (application type) targeted in the project, and selects a coding contract corresponding to the application type. The rule selection unit 121 includes a source file extraction unit 1211, an application type determination unit 1212, an application rule determination unit 1213, a rule correspondence information management table 1214, a check target output unit 1215, and the like.

  The source file extraction unit 1211 extracts from the project asset 111 a list of source files 1110 in which source codes to be checked for coding rules are stored. The application type determination unit 1212 inspects the project asset 111 and determines the application type of the application targeted in the project.

  The application rule determination unit 1213 selects a coding rule 1210 corresponding to the application type based on the application type determined by the application type determination unit 1212 and the rule correspondence information management table 1214. The rule correspondence information management table 1214 is a table in which the correspondence between application types and coding rules is managed, and coding rules to be applied for each application type are defined. Therefore, the application rule determination unit 1213 determines the coding rule 1210 to be applied to the source file 1110 by searching the rule correspondence information management table 1214 using the application type as a key.

  The check target output unit 1215 outputs the list of source files 1110 extracted from the source file extraction unit 1211 or the application rule determination unit 1213 and the coding rule 1210 to the rule check unit 122.

  The rule checking unit 122 checks whether the source code stored in the source file 1110 conforms to the coding rule 1210. Note that the checking process by the rule checking unit 122 is not limited to a predetermined one, and a known one may be used. Therefore, the description format of the coding convention 1210 is not limited to a predetermined one.

  Next, details of the application type determination unit 1212 will be described. FIG. 4 is a diagram illustrating a functional configuration example of the application type determination unit. 4, the application type determination unit 1212 includes a project type determination unit 1212a, a configuration file determination unit 1212b, a configuration file content determination unit 1212c, a build tool determination unit 1212d, and an application type specification unit 1212e.

  As shown in FIG. 4, the project asset 111 includes a project information table 1111 as a part thereof. The project information table 1111 is a table that holds information such as the project type 1111a, configuration file information 1111b, and build tool information 1111c. The project type 1111a is a type of project classified according to the application type targeted by the project, and is automatically based on information indicating what kind of application is scheduled to be created when the project is created. Selected. The configuration file information 1111b is information on files that constitute the project. The build tool information 1111c refers to information related to the build method of the project, and holds information for identifying the build tool 12 used in each build process, for example, in a table format.

  The application type determination unit 1212 determines the application type of the project based on the project asset 111 configured as described above. That is, the project type determination unit 1212a determines the application type based on the project type in the project information table 1111. The configuration file determination unit 1212b determines the application type based on the file configuration of the project. The configuration file content determination unit 1212c determines the application type by analyzing the content of the source file that is a part of the configuration file. The build tool determination unit 1212d determines the application type based on the build tool used by the project. The application type identification unit 1212e identifies the application type based on the determination results of the project type determination unit 1212a, the configuration file determination unit 1212b, the configuration file content determination unit 1212c, the build tool determination unit 1212d, and the like. The application type specified by the application type specifying unit 1212e is output as the determination result of the application type determining unit 1212.

  The processing procedure of the software development support apparatus 10 will be described below. FIG. 5 is a flowchart for explaining a processing procedure at the time of building by the development environment providing unit.

  When the start of the build is instructed by the user via the GUI (for example, menu etc.) of the development environment providing unit 11, the development environment providing unit 11 is in the order defined in the build tool information 1111c in the project asset 111. The build tool 12 is called (S101 to S104). The called build tool executes processing according to the build tool. This builds the application. The build tool 12 that is not essential for building an application can be added to or deleted from the project as desired by the user. Therefore, when the rule check tool 12c is added to the project, the rule check tool 12 process is executed in a series of processes in the build. That is, the software development support apparatus 10 according to the present embodiment executes the coding rule check work as one process of the build work. Therefore, the user does not need to perform both operations separately.

  Next, the processing procedure of the rule check tool 12c in FIG. 3 will be described. FIG. 6 is a flowchart for explaining the processing procedure of the convention check tool. The processing in FIG. 6 is executed when the contract check tool 12c is called from the development environment providing unit 11 in step S104 in FIG.

  First, the application type determination unit 1212 determines the application type based on the project asset 111 (S201). Subsequently, the application rule determination unit 1213 determines the coding rule 1210 corresponding to the application type based on the application type determined by the application type determination unit 1212 and the rule correspondence information management table 1214 (S202).

  FIG. 7 is a diagram illustrating a configuration example of the convention correspondence information management table.

  In FIG. 7, in the rule correspondence information management table 1214, a rule to be applied (coding rule) is set for each application type. For example, according to FIG. 7, when the application type is EJB (registered trademark) (Enterprise JavaBeans (registered trademark)), the rules A, B, D, and G are applied. Further, the rules A, C, D, and G are applied to the Web application (Web application). In FIG. 7, other than EJB (registered trademark) and Web application are classified as “others”, but the application types included in “others” are subdivided, and the rules to be applied for each subdivided application type May be defined.

  Subsequently, the source file extraction unit 1211 extracts a list of source files 1110 from the project asset 111 (S203). A list of coding conventions 1210 and source files 1110 are output to the convention check unit 122 by the check target output unit 1215. The rule checking unit 122 checks whether the source code of the source file 1110 conforms to the coding rule 1210 (S204).

  Next, details of processing by the application type determination unit 1212 in step S201 will be described. FIG. 8 is a flowchart for explaining the processing procedure of the application type determination process by the application type determination unit.

  First, the build tool determination unit 1212d determines the application type based on the build tool information 1111c (S301). That is, the build tool 12 added to the project is defined in the build tool information 1111c. The application type has a certain degree of correspondence with the build tool used by the project. Therefore, the build tool determination unit 1212d determines the application type based on this correspondence. A plurality of build tools can be added to one project.

  The correspondence relationship between the application type and the build tool may be created in advance as information in a table format as shown in FIG. 9, for example.

  FIG. 9 is a diagram illustrating a configuration example of a table for managing a correspondence relationship between an application type and a build tool.

  In FIG. 9, the table 1212d-1 defines application types that can be related to each build tool. In the example of FIG. 9, it is defined that the Java (registered trademark) compiler can be used for builds of all application types. Further, it is defined that the JavaBeans (registered trademark) information generation tool can be used for building a client application or a library (client / library). Further, it is defined that the Jar package tool can be used for building a client library, an EJB (registered trademark), and a Web service.

  The table for managing the correspondence between the application type and the build tool may be configured as shown in FIG. FIG. 10 is a diagram illustrating a second configuration example of the table for managing the correspondence between the application type and the build tool.

  In FIG. 10, a build tool normally used for each application type is defined in a table 1212d-2. In the example of FIG. 10, a Java (registered trademark) compiler, a JavaBeans (registered trademark) information generation tool, a JavaBeans (registered trademark) manifest generation tool, and a Jar package tool are normally used for building a client application or library. Is defined. In addition, it is defined that a Java (registered trademark) compiler, a JSP (registered trademark) (JavaServer Pages (registered trademark)) compiler, and a WAR package tool are normally used for building a Web application.

  Therefore, the build tool determination unit 1212d determines the application type based on the table 1212d-1 or the table 1212d-2. For example, when a Java (registered trademark) compiler, JSP (registered trademark) compiler, and WAR package are set as a build tool in a project, the application type is uniquely identified as “Web application”. When the application type is uniquely specified, the build tool determining unit 1212d outputs the application type to the application type specifying unit 1212e.

  By the way, the application type may not be uniquely identified based on the build tool. For example, when a Java (registered trademark) compiler, a JSP (registered trademark) compiler, and an EJB (registered trademark) specification inspection tool are set as a build tool in a project, the application type is “EJB (registered trademark)” or “Web There is a possibility of "app". In this case, the build tool determining unit 1212d outputs the plurality of application types to the application type specifying unit 1212e. Further, when only a Java (registered trademark) compiler is set as a build tool in a project, there is a possibility for all application types. In this case, the build tool determination unit 1212d outputs “determination impossible” to the application type identification unit 1212e.

  If the application type can be uniquely identified by the build tool determination unit 1212d (Yes in S302), the application type identification unit 1212e outputs the application type to the application rule determination unit 1213, and ends the process.

  On the other hand, when the build tool determination unit 1212d cannot uniquely identify the application type (No in S302), the configuration file determination unit 1212b determines the application type based on the configuration file information 1111b (S303). That is, the file configuration of the project is defined in the configuration file information 1111b. The application type has a certain degree of correspondence with the file structure of the project (what kind of files are included in the project). Therefore, the configuration file determination unit 1212b determines the application type based on this correspondence.

  FIG. 11 is a diagram illustrating an example of a correspondence relationship between an application type and a file configuration.

  FIG. 11 shows that in the case of EJB (registered trademark), ejb-jar.xml is an essential configuration file. In addition, although it is not essential, there are those that can specify the application type when a specific file is included in the configuration file. For example, in FIG. 11, if web.xml exists, it indicates that it is a Web application.

  Therefore, for example, when based on the correspondence as shown in FIG. 11, when only one of ejb-jar.xml and web.xml is included in the configuration file, the application type is “EJB (registered trademark)”. ”Or“ Web application ”. Therefore, in this case, the configuration file determining unit 1212b outputs the uniquely specified application type to the application type specifying unit 1212e.

  When both ejb-jar.xml and web.xml are included in the configuration file, the configuration file determination unit 1212e uses a plurality of application types (“EJB (registered trademark)” and “Web application”) as applications. The data is output to the type identification unit 1212e.

  When none of the files is included in the configuration file, the configuration file determination unit 1212e outputs “undeterminable” to the application type identification unit 1212e.

  If the application file type can be uniquely identified by the configuration file determination unit 1212b (Yes in S304), the application type identification unit 1212e outputs the application type to the application rule determination unit 1213 and ends the process.

  On the other hand, when the application file type cannot be uniquely identified by the configuration file determination unit 1212b (No in S304), the configuration file content determination unit 1212c determines the application type based on the content of the configuration file (S305). That is, the application type has a certain degree of correspondence with the contents of the configuration file. Therefore, the configuration file content determination unit 1212c determines the application type based on this correspondence.

  Specifically, for example, in the case of EJB (registered trademark), a class that implements the interface javax.ejb.EnterpriseBean is required. Therefore, the configuration file content determination unit 1212c determines the application type by analyzing the content of the source file and examining which interface is implemented and which class is inherited.

  FIG. 12 is a diagram illustrating an example of a correspondence relationship between the application type and the contents of the configuration file.

  According to FIG. 12, when there is a class that inherits the “javax.servlet.http.HttpServlet class”, the determination result of the application type includes “Web application”. When there is a class that implements the “javax.ejb.EnterpriseBean interface”, “EJB (registered trademark)” is included in the determination result of the application type. Further, when there is a class that inherits the “java.awt.Component class”, the determination result of the application type includes “client application”. If none of these are applicable, “determination impossible” is set as the determination result. The determination result by the configuration file content determination unit 1212c is output to the application type identification unit 1212e. Whether or not a class or interface is inherited may be determined based on whether or not a character string indicating that the class or interface is inherited is included in the source code.

  When the application file type can be uniquely identified by the configuration file content determination unit 1212c (Yes in S306), the application type identification unit 1212e outputs the application type to the application rule determination unit 1213, and ends the process.

  On the other hand, if the application type cannot be uniquely identified by the configuration file content determination unit 1212c (No in S306), the project type determination unit 1212a determines the application type based on the project type 1111a (S307). That is, the project type 1212a is information selected by the development environment providing unit 111 based on information indicating what kind of application is scheduled to be created when the project is created. Have a correspondence. Therefore, the project type determination unit 1212a determines the application type based on this correspondence.

  FIG. 13 is a diagram illustrating a correspondence relationship between application types and project types.

  In the example of FIG. 13, an example of application types corresponding to each project type is shown. In the example of FIG. 13, the granularity of the application type is larger than the granularity of the project type. Therefore, in this case, the application type is uniquely determined based on the project type. For example, when the project type is “appletproject”, the application type is determined to be “applet”. When the project type is “soapproject”, the application type is determined to be “Web service”. Therefore, the application type output from the project type determining unit 1212a to the application type specifying unit 1212e is unique, and the application type specifying unit 1212e outputs the application type to the application rule determining unit 1213.

  By the way, if the application type can be uniquely identified according to the project type, it is considered that the application type may be determined based only on the project type. However, in the present embodiment, the case where the correspondence between the project type and the application type is not necessarily guaranteed is also taken into consideration. In other words, the project type is information that is determined at the time of project generation, but the actual application type is information that can be changed by subsequent development work (addition or deletion of build tools, addition or deletion of configuration files, coding, etc.). It is assumed that there is. Therefore, in this embodiment, the application type is determined in the order of the build tool, the file configuration, the contents of the configuration file, and the project type. The order of determination is desirably the order in which the correspondence between the information used for determination and the application type is strong (that is, the order in which the reliability of the information used for determination is high). This is because an application type uniquely determined based on information with low reliability has low reliability. In this embodiment, the case where the reliability is high in the order of the build tool, the file structure, the contents of the configuration file, and the project type is taken as an example, and this order is appropriately changed according to the high reliability. Also good.

  Further, the determination of the application type may not always be performed based on the above four pieces of information. For example, it may be performed based on the file configuration and project type. However, when there is a case where the application type is not uniquely determined based on the file configuration and the project type, it is desirable to improve the accuracy of the determination result by using the contents of the build tool or the configuration file.

  As described above, according to the software development support apparatus 10 in the embodiment of the present invention, the application type of the application to be checked for the coding rule is automatically determined, and the coding rule corresponding to the application type is automatically determined. Can be selected. Therefore, the user can be freed from complicated operations such as selection of application type and selection of coding convention to be applied, and productivity can be improved.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to the specific embodiment which concerns, In the range of the summary of this invention described in the claim, various deformation | transformation * It can be changed.

Regarding the above description, the following items are further disclosed.
(Supplementary note 1)
A file configuration determination procedure for determining the type of the application based on the file configuration of a project defined as an application development environment;
A project type determination procedure for determining the type of the application based on the type of the project;
It is specified by the rule correspondence information in which the coding rule applied to the source code of the application is defined according to the type of the application, and at least one determination result in the file configuration determination procedure and the project type determination procedure A coding rule selection program for executing an application rule determining procedure for determining a coding rule applied to the source code of the application based on the type of application.
(Supplementary note 2) The coding rule selection program according to supplementary note 1, wherein the project type determination procedure is executed when the type of the application is not uniquely specified in the file configuration determination procedure.
(Supplementary note 3) The coding rule selection program according to supplementary note 1 or 2, wherein the file configuration determination procedure determines the type of the application based on the presence or absence of a predetermined file in the files constituting the project.
(Additional remark 4) It has the build tool determination procedure which determines the classification of the said application based on the structure of the program used for the build of the said application in the said project,
The applicable contract determination procedure is based on the contract correspondence information and the type of application specified by at least one determination result in the build tool determination procedure, the file configuration determination procedure, and the project type determination procedure. The coding rule selection program according to any one of appendices 1 to 3, wherein a coding rule to be applied to the source code of the application is determined.
(Supplementary note 5) The coding rule selection program according to supplementary note 4, wherein the file configuration determination procedure is executed when the type of the application is not uniquely specified in the build tool determination procedure.
(Supplementary note 6) The coding rule selection program according to supplementary note 5, wherein when the type of the application is not uniquely specified in the build tool determination procedure and the file configuration determination procedure, the project type determination procedure is executed.
(Additional remark 7) It has the file content determination procedure which determines the classification of the said application based on the content of the predetermined file which comprises the said project,
The application rule determination procedure is based on the rule correspondence information and the type of application specified by at least one determination result in the file content determination procedure, the file configuration determination procedure, and the project type determination procedure. The coding rule selection program according to any one of appendices 1 to 3, wherein a coding rule to be applied to the source code of the application is determined.
(Supplementary note 8) The coding rule selection program according to supplementary note 7, wherein the file content determination procedure is executed when the type of the application is not uniquely specified in the file configuration determination procedure.
(Supplementary note 9) The coding rule selection program according to supplementary note 8, wherein the project type determination procedure is executed when the type of the application is not uniquely identified in the file configuration determination procedure and the file content determination procedure.
(Additional remark 10) It has the file content determination procedure which determines the classification of the said application based on the content of the predetermined file which comprises the said project,
The application rule determination procedure is an application specified by the rule correspondence information and at least one determination result in the file content determination procedure, the build tool determination procedure, the file configuration determination procedure, and the project type determination procedure. 7. The coding rule selection program according to any one of appendices 4 to 6, wherein the coding rule applied to the source code of the application is determined based on the type of the coding.
(Supplementary note 11) The coding rule selection program according to supplementary note 10, wherein the file content determination procedure is executed when the type of the application is not uniquely identified in the file configuration determination procedure.
(Additional remark 12) The said project type determination procedure is performed when the said application type is not uniquely specified in the said build tool determination procedure, the said file structure determination procedure, and the said file content determination procedure, The additional description 11 characterized by the above-mentioned. Coding convention selection program.
(Supplementary note 13) The coding rule according to any one of Supplementary notes 7 to 12, wherein the file content determination procedure determines the type of the application based on the presence or absence of a predetermined character string in the source code of the application. Selection program.
(Additional remark 14) The computer-readable recording medium which recorded the coding rule selection program as described in any one of additional marks 1 thru | or 13.
(Supplementary note 15) A coding rule selection method for selecting a coding rule to be applied to an application source code using a computer,
A file configuration determination procedure for determining the type of the application based on the file configuration of a project defined as an application development environment;
A project type determination procedure for determining the type of the application based on the type of the project;
It is specified by the rule correspondence information in which the coding rule applied to the source code of the application is defined according to the type of the application, and at least one determination result in the file configuration determination procedure and the project type determination procedure A coding rule selection method comprising: an application rule determining procedure for determining a coding rule applied to a source code of an application based on an application type.
(Supplementary Note 16) File configuration determination means for determining the type of the application based on the file configuration of the project defined as the application development environment;
Project type determination means for determining the type of the application based on the type of the project;
It is specified by the rule correspondence information in which the coding rule applied to the source code of the application is defined according to the type of the application, and at least one determination result by the file configuration determination unit and the project type determination unit. A coding rule selecting device comprising: application rule determining means for determining a coding rule applied to the source code of the application based on the type of application.

It is a figure which shows the hardware structural example of the software development assistance apparatus in embodiment of this invention. It is a figure which shows the function structural example of the software development assistance apparatus in embodiment of this invention. It is a figure which shows the function structural example of the rule check tool in embodiment of this invention. It is a figure which shows the function structural example of an application classification determination part. It is a flowchart for demonstrating the process sequence at the time of the build by a development environment provision part. It is a flowchart for demonstrating the process sequence of a rule check tool. It is a figure which shows the structural example of a rule corresponding | compatible information management table. It is a flowchart for demonstrating the process sequence of the determination process of an application classification by an application classification determination part. It is a figure which shows the structural example of the table which manages the correspondence between application classification and a build tool. It is a figure which shows the 2nd structural example of the table which manages the correspondence between an application classification and a build tool. It is a figure which shows the example of the correspondence of application classification and file structure. It is a figure which shows the example of the correspondence of application classification and the content of a configuration file. It is a figure which shows the correspondence of application classification and project classification.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Software development support apparatus 11 Development environment provision part 12, 12a, 12b Build tool 12c Contract check tool 100 Drive apparatus 101 Recording medium 102 Auxiliary storage apparatus 103 Memory apparatus 104 Arithmetic processing apparatus 105 Display apparatus 106 Input apparatus 111 Project assets 121 Contract selection Unit 122 rule check unit 1110 source file 1210 coding rule 1211 source file extraction unit 1212 application type determination unit 1212a project type determination unit 1212b configuration file determination unit 1212c configuration file content determination unit 1212d build tool determination unit 1213 applicable rule determination unit 1214 Information management table 1215 Check target output unit B bus

Claims (5)

On the computer,
A file configuration determination procedure for determining the type of the application based on the file configuration of a project defined as an application development environment;
A project type determination procedure for determining the type of the application based on the type of the project;
It is specified by the rule correspondence information in which the coding rule applied to the source code of the application is defined according to the type of the application, and at least one determination result in the file configuration determination procedure and the project type determination procedure A coding rule selection program for executing an application rule determining procedure for determining a coding rule applied to the source code of the application based on the type of application. The coding rule selection program according to claim 1, wherein the project type determination procedure is executed when the type of the application is not uniquely specified in the file configuration determination procedure. A build tool determination procedure for determining a type of the application based on a configuration of a program used for building the application in the project;
The applicable contract determination procedure is based on the contract correspondence information and the type of application specified by at least one determination result in the build tool determination procedure, the file configuration determination procedure, and the project type determination procedure. The coding rule selection program according to claim 1 or 2, wherein a coding rule applied to the source code of the application is determined. 4. The coding rule selection program according to claim 3, wherein the file configuration determination procedure is executed when the type of the application is not uniquely specified in the build tool determination procedure. A file content determination procedure for determining the type of the application based on the content of a predetermined file constituting the project,
The application rule determination procedure is based on the rule correspondence information and the type of application specified by at least one determination result in the file content determination procedure, the file configuration determination procedure, and the project type determination procedure. The coding rule selection program according to claim 1 or 2, wherein a coding rule applied to the source code of the application is determined.

Images