In the customer's information system, we will provide application visualization products from the viewpoint of business model (logical model) and logical architecture (responsibility).
In the scene of maintenance development and operation of the current system, the change of the person in charge and the aging of the system are progressing and the legacy of system assets is progressing, and there is a difficulty in system renovation due to "understanding of current business". For functions that are not subject to investigation when the current system is rebuilt, the investigation work is left to the system development department and vendors (for example, "with the current specifications"). At present, it is difficult to grasp and visualize in the upstream process.
Here, we introduce the "System Maintenance Support Function" product of the system visualization solution.
Conventional application asset visualization support generally provides the following four points. (①)
In addition, business modeling (modeling service) that supports business visualization creates current business models (As-Is) and new business models (To-Be), and defines data (thing: object) and processes (things: operation) that are defined in the business. Visualize. (②)
The following is a business model diagram expressed in the data domain (example: logical model of the electric industry)
① is lacking in the viewpoint of business visualization, and In ②, in order to connect the application assets of the current system, it takes a certain amount of man-hours and time in the absence of a person in charge who understands the current business. In order to improve the system, it is necessary and important to have a means to visualize the application assets linked to the "business flow and information necessary for business" of the current system.
When an engineer conducts an impact investigation or analysis work, it is common to take a bird's-eye view of the entire target system, identify the target functions and ranges, and understand the processing of specific programs included in them. is. It is important to be aware of this processing analysis step (order).
* Indicates the steps of impact investigation and analysis (≠ procedure for simple statement correction, etc.)
In order to identify the target functions and scope from an overview of the current system as a whole, it is necessary and important to have a means of visualizing the application assets linked to the "business flow and information necessary for business".
Therefore, the application model of the current system is linked to the data model of the current system by linking the elements that become the data items of the current system to the "business model (logical model) data domain" of the industry standard and the "thing (object) list" included in them. Visualize from the viewpoint of (logical model). In this way, it is possible to visualize the current system from the same viewpoint as the industry package.
* Data flow and processing access lines and some of the figures are omitted.
For the procedural type and function type of the host system development method, a group for each procedure is created as an application in consideration of commonality in the flow of processing according to the procedure (design a "line"). In the object-oriented development method, the unit of development is to create a collection of minimum units of things (information and state) and things (behavior, operation) as an application (design a "point").
For this reason, especially in object-oriented development methods, it is difficult to visualize the flow of a series of procedures, even if it is possible to grasp the scope of influence and connection only by collecting (linking) each application with the configuration and relationship (Just collect fine "points"), Visualize logical architecture , application location, application type, etc.
