JP2016001411A - Existing information system screen specification extraction device and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a user with specifications by extracting the specifications about variations of a business screen which are caused when different input and confirmation processing have to be executed due to processing contents even in the same kind of business processing in the existing business system.SOLUTION: The existing system screen specification extraction device is a device for extracting screen program specifications from a screen log of collected existing systems. The existing system screen specification extraction device includes: a screen variation extraction part for extracting variations of a screen structure of each screen program from a set of inputted screen logs by comparison processing among the collected screen logs; a screen variation information recording part for storing acquired screen variation information; and an extracted screen specification output part for outputting a list of screen types with screen variations existing and details of each screen variation as specifications to a user on the basis of the recorded screen variation information.

Description

  The present invention relates to a technique for extracting screen specifications for analyzing problems and the like of an existing information system (existing information system or existing system).

  Currently, information systems are used to perform various tasks. When the time has passed since the introduction of the information system, the information system is replaced or changed to a new system in order to solve the problem. In such replacement, etc., problems in the existing information system before replacement are analyzed. For this reason, it is necessary to extract screen specifications. As a background art of this technical field, there is Japanese Patent No. 5108660 (Patent Document 1). In this publication, “a first step in which an information collection device extracts information in a table format or a database format from a plurality of Web documents accessible via a communication network based on tags included in the Web document; From the extracted information in the table format or database format, based on the dependency relationship between the information indicated by the tag, the relationship between the attribute dependent on the predetermined item and the attribute value indicating the content of the attribute Information that unifies the information for each of the plurality of associated Web documents by associating the second step of extracting the information with the information having the relationship between the item, the attribute, and the attribute value for each extracted Web document At least a third step stored in the storage means, and the second step exceeds a predetermined threshold for a predetermined item Of information dependent common in Web documents, information collection method and extracting the attributes and attribute values. "Is described as (see claim 1).

  There is JP-A-2005-92889 (Patent Document 2). In this publication, “a structure information block extraction step for generating a structure information block tree of the web page, which is an information block extraction method for segmenting one web page into a plurality of information blocks having coherent content; And a semantic information block extraction step of clustering and merging the structural information blocks and labeling the meaning of the resulting blocks. ”(See claim 1).

Japanese Patent No. 5108660 Japanese Patent Laid-Open No. 2005-92889

  The problem of the present invention is that in the existing business system, even if it is the same type of business processing, it extracts the specifications regarding the variation of the business screen caused by having to perform different input and confirmation processing from the processing content, It is to be presented to the user.

  Patent Document 1 extracts an attribute value indicating the content of information extracted by a method of extracting information in a table or database format based on tag information included in a Web document and a dependency relationship of information included in the tag How to do is described. However, this method only extracts information displayed on the screen based on the knowledge specific to the system to be analyzed such as a table or a database. For example, as Web browsing's name in such a welcome message of "Hello Hitachi Taro" to be displayed for each viewer of the page "Taro Hitachi", to extract the value of the embedded variable in nature statement It is not possible to extract a value that causes variation of each screen.

  Further, Patent Document 2 describes a method for extracting information blocks in a web page by using an information block given by a tag for a certain web page. According to this method, it is possible to clarify the information shown in one web page, but on the other hand, the differences in input information and display information that occur in the flow of work to be processed, that is, screen variations and the data that causes them Can not be revealed.

In order to solve the above-mentioned problems, in the present invention, these specifications are specified by calculating a difference in information about a screen when there is a variation in an arbitrary screen using a screen log. More specifically, the following configuration is adopted.
The present application includes a plurality of means for solving the above-described problems. To give an example, the present system is an existing system screen specification extraction device that extracts a screen program specification of the existing system from a screen log of the existing system, and the screen A difference extraction unit that collects and collects a plurality of screen logs of related screens for the logs, compares each related information for the collected plurality of screen logs, and extracts difference information regarding the difference, and the difference information An analysis unit that separates a common area and a variable area in the screen of the screen log, and a screen specification output unit that specifies and outputs information about the variable area as a result of the analysis as a screen specification of the screen; Have An existing screen specification extraction method using the existing system screen specification extraction device is also an aspect of the present invention.

  According to the present invention, it is possible to clarify differences in input information and display information on a business system screen, that is, screen variations and data that cause them.

It is an example of the block diagram of the existing system screen specification extraction apparatus 100 in a present Example. It is an example of the conceptual diagram of the input / output relationship of the screen program which the existing system screen specification extraction apparatus 100 makes a specification extraction object. It is an example of a structure of the screen variation difference extraction program 120. 4 is an example of an information configuration stored in an existing system screen log recording unit 150. 4 is an example of an information configuration stored in a screen variation information recording unit 160. It is explanatory drawing of an example of screen A real display code (4) 350. 3 is a detailed configuration example of an existing system screen log recording unit 150. 4 is an example of a screen display code management table stored in a screen display code recording unit 151. It is an example of the screen transition table stored in the screen transition information recording part 152. FIG. 3 is a detailed configuration example of a screen variation information recording unit 160. 4 is a detailed configuration example of a screen variation difference extraction program 120. It is an example of an explanatory diagram of a screen A display code (1) 320 analyzed by the screen structure extraction program 121. It is an example of a screen display tree 3300 of each screen A display code (2) 330. It is an example of a screen display tree 3400 of each screen A display code (3) 340. It is an example of the screen display tree 3500 of each screen A display code (4) 350. It is an example of a screen structure variation management table stored in the screen structure variation management information recording unit 161. It is an example of explanatory drawing of the analysis of the fixed character string part and variable character string part of a character string. It is explanatory drawing of an example of a screen structure tree. FIG. 10 is an explanatory diagram of a screen structure tree 5200. 10 is a list of values included in a fixed character string node of a screen structure tree 5200. 5 is an example of an explanatory diagram of a screen structure tree. It is an example of the table of the screen structure variation management information recording part in which screen structure tree ID was written. It is an example of explanatory drawing of subtree structure feature value calculation. It is an example of an aggregation structure tree. It is explanatory drawing of the structure aggregation tree obtained from the screen structure tree. It is explanatory drawing of the structure aggregation tree obtained from the screen structure tree. It is an example of the screen structure variation management table in which structure aggregation tree ID writing is written. It is an example of the screen structure variation management table in which the value of the general structure feature value is written. It is an example of the result obtained by analyzing a tag node. It is an example of the result obtained by analyzing a structure aggregation tree. It is an example of the screen variation management table in which the screen variation ID 1619 of the table is written. It is an example of screen variable attachment information extracted by the screen variable extraction program 124 and written in the screen variable recording unit 163. This is an example of variation-variable related information. It is an example of the result of causal analysis and frequency analysis of variation-variable relation information. It is an example of the screen variation analysis result table of the screen variation factor analysis result recording unit 170. It is an example of a display of a screen variation analysis result list presented by the extraction screen specification output program 140. It is an example of a display of the screen variation detailed information shown by the extraction screen specification output program 140. It is a 2nd display example of the screen variation detailed information shown by the extraction screen specification output program 140. FIG. It is a 3rd example of a display of the screen variation detailed information shown by the extraction screen specification output program 140. FIG. It is a display example of factor information of screen variations presented by the extraction screen specification output program 140. 4 is a flowchart showing an entire procedure for extracting an existing system screen specification using the apparatus 100. It is a flowchart which shows the procedure of the process which extracts a screen variation. It is a flowchart which shows the detailed procedure of a process of the screen structure extraction program 121. FIG. It is a flowchart which shows the detailed procedure of a process of the screen variable part analysis program 122. FIG. It is a flowchart which shows the detailed procedure of the process of the screen variation analysis program 123. FIG. It is a flowchart which shows the detailed procedure of a process of the screen variable extraction program. It is a flowchart which shows the detailed procedure of the process of the screen variation factor analysis program 130. It is a flowchart which shows the detailed procedure of the process of the extraction screen specification output program 140. FIG.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
In this embodiment, an example of the existing system screen specification extraction device 100 will be described.
FIG. 1 is an example of a configuration diagram of an existing system screen specification extraction device 100 in the present embodiment.
The existing system screen specification extraction device 100 includes a CPU (Central Processing Unit) 101, a memory 102, an external storage device 103, an input device 106, an output device 107, and a communication device 108. The CPU 101, the memory 102, An external interface 105 is connected. An external storage device 103, an input device 106, an output device 107, and a communication device 108 are connected to the external interface 105.

  The external storage device 103 holds an existing screen log storage program 110, a screen variation difference extraction program 120, a screen variation factor analysis program 130, and an extracted screen specification output program 140 as processing programs executed by the CPU 101. These programs are read from the external storage device 103 to the memory 102 and executed by the CPU 101. The external storage device 103 also includes an existing system screen log recording unit 150, a screen variation information recording unit 160, a screen variation factor analysis result recording unit 170, and a screen description grammar recording unit 180.

  FIG. 2 is an example of a conceptual diagram of the input / output relationship of a screen program that is subject to specification extraction by the existing system screen specification extraction device 100. The screen A primitive program 301 receives a request from the user of the system, receives the previous screen input data 310 input on the previous screen of the screen A and the data 311 from the database in the screen transition, and displays the screen to the user. A Real display code is output. In FIG. 2, as an example, screen A actual display code (1) 320, screen A actual display code (2) 330, screen A actual display code (3) 340, and screen A actual display code (4) 350 are output. Represents an image.

  3 to 6 are explanatory diagrams of a screen A actual display code group used for explanation in the present embodiment. An example of a screen display code for the common screen type “repayment plan confirmation screen” will be described below.

