Composite control method of demand preview business

Abstract

The invention discloses a composite control method of demand preview business. The composite control method comprises the following steps: (a) collecting and arranging the business structure level information, the application architecture level information and the data model level information of a large scale system; (b) establishing a mapping relation among the business structure level information, the application architecture level information and the data model level information to form a business functional entity which is stored in a resource library as business nodes; (c) selecting the business nodes in the resource library into a business process display drawing, adding, combining or deleting the business nodes and carrying out rapid one-button interface storage to form an independent business component; (d) freely combining different business components to realize visual preview for business demands, and evaluating the workload of new demands. The business structure level information, the application architecture level information and the data model level information are stored in a unified mode in the business nodes, the visualization and componentization of the business functional entity are realized, and the different business components are freely combined, so that the function preview of new demands and the evaluation of developed workload are realized.

Description

technical field [0001] The invention relates to a software design control method, in particular to a combination control method of demand preview service. Background technique [0002] During the rehearsal of large-scale software requirements, it is necessary to correlate information at multiple logical levels, including business architecture, application architecture, data model, technical architecture, etc. The harmonious coexistence of functions will not affect each other, ensuring the quality of development. [0003] The usual practice of existing technology is as follows: Since the information on business architecture, application architecture, data model, technical architecture and other levels is usually scattered in various development documents, there is no rule at all, and every time a new requirement is investigated, Both need to spend a lot of energy in massive documents to straighten out the relationship between the newly added demand modules and the original m...

AI Technical Summary

Problems solved by technology

[0005] 1) The amount of information that needs attention is too large, and it is not intuitive, and it is easy to miss;

[0006] 2) Very professional people are needed to complete this process, and the labor cost is high;

[0007] 3) Due to the weak correlation between development documents, it is easy to cause repeated development of functional modules, waste development resources, and increase development costs

Images