Component design supporting method and system

Abstract

The invention provides a component design supporting method and system, aims at improving system maintenance and quantitatively evaluating maintenance time of components. According to the invention, when a system designer designs a unit bringing together the business application functionality and data subsystem, that is, the component, maintenance history information is used to extract a maintenance mode obtained by modeling impact waves and positions during the maintenance and correct work time, and maintenance work time is evaluated by the maintenance mode, thereby being capable of designing the component with minimum maintenance work time.

Description

technical field [0001] The present invention relates to a system design method of a business application program, and more particularly, to a technique for a system designer to design a sub-system unit, ie, a module, which integrates functions and data of a business application program via a communication network. Background technique [0002] Currently, systems such as business applications are used for business execution. Such a system is often composed of multiple components and tends to be complicated in structure, and several proposals for its management have been proposed. As one of them, there is Japanese Unexamined Patent Application Publication No. 2009-129355 (Patent Document 1). In this patent document 1, it is described that "it is solved by a component division support device having a dependency analysis unit that uses policy data specifying an invalid dependency relationship and detects a violation of the policy from the dependency relationship." Dependency r...

AI Technical Summary

Problems solved by technology

[0005] In the technology disclosed in Patent Document 1, based on the strategy of specifying the dependency relationship between objects, the improper dependency relationship that affects the maintainability such as mutual calls between functions is extracted / improved, but it is not possible to quantitatively measure each component. maintenance hours

For example, it is impossible to quantitatively measure maintenance man-hours from multiple component designs and determine the design with the highest maintainability

[0006] In Non-Patent Document 1, multiple indexes are used to quantitatively evaluate the maintainability of components, but the maintenance man-hour itself cannot be measured

In addition, since only the dependency relationship between objects is evaluated, the "maintenance tendency" or "the scope of responsibility of the person in charge of maintenance" based on the domain characteristics of the business application is not reflected in the maintainability evaluation

For example, depending on the domain characteristics of the business application, the functions or data that are likely to be corrected during maintenance, and the functions or data that are likely to be affected by the correction are different

In addition, depending on whether the scope of correction during maintenance can be handled by one person in charge or requires the cooperation of multiple people in charge, the maintenance man-hours will vary.

Images