Test-driven Requirement Analysis-requirement document review example

Links to related articles are as follows:

Microsoft bridge problem and testing personnel literacy

New Equivalence Method Solution

NP problems in Test Case Design

View an instance using C/C ++ code

90% programmers cannot write BUG-free binary lookup programs?

Requirement document review instanceThe quality of software development documents can only be guaranteed through review. How to effectively discover problems in documents is a headache for many people. First, let's take a look at the requirements for log files as follows: "The software must record all visitors, each access request must record the access start time, access End Time, and IP address of the visitor as a log record. An access record log file must be generated every day on a daily basis ." In this requirement description, if you want to discover problems, you must first imagine that you are a Log Module developer. Based on this requirement description, can you develop a log module? The information to be recorded in the log file is mentioned above: Access start time, end time, and IP address. The first day seems to be able to be developed according to this requirement description. If you use elemental analysis to analyze this demand, you will find that it is not as optimistic as you think. First, find out the three explicit elements involved in the requirement: n visitors n access records n log files. First, analyze the two elements, visitor and access record. First, check the attributes of the visitor, in addition to the access time and IP address mentioned in the description, what attributes does the visitor have? Obviously, the visitor's access content is the most important attribute. Is it sufficient to only record the access time and the visitor's IP address? What useful information can be analyzed from the log? From the time information, we can only see that there were a large number of visitors during that time, and the Time Distribution of users was obtained. It is difficult to have in-depth analysis on user behavior, only by knowing which content visitors are accessing can they obtain more valuable information. The Web server software records the access URL Information to know the visitor's access content. Therefore, the access record contains information about the access content. From the element of access record, the main attribute of access record is the record format. What format should each record be recorded in? Not described. Experienced developers know that the log record format is a very important issue, because log record analysis generally requires the use of specialized analysis software or write specialized analysis programs for analysis. The primary consideration is how to design a reasonable record format to use existing Log Analysis Software for analysis. Analyze the element of the log file to see the attributes of the log file. First, the log file has the file name, storage location, and file format, file Content, file creation time, file size, File Permission, and other attributes. The Requirement Description describes how to generate a log file every day. Based on the file creation time attribute, the log file is generated 24 hours a day, it is not described from or from. From the file name attribute, the requirement for naming log files is not mentioned. The storage location attribute does not indicate where the log files are stored. Are all log files stored in the same subdirectory of the application? From the perspective of File Format attributes, is the log file stored in text or binary format? What is the format of the file content, and how to separate each access record? Is it separated by carriage return or other characters? No description. Analyze the file content attributes. In addition to the content described above, whether other content can be saved or not. If other content cannot be saved, in the Requirement Description, add the following sentence: "access record information can only be stored in log files, and other record information cannot be stored ". Is there a limit on the size of a log file based on the file size attribute? If there are a lot of access requests during the peak hours of a day, whether to split the log files into multiple ones is an issue that needs to be considered. Based on the analysis of File Permission attributes, can all users on the machine access log files or only specific users access log files? Whether to set permissions for a file is an issue that needs to be considered. Therefore, after analyzing the above requirement description through the element analysis method, you will find that many problems in the requirement description are not clearly described. Some people may wonder if the workload will be too heavy if all the questions mentioned above are described? From the perspective of requirement analysis, if the requirement specification is described in detail, it will increase a lot of work, but from the perspective of the entire development process, if the requirement description is complete, there is little possibility of ambiguity and omission in the development of the subsequent stages. In fact, the time saved in the subsequent stages will greatly exceed the time needed. In fact, we should not only use the test case design method when reviewing requirements, but also adopt the test case design to drive demand analysis, that is, design the test case during the design process, use test case design to drive demand analysis and improve the content of demand analysis.