JP5470308B2 - Legal analysis support device, legal analysis support method, and legal analysis support program - Google Patents

Description

  The present invention relates to a legal analysis support apparatus that supports work for extracting requirements related to a system that performs processing related to laws and regulations from laws and regulations such as government ordinances and ministerial ordinances.

  Laws and regulations have a role as social specifications, and regulate social organizations and structures, goals and objectives, organizational activities and procedures. If you look at laws and regulations from organizations such as the national government, local governments, and companies, the laws can be said to be business specifications. Organizational work must be consistent with laws and regulations. In addition, when a part or all of the business is systemized, it is essential to ensure consistency with the law for the systemized part.

  System development based on laws and regulations is a work process (hereinafter referred to as “legal analysis process”) that extracts requirements (hereinafter referred to as “legal requirements”) specified in laws and regulations related to the target system. First, a requirement definition process, a design process, a manufacturing process, and a test process are sequentially performed.

  The legal analysis process is of course very important. The results of the legal analysis process affect all subsequent requirements definition processes, design processes, manufacturing processes, and test processes. Since the test process is performed on the premise of the result of the legal analysis process, if the legal analysis process is inadequate, there is a possibility that the inadequate system will not surface until the operation of the system at the customer site starts. If the deficiency comes to the surface at the customer site, not only will it lead to a decline in credit, but there is also a risk of claiming damages. Therefore, the quality of the legal analysis process affects the software quality of the system.

  In order to deal with such problems, in Patent Document 1, the structure of laws and regulations (chapter, article, paragraph) is based on conversion rules, and is not a common requirement for pharmaceuticals, quasi-drugs, cosmetics, and medical devices in the Pharmaceutical Affairs Law Techniques for classifying and visualizing requirements are disclosed.

  Further, in Patent Document 2, in a system that manages whether or not conforming to a standard such as ISO, the conformity to the standard original is quantified by managing the relationship between the standard original number and the question sentence. Technology is disclosed.

JP 2010-113399 A JP 11-73452 A

  With the technology disclosed in Patent Document 1, it is possible to visualize whether requirements relating to pharmaceuticals, quasi-drugs, cosmetics, and the like are defined in units such as chapters, articles, and items. However, a technique for extracting requirements specifically defined in each legal article is not disclosed.

  Further, by applying the technology disclosed in Patent Document 2, the correspondence between the clause number of each clause and the legal requirement can be clarified. However, a plurality of legal requirements may be defined in one clause, and it cannot be confirmed whether legal requirements can be extracted from each clause without omission.

  In addition, there is a problem that the legal analysis process work varies between the person who is familiar with the law and the person who is not so familiar with the work efficiency and the quality of the legal requirements. In addition, laws and regulations are often used for reference (eg, as stipulated in Article X, paragraph □), and legal requirements are defined across multiple laws and regulations, such as laws, government ordinances, and ministerial ordinances. There is a problem that it takes a lot of time to organize the relations.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide a technique capable of improving the efficiency of extracting the requirements specified in the law.

  The legal analysis support apparatus according to the first aspect of the present invention for achieving the above object is a legal analysis support apparatus that performs support for extracting requirements related to a processing system for processing related to the law from the law, Legal text storage means for storing legal texts, requirement extraction conditions for determining whether the legal text contains requirements related to the processing system, and requirements for meeting the requirements extraction conditions Requirement extraction rule storage means that associates and stores types, and requirement determination means that determines whether or not a requirement for the processing system is included in a predetermined unit of a legal provision based on the requirement extraction condition , A type display means for displaying on the display device a requirement type corresponding to one or more of the requirement extraction conditions determined to include a requirement, and designation of the requirement type of the requirement set by the user The requirement type accepting means, the requirement accepting means for accepting the input of the requirement corresponding to the requirement type in the predetermined unit from the user, the predetermined unit, the specified requirement type, and the input requirement And requirement storage control means for storing the legal requirement information in the legal requirement information storage means.

  In the legal analysis support apparatus, the requirement extraction rule storage means stores the requirement extraction condition and an index indicating the degree of certainty about the requirement extracted by the requirement extraction condition in association with each other, and the type display means The requirement type may be displayed based on an index associated with the requirement type.

  In the legal analysis support apparatus, the type display means may display a requirement type whose index is larger than a predetermined value and a requirement type whose index is a predetermined value or less in different areas.

  In the legal analysis support apparatus, the requirement type may include data, use cases, and term definitions.

  The legal analysis support apparatus further includes a requirement location accepting unit that accepts designation of a requirement description location in a predetermined unit from a user, and the requirement storage control unit is a requirement location that indicates a requirement description location in a predetermined unit. Information may be stored in association with each other.

  Further, in the legal analysis support apparatus, the requirement extraction rule storage means stores the requirement extraction condition and an index indicating the degree of certainty about the requirement extracted by the requirement extraction condition in association with each other. Based on the condition acceptance means that accepts update or addition of extraction conditions, and the requirement extraction conditions that have been updated or changed, the description location corresponding to the requirement extraction conditions is specified and specified for a plurality of prescribed units of the legal provisions. The change condition judging means that grasps the number of described description parts and the description in the legal requirement information that is the same requirement type as the requirement type corresponding to the requirement extraction condition and at least partially overlaps the specified description part Requirement extraction based on the legal requirement determination means that grasps the number of requirements associated with a location, the number of grasped description locations, and the grasped number of requirements Determining an index to be associated with the matter, in association with the requirements extraction conditions may be further having a index determination means for storing.

  Further, in the above-mentioned legal analysis support apparatus, an analysis target determination rule storage means for storing an analysis target determination rule for determining whether or not a predetermined unit of a legal provision is an analysis target of requirement extraction, Analytical object display means for determining whether or not a predetermined unit of the text is an analysis object, an analysis object display means for displaying the text of the predetermined unit and information indicating whether or not the predetermined unit is the analysis object And may be further provided.

  In the above-mentioned legal analysis support apparatus, the analysis target determining means may determine that the other predetermined unit is the analysis target when the predetermined unit is subordinate to another predetermined unit. The predetermined unit may be determined as an analysis target.

  Further, in the above-described legal analysis support apparatus, the analysis target determination rule includes a rule for determining that the analysis target determination rule is not an analysis target when a description of “treat to” is included in a predetermined unit of the text. Also good.

  Further, in the above-mentioned legal analysis support apparatus, there is further provided a requirement classification means for classifying and outputting legal requirement information including a predetermined unit, a specified requirement type, and an inputted requirement, into different files for each requirement type. You may make it have.

  In order to achieve the above object, the legal analysis support method according to the second aspect of the present invention provides a legal analysis by a legal analysis support apparatus that assists in extracting requirements related to a processing system for processing related to the legal law from the legal law. This is an analysis support method, in which the legal text storage means of the legal analysis support device stores the legal text, and the requirement extraction rule storage means of the legal analysis support device includes requirements related to the processing system in the legal text. The requirement extraction condition for determining whether or not the requirement extraction condition and the requirement type when matching the requirement extraction condition are stored in association with each other, and the requirement determination means of the legal analysis support device is based on the requirement extraction condition, It is determined whether or not the requirements for the processing system are included in a predetermined unit of the legal provisions, and the type display means of the legal analysis support apparatus determines that the requirements are included. The requirement type corresponding to the extraction condition is displayed on the display device, the requirement type accepting unit of the legal analysis support device accepts specification of the requirement type of the requirement set by the user, and the requirement accepting unit of the legal analysis support device is received from the user The requirement input corresponding to the requirement type in the predetermined unit is received, and the requirement storage control means of the legal analysis support device associates the predetermined unit, the specified requirement type, and the input requirement with the legal requirement information. Is stored in the legal requirement information storage means.

  In order to achieve the above object, the legal analysis support program according to the third aspect of the present invention constitutes a legal analysis support apparatus that supports the extraction of requirements related to a processing system for performing a process related to the legal law from the law. A legal analysis support program for causing a computer to execute a computer based on a requirement extraction condition for determining whether or not the legal provision includes a requirement related to a processing system. A requirement determining means for determining whether or not a requirement for the processing system is included in a predetermined unit of the text, and a requirement type corresponding to one or more requirement extraction conditions determined to include the requirement on the display device Type display means to be displayed, requirement type reception means for receiving specification of requirement type of requirement set by user, and requirement in predetermined unit from user Requirement receiving means for receiving an input of a corresponding requirement separately, requirement storage control means for storing legal requirement information in which a predetermined unit, a specified requirement type, and an inputted requirement are associated with each other in the legal requirement information storage means To function as.

  According to the present invention, it is possible to improve the efficiency of extracting requirements specified in laws and regulations.

