JP2014167674A - Database access verification method, database access verification device, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To verify deadlock of a database in a design phase.SOLUTION: A database access verification method includes: a route extraction step where a route extraction unit acquires design document information from a design document storage unit which stores design document information defining an information processing procedure of software and extracts an information processing route on the basis of the acquired design document information; and a verification step where a verification unit extracts extraction access order information showing a database access order in the route extracted by the route extraction step, and verifies whether the extracted extraction access order information matches reference access order information acquired from an order storage unit which stores reference access order information showing a predetermined database access order.

Description

  The present invention relates to a database access verification method, a database access verification device, and a program.

  In recent years, a technique for supporting verification of software that has been performed manually and visually is known. For example, Patent Literature 1 and Patent Literature 2 describe a technique that supports verification of a sequence diagram, which has been conventionally performed manually and visually, by analyzing the sequence diagram.

JP 2008-90857 A JP 2008-197975 A

By the way, in software using a database, it is important to prevent database deadlock, and the verification is generally performed by operating a program implemented in a program implementation stage or a test stage. .
However, in the verification at the mounting stage or the test stage, for example, since the number of rework steps when it is found that a database deadlock occurs, it is desirable to verify at an early stage such as the design stage. However, when verification is performed at the software design stage, it is necessary to check the access order of the database by, for example, manual work and visual observation, and thus it is difficult to verify without omission. Further, with the techniques described in Patent Document 1 and Patent Document 2 for supporting the verification of the sequence diagram, it was not possible to verify the deadlock of the database at the design stage.

  The present invention has been made to solve the above problems, and an object thereof is to provide a database access verification method, a database access verification device, and a program capable of verifying a deadlock of a database in a design stage. .

  In order to solve the above problem, according to one aspect of the present invention, the route extraction unit acquires the design document information from the design document storage unit that stores the design document information that defines the information processing procedure in software, and acquires the design document information. Based on the design document information, a route extraction step for extracting the route of the information processing, and a verification unit extracts extraction access order information indicating a database access order in the route extracted by the route extraction step, Verification for verifying whether or not the extracted access order information extracted matches the reference access order information acquired from the order storage unit that stores reference access order information indicating a predetermined order for accessing the database A database access verification method comprising: steps.

  Further, according to one aspect of the present invention, in the database access verification method, the design document information includes a flow diagram visualizing the information processing procedure, the information processing procedure, and a database accessed in the information processing. And the access type indicating the type of operating the database accessed in the information processing in association with each other, and in the route extraction step, the route extraction unit includes the flow diagram, the information processing procedure, The path is extracted based on the path, and in the verification step, the verification unit is configured to determine the path extracted in the path extraction step, the information processing procedure, the table name, and the access type. The extracted access order information is extracted.

  Further, according to one aspect of the present invention, in the database access verification method, in the route extraction step, the route extraction unit extracts a plurality of the routes according to a branch process included in the flow diagram, and performs the verification. In the step, the verification unit verifies whether or not the extracted access order information and the reference access order information in each path are consistent with each of the plurality of paths.

  In one embodiment of the present invention, in the database access verification method, the reference access order information includes a table name of a database and a sequence number indicating an access order corresponding to the table name, and in the verification step, The verification unit uses, as the extracted access order information, the access information that associates the table name of the database accessed in the route with the sequence number corresponding to the table name in the reference access order information in the order of the route. When it is stored in the verification storage unit and the sequence numbers of the access information in the verification storage unit are stored in ascending order, it is determined that the extracted access sequence information is consistent with the reference access sequence information It is characterized by doing.

  Further, according to one aspect of the present invention, the design document information is acquired from a design document storage unit that stores design document information that defines a procedure of information processing in software, and the database is based on the acquired design document information. A path extracting unit that extracts the information processing path including access; and extracting access order information indicating a database access order in the information processing path extracted by the path extracting unit, and extracting the extracted access order A verification unit that verifies whether the information matches the reference access order information acquired from the order storage unit that stores the reference access order information indicating a predetermined order of accessing the database. This is a database access verification device characterized.

  Further, according to one aspect of the present invention, in the computer, the path extraction unit acquires the design document information from a design document storage unit that stores design document information that defines a procedure of information processing in software. A route extraction step for extracting a route of the information processing including access to a database based on the information; and a verification unit that extracts extracted access order information indicating a database access order in the route extracted by the route extraction step. Whether the extracted access order information extracted and extracted matches the reference access order information acquired from the order storage unit that stores reference access order information indicating a predetermined order of accessing the database. This is a program for executing a verification step for verification.

  According to the present invention, it is possible to verify database deadlock at the design stage.

It is a block diagram which shows an example of the database access verification apparatus by 1st Embodiment. It is a schematic diagram which shows the structural example of the design document memory | storage part in this embodiment. It is a figure which shows an example of the flow information sheet | seat of online process design document information in this embodiment. It is a figure which shows an example of the kind of flowchart figure which can be analyzed in this embodiment. It is a figure which shows an example of the basic information sheet of the online process design document information in this embodiment. It is a figure which shows an example of the flow information sheet | seat of the service type design document information in this embodiment. It is a figure which shows an example of the basic information sheet of the service type | system | group design document information in this embodiment. It is a figure which shows an example of the acquisition information sheet in this embodiment. It is a figure which shows an example of the output information sheet in this embodiment. It is a figure which shows an example of the parameterized logic information sheet in this embodiment. It is a figure which shows an example of the reference | standard access order information in this embodiment. It is a figure which shows an example of the verification result in this embodiment. It is a flowchart which shows an example of the procedure of the database access verification in this embodiment. It is a flowchart which shows an example of the prior check process of the input information in this embodiment. It is a flowchart which shows an example of the route extraction process in this embodiment. It is a flowchart which shows an example of the extraction process of a branch pattern in this embodiment. It is a flowchart which shows an example of the path | route production | generation process in this embodiment. It is a schematic diagram which shows an example of the route extraction in this embodiment. It is a schematic diagram which shows another example of the route extraction in this embodiment. It is a flowchart which shows an example of the verification process of the access order in this embodiment. It is an image figure which shows an example of the verification process of the access order in this embodiment. It is a block diagram which shows an example of the database access verification apparatus by 2nd Embodiment. It is a figure which shows an example of the collective verification result in this embodiment. It is a flowchart which shows an example of the batch verification process in this embodiment.

Hereinafter, a database access verification apparatus and a database access verification method according to an embodiment of the present invention will be described with reference to the drawings.
[First Embodiment]
FIG. 1 is a block diagram showing an example of a database access verification apparatus (DB access verification apparatus 1) according to this embodiment. In the following description, “database” may be abbreviated as “DB”.

In the DB access verification apparatus 1 according to the present embodiment, a database deadlock occurs at the software design stage by verifying a database procedure in software (system) defined by a plurality of design documents (design document information). This is a software design support tool that can determine whether or not to do so. Note that “database deadlock” refers to a state in which, in a plurality of processes, when the same database is accessed, waiting for the end of each other process, and as a result, no process can proceed further.
In the present embodiment, the software to be designed is realized by a database language (for example, SQL (Esqueuel)) to access the database.

First, an outline of each component provided in the DB access verification device 1 will be described here.
In FIG. 1, the DB access verification device 1 includes a design document storage unit 10, an access order storage unit 20, a control unit 30, and a verification storage unit 40.

  The design document storage unit 10 stores design document information serving as input information. Here, the design document information is information that defines a procedure of information processing in the software to be designed, and is also used as a design document used when the designer designs the software. The design document storage unit 10 stores a plurality of design document information for designing software to be designed. Details of the design document information will be described later.

  The access order storage unit 20 (order storage unit) stores reference access order information indicating a predetermined order of accessing the database. Here, the reference access order information indicates the correct access order for the database accessed in the software to be designed, and the access order in which no deadlock occurs in the database is determined in advance according to the database specifications. . The access order storage unit 20 stores, for example, a list in which database names and access order numbers are associated as reference access order information. Details of the reference access order information will be described later.

