JP2012203702A - Business system change support system, business system change support program, and business system change support method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem that the degree of appropriateness of a change part of a business system is not recognized under an environment in which business by the business system is repeatedly changed.SOLUTION: A business system change support system comprises: storage means for storing information of each step of business registered as an element of the business system, information of each application, and their relationship, and storing man-hours and increase/decrease of a scale for the change performed to the application as a change history for every change of the business system; and processing means for registering addition, change and deletion to the change history separate from existing information without overwriting the existing information, summing up the number of times of the business change for the pertinent business step separately for the addition, the change and the deletion from the recorded change history for a range specified from a user, summing up the total man-hours and the total increase/decrease of the scale accompanying the business change of the application in charge of the step, and outputting summed-up information as a list.

Description

  The present invention relates to a business system change support system and a method for supporting the business system change support system for assisting a department having jurisdiction over the change of the business system in a business environment where the business system is repeatedly changed. About.

  Utilizing information processing technology as a business system, we have provided various services and information. These business systems are being replaced, improved, repaired, and modified as the times change.

  For companies, it is necessary to create a system that can respond to changes in the market environment and user needs in accordance with the growth of basic technologies, such as service-oriented development and the rise of cloud environments, and can rapidly develop new businesses. Therefore, it is desirable to be able to start up a business system according to requirements and to reconstruct the business system in a short period of time.

Business systems are often responsible for the planning, development, operation and maintenance of their information systems department.
Also, companies that use business systems give their information system departments the role of supervisory departments in development, and work in the downstream processes (design to manufacturing, testing, operation) in the software development process of the business system applications. Often outsourced to one or more SIer (System Integrator) to develop business systems under the supervision of the information system department.

  Patent document 1 is mentioned as a technique relevant to the introduction of the business system. In Patent Literature 1, two or more programs of a sales management program, a sales support program, a schedule management program, and an inventory management program are constructed by appropriately combining a plurality of component programs, and the programs used respectively between departments are linked. An integrated business system that shares part programs is described. In this integrated business system, when the system is started up, the development cost can be reduced and the development period can be shortened with the sharing of the part program. Please refer to them as necessary.

In order to construct and operate business applications, various management and devices are required.
As one aspect, it is important to grasp the change of the entire system and manage it according to the change. Depending on the company's business scale, outsourcing the software development process downstream of application development and update to multiple SIers, the user company responsible for the entire system is responsible for the business execution status, system operation status, and business requirements. There are many cases in charge of only system planning tailored to the situation. The user company needs to perform management from the following viewpoints in order to grasp and deal with such problems.

1. The business is running smoothly
(1) Quickly deal with business problems discovered from business data flowing on business systems
(2) Quick response to business problems caused by the operational status of business systems
2. Appropriate business system
(1) Respond quickly to failures such as system outages that occur in business systems
(2) Construction and maintenance of an efficient architecture that can cope with business renewal, change and restructuring. Is based on business process design information designed using BPMN (Business Process Modeling Notation), which is a typical method for describing business processes, and BAM (Business Activity Monitoring) is used to monitor the progress of business in real time. ) Product exists. BAM can grasp information such as defective product rate, lead time, number of complaints, number of sales, out-of-stock rate, and business processing time, and provides functions mainly for managers and business managers of user companies.

2. In general, it is a category in which the information system management department of the user company and the SIer who received the order are responsible for management.
2- (1) is a field that can be solved by operation management products specialized in system monitoring and troubleshooting.
For 2- (2), the existing business system is appropriately constructed so that it can respond to the subsequent update, change, and restructuring of the business, and an efficient architecture that tracks the subsequent changes is developed each time. do it.

JP 2006-277520 A

  As mentioned above, companies that use business systems outsource software development processes to multiple SIers, and their information system department is responsible for planning and maintaining business systems including SIer supervision. There are many cases.

Such an information system department has the following problems from the viewpoint of constructing and maintaining an efficient architecture that can cope with business changes while minimizing costs. In addition, the following problems become even more noticeable for user companies who place orders with multiple SIers.
・ I want to change the function of an application according to business changes, but I do not know the entire system, so I cannot judge whether the scale and cost of the change are appropriate.
・ I want to optimize the existing system infrastructure and business applications in accordance with the latest business processes, improve functions and bundle common parts, but I don't know where to start.

  One of these factors is that the information system department does not have the capacity (time and expense) to grasp the entire picture including the architecture and source code, and the capacity to demonstrate sufficient technical capabilities. Can understand the current situation, even if they have grasped, but have not been able to grasp the system.

  As an approach for solving the former problem, there is a mechanism for visualizing and displaying a business procedure in an easy-to-understand manner using a method BPMN for describing a business process in order to grasp the correspondence between the business and the system. In addition, there is a technique for managing characteristics of business processing as a rule in combination with BRMS (Business Rules Management System), which is a position that complements BPMN, and specifying a point of influence on the system due to a change. As an example, it is mounted on IBM WebSphere (registered trademark) ILOG (registered trademark) JRules, or ORACLE BPM SUITE 11g.

