Business variable-oriented software development scheme generation method

Abstract

The invention provides an accurate demand design and demand analysis-based business variable-oriented software development scheme generation method. The method comprises an accurate system function demand design and demand analysis stage, an accurate software function demand design and demand analysis stage, and an accurate function demand design and demand analysis stage. In the accurate system function demand design and demand analysis stage, function demands are divided into multiple function units according to original system function demand information of a user; a corresponding businesslogic variable is matched for each function unit; a corresponding discrete event is established according to the business logic variable, wherein the discrete event is used for triggering change of the business logic variable; and according to the discrete event, a demand function of the business logic variable is defined. In the accurate software function demand design and demand analysis stage,a business physical variable for realizing the business logic variable is established; and a demand function of the business physical variable is defined. In the accurate function demand design and demand analysis stage, combinations of function input parameter control contents and business physical variable control contents are established, change laws for business physical variable contents in combination groups are established, and output is performed.

Description

technical field

[0001] The invention relates to the technical field of software development engineering, in particular to a method for generating a business variable-oriented software development scheme. Background technique

[0002] Software development is a system engineering including requirements capture, requirements analysis, design, implementation and testing. At present, the most widely used software development tool on the market is the UML tool that adopts the object-oriented design method, but this tool has the following shortcomings: 1. It complicates the problem, that is, users and designers at the system level do not need to see things such as "class "With such a concept, users and designers do not need to care whether the system is implemented using a structure-oriented method or an object-oriented method. If these factors are considered, it will undoubtedly complicate the requirements analysis; 2. Although modeling is emphasized, both There are still static ...

Images