The control unit 30 is a processor including, for example, a CPU (Central Processing Unit) and the like, and comprehensively controls the DB access verification apparatus 1. The control unit 30 verifies the access order to the database in the software to be designed based on the design document information stored in the design document storage unit 10 as input information and the reference access order information stored in the access order storage unit 20. And output the verification result. The control unit 30 stores the verification result as output information in the verification storage unit 40.
The control unit 30 includes a pre-check unit 31, a route extraction unit 32, a DB access verification unit 33, and a verification result output unit 34.

  The pre-check unit 31 determines whether or not the input information, which is design document information stored in the design document storage unit 10, can correctly execute the verification process when executing the database access order verification process. Process (pre-check process) to be executed.

  The route extraction unit 32 acquires design document information from the design document storage unit 10 and extracts a route for information processing based on the acquired design document information. The path extraction unit 32 analyzes processing branches in the design document information and references to other design document information from the design document information, and extracts information processing paths. For example, when the branching process is included in the design document information, the path extracting unit 32 extracts a plurality of paths according to the branching process.

  The DB access verification unit 33 (verification unit) extracts the extracted access order information indicating the database access order in the route extracted by the route extraction unit 32, and acquires the extracted extracted access order information and the access order storage unit 20. It is verified whether or not the reference access order information is consistent. That is, the DB access verification unit 33 extracts the access order of the database for each of the plurality of routes extracted by the route extraction unit 32, and extracts the extracted access order information for each route and the access order storage unit 20. It is verified whether or not the acquired reference access order information is consistent.

  Specifically, the DB access verification unit 33 extracts, for example, the table name of the database accessed in the route extracted by the route extraction unit 32. Further, the DB access verification unit 33 uses, as extracted access order information, access information in which the extracted table name is associated with a sequence number corresponding to the table name in the reference access order information stored in the access order storage unit 20. The data is stored in the verification storage unit 40 in the order of the route. Then, the DB access verification unit 33 causes the verification storage unit 40 to store access information for all table names that access the database in the path. For example, when the sequence numbers of the access information in the verification storage unit 40 are stored in ascending order, the DB access verification unit 33 determines that the extracted access sequence information in the route matches the reference access sequence information To do. In addition, the DB access verification unit 33 may cause inconsistency between the extracted access order information in the route and the reference access order information when, for example, the order numbers of the access information in the verification storage unit 40 are not stored in ascending order. It is determined that

  Note that when such inconsistency occurs, the procedure specified in the design document information is not correct, which may cause a deadlock in the database. Therefore, the designer can know the possibility of deadlock in the database of the software to be designed at the design document information stage (design document stage), that is, the design stage.

  The verification result output unit 34 outputs the verification result verified by the DB access verification unit 33 by causing the verification storage unit 40 to store the verification result. Specifically, the verification result output unit 34 stores, in the verification storage unit 40, a verification result indicating whether or not the extracted access order information in each path matches the reference access order information acquired from the access order storage unit 20. Let

  The verification storage unit 40 stores information related to database access verification. For example, the verification storage unit 40 stores the extracted access order information verified by the control unit 30 and also stores the verification result. The verification storage unit 40 may store route information indicating the route extracted by the route extraction unit 32. Details of the information stored in the verification storage unit 40 will be described later.

<Structure of design document information>
Next, the configuration of the design document information stored in the design document storage unit 10 will be described.
FIG. 2 is a schematic diagram illustrating a configuration example of the design document storage unit 10 in the present embodiment.
In this figure, the design document storage unit 10 stores online processing design document information 11, service system design document information 12, and parameterized logic design document information 13. That is, the design document information includes, for example, online processing design document information 11, service system design document information 12, and parameterized logic design document information 13. In the example illustrated in FIG. 2, the design document storage unit 10 stores a plurality of online processing design document information 11, service system design document information 12, and parameterized logic design document information 13.

  The online processing design document information 11 is processing related to message input / output, and is design document information indicating an information processing procedure in which processing is started from a message. The online processing design document information 11 is design document information that mainly defines the starting process. Processing of the service system design document information 12 described later from the online processing design document information 11 or the parameterized logic design document information 13 Transition to processing. For example, one online process corresponds to one transaction process. The online processing design document information 11 includes a flow information sheet ST11 (flow information) and a basic information sheet ST21 (basic information), and the flow information sheet ST11 and the basic information sheet ST21 are associated with each other. Here, the “sheet” is a worksheet showing a table composed of rows and columns, which is used in spreadsheet software, and in the present embodiment, the design document information is a file using the worksheet. It is stored in the design document storage unit 10.

The service system design document information 12 is, for example, specification document information that defines processing of various services, common component design document information that defines various common components that perform predetermined processing, and the like. This is design document information indicating a procedure of information processing for starting processing. The service system design document information 12 includes a flow information sheet ST12 (flow information) and a basic information sheet ST22 (basic information). When accessing the database, the service system design document information 12 further includes an acquisition information sheet ST3 or an output information sheet ST4.
It should be noted that the flow information sheet ST1 of the online processing design document information 11 and the flow information sheet ST12 of the service system design document information 12 are not particularly distinguished, or simply indicate a flow information sheet, the flow information sheet ST1. Will be described. In addition, the basic information sheet ST2 of the online processing design document information 11 and the basic information sheet ST22 of the service system design document information 12 are not particularly distinguished, or when simply indicating a basic information sheet, the basic information sheet ST2 Will be described.

  The parameterized logic design document information 13 is, for example, specification document information that defines a process that branches based on a predetermined parameter, and includes a parameterized logic information sheet ST5 (parameterized logic information). The parameterized logic design document information 13 is design document information referred to from the service system design document information 12.

  As described above, the design document information includes a plurality of design document information (online processing design document information 11, service system design document information 12, and parameterized logic design document information 13). By referring to the document information, the processing procedure of the development target software (system) is defined by a plurality of design document information.

<Configuration of Online Processing Design Document Information 11>
Next, the configuration of the flow information sheet ST11 and the basic information sheet ST21 in the online process design document information 11 will be described. The example shown in FIGS. 3 and 4 shows the flow information sheet ST11 and the basic information sheet ST21 in the online process design document information 11 when the “online process name” is “4_02_online process”.

FIG. 3 is a diagram showing an example of the flow information sheet ST11 in the online process design document information 11.
As shown in this figure, the flow information sheet ST11 has “chapter / section / section”, “online process name”, and “process flow”. “Chapter / Section / Section” indicates the hierarchical structure of the design document information, and “Online process name” indicates the process name of the online process defined in this design document. The “processing flow” includes a flow diagram visualizing the procedure of information processing. In the example shown in FIG. 3, a flowchart F1 for executing “1. Process A” is written (drawn) as a flow diagram.

  In order to read a flow diagram as flow information by the DB access verification apparatus 1 according to the present embodiment, the flow diagram needs to be written according to a predetermined rule as shown in FIG. Here, the creation rule of the flowchart in the present embodiment will be described.

FIG. 4 is a diagram illustrating an example of types of flowcharts that can be analyzed in the present embodiment. The basic figure in FIG. 4A is a “text box” and a square figure of “square / rectangular” indicates “processing”, and is used when “processing” is described in the flowchart. In the flow diagram, text boxes without frame lines are ignored.
Further, a quadrilateral figure of “rounded square” in FIG. 4B indicates “alternative processing” and is used when calling a service in the flowchart.
In addition, a figure whose basic figure is “diamond” in FIG. 4C is “determined” and is used when processing is branched in the flowchart.

In addition, a figure whose basic figure is “trapezoid” in FIG. 4D is used as a starting point of a loop in the flowchart.
Further, the “hand work” (inverted trapezoidal) figure in FIG. 4E is used as the end point of the loop in the flowchart.
Also, the line “arrow” or “key line arrow connector” in FIG. 4F is used as a connector for connecting processes in the flowchart.
Also, the “terminal” figure in FIG. 4G is used for the start or end in the flowchart of the service system design document information.
Also, the “connector” figure in FIG. 4H is used as a connector with the flowcharts of other pages.
Note that figures other than FIGS. 4A to 4H are not analyzed and are ignored even if they are written in the flow diagram.

Next, the configuration of the basic information sheet ST21 in the online process design document information 11 will be described with reference to FIG.
FIG. 5 is a diagram showing an example of the basic information sheet ST21 in the online processing design document information 11. As shown in FIG.

As shown in this figure, the basic information sheet ST21 is design document information that defines the procedure of information processing, and includes “chapter / section / section”, “online process name”, “message” table, “service / part”. A table and a “content” table. The “message” table is a table that defines an input message or an output message, and includes “item number”, “message name”, “output condition”, “output destination”, “type”, “output unit”, and “remarks”. "Is associated.
In the example shown in FIG. 5, in the “message” table, “message name” corresponding to “1” of “item number” is “input message”, and “2” corresponding to “2” of “item number”. “Message name” indicates “output message”.

The “service / part” table is a table that defines a service or common part to be referred to (called) by this design document information. The “item number”, “service name / part name”, “type”, and “ "Remarks" are associated.
In the example shown in FIG. 5, in the “service / part” table, “service name / part name” corresponding to “1” of “item number” is “4 — 02_common service”, and “type” is “common”. "Service".

The “content” table is a table that defines the processing procedure corresponding to the flow diagram of the flow information sheet ST11, and is associated with “item number”, “processing procedure”, “detail”, and “remarks”. Yes. Here, “item number” and “processing procedure” indicate processing corresponding to each processing in the flow chart of the flow information sheet ST11, and “details” indicate specification information of a reference destination that defines the processing. Yes.
In the example shown in FIG. 5, in the “contents” table, “processing procedure” corresponding to “1” of “item number” is “processing A”, and “remarks” is “common service design document“ 4 — 02_common ”. This indicates that the service is “reference”. Here, the content of “remarks” indicates a reference destination to another sheet or other design document information. Further, the “item number” and “processing procedure” in the “content” table are created in accordance with the processing procedure of the flowchart F1 in the flow information sheet ST11.
As described above, the design document storage unit 10 stores the flow information sheet ST11 and the basic information sheet ST21 in association with each other as the online processing design document information 11.

