Intra-system data flow visualization system
The data flow visualization system addresses the challenge of understanding influence scope in inter-system data changes by generating detailed diagrams with impact and propagation information, enhancing system maintenance efficiency.
Patent Information
- Application Number
- JP2023076760
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-08
- Publication Date
- 2024-11-20
AI Technical Summary
Conventional inter-system coordination data visualization devices only display coordination conditions, making it difficult to understand the scope of influence when changes occur in data flowing between multiple computer systems.
A data flow visualization system that acquires input/output relationship information, determines impacts on other systems, generates data flow diagrams, and includes propagation presence/absence information, timing, and person in charge details to visually grasp the range of influence.
Enables easy understanding of the range of influence on each computer system due to data changes, facilitating efficient maintenance and trouble prevention.
Smart Images

Figure 2024161760000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a data flow visualization system for visualizing data flows between a plurality of computer systems. [Background technology]
[0002] Patent Document 1 discloses an inter-system linkage data visualization device that includes an acquisition unit that acquires distributed data including linkage conditions for linking multiple computer systems, an analysis unit that analyzes and determines the contents of the linkage conditions of the distributed data, and a visualization control unit that displays the linkage conditions of the distributed data determined by the analysis on a monitor. With this device, the linkage conditions of the distributed data can be visually confirmed, making it easy to grasp the linkage between computer systems. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2018-164180 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, in the case of the conventional inter-system collaboration data visualization device described above, only the collaboration conditions are displayed, making it difficult to grasp the scope of impact on each computer system, for example, when changes occur to the collaboration conditions.
[0005] The present invention has been made in consideration of these circumstances, and its main objective is to provide an inter-system data flow visualization system that can visually grasp the scope of impact when changes occur to data flowing between multiple computer systems. [Means for solving the problem]
[0006] In order to solve the above problems, one embodiment of the data flow visualization system between systems of the present invention comprises an input / output relationship acquisition unit that acquires input / output relationship information indicating the input / output relationship of files including data between multiple computer systems, a determination unit that, when a change occurs to data in one computer system, determines whether or not there is an impact on other computer systems based on the input / output relationship, a generation unit that generates data flow diagram information for illustrating the data flow between the computer systems including the determination result of whether or not there is an impact, and an output unit that outputs the data flow diagram information.
[0007] In the above aspect, the system may further include a processing content acquisition unit that acquires processing content information indicating the content of information processing using each data in each computer system, and the determination unit may determine whether the data to be changed is used in the information processing based on the processing content information, and determine that there is an impact when it is determined that the data will be used.
[0008] In addition, in the above aspect, the system may further include a propagation presence / absence acquisition unit that acquires propagation presence / absence information indicating whether each data is propagated from an upstream computer system to a downstream computer system, and the determination unit may determine whether the data to be changed will be propagated based on the propagation presence / absence information, and determine that there is an impact when it is determined that the data will be propagated.
[0009] In addition, in the above aspect, if the determination unit determines that the data to be changed will not be propagated, the generation unit may generate the data flow diagram information including non-propagation information indicating that the data will not be propagated.
[0010] In addition, in the above aspect, the input / output relationship information includes timing information indicating the timing at which a file is input from an upstream computer system to a downstream computer system, and the generation unit may generate the data flow diagram information including the input timing.
[0011] In the above aspect, the input / output relationship information may include person in charge information indicating a person in charge of each computer system, and the generation unit may generate the data flow diagram information including the person in charge.
[0012] In addition, in the above aspect, the person in charge information may include person in charge transition information indicating a transition status of the person in charge, and the generation unit may generate the data flow diagram information including the transition status of the person in charge.
[0013] In addition, in the above aspect, a prompting unit may prompt a person in charge of each computer system to confirm whether or not the judgment result needs to be corrected, and when an instruction to correct the judgment result is received from the person in charge, the generation unit may generate the data flow diagram information that reflects the correction. Effect of the Invention
[0014] According to the present invention, it is possible to easily grasp the extent of the effect on each computer system caused by a change in data. [Brief description of the drawings]
[0015] [Figure 1] FIG. 1 is a block diagram showing a configuration of a data flow visualization system. [Diagram 2] FIG. 13 is a diagram showing an example of the layout of an input / output relationship database. [Diagram 3] FIG. 13 is a diagram showing an example of the layout of a file details database. [Figure 4] FIG. 13 is a diagram showing an example of the layout of a processing content database. [Diagram 5] 11 is a flowchart showing an example of a procedure of a first data flow visualization process. [Figure 6] FIG. 13 is a diagram showing an example of a first data flow screen. [Figure 7A] FIG. 13 is a diagram showing an example of a second data flow screen. [Figure 7B] FIG. 13 is a diagram showing an example of a second data flow screen. [Figure 8A]FIG. 13 is a diagram showing an example of a third data flow screen. [Figure 8B] FIG. 13 is a diagram showing an example of a third data flow screen. [Figure 8C] FIG. 13 is a diagram showing an example of a third data flow screen. [Figure 8D] FIG. 13 is a diagram showing an example of a third data flow screen. [Figure 9] 10 is a flowchart showing an example of a procedure of a second data flow visualization process. [Figure 10A] FIG. 13 is a diagram showing an example of a third data flow screen. [Figure 10B] FIG. 13 is a diagram showing an example of a third data flow screen. [Figure 10C] FIG. 13 is a diagram showing an example of a third data flow screen. [Figure 10D] FIG. 13 is a diagram showing an example of a third data flow screen. [Figure 11] FIG. 13 is a diagram showing a modified example of the third data flow screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0016] Preferred embodiments of the present invention will be described below with reference to the drawings. Note that the following embodiments are merely examples of methods and devices for embodying the technical idea of the present invention, and the technical idea of the present invention is not limited to the following. The technical idea of the present invention can be modified in various ways within the technical scope described in the claims.
[0017] The data flow visualization system of this embodiment is capable of visually grasping the extent of the impact when a change occurs in data flowing between multiple computer systems. The data changes in this embodiment include various changes. For example, changes in the format, content, size, or unit of data are included in the data changes. Changes in data also include changes in the size of a file made up of data, the timing at which that file is generated in a computer system, or the timing at which the computer system needs that file.
[0018] (System Configuration) 1 is a block diagram showing the configuration of a data flow visualization system according to this embodiment. The data flow visualization system (hereinafter referred to as the "visualization system") 1 is a computer system that visualizes data flows between multiple computer systems 2. Each computer system 2 is, for example, a business system that performs a predetermined business operation while cooperating by mutually inputting and outputting data. Hereinafter, this computer system will be referred to as a business system.
[0019] The visualization system 1 communicates with a user terminal 3 via a communication network such as a LAN. The user terminal 3 is an information terminal used by a person in charge of managing the business system 2, and examples of such terminals include a personal computer and a tablet terminal. The user terminal 3 acquires information provided by the visualization system 1 using an internet browser or a dedicated application, and displays the information on a display unit.
[0020] The visualization system 1 is configured with a computer equipped with a control unit including a CPU, RAM, and ROM, and each process described below is executed by this control unit. The visualization system 1 also has each of the following databases: an input / output relation database (DB) 11, a file detail database (DB) 12, and a process content database (DB) 13. The following describes these databases in detail.
[0021] (A) Input / Output Relationship DB11 The input / output relationship DB 11 is a database that stores input / output relationship information indicating the input / output relationship of files between a plurality of business systems 2. This input / output relationship information is generated for each business system 2, and various information regarding other business systems 2 that perform input / output with that business system 2 is specified.
[0022] Fig. 2 is a diagram showing an example of the layout of the input / output relationship DB 11. Fig. 2 shows input / output relationship information related to one specific business system 2. As shown in Fig. 2, the input / output relationship DB 11 stores information indicating the type of input / output, the business system 2 that performs input / output with the one business system 2, the department and person in charge of the business system 2, the file to be input / output, and the time when the file is input / output (transmitted / received).
[0023] Regarding the person in charge, in addition to the current person in charge, if there was another person in charge in the past, information indicating the past person in charge is also stored in the input / output relationship DB 11. In that case, information indicating the multiple persons in charge is stored so that the order in which the persons in charge were in charge can be identified. Therefore, by referring to the input / output relationship DB 11, it is possible to understand the transition status of the person in charge.
[0024] Although not shown in Fig. 2, contact information (such as an email address) of each person in charge is also stored in the input / output relationship DB 11. As will be described later, the visualization system 1 provides the contact information to the person in charge via the user terminal 3. The person in charge can use the contact information to contact a person in charge of another business system 2 as necessary.
[0025] (B) File details DB12 The file details DB 12 is a database that stores file detail information relating to the details of files input and output between the business systems 2. Fig. 3 is a diagram showing an example of the layout of the file details DB 12. As shown in Fig. 3, the file details DB 12 stores information indicating the business system 2 that processes the file, the file, and a definition document of the file. Note that with regard to the file definition document, the definition document itself may be stored, or the save destination of the definition document, etc. may be stored.
[0026] The file definition specifies details of the data, such as the names and contents of the data items included in the file, and the definitions of data types and variables, etc. The visualization system 1 can grasp the details of the file and the data included in the file by referring to the definition.
[0027] (C) Processing content DB13 The processing content DB 13 is a database that stores processing content information related to the contents of information processing executed using various data in each business system 2. Fig. 4 is a diagram showing an example of the layout of the processing content DB 13. As shown in Fig. 4, the processing content DB 13 stores information indicating the business system 2 that executes the information processing, a computer program that realizes the information processing, and a design document for the computer program.
[0028] The design specifications of the computer program specify the details of the processing to be performed on each piece of data. The design specifications also specify whether or not all or part of each piece of data is to be propagated to the downstream business system 2. As will be described later, the visualization system 1 determines whether or not all or part of each piece of data is to be processed and whether or not it is to be propagated on a downstream basis based on the contents of the design specifications, and determines whether or not there is an impact on the downstream business system 2 based on the result.
[0029] The information stored in the above-mentioned input / output relationship DB 11, file details DB 12, and processing content DB 13 is manually input to the visualization system 1. However, the visualization system 1 may automatically acquire all or part of the information from various definition documents, design documents, etc. of each business system 2. The information stored in each database is updated as appropriate to keep it up to date.
[0030] In addition to the above-mentioned information, the visualization system 1 stores various information in a storage unit, such as an overview of each business system 2 and a planned release date of a newly released business system 2. Each process described later is executed using the information.
[0031] (System Operation) A person in charge of a business system 2 accesses the visualization system 1 using a user terminal 3 to request visualization of the data flow in order to check the data flow between each business system 2, such as when revising a computer program implemented in that business system 2, when resolving a trouble that has occurred, or when linking a business system 2 with another business system 2 for the first time. In response to the request, the visualization system 1 realizes visualization of the data flow.
[0032] 5 is a flowchart showing an example of the procedure of the first data flow visualization process executed by the visualization system 1 and the user terminal 3. First, the user terminal 3 transmits a visualization request for the data flow between the business systems 2 to the visualization system 1 according to an instruction from the person in charge of the business systems 2 (S101). This visualization request includes information for identifying the business system 2 that the person in charge is in charge of. Therefore, the visualization system 1 can know which business system 2 the person in charge of has made this visualization request. Here, the explanation will be continued assuming that the person in charge is in charge of the XXX system.
[0033] When the visualization system 1 receives a visualization request from the user terminal 3 (S201), it acquires input / output relationship information from the input / output relationship DB 11 (S202). Next, the visualization system 1 acquires file detail information on the file included in the input / output relationship information from the file detail DB 12 (S203), and further acquires processing content information that specifies the processing content for the file from the processing content DB 13 (S204).
[0034] Next, the visualization system 1 uses the input / output relationship information, the file detail information, and the processing content information acquired as described above to generate data flow diagram information for illustrating the data flow between the business systems 2 (S205). This data flow diagram information corresponds to information displayed on the first to third data flow screens described later. Therefore, the details thereof will be described later with reference to each screen.
[0035] The visualization system 1 transmits the generated data flow diagram information to the user terminal 3 (S206). To explain in more detail, the visualization system 1 first transmits data flow diagram information for displaying the first data flow screen, and thereafter transmits data flow diagram information for displaying the second and third data flow screens in response to requests from the user terminal 3.
[0036] When the user terminal 3 receives the data flow diagram information from the visualization system 1 (S102), it uses the data flow diagram information to display a data flow screen on the display unit (S103). The details of this data flow screen will be described below.
[0037] As described above, in this embodiment, three types of data flow screens, the first to third data flow screens, are displayed on the display unit of the user terminal 3. The first data flow screen is displayed first, an example of which is shown in FIG. 6. As shown in FIG. 6, the first data flow screen is a screen showing the input / output relationships of files between multiple business systems 2 with arrows. These input / output relationships have been generated by the visualization system 1 based on the input / output relationship information. For each business system 2, the name of the system, the name of the department in charge, and an overview of the system are displayed, and the flow of files between business systems 2 where files are input or output is shown with arrows.
[0038] On the first data flow screen, the business system 2 that the person in charge of who requested the data flow visualization is in charge of is positioned in the center ("XXX system" in the example shown in Fig. 6). Also, to make it easy to understand that this business system 2 is the person in charge of that system, it is surrounded by a thicker frame than the other business systems 2.
[0039] Furthermore, the newly released business system 2 is displayed in a manner that makes it easy to understand that fact. In the example shown in Fig. 6, the newly released "EEE system" is surrounded by a dashed frame. Furthermore, the planned date of the release is also displayed.
[0040] The display of the system name of each business system 2 is a link, and when this link is pressed, data flow diagram information for displaying the second data flow screen related to the pressed business system 2 is transmitted from the visualization system 1 to the user terminal 3. The following explanation will be given taking the second data flow screen related to "XXX system" as an example.
[0041] The user terminal 3 displays a second data flow screen on the display unit by using the data flow illustrated information received from the visualization system 1. Figures 7A and 7B are diagrams showing an example of the second data flow screen. As shown in Figure 7A, the second data flow screen displays two pieces of file information: input file information on a file input from another business system 2 to the XXX system, and output file information on a file output from the XXX system to the other business system 2.
[0042] The input file information includes the name of the business system 2 from which the input originates, the department in charge, the person in charge, the name of the file being input, and the time when the file is input (received time). Similarly, the output file information includes the name of the business system 2 to which the output is directed, the department in charge, the current person in charge, the name of the file being output, and the time when the file is output (sent time). Each of these pieces of information is stored in the input / output relationship DB 11.
[0043] The column showing the current person in charge has a letter icon attached to it. This icon is linked to the email address of that person, and when this icon is pressed, the mailer installed in the user terminal 3 starts up and an email addressed to that email address is automatically created. This allows the person in charge of the XXX system to easily contact the person in charge of the other business system 2 to whom they wish to make an inquiry.
[0044] When the person in charge of the XXX system wishes to contact a past person in charge of another business system 2, rather than the current person in charge, the person in charge presses the "Click here for person in charge transitions" display in the person in charge display column on the second data flow screen. When this display is pressed, the transition status of the person in charge is displayed in a pop-up as shown in FIG. 7B. This allows the person in charge of the XXX system to know the person in charge they wish to contact. Note that the display of the person in this pop-up display screen is linked to the email address of that person, and when this display section is pressed, an email is automatically created in the same way as in the above case, making it possible to easily contact the person in question.
[0045] For both the input file and the output file, the file name is displayed as a link, and when the link is pressed, data flow diagram information for displaying a third data flow screen showing the relationship between the files including the pressed file is transmitted from the visualization system 1 to the user terminal 3. The following describes an example of the third data flow screen when "A-1 file" in Figures 7A and 7B is pressed.
[0046] The user terminal 3 displays a third data flow screen on the display unit using the data flow illustrated information received from the visualization system 1. Fig. 8A to Fig. 8D are diagrams showing an example of the third data flow screen. As shown in Fig. 8A, the third data flow screen displays information on each input file including the A-1 file input to the XXX system, information on the generated file finally generated by the XXX system that received the input file, and information on the intermediate layer that is processed in the intermediate processing executed in the XXX system before the generated file is generated. In the following, the intermediate layer may also be referred to as a file.
[0047] For each input file, intermediate layer, and generated file, the name of the business system 2 and the file name, as well as the item name and physical name of the data contained in each file are displayed, and the flow of data for each item is indicated by arrows between files with data input / output. This displayed information is specified in the definition document of each file that can be identified in the file details DB 12.
[0048] When the person in charge of the XXX system places the cursor on the name of a data item displayed on the third data flow screen, detailed information on that item is displayed in a pop-up. For example, when the cursor is placed on the name of a data item in the input file, the meaning of that item and the definition document in which that item is specified are displayed, as shown in Figure 8B.
[0049] In addition, when the cursor is placed on the item name of data in the intermediate layer and the generated file, the data aggregation and calculation conditions and the design document of the computer program that realizes the information processing using the conditions are displayed as shown in Figures 8C and 8D, respectively. Note that this information can be obtained using the design document of the computer program that can be specified in the processing content DB 13.
[0050] By referring to the first to third data flow screens described above, the person in charge of the XXX system can easily understand the linkage status between the business system 2 he or she is in charge of and other business systems 2, which enables the smooth performance of maintenance and other operations.
[0051] Next, a second data flow visualization process for visualizing a data flow including the extent of the impact when a change occurs in data will be described. This second data flow visualization process can be executed when a third data flow screen such as those shown in Figures 8A to 8D is displayed on the display unit of the user terminal 3 as a result of the above-mentioned first data flow visualization process.
[0052] Fig. 9 is a flow chart showing an example of the procedure of the second data flow visualization process. Fig. 10A to Fig. 10D are diagrams showing an example of a third data flow screen displayed on the display unit of the user terminal 3 in the second data flow visualization process. When a display area of the item name of data displayed on the third data flow screen exemplified in Fig. 8A to Fig. 8D is pressed by a person in charge, the user terminal 3 displays an impact scope search window for searching the impact scope of the data change (S301).
[0053] Fig. 10A shows an example of a third data flow screen including an impact scope search window. As shown in Fig. 10A, the impact scope search window 111 displays a display field for displaying the name of the business system 2 and the file, and the item name of the data of the file, an input field for inputting the change portion, and buttons for instructing to start and cancel the search. Note that Fig. 10A shows an example in which "FE_NY_100T" has been input as the change portion. This is one of the variables belonging to the item "product name". Here, the explanation will continue assuming that a change occurs in the definition of this variable "FE_NY_100T".
[0054] The person in charge enters the changes in the input field of the impact scope search window 111 and presses the search button to complete the input of the search information. When the user terminal 3 accepts the input of the search information from the person in charge (S302), it transmits a search request including the entered changes, file names, and item names to the visualization system 1 (S303).
[0055] When the visualization system 1 receives a search request (S401), it acquires input / output information related to the business system 2 to which the file including the current change is input from the input / output relationship DB 11 (S402). Next, the visualization system 1 acquires file detail information related to the file included in the input / output relationship information from the file detail DB 12 (S403), and further acquires processing content information that specifies the processing content for that file from the processing content DB 13 (S404).
[0056] Next, the visualization system 1 judges whether or not the change will have an impact on each business system 2 based on the acquired input / output relationship information, file detail information, and processing content information (S405). To explain a specific example of this judgment, for example, in a business system 2 to which a file including a change has been input, if there is a computer program that performs a predetermined process on the change, it is judged that the computer program of the business system 2 will be affected. In contrast, if there is no such computer program in the business system 2, it is judged that there will be no impact on each computer program of the business system 2.
[0057] Furthermore, even if a computer program that performs a specified processing on the changes exists in a business system 2 to which a file containing changes is input, if the changes are not propagated by that computer program to a downstream business system 2, it is determined that there is no impact on each computer program in the downstream business system 2.
[0058] Next, the visualization system 1 generates new data flow diagram information by reflecting the result of the determination of the presence or absence of an influence on the data flow diagram information generated by the preceding first data flow visualization process (S406). This data flow diagram information corresponds to the information displayed on the third data flow screen exemplified in Figures 10B to 10D. As will be described later, the first and second data flow screens may be displayed thereafter, but these screens are the same as those in the first data flow visualization process and no particular changes are made.
[0059] The visualization system 1 transmits the generated data flow diagram information to the user terminal 3 (S407). Upon receiving this data flow diagram information (S304), the user terminal 3 uses the data flow diagram information to display a third data flow screen on the display unit (S305).
[0060] 10B to 10D show an example of a third data flow screen showing the contents of the data flow diagram information generated in step S406 described above. In the example shown in FIG. 10B, a thick arrow is used as information showing the determination result that there is an influence. More specifically, if there is a computer program that is determined to be influenced in step S404, the arrow showing the data flow that caused the determination result is changed from a thin line to a thick line and displayed. In FIG. 10B, four arrows are displayed in thick lines.
[0061] Also, when it is determined that there is no impact because the change will not be propagated to downstream business system 2, it is useful as reference information to clearly indicate that the change will not be propagated. Therefore, the arrows showing the data flow related to the change are displayed in dashed lines instead of solid lines. In Fig. 10B, two arrows are displayed in dashed lines.
[0062] The person in charge can understand the range of impact caused by the data change by referring to the thick arrows on the third data flow screen. Also, by referring to the dashed arrows, the person in charge can easily confirm data that has not been propagated along the way. Note that these thick and dashed lines are merely examples, and it goes without saying that they may be expressed in other ways (for example, by changing the color or blinking, etc.).
[0063] When the person in charge places the cursor on the item name of the data displayed on the third data flow screen, information indicating the processing content related to the changed portion is displayed in a pop-up. For example, when the cursor is placed on the item name of the data in the intermediate layer, an overview of the processing related to the changed portion (here, the variable "FE_NY_100T") and a design document of the computer program that realizes the processing are displayed, as shown in FIG. 10C. The same is true when the cursor is placed on the item name of the data in the generated file; an overview of the processing related to the changed portion and a design document of the computer program that realizes the processing are displayed, as shown in FIG. 10D. These displays enable the person in charge to efficiently obtain information that is useful for maintenance, etc.
[0064] After the third data flow screen is displayed as described above, the first and second data flow screens can be displayed again by the person in charge. This allows the person in charge to take necessary measures while referring to details of each business system 2 and each file at any time. For example, after checking the extent of the impact on the third data flow screen, the person in charge can display the second data flow screen and check the sending and receiving time of the affected file, thereby grasping the time when the impact will become apparent. This makes it possible to prevent the occurrence of failures caused by data changes, for example, and to efficiently handle problems.
[0065] In this embodiment, the first to third data flow screens are displayed on separate screens, but at least two of the first to third data flow screens may be displayed on a single screen, which can improve the visibility of information.
[0066] (Other embodiments) In the above embodiment, the visualization system 1 determines whether there is an impact by using the processing content information stored in the processing content DB 13 (S405), but this is not limited to this, and the presence or absence of an impact may be determined without using the processing content information. For example, the visualization system 1 may determine whether a file including data related to the change is input or output by using the input / output relationship information and the file detail information, and determine whether there is an impact based only on the determination result.
[0067] In addition, when the judgment result of the presence or absence of an influence changes depending on the contents of the specification or the like that the visualization system 1 does not understand, there is a possibility that the above embodiment cannot make an accurate judgment. Therefore, it is convenient to have a function that allows the judgment result to be manually corrected. For example, in order to allow a person in charge who judges that the judgment result by the visualization system 1 is not appropriate to manually correct it, a correction button 112 and a registration button 113 for registering the correction contents may be provided on the third data flow screen as shown in FIG. 11. In this case, after the person in charge presses the correction button 112, if the person in charge moves the cursor to the part to be corrected and presses it again, the judgment result of that part is displayed inverted. In the example shown in FIG. 11, the data flow of the item name "product name" between "A-1 file" and "middle layer X-1" was displayed with a thick line (see FIG. 10B), but as a result of the correction, it is changed to a display with a thin line, that is, a judgment result of no influence. After that, when the registration button 113 is pressed, information indicating the change contents is transmitted from the user terminal 3 to the visualization system 1. Based on this information, the visualization system 1 generates data flow diagram information that reflects the modifications made by the person in charge and provides this to each person in charge. This allows each person in charge to understand the data flow more accurately. The visualization system 1 also stores information indicating the modifications, and determines whether there has been an impact based on this information the next time each person inquires about the changes. This makes it possible to expect more accurate determinations from the next time onwards.
[0068] As described above, when the visualization system 1 has a function for realizing manual correction by a person in charge, it is desirable to have a function for notifying each person in charge that the manual correction is possible, since it is possible to accurately determine the necessity of the correction by utilizing the knowledge of each person in charge. Therefore, in the second data flow visualization process, the visualization system 1 may notify the person in charge of each business system 2 displayed on the third data flow screen to confirm whether or not the correction is necessary. This notification may be made, for example, by using the email address of each person in charge stored in the input / output relationship DB 11. In this case, when the person in charge who received the notification accesses the visualization system 1 using the user terminal 3, the display unit of the user terminal 3 displays the third data flow screen as shown in FIG. 11, for example. Here, each person in charge appropriately makes corrections and registers the contents of the corrections, so that it is possible to grasp the scope of the impact more accurately. [Explanation of symbols]
[0069] 1. Data flow visualization system 11 Input-Output Relational Database 12 File Details Database 13 Processing Content Database 2. Computer Systems (Business Systems) 3. User terminal 101 Communication Network
Claims
1. an input / output relationship acquisition unit that acquires input / output relationship information indicating an input / output relationship of a file including data among a plurality of computer systems; a determination unit that, when a change occurs in data in one computer system, determines whether or not there is an effect on other computer systems based on the input / output relationship; a generating unit that generates data flow diagram information for illustrating a data flow between computer systems including the determination result of the presence or absence of the influence; an output unit for outputting the data flow diagram information; A data flow visualization system between systems.
2. A processing content acquisition unit that acquires processing content information indicating the content of information processing using each data in each computer system Further equipped with the determination unit determines whether the data to be changed is used in the information processing based on the processing content information, and determines that there is an influence when it is determined that the data to be changed is used in the information processing. The data flow visualization system according to claim 1 .
3. a propagation presence / absence acquisition unit that acquires propagation presence / absence information indicating whether each piece of data is propagated from an upstream computer system to a downstream computer system; Further equipped with The determination unit determines whether or not the changed data is propagated based on the propagation presence / absence information, and determines that there is an influence when it is determined that the changed data is propagated.
3. The data flow visualization system between systems according to claim 1 or 2.
4. When the determination unit determines that the data to be changed is not propagated, the generation unit generates the data flow illustrated information including non-propagation information indicating that the data is not propagated. The data flow visualization system according to claim 3.
5. the input / output relationship information includes timing information indicating a timing at which a file is input from an upstream computer system to a downstream computer system; The generating unit generates the data flow diagram information including the input timing.
3. The data flow visualization system between systems according to claim 1 or 2.
6. The input / output relationship information includes person in charge information indicating a person in charge of each computer system, The generation unit generates the data flow illustrated information including the person in charge.
3. The data flow visualization system between systems according to claim 1 or 2.
7. The person in charge information includes person in charge transition information indicating a transition status of the person in charge, The generation unit generates the data flow illustrated information including a transition status of the person in charge. The data flow visualization system according to claim 6.
8. a prompting unit that prompts a person in charge of each computer system to confirm whether or not the result of the determination needs to be corrected; When an instruction to correct the determination result is received from the person in charge, the generation unit generates the data flow illustrated information reflecting the correction.
3. The data flow visualization system between systems according to claim 1 or 2.
Citation Information
Patent Citations
Inter-system cooperation data visualization apparatus and visualization method
JP2018164180A