It is an example of the functional block diagram of the law analysis support apparatus which concerns on one Embodiment of this invention. It is an example of the block diagram of the computer which comprises the law analysis support apparatus which concerns on one Embodiment of this invention. It is a figure which shows the example of a data structure of the law analysis file which concerns on one Embodiment of this invention. It is a figure which shows the example of a data structure of the data requirement file which concerns on one Embodiment of this invention. It is a figure which shows the data structure example of the use case requirement file which concerns on one Embodiment of this invention. It is a figure which shows the data structure example of the term definition file which concerns on one Embodiment of this invention. It is a figure which shows an example of the pattern definition file which concerns on one Embodiment of this invention. It is a figure which shows an example of the analysis object determination rule file which concerns on one Embodiment of this invention. It is a figure which shows an example of the requirement extraction rule file which concerns on one Embodiment of this invention. It is a flowchart which shows the process of the analysis object determination part which concerns on one Embodiment of this invention. It is a flowchart which shows the process of the requirement extraction part which concerns on one Embodiment of this invention. It is a flowchart which shows the process of the requirement classification | category part which concerns on one Embodiment of this invention. It is a figure which shows the example of a display screen of the law analysis file which concerns on one Embodiment of this invention. It is a figure which shows the example of a display screen of the requirement extraction result of the requirement extraction part which concerns on one Embodiment of this invention. It is a figure which shows the example of a legal requirement input screen which concerns on one Embodiment of this invention. It is a flowchart which shows the process of the requirement extraction rule update part which concerns on one Embodiment of this invention.

  Embodiments of the present invention will be described with reference to the drawings. The embodiments described below do not limit the invention according to the claims, and all the elements and combinations described in the embodiments are essential for the solution of the invention. Is not limited.

  FIG. 1 is an example of a functional configuration diagram of a legal analysis support apparatus according to an embodiment of the present invention.

  The legal analysis support apparatus 100 includes, for example, a computer including at least a CPU (Central Processing Unit) and a storage device, and includes an analysis target determination unit 101, a requirement extraction unit 102, a requirement classification unit 103, and functional logic. A requirement extraction rule update unit 104 is provided. The legal analysis support apparatus 100 also includes a legal analysis file 111, a data requirement file 112, a use case requirement file 113, a term definition file 114, a pattern definition file 121, an analysis target determination rule file 122, and a requirement extraction rule file 123. It is stored in the storage device (203, 204).

  Based on the analysis target determination rule file 122, the analysis target determination unit 101 determines whether or not a predetermined unit (predetermined unit, hereinafter also referred to as “each clause”) of a legal provision is a target of requirement analysis. Here, the predetermined unit is, for example, a unit of an article, paragraph, or number. If one article of a legal article does not include a subordinate item (section, number), the whole article of the corresponding article If the structure of the article includes lower items, the lowermost description part of each item (for example, the description part corresponding to the issue if there is an issue) and the lower description from the upper description part The description part of the range excluding the description part (for example, if there is a sign, it is a so-called column-written part excluding the description part of the sign from the description part of the term). In addition, as a predetermined unit, the whole article | item may be used as a unit, and if it is a term, it may be the whole term including a number.

  Further, the analysis target determination unit 101 determines whether or not each clause is an analysis target based on the hierarchical relationship between the clauses, paragraphs, and issues and the subordinate relationship between the clauses.

  The requirement extraction unit 102 extracts candidates for requirements (legal requirements) included in each clause based on the requirement extraction rule file 123. In addition, the requirement extraction unit 102 verifies the legal requirement extraction from each clause. This supports the creation of the legal analysis file 111 by the user.

  The requirement classification unit 103 classifies the legal requirements into data requirements that are data requirements, use case requirements that are requirements for use cases, and term definitions that are requirements for definition of terms. The data requirement file 112, the use case requirement file 113, and the term definition file 114 are output. This makes it possible to organize and visualize the legal requirements that were distributed and defined in laws, government ordinances and ministerial ordinances in terms of data requirements, use case requirements, and term definitions.

  The requirement extraction rule update unit 104 updates the requirement extraction rule file 123. The update extraction rule update unit 104 updates the requirement extraction rule file 123 when a requirement extraction rule is added or changed in the requirement extraction rule file 123 or when the law analysis file 111 is updated.

  The legal analysis file 111 is a file in which legal requirements and legal provisions are recorded in association with each other. The legal analysis file 111 is created in units of legal documents (laws, government ordinances, ministerial ordinances, etc.). For example, when there are three related legal documents, ie, a law, a government ordinance, and a ministerial ordinance, as the law analysis file 111, three files that record the respective legal requirements of the law, the government ordinance, and the ministerial ordinance are created. It should be noted that information for identifying legal documents (for example, legal names) is managed in one legal analysis file 111 so that the legal requirements of multiple legal documents are managed in one legal analysis file 111. May be.

  The data requirement file 112 is a file in which requirements relating to data defined by laws and regulations are recorded. The information included in the data requirement file 112 includes information on requirements regarding data recorded in the law analysis file 111, requirements regarding data added by the user, and the like. The data requirement file 112 is created for each target system.

  The use case requirement file 113 is a file in which requirements relating to use cases defined in laws and regulations are recorded. The information included in the use case requirement file 113 includes information on requirements related to use cases recorded in the law analysis file 111, requirements regarding use cases added by the user, and the like. The use case requirement file 113 is created for each target system.

  The term definition file 114 is a file in which information related to definitions of various terms prescribed in laws and regulations is recorded. The information included in the term definition file 114 includes information on term definitions recorded in the law analysis file 111, information on term definitions added by the user, and the like. The term definition file 114 is created for each target system.

  The pattern definition file 121 is a file that defines a character string pattern included in a legal provision used in the analysis target determination rule file 122 and the requirement extraction rule file 123. By using the pattern definition file 121, it is possible to save labor for describing the rules in the analysis target determination rule file 122 and the requirement extraction rule file 123.

  The analysis target determination rule file 122 is a file that defines a rule (analysis target determination rule) for determining whether or not each clause of the law is an analysis target.

  The requirement extraction rule file 123 is a file that defines a requirement prescribed in laws and regulations and a rule for determining the type of the requirement (requirement extraction rule).

  In this embodiment, the law analysis file 111, the data requirement file 112, the use case requirement file 113, the term definition file 114, the pattern definition file 121, the analysis target determination rule file 122, and the requirement extraction rule file 123 are different. Although it is managed as a file, any configuration may be used as long as the information managed in each file can be identified. For example, a configuration in which a database is used for centralized management It is also good.

  FIG. 2 is an example of a configuration diagram of a computer constituting the legal analysis support apparatus according to the embodiment of the present invention.

  A computer 201 constituting the legal analysis support apparatus 100 includes a CPU 202, a main storage device 203, an auxiliary storage device 204, a network interface 205, and an I / O interface 206, which are connected to each other via an internal bus 207. Yes. In this specification, the main storage device 203 and the auxiliary storage device 204 may be simply referred to as “storage device”. The main storage device 203 is, for example, a RAM (Random Access Memory). The auxiliary storage device 204 is, for example, a hard disk drive. The network interface 205 mediates communication with other devices via the network. The I / O interface 206 is connected to, for example, a display (display device), a mouse, a keyboard, and the like, and performs data input / output with these devices.

  Here, the law analysis file 111, the data requirement file 112, the use case requirement file 113, the term definition file 114, the pattern definition file 121, the analysis target determination rule file 122, and the requirement extraction rule file 123 are stored in a storage device. The The analysis target determination unit 101, the requirement extraction unit 102, the requirement classification unit 103, and the requirement extraction rule update unit 104 are controlled by the CPU 202 executing a legal analysis support program stored in the storage device and controlling each unit. Composed.

  Here, the legal text storage unit, the requirement extraction rule storage unit, the legal requirement information storage unit, and the analysis target determination rule storage unit referred to in the claims are mainly configured by the auxiliary storage device 204, and the requirement determination unit, type The display means, the request reception means, the requirement storage control means, and the requirement location reception means correspond to the requirement extraction unit 102, and the condition reception means, the change condition determination means, the legal requirement determination means, and the index determination means are the requirement extraction rules. Corresponding to the updating unit 104, the analysis target determination unit and the analysis target display unit correspond to the analysis target determination unit 101, and the requirement classification unit corresponds to the requirement classification unit 103.

  Subsequently, an example of the data structure of the law analysis file 111 according to the embodiment of the present invention will be described.

  FIG. 3 is a diagram showing an example of the data structure of a law analysis file according to an embodiment of the present invention. In the drawing showing an example of the data structure of the present embodiment, each entity (data entity) is represented by a rectangle, the upper column in the rectangle indicates the entity name, and the lower column in the rectangle indicates this entity. Indicates the attribute name. The relationship between entities is expressed by connecting a diamond and a solid line, and the diamond side entity and the solid line side entity are in a one-to-many relationship.

  The legal analysis file 111 includes legal information 301, legal text information 302, legal requirement information 303, and requirement extraction rule match information 304 as entities.

  There is one law information 301 in the law analysis file 111, and a law ID and a law name are stored as information for identifying the law. The law ID is an abbreviation of the law name, and is set so as not to overlap with the law ID of another law analysis file 111 managed by the law analysis support apparatus 100. For example, if the name of the law is “Basic Resident Registration Law”, the law ID is set to “Sumi law” by the user. The law analysis support apparatus 100 may automatically set the law name so that it does not overlap with other law IDs.

  The legal provision information 302 stores a provision number, a legal provision, and an analysis target flag as information relating to the legal provisions of each provision. The clause number is the number of the article, paragraph or issue corresponding to the legal provision. A legal provision is a sentence (also referred to as a provision) described in an article, paragraph, or issue corresponding to a provision number. The analysis target flag is information indicating whether or not the requirement relating to the target system (target system) is specified by the clause, and either TRUE or FALSE is set. In the case of TRUE, it means that the requirements related to the target system are specified, and in the case of FALSE, it means that the requirements related to the target system are not specified.

  The legal requirement information 303 includes legal requirement ID, subordinate legal requirement requirement ID, type, requirement 1, requirement 2, text corresponding location (requirement location information), and requirement extraction rule ID 901 (see FIG. 9). Is stored. The legal requirement ID represents an identifier for uniquely identifying the legal requirement. The subordinate legal requirement ID represents the subordinate legal requirement ID when subordinate to another legal requirement. The type represents the type of legal requirement such as data, use case, term definition. Requirement 1 and requirement 2 are requirements extracted from the text, and are described according to the type. The section corresponding to the text indicates a description location in the text corresponding to the legal requirement. For example, the section corresponding to the clause is represented by the description start position of the legal requirement from the beginning of the clause and the length from the description start position to the description end position. The requirement extraction rule ID represents an identifier of a requirement extraction rule defined in the requirement extraction rule file 123 applied when extracting legal requirements.

  The requirement extraction rule match information 304 stores a requirement extraction rule ID, a type, and a rule match location as information on a requirement extraction rule that can be applied to the legal provision of the legal provision information 302. The requirement extraction rule ID represents an identifier (requirement extraction rule ID 901) of a requirement extraction rule applicable to the legal provisions. The type represents the type 903 of the requirement extraction rule. The rule match part represents the part of the clause that matches the requirement extraction determination condition 902 of the requirement extraction rule. For example, the section corresponding to the clause is represented by the description start position of the legal requirement from the beginning of the clause and the length from the description start position to the description end position.

  Next, a data structure example of the data requirement file 112 according to an embodiment of the present invention will be described.

  FIG. 4 is a diagram showing an example data structure of a data requirement file according to an embodiment of the present invention.

  The data requirement file 112 includes legal information 401, data information 402, and data requirement information 403 as entities.

  There is one law information 401 in the data requirement file 112, and the law name is stored as information for identifying the law that is the input information of the data requirement file 112. If there are multiple law names, they are stored by separating them with commas (,). The name of the law is set by the requirement classification unit 103 by acquiring a value from the law information 301 of the law analysis file 111. The law name may be the law ID of the law analysis file 111.

  The data information 402 stores a data ID and a data name as information for identifying data defined by law. The data ID is an identifier for uniquely identifying data in the data requirement file 112 and is set by the requirement classification unit 103. The data name represents the name of the data, and the requirement classification unit 103 acquires and sets the value of requirement 1 in the legal requirement information 303 of the legal analysis file 111. The data information 402 is set in units of input / output of each use case or a form.

  The data requirement information 403 stores a requirement ID, a data requirement, a legal requirement ID, and a parent requirement ID as information relating to data requirements. The requirement ID is an identifier for uniquely identifying the data requirement, and is set by the requirement classification unit 103. The data requirement is a requirement relating to the data described in the law analysis file 111, and the requirement classification unit 103 acquires and sets the value of requirement 2 of the law requirement information 303. The legal requirement ID is the legal requirement ID of the legal requirement information 303 that is the reference destination of the data requirement, and is set by the requirement classification unit 103. The parent requirement ID is a requirement ID of the other data requirement information 403 when the data requirement is a lower requirement of the other data requirement information 403, and is set by the requirement classification unit 103. The hierarchical relationship of data requirements can be expressed by using the parent requirement ID.

  Next, an example of the data structure of the use case requirement file 113 according to an embodiment of the present invention will be described.

  FIG. 5 is a diagram showing an example data structure of a use case requirement file according to an embodiment of the present invention.

  The use case requirement file 113 includes legal information 501, use case information 502, use case type information 503, and use case requirement information 504 as entities.

  There is one law information 501 in the use case requirement file 113, and the law name is stored as information for identifying the law that is the input information of the use case requirement file 113. If there are multiple law names, they are defined by separating them with commas (,). The name of the law is set by the requirement classification unit 103 by acquiring a value from the law information 301 of the law analysis file 111. The law name may be the law ID of the law analysis file 111.

  The use case information 502 stores a use case ID and a use case name as information for identifying a use case specified by law. The use case ID is an identifier for uniquely identifying the use case in the use case requirement file 113, and is set by the requirement classification unit 103. The use case name represents the name of the use case and is set by the user.

  The use case type information 503 stores a use case type as information for identifying a basic scenario, an alternative scenario, or an exception scenario. The use case type can be specified from the basic scenario, the alternative scenario, or the exceptional scenario by using the pull-down menu or the like on the setting screen of the legal analysis support apparatus 100. Here, the basic scenario indicates a case that is used in a normal flow, the alternative scenario indicates a case in which a certain condition exists and is used through another process, and an exception scenario is an abnormal flow The case used in is shown. For example, in the case of a use case where a resident card creation request is received, the resident card creation request satisfies the requirements, the case where the resident card is created is a normal scenario, and the resident card creation request satisfies the requirements. If the resident's card is created through other processing to satisfy the specified condition, the alternative scenario is not satisfied, but the resident card request is not satisfied and the resident card is not created. It is.

  The use case requirement information 504 stores a requirement ID, a requirement type, a use case requirement, a reference source ID, and a parent requirement ID as information on the use case requirement. The requirement ID is an identifier for uniquely identifying the use case requirement, and is set by the requirement classification unit 103. The requirement type is one of input, output, precondition, and postcondition, and is determined and set by the requirement classification unit 103 based on the reference destination of the use case requirement. When the reference destination of the use case requirement is requirement 1 in the legal requirement information 303, the requirement type is a precondition. When the use case requirement reference source is requirement 2 of the legal requirement information 303, the requirement type is a post-condition. When the reference source of the use case requirement is the data name of the data information 402 of the data requirement file 112, the requirement type is input or output. In this case, the requirement classification unit 103 displays whether the input is an input or an output, and determines a requirement type by selecting an input or an output by the user. The use case requirement is a requirement relating to the use case described in the law analysis file 111 or the data requirement file 112. When the requirement type is input or output, the requirement classification unit 103 sets the data name of the data information 402 to the use case requirement, and in other cases, the requirement 1 or requirement of the legal requirement information 303 of the legal analysis file 111 Set the contents of 2. The reference destination ID is a value of either the legal requirement ID of the legal requirement information 303 of the legal analysis file 111, which is the reference destination of the use case requirement, or the data ID of the data information 402 of the data requirement file 112. Set by the unit 103. The parent requirement ID is a requirement ID of the other use case requirement information 504 when the use case requirement is a lower requirement of the other use case requirement information 504, and the requirement classification unit 103 sets a value. By using the parent requirement ID, the hierarchical relationship of use case requirements can be expressed.

  Next, an example of the data structure of the term definition file 114 according to an embodiment of the present invention will be described.

  FIG. 6 is a diagram showing an example data structure of a term definition file according to an embodiment of the present invention.

  The term definition file 114 includes legal information 601, term information 602, and term definition information 603 as entities.

  There is one law information 601 in the term definition file 114, and the law name is stored as information for identifying the law that has been input to the term definition file 114. If there are multiple law names, they are stored by separating them with commas (,). The name of the law is set by the requirement classification unit 103 by acquiring a value from the law information 301 of the law analysis file 111. The law name may be the law ID of the law information 301.

  The term information 602 stores a term ID and a term name as information for identifying a term defined by law.

  The term ID is an identifier for uniquely identifying a term in the term definition file 114, and is set by the requirement classification unit 103. The term name represents the name of the term, and the requirement classification unit 103 acquires and sets the value of requirement 1 in the legal requirement information 303 of the legal analysis file 111. The term name may be a term other than the term stipulated by law. In this case, the user sets a term name.

  The term definition information 603 stores a definition ID, definition content, legal requirement ID, and parent definition ID as information related to the definition of the term. The definition ID is an identifier for uniquely identifying the definition content, and is set by the requirement classification unit 103. The definition content is the definition content related to the term described in the law analysis file 111, and the requirement classification unit 103 acquires and sets the value of requirement 2 of the law requirement information 303 of the law analysis file 111. In addition, when a user adds a term other than a term stipulated by law, the definition content is set by the user. The legal requirement ID is the legal requirement ID of the legal requirement information 303 of the legal analysis file 111 that is the reference destination of the definition content, and is set by the requirement classification unit 103. The parent definition ID is the definition ID of the other term definition information 603 when the definition content is the definition content lower than the other term definition information 603, and the requirement classification unit 103 sets a value. By using the parent definition ID, the hierarchical relationship of the definition contents can be expressed.

  Next, the pattern definition file 121 according to an embodiment of the present invention will be described.

  FIG. 7 is a diagram showing an example of a pattern definition file according to an embodiment of the present invention.

  The pattern definition file 121 includes items of a pattern name 701, a regular expression flag 702, and a pattern character string 703. The pattern name 701 is information for identifying a pattern. The regular expression flag 702 is a value of either TRUE or FALSE. In the case of TRUE, the regular expression flag 702 indicates that the pattern character string 703 is a character string using a regular expression, and in the case of FALSE, the pattern character string. Reference numeral 703 denotes a character string that does not use a regular expression. The pattern character string 703 is a search character string for extracting a specific character string included in the legal text. When there are a plurality of the same pattern names, one pattern is obtained by combining the patterns with “OR”. For example, in FIG. 7, there are two pattern names “actors”. In this case, “actor” means a character string of “city head” or “city executive body”. Note that the pattern of the pattern definition file 121 is a character string pattern used in the analysis target determination rule file 122 and the requirement extraction rule 123 that has been previously identified and stored by the user.

  Further, “Actor” in FIG. 7 is a pattern representing a user of the target system. In the case of a system used in a municipality based on the Basic Resident Register Act, Acta is a municipal employee, and the corresponding terms in the law are "Municipal Mayor" and "City / Municipal Entities". Regarding the setting of patterns, it is necessary to make a judgment based on prior knowledge and past knowledge. The term used to describe the actors of the system used in municipalities is “Municipal” even if other laws are seen. The other laws also use the pattern “actor” shown in FIG. can do.

  Next, an example of the analysis target determination rule file 122 according to the embodiment of the present invention will be described.

  FIG. 8 is a diagram showing an example of an analysis object determination rule file according to an embodiment of the present invention.

  The analysis target determination rule file 122 includes items of an analysis target determination rule ID 801, an analysis target determination condition 802, an analysis target flag 803, and a regular expression flag 804. A set of these four items of data is referred to as an “analysis target determination rule”.

  The analysis target determination rule ID 801 is an identifier that uniquely identifies the analysis target determination rule. The analysis target determination condition 802 is a condition for searching for a character string included in a law ordinance for determining whether or not it is an analysis target. The analysis target flag 803 is a value of either TRUE or FALSE. In the case of TRUE, the analysis target flag 803 indicates that the analysis target is set. In the case of FALSE, the analysis target flag 803 indicates that the analysis target flag 803 is not set as an analysis target. The regular expression flag 804 is a value of either TRUE or FALSE. In the case of TRUE, it indicates that the analysis target determination condition 802 uses a regular expression. In the case of FALSE, the analysis target determination condition 802 indicates that a regular expression is not used.

  In FIG. 8, the analysis target determination rule whose analysis target determination rule ID 801 is “AT001” is that the regular expression flag 804 is “TRUE” and the analysis target flag 803 is “TRUE”. If it is expressed using a regular expression and the legal text satisfies the analysis target determination condition 802, it means that the legal text is an analysis target. “% Actor% (to ||)” in the analysis target determination condition 802 means “% Actor% is” or “to% Actor%”. A character string between “%” represents a pattern name 701 defined in the pattern definition file 121.

  In the case where the pattern definition file 121 is shown in FIG. 7, since there are two actors, “Municipal mayor” and “Executive organization of municipalities”, “% actor% (for |)” in the analysis target determination condition 802. At the time of execution, it is broken down into four analysis target determination conditions 802, “Municipal mayor”, “Municipal mayor”, “Municipal executive organization”, “Municipal executive organization”, and any character in the legal provisions. If it contains a column, it is determined as an analysis target. If the text of the law contains the text “Mayor of the municipality”, the law ordinance prescribes the obligation or right for the mayor. Obligations and rights to the mayor are likely to be a task that needs to be improved, and are included in the analysis if they contain the character string “Mayor”.

  Next, the requirement extraction rule file 123 according to an embodiment of the present invention will be described.

  FIG. 9 is a diagram showing an example of a requirement extraction rule file according to an embodiment of the present invention.

  The requirement extraction rule file 123 includes items of a requirement extraction rule ID 901, a requirement extraction determination condition 902, a type 903, a priority 904, and a regular expression flag 905. A set of these five items of data is referred to as a “requirement extraction rule”.

  The requirement extraction rule ID 901 is an identifier that uniquely identifies the requirement extraction rule. The requirement extraction determination condition 902 is a rule for classifying the legal requirements, and can be defined using the pattern name 701 of the pattern definition file 121 and the configuration information of the legal provisions. Here, the legal provisions are usually written as “XX is (main part), Δ △ (condition part), □□ must be (predicate)”. The constitutional information of the legal provisions refers to the main part, the conditional part, the predicate, etc. of such legal provisions. The type 903 is a type of requirement specified in the legal requirement information 303 of the legal analysis file 111 when the legal provisions match the condition.

  The priority 904 is an index (priority) indicating the probability of the requirement extraction rule, and is extracted as a legal requirement based on the number of clauses that match the requirement extraction determination condition 902 or based on the requirement extraction rule. The requirement extraction rule update unit 104 calculates based on the number of requirements. The requirement extraction rule is information defined by the user. Some requirements extraction rules are correct and some requirements extraction rules are not. By introducing the priority 904, it is possible to control the display order of legal requirements displayed by the requirement extraction unit 102 as candidates, the non-display of legal requirements, and the like.

  The regular expression flag 905 is a value of either TRUE or FALSE, indicating that the requirement extraction determination condition 902 uses a regular expression in the case of TRUE, and the requirement extraction determination condition in the case of FALSE. 902 indicates that a regular expression is not used.

  In FIG. 9, the requirement extraction rule whose requirement extraction rule ID 901 is “RE001” is that the regular expression flag 905 is “FALSE” and the type 903 is “use case”. It is expressed without being used, and when the legal text matches the requirement extraction determination condition 902, it means that the requirement type is determined as “use case”. Requirement extraction judgment condition 902 “(main part like% actor%) AND (must predicate like %% action%)” includes “% actor%” in the main part of the statute and the predicate. It means to include “% Action% Must Be”.

  In the case where the pattern definition file 121 is shown in FIG. 7, the actor is “Municipal mayor” or “Executive organization of municipality”, and the action is “Notification” or “Grant”. “Municipal heads must be notified” “Municipal heads must be issued” “Municipal executive bodies must be notified” 4 “Municipal executive bodies must be issued” 4 When it is decomposed into two requirement extraction determination conditions 902 and any of the character strings is included in the legal provisions, it is determined as a “use case”. In this embodiment, it is assumed that the target system is used by the municipal staff, and the legal provisions including actions such as “notification” and “delivery” that are highly likely to be systemized are determined as use cases. Requirement extraction rules are set.

  Next, an example of the law analysis file display screen 1300 according to the embodiment of the present invention will be described.

  FIG. 13 is a view showing an example of a display screen of a legal analysis file according to an embodiment of the present invention.

  The law analysis file display screen 1300 includes a “return to menu screen” button 1301, an analysis target determination button 1302, and a “requirement extraction” button 1303. When the “return to menu screen” button 1301 is pressed by the user, the screen returns to the menu screen. When the “analysis target determination” button 1302 is pressed by the user, the process of the analysis target determination unit 101 is executed. When the “requirement extraction” button 1303 is pressed by the user, the processing of the requirement extraction unit 102 is executed.

  The legal analysis file display screen 1300 also includes the legal name of the legal information 301 of the legal analysis file 111, the legal text and analysis target flag of the legal text information 302, the legal requirement ID, type, requirement 1 and requirements of the legal requirement information 303. The value of each item of 2 is displayed. Since the contents of requirement 1 and requirement 2 of the legal requirement information 303 differ depending on the type of legal requirement, the requirement name is displayed on the legal analysis file display screen 1300 according to the type. For example, when the type is data, the requirement name of requirement 1 is an entity name, and the requirement name of requirement 2 is a data requirement.

  Subsequently, processing of the analysis target determination unit 101 according to an embodiment of the present invention will be described.

  FIG. 10 is a flowchart showing processing of the analysis target determination unit according to the embodiment of the present invention.

  The analysis target determination unit 101 starts the execution of processing by pressing the analysis target determination 1302 button on the law analysis file display screen 1300 by the user, batch processing, or the like.

  First, the analysis target determination unit 101 reads the legal article information 302 from the legal analysis file 111 (step S1001), and proceeds to step S1002. Next, the analysis target determination unit 101 determines whether or not the analysis target flag of the legal article information 302 has been set (step S1002). As a result, if it has been set (YES in step S1002), the process proceeds to step S1007. If it has not been set (NO in step S1002), the process proceeds to step S1003. In the present embodiment, the specification allows the user to set the analysis target flag of the legal text information 302, and the specification of the analysis target flag setting information set by the user is prioritized by performing the process of step S1002. It is said. As a modification, the set analysis target flag may be ignored and it may be determined again whether or not it is an analysis target. In this case, the process of step S1002 may be omitted. .

  Next, the analysis target determination unit 101 determines whether or not the legal provision of the relevant legal provision information 302 is a dependent provision or a number (step S1003). As a result, if it is a subordinate clause or issue (YES in step S1003), the process proceeds to step S1004, and if not (NO in step S1003), the process proceeds to step S1005. Dependent clauses include reference information to other clauses such as “has stipulated in Article ○, paragraph △” in the laws and regulations, and the other clauses are restricted or supplemented. It is a clause that is closely related to other clauses. In addition, the number is used when enumerating matters in laws and regulations, and is a part (subordinate) of a term.

  Next, the analysis target determination unit 101 acquires the analysis target flag of the subordinate or higher-level clause (step S1004). When the legal clause of the relevant legal clause information 302 is a subordinate clause, the analysis target determining unit 101 identifies the subordinate clause from the reference information to other clauses included in the relevant legal clause, and determines the laws of the subordinate clause. The value of the analysis target flag in the text information 302 is acquired. In addition, when the legal text of the legal text information 302 is a number, the analysis target determination unit 101 identifies a clause corresponding to the higher rank of the number, and acquires the value of the analysis target flag of the legal clause information 302 of the clause. After obtaining the value of the analysis target flag, the analysis target determination unit 101 proceeds to step S1006.

  On the other hand, if the legal text of the legal text information 302 is not a subordinate clause or issue (NO in step S1003), the analysis target determination unit 101 determines that the target legal text is to be analyzed based on the analysis target determination rule file 122. Is determined (step S1005). Specifically, the analysis target determination unit 101 determines whether or not there is a description that matches the analysis target determination condition 802 of the analysis target determination rule file 122 in the legal provision of the legal provision information. If there is a description that matches, the analysis target determination unit 101 acquires the value of the analysis target flag 803 of the analysis target determination rule file 122. “Not set (no value)”. After obtaining the value of the analysis target flag 803, the process proceeds to step S1006.

  In step S1006, the analysis target determination unit 101 sets the value of the analysis target flag of the relevant legal article information 302 in the legal analysis file 111 (step S1006). If the value of the analysis target flag acquired in step S1004 is “not set (no value)”, or if the determination result of the analysis target in step S1005 is “not set (no value)”, step The process of S1006 is skipped.

  Next, the analysis target determination unit 101 determines whether or not there is an unprocessed legal text (clause: legal text information 302) in the legal analysis file 111 (step S1007). As a result of the determination, if there is an unprocessed legal provision (legal condition information 302) (YES in step S1007), the process returns to step S1001, and if not (NO in step S1007), the process ends.

  In the example shown in FIG. 10, the flow is to continuously determine whether or not it is an analysis target for all the legal article information 302 of the legal analysis file 111. May be processed interactively for each case. For example, when a user presses a button on a specific legal provision information 302 selected by the user, a determination process is performed to determine whether or not the single legal provision information 302 is an analysis target. Also good. In this case, the process of step S1007 may be omitted.

  As another example, in the case where the process of step S1002 is omitted and the analysis target flag of the legal provisions information 302 has been set, the analysis target flag obtained as a result of the execution of steps S1004 and S1005 A warning screen may be displayed when the value does not match the set analysis target flag value.

  Subsequently, processing of the requirement extraction unit 102 according to an embodiment of the present invention will be described.

  FIG. 11 is a flowchart showing processing of the requirement extraction unit according to an embodiment of the present invention.

  The requirement extraction unit 102 starts the execution of the processing for the legal provision information 302 selected by the user when the requirement extraction button 1303 on the legal analysis file display screen 1300 is pressed by the user.

  The requirement extraction unit 102 reads the legal requirement information 302 selected by the user, the legal requirement information 303 corresponding to the legal requirement information 302, and the requirement extraction rule match information 304 (step S1101). After reading, the process proceeds to step S1102.

  Next, the requirement extraction unit 102 determines the requirements stipulated in the legal provisions of the legal provisions information 302 based on the requirement extraction rules of the requirement extraction rule file 123 (step S1102). Specifically, the requirement extraction unit 102 determines whether or not the relevant legal provisions match the requirement extraction determination condition 902 of the requirement extraction rule file 123. If they match, the requirement extraction determination condition 902 The extraction rule ID 901 and type 903, and the position of the character string that matches the requirement extraction determination condition 902 in the legal text are written in the requirement extraction rule ID, type, and rule match location of the requirement extraction rule match information 304, respectively. In the case where a plurality of requirement extraction determination conditions 902 are matched, the requirement extraction unit 102 creates requirement extraction rule match information 304 for each of the matched requirement extraction determination conditions 902. If information is already recorded in the requirement extraction rule match information 304, it may be considered that the process of step S1102 has already been executed, and the process of step S1102 may be omitted. After writing in the requirement extraction rule match information 304, the process proceeds to step S1103.

  Next, the requirement extraction unit 102 displays the identified requirement based on the legal requirement information 303 corresponding to the legal provision information 302 and the priority 904 of the requirement extraction rule file 123 (step S1103). The requirement extraction unit 102 has the requirement extraction rule ID of the requirement extraction rule match information 304 out of the requirement extraction rule match information 304 corresponding to the legal provision information 302 corresponding to the legal requirement information 303 corresponding to the legal provision information 302. The requirement extraction rule match information 304 that does not match the extraction rule ID is specified. Subsequently, the requirement extraction unit 102 acquires the priority 904 of the requirement extraction rule file 123 from the requirement extraction rule ID of the specified requirement extraction rule match information 304. Subsequently, the requirement extraction unit 102 rearranges the requirements in descending order of the priority 904, and displays a requirement extraction result screen. If the priority 904 is lower than a certain threshold value, the requirement extraction unit 102 may not display on the screen, or may display the requirement with a high priority and the display area separately.

  Here, an example of the requirement extraction result display screen 1400 of the requirement extraction unit 102 according to the embodiment of the present invention will be described.

  FIG. 14 is a view showing an example of a requirement extraction result display screen of the requirement extraction unit according to an embodiment of the present invention.

  The requirement extraction result display screen 1400 displays two items: a requirement candidate and a requirement candidate below a threshold (for example, priority “10”). Below the requirement candidates, requirement extraction rules having a priority 904 greater than the threshold are displayed, and other requirement extraction rules are displayed below the requirement candidates below the threshold. The contents displayed as the requirement extraction rule are a requirement extraction rule ID 901, a type 903, and a priority 904. The requirement extraction result display screen 1400 displays two buttons, an OK button and a cancel button. When the user selects either the requirement candidate or the requirement extraction rule under the requirement candidate below the threshold and presses the OK button, the requirement extraction unit 102 extracts the requirement selected by the user. Get the rules. When the cancel button is pressed by the user, the requirement extraction unit 102 closes the requirement extraction result display screen 1400.

  After displaying the requirement extraction result display screen 1400, the requirement extraction unit 102 proceeds to step S1104. The requirement extraction unit 102 waits for selection of requirement candidates by the user (step S1104). The requirement extraction unit 102 waits for any of the requirement extraction rules displayed on the requirement extraction result display screen 1400 to be selected by the user and the OK button to be pressed. After the OK button is pressed, the process proceeds to step S1105. If the user presses the cancel button, the process proceeds to step S1106.

  The requirement extraction unit 102 highlights the relevant part of the legal text corresponding to the requirement extraction rule selected by the user (step S1105). The requirement extraction unit 102 displays the legal requirement input screen 1500 and highlights (for example, underline and bold) the relevant part of the legal provisions corresponding to the requirement extraction rule.

  Here, an example of the legal requirement input screen 1500 according to an embodiment of the present invention will be described.

  FIG. 15 is a diagram showing an example of a legal requirement input screen according to an embodiment of the present invention. FIG. 15A shows an example of the legal requirement input screen 1500 immediately after the screen is displayed, and FIG. 15B shows an example of the legal requirement input screen 1500 after the requirement is inputted by the user. Yes.

  The legal requirement input screen 1500 has a part for inputting and displaying the items of legal provisions, type, subordinate legal requirement ID, requirement 1 and requirement 2. In the legal text, the value of the legal text in the legal text information 302 of the legal analysis file 111 is displayed. In the type, the type of the requirement extraction rule selected by the user in step S1104 is displayed. The dependent legal requirement ID is a part where the user inputs the legal requirement ID of the other legal requirement when the legal requirement is dependent on the other legal requirement. Requirement 1 and requirement 2 are parts where the user inputs requirements according to the type. Note that “(name of data)” and “data requirement” are written in parentheses next to requirement 1 and requirement 2, and these values are set by the requirement extraction unit 102 depending on the type. In the legal requirement input screen 1500 shown in FIG. 15A, the type is “data”, and the character strings “data name” and “data requirement” are assigned to the requirements 1 and 2 respectively corresponding to the type “data”. Is displayed.

  The legal requirement input screen 1500 may be simultaneously displayed on the same screen as the requirement extraction result display screen 1400. In this case, on the requirement extraction result display screen 1400, the requirement extraction unit 102 displays the position and type of the legal text highlighting on the legal requirement input screen 1500 in synchronization according to the requirement candidate selected by the user. In this case, the user can easily see the corresponding part between the requirement candidate and the legal provision.

  After the requirement extraction unit 102 displays the legal requirement input screen 1500 shown in FIG. 15A, the process proceeds to step S1106.

  Next, the requirement extraction unit 102 waits for the marking of the requirement part and the description of the requirement on the legal requirement input screen 1500 by the user (step S1106). In step S1105, the user refers to before and after the highlighted portion of the legal provisions, identifies the portion where the requirement is described, and marks the portion. The law extraction unit 102 displays the screen so that the location marked by the user can be understood by changing the format of the location marked by the user, such as underline or bold. Subsequently, the user inputs a requirement corresponding to the type in the items of requirement 1 and requirement 2. In the legal requirement input screen 1500 shown in FIG. 15B, the user has marked the parts “I have written ... of the municipality from another municipality” and “to that effect”. The location corresponding to the requirement extraction rule is only “to that effect”, but here, the user also marks the portion corresponding to the pronoun “that”. In addition, requirement 1 and requirement 2 are input by the user with reference to the information of the marked part. The content of requirement 1 (data name) does not include the same description in the marking portion, but the user reviews the data name and inputs it. After the OK button on the legal requirement input screen 1500 is pressed, the process proceeds to step S1107. If the cancel button on the legal requirement input screen 1500 is pressed, the process proceeds to step S1103.

  Next, the requirement extraction unit 102 records (stores) the extracted legal requirements and various information input by the user (step S1107). The requirement extraction unit 102 stores the type of the legal requirement input screen 1500, the dependent legal requirement ID, the requirement 1 and the requirement 2 values in the corresponding locations of the legal requirement information 303 of the legal analysis file 111, respectively. In addition, the requirement extraction unit 102 determines the location marked by the user on the legal requirement input screen 1500 and the requirement extraction rule ID applied to the extraction of the legal requirement, the clause corresponding location of the legal requirement information 303 and the requirement extraction rule ID. Respectively. Note that the location marked by the user is represented by, for example, a set of the number of characters from the beginning of the legal text to the marking start location (marking start location) and the number of characters from the marking start location to the marking end location. After various information is stored in the legal requirement information 303, the process proceeds to step S1108.

  Next, the requirement extraction unit 102 determines whether there is another requirement candidate (step S1108). If there is another requirement candidate (YES in step S1108), the process returns to step S1103. If there is no other candidate (NO in step S1108), the process proceeds to step S1109. In the present embodiment, the other requirement candidates are the requirement candidates of the requirement extraction result 1400 (whose priority is greater than the threshold value). Thereby, the extraction more about the requirement with high priority can be prevented appropriately.

  Next, the requirement extraction unit 102 determines whether or not there is a part that is not marked in the law ordinance (step S1109). The requirement extraction unit 102 determines whether or not there is an unmarked part by using the values of the part corresponding to the provisions of all the legal requirement information 303 related to the relevant legal provisions. If there is a part that is not marked (YES in step S1109), the process returns to step S1106. If not (NO in step S1109), the requirement extraction unit 102 ends the process. When the process returns to step S1106, the type of the legal requirement input screen 1500 is designated by the user.

  Subsequently, processing of the requirement classification unit 103 according to an embodiment of the present invention will be described.

  FIG. 12 is a flowchart showing processing of the requirement classification unit according to the embodiment of the present invention.

  The requirement classification unit 103 starts execution of processing by user operation, batch processing, or the like. The requirement classification unit 103 reads the law analysis file 111 (step S1201). The requirement classification unit 103 reads all the legal analysis files 111 in which the results of extracting the requirements from the legal documents related to the target system are recorded. Whether or not it is related to the target system is determined, for example, by targeting the law analysis file 111 stored in a specific folder or by targeting the law analysis file 111 specified by the user. After reading the law analysis file 111, the process proceeds to step S1202.

  Next, the requirement classification unit 103 extracts term definition information from the read law analysis file 111 and creates a term definition file 114 (step S1202). The requirement classification unit 103 includes the legal requirement information 303 in which the analysis target flag of the legal information 301 and the legal provision information 302 is “TRUE” from the legal analysis file 111 and the type of the legal requirement information 303 is “definition”. To extract. Subsequently, the requirement classification unit 103 writes the information of the legal information 301 and the legal requirement information 303 in the legal information 601, the term information 602, and the term definition information 603 of the term definition file 114. If there is a created term definition file 114, the update process is performed only for the changed part. After creating the term definition file 114, the process proceeds to step S1203.

  Next, the requirement classification unit 103 extracts data requirement information from the law analysis file 111 and creates the data requirement file 112 (step S1203). The requirement classification unit 103 includes the legal requirement information 303 in which the analysis target flag of the legal information 301 and the legal provision information 302 is “TRUE” from the legal analysis file 111 and the type of the legal requirement information 303 is “data”. To extract. Subsequently, the requirement classification unit 103 writes the information of the legal information 301 and the legal requirement information 303 in the legal information 401, the data information 402, and the data requirement information 403 of the data requirement file 112. If there is a data requirement file 112 that has already been created, the update process is performed only for the portions that have changed. After creating the data requirement file 112, the process proceeds to step S1204.

  Next, the requirement classification unit 103 extracts information on use case requirements from the law analysis file 111, creates a use case requirement file 113 (step S1204), and ends the processing. The requirement classifying unit 103 provides the legal requirement information from the legal analysis file 111 where the analysis target flag of the legal information 301 and the legal provision information 302 is “TRUE” and the type of the legal requirement information 303 is “use case”. 303 is extracted. Subsequently, the requirement classification unit 103 writes the information of the legal information 301 and the legal requirement information 303 in the legal information 501, the use case information 502, the use case type information 503, and the use case requirement information 504 of the use case requirement file 112. . If there is a use case requirement file 113 that has been created, the update process is performed only for the changed part.

  Next, processing of the requirement extraction rule update unit 104 according to the embodiment of the present invention will be described.

  FIG. 16 is a flowchart showing processing of the requirement extraction rule update unit according to the embodiment of the present invention.

  The requirement extraction rule update unit 104 starts execution of the process when the requirement extraction rule of the requirement extraction rule file 123 is added or changed. The requirement extraction rule update unit 104 reads the law analysis file 111 and the requirement extraction rule file 123 (step S1601). The requirement extraction rule update unit 104 reads the law analysis file 111 to which the requirement extraction rule file 123 to be updated with the priority 904 is applied. Whether or not the requirement extraction rule file 123 is applied is determined, for example, by targeting the law analysis file 111 stored in a specific folder. After reading the law analysis file 111 and the requirement extraction rule file 123, the process advances to step S1602.

  Next, the requirement extraction rule update unit 104 determines whether a requirement extraction rule has been added to the requirement extraction rule file 123 or whether the requirement extraction determination condition 902 of the requirement extraction rule file 123 has been changed (step S1602). ). If the requirement extraction rule is added or the requirement extraction determination condition 902 is changed (YES in step S1602), the process proceeds to step S1603. Otherwise (NO in step S1602), the process proceeds to step S1604. The case where this is not the case is a case where the type 903 is changed without changing the requirement extraction determination condition 902 of the requirement extraction rule 123.

  Next, the requirement extraction rule update unit 104 creates temporary requirement extraction rule match information 304 on the main storage device 203 (step S1603). Specifically, the requirement extraction rule update unit 104 includes a requirement extraction rule in which the legal provisions in the legal provision information 302 of the legal analysis file 111 are added to the requirement extraction rule file 123 or a changed requirement in the requirement extraction rule. It is determined whether or not the extraction determination condition 902 is met. In this determination, all the legal article information 302 having one or more legal requirement information 303 is targeted. If there is a matching part as a result of this determination, temporary requirement extraction rule match information 304 is created on the main storage device 203. After the requirement extraction rule match information 304 is created, the process proceeds to step S1604.

  Next, the requirement extraction rule update unit 104 displays statistical information regarding the requirement extraction rule match information 304 (step S1604). The requirement extraction rule update unit 104 acquires the number of requirement extraction rule match information 304 created on the main storage device 203. Subsequently, the requirement extraction rule update unit 104 determines that the range specified by the rule match location of the requirement extraction rule match information 304 is a part of the clause corresponding location of the legal requirement information 303, and the requirement extraction rule match information The number of the legal requirement information 303 with the same type of 304 and the legal requirement information 303 is acquired. Subsequently, the requirement extraction rule update unit 104 acquires the number of acquired requirement extraction rule match information 304, the acquired number of legal requirement information 303, and the requirement extraction rule match information 304 acquired the number of acquired legal requirement information 303. The value divided by the number of is displayed on the display. After being displayed on the display, the process proceeds to step S1605. The user looks at the information displayed on the display and determines whether to add or change the requirement extraction rule.

  Next, the requirement extraction rule update unit 104 waits for the user's determination regarding addition of the requirement extraction rule and confirmation of change (step S1605). The update extraction rule update unit 104 acquires information on whether or not the user accepts the addition of the requirement extraction rule and the confirmation of the change, for example, by acquiring an operation event such as a user pressing an OK button or a cancel button. To get. After obtaining the determination result that approves the user's confirmation, the process proceeds to step S1606. If the user does not accept the addition or change of the requirement extraction rule, such as when the user presses the cancel button, the requirement extraction rule update unit 104 ends the process in this step (step S1605).

  Next, the requirement extraction rule update unit 104 calculates the priority 904 of the requirement extraction rule (step S1606). The requirement extraction rule updating unit 104 uses the number (A) of the legal requirement information 303, the number (B) of the requirement extraction rule match information 304 acquired in step S1604, the total number (C) of the legal requirement information 303, and the like. The priority 904 is calculated. For example, the priority 904 is calculated as (A / B) × (B / C). After calculating the priority 904, the process proceeds to step S1607.

  Next, the requirement extraction rule update unit 104 updates the law analysis file 111 and the requirement extraction rule file 123 (step S1607). The requirement extraction rule update unit 104 adds the requirement extraction rule match information 304 temporarily stored in the main storage device 203 in step S1603 to the law analysis file 111. Subsequently, the requirement extraction rule update unit 104 reflects the priority 904 of the requirement extraction rule to be added or changed in the requirement extraction rule file 123.

  As a modified example of the above processing, when the requirement extraction rule update processing 104 grasps an event in which addition, change, or deletion of the legal requirement information 303 or the requirement extraction rule match information 304 of the legal analysis file 111 is changed. The above processing may be executed. In this case, steps S1602, S1604, and S1605 are omitted.

  The above-described embodiments of the present invention are examples for explaining the present invention, and are not intended to limit the scope of the present invention only to those embodiments. Those skilled in the art can implement the present invention in various other modes without departing from the gist of the present invention.