<Configuration of Service System Design Document Information 12>
Next, the configuration of the flow information sheet ST12, the basic information sheet ST22, the acquisition information sheet ST3, and the output information sheet ST4 in the service system design document information 12 will be described. The examples illustrated in FIGS. 6 to 9 illustrate the flow information sheet ST12 and the basic information sheet ST22 in the service system design document information 12 when the “service name” is “4 — 02_common service”.

FIG. 6 is a diagram showing an example of the flow information sheet ST12 in the service system design document information 12.
As shown in this figure, the flow information sheet ST12 has “chapter / section / section”, “service name”, and “processing flow”. The configuration of the flow information sheet ST12 is the same as that of the flow information sheet ST11 of the online processing design document information 11.
In the example illustrated in FIG. 6, a flowchart F <b> 2 for executing “1. Process A” to “5. Process D” is written (drawn) as a flowchart.
In the flow information sheet ST12, the predetermined rule for reading the flow chart as the flow information is the same as the flow information sheet ST11 of the online process design document information 11, and it is necessary to follow the rule shown in FIG. Therefore, in the flow information sheet ST12, the process connected by the broken arrow (for example, “acquisition table 1” or the like is ignored by the DB access verification device 1 and is not read as design document information. The processes connected by the arrows are drawn so that the processes can be easily understood when the designer looks at the design document information.

FIG. 7 is a diagram showing an example of the basic information sheet ST22 in the service system design document information 12. As shown in FIG.
As shown in this figure, the basic information sheet ST22 is design document information that defines the procedure of information processing, and includes “chapter / section / section”, “service name”, “DB access” table, “parts” table, And a “content” table.

The “DB access” table is a table that defines information related to “table name” accessed as a database, and corresponds to “item number”, “table name”, “C / R / U / D”, and “remarks”. It is attached. Here, “C / R / U / D” indicates the type of access, “C” is “add (create)”, “R” is “reference”, “U” is “update”, “ “D” indicates “delete”.
In the example illustrated in FIG. 7, in the “DB access” table, “table name” corresponding to “1” of “item number” is “acquisition table 1”, and “C / R / U / D” is “R” (reference). In addition, “table name” corresponding to “2” of “item number” is “acquisition table 2”, and “C / R / U / D” is “R” (reference). Further, the “table name” corresponding to “3” of “item number” is “acquisition table 3”, and “C / R / U / D” is “R” (reference). In addition, “table name” corresponding to “4” of “item number” is “output table”, and “C / R / U / D” is “C” (addition).

The “parts” table is a table that defines information on “part names” referred to in “4 — 02_common service”, and “item number”, “part name”, and “remarks” are associated with each other.
In the example illustrated in FIG. 7, in the “components” table, the “component name” is “5_01_common component”, “5_02_common component”, “5_03_common component”, “5_04_common component”, and “5_05_common component”. Reference is made to five common parts.

The “content” table is a table that defines the processing procedure corresponding to the flow diagram of the flow information sheet ST12, and is associated with “item number”, “processing procedure”, “detail”, and “remarks”. Yes. Here, “item number” and “processing procedure” indicate processing corresponding to each processing in the flowchart of the flow information sheet ST12, and “details” indicate reference specification information that defines the processing, and database Acquisition information or output information.
In the example shown in FIG. 7, in the “content” table, “processing procedure” corresponding to “1” of “item number” is “data acquisition processing”, and “acquisition table 1” to “acquisition table 3”. The acquisition information sheet ST3 is referred to. Further, the “processing procedure” corresponding to “4” of “item number” is “processing C”, which indicates that the output information sheet ST4 of the “output table” is referred to.

FIG. 8 is a diagram illustrating an example of the acquisition information sheet ST3 in the service system design document information 12.
As shown in this figure, the acquisition information sheet ST3 is design document information that regulates the acquisition of information from the database, and includes “chapter / section / section”, “service name”, “acquisition information” table, and “acquisition information”. Item "table.

In the “acquisition information” table, “corresponding processing procedure”, “acquisition source type”, “acquisition source”, “access type”, and “number of acquisitions” are associated with each other. Here, “corresponding processing procedure” indicates a corresponding processing procedure. The “acquisition source type” indicates the type of the acquisition source, and defines “DB” (database) or “file”. “Acquisition source” indicates the name of the table from which information is acquired, and “Number of acquisitions” indicates the number of acquisitions of information. The “access type” indicates the type of access (type for operating the database) in information acquisition, and defines “reference” or “reference with update”.
In the example illustrated in FIG. 8, in the “acquisition information” table, “corresponding processing procedure” is “acquisition processing”, “acquisition source type” is “DB”, and “acquisition source” is “acquisition table 1”. ", Indicating that the" access type "is" reference ".
Further, one or more table names can be set in the “acquisition source” described above. Specifically, when a plurality of table names are set, they can be set by separating them with “,” (comma). For example, when “acquisition table 1” and “acquisition table 2” are stored as “acquisition sources”, “acquisition table 1, acquisition table 2” is used. In this case, the DB access verification unit 33 performs access verification assuming that accesses are made in order from the table described at the top.

The “acquired item” table is a table that defines information related to items to be acquired as information, and is associated with “item number”, “item name”, “setting content”, and “remarks”.
In the example shown in FIG. 8, in the “acquired item” table, “item name” corresponding to “1” of “item number” is “XX data” and corresponds to “2” of “item number”. “Item name” to be “XX data”.

FIG. 9 is a diagram showing an example of the output information sheet ST4 in the service system design document information 12.
As shown in this figure, the output information sheet ST4 is design document information that regulates the output of information to the database, and includes “chapter / section / section”, “service name”, “output information” table, and “output”. Item "table.

In the “output information” table, “corresponding processing procedure”, “output destination type”, “output destination”, and “access type” are associated with each other. Here, “corresponding processing procedure” indicates a corresponding processing procedure. The “output destination type” indicates the type of the output destination and defines “DB” (database) or “file”. The “output destination” indicates the name of a table for outputting information. “Access type” indicates the type of access (type of database operation) in the output of information, and defines “creation” (addition), “update”, or “deletion”.
In the example shown in FIG. 9, in the “output information” table, “corresponding processing procedure” is “output processing”, “output destination type” is “DB”, and “output destination” is “output table”. The “access type” is “update”.

The “output item” table is a table that defines information about items to be output as information, and “item number”, “item name”, “setting content”, and “remarks” are associated with each other.
In the example illustrated in FIG. 9, in the “output item” table, “item name” corresponding to “1” of “item number” is “data A” and corresponds to “2” of “item number”. It shows that “item name” is “data B”.

  As described above, the design document storage unit 10 stores the flow information sheet ST12, the basic information sheet ST22, the acquisition information sheet ST3, and the output information sheet ST4 in association with each other as the service system design document information 12. . In addition, the design document information is accessed in the information processing flow chart (for example, the flow information sheet ST12), the information processing procedure (for example, the “content” table in the basic information sheet ST22), and the information processing. Database table name and access type in association with each other. Here, for example, the “DB access” table of the basic information sheet ST22, the “acquisition information” table of the acquisition information sheet ST3, and the “output information” table of the output information sheet ST4 correspond to the table name and access type of the database. .

<Configuration of Parameterized Logic Design Document Information 13>
Next, the configuration of the parameterized logic information sheet ST5 in the parameterized logic design document information 13 will be described.

FIG. 10 is a diagram showing an example of the parameterized logic information sheet ST5 in the parameterized logic design document information 13. As shown in FIG.
As shown in FIG. 10 (a), the parameterized logic information sheet ST5 is design document information that defines the parameterized logic processing, and includes “chapter / section / section”, “parameterized logic name”, and “mapping definition”. ”Table.

In the “mapping definition” table, “item number”, “parameter combination”, and “processing logic” are associated with each other. Here, “parameter combination” indicates a combination of parameters used for branching (condition for branching), and “parameter combination” includes “parameter attribute 1”, “parameter attribute 2”, and “description”. Is included. “Processing logic” indicates processing referred to by branching.
In the example shown in FIG. 10A, in the “mapping definition” table, “parameter attribute 1” corresponding to “1” of “item number” is “1”, and “parameter attribute 2” is “A”. "Processing logic" is "Common part design document" A common part "see". Also, "Parameter attribute 1" corresponding to "2" of "Item number" is "1""Parameter attribute 2" is "B", and "processing logic" is "common component design document" see B common component "". Also, "item number""3""Parameter attribute 1" corresponding to "" is "2", "Parameter attribute 2" is "A", and "Processing logic" is "See common part design document" C common parts "" ing.

A flowchart F3 shown in FIG. 10B shows parameterized logic processing defined by the parameterized logic information sheet ST5 shown in FIG. In the flowchart F3, any one of the “A common part” process, the “B common part” process, and the “C common part” process is performed according to the parameter attribute value in accordance with the definition of the parameterized logic information sheet ST5. A process that branches into two processes is shown.
In the present embodiment, the parameterized logic design document information 13 does not include a flowchart as shown in FIG. Therefore, when extracting the route, the route extracting unit 32 of the control unit 30 generates a flowchart as shown in FIG. 10B based on the parameterized logic information sheet ST5.

<Configuration of reference access order information>
Next, the configuration of the reference access order information stored in the access order storage unit 20 will be described.
FIG. 11 is a diagram illustrating an example of the reference access order information in the present embodiment.
In this figure, the access order storage unit 20 stores “chapter / section / item”, “subsystem name”, and access order list table as reference access order information (access order information sheet ST6).
The access order list table shows a list of database access orders, and “item number”, “table name”, and “access order” are associated with each other. Here, “table name” indicates a table name in the database, and “access order” indicates an access order number.

In the example shown in FIG. 11, in the access order list table, “table name” corresponding to “1” of “item number” is “acquisition table 1”, and “access order” is “1”. Is shown. In addition, “table name” corresponding to “2” of “item number” is “output table”, and “access order” is “2”.
In the example shown in FIG. 11, an example in which “item number” and “access order” match is shown, but it does not need to match.
Thus, the reference access order information includes the database table name and the order number indicating the access order corresponding to the table name.

<Configuration of verification results>
Next, the configuration of information indicating the verification result stored in the verification storage unit 40 will be described.
FIG. 12 is a diagram illustrating an example of a verification result in the present embodiment.
FIG. 12A shows an example of a verification result in certain online processing design document information 11. In FIG. 12A, the verification result is stored in the verification storage unit 40 as a verification result sheet ST41.

The verification result sheet ST41 includes “route”, “determination”, “C / R / U / D”, “table route”, and “hash value of processing route”. Here, “route” indicates a route of information processing extracted by the route extraction unit 32. Since the DB access verification unit 33 performs verification of the database access order for each of a plurality of paths, the verification result sheet ST41 includes verification results corresponding to the plurality of paths.
“Determination” indicates the determination result of the access order of the database, and includes two determination results of “tool” and “visually”. Note that “tool” indicates a determination result by the DB access verification apparatus 1 in the present embodiment, and “visually” indicates an entry field for separately entering the determination result by hand. The DB access verification unit 33 determines “tool” as “◯” when the access order to the database is in ascending order, and determines “tool” as “×” when the order is not in ascending order.

  “C / R / U / D” indicates the number of accesses to the database for each access type, and includes the number of accesses for “addition” (creation), “reference”, “update”, and “deletion”. Yes. The “table route” indicates a list of table access order in each route. In the “table route”, “()” (parentheses) indicates the access order in the loop. The “processing path hash value” indicates, for example, a hash value obtained by calculating “design document name + processing name + table name” using a hash function SHA1 (Secure Hash Algorithm 1).

  In the example shown in FIG. 12A, in the verification result sheet ST41, “Tool” of “Judgment” corresponding to “Route 1” is “O”, and “Table route” is “1”. , 2 ". In this case, since “1, 2” is in ascending order, the DB access verification unit 33 determines “Tool” of “Decision” as “◯”. Further, the “tool” of “determination” corresponding to “route 3” is “x”, and “table route” is “1, 2, (9, 20, 13), 22, 23, 25”. ". In this case, the DB access verification unit 33 determines that “tool” of “determination” is “x” because “1, 2, (9, 20, 13), 22, 23, 25” is not in ascending order. .

Further, the “processing path hash value” described above is calculated by the verification result output unit 34, and the efficiency is improved when the verification process of the access order and the correction (update) of the design document information based on the verification result are repeatedly executed. It is used to find the verification result of the route including the design document information that is well revised (updated). For example, the verification result output unit 34 extracts a path including the modified (updated) design document information based on the “processing path hash value”, and a verification result list of the path including the corrected (updated) design document information. May be generated as a verification result.
Specifically, the verification result output unit 34, for example, includes all “design document names”, “processing item numbers”, “processing names”, “table names”, “access types”, and “order” in one path. A hash value is calculated with a character string in which is enumerated. For example, in the case illustrated in FIG. 12B, the verification result output unit 34 displays “Process A design document, 1.XXX processing service, reference with update, acquisition table 1, 1, process A design document, 1 ... Hash value of processing service, reference with update, output table, 2, processing A design document, loop 1 start.

  Further, the verification result may include a list of access information in each route as shown in FIG. The verification storage unit 40 stores an access information sheet ST42 as shown in FIG. 12B as a verification result. Note that the access information sheet ST42 shown in FIG. 12B is for one route, and the verification storage unit 40 stores a plurality of access information sheets ST42 corresponding to each route.

The access information sheet ST42 includes access information in which “design document name”, “processing item number”, “processing name”, “DB access”, and “order” are associated with each other, and “result”. They are stored in the order of the route. Here, “design document name” indicates the name of the analyzed or verified design document or reference design document, and “DB access” indicates the “table name” and “access type” of the access destination. “Order” indicates the “access order” number corresponding to “table name” in the reference access order information (access order information sheet ST6).
In the present embodiment, it is assumed that one database is used in one subsystem. Therefore, when “table name” is a table other than the subsystem acquired from the design document information (origin design document information) as the starting point, “−” or “×” is stored in the “order”. . For example, if the table is a table other than the acquired subsystem and the “access type” is “reference”, the DB access verification unit 33 stores “−” in the “order”. For example, when the table is a table other than the acquired subsystem and the “access type” is “add”, “update”, or “delete”, the DB access verification unit 33 sets “x” to “order”. Remember.

The “result” indicates a verification result obtained by determining whether or not the access procedure in the route extracted by the route extraction unit 32 is consistent with the reference access order information. For example, when the “order” is an ascending order, the DB access verification unit 33 determines that the access procedure in this route is consistent with the reference access order information, and the verification result output unit 34 “○” is stored in “”. For example, when the “order” is not in ascending order, the DB access verification unit 33 determines that the access procedure in this route is not consistent with the reference access order information, and the verification result output unit 34 “×” is stored in “Result”.
In the example shown in FIG. 12B, in the access information sheet ST42, since “order” is in ascending order, “result” is “◯”.

  Also, the DB access verification unit 33 excludes this determination from the determination when “order” is “−”. If the “order” is “x”, the DB access verification unit 33 determines that the access procedure in this route is not consistent with the reference access order information, and the verification result output unit 34 “×” is stored in “Result”. As described above, according to the present embodiment, it is possible to provide separate criteria for access verification for acquiring data from the database and access verification for outputting data to the database.

Next, the operation of the DB access verification apparatus 1 in this embodiment will be described.
FIG. 13 is a flowchart illustrating an example of a procedure for DB access verification in the present embodiment. Note that the processing of the flowchart shown in FIG. 13 is started after design document information as a starting point is selected.

  In this figure, first, the control unit 30 of the DB access verification device 1 executes a pre-check process for input information (step S101). Specifically, the prior check unit 31 of the control unit 30 checks that the input information can be read correctly when executing DB access verification. That is, the prior check unit 31 checks whether or not the design document information stored in the design document storage unit 10 can be correctly analyzed. The details of the input information pre-check process will be described later with reference to FIG.

  Next, the control unit 30 determines whether or not the advance check is OK (no problem) (step S102). That is, the control unit 30 determines whether there is no problem with the advance check based on the result of the advance check by the advance check unit 31. If there is no problem with the advance check (step S102: YES), the control unit 30 advances the process to step S103. Further, when the prior check is problematic (step S102: NO), the control unit 30 ends the DB access verification process.

  Next, in step S103 (route extraction step), the route extraction unit 32 extracts a route based on the design document information (route extraction process). The route extraction unit 32 acquires design document information from the design document storage unit 10 and extracts a route for information processing based on the acquired design document information. Specifically, the route extraction unit 32 extracts a route based on a flow information sheet ST1 (flow diagram) and a basic information sheet ST2 (information processing procedure) included in the design document information. Here, the route extraction unit 32 extracts a plurality of routes according to the branching process included in the flow information sheet ST1. Details of this route extraction processing will be described later with reference to FIG.

Next, the DB access verification unit 33 executes access order verification processing based on the route extracted by the route extraction unit 32 (step S104: verification step). The DB access verification unit 33 verifies whether the extracted access order information in the route extracted by the route extraction unit 32 matches the reference access order information acquired from the access order storage unit 20.
Specifically, the DB access verification unit 33 determines whether a route is extracted based on the route extracted by the route extraction unit 32, the information processing procedure (the “content” table in the basic information sheet ST2), the table name, and the access type. Extraction access order information is extracted. The DB access verification unit 33 verifies whether the extracted extracted access order information matches the reference access order information acquired from the access order storage unit 20. The details of the access order verification process will be described later with reference to FIGS.

  Next, the verification result output unit 34 outputs the verification result (step S105). That is, the verification result output unit 34 stores the verification results (for example, the verification result sheet ST41 and the access information sheet ST42 shown in FIG. 12) verified by the DB access verification unit 33 as output information in the verification storage unit 40.

<Pre-check process for input information>
Next, the detailed procedure of the input information pre-check process, which is the process in step S101 of FIG. 13, will be described.
FIG. 14 is a flowchart illustrating an example of input information pre-check processing in the present embodiment.

  In this figure, first, the prior check unit 31 determines whether or not there is basic information (basic information sheet ST2) (step S201). That is, the pre-check unit 31 determines whether or not each basic information sheet ST2 of various design document information including the design document information as a starting point and the design document information to be referred to is stored in the design document storage unit 10. The advance check unit 31 advances the process to step S202 when each basic information sheet ST2 of various design document information is stored in the design document storage unit 10 (step S201: YES). Further, the pre-check unit 31 ends the process when each basic information sheet ST2 of various design document information is not stored in the design document storage unit 10 (step S201: NO).

  Next, in step S202, the pre-check unit 31 determines whether there is flow information (flow information sheet ST1). That is, the pre-check unit 31 determines whether or not a flow information sheet ST1 of various design document information including the design document information as a starting point and the referenced design document information is stored in the design document storage unit 10. When the flow information sheet ST1 of various design document information is stored in the design document storage unit 10 (step S202: YES), the advance check unit 31 advances the process to step S203. The pre-check unit 31 ends the process when the flow information sheet ST1 of various design document information is not stored in the design document storage unit 10 (step S202: NO).

Next, in step S203, the pre-check unit 31 executes a check process for basic information (basic information sheet ST2). That is, the pre-check unit 31 checks whether there is a problem in the information in the “content” table of each basic information sheet ST2.
Specifically, the pre-check unit 31 checks whether there is information stored in “order” and “detail” of the “content” table.
In addition, when there is a problem in the basic information sheet ST2, the prior check unit 31 may output the warning information including the problematic part and the content of the problem in the verification storage unit 40.

  Next, the pre-check unit 31 executes a check process for flow information (flow information sheet ST1) (step S204). That is, the pre-check unit 31 checks whether there is a problem in the “processing flow” (flow diagram) of each flow information sheet ST1.

Specifically, the pre-check unit 31 checks the following items in the “processing flow” (flow diagram).
(1) Whether the connector for connecting the figure is connected correctly.
(2) Whether the connector is in the shape of an arrow.
For example, the pre-check unit 31 determines that there is a problem (error) when the shape of the connector is an arrow or no arrow at both ends.
(3) Whether there is a called “connector” corresponding to the called “connector” when there is a “connector” shown in FIG.
(4) Whether the order described in the processing contents of the graphic exists in the “order” of the “content” table of the basic information sheet ST2.
(5) Whether the processing content of the graphic is described in a format of “order. Processing procedure” (for example, “1. processing A”).

In addition, when there is a problem in the flow information sheet ST1, the pre-check unit 31 may output the warning information including the problematic part and the content of the problem in the verification storage unit 40.
The pre-check unit 31 executes the check process of the flow information sheet ST1 and ends the pre-check process of input information.

<Route extraction process>
Next, a detailed procedure of route extraction processing that is processing in step S103 of FIG. 13 will be described.
FIG. 15 is a flowchart illustrating an example of route extraction processing according to the present embodiment.

  In this figure, first, the route extraction unit 32 acquires a subsystem (step S301). That is, the path extraction unit 32 acquires the subsystem name based on the basic information sheet ST2 of the design document information that is the starting point.

Next, the route extraction unit 32 acquires reference access order information stored in the access order storage unit 20 (step S302).
Next, the route extraction unit 32 determines whether or not the reference access order information has been acquired (step S303). When the reference access order information is acquired in step S302 (step S303: YES), the route extraction unit 32 advances the process to step S304. In addition, when the reference access order information cannot be acquired in step S302 (step S303: NO), the route extraction unit 32 ends the route extraction process.

  Next, in step S304, the path extraction unit 32 executes an analysis process of the original design document information. That is, the path extraction unit 32 analyzes the flow information sheet ST1 and the basic information sheet ST2 of the design document information (original design document information) as a starting point. For example, in the flow diagram, the route extraction unit 32 reads each item (flow figure), analyzes the arrow, and detects an item as a starting point. Note that the route extraction unit 32 creates a dummy parent item (virtual start item) as a starting point of route creation above the item that is the starting point. This parent item for dummy is created for the purpose of unifying the starting point of route creation because the shape of the starting item varies depending on the flow.

  Next, the path extraction unit 32 executes reference design document information analysis processing (step S305). That is, the path extraction unit 32 analyzes the flow information sheet ST1 and the basic information sheet ST2 of the reference design document information that are referred to in order from the original design document information. For example, in the flowchart, the route extraction unit 32 reads each item, analyzes the arrow, and detects the item that is the starting point. Note that the path extraction unit 32 creates a dummy parent item (virtual start item) as a starting point of path creation for the reference design document information as well as the original design document information.

  Next, the path extraction unit 32 analyzes the reference destination of the basic information sheet ST2, and determines whether there is a reference destination that has not been analyzed (step S306). If there is a reference destination that has not been analyzed (step S306: YES), the path extraction unit 32 returns the process to step S305 and repeats the analysis process of the reference design document information. In addition, when there is a reference destination that has not been analyzed (step S306: NO), the route extraction unit 32 advances the processing to step S307.

  Next, in step S307, the route extraction unit 32 executes branch pattern extraction processing. That is, the path extraction unit 32 extracts branch processing included in the analyzed original design document information and reference design document information, and creates a branch pattern (branch combination pattern). The details of the branch pattern extraction process (the process of the first extraction step) will be described later with reference to FIG.

  Next, the route extraction unit 32 executes route generation processing for extracting a route based on the branch pattern (step S308). That is, the route extraction unit 32 generates a plurality of routes according to the branch pattern, and ends the process. Details of this route generation processing (processing of the second extraction step) will be described later with reference to FIG.

<Branch pattern extraction processing>
Next, a detailed procedure of the branch pattern extraction process, which is the process in step S307 of FIG. 15, will be described.
FIG. 16 is a flowchart illustrating an example of branch pattern extraction processing in the present embodiment.

  In this figure, first, the route extraction unit 32 calculates the maximum number of branches in one route (step S401). That is, the route extraction unit 32 extracts all reference design document information branches from the starting point design document information as a starting point, and calculates the maximum number of branches. For example, the route extraction unit 32 calculates the maximum number of branches based on the number of branches of all reference design document information, the number of reference design document information, and the number of times the reference design document information is called from the origin design document information. To do.

  Next, the route extraction unit 32 generates a list of branches that pass through one route (step S402). The path extraction unit 32 calculates all branch patterns and generates a list of branches on the assumption that branches are executed for the maximum number of times of the above-described branches. For example, when there are three branches that branch into two routes, the total number of branch patterns is one of three branches (eg, “branch A”, “branch B”, “branch C”). Since there are three call combinations, there are 216 combinations as shown in the following equation (1).

  2 × 2 × 2 × 3 × 3 × 3 = 216 ways (1)

  Next, the route extraction unit 32 extracts the first branch and the branch of the starting point design document information (step S403). The path extraction unit 32 analyzes the reference design document information in order from the starting point design document information, and extracts the first branch and the branch of the starting point design document information.

Next, the route extraction unit 32 creates a combination of branch patterns (step S404). Specifically, the route extraction unit 32 uses the following two mechanisms to create combinations of branch patterns by narrowing down combinations from a list of branches.
First, the route extraction unit 32 narrows down the combinations using the fact that the first branch is unchanged. For example, in the above-described example, when “branch A” is the first branch, there are 72 combinations of branch patterns as shown in the following formula (2).

  2 × 2 × 2 × 1 × 3 × 3 = 72 ways (2)

  Furthermore, the route extraction unit 32 narrows down the combinations by using the fact that the branch of the origin design document information passes only once. For example, in the above-described example, when “branch B” and “branch C” are branches of the origin design document information, there are 16 combinations of branch patterns as shown in the following formula (3). In this case, there are two branch paths: “branch A” → “branch B” → “branch C” and “branch A” → “branch C” → “branch B”.

  2 × 2 × 2 × 1 × 2 × 1 = 16 ways (3)

  Thus, the route extraction unit 32 creates a combination of branch patterns by narrowing down the combinations. Thereby, since the combination pattern is reduced, the DB access verification apparatus 1 in the present embodiment can reduce the storage capacity of the storage unit to be used in the path generation processing described later. In addition, the DB access verification device 1 can reduce the amount of calculation, and therefore can shorten the processing time.

<Route generation processing>
Next, a detailed procedure of the route generation process that is the process in step S308 of FIG. 15 will be described.
FIG. 17 is a flowchart illustrating an example of route generation processing in the present embodiment.
Note that the process shown in FIG. 17 is a process executed for one of the combinations of branch patterns, and the route extraction unit 32 performs the process shown in FIG. To extract a plurality of routes.

  In this figure, first, the path extraction unit 32 initializes a branch pointer (step S501). Here, the branch pointer is information indicating which branch is searched in the branch path based on the branch pattern. For example, the route extraction unit 32 sets the value of the branch pointer to “0” and starts the route generation process from the above-described dummy parent item.

  Next, the route extraction unit 32 reads an item (flow item) (step S502). That is, the route extraction unit 32 reads items in the flow diagram of the flow information sheet ST1.

  Next, the path extraction unit 32 determines whether or not the read item is a branch (step S503). When the read item is a branch (step S503: YES), the route extraction unit 32 advances the process to step S504. Moreover, the path | route extraction part 32 advances a process to step S505, when the read item is not a branch (step S503: NO).

  Next, in step S504, the path extraction unit 32 determines whether or not the branch is a correct branch. In other words, the route extraction unit 32 determines whether or not the branch follows a branch pattern route extracted by the branch pattern extraction process described above. When the branch is a correct branch (step S504: YES), the route extraction unit 32 advances the process to step S505. Moreover, the path | route extraction part 32 advances a process to step S510, when a branch is not a correct branch (step S504: NO).

  Next, in step S505, the path extraction unit 32 determines whether or not to transit to other design document information (reference design document information). The path extraction unit 32 advances the process to step S506 when transitioning to other design document information (reference design document information) (step S505: YES). Moreover, the path | route extraction part 32 advances a process to step S511, when not changing to other design document information (reference design document information) (step S505: NO).

  Next, in step S506, the route extraction unit 32 determines whether the flow item is connected to the previous flow item. That is, the route extraction unit 32 determines whether or not the flow item read in step S502 is connected to the route traced so far. When the flow item is connected to the previous flow item (step S506: YES), the route extraction unit 32 determines that the route that has been followed is correct and advances the process to step S507. Further, when the flow item is not connected to the previous flow item (step S506: NO), the route extraction unit 32 determines that the route that has been followed is not correct, and advances the processing to step S510.

  Next, in step S507, the route extraction unit 32 employs the flow item route. That is, the route extraction unit 32 adds the flow item read in step S502 to the route.

  Next, the route extraction unit 32 updates the branch pointer (step S508). That is, the path extraction unit 32 adds (increments) “1” to the branch pointer in order to move to the search for the next branch.

  Next, the path extraction unit 32 stores the reference source design document information in the verification storage unit 40 (step S509). Here, the reference source design document information is information for identifying the reference source design document information, and the path extracting unit 32 stores the reference source design document information in the verification storage unit 40 as return destination information. Let

  Next, the route extraction unit 32 determines whether there is a next flow item (step S510). If there is a next flow item, the route extraction unit 32 returns the process to step S502 and reads the next flow item. In addition, the route extraction unit 32 ends the process when there is no next flow item. Thereby, the route extraction unit 32 finishes creating a route along the branch pattern of one route. The route extraction unit 32 executes the route generation process from step S501 again for the next branch pattern.

  In step S511 in the case where there is no transition to other design document information (reference design document information), the path extraction unit 32 determines whether or not the flow item is connected to the previous flow item. This process is the same as the process in step S506 described above. When the flow item is connected to the previous flow item (step S511: YES), the route extraction unit 32 determines that the route that has been followed is correct, and the process proceeds to step S512. In addition, when the flow item is not connected to the previous flow item (step S511: NO), the route extraction unit 32 determines that the route that has been followed is not correct, and advances the processing to step S510.

  Next, in step S512, the path extraction unit 32 determines whether or not the return is from other specification information (reference design document information). If the route extraction unit 32 is a return from other design document information (reference design document information) (step S512: YES), the process proceeds to step S513. In addition, the route extraction unit 32 advances the processing to step S514 when the return is not from other design document information (reference design document information) (step S512: NO).

  Next, in step S513, the path extraction unit 32 deletes the stored reference source design document information from the verification storage unit 40. Here, since it has returned from other design document information (reference design document information), the path extraction unit 32 deletes the reference source design document information stored in the verification storage unit 40 in step S509.

  Next, in step S514, the route extraction unit 32 employs the flow item route. That is, the route extraction unit 32 adds the flow item read in step S502 to the route.

  Next, the route extraction unit 32 updates the branch pointer (step S515). That is, the path extraction unit 32 adds (increments) “1” to the branch pointer in order to move to the search for the next branch. The route extraction unit 32 advances the process to step S510 after the process of step S515 is completed.

Next, an example of the route extracted by the route extraction process described above by the route extraction unit 32 will be described.
18 and 19 are schematic diagrams showing an example of route extraction in the present embodiment.
The example shown in FIG. 18 shows an example when there is no branching of processing. FIG. 18A shows a “processing flow” of the flow information sheet ST1, and a flowchart F4 shows a procedure of “1. reading processing” → “2. Writing processing” → “3. Updating processing”. . The route extraction unit 32 analyzes the flow information sheet ST1 and the basic information sheet ST2, and generates information indicating the route as shown in FIG. Then, the route extraction unit 32 creates a route as shown in FIG. 18C based on the information shown in FIG. 18B and stores the route in the verification storage unit 40.

  In addition, the example illustrated in FIG. 19 illustrates an example in which a process includes a branch. FIG. 19A shows a “processing flow” of the flow information sheet ST1, and a flowchart F5 shows “1. processing A”, “branch”, “2. processing B”, “3. processing C”, and “ 4 shows a processing procedure having “Process D”. In this case, two routes, a route K1 and a route K2, are conceivable. The route extraction unit 32 analyzes the flow information sheet ST1 and the basic information sheet ST2, and generates a branch pattern between the route K1 and the route K2. Then, the route extraction unit 32 creates “route 1” shown in FIG. 19B and “route 2” shown in FIG. 19C based on the generated branch pattern. Here, “Route 1” is a route of “1. Process A” → “2. Process B” → “4. Process D”, and “Route 2” is “1. Process A” → “2”. .. Process C "→" 4. Process D ". The route extraction unit 32 stores the created routes (“route 1” and “route 2”) in the verification storage unit 40.

<Access order verification process>
Next, a detailed procedure of the access order verification process, which is the process in step S105 of FIG. 13, will be described.
FIG. 20 is a flowchart illustrating an example of access order verification processing according to the present embodiment. FIG. 21 is an image diagram showing an example of access order verification processing in the present embodiment.
The process shown in FIG. 20 is a process executed for one of the plurality of routes extracted by the route extraction unit 32, and the DB access verification unit 33 performs the process shown in FIG. The access order in a plurality of routes is verified by sequentially executing each route.

  In FIG. 20, first, the DB access verification unit 33 acquires the number of the process at the starting point of the route (step S601). That is, the DB access verification unit 33 acquires the “number” of the first process in the flow information sheet ST1 of the starting point design document information as the starting point. For example, in the flow information sheet ST1 shown in FIG. 21A, the process that is the starting point of the flowchart F6 is “1.XXX processing service”. In this case, the DB access verification unit 33 sets “number” as “ 1 ”is acquired.

  Next, the DB access verification unit 33 searches the acquired “number” from the content table of the basic information sheet ST2 (step S602). For example, when the acquired “number” is “1”, the DB access verification unit 33, as shown in FIG. 21B, “in” in the “order” of the basic information sheet ST2 (“content” table). Search for “1”. In this case, the “processing procedure” whose “order” is “1” corresponds to “XX processing service”.

  Next, the DB access verification unit 33 analyzes the character string in the corresponding detail column (“details”) (step S603). That is, the DB access verification unit 33 analyzes the reference destination stored in the “details” of the process in the “content” table corresponding to the acquired “number”. In the example illustrated in FIG. 21B, “Details” stores a character string “refer to acquisition information (acquisition table 1)”.

Next, the DB access verification unit 33 determines whether or not the character string is a reference to a DB (database) (step S604). That is, the DB access verification unit 33 determines whether the reference destination indicated by the character string “details” is the acquisition information sheet ST3 or the output information sheet ST4. The character string includes “acquired information” when the reference destination is the acquisition information sheet ST3, and includes “output information” when the reference destination is the output information sheet ST4.
For example, in the example shown in FIG. 21B, the character string “refer to the acquisition information (acquisition table 1)” is stored in the “detail” corresponding to the “order” “1”. This indicates that the information sheet ST3 is being referred to.
When the character string is a reference to a DB (database) (step S604: YES), the DB access verification unit 33 advances the process to step S605. If the character string is not a reference to the DB (database) (step S604: NO), the DB access verification unit 33 advances the process to step S607.

  Next, in step S605, the DB access verification unit 33 acquires the table name (“acquisition source”) and “access type” from the reference destination information sheet. For example, in the example illustrated in FIG. 21C, the DB access verification unit 33 acquires “acquisition table 1” as the table name from the acquisition information sheet ST3 that is the reference destination information sheet, and “access type” as “access type”. Get “Reference with update”. As described above, the acquisition information sheet ST3 can set a plurality of table names (“acquisition source”). When a plurality of table names (“acquisition source”) are set in the acquisition information sheet ST3, the DB access verification unit 33 acquires a plurality of table names in order from the top table name.

  Next, the DB access verification unit 33 acquires the order number of the corresponding table from the reference access order information (step S606). That is, the DB access verification unit 33 obtains the “access order” (order number) corresponding to the table name acquired in step S605 from the reference access order information (ST6 in FIG. 11) stored in the access order storage unit 20. For example, in the reference access order information shown in FIG. 11, the “access order” corresponding to “acquisition table 1” is “1”, and the DB access verification unit 33 acquires “1” as the order number.

  Next, the DB access verification unit 33 stores the extracted access order information in the verification storage unit 40 (step S607). Specifically, as illustrated in FIG. 12B, the DB access verification unit 33 acquires the acquired “processing procedure” (processing name), “access type”, table name, and “access order” (order number). ) Are stored in the verification storage unit 40 as access information. In this way, the DB access verification unit 33 uses the access information that associates the table name of the database accessed in the route and the order number corresponding to the table name in the reference access order information as the extracted access order information. Is stored in the verification storage unit 40.

  Next, the DB access verification unit 33 determines whether there is a next process of the route (step S608). That is, the DB access verification unit 33 determines whether there is a next process based on the route extracted by the route extraction unit 32. When there is the next process (step S608: YES), the DB access verification unit 33 advances the process to step S609. If there is no next process (step S608: NO), the DB access verification unit 33 advances the process to step S610.

  Next, in step S609, the DB access verification unit 33 acquires the number of the next process. That is, the DB access verification unit 33 acquires the “number” of the next field process in the route extracted by the route extraction unit 32, and returns the process to step S602.

  In step S610, the DB access verification unit 33 determines whether the order number of the table is in ascending order. In this case, there is no next process, and extraction of the extracted access order information for one route is completed. The DB access verification unit 33 refers to the access information sheet ST42 stored in the verification storage unit 40 as shown in FIG. 12B, and determines whether the “access order” (order number) is in ascending order. judge. When the “access order” (order number) is in ascending order (step S610: YES), the DB access verification unit 33 advances the process to step S611. If the “access order” (order number) is not in ascending order (step S610: NO), the DB access verification unit 33 advances the process to step S612.