FIG. 3 is an explanatory diagram of an example of the screen A actual display code (1) 320. The figure indicated by reference numeral 320i shows a display image of a repayment plan confirmation screen for the name “Hitachi Taro”. Reference numeral 320c shows an example in which a screen display code for displaying the display image is described in the HTML format. FIG. 4 is an explanatory diagram of an example of the screen A actual display code (2) 330. As in FIG. 3, the diagram indicated by reference numeral 330 i is a display image of the repayment plan confirmation screen for the name “Yokohama Hanako”, and reference numeral 320 c is an example in which the screen display code for displaying the display image is described in HTML format. It is.

FIG. 5 is an explanatory diagram of an example of the screen A actual display code (3) 340. As in FIG. 3, the diagram indicated by reference numeral 340 i is a display image of the repayment plan confirmation screen for the name “Tokyo Miyako”, and reference numeral 340 c is an example in which the screen display code for displaying the display image is described in HTML format. FIG. 6 is an explanatory diagram of an example of the screen A actual display code (4) 350. Similar to FIG. 3, the diagram indicated by reference numeral 350 i is a display image of the repayment plan confirmation screen for the name “Saburo Ibaraki”, and reference numeral 350 c is an example in which the screen display code for displaying the display image is described in HTML format. It is.

  3 to 6 show examples of the screen A display code group of FIG. 2 used for explanation in this embodiment. The screen display codes 320c, 330c, 340c, and 350c describe portions necessary for the description of this embodiment, and descriptions that are not directly related to the description are omitted. Further, in this embodiment, only four examples of the screen A display code of FIG. 2 are shown, but this is for the sake of simplicity of explanation, and a large number of screen displays actually obtained through actual operation of the business system. The code exists.

  In FIG. 2, only the screen A source program 301 is shown for simplicity, but there are a plurality of screen source programs in the actual system. In this embodiment, a screen source program identified by an identifier unit such as a name is referred to as a screen type, and a difference in structure of screen actual display codes output in the same screen type is referred to as a variation. For example, the screen image indicated by reference numeral 320i and the screen image indicated by reference numeral 330i are the same “repayment plan confirmation screen”, and have the same screen type. The lower three lines from the customer information indicated by reference numeral 321i and the lower three lines of customer information indicated by reference numeral 331i differ in the displayed values, but the items of name, address, and repayment method are common. However, while the future repayment plan indicated by reference numeral 325i shows the repayment date and the amount of each repayment in a bulleted form, the future repayment plan indicated by reference numeral 335i is shown in a tabular form. The structure is different. An example in which the screen types are the same but the displayed information is different is called a variation. One of the purposes of the present embodiment is to automatically extract the types of variations in this single screen type from a large number of screen display codes and to clarify the variations including those with a low frequency.

  FIG. 7 is a detailed configuration example of the existing system screen log recording unit 150. The existing system screen log recording unit 150 includes a screen display code recording unit 151 and a screen transition information recording unit 152. The screen display code recording unit 151 records a table for managing these screen display codes in addition to the screen display codes themselves.

  FIG. 8 is an example of a screen display code management table stored in the screen display code recording unit 151. In this embodiment, the screen display code management table includes a screen type ID 1511, a screen type name 1512, and a screen display code ID 1513. The screen type ID 1511 is an ID uniquely given to the screen type name 1512, and the screen display code ID 1513 is a uniquely given ID for referring to the actual state of the screen display code. Record 1515 indicates screen A actual display code (1) 320, record 1516 indicates screen A actual display code (2) 330, record 1517 indicates screen A actual display code (3) 340, and record 1518 indicates screen A. An actual display code (4) 350 is shown. These pieces of information are stored acquired by the existing screen log storage program 110.

  Returning to FIG. 7, screen transition information is recorded in the screen transition information recording unit 152.

  FIG. 9 is an example of a screen transition table stored in the screen transition information recording unit 152. In this embodiment, the screen transition table includes a screen transition ID 1521, a current screen display code ID 1522, and a previous screen display code ID 1523. The values included in the current screen display code ID 1522 and the previous screen display code ID 1523 are recorded in the screen display code ID 1513 stored in the screen display code recording unit 151. For example, the record 1525 indicates that the previous screen of the screen A display code (1) 320 is a screen indicated by the screen display code recorded in “IRP — 921”.

  FIG. 10 is a detailed configuration example of the screen variation information recording unit 160. In this embodiment, the screen variation information recording unit 160 includes a screen structure variation management information recording unit 161, a screen structure tree recording unit 162, and a screen variable recording unit 163. Details of data stored in each unit will be described later together with processing of the screen variation difference extraction program 120.

  FIG. 11 is a detailed configuration example of the screen variation difference extraction program 120. In this embodiment, the screen variation difference extraction program 120 includes a screen structure extraction program 121, a screen variable part analysis program 122, a screen variation analysis program 123, and a screen variable extraction program 124.

  The screen structure extraction program 121 first reads the screen display code stored in the screen display code recording unit 151 of the existing system screen log recording unit 150, and uses the screen display code grammar recorded in the screen description grammar recording unit 180. Based on this, the structure of each screen display code is analyzed.

  FIG. 12 is an example of an explanatory diagram of the screen A display code (1) 320 analyzed by the screen structure extraction program 121. The screen structure extraction program 121 reads the screen A display code (1) 320 from the screen display code recording unit 151 and analyzes the structure according to the grammar of the screen display code recorded in the screen description grammar recording unit 180. In this embodiment, the screen display tree 3200 is constructed by analyzing based on the HTML grammar. The tree shown in the screen display tree 3200 is omitted except for the portions necessary for the description of this embodiment. Since the existing method is also known about the construction method of a screen display tree, the detailed description in a present Example is omitted. Note that a circle in the screen display tree 3200 represents a root node or an intermediate node indicating a child structure below, and a rectangle represents a terminal node. Information on the HTML tag is stored in the root node and the halfway node, and a character string displayed on the normal screen is stored in the terminal node. Hereinafter, in the present embodiment, the root node and the midway node are referred to as tag nodes, and the terminal node is referred to as a character string node. For example, the tag node 3210 is a node to which the body tag is assigned in the screen A display code (1) 320, and there is an html tag node 3205 as a parent tag node, a div tag node 3211 as a child node, and a div tag node 3212 different from this. It shows that. Further, this number is given to the lexical node according to a certain rule. In the present embodiment, numbers are assigned in the order in which they appear as a result of depth-first search. For example, “1” shown in the rectangle of the lexical node 3220 indicates that the number is 1 in the display tree 3200.

  A table 3250 displays a list of lexical node values in the screen display tree 3200. The number 3251 means the number given to the lexical node of the screen display tree 3200, and the character string 3252 means the character string existing at the position of the lexical node. For example, the lexical node 3220 shows the number 1 in the rectangle, which corresponds to the record 3261. That is, the lexical code 3220 indicates that the character string “customer information” exists. In this embodiment, the lexical nodes are separately summarized in a table for explanation, but the character string information may be directly stored in the lexical nodes of the screen display tree. The screen structure extraction program 121 assigns a key 3201 (TR_CRP_1001 in this example) that can uniquely access the screen display tree 3200 of the analysis result.

  Next, the screen structure extraction program 121 calculates an approximate screen feature value for each screen display tree. The approximate structure value is calculated based on the structure of the screen display tree and the type of tag node. For example, it may be a character string such as “htmlheadbodydivh2...” In which a tag node and a lexical node are circulated from the root tag node of the tree by a depth-first search and the tag type of the tag node obtained at that time is connected as a character string. The result of calculating the hash value may be used. In this embodiment, the result of calculating the hash value is shown. When calculating the summary screen feature value, the fact that a lexical node exists is used for the lexical node, and the character string itself included in the lexical node is not subject to value calculation. A feature value 3202 is an example of a schematic screen feature value of the screen display tree 3200.

  When the above processing is completed, the screen structure extraction program 121 writes the access key to the screen display tree and the approximate screen feature value of the screen display tree in the screen structure variation management information recording unit 161. In addition, the screen display tree is written to the screen structure tree recording unit 162 and the control is transferred to the screen variable unit analysis program 122.

  FIG. 13 to FIG. 15 are examples of analysis results of each screen A display code used in the description of this embodiment. The method of creating the display tree and the notation of each figure are the same as in FIG. 12, and details are omitted. Each element will be described as necessary in the operation of the screen structure extraction program 121 and the screen structure extraction program 121 described later.

  FIG. 13 is an example of a screen display tree 3300 for each screen A display code (2) 330. The screen display tree 3300 is an analysis result of the screen A display code (2) 330 by the screen structure extraction program 121. Table 3350 displays a list of lexical node values in the screen display tree 3200.

  FIG. 14 is an example of a screen display tree 3400 for each screen A display code (3) 340. The screen display tree 3400 is an analysis result of the screen A display code (3) 3400 by the screen structure extraction program 121. A table 3450 displays a list of lexical node values in the screen display tree 3400.

  FIG. 15 is an example of a screen display tree 3500 for each screen A display code (4) 350. The screen display tree 3500 is an analysis result of the screen A display code (4) 3500 by the screen structure extraction program 121. Table 3550 is a list of lexical node values in the screen display tree 3500.

  FIG. 16 is an example of a screen structure variation management table stored in the screen structure variation management information recording unit 161. The screen structure variation management table 1610 includes a screen type ID 1611, a screen type name 1612, a screen display code 1613, a screen display tree ID 1614, an approximate screen feature value 1615, a screen structure tree ID 1616, a repeated structure aggregation tree ID 1617, and a structure aggregation tree feature value. 1618 is a table having a column for recording a screen variation ID 1619. In the screen type ID 1611, the screen type name 1612, and the screen display code 1613, the screen type ID 1511, the screen type name 1512, and the screen display code 1513 of the screen display code analyzed by the screen structure extraction program 121 are written, and the screen display tree ID 1614 is written. An access key to the screen display tree constructed by the screen structure extraction program 121 is written to the screen screen, and an approximate screen feature value calculated by the screen structure extraction program 121 is written to the approximate screen feature value 1615.

  Returning to FIG. 11, the screen variable part analysis program 122 is written in the screen structure tree recording unit 162 and the information of the screen structure management table analyzed by the screen structure extraction program 121 and written in the screen structure variation management information recording unit 161. The variable part of each screen display code is extracted based on the screen display tree.

  First, the screen variable part analysis program 122 groups screen display trees using the approximate screen feature value 1615 of the screen structure variation management table 1610 as a key. For example, the screen A display code (1) 320 (screen display code IDCRP — 1001) indicated by the record 1621 and the screen A display code (3) 340 (screen display code IDCRP — 1003) indicated by the record 1623 are “bdX1Q3341 ”Are the same value, and are processed as the same group. Since the screen A display code (2) 330 (screen display code IDCRP — 1002) indicated by the record 1622 and the screen A display code (4) 350 (screen display code IDCRP — 1004) indicated by the record 1624 have different general screen feature values, they are in different groups. Process as. Hereinafter, the operation of the screen variable part analysis program 122 will be described by taking as an example the group of the approximate screen feature value “bdX1Q3341” to which the screen A display code (1) 320 and the screen A display code (3) 340 belong.

  The screen variable part analysis program 122 acquires the screen display tree from the screen transition information recording unit 152 for the group having the value of the approximate screen feature value “bdX1Q3341” from the screen structure variation management table 1610 using the screen display tree ID 1613 as a key. In practice, a large number of screen display trees are acquired. However, in this embodiment, for simplicity, the screen display tree 3200 of the screen A display code (1) 320 and the screen display tree 3500 of the screen A display code (4) 350 are used. These two are used in the following description as representative examples.

  As described above, screen display trees having the same general screen feature value have the same structure. That is, each screen display code appears at the lexical node portion. In addition, since the same structure is used in the same screen type, the character strings included in the lexical node having the same number are considered to indicate the same type of value. The screen structure extraction program 121 aggregates the values of lexical nodes having the same number for each acquired screen display tree. Then, the lexical difference is calculated for the aggregated character string group, the fixed character string part common to all the aggregated character strings, and the variable character string that has changed in all the aggregated character strings Disassemble the part.

  FIG. 17 is an example of an explanatory diagram of analysis of a fixed character string portion and a variable character string portion of a character string.

  A rectangle 4100 shows an analysis image of the character string group of number 1 in the general screen feature value “bdX1Q3341”. Table 4110 shows an example of the result of aggregating the character string group of No. 1 in each screen display tree of the general screen feature value “bdX1Q3341” group. The record 4111 is the value of the character string of number 1 in the screen display tree 3200 (see the record 3261 in FIG. 12). The record 4112 is the value of the character string of number 1 in the screen display tree 3400 (see the record 3461 in FIG. 14). In this embodiment, since the character string “customer information” is collected in the table 4110, only the fixed character string portion 4115 “customer information” is obtained as a result, and there is no variable character string portion. As a result, it is obtained that the number 1 of each screen display tree of the general screen feature value “bdX1Q3341” group is composed of only the fixed character string portion 4115 “customer information”.

  A rectangle 4200 shows an image of analysis of the character string group of number 2 in the general screen feature value “bdX1Q3341”. Table 4210 is an example of a result of aggregating the character string group of number 2 in each screen display tree of the summary screen feature value “bdX1Q3341” group. The record 4211 is the value of the character string of number 2 in the screen display tree 3200 (see the record 3262 in FIG. 12). The record 4212 is the value of the character string of number 2 in the screen display tree 3400 (see the record 3462 in FIG. 14). In this embodiment, the character strings stored in the table 4210 start from a common character string in which three characters are “name:” from the start of the character string. Therefore, the portion is extracted as a fixed character string portion 4215 “name:”. Subsequent character strings are not common to the respective screens, and therefore are extracted as a variable character string portion 4216. As a result, it is obtained that the number 2 of each screen display tree of the general screen feature value “bdX1Q3341” group is composed of the fixed character string portion 4215 “name:” followed by the character string and the variable character string portion 4216.

  Next, the screen variable part analysis program 122 calculates the variable part in the screen display based on the analysis result of the fixed character string part and the variable character string part of the character string included in the character string node obtained by the above process. Build the revealed screen structure tree. Specifically, a new tree in which the character string tag of each number is replaced with a fixed character string node whose node is a fixed character string portion obtained as a result of analysis and a variable character string node whose node is a variable character string portion That is, a screen structure tree is constructed. An identification number is assigned to each of the replaced fixed character string node and variable character string node according to a certain rule so as to be newly unique in the screen structure tree.

  FIG. 18 is an explanatory diagram of an example of the screen structure tree. In the screen structure tree 5100 shown in the figure, the screen variable part analysis program 122 analyzes the screen display tree having the above-mentioned general screen feature value “bdX1Q3341”, and based on the result, the character string node is changed to the fixed character string node and the variable. This is the result of replacement with a string node. In the terminal node of the screen structure tree, a node indicated by a rectangle is a fixed character string node, and a node indicated by a rounded rectangle is a variable character string node. The fixed character string node 5110 and the variable character string node 5111 obtain the character string node of the number 2 of the screen display tree having the general screen feature value “bdX1Q3341” (for example, the character string node 3221 of the screen display tree 3200) as a result of the analysis. The node indicating the fixed character string portion 4215 and the node indicating the variable character string portion 4216 are respectively replaced. A table 5150 shows values of fixed character strings included in the fixed character string of the screen structure tree 5100.

  In FIGS. 19 to 21, an example of a screen structure tree obtained from the analysis result of the group having the general screen feature value “a2VI3fakd” and the general screen feature value “3Ikadj8ag” (see FIG. 16) not described in detail above. Show. Since the construction method and the drawing method are the same as those in FIG. 18, the details are omitted.

