JP4630640B2 - Design information verification apparatus and design information verification method - Google Patents

Description

  The present invention relates to a design information verification apparatus and a design information verification method for verifying design information of software to be developed in order to ensure the quality of the design information.

  Generally, a software design tool incorporates a design information verification function. The verification function built into such a design tool is limited to verification in a large framework such as consistency between diagrams. For example, the relationship of classes related to one screen transition However, it does not perform verification that goes into the details of the design.

A system that supports verification of association between classes classified into models by posting interaction information between classes to the designer as a method for verification that goes into detailed design details. (For example, refer to Patent Document 1).
JP 2004-110415 A

  However, the technique of Patent Document 1 does not automatically verify design information. Therefore, a method of defining design information verification rules in advance and automatically verifying design information in accordance with the verification rules can be considered. In this case, between the expression of the rule and the design information It is necessary to ensure consistency. However, since the definition of the schema for managing the design information is usually different for each department or project, it is difficult to realize a general-purpose verification apparatus that verifies design information using verification rules.

  The present invention has been made in view of the above points, and a design information verification apparatus and design information that can perform design information verification automatically and without depending on the definition of the schema of the design information. The purpose is to provide a verification method.

  In order to solve the above problems, the design information verification apparatus of the present invention describes design information related to one screen transition in each of a plurality of items to which information of the first schema is assigned. Design information storage means for storing design information including a design specification in a tabular format that defines mapping between the schema information of the first schema and the second schema information of the design information, and the first schema information The verification rule storage means storing the verification rule for verifying the design information, and when the verification instruction for the design information stored in the design information storage means occurs, the verification rule stored in the verification rule storage means The verification means for changing to the verification rule using the information of the second schema based on the mapping defined in the design specification, and verifying the design information by the changed verification rule It is intended to include a.

  According to the design information verification apparatus and the design information verification method of the present invention, design information can be verified automatically and without depending on the definition of the schema of the design information.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a block diagram showing the overall configuration of a design information verification apparatus according to an embodiment of the present invention.

  As shown in the figure, the design information verification apparatus 100 includes an overall control unit 1, an input control unit 2, an output control unit 3, a design information selection / input unit 4, a design information verification unit 5, a design information database (hereinafter referred to as a design information database). , Design information DB and description) 6, design information verification rule database (hereinafter referred to as design information verification rule DB) 7, design information metadata database (hereinafter referred to as design information metadata DB) 8 and the like. Specifically, the design information verification apparatus 100 includes computer hardware elements such as a CPU (Central Processing Unit), a memory, an HDD (Hard Disk Drive), an input device, an output device, an OS (Operating System), and the like. It consists of software elements such as application programs that run on the above. The design information DB 6, the design information verification rule DB 7, and the design information metadata DB 8 are constructed in a storage unit that is hardware such as a computer system memory or HDD.

  The overall control unit 1 controls the exchange of data and commands among the input control unit 2, the output control unit 3, the design information selection / input unit 4, and the design information verification unit 5. The input control unit 2 controls input from an input device such as a keyboard and a mouse (not shown). The output control unit 3 performs control to display design information, design information verification rules, verification results, and the like on a display device (not shown). The design information selection / input unit 4 is a means for executing commands such as storing design information in the design information DB 6 and selecting or updating design information stored in the design information DB 6. The design information verification unit 5 is means for verifying design information in accordance with the design information verification rules stored in the design information verification rule DB 7. The design information DB 6 is a database that stores design information. The design information verification rule DB 7 is a database in which rules for verifying the design information are stored. The design information metadata DB 8 is a mapping between a standard schema (first schema information) used for design information verification rule expression and a schema (second schema information) used for design information expression. This is a database in which information (design information metadata) for defining a file is stored.

  FIG. 2 is a block diagram showing a configuration of the design information verification unit 5.

  As shown in the figure, the design information verification unit 5 includes a verification engine 11, a design information expansion unit 12, a verification rule expansion unit 13, and a design verification execution unit 14.

  The verification engine 11 is a unit that controls input / output with the outside and comprehensively controls the operations of the design information expansion unit 12, the verification rule expansion unit 13, and the design verification execution unit 14. The verification engine 11 converts the design information designated as the verification target into a data structure suitable for the verification process in the design verification execution unit 14 and expands the design information in the design information expansion unit 12. Further, the verification engine 11 changes the design information verification rule read from the design information verification rule DB 7 into an expression that matches the schema of the design information and expands it in the verification rule expansion unit 13. The verification engine 11 reads out the design information expanded in the design information expansion unit 12 and the design information verification rule expanded in the verification rule expansion unit 13 for verification, and gives them to the design verification execution unit 14. The design verification execution unit 14 receives design information and design information verification rules from the verification engine 11, and executes verification of design information based on the design information verification rules.