In step S611, the DB access verification unit 33 determines that the extracted access order information matches the reference access order information, and the verification result output unit 34 stores the verification result in the verification storage unit 40. After the verification result output unit 34 stores the verification result in the verification storage unit 40, the DB access verification unit 33 ends the access order verification process. The verification result stored by the verification result output unit 34 is, for example, “result” of the access information sheet ST42.
As described above, when the access information sequence numbers in the verification storage unit 40 are stored in ascending order, the DB access verification unit 33 matches the extracted access order information in the path with the reference access order information. Is determined.

  In step S612, the DB access verification unit 33 determines that the extracted access order information and the reference access order information are not consistent (inconsistent), and the verification result output unit 34 verifies the verification result. The data is stored in the storage unit 40. After the verification result output unit 34 stores the verification result in the verification storage unit 40, the DB access verification unit 33 ends the access order verification process.

  As described above, the DB access verification unit 33 sequentially performs the access order verification processing illustrated in FIG. 20 for each of a plurality of paths. When the access order verification processing is completed for all routes, the verification result output unit 34 generates information on the verification result sheet ST41 corresponding to each route based on the access information sheet ST42 corresponding to each route. To do. Then, the verification result output unit 34 causes the verification storage unit 40 to store the information of the generated verification result sheet ST41.

