Read the note: Ten Steps to software requirements (iii)

The purpose of verifying the software requirements is to ensure the completeness and correctness of the results of the requirements analysis, and to ensure that software products developed by the software are required by the users. The importance of software requirements validation is the discovery of problems in the repair requirements analysis. The main work of software requirements verification is self-verification, user verification, system verification, technical verification, expert verification, mainly in the form of a review will be carried out to collect opinions from all sides to be amended. The problem of requirement verification is still in the stage of artificial detection, which is not enough attention to the verification work. At present, the existing problems in the method of verification, a lot of also rely on artificial detection, which for the current large data volume service is not enough, the operability is not too high. We would like to say that this situation, there is no other way? I think there is still, that is, in the validation of the content to make the request. The first is the validation of the verification content, then the verification of the system, it must be conducted on the basis of business research results verification, and second, in the demand analysis to the business and system functions to quantify the analysis, such as the frequency of business, the input/output data flow per business, the communication capacity of the system, request the corresponding ability.

The hypothetical method in formal logic is a way of coping with changes, making corresponding assumptions and logical adjustments according to expected changes and own views, and can do more in the early stages of development, group discussions to determine the corresponding changes, and make logical assumptions to reduce the corresponding errors. In order to avoid the ambiguity of programming software, the logic judgment will guess the expectation, thus avoiding the two semantics of the software. Emphasize the completeness of software requirements, like only the world, can transform the world, can not understand how to transform? Integrating business and software together, the business system is composed of the physical world people and people, the interaction between people and objects, the software system is composed of the information World code and the device carrier of the physical world and the information interaction of the people, which embodies the importance of the business research and the primary.

"Software requirement verification is a means of software requirements risk control, we should use the verification method based on engineering experience with caution." "In addition to the manual validation of the software requirements analysis, I think we should also test the results of the analysis to verify that if it is a global

, then the test should be focused, targeted based on the known results as a reference to detect. Testing is one of the criteria for verifying truth, and it is also the basis of judging the result. Manual method by writing system function test trial example, with

Test cases are checked against requirements analysis results to identify problems in the requirements analysis that can only be tested for functional correctness. Machine testing is a similar way of building prototypes, but unlike artificial methods, machines

Test is to simulate a running environment on the simulation system to test, not only can measure the logical correctness of the system function, but also can give the relevant parameters of the system performance.

The software requirement is the abstraction of the future software system on the basis of the abstraction of the reality visible business, and the software system is only the result that the re-abstraction of the future software system is materialized in the information world. At first, the remark was somewhat obscure,

Easy to understand, but think about it really, the business is just abstract in the physical world, software systems are just abstract in the information world, so business and software systems also have a considerable commonality. The book often mentions a

Example: Copernicus proposed "heliocentric" before people are now "geocentric" this circle, and software requirements since is CHOUFSO, it is bold to make software requirements become the center of the entire development activities. A lot of software projects fail, and the reasons for failure are mostly attributed to demand. Demand is CHOUFSO, some people think it is not good, but I think CHOUFSO is a good thing, it is important to explain it. Afterwards Choufso is indifferent, in the matter Choufso is beneficial. The author bases on the center and

The relationship model of the dots makes a bold analogy, and the CHOUFSO needs analysis as the center of the software development ring, then the relational models of the software development activities will be as expected.

From "light business, heavy system" to "heavy business, heavy system" is the important concept of the new generation of software requirements engineering. Because the phenomenon of "light business, heavy system" is always unavoidable in the relative traditional demand analysis work, especially workmanship

The software projects of the class and framework are especially important, while the software development activities of the management system also pay more attention to some business. While it is common for people who are involved in demand analysis to be in a position where business needs are primarily the responsibility of the client, the main job of the demand analyst is to translate the user-described business into user requirements and system requirements.

Read the note: Ten Steps to software requirements (iii)