By combining the features of both products, a business process is described in BPMN, and an application corresponding to a business rule that defines the characteristics of business processing (business rules, conditions, judgment criteria) is generated, and the system is executed on the execution engine. Is to operate as.
According to this feature, when business processes and rules are changed, there is an advantage that the affected part on the system can be grasped, but it is assumed that an original execution base is introduced, and it is desired to use an existing system or to easily reconstruct it. For user companies that cannot be replaced, there are very high barriers in terms of introduction cost and time.

  As for the latter problem, there is an approach of reversing the architecture information from the source code of the operating system to improve the inefficient point on the architecture. With such an architecture analysis tool, it is possible to determine whether or not the implementation is optimal based on certain business specifications and functional specifications, such as analysis and visualization of software structure, and analysis of effects when software is changed. However, although it is useful for SIer when performing optimization at the source level, it is difficult for the information system department to understand the response between analysis results and changes in business, the impact of analysis results on overall operations, and business processes. There are restrictions such as rules and rules, and it is insufficient as a function from the viewpoint of optimization in accordance with work and changes.

  Therefore, the present invention has been made in view of the above-described problems, and prioritizes optimization of business systems while considering business processing characteristics and existing business systems when repeatedly modifying existing business systems. It is an object of the present invention to provide a business system change support system that outputs information that can be easily grasped.

  The business system change support system according to the present invention stores information on individual steps of business registered as business system elements, information on individual applications registered as business system elements, and their relationships. In addition, for each change of the business system, storage means for storing the change in man-hour and scale of the change made in the application as a change history, and addition, change, and deletion to the change history to existing information In addition to registering it separately from the existing information without overwriting, the business change to the corresponding business step from the change history recorded in the storage means within the range specified by the user The number of times is added, changed, and deleted, and the total processing is performed. Decreasing the aggregation processing, characterized by comprising comprises processing means for outputting the aggregate information as a list.

  According to the present invention, when an existing business system is repeatedly changed, a business system that outputs information that can easily grasp priorities in business system optimization while considering business processing characteristics and existing business systems. A change support system can be provided.

It is a block diagram which shows the structure of the business system change assistance system concerning a 1st Example. It is explanatory drawing which shows the table and data item which a work design information storage part has. It is explanatory drawing which shows the table and data item which a system information storage part has. It is explanatory drawing which shows the table and data item which a change log | history storage part has. It is explanatory drawing which shows the table and data item which a relationship information storage part has. It is explanatory drawing which visualizes and shows the relationship between business design information and system information. It is a flowchart which shows the new registration flow of the business design information and system information in a change registration part. It is a flowchart which shows the update registration flow of the business design information in a change registration part. It is a flowchart which shows the update registration flow of the system information in a change registration part. It is explanatory drawing which shows the order management business regarding a sales business made into the business processed by a change log | history analysis part. It is explanatory drawing which shows the output of the process result of the change log | history analysis part with respect to the work step (L0-S3) in FIG. It is explanatory drawing which shows the output of the process result of the change log | history analysis part with respect to the work step (L2-S2) in FIG. It is a flowchart which shows the processing flow performed using the change log | history with respect to the designated range in a change log | history analysis part. FIG. 14 is a continuation flowchart of FIG. 13A showing a processing flow performed using a change history for a specified range in a change history analysis unit. It is a block diagram which shows the structure of the business system change assistance system concerning a 2nd Example.

  Embodiments of the present invention will be described using examples based on FIGS.

  FIG. 1 is a block diagram illustrating a configuration of a business system change support system 100 according to the first embodiment.

  In the business system change support system 100, a storage device 110 that stores necessary data, a processing device 120 that accumulates, aggregates, and processes data, an input device 130 that a user performs an input operation, and a user browses processing results. The display device 140 is configured.

The storage device 110 includes a next business design information storage unit 112, a system information storage unit 113, a change history storage unit 114, and a relationship information storage unit 115.
The business design information storage unit 112 stores information related to business design and the like regarding the steps obtained by dividing the flow of the business into predetermined work units and the business rules obtained by making the processing of the steps into rules.
The system information storage unit 113 stores information related to software design and the like regarding the application and source code indicating the system configuration and the collection of source codes, and their storage destinations.
The change history storage unit 114 stores information related to business and system change histories. The change history records, for each change of the business system, the man-hour for the change made to the system and the increase / decrease in its scale.
The relationship information storage unit 115 stores relationships between business steps and rules, and systems and applications.