FIG. 19 is an example of an explanatory diagram of the screen structure tree 5200. The screen structure tree 5200 is a result obtained by the screen variable part analysis program 122 analyzing a screen display tree having the general screen feature value “a2VI3fakd”.
FIG. 20 is a list of values included in the fixed character string node of the screen structure tree 5200.

  FIG. 21 is an example of an explanatory diagram of the screen structure tree 5300. The screen structure tree 5300 is a result obtained by the screen variable part analysis program 122 analyzing a screen display tree having the approximate screen feature value “3Ikadj8ag”. A table 5350 is a list of values included in the fixed character string node of the screen structure tree 5300.

  As described above, the screen variable part analysis program 122 constructs a screen structure tree of each approximate screen feature value, and then assigns an ID (for example, see 5101: FIG. 18) that allows access to each screen structure tree. The screen structure tree ID is written in the variation management information recording unit 161, and the obtained screen structure tree group is written in the screen structure tree recording unit 162. The above is the operation of the screen variable part analysis program 122.

  FIG. 22 is an example of a table of the screen structure variation management information recording unit in which the screen structure tree ID is written. The screen structure variation table example 1610a is a result of writing the screen structure tree ID obtained as a result of the above processing into the screen structure tree ID column 1616 in the table.

  Returning to FIG. 11, the screen variation analysis program 123 acquires the screen structure tree group written in the screen structure tree recording unit 162 by the screen variable part analysis program 122 and analyzes the screen variation of each screen type. More specifically, the screen variation analysis program 123 analyzes the screen structure tree, finds a repetitive portion of the structure, and aggregates the same as a single repetitive portion, thereby extracting a highly accurate screen variation. For example, since the screen display tree 3300 and the screen display tree 3500 have different numbers of nodes to be held, different approximate screen feature amounts are calculated and written in the screen structure tree recording unit 162 as different types of screen structure trees. However, as shown in the screen A display code (2) 330 (see FIG. 4) and the screen A display code (2) 350 (see FIG. 6), only the number of records in the portion displayed in the table format is different. Therefore, the information represented is the same, and if the number of records is different, a different type of variation will include a lot of noise for the developer receiving the results. Therefore, the accuracy of the resulting screen variations is increased by finding and consolidating repeated parts.

  The screen variation analysis program 123 first calculates, for each tag node existing in each screen structure tree, a feature value having the same value if it has the same structure with respect to a subtree including itself. This is hereinafter referred to as a subtree structure feature value. The data used for calculating the feature value includes the information and position of the tag node included in the subtree, the character string information and position of the fixed character string node included in the subtree, and the position of the variable character string included in the subtree. As for the variable character string, since the value that actually enters the variable is variable, the position is used to calculate the subtree structure feature value. Here, regarding the variable character string, the above-mentioned calculation may be performed using only the position without considering the content.

  FIG. 23 is an example of an explanatory diagram for calculating a subtree structure feature value. The tag node 5230 is the same as the tag node 5230 in the screen structure tree 5200 (see FIG. 19). This figure shows a subtree below the tag node 5230. Each tag node is given Id for convenience of explanation. Table 6200 is a list of information obtained by converting information obtained by patroling the subtree starting from each tag node into a character string. In this example, the character string enclosed by the symbols “<” and “>” in the character string is tag node information, the character string enclosed by the symbols “” ”and“ ”” is fixed character string node information, The character string “[var]” indicates the appearance position of the variable character string node. For example, a record whose id is 17 indicates that a variable character string node, a fixed character string node whose character string value is “/”, and a variable character string node exist under the “td” tag node in this order. In this way, a subtree cyclic character string is calculated for each subtree. This partial tree cyclic character string may be used as a partial tree structure feature value. However, since the character length is too long in the partial tree close to the root of the screen structure tree, the hash of this character string is calculated in this embodiment. For example, the same character string is assigned a value that is easy to group. Table 6210 is an example of a list of subtree structure feature values calculated by the above processing. For the sake of explanation, a highly readable value is described for convenience.

  Next, the screen variation analysis program 123 finds and aggregates repeated structures included in each screen structure tree based on the obtained partial tree structure feature values. The screen variation analysis program 123 circulates in order from the root node of the screen structure tree to be analyzed, and acquires the subtree structure feature values of the subtree starting from the child node of the current tag node. If there is a subtree having the same acquired subtree structure feature value, it is determined that the subtree structure is repeated, and subtrees having a common structure are integrated into one. After aggregation, a flag indicating repetition is given to the start tag node of the subtree of the aggregation result. After the above processing is completed, a repetitive structure aggregation tree pair in which repetitive structures in the screen structure tree are aggregated is assigned, and a repetitive structure aggregation tree ID that is uniquely accessible is assigned.

  Hereinafter, description will be made by taking as an example the subtree from which the subtree structure feature value of FIG. The screen variation analysis program 123 refers to the sub-tree structure feature value of the child node of the tag node 5230 when it reaches the tag node 5230 in the tour. The subtree structure feature value of the tag node assigned 13 to the id which is the first child node of the tag node 5230 is SUBHASH_13. The subtree structure feature value of the tag node to which 16 is assigned to id which is the second child node of the tag node 5230 is SUBHASH_16. Since these two nodes have different subtree structure feature values, it is determined that they have different structures. The subtree structure feature value of the tag node assigned 19 to the id that is the third child node of the tag node 5230 is SUBHASH_13. At this time, the tag node having id 16 and the tag node having id 19 have the same partial tree structure feature value. Therefore, the screen variation analysis program 123 determines that subtrees starting from these two tag nodes can be aggregated, and aggregates them. Although omitted, the sub-tree structure feature value of the tag node assigned id 22 which is the fourth child node of tag node 5230 is also the same as the sub-tree structure feature value of id “13” and id “19”. Since it has

  FIG. 24 is an example of an aggregate structure tree. As a result of the above processing, the repeated structures of the partial trees of the screen structure tree 5200 are aggregated. A tag node 7030 corresponds to the tag node 5230 in FIG. The right subtree of the tag node 5230 is a repetitive unit obtained as an aggregation result, and the flag of repetition is turned on for the start tag node 7031 of the subtree as shown in the balloon diagram 7040. After the structure aggregation tree 7000 is constructed, a structure aggregation ID 7001 that can uniquely access the structure aggregation tree 7000 is assigned.

  FIG. 25 is an explanatory diagram of a structure aggregation tree obtained from the screen structure tree 5100. Since the screen structure tree 5100 has no repeated structure, the structure aggregation tree 7100 has the same shape as the screen structure tree 5100.

  FIG. 26 is an explanatory diagram of a structure aggregation tree obtained from the screen structure tree 5300. Since the screen structure tree 5300 has no repeated structure, the structure aggregation tree 7200 has the same shape as the screen structure tree 5300.

  After constructing the structure aggregation tree in which the screen structure trees are aggregated as described above, the screen variation analysis program 123 obtains the record corresponding to the screen structure tree ID before aggregation in the table of the screen structure variation management information recording unit 161. The repeated structure aggregation tree ID is written, and the structure aggregation tree is written in the screen structure tree recording unit 162.

  FIG. 27 is an example of a screen structure variation management table in which structure aggregation tree ID writing is written.

  Next, the screen variation analysis program 123 calculates the approximate structure feature value for each of the obtained structure aggregation trees. The approximate structure feature value is a value that can uniquely identify the structure, which is calculated from the tag node information and its position, the fixed character string node information and its position, and the variable character string node position included in the structure aggregation tree. In calculating the approximate structural feature value, calculation is performed without including a flag indicating repetition. This is because the same information is aggregated. For example, even a table having only one record in a variable-length table is handled and aggregated in the same manner as a table having a plurality of records. A specific method for calculating the approximate structure feature value is the same as the above-described approximate screen feature value and subtree feature value, and is therefore omitted.

  FIG. 28 is an example of the screen structure variation management table in which the value of the approximate structure feature value is written.

  Next, the screen variation analysis program 123 generates a repetitive structure aggregation tree having the same structure aggregation feature value based on the approximate structure feature value 1618 of the screen structure variation management table 1610c written in the screen structure variation management information recording unit 161. Is obtained from the screen structure tree recording unit 162 using the repeated structure aggregation tree ID 1617 as a key. The screen variation analysis program 123 searches the acquired repeated structure aggregation tree group for the tag node to which the repetition flag is assigned, and in the obtained repetition structure aggregation tree group, at least one tag node to which the repetition flag is assigned. Construct a tree with repeated flags added for. This is called a screen variation tree.

  For example, the repeated structure aggregation tree 7000 (structure aggregation tree ID: SMTR_100_0002) in FIG. 24 and the repeated structure aggregation tree 7200 (structure aggregation tree ID: SMTR_100_0003) in FIG. 26 have the same structure aggregation feature value “VWXYZ123”. In these trees, tag nodes whose repetition flags are turned on are extracted. Then, the repetition flag is turned on for the tag node 7031 of the structure aggregation tree 7000. In the structure aggregation tree 7200, the repetition flag of the tag node 7231 at the same position on the structure is off, but it is a condition that at least one tag node with the repetition flag on is present in the structure aggregation tree group. Then, a screen variation tree is constructed with the repetition flag at that position turned on.

  FIG. 29 is an example of a result obtained by similarly analyzing other tag nodes. FIG. 30 is an example of a result obtained by analyzing a repeated structure aggregation tree having the structure aggregation feature value “ABCDEF” in the same manner.

  The screen variation analysis program 123 assigns a screen variation ID that can be uniquely accessed to the screen variation tree obtained in this way, and writes the assigned screen variation ID to the screen variation ID 1619 of the table in the screen structure variation management information recording unit 161. The screen variation tree is written in the screen structure tree recording unit 162.

  FIG. 31 is an example of a screen variation management table in which the screen variation ID 1619 of the table is written.

  The operation of the screen variation analysis program 123 has been described above. The screen variation analysis program 123 reveals variations of each screen type from the screen log, so that the user can comprehensively understand the branch of the screen in the existing screen specifications.

  Returning to FIG. 11, the screen variable extraction program 124 is analyzed by the screen structure extraction program 121, the screen variable part analysis program 122, and the screen variation analysis program 123, and is stored in the screen structure variation management information recording unit 161 and the screen structure tree recording unit 162. Based on the stored screen display tree and screen variation tree, variable information included in each screen display code is extracted. If these variable information is taken as an example in FIG. 2, the previous screen input data 310 or the data 311 from the database is used as an input source and is embedded in each screen A display code by the screen A primitive program 301.

  More specifically, the screen variable extraction program 124 sets the screen display tree ID 1614 and the screen variation ID 1619 for each record in the screen structure variation management table 1610d (see FIG. 31) stored in the screen structure variation management information recording unit 161. Based on this, a screen display tree and a screen variation tree are acquired from the screen structure tree recording unit 162. The screen variable extraction program 124 matches the fixed character string node and variable character string node information of the screen variation tree with the character string node of the screen display tree based on the tree structure of both, thereby obtaining the variable character string node portion. The specific character string included in is acquired from the lexical node of the screen display tree.

  Hereinafter, the record 1621 of the screen structure variation management table 1610d in FIG. 31 will be described as an example. Based on the screen display code ID 1613 “CRO — 1001” and the screen variation ID 1619 “VARTR — 100 — 001” of the record 1621, the screen variation analysis program 123 sets the screen display tree 3200 (FIG. 12) and the screen variation tree 8100 from the screen structure tree recording unit 162, respectively. get. Then, variable extraction processing is performed using the fixed character string node and variable character string node information of the screen variation tree corresponding to the character string node of the screen display tree. For example, the element of the screen variation tree corresponding to the character string node 3220 of the screen display tree 3200 is a fixed character string node 8111. Therefore, the variable extraction process can be omitted. Elements of the screen variation tree corresponding to the character string node 3221 of the screen display tree 3200 are a fixed character string node 8112 and a variable character string node 8113. Since variable string node is included, variable processing is performed. The character string of the character string node 3221 is “Name: Hitachi Taro”, and the character string of the fixed character string node 8112 is “Name:”. Accordingly, “Hitachi Taro” from which this is removed is a variable value included in the variable character string node at the position in the screen display tree 3200.

  Also, as described above, even with the same screen type, screen variations have occurred, so variables cannot be grouped simply in the order they appear. The screen variation analysis program 123 determines that the variable character string nodes belonging to the subtrees having the same value are the same based on the subtree feature values assigned to the screen variation tree, and the extracted variables are displayed on the screen. After grouping by type, it is written in the screen variable recording unit 163.

  FIG. 32 is an example of screen variable attachment information extracted by the screen variable extraction program 124 and written in the screen variable recording unit 163. The table 1620 includes at least a screen ID 1621, a screen display ID 1622, and variable storage units corresponding to the number of types of variables that appear on the screen.

  The above is the processing of the screen variable extraction program 124. The screen variable extraction can be extracted by the processing of the screen variable extraction program 124 and the screen structure extraction program 121, the screen variable part analysis program 122, and the screen variation analysis program 123 that have been described so far. This makes it easier to statistically analyze variables than the data that is generated, and facilitates understanding and efficiency of existing system specifications.

  Returning to FIG. 1, the screen variation factor analysis program 130 extracts the screen transition information stored in the existing system screen log recording section 150 by the existing screen log storage program 110 and the screen variation information recording section 160 extracted by the screen variation difference extraction program 120. The variable for determining the screen variation and its variable value are calculated by mutual dependency analysis based on the screen variation information stored in the screen and the screen variable information.

  The screen variation factor analysis program 130 advances the analysis for each screen type ID 1611 indicating the screen type of the screen variation information recording unit. The screen display code ID 1613 and the screen variation ID are acquired for each record in the screen variation information recording unit. Next, the screen variable recording unit 163 is searched based on the screen display code ID 1613, and a screen variable group corresponding to the screen display code ID is acquired. Next, a value is acquired for each screen variable of the screen variable group, and a record consisting of the screen display code ID, the value of the screen variable, and the screen variation ID acquired earlier, that is, the relation information between the variations and variables is configured. And written in the screen variation factor analysis result recording unit 170. Further, the screen transition information recording unit 152 is searched based on the acquired screen display code ID, and a screen display code ID (previous screen display code ID) that is the previous screen of the display code ID is acquired. Based on the obtained previous screen display code ID, the screen variable recording unit 163 is searched to acquire a screen variable group corresponding to the screen display code ID. Thereafter, in the same manner as described above, the variation-variable relation information is constructed from the display screen code ID (not the previous screen display code), the value of the screen variable, and the screen variation ID, and is recorded in the screen variation factor analysis result recording unit 170.

  FIG. 33 is an example of variation-variable related information. A table 1710 shows the relationship between the variable value of the variable var1 1712 and the screen variation ID 1713 for each screen display code ID 1711 of the screen type ID “SC100”. Similarly, the table 1720 shows the relationship between the variable value of the variable var2 1722 and the screen variation ID 1723 for each screen display code ID 1721 of the screen type ID “SC100”. Table 1730 shows the relationship between the variable value of variable var3 1732 and the screen variation ID 1733 for each screen display code ID 1731 of the screen type ID “SC100”.

  Next, the screen variation factor analysis program 130 performs a causal relationship analysis and a frequency analysis on the obtained variation-variable relation information. The causal relationship analysis is to analyze and aggregate the variation-variable relation information and total the possible screen variations for the value of the variable. Frequency analysis is the calculation of the rate of occurrence of each variable value in the screen type.

  FIG. 34 is an example of the results of causal relationship analysis and frequency analysis of variation-variable related information. This is an example of variation-variable related information. Table 1740 shows the analysis result of Table 1710, and shows the frequency 1742 for each variable value of the variable var1 1741 and the screen variation ID 1743 that each variable value can take. Table 1750 shows the analysis result of Table 1720, and shows the frequency 1752 for each variable value of the variable var2 1751 and the screen variation ID 1753 that each variable value can take. Table 1760 shows the analysis result of Table 1730, and shows the frequency 1762 for each variable value of the variable var1 1761 and the screen variation ID 1763 that each variable value can take.

  Next, the screen variation factor analysis program 130 analyzes factors that cause screen variations based on the results of the causal relationship analysis and frequency analysis of the variation-variable relation information. First, the screen variation factor analysis program 130 analyzes possible screen variation IDs for each variable value. If there is at least one record with a plurality of possible screen variations for one variable value, that screen variable is excluded from the cause of the screen variation. This is because the variation is not determined by only one value. Next, the screen variation factor analysis program 130 analyzes the frequency of each variable value. If there is no variable value whose frequency exceeds a certain threshold value, the screen variable is excluded from the cause of the screen variation. This is because a variable value can take only one variation if the appearance frequency is as close to 0 as possible. In this embodiment, assuming that a sufficient screen display code is obtained, the following description will be made with 1% as a threshold value. The appropriate value varies depending on the total number of screen display codes obtained, the number of screen variation IDs, and the type of variable value. Therefore, it is not necessarily limited to this value.

  Returning to FIG. 34, in the example shown in Table 1750, since there are two possible screen variation IDs 1753 for one variable value, for example, “Chiyoda-ku, Tokyo”, the screen variation factor analysis program 130 generates screen variations. Judged not to be a factor. In the example shown in Table 1749, there is one screen variation ID 1743 that can be taken for each variable value. However, since the frequency of the variable value is less than 1%, the screen variation factor analysis program 130 does not generate a screen variation. Judged not to be a factor. In the example shown in Table 1760, since all the conditions are cleared, the screen variation factor analysis program 130 determines that this is the cause of the screen variation.

  The screen variation factor analysis program 130 writes the result obtained above in the screen variation factor analysis result recording unit 170.

  FIG. 35 is an example of a screen variation analysis result table of the screen variation factor analysis result recording unit 170. The screen variation analysis result table 1700 has a screen type ID 1701, a variable affiliation screen type ID 1702, a factor variable candidate 1703, a variable value 1704, and a possible screen variation ID 1705.

  The above is the processing of the screen variation factor analysis program 130. By the processing of the screen variation factor analysis program 130, variables that cause screen variations and the specific values of the variables are automatically clarified, so that it is possible to improve the efficiency of grasping the logic specifications of the existing system.

  Returning to FIG. 2, the extracted screen specification output program 140 presents screen variation information to the user through the output device 107 based on the screen variation information recording unit 160 and the screen variation factor analysis result recording unit 170. Hereinafter, the presentation of the results will be described as the operation of the extraction screen specification output program 140.

  The screen variation information recording unit 160 presents, as a list, screen types having screen variations for the screen types of the system to be analyzed to the existing system screen specification extraction device 100 in response to a request from the user. This presentation is based on the information in the table of the screen structure variation management information recording unit 161.

  FIG. 36 is an example of display of a screen variation analysis result list presented by the extraction screen specification output program 140. A screen 9000 is an example of presenting a list of screen variations to the user. This screen has at least a screen type name 9002 and a screen variation number 9003. Further, a serial number 9001 for a screen type having a screen variation and a detailed link 9004 for displaying the screen variation for each screen type are provided. The information shown in the record 9005 is based on a specific example that has been analyzed so far in this embodiment. For example, the screen structure variation table 1610d (FIG. 31) stored in the screen structure variation management information recording unit 161. For the screen type ID 1611 “SC100”, the screen type name 1612 “repayment plan confirmation screen” is displayed in the screen type name 9002, and the value “2” obtained by totaling the possible values of the screen variation ID 1619 is displayed in the screen variation number 9003 Yes.

  In addition, the screen variation information recording unit 160 shows details of screen variations for a screen type of a system to be analyzed to the existing system screen specification extraction device 100 in response to a request from the user. This presentation is based on information stored in the screen variation information recording unit 160. Further, the information in the screen display code recording unit 151 is also referred to in some cases.

  FIG. 37 is an example of display of detailed screen variation information presented by the extracted screen specification output program 140. A screen 9100 is an example of presenting screen variations of a certain screen type to the user, and is a display example based on the screen type ID “SC100” used in the description of the present embodiment. For the screen variation of the screen type ID “SC100”, for example, the screen 9100 randomly selects one screen display code ID 1613 having a screen variation ID 1619 to be displayed as a pattern from the screen variation management table 1610d, and the selected screen display code ID Based on the above, a specific screen display code is acquired from the screen display code recording unit 151. The acquired screen display code is rendered in the same way as it is actually displayed, and shown to the user as a screen display sample.

  FIG. 38 is a second display example of the screen variation detailed information presented by the extracted screen specification output program 140. The screen 9110 is a form in which the screen display code, which is a sample of each screen variation acquired by the same method as that in FIG. 37, is directly displayed to the user as a character string.

  FIG. 39 is a third display example of screen variation detailed information presented by the extracted screen specification output program 140. The screen 9100 reads the screen variation tree corresponding to the screen variation ID 1619 displayed as a pattern from the screen variation management table 1610d, for example, for the screen variation of the screen type ID “SC100” from the screen structure tree recording unit 162 so that the tree shape can be understood. This is the form shown to the user.

  Further, the extracted screen specification output program 140 indicates variables that cause screen variations and candidates for the variable values for a screen type of an analysis target system of the existing system screen specification extracting device 100 in response to a request from the user. . This presentation is based on information stored in the screen structure variation management information recording unit 161 and the screen variable recording unit 163.

  FIG. 40 is a display example of factor information of screen variations presented by the extracted screen specification output program 140. A screen 9200 is an example showing a factor variable of a screen variation of a certain screen type for the user, and is a display example based on the screen type ID “SC100” used in the description of the present embodiment. The screen 9200 includes at least a screen that is a factor of screen variation and variable information 9201 in the screen, an example of the screen variable value, and a screen variation pattern that is displayed in the case of the variable value. An example of the screen variable value and a display example of the screen variation pattern displayed at the time of the variable value are denoted by reference numerals 9202 and 9203. In addition to these pieces of information, a screen variation sample that recalls a specific screen display example may be displayed. Examples are indicated by reference numerals 9203 and 9204.

  A processing procedure when the existing system screen specification extraction device 100 having the configuration described above performs processing will be described.

  FIG. 41 is a flowchart showing the entire procedure for extracting the existing system screen specifications using the apparatus 100.