Next, design information will be described.
The design information includes, in addition to design information in which use case diagrams and screen transition diagrams are made into a database, a table-type design specification in which classes related to one screen transition are arranged in one line.

  FIG. 3 is an example of a use case diagram. This use case is based on a membership-based online purchasing system. In this system, the user registration, the change of user information, and the withdrawal process are not performed directly by the user on-line, but are requested by the postal mail. For this reason, the user management 41 is performed by the customer staff 42 who receives the notification by mail. Purchases online can be made directly by the user 43 via the Internet, but for customers who do not have an Internet environment or who are temporarily unavailable, they can accept purchase applications over the phone. And In this case, instead of the user himself / herself, the customer staff 42 inputs the purchase. For this reason, the online purchase 44 can be performed by the user 43 and the customer staff 42. Here, the user management 41 and online purchase 44 correspond to use cases, the customer representative 42, and the user 43 correspond to actors.

  FIG. 4 is a diagram showing schema information and design information of the use case diagram shown in FIG. As shown in the figure, the schema information of the use case diagram shown in FIG. 3 includes a schema 51 that expresses a use case, a schema 52 that expresses an actor, and a schema 53 that expresses a relationship between them. A schema 51 representing a use case includes a use case ID and a use case name. A schema 52 representing an actor includes an actor ID and an actor name. The schema 53 that expresses the relationship includes a use case ID, an actor ID, and information indicating the types of these relations. 51A, 52A, and 53A are design information in which the use case diagram of FIG. 3 is databased based on these schemas.

  FIG. 5 is an example of a screen transition diagram regarding a part of the use case of the user management 41 in the use case diagram shown in FIG. In this example, a user information management menu 61 is displayed as an initial menu. By pressing the “User Registration” button on the user information management menu 61, the screen display is switched to the user information input screen 62. When the user information to be newly registered is input on the user information input screen 62 and the “registration” button is pressed, the screen further transits to the user information registration confirmation screen 63. Confirm the input contents on this screen, and press the “Confirm” button when it is confirmed that it is correct. Thereby, the user registration process is actually executed. When the user registration process ends normally, the screen transitions to a user information registration completion screen 64. When the user registration process ends abnormally, the screen transitions to a user registration error screen 65.

  FIG. 6 is a diagram showing schema information and design information of the screen transition diagram shown in FIG. As shown in the figure, the schema information of the screen transition diagram shown in FIG. 6 includes a schema 71 representing each of the screens 61, 62, 63, 64, 65 and a schema representing transitions between these screens. 72. A schema 71 representing a screen is composed of a drawing ID and its screen name. The schema 72 expressing the transition between screens includes a drawing ID, a transition source screen ID, a transition destination screen ID, a screen transition trigger, and a transition condition. 71A and 72A are design information obtained by converting the screen transition diagram of FIG. 6 into a database based on these schemas.

  In the design information DB 6, in addition to the above-described use case diagram and design information in which the screen transition diagram is made into a database, as shown in FIG. 7, there is a tabular design specification in which classes related to one screen transition are arranged in one line. Stored.

  The tabular design specification shown in FIG. 7 is developed based on the information for defining the mapping between the standard schema and the schema of the design information stored in the design information metadata DB 8 as shown in FIG. It was created by the person 9. Information for mapping the schema is given in the form of a table in which standard schema information is assigned to each item. Developer 9 does not match the information of the standard schema assigned to each item in this table with the schema information of design information, so each class describes a class related to one screen transition. Create a tabular design specification in a single line. In general, the definition of a schema for managing design information differs for each department or project. On the other hand, since the design information verification rule is created based on the standard schema, it cannot be used as it is for verification of the design information. Therefore, by creating a tabular design specification based on the schema mapping information shown in FIG. 8, mapping between design information schema information and standard schema information is defined. Independent verification is realized.

  According to the design specification of FIG. 7, the “use case” in the standard schema corresponds to “register and manage user information” and “purchase online” in the schema of the design information, and the “actor” in the standard schema is the schema of the design information. Corresponding to "Customer" and "Customer management" in the standard schema "Request generation screen" "Transition destination screen" is "User information management menu" "User information input screen" "User information registration confirmation screen" of design information schema Corresponding to “User information registration completion screen” and “User registration error screen”, “Request” of standard schema is a trigger for screen transition of design information schema “User registration” button pressed “Register” button pressed Corresponding to “Pressing the“ Confirm ”button” or “Pressing the“ Return to menu ”button”, the “Transition condition” of the standard schema is “Registered” It is defined that corresponds to the "" registration abnormal ".

  A plurality of pieces of information for schema mapping are facilitated, and the developer 9 can specify mapping information to be used in the schema 9 by the number. The design information shown in FIG. 7 is created based on the mapping information of number = 1. FIG. 9 is an example of design information created based on the mapping information of number = 2.

  FIG. 10 is a diagram illustrating an example of the design information verification rule. In this example, the design information verification rule is written in Japanese, but in reality, the process can be patterned, and the definition in the natural language is not essential.

  The rule of number 1 is a verification item of contents related to the use case of design information. The use case to be verified in the design information of FIG. 7 is only one item “register and manage user information”. The comparison target is a “use case diagram”, and the verification content is “the corresponding use case is defined”. Whether or not the corresponding use case is defined can be verified by referring to the use case diagram database (FIG. 4).

  The rule of number 2 is a verification item of the contents related to the actor of the design information. In the design information of FIG. 7, the actor to be verified is only one item of “customer management charge”. The comparison target is “use case diagram” and the verification content is “corresponding actor is defined”. Whether or not the corresponding actor is defined can be verified by referring to the use case diagram database (FIG. 4).

  The rule of number 3 is a verification item for the contents related to the request generation screen. The comparison target is a “screen transition diagram”, and the verification content is “the relevant screen is defined”. Whether or not the corresponding request generation screen is defined can be verified by referring to the screen transition diagram database (FIG. 6).

  The rule of number 4 is a verification item of contents related to the transition destination screen. The comparison target is a “screen transition diagram”, and the verification content is “the relevant screen is defined”. Whether or not the corresponding transition destination screen is defined can be verified by referring to the screen transition diagram database (FIG. 6).

  The rule of number 5 is a verification item of contents related to the screen transition condition. The comparison target is “service”, and the verification content is “if there is a transition condition, the service is defined”. The fact that there is a condition for transitioning the screen means that there is a process for generating some branch before that. For this reason, in the third and fourth lines where the transition condition is described in FIG. 7, the “service” that is the main body of the process must be described in the same line.

  The rule of number 6 is a verification item of contents related to the request generation screen. The comparison target is “transition destination screen”, and the verification content is “request generation screen is any transition destination screen”. Whether or not the request generation screen is any of the transition destination screens can be verified by referring to the database (FIG. 6) of the screen transition diagram.