The processing device 120 includes a next change registration unit 121 and a change history analysis unit 122.
The change registration unit 121 newly registers, adds, changes, and deletes information in each storage unit of the storage device 110.
The change history analysis unit 122 aggregates and processes desired information while referring to the change history within a range of conditions input by the user from the input device 130, and outputs the processing result to the display device 140.

  In addition, the business design information storage unit 112, the system information storage unit 113, the change history storage unit 114, and the relationship information storage unit 115 of the storage device 110 store data tables illustrated in FIGS. In the figure, rectangles indicate tables and data items constituting the tables, and lines between rectangles indicate relationships. Characters (0, 1,0 to *, 1 to *) written at both ends of the relation line represent the multiplicity of records.

FIG. 2 shows a table and data items of the business design information storage unit 112. The business design information here refers to a business step in which layers of work are set according to the granularity of each work and decomposed into work units, called business steps, and business characteristics included in business steps are called business rules. This information is composed of a set of It is possible to define zero or more business rules for one business step, and record each information in the business step table and business rule table. Information that can identify the previous step and the subsequent step is also recorded in the business step.
The correspondence between the business step and the business rule is defined in the relationship information storage unit 115.

FIG. 3 shows a table and data items of the system information storage unit 113. The system information here refers to information related to source codes in units of files and information of units of applications formed by these chunks, and is configured by a set of them. The block may be an arbitrary unit set by the user.
In the source code table, a source code file storage destination path and version, a logical source code name indicating the position of the source code, and the like are recorded.

  FIG. 4 shows a table and data items of the change history storage unit 114. The change history here refers to information obtained by sequentially accumulating contents of changes including man-hours of business information and system information changed by a user at a certain timing, and source code change amounts in units of applications.

FIG. 5 shows a table and data items of the relationship information storage unit 115.
The business configuration table stores the relationship between the business step recorded in the business design information storage unit 112 and its lower steps.
The rule application relationship table stores the relationship to which business step the business rule recorded in the business design information storage unit 112 is applied.
The system configuration table stores the relationship between the system information application and the applications included therein.
The business-system correspondence table stores the correspondence between business steps and applications.

Here, the relationship between the business design information and the system information is visualized and described with reference to FIG.
FIG. 6 shows the business design information in a tree structure. In the business, apexes are assigned as layer 0, and each of the broken down work steps exists in layers 1 to 3, respectively. In the example of FIG. 6, the illustrated business is composed of layer 1 business steps [L1-S1], [L1-S2], [L1-S3]. Also, the business step [L2-S1] is disassembled into layer 2 business steps [L2-S1], [L2-S2] ... [L2-S8], and the business step [L2-S2] Decomposed are the business steps [L3-S1], [L3-S2], [L3-S3].
Also, as shown in the figure, business rules A, B, and C are associated with each predetermined business step, and business rules A are business steps [L2-S2] [L2-S8] and business rules B are Business step [L3-S2] and business rule C are applied to business steps [L3-S3] and [L3S11]. These pieces of information and the relationship between the information are recorded in the business step table and business rule table of the business design storage unit 112 and the business configuration table and rule application relation table of the relationship information storage unit 115.

On the other hand, as system information, AP200, AP220, APc10, and APc01 are defined as applications. As shown in the figure, the AP 200 uses a source code group corresponding to the business steps [L1-S2] and [L1-S3] and its lower steps as an application for realizing the business. Similarly, AP 220 uses the business step [L2-S2] and its lower steps, and AP 280 uses the business step [L2-S8] and its lower step source code group.
As applications commonly used in business, APc10 is related to business steps [L3-S2] [L3-S3], and APc01 is related to business steps [L3-S3] [L3-S11]. ing.

  As described above, an application can be defined with various granularities from a unit constituting a flow of a series of processes to a common logic of processes used locally. The application defined as APc10 manages the definition of APc01 and other source code related to APc10. Similarly, the source code group linked to the AP 220 is managed as the source code related to the APc 10 and other APs 220.

Each information and the relationship between the information are recorded in the application table and the source code table of the system information storage unit 113, and the system configuration table and the business-system correspondence table of the relationship information storage unit 115.
The application registration unit is arbitrary. In other words, by registering small-scale source code groups associated with lower-level business as applications, business changes and system change history can be managed in more detail.

Next, the operation of the business system change support system 100 will be described with reference to FIGS.
The user who performs the operation here is the information system department of the user company and SIer who is the ordering party for system development. That is, the business system information of the business system change support system 100 is operated by the information system department of the user company, and the system information is operated by the SIer.

