Scene-based demand modeling system and method, and information data processing terminal

Abstract

The invention belongs to the technical field of devices for executing special programs, and discloses a scene-based demand modeling system and method, and an information data processing terminal, andthe system comprises a demand preparation module, a business modeling module, and a system modeling module. According to the method, the process of converting the business document and the report intothe business entity is realized, and the business entity forms a derivation clue of the conceptual entity with the association relationship through analysis; the crowd analysis derives and converts from a business scene to a business role, and the business role derives an evolution line of the system user from the computer execution angle; a step-by-step basis, derivation and evolution are provided for transition from service current situation description to computerized description.

Description

Technical field [0001] The invention belongs to the technical field of devices for executing special programs, and in particular relates to a scenario-based demand modeling system and method, and an information data processing terminal. Background technique [0002] At present, the existing technology commonly used in the industry is as follows: divide the system modules, conduct research and modeling according to the modules, and the modeling process is more from the perspective of program implementation, and lacks the understanding of the user’s business, and cannot be timely and effective. The major problems in the discovery requirements cannot guide customers to establish the overall perspective and scene of the business; mainly structured modeling process, mainly using organizational structure diagrams, business flowcharts, data flow diagrams and other forms to express the modeling process ; The integration of software modeling is separated by a clearly divided process, resu...

AI Technical Summary

Problems solved by technology

[0002] At present, the existing technologies commonly used in the industry are as follows: divide the system modules, conduct research and modeling according to the modules, the modeling process is more from the perspective of program realization, and lacks the understanding process of user business, which cannot be timely and effective. The major problems in the discovery requirements cannot guide customers to establish an overall perspective and scenario of the business; the structured modeling process is mainly used to express the modeling process in the form of organizational charts, business flow charts, and data flow diagrams ;The integration of software modeling is separated by a clear process of phase division, resulting in inconsistencies in the context, and the requirements and later design and development cannot be effectively unified

[0003] To sum up, the problems existing in the existing technology are: guided by the functional modules finally realized by the system; using system flow charts, functional module diagrams, etc. to describe the required services; There are fewer implementations of intelligent scripts; the stages of the development process are clearly distinguished, but the correlation is not strong

[0004] The difficulty and significance of solving the above technical problems: the research process centered on "functional modules": incomplete demand research and incomplete business understanding; poor business penetration ability, difficult to form a closed loop; demand process described from the perspective of developers: not possible It is good to think about problems from the perspective of customers; the analysis process based on structural modeling: ignores the integrity of the business, resulting in incomplete and imperfect requirements; the development process based on vertical structure: requires high-level developers, From the front-end page to the back-end logic and database, etc.; the testing process mainly focused on developers: a waste of manpower and low efficiency; the operation and maintenance process based on centralized deployment: the impact of errors is large, and the upgrade can only stop and modify Can't roll back well; distinguish the overall process of software development by stages: the stages are split, incoherent, can't run through the whole software development process well, can't form a unified whole, can't collect and feedback problems well

Images