As described above, the database access verification method according to the present embodiment includes the path extraction step and the verification step. In the route extraction step, the route extraction unit 32 acquires design document information from the design document storage unit 10 that stores design document information that defines the procedure of information processing in software, and performs information processing based on the acquired design document information. Extract the path. In the verification step, the DB access verification unit 33 (verification unit) extracts the extracted access order information indicating the access order of the database in the route extracted in the route extraction step, and extracts the extracted access order information and the access order. It is verified whether or not the reference access order information acquired from the storage unit 20 (order storage unit) matches. The access order storage unit 20 stores reference access order information indicating a predetermined order for accessing the database.
As a result, the order of accessing the database can be verified in the design stage (for example, the design document stage), so the database access verification method in the present embodiment can verify the database deadlock in the design stage. . Further, in the database access verification method according to the present embodiment, the database access verification is executed by the path extraction unit 32 and the DB access verification unit 33, so that, for example, compared to the case where the database access order is confirmed manually and visually. And can be verified without omission.

  Further, since the database access verification method in the present embodiment can verify the database deadlock in the design stage, for example, when it is found that the database deadlock occurs in the verification in the implementation stage or the test stage. The number of reworking steps can be reduced. Further, the database access verification method in the present embodiment can shorten the software design period by reducing rework.