<Description of Operation of Change Registration Unit 121>
FIG. 7 shows a flow of processing including registration of related data in the change history storage unit 114 when new registration of data in the business design information storage unit 112 is performed. In FIG. 7, the business design information and system information input from the input device 130 are registered in the respective storage units, and the relationship between them is registered in the relationship information storage unit 115.

  FIG. 8 shows a flow of processing including addition, change, and deletion of related data to the change history storage unit 114 when adding, changing, and deleting data to the business design information storage unit 112. For data changes, existing information is not overwritten but treated as new and a new record is registered. For deletion, a deletion flag provided in the table is set, and the existing information is kept stored.

  FIG. 9 shows a processing flow including addition, change, and deletion of related data to the change history storage unit 114 when adding, changing, and deleting data to the system information storage unit 113. For data changes, existing information is not overwritten, but it is treated as new and a new record is registered. For deletion, a deletion flag provided in the table is set, and the existing information remains stored.

<Description of Operation of Change History Analysis Unit 122>
The processing operation of the change history analysis unit 122 will be described using a business example based on the order management business related to the sales business shown in FIG.

  FIG. 10 shows the business flow in a format in which business name: order management (layer 0) is broken down into layers 1, 2, and 3 according to the granularity of work. 11 and 12 are examples of screens that the change history analysis unit 122 outputs to the display device 140 when the business design information is registered based on the business design as illustrated.

  FIG. 11 is an example of a change history display screen output by the change history analysis unit 122. The display screen 1410 includes a specified period 1411, a specified job 1412, and a change history summary 1413. Information on the specified period 1411 and the specified task 1412 is information input by the user when making an inquiry to the change history analysis unit 122.

  In the change history summary 1413, a summary of the results obtained by summing up and processing desired information from the change history corresponding to the specified period for each of the layer 1 business steps constituting the layer 0 business designated in the designated business 1412 is displayed. indicate. Further, the change history summary 1413 includes, for each business step, the number of additions, changes, and deletions of business steps and business rules defined below, and the addition / change / deletion scale of the source code line of the associated application. Is displayed as the degree of change of work or system.

  In addition, the cumulative value of the number of additions, changes, and deletions for each business step and business rule is calculated as the amount of change, and the increase / decrease value of the source code line for each application total scale is the total scale increase / decrease (scale description increase / decrease) indicate. In the change cost, a cumulative value (total man-hours) of man-hours (change costs) required for correcting each application is displayed.

Here, information and analysis examples that can be read from the screen example shown in FIG. 11 will be described. It is assumed that the information provided can be used as follows.
・ In locations where it is determined that the frequency of business changes is high, localizing the processing logic, creating a library of common functions among multiple applications, and strengthening the functions on the basis of changes on the base side, reduce the man-hours and labor of the change work. Consider whether it can be reduced
・ Decrease the priority of optimization for areas where the frequency of business changes is determined to be low
-If the degree of system change is large compared to the degree of business change, check what changes are being made on the system side, and then consider whether the volume of change work can be reduced. Referring to screen 1410, in the business of order management based on business design information, the number of business steps and business rules included in the order confirmation (L1-S2) is larger than the others, while order information is registered from the corresponding system information. It can be read that the source code size of the application corresponding to (L1-S4) and billing (L1-S5) is the same as 300KL.
Next, when checking the amount of change in the business from the business change contents column, it can be read that the amount of change for the business rules included in the order confirmation (L1-S2) is large compared to others and there is no other big difference. .
Also, was the order confirmation (L1-S2) and order confirmed from the change cost in the system change column? It can be seen that a cumulative amount of 1000 people · H is spent respectively on the change of the application AP 200 corresponding to (L1-S3) and the application AP 400 corresponding to the charge request (L1-S5). Similarly, from the application change scale, it can be seen that the AP 200 is added and the change scale is larger than the others, and the change scale of the AP 400 is prominent.

  Based on these matters, we will consider reducing the maintenance cost related to system changes. In this case, referring to the change history summary, it is possible to overlook the entire order management business system, and the following can be considered for system optimization.

(1) In order confirmation (L1-S2), changes in business steps are small, but due to repeated changes in business rules, the source code of the corresponding application is greatly added, changed, or deleted, increasing the total source code The amount is large and the change cost is large accordingly. (2) In the billing (L1-L5), the change of business steps and business rules is small, but the scale of application changes is greatly accumulated, Accordingly, the change cost is large. From this, first, confirm the details of the change in the business design information and system information, and the details of the change cost, which were further broken down for (1) and (2). Since the ratio of the cost to the whole is small, it can be judged that the optimization priority is lowered.
In the example of the screen in FIG. 11, it is possible to display information about lower layer business by clicking the business step name link. The lower layer may be displayed simultaneously by indenting.

  Also, the change history analysis unit 122 stands out from the extracted information by performing color coding, underlining, highlighting, character enlargement, etc., on the portion useful for consideration as information to be examined by the user from the information aggregated as the output list. The output may be as follows. At this time, the change history analysis unit 122 performs, for example, a process of extracting a predetermined location, for example, a location where the frequency of change of each business step is relatively high, or the total man-hours relative to the change amount of the change of the business step is relatively It is only necessary to extract a high part, a part where the increase / decrease of the scale relative to the change amount of the change of the business step is relatively high, etc. by a threshold value or a comparison calculation. In addition, for each extraction method, character information indicating a study method using the information, voice explanation, or the like may be output as advice.