Next, the operation of the design information verification apparatus 100 will be described.
FIG. 11 is a flowchart of the design information verification operation performed by the design information verification apparatus 100.

  First, the developer 9 selects design information to be verified (step 101). Specifically, this selection is performed by the developer 9 inputting a command for selecting design information to be verified by operating an input device such as a keyboard or a mouse (not shown). The overall control unit 1 receives the command through the input control unit 2 and passes it to the design information selection / input unit 4. Based on the command, the design information selection / input unit 4 reads the design specifications in tabular form from the design information DB 6.

  The tabular design specifications read from the design information DB 6 are displayed on a display device (not shown) via the output control unit 3 (step 102). At this time, a verification execution button for instructing execution of verification for the design information being displayed is displayed on the display screen. When the verification execution button is operated by the developer 9, the overall control unit 1 performs design information verification. A verification execution command is given to the unit 5 (step 103).

  Upon receiving the verification execution command, the design information verification unit 5 converts the design information read from the design information DB 6 by the design information selection / input unit 4 into a data structure suitable for verification by the verification engine 11. The design information is expanded in the design information expansion unit 12 (step 104), the design information verification rule is read from the design information verification rule DB 7 (step 105), and the description of the design information verification rule is stored in the standard schema defined in the design specification. Based on the mapping between the information and the schema information of the design information, the expression is changed to an expression using the schema information of the design information (step 106), and is expanded in the verification rule expansion unit 13.

  For example, the rule of number 1 in FIG. 10 that “the corresponding use case is defined” is “the user information is registered and managed but is defined” and “online purchase is defined”. Changed to expression. The rule “number 2 is defined” is changed to the expression “customer is defined” and “customer manager is defined”. The rule “number 3 is defined” is changed to “whether the user information management menu is defined”, “whether the user information input screen is defined” or the like.

  Subsequently, the design information verification unit 5 starts the verification engine 11 and starts a verification operation. The verification engine 11 gives the design information expanded in the design information expansion unit 12 and the design information verification rules expanded in the verification rule expansion unit 13 to the design verification execution unit 14 one by one, and executes design information verification. (Step 107). When the verification engine 11 acquires the result of verification by the design verification execution unit 14, the verification engine 11 returns the result to the overall control unit 1. The overall control unit 1 displays the received verification result on a display device (not shown) through the output control unit 3 and notifies the developer 9 (step 108). Here, in the verification, since it is known at which position according to which rule the error has occurred, the position of the design information in which the error has occurred and the error content can be included in the verification result and output.

  As described above, according to the design information verification apparatus 100 of this embodiment, design information verification is automatically performed according to a predefined rule, and use cases, actors, and requests that are related to individual screen transitions are generated. This can be done in fine units such as screens, transition destination screens, transition conditions, and request generation screens.

  In addition, according to the design information verification apparatus 100 of this embodiment, the mapping between the schema of the design information and the standard schema is defined by creating a tabular design specification based on the information for schema mapping. And verification independent of the schema of design information is realized.

  It should be noted that the present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the scope of the present invention.