Further, in the present embodiment, the design document information operates a flow diagram visualizing the information processing procedure, the information processing procedure, the table name of the database accessed in the information processing, and the database accessed in the information processing. An access type indicating the type is included in association with each other. In the route extraction step, the route extraction unit 32 extracts a route based on the flowchart and the information processing procedure. In the verification step, the DB access verification unit 33 extracts the extracted access order information in the route based on the route extracted in the route extraction step, the information processing procedure, the table name, and the access type.
As a result, the database access verification method according to the present embodiment performs database access verification based on the design document information including the flowchart used for software design, the information processing procedure, the database table name, and the access type. Do. Therefore, it is not necessary to separately create input information for verification, and a design document used for software design can be used. Therefore, the database access verification method in the present embodiment can improve the work efficiency of software design and verification.

In the present embodiment, in the route extraction step, the route extraction unit 32 extracts a plurality of routes according to the branching process included in the flowchart. In the verification step, the DB access verification unit 33 verifies whether the extracted access order information in each path matches the reference access order information for each of the plurality of paths.
As a result, the database access verification method according to the present embodiment verifies the access order for a plurality of paths according to the branch process, so that the path according to the branch process is verified without omission at the design stage. be able to.

In the present embodiment, the reference access order information includes a database table name and a sequence number indicating an access sequence corresponding to the table name. In the verification step, the DB access verification unit 33 verifies the access information associating the table name of the database accessed in the route with the sequence number corresponding to the table name in the reference access order information in the order of the route as the access order. It is stored in the storage unit 40. Then, the DB access verification unit 33 determines that the extracted access order information in the route matches the reference access order information when the sequence numbers of the access information in the verification storage unit 40 are stored in ascending order. To do.
As a result, the database access verification method in the present embodiment can determine the result based on whether or not the sequence number of the access information stored in the verification storage unit 40 is in ascending order. Access verification can be performed.