FIG. 12 shows an example of a change history display screen displaying information broken down on (1). The display items are the same as in FIG.
Suppose that the user breaks down and confirms the work of the lower layer, and it is found that the price calculation (L2-S2) accounts for most of the change cost in (1). Therefore, it is set as the scene which confirms about each business step of the layer 3 which is the lower layer. The analysis of FIG. 11 is continued from the screen example of FIG.
Looking at the percentage of change cost, the change cost of application AP222 corresponding to manufacturer discount judgment (L3-S2) and manufacturer discount application (L3-S3) accounts for 80% of the price calculation (L2-S2). Therefore, when attention is paid to the change contents of the business design information and system information, the number of additions and changes of business rules is conspicuous.
From these facts, the user can recall the search for other business rules that are similar to the business rules to be added as one policy for reducing the cost of system changes to be made in the future. become. If it exists, does not include similar processing logic that can be aggregated in the business step to which the business rule is applied, or does not include similar processing logic that can be aggregated in the added or changed source code , Etc. can be considered to optimize the source code to be maintained.

13 (FIGS. 13-1 and 13-2) is a processing flow performed by the change history analysis unit 122 when outputting the screen examples of FIGS.
As shown in the drawing, by inputting a specified period and a specified task to the change history analysis unit 122, various information that is used as a change history summary for the range specified by the user in accordance with the illustrated processing example. Are extracted from each storage unit of the storage device 110, calculated from the information, aggregated, and output.

  By operating the business system change support system 100 in this way, the following effects can be obtained.

  The first effect is that it is possible to quantitatively refer to the respective fluctuation scales of the work design information and system information and the accumulated value of the work cost from the change history accumulated sequentially in the past. As a result, the information system department of the user company that is the user can optimize the system to reduce maintenance costs without having to know the system architecture and source code in detail, depending on the status of each variable. Can grasp useful information that can be used for prioritization judgment and requirement extraction.

  The second effect is that even if there is an existing business design document, software design document, source code, or other assets, it is possible for users to manage business and system linking and change history later. The introduction burden is light.

  In other words, business design information, system information, and their corresponding relationships can be registered in the information processing system in advance, and when a change occurs, the change target and change amount can be accumulated as a change history so that the user (supervision department) can The overhead information used for reducing the change cost can be obtained by inputting a designated range such as a designated period or a designated job.

  Next, a second embodiment will be described with reference to FIG.

FIG. 14 is a block diagram illustrating a configuration of a business system change support system 200 according to the second embodiment.
In the business system change support system 200, a storage device 110 that stores necessary data, a processing device 220 that stores and processes data, an input device 130 that allows a user to perform an input operation, and a display device that allows a user to view processing results. 140. The difference between the business system change support system 200 and the business system change support system 100 is that the processing device 120 is replaced with a processing device 220.

  In addition to the change registration unit 121 and the change history analysis unit 122, the processing device 220 is provided with a business design information extraction unit 223 and a system information extraction unit 224.

  The business design information extraction unit 223 extracts each information (business step, business rule) input to the business design information storage unit 112 using the business design created and visualized by BPMN or the like as input, and stores it in the recording device 110. sign up.

  The system information extraction unit 224 extracts and records each information (application, source code) input to the system information storage unit 113 using the software design, source code, and build script created and visualized by UML or the like as inputs. Register with device 110.

  In this manner, by adding the business design information extraction unit 223 to the processing device 220, it is possible to reduce the burden of inputting information related to the business design. It can also be used to extract missing parts of information related to business design. Similarly, by adding the system information extraction unit 224, the burden of inputting system information can be reduced.

  As described above, the business system change support system to which the present invention is applied associates the characteristics of business processing with the entities constituting the business system and their change history even when an existing system exists, With a system that can accumulate and grasp from the past to the present, it provides information that can be used as a reference for determining whether SIer work estimates are appropriate, prioritizing business system optimization, and extracting requirements from the standpoint of the information system department.

  The business system change support system may be constructed using a general information processing apparatus. That is, each part of the business system change support system uses a combination of hardware and software, and a business system change support program is developed in the RAM, and hardware such as a CPU is operated on the basis of the program. Realized as various means. The program may be recorded on a storage medium and distributed. The program recorded on the recording medium is read into a memory via a wired, wireless, or recording medium itself, and operates a control unit or the like. Examples of the recording medium include an optical disk, a magnetic disk, a semiconductor memory device, and a hard disk.

  In other words, the information processing apparatus that operates as the business system change support system operates as the storage device or the processing apparatus described above based on the business system change support program expanded in the RAM. It can function as a registration unit, a change history analysis unit, a business design information extraction unit, and a system information extraction unit, and can be operated in cooperation with an input device and a display device.

  It is also effective to improve the searchability when analyzing the change history by extracting the parent-child relationship and configuration of business rules in advance and registering them as a table in the relationship information storage unit.

  It is also possible to pre-define weighting values indicating importance and granularity in the business step and business rules of the business design information, and add processing to the change history analysis unit that takes into account the amount of change in the business design information. It is also effective to quantitatively calculate changes in work that take into account meanings that match the needs of employees.

  In addition, the output result of the change history analysis unit displayed on the display device is associated with a list in which individual steps of graph display and work are associated with the tree structure, and the position of the tree structure as information to be considered by the user It is also effective to display the man-hour size and the like with a visible effect.

  In this way, when repeatedly changing an existing business system, by providing the information obtained from the change history as information that can grasp the business process characteristics of the business system and the existing business system from a bird's-eye view, Users can easily grasp priorities for optimization.

  It should be noted that the specific configuration of the present invention is not limited to the above-described embodiment, and changes within a range not departing from the gist of the present invention are included in the present invention.