100 legal analysis support device, 101 analysis target determination unit, 102 requirement extraction unit, 103 requirement classification unit, 104 requirement extraction rule update unit, 111 legal analysis file, 112 data requirement file, 113 use case requirement file, 114 term definition file, 121 pattern definition file, 122 analysis target determination rule file, 123 requirement extraction rule file, 201 computer, 202 CPU, 203 main storage device, 204 auxiliary storage device, 205 network interface, 206 I / O interface, 207 internal bus

Claims (12)

A legal analysis support device that assists in extracting requirements related to a processing system for processing related to the law from laws and regulations,
Legal text storage means for storing the text of the law;
Requirement extraction for associating and storing a requirement extraction condition for determining whether or not a requirement related to the processing system is included in the provisions of the law, and a requirement type when the requirement extraction condition is met Rule storage means;
Requirement determining means for determining whether or not a requirement for the processing system is included in a predetermined unit of the provisions of the law based on the requirement extraction condition;
Type display means for displaying on the display device a requirement type corresponding to one or more of the requirement extraction conditions determined to include a requirement;
Requirement type accepting means for accepting designation of the requirement type of the requirement set by the user;
Requirement receiving means for receiving an input of a requirement corresponding to the requirement type in the predetermined unit from a user;
A legal analysis support apparatus comprising: a requirement storage control unit that stores legal requirement information that associates the predetermined unit, the specified requirement type, and the input requirement with a legal requirement information storage unit. The requirement extraction rule storage means stores the requirement extraction condition and an index indicating a degree of certainty about the requirement extracted by the requirement extraction condition in association with each other,
The law analysis support apparatus according to claim 1, wherein the type display unit displays the requirement type based on the index associated with the requirement type. 3. The legal analysis support apparatus according to claim 2, wherein the type display means displays a requirement type in which the index is greater than a predetermined value and a requirement type in which the index is equal to or less than the predetermined value in different areas. The legal requirement analysis support apparatus according to any one of claims 1 to 3, wherein the requirement type includes data, use cases, and term definitions. A requirement location receiving means for receiving designation of a description location of the requirement in the predetermined unit from a user;
The legal requirement analysis support apparatus according to any one of claims 1 to 4, wherein the requirement storage control unit stores requirement location information indicating a description location of the requirement in association with the predetermined unit. The requirement extraction rule storage means stores the requirement extraction condition and an index indicating a degree of certainty about the requirement extracted by the requirement extraction condition in association with each other,
Condition receiving means for receiving update or addition of the requirement extraction condition;
A change that identifies the description locations corresponding to the requirement extraction conditions and grasps the number of the specified description locations for a plurality of predetermined units of the provisions of the law based on the updated or changed requirement extraction conditions Condition judging means;
In the legal requirement information, the number of requirements corresponding to a description location that is the same requirement type as the requirement type corresponding to the requirement extraction condition and at least partially overlaps the specified description location. Legal requirement judgment means to grasp,
An index determining unit that determines an index to be associated with the requirement extraction condition based on the grasped number of the description portions and the grasped number of the requirement, and stores the index in association with the requirement extraction condition. 5. The legal analysis support device according to 5. Analysis target determination rule storage means for storing an analysis target determination rule for determining whether or not the predetermined unit of the provisions of the law is an analysis target of requirement extraction;
Analysis target determination means for determining whether or not a predetermined unit of the provisions of the law is an analysis target;
The analysis target display unit that further displays the predetermined unit text and information indicating whether or not the predetermined unit is an analysis target in association with each other. Legal analysis support equipment. When the predetermined unit is subordinate to another predetermined unit, the analysis target determining unit determines the predetermined unit if it is determined that the other predetermined unit is an analysis target. The legal analysis support apparatus according to claim 7, wherein the legal analysis support apparatus is determined as an analysis target. The analysis target determination rule includes a rule for determining that the analysis target is not an analysis target when a description of “decompose” is included in the text of a predetermined unit. The legal analysis support device described. Claim 1 thru | or further comprising the requirement classification | category means which classify | regulates and outputs the legal requirement information containing the said predetermined | prescribed unit, the said designated requirement classification | category, and the said input requirement to a different file for every said requirement classification. The legal analysis support apparatus according to claim 9. A law analysis support method by a law analysis support device that supports the extraction of requirements related to a processing system for processing related to the law from a law,
The legal text storage means of the legal analysis support device stores the legal text,
The requirement extraction rule storage means of the legal analysis support device matches the requirement extraction condition for determining whether or not the legal provision contains a requirement related to the processing system, and the requirement extraction condition And store the requirement type in association with
The requirement determination means of the law analysis support device determines whether or not a requirement for the processing system is included in a predetermined unit of the law provision based on the requirement extraction condition,
The type display means of the legal analysis support device causes the display device to display a requirement type corresponding to the one or more requirement extraction conditions determined to include a requirement,
The requirement type accepting unit of the legal analysis support device accepts designation of the requirement type of the requirement set by the user,
The requirement receiving means of the legal analysis support device receives an input of a requirement corresponding to the requirement type in the predetermined unit from a user,
Legal analysis that causes the requirement storage control means of the legal analysis support apparatus to store legal requirement information that associates the predetermined unit, the specified requirement type, and the input requirement with the legal requirement information storage means Support method. A legal analysis support program for causing a computer that constitutes a legal analysis support device to perform support for extracting requirements related to a processing system for performing a process related to the law from a law,
The computer,
Based on a requirement extraction condition for determining whether or not a requirement related to the processing system is included in the provision of the law, the requirement for the processing system is included in a predetermined unit of the provision of the law. Requirement judging means for judging whether or not,
Type display means for displaying on the display device a requirement type corresponding to one or more of the requirement extraction conditions determined to include a requirement;
Requirement type accepting means for accepting designation of the requirement type of the requirement set by the user;
Requirement receiving means for receiving an input of a requirement corresponding to the requirement type in the predetermined unit from a user;
A legal analysis support program that functions as a requirement storage control unit that stores legal requirement information that associates the predetermined unit, the specified requirement type, and the input requirement with a legal requirement information storage unit.

Images