In step S100, the existing screen log storage program 110 stores the screen log information input by the user of the apparatus 100, that is, the screen display code information and the screen transition information in the existing system screen log recording unit 150. (Step S100)
In step S200, the screen variation difference extraction program 120 reads the screen log information stored in the existing system screen log recording unit 150, extracts screen variation information and screen variable information from the screen log information, and stores them in the screen variation information recording unit 160. Write. Detailed processing will be described later.

  In step S300, the screen variation factor analysis program 130 reads the screen transition information written in the existing system screen log recording unit 150 and the screen structure variation information and the screen variable information written in the screen variation information recording unit 160, and displays the screen variation information. The screen variable that is a factor and its value are analyzed, and the obtained screen variation factor analysis result is written in the screen variation factor analysis result recording unit 170. Detailed processing will be described later.

  In step S400, the extracted screen specification output program 140 extracts the existing system extracted based on the screen variation information written in the screen variation information recording unit 160 and the screen variation factor analysis result written in the screen variation factor analysis result recording unit 170. The screen specifications are presented to the user of the apparatus 100. Detailed processing will be described later.

  Next, the process of step S200 is demonstrated based on the flowchart of FIG.

  FIG. 42 is a flowchart illustrating a processing procedure for extracting screen variations.

  In step S210, the screen structure extraction program 121 sequentially acquires screen display codes from the screen display code recording unit 151, and extracts the structure of each screen display code.