In addition, a part or all of the above-described embodiments can be described as follows. Note that the following supplementary notes do not limit the present invention.
[Appendix 1]
Information on individual steps of business registered as business system elements, information on individual applications registered as business system elements, and their relationships are stored, and each time the business system is changed, Storage means for storing, as a change history, man-hours and changes in scale for changes made to the application;
The addition, change, and deletion to the change history are registered separately from the existing information without overwriting the existing information, and the range specified by the user is recorded in the storage means. From the change history, the number of job changes for the corresponding job step is added, changed, and deleted, and totalized, and the total increase and decrease of the number of man-hours and scale associated with the job change of the application that takes the step is tabulated And a business system change support system comprising processing means for outputting the totaled information as a list.

[Appendix 2]
The processing means accepts individual job steps and / or periods referring to the change history as a range designated by the user, and adds, changes, and deletes the number of job changes for the designated steps and / or periods. The business system change as described in the above supplementary note, wherein the total processing is performed separately, and the increase and decrease of the total man-hour and scale accompanying the business change of the application that takes the step is totalized, and the totaled information is output as a list Support system.

[Appendix 3]
The processing means counts the number of business changes for the corresponding business step within the range specified by the user, and for each of the two or more steps having the same application having the step, for each application. The business system change support system as described in the above supplementary note, characterized in that the total increase and decrease of the number of man-hours and the scale due to the business change are totalized and the totalized information is output as a list.

[Appendix 4]
The business system change support system according to the above supplementary note, wherein information indicating the number of changes is not registered artificially in the information registered as the change history.

[Appendix 5]
The processing means reflects the weight value indicating the importance / granularity registered in advance for each individual step in the amount of change in the work change content within the range specified by the user, The business system change support system according to the above supplementary note, wherein an intention to recall a change to be prioritized is given to a list to be aggregated and output by assigning importance / granularity to each business in the system.

[Appendix 6]
The processing means, from the information aggregated as an output list, a location where the frequency of change of each business step is relatively high, a location where the total man-hour for the amount of change in the change of the business step is relatively high, In addition, we extract the part where the increase or decrease of the scale with respect to the change amount of the change of the work step is relatively high, output it as the information to be considered by the user so that it can be recognized as other information, The business system change support system as described in the above supplementary note, wherein advice on the examination method for the classified portion registered in advance in association with each extraction process is output.

[Appendix 7]
The processing means associates the aggregated information to be output with a list in which individual steps of the business registered as elements of the business system are associated with the tree structure, and the tree structure The business system change support system as described in the above supplementary note, wherein the position and the man-hour size are classified and output so as to be visually recognizable.

[Appendix 8]
Means for recording and storing system information indicating a system configuration by associating information on an application forming a business system with information on a source code which is a component of the application;
Means for recording and storing the business design information including the business flow as a business configuration by associating the steps obtained by dividing the business flow into predetermined work units, and including the application relation of the business rules in which the processing relations of the steps are ruled;
For each change in the business configuration and business rule application relationship indicated by the business design information, the change made in the application and the source code indicated by the system information and the increase and decrease in scale together with the man-hour are recorded as information related to the change history. Means for storing;
Means for recording and storing, as related information, information associating the application configuration of the business configuration and business rules indicated by the business design information with the system configuration indicated by the system information;
A change registration means 1210 for registering separately from the existing information without overwriting existing information with additions, changes, and deletions to the business design information and the system information;
About the business design information, the system information, and the change history registered when the existing business system is repeatedly changed through the change registration unit within the range included in the business step instructed by the user Information, and the related information is obtained, and the number of work changes is added, changed, and deleted for each lower step, and the total man-hours and scale associated with the work change for each application that takes charge of the lower steps. Change history analysis means that aggregates the increase / decrease, processes the aggregated information into a list, and outputs it,
A business system change support system characterized by comprising:

[Appendix 9]
The control unit of the information processing device
Information on individual steps of business registered as business system elements, information on individual applications registered as business system elements, and their relationships are stored, and each time the business system is changed, Storage means for storing, as a change history, man-hours and changes in scale for changes made to the application;
The addition, change, and deletion to the change history are registered separately from the existing information without overwriting the existing information, and the range specified by the user is recorded in the storage means. From the change history, the number of job changes for the corresponding job step is added, changed, and deleted, and totalized, and the total increase and decrease of the number of man-hours and scale associated with the job change of the application that takes the step is tabulated And a business system change support program that operates as a processing means for outputting the collected information as a list.

[Appendix 10]
The processing means accepts individual job steps and / or a period referring to the change history as a range specified by the user, and adds, changes, and deletes the number of job changes for the specified step and / or period. The program according to the above-mentioned supplementary note, wherein the totaling process is divided into two, the total increase and decrease of the total man-hours and the scale accompanying the change of the business of the application that takes the step is totalized, and the totalized information is output as a list.

[Appendix 11]
The processing means totalizes the number of business changes for the corresponding business step within the range specified by the user, and for each of the two or more steps having the same application having the step, for each application. The program according to the above-mentioned supplementary note, characterized in that the total increase and decrease of the number of man-hours and the scale accompanying the business change is totalized and the totalized information is output as a list.

[Appendix 12]
The program described in the above supplementary note, wherein the information registered as the change history does not include an item in which information indicating the number of changes artificially is registered.

[Appendix 13]
The processing means is configured to reflect a weight value indicating the importance / granularity registered in advance for each individual step in the amount of change in the work change content in the range specified by the user, so that the user's work The program according to the above-mentioned supplementary note, wherein an intention to recall a change to be prioritized is given to a list to be aggregated and output by assigning importance / granularity to each business in the system.

[Appendix 14]
From the information aggregated as a list to be output to the processing means, the location where the frequency of change of each business step is relatively high, the location where the total man-hour for the amount of change in the change of the business step is relatively high, In addition, we extract the part where the increase or decrease of the scale with respect to the change amount of the change of the work step is relatively high, output it as the information to be considered by the user so that it can be recognized as other information, The program according to the above-mentioned supplementary note, wherein advice on a method for studying the classified portion registered in advance in association with each extraction process is output.

[Appendix 15]
The aggregated information to be output to the processing means is associated with a list in which individual steps of business registered as elements of the business system are associated with the tree structure, and the tree structure as information to be considered by the user The program according to the above supplementary note, wherein the position and the man-hour size are classified and output so as to be visually recognizable.

[Appendix 16]
The control unit of the information processing device
Means for recording and storing system information indicating a system configuration by associating information on an application forming a business system with information on a source code which is a component of the application;
Means for recording and storing the business design information including the business flow as a business configuration by associating the steps obtained by dividing the business flow into predetermined work units, and including the application relation of the business rules in which the processing relations of the steps are ruled;
For each change in the business configuration and business rule application relationship indicated by the business design information, the change made in the application and the source code indicated by the system information and the increase and decrease in scale together with the man-hour are recorded as information related to the change history. Means for storing;
Means for recording and storing, as related information, information associating the application configuration of the business configuration and business rules indicated by the business design information with the system configuration indicated by the system information;
A change registration means 1210 for registering separately from the existing information without overwriting existing information with additions, changes, and deletions to the business design information and the system information;
About the business design information, the system information, and the change history registered when the existing business system is repeatedly changed through the change registration unit within the range included in the business step instructed by the user Information, and the related information is obtained, and the number of work changes is added, changed, and deleted for each lower step, and the total man-hours and scale associated with the work change for each application that takes charge of the lower steps. Change history analysis means that aggregates the increase / decrease, processes the aggregated information into a list, and outputs it,
A business system change support program characterized by being operated in the same manner.

[Appendix 17]
In the information processing system,
Stores information on individual steps of business registered as business system elements, information on individual applications registered as business system elements, and their relationships,
For each change of the business system, the change in man-hour and scale of the change made to the application is used as a change history, and the existing information is added to the existing information without overwriting the existing information. Register and remember separately,
When considering changes to the business system, the number of business changes for the corresponding business step is added, changed, or deleted from the recorded change history within the range specified by the user. And
Process the total increase and decrease of the total man-hours and scale due to the business change of the application that takes this step,
A business system change support method characterized by outputting the totaled information as a list.

  The present invention has an existing system and can be used for new software development using the assets. In particular, it can provide useful information for design information management, asset management, and project management.

100 business system change support system 110 storage device 112 business design information storage unit 113 system information storage unit 114 change history storage unit 115 relation information storage unit 120 processing device 121 change registration unit 122 change history analysis unit 130 input device 140 display device 200 business System change support system 220 Processing device 223 Business design information extraction unit 224 System information extraction unit