It is a block diagram which shows the whole structure of the design information verification apparatus which concerns on one Embodiment of this invention. It is a block diagram which shows the structure of the design information verification part of FIG. It is a figure which shows the example of a use case figure. FIG. 4 is a diagram showing schema information and design information of the use case diagram shown in FIG. 3. FIG. 4 is a screen transition diagram regarding a part of a use case of user management in the use case diagram shown in FIG. 3. It is a figure which shows the schema information and design information of the screen transition diagram shown in FIG. It is a figure which shows the example of the design specification of a table format. It is a figure which shows the information for defining mapping with the schema of a standard schema and design information. It is a figure which shows the example of another design specification of a table format. It is a figure which shows the example of a design information verification rule. 3 is a flowchart of design information verification operation by the design information verification apparatus of FIG. 1.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 .... Overall control part 2 .... Input control part 3 .... Output control part 4 .... Design information selection / input part 5 .... Design information verification part 6 .... Design information DB
7 ... Design information verification rule DB
8 ... Design information metadata DB

Claims (4)

Design information related to one screen transition is described in each of the plurality of items to which the information of the first schema is assigned, and the information of the first schema and the information of the second schema of the design information Design information storage means for storing design information including a tabular design specification in which mapping is defined;
A verification rule storage means for storing a verification rule for verifying the design information, created using the information of the first schema;
When an instruction to verify the design information stored in the design information storage unit is generated, the verification rule stored in the verification rule storage unit is changed based on the mapping defined in the design specification. And a verification means for verifying the design information by using the changed verification rule.   The design information verification apparatus according to claim 1, wherein the verification rule stored in the verification rule storage unit is a rule for verifying the design information in units of the items.   Design information related to one screen transition is described in each of the plurality of items to which the information of the first schema is assigned, and the information of the first schema and the information of the second schema of the design information A table-like design specification defining the mapping is stored in the design information storage means, and a verification rule for verifying the design information created using the information of the first schema is verified rule storage means When a verification instruction for the design information is generated, the verification unit stores the verification rule stored in the verification rule storage unit based on the mapping defined in the design specification. 2. A design information verification method, wherein the verification information is changed to a verification rule using information of the schema 2 and the design information is verified by the changed verification rule.   4. The design information verification method according to claim 3, wherein the verification rule stored in the verification rule storage means is a rule for verifying the design information in units of the items.

Images