The process of step S210 will be described in detail with reference to FIG.
FIG. 43 is a flowchart showing a detailed procedure of processing of the screen structure extraction program 121.

  First, the screen structure extraction program 121 reads a grammar describing a screen of a system to be analyzed from the screen description grammar recording unit 180 and prepares for subsequent processing (step S2101).

  The screen structure extraction program 121 searches the screen display code recording unit 151 and determines whether there is an unprocessed screen display code (step S2102). If there is an unprocessed screen display code, step S2103 is executed, and if there is no unprocessed screen display code, the process ends. Hereinafter, a case where an unprocessed screen display code exists will be described.

  The screen structure extraction program 121 reads one unprocessed screen display code from the screen display code recording unit 151 (step S2103).

  The screen structure extraction program 121 constructs a screen display tree for the read screen display code based on the grammar describing the screen acquired in step S2101 (step S2104).

  The screen structure extraction program 121 calculates an approximate screen feature value that uniquely identifies each structure of the constructed screen display tree by the above-described method (step S2105).

  The screen structure extraction program 121 writes the constructed screen display tree in the screen structure tree recording unit 162, and writes the ID for accessing the screen display tree and the calculated approximate screen feature value of the screen display tree in the screen structure variation management information recording unit 161. (Step S2106). After this writing process is completed, the screen structure extraction program 121 moves the process to step S2102.

  Returning to FIG. 42, in step S220, the screen variable part analysis program 122 reads the screen display tree from the screen variation information recording part 160, analyzes the variable part on the screen of each screen display tree, and executes the screen variation information recording part. 160 is written.