In the present embodiment, the design document information includes acquisition information related to data acquisition from the database (for example, acquisition information sheet ST3), and output information related to data output to the database (for example, output information sheet ST4). Is included.
As a result, the database access verification method in the present embodiment can provide separate criteria for access verification for acquiring data from the database and access verification for outputting data to the database.

In the present embodiment, in the route extraction step, the route extraction unit 32 performs a first extraction step of extracting a combination of branch patterns based on the design document information, and a plurality of routes corresponding to the extracted branch patterns. A second extraction step to be created is executed.
Thereby, since the database access verification method according to the present embodiment creates a route based on the previously extracted branch pattern, there is no need to determine a branch when creating a route. Therefore, the database access verification method according to the present embodiment can simplify the process of creating a route and reduce the processing time for creating a route.

In the present embodiment, in the first extraction step of extracting a combination of branch patterns, the route extraction unit 32 determines the first branch and the branch included in the specification information that is the starting point based on the specification information. And the number of combinations of branch patterns is reduced based on the first branch extracted and the branch included in the specification information that is the starting point.
As a result, the route extraction unit 32 can reduce the storage capacity of the storage unit used when creating the route, and can reduce the amount of calculation when creating the route, thereby shortening the processing time. .

Further, according to the present embodiment, the DB access verification device 1 includes the path extraction unit 32 and the DB access verification unit 33. The route extraction unit 32 acquires design document information from the design document storage unit 10, and extracts a route for information processing including access to the database based on the acquired design document information. Then, the DB access verification unit 33 extracts the extracted access order information indicating the database access order in the information processing path extracted by the path extraction unit 32, and the extracted access order information and the access order storage unit 20 It is verified whether or not the stored reference access order information indicating a predetermined order of accessing the database matches.
Thereby, the DB access verification apparatus 1 in this embodiment has the same effect as the database access verification method in this embodiment.

[Second Embodiment]
Next, a database access verification apparatus and a database access verification method according to the second embodiment will be described with reference to the drawings.
FIG. 22 is a block diagram illustrating an example of a database access verification apparatus (DB access verification apparatus 1a) according to the second embodiment. In this figure, the same components as those in FIG. 1 are denoted by the same reference numerals, and the description thereof is omitted.

  In the DB access verification apparatus 1a according to the present embodiment, the control unit 30a includes a collective verification control unit 35, and performs batch access verification on design document information serving as a plurality of starting points for each software to be designed. This is different from the DB access verification device 1 in the first embodiment. Note that the DB access verification apparatus 1a includes a batch verification mode in which database access verification is performed in batch, and a selection verification mode in which verification is performed after design document information as a starting point similar to that in the first embodiment is selected. May be switched and executed by designation from the user (software designer).

22, the DB access verification device 1a includes a design document storage unit 10, an access order storage unit 20, a control unit 30a, and a verification storage unit 40a.
The control unit 30 a includes a pre-check unit 31, a path extraction unit 32, a DB access verification unit 33, a verification result output unit 34, and a collective verification control unit 35.

  The collective verification control unit 35 analyzes the design document information stored in the design document storage unit 10, and extracts starting design document information as a starting point of, for example, the online processing design document information 11 in the software to be designed. The collective verification control unit 35 causes the pre-check unit 31, the path extraction unit 32, the DB access verification unit 33, and the verification result output unit 34 to perform database access verification using the extracted starting point design document information as a starting point. Take control. The collective verification control unit 35 performs control to execute database access verification for each of the plurality of origin design document information when a plurality of origin design document information is extracted.