Claims (10)

Information on individual steps of business registered as business system elements, information on individual applications registered as business system elements, and their relationships are stored, and each time the business system is changed, Storage means for storing, as a change history, man-hours and changes in scale for changes made to the application;
The addition, change, and deletion to the change history are registered separately from the existing information without overwriting the existing information, and the range specified by the user is recorded in the storage means. From the change history, the number of job changes for the corresponding job step is added, changed, and deleted, and totalized, and the total increase and decrease of the number of man-hours and scale associated with the job change of the application that takes the step is tabulated And a business system change support system comprising processing means for outputting the totaled information as a list. The processing means accepts individual job steps and / or periods referring to the change history as a range designated by the user, and adds, changes, and deletes the number of job changes for the designated steps and / or periods. 2. The business system according to claim 1, wherein the totalization processing is performed separately, the total increase and decrease of the total man-hour and the scale accompanying the business change of the application that takes the step is totalized, and the totalized information is output as a list Change support system. The processing means counts the number of business changes for the corresponding business step within the range specified by the user, and for each of the two or more steps having the same application having the step, for each application. The business system change support system according to claim 1, wherein the total man-hour and the increase / decrease of the scale accompanying the business change are totalized, and the totaled information is output as a list.   4. The business system change support system according to claim 1, wherein information indicating the number of changes is not manually registered in the information registered as the change history. 5. The processing means reflects the weight value indicating the importance / granularity registered in advance for each individual step in the amount of change in the work change content within the range specified by the user, 5. An intention to recall a change to be prioritized is given to a list to be aggregated and output by assigning importance / granularity to individual tasks in the system. The business system change support system described in 1. The processing means, from the information aggregated as an output list, a location where the frequency of change of each business step is relatively high, a location where the total man-hour for the amount of change in the change of the business step is relatively high, In addition, we extract the part where the increase or decrease of the scale with respect to the change amount of the change of the work step is relatively high, output it as the information to be considered by the user so that it can be recognized as other information, 6. The business system change support system according to any one of claims 1 to 5, wherein advice on a method for studying the classified portion registered in advance in association with each extraction process is output. The processing means associates the aggregated information to be output with a list in which individual steps of the business registered as elements of the business system are associated with the tree structure, and the tree structure 7. The business system change support system according to claim 6, wherein said position and said man-hour size are classified and output so as to be visually recognizable. Means for recording and storing system information indicating a system configuration by associating information on an application forming a business system with information on a source code which is a component of the application;
Means for recording and storing the business design information including the business flow as a business configuration by associating the steps obtained by dividing the business flow into predetermined work units, and including the application relation of the business rules in which the processing relations of the steps are ruled;
For each change in the business configuration and business rule application relationship indicated by the business design information, the change made in the application and the source code indicated by the system information and the increase and decrease in scale together with the man-hour are recorded as information related to the change history. Means for storing;
Means for recording and storing, as related information, information associating the application configuration of the business configuration and business rules indicated by the business design information with the system configuration indicated by the system information;
A change registration means 1210 for registering separately from the existing information without overwriting existing information with additions, changes, and deletions to the business design information and the system information;
About the business design information, the system information, and the change history registered when the existing business system is repeatedly changed through the change registration unit within the range included in the business step instructed by the user Information, and the related information is obtained, and the number of work changes is added, changed, and deleted for each lower step, and the total man-hours and scale associated with the work change for each application that takes charge of the lower steps. Change history analysis means that aggregates the increase / decrease, processes the aggregated information into a list, and outputs it,
A business system change support system characterized by comprising: The control unit of the information processing device
Information on individual steps of business registered as business system elements, information on individual applications registered as business system elements, and their relationships are stored, and each time the business system is changed, Storage means for storing, as a change history, man-hours and changes in scale for changes made to the application;
The addition, change, and deletion to the change history are registered separately from the existing information without overwriting the existing information, and the range specified by the user is recorded in the storage means. From the change history, the number of job changes for the corresponding job step is added, changed, and deleted, and totalized, and the total increase and decrease of the number of man-hours and scale associated with the job change of the application that takes the step is tabulated And a business system change support program that operates as a processing means for outputting the collected information as a list. In the information processing system,
Stores information on individual steps of business registered as business system elements, information on individual applications registered as business system elements, and their relationships,
For each change of the business system, the change in man-hour and scale of the change made to the application is used as a change history, and the existing information is added to the existing information without overwriting the existing information. Register and remember separately,
When considering changes to the business system, the number of business changes for the corresponding business step is added, changed, or deleted from the recorded change history within the range specified by the user. And
Process the total increase and decrease of the total man-hours and scale due to the business change of the application that takes this step,
A business system change support method characterized by outputting the totaled information as a list.

Images