The process of step S220 will be described in detail with reference to FIG.
FIG. 44 is a flowchart showing a detailed procedure of processing of the screen variable part analysis program 122.

  First, the screen variable part analysis program 122 acquires the general screen feature value group calculated in step S2105 from the screen variation information recording unit 160, and groups screen display trees having the same general screen feature value (step S2201). .

  The screen variable part analysis program 122 determines whether or not there is an unprocessed group for the equivalence group of the grouped schematic screen feature values (step S2202). If there is an unprocessed equivalence group, the process proceeds to step S2203. If there is no unprocessed equivalence group, the process ends. Hereinafter, a case where an unprocessed equivalence group exists will be described.

  The screen variable part analysis program 122 selects one unprocessed general screen feature value, and acquires a screen display tree group having the general screen feature value from the screen structure tree recording unit 162 of the screen variation information recording unit 160 ( Step S2203).

  The screen variable part analysis program 122 searches each obtained screen display tree group, acquires a character string existing at the end position of the tree, that is, a character string node, and sets each character string node at the same position on the tree structure. Aggregate (step S2204).

  The screen variable part analysis program 122 determines whether or not there is an unprocessed character string node group for each aggregated character string node group (step S2205). If there is an unprocessed character string node group, the process proceeds to step S2206; otherwise, the process proceeds to step S2208. Hereinafter, first, a case where there is an unprocessed character string node group will be described.

  The screen variable part analysis program 122 selects one unprocessed character string node group, takes a difference between each character string included in the character string node group, and is a partial character string that is common to all character strings, that is, a fixed character string. And a partial character string that changes between character strings, that is, a variable character string portion is analyzed (step S2206).

  The screen variable part analysis program 122 replaces each character string node of the screen display tree with a fixed character string node representing the fixed character string part obtained in step S2207 and a variable character string node representing the variable character string part. A structure tree is constructed (step S2207).

  In step S2205, after determining that there is no unprocessed character string node group, that is, all the character string nodes have been processed, the screen variable part analysis program 122 stores the obtained screen structure tree in the screen variation information recording part 160. Information necessary for accessing the screen structure tree is written into the screen structure variation management information recording unit 161 in the screen structure tree recording unit 162 (step S2208). After writing, the process proceeds to step S2202.

  Returning to FIG. 42, in step S230, the screen variation analysis program 123 reads the screen structure tree from the screen variation information recording unit 160, analyzes this, extracts screen variation information for each screen type, and extracts the screen variation information recording unit. 160 is written.