In addition to the verification result sheet ST41 and the access information sheet ST42 described in the first embodiment, the verification storage unit 40a in the present embodiment stores a batch verification result sheet ST43 illustrated in FIG. 23 as a verification result. Yes.
FIG. 23 is a diagram illustrating an example of a collective verification result in the present embodiment.
As shown in FIG. 23, the collective verification result sheet ST43 has “item number”, “deliverable name”, “number of errors”, and “result”. Here, the “product name” indicates, for example, the name of the origin design document information. The “number of errors” indicates the number of design document information in which errors are detected in the preliminary check by the preliminary check unit 31. This “number of errors” includes the number of errors in the basic information sheet ST2 and the number of errors in the flow information sheet ST1.

  “Result” indicates a verification result of database access verification, and includes “◯” and “×”. “O” in “Result” indicates the number of “O” determined among the routes extracted by the route extracting unit 32, and “X” in “Result” is indicated by the route extracting unit 32. Of the extracted routes, the number determined as “×” is shown. If an error occurs in the pre-check, the DB access verification apparatus 1a does not perform database access verification. In this case, both “O” and “X” of “Result” are “0”. .

  In the example shown in FIG. 23, the “product name” corresponding to “1” of “item number” is “01_processing design document”, and “basic information” of “number of errors” is “2”. , “Flow information” of “Error count” is “0”. Also, the “product name” corresponding to “7” of “item number” is “XX processing design document”, “basic information” and “flow information” of “number of errors” are “0”, “◯” in “Result” is “5”, and “X” in “Result” is “4”.

Next, the operation of the DB access verification device 1a in this embodiment will be described.
FIG. 24 is a flowchart illustrating an example of batch verification processing in the present embodiment.
In FIG. 24, first, the control unit 30a of the DB access verification device 1a executes a starting point design document information extraction process (step S701). Specifically, the collective verification control unit 35 of the control unit 30a extracts starting point design document information as a starting point, such as the online processing design document information 11, for example.

  The collective verification control unit 35 performs control for executing database access verification in the subsequent processing from step S703 to step S706 for the extracted starting point design document information. Note that the processing from step S703 to step S706 is the same as the processing from step S101 to step S105 shown in FIG.

  Next, in step S707, the collective verification control unit 35 determines whether there is next starting point design document information. If there is next origin design document information (step S707: YES), the collective verification control unit 35 advances the process to step S708. Further, when there is no next starting point design document information (step S707: NO), the collective verification control unit 35 advances the process to step S709.

  In step S708, the collective verification control unit 35 changes the starting point design document information and returns the process to step S702. Thus, the collective verification control unit 35 performs control to execute database access verification for the next starting point design document information.

  In step S708, the batch verification control unit 35 outputs the batch verification result and ends the process. That is, the collective verification control unit 35 generates a collective verification result (collective verification result sheet ST43) as shown in FIG. 23, and stores the generated collective verification result in the verification storage unit 40a.

As described above, the DB access verification device 1a according to the present embodiment includes the collective verification control unit 35. The collective verification control unit 35 performs control for collectively performing database access verification on design document information that is a plurality of starting points for each predetermined unit of software (for example, for each software to be designed).
Thereby, the DB access verification apparatus 1a and the database access verification method according to the present embodiment can perform database access verification collectively for each predetermined unit of software. In this case, since it is not necessary to select the design document information as a starting point for each database access verification, the DB access verification apparatus 1a and the database access verification method in this embodiment shorten the period for executing the database access verification. be able to.

The present invention is not limited to the above embodiments, and can be modified without departing from the spirit of the present invention.
For example, in each of the embodiments described above, the DB access verification device 1 (1a) has been described as including the design document storage unit 10, the access order storage unit 20, and the verification storage unit 40 (40a). The unit 10, the access order storage unit 20, and the verification storage unit 40 (40a) may be provided in an external device such as a server device, for example. The control unit 30 (30a) may be a computer device such as a client terminal or an application server, for example.

In each of the above embodiments, the design document storage unit 10, the access order storage unit 20, and the verification storage unit 40 (40a) have been described as being individually configured. Any combination of the unit 20 and the verification storage unit 40 (40a) may be configured as one.
Further, in each of the above embodiments, the case of verifying the access order in units of tables has been described. However, the access order may be verified in units of columns in the table.

  In the second embodiment described above, when the design document storage unit 10 stores design document information corresponding to a plurality of software, the collective verification control unit 35 selects one of the plurality of softwares. Depending on the selected software, the database access verification may be executed in the batch verification mode.

The program for realizing the function of the DB access verification device 1 (1a) in the present invention is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed. Accordingly, the processing of the DB access verification device 1 (1a) described above may be performed. Here, “loading and executing a program recorded on a recording medium into a computer system” includes installing the program in the computer system. The “computer system” here includes an OS and hardware such as peripheral devices.
Further, the “computer system” may include a plurality of computer devices connected via a network including a communication line such as the Internet, WAN, LAN, and dedicated line. The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. As described above, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM. The recording medium also includes a recording medium provided inside or outside that is accessible from the distribution server in order to distribute the program.
Note that the program may be divided into a plurality of parts and downloaded at different timings, and the DB access verification apparatus 1 (1a) may be combined, or the distribution server that distributes each of the divided programs may be different. Furthermore, the “computer-readable recording medium” holds a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that becomes a server or a client when the program is transmitted via a network. Including things. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, what is called a difference file (difference program) may be sufficient.

  Moreover, you may implement | achieve part or all of the function mentioned above as integrated circuits, such as LSI (Large Scale Integration). Each function described above may be individually made into a processor, or a part or all of them may be integrated into a processor. Further, the method of circuit integration is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. In addition, when an integrated circuit technology that replaces LSI appears due to the advancement of semiconductor technology, an integrated circuit based on the technology may be used.

DESCRIPTION OF SYMBOLS 1, 1a DB access verification apparatus 10 Design document memory | storage part 11 Online process design document information 12 Service system design document information 13 Parameterized logic design document information 20 Access order memory | storage part 30, 30a Control part 31 Prior check part 32 Path | route extraction part 33 DB access verification unit 34 Verification result output unit 35 Batch verification control unit 40, 40a Verification storage unit

Claims (6)

A route extraction unit acquires the design document information from a design document storage unit that stores design document information that defines a procedure of information processing in software, and extracts the information processing path based on the acquired design document information Route extraction step to
The verification unit extracts the extracted access order information indicating the access order of the database in the route extracted by the route extracting step, and indicates the extracted access order information extracted and the predetermined order of accessing the database And a verification step of verifying whether or not the reference access order information acquired from the order storage unit that stores the reference access order information is consistent. The design document information includes a flow diagram visualizing the information processing procedure, the information processing procedure, the table name of the database accessed in the information processing, and the type of operating the database accessed in the information processing. Associated with the access type shown,
In the route extraction step, the route extraction unit extracts the route based on the flowchart and the information processing procedure,
In the verification step, the verification unit extracts the extracted access order information based on the path extracted in the path extraction step, the information processing procedure, the table name, and the access type. The database access verification method according to claim 1, wherein: In the route extraction step, the route extraction unit extracts a plurality of the routes according to a branch process included in the flow diagram,
In the verification step, the verification unit verifies, for each of the plurality of paths, whether or not the extracted access order information in each path matches the reference access order information. Item 3. The database access verification method according to Item 2. The reference access order information includes a database table name and an order number indicating an access order corresponding to the table name,
In the verification step, the verification unit uses, as the extracted access order information, access information that associates a table name of a database to be accessed in the path with the sequence number corresponding to the table name in the reference access order information. When the sequence number of the access information in the verification storage unit is stored in the ascending order, the extracted access sequence information and the reference access sequence information are matched. The database access verification method according to any one of claims 1 to 3, wherein the database access verification method is determined. The design document information is acquired from a design document storage unit that stores design document information that defines a procedure of information processing in software, and the information processing path including access to a database is obtained based on the acquired design document information. A route extraction unit to extract;
Extracted extracted access order information indicating the database access order in the information processing path extracted by the path extraction unit, and the extracted access order information extracted and a reference indicating a predetermined order for accessing the database A database access verification apparatus comprising: a verification unit that verifies whether or not the reference access sequence information acquired from the sequence storage unit that stores the access sequence information matches. On the computer,
The path extraction unit acquires the design document information from a design document storage unit that stores design document information that defines a procedure of information processing in software, and includes access to a database based on the acquired design document information. A route extraction step for extracting a route for information processing;
The verification unit extracts the extracted access order information indicating the access order of the database in the route extracted by the route extracting step, and indicates the extracted access order information extracted and the predetermined order of accessing the database And a verification step for verifying whether or not the reference access order information acquired from the order storage unit for storing the reference access order information matches.

Images