The process of step S230 will be described in detail with reference to FIG.
FIG. 45 is a flowchart showing a detailed procedure of processing of the screen variation analysis program 123.

  First, the screen variation analysis program 123 searches the screen structure tree recording unit 162 to determine whether there is an unprocessed screen structure tree (step S2301). If there is an unprocessed screen structure tree, the process proceeds to step S2302, and if not, the process proceeds to step S2308. Hereinafter, the case where an unprocessed screen structure tree exists will be described first.

  The screen variation analysis program 123 selects and acquires one unprocessed screen structure tree from the screen structure tree recording unit 162 (step S2302).

  Next, the screen variation analysis program 123 calculates, for each subtree of the acquired screen structure tree, a subtree structure feature value that makes the structure of each subtree unique, and assigns it to the vertex node of the subtree (step) S2303).

  The screen variation analysis program 123 identifies a repetitive structure portion of the screen structure tree by finding a portion where the subtree structure feature value having the same value repeats based on the calculated subtree structure feature value (step S2304).

  The screen variation analysis program 123 constructs a structure aggregation tree in which the identified repetitive structure portions are aggregated as one subtree having a repetition attribute (step S2305).

  Thereafter, the screen variation analysis program 123 calculates, for the obtained structure aggregation tree, an approximate structure feature value that uniquely identifies the tree structure excluding the repetitive attribute, and assigns it to the obtained structure tree (step S2306).

  The screen variation analysis program 123 stores the obtained structure aggregation tree in the screen structure tree recording unit 162 of the screen variation information recording unit 160, and the access ID and the approximate structure feature value for the structure aggregation tree in the screen variation information recording unit 160, respectively. Writing is performed (step S2307).

  After determining in step S2301 that there is no unprocessed screen structure tree, that is, all necessary screen structure trees have been processed, the screen variation analysis program 123 uses the structure outline feature value as a search key as the screen variation information. The structure leading role tree of the recording unit 160 is searched, and the structure aggregation tree having the same value is newly integrated as a screen variation tree (step S2308).

  The screen variation analysis program 123 writes the obtained screen variation tree group to the screen structure tree recording unit 162 of the screen variation information recording unit 160 and the access ID to the screen variation tree to the screen structure variation management information recording unit 161 ( Step S2309).

Returning to FIG. 42, in step S240, the screen variable extraction program 124 uses the screen display tree and the screen variation tree stored in the screen variation information recording unit 160 to change the on-screen variable displayed in the screen code for each screen type. This is a process of extracting and writing to the screen variable recording unit 163.
The process of step S240 will be described in detail with reference to FIG.

  FIG. 46 is a flowchart showing a detailed procedure of processing of the screen variable extraction program 124.

  First, the screen variable extraction program 124 searches the screen structure variation management information recording unit 161 of the screen variation information recording unit 160 and determines whether or not there is an unprocessed screen type (step S2401). If there is an unprocessed screen type, the process proceeds to step S2402, and if not, the process ends. Hereinafter, a case where an unprocessed screen type exists will be described.

  The screen variable extraction program 124 selects and acquires one unprocessed screen type (step S2402).

  The screen variable extraction program 124 searches the screen structure variation management information recording unit 161 using the acquired screen type ID as a key, and determines whether or not an unprocessed screen variation tree exists for the screen type (step S2403). ). If there is an unprocessed screen variation tree, the process proceeds to step S2404, and if not, the process proceeds to step S2407. Hereinafter, first, a case where an unprocessed screen variation tree exists will be described.

  The screen variable extraction program 124 selects one unprocessed screen variation tree and acquires it from the screen structure tree recording unit 162 (step S2404).

  The screen variable extraction program 124 searches and acquires a screen display tree related to the acquired screen variation tree from the screen structure variation management information recording unit 161 using the screen variation tree ID as a key (step S2405).

  The screen variable extraction program 124, based on the information of each fixed character string node and variable character string node existing at the end of the acquired screen variation tree, the character string node existing at the same position of each screen display tree acquired in step S2405. The variable character string is extracted from, and the value is collected for each variable character string node to be extracted (step S2406). Thereafter, the process proceeds to step S2403.

  If it is determined in step S2403 that an unprocessed screen variation tree does not exist, that is, the variable extraction processing for all necessary screen variation trees is completed, the screen variable extraction program 124 uses the screen variation tree belonging to the screen type, A variable character string node indicating the same information is identified based on the subtree feature value, and the variable character strings of the screen variations identified based on the result are integrated into one (step S2407).

  The screen variable extraction program 124 writes the variable character string information group extracted by the above processing in the screen variable recording unit 163 as a screen type variable group (step S2408). After writing, the process proceeds to step S2401.

  Returning to FIG. 41, the process of step S300 will be described in detail based on the flowchart of FIG.

  FIG. 47 is a flowchart showing a detailed procedure of processing of the screen variation factor analysis program 130.

  First, the screen variation factor analysis program 130 searches the screen structure variation management information recording unit 161 of the screen variation information recording unit 160 to determine whether or not an unprocessed screen type exists (step S310). If there is an unprocessed screen type, the process proceeds to step S320, and if not, the process ends. Hereinafter, a case where there is an unprocessed screen type will be described.

  The screen variation factor analysis program 130 selects one unprocessed screen type, and acquires screen variation information and a screen variable information group associated with the screen type (step S320).

  The screen variation factor analysis program 130 determines whether there is an unprocessed screen variable (step S330). If there is an unprocessed screen variable, the process is copied to step S340, and if not, the process proceeds to S310. In the following, processing when there is an unprocessed screen variable will be described.

  The screen variation factor analysis program 130 selects one unprocessed screen variable, and calculates as a causal relationship each variable value that the variable can take and which screen variation can occur simultaneously (step S340).

  The screen variation factor analysis program 130 analyzes the calculated causal relationship and determines whether there are variable values associated with a plurality of screen variations (step S350). If there is at least one variable value associated with a plurality of screen variations, the screen variable including the variable value is determined not to be a determinant of the screen variation, and the process proceeds to step S330. The process proceeds to step S360 as a candidate for the determinant.

  The screen variation factor analysis program 130 calculates the distribution of the appearance frequency of each variable value in the screen variable (step S360).

  The screen variation factor analysis program 130 analyzes the appearance frequency of each obtained variable value, and determines whether or not there is a variable value having an appearance frequency exceeding a predetermined threshold (step S370). If there is a variable value having an appearance frequency exceeding the predetermined threshold, the process proceeds to step S380 with the screen variable as a screen variation determinant candidate, and if not, the screen variable is not determined as a screen variation determinant. If not, the process proceeds to step S330.

  The screen variation factor analysis program 130 writes the screen variable determined as the candidate for the screen variation determinant as the screen variation factor into the screen variation factor analysis result recording unit 170 (step S380). After writing, the process proceeds to step S330.

  Returning to FIG. 41, the process of step S400 will be described in detail based on the flowchart of FIG.

  FIG. 48 is a flowchart showing a detailed procedure of processing of the extraction screen specification output program 140.

  The extraction screen specification output program 140 receives a request regarding the extraction screen specification output from the user (step S401).

  The extracted screen specification output program 140 determines whether or not the received request is a screen variation list output request (step S402). If the received request is a screen variation list output request, the process proceeds to step S403; otherwise, the process proceeds to step S404.

  Upon receiving the screen variation list output request, the extracted screen specification output program 140 retrieves and acquires screen variation information from the screen variation information recording unit 160, and outputs the result, for example, as shown in the screen variation analysis result list 9000 in FIG. Step S403). After outputting, the process proceeds to step S401.

  The extracted screen specification output program 140 determines whether or not the received request is a screen variation detailed output request (step S404). If the received request is a screen variation detailed output request, the process proceeds to step S405; otherwise, the process proceeds to step S406.

  Upon receiving the screen variation list output request, the extracted screen specification output program 140 searches and acquires screen variation information and screen display code information from the screen variation information recording unit 160. For example, the screen variation display screen 9100 in FIG. The result is output as follows (step S405). After outputting, the process proceeds to step S401.

  The extracted screen specification output program 140 determines whether or not the received request is a screen variation factor output request (step S406). If the received request is a screen variation factor output request, the process proceeds to step S407; otherwise, the process proceeds to step S408.

  Upon receiving the screen variation list output request, the extracted screen specification output program 140 receives screen variation information and screen display code information from the screen variation information recording unit 160, and screen variation factor analysis result information from the screen variation factor analysis result recording unit 170. Is retrieved and output, for example, as in the screen variation display screen 9200 of FIG. 40 (step S407). After outputting, the process proceeds to step S401.

  The extraction screen specification output program 140 determines whether or not the received request is a processing end request (step S408). If the received request is a request requiring termination, the process is terminated; otherwise, the process proceeds to step S401.

  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 these embodiments. For example, the above-described embodiments have been described in detail in order to easily understand the present description, and are not necessarily limited to those having all the configurations described.

  Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them, for example, with an integrated circuit. Further, each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files that realize the following functions can be stored in a memory, a storage device such as a hard disk or an SSD (Solid State Drive), or a storage medium such as an IC card, an SD card, or a DVD.

  In addition, the control lines and information lines are those that are considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

  In the existing system screen specification extraction device 100 of the above-described embodiment, the user of the device 100 uses each variable character string as a result of the screen variable portion analysis program 122 of the screen variation difference extraction program 120 analyzing the variable portion on the screen. In some cases, you may want to make corrections such as combining, disassembling, and expanding the range of variable character strings. Therefore, in addition to the configuration of the embodiment, a screen variable that presents the processing result of the screen variable part analysis program 122 to the user of the apparatus 100 using an image display code or the like as a sample and inputs a variable character string desired by the user. It is good also as a structure which has the part correction program 125. FIG.

100 Existing system screen specification extraction device 101 CPU
102 Memory 103 External Storage Device 104 Bus 105 External Interface 106 Input Device 107 Output Device 108 Communication Device 110 Existing Screen Log Storage Program 120 Screen Variation Difference Extraction Program 121 Screen Structure Extraction Program 122 Screen Variable Part Analysis Program 123 Screen Variation Analysis Program 124 Screen Variable extraction program 130 Screen variation factor analysis program 140 Extraction screen specification output program 150 Existing system screen log recording unit 151 Screen display code recording unit 152 Screen transition information recording unit 160 Screen variation information recording unit 161 Screen structure variation management information recording unit 162 Screen Structure tree recording unit 163 Screen variable recording unit 170 Screen variation factor analysis result recording unit 180 Screen description grammar recording unit

Claims (10)

An existing system screen specification extraction device that extracts the screen program specification of the existing system from the screen log of the existing system,
About the screen log, a plurality of screen logs of related screens are collected and collected, and for the collected plurality of screen logs, a difference extraction unit that compares each related information and extracts difference information about the difference, and
Analyzing the difference information, an analysis unit for separating a common area and a variable area in the screen of the screen log,
An existing system screen specification extraction device comprising: a screen specification output unit that specifies and outputs information relating to a variable area as a result of analysis as a screen specification of the screen. An existing system screen specification extraction device according to claim 1,
The difference extraction unit is configured to change a screen structure variation of a screen program that generates a screen indicated by the screen log from the plurality of screen logs by a comparison process between the screen logs constituting the input screen logs. Extract and
The screen specification output unit outputs a screen specification including at least one of a list of screen types in which screen structure variations exist and details of each screen variation based on the screen structure variations. System screen specification extraction device. The existing system screen extraction device according to claim 1,
The difference extraction unit extracts screen variable information by calculating a difference between screen description codes common to the plurality of screen logs,
The existing system screen specification extracting device, wherein the screen specification output unit outputs the screen variable information. An existing system screen specification extraction device according to claim 3,
The analysis unit analyzes a recorded screen variation or variable information causal relationship, analyzes a variable that is a factor that determines display of each screen variation and its variable value, and calculates a screen variation factor analysis result,
The screen specification output unit outputs the screen variation factor analysis result as a screen specification of the existing system. An existing system screen specification extraction device according to any one of claims 3 and 4,
The screen specification output unit outputs a variable area on the screen from the analysis result of the difference extraction unit,
An existing system screen specification extraction device, further comprising a screen variable part information correction unit that receives correction information including combination and decomposition of variable areas and expansion of a range and identifies the received correction information as a variable area. An existing system screen specification extraction method for extracting the screen program specification of the existing system from the screen log of the existing system,
Regarding the screen log, a plurality of screen logs of related screens are collected and collected, and for the collected plurality of screen logs, a difference extraction step of comparing each related information and extracting difference information about the difference, and
Analyzing the difference information, and analyzing the common area and the variable area in the screen of the screen log;
An existing system screen specification extraction method, comprising: a screen specification output step for specifying and outputting information relating to a variable area as a result of analysis as a screen specification of the screen. An existing system screen specification extraction method according to claim 6,
In the difference extraction step, a variation of the screen structure of the screen program that generates the screen indicated by the screen log from the plurality of screen logs is compared by a comparison process between the screen logs constituting the input screen logs. Extract and
The screen specification output step outputs a screen specification including at least one of a list of screen types in which screen structure variations exist and details of each screen variation based on the screen structure variations. System screen specification extraction method. An existing system screen extraction method according to claim 6,
The difference extraction step extracts screen variable information by calculating a difference between screen description codes common to the plurality of screen logs,
The said screen specification output step outputs the said screen variable information, The existing system screen specification extraction method characterized by the above-mentioned. An existing system screen specification extraction method according to claim 8,
In the analysis step, by analyzing the recorded screen variation or variable information causal relationship, a variable serving as a factor for determining display of each screen variation and its variable value are analyzed to calculate a screen variation factor analysis result,
In the screen specification output step, the screen variation factor analysis result is output as a screen specification of the existing system. An existing system screen specification extraction method according to any one of claims 8 and 9,
The screen specification output step outputs a variable area on the screen from the analysis result of the difference extraction unit,
An existing system screen specification extraction method, further comprising a screen variable part information correction step for receiving correction information including combination and decomposition of variable areas and expansion of a range, and specifying the received correction information as a variable area.

Images