Shulou(Shulou.com)06/03 Report--

Software requirements are extremely important for software development and testing. The report of American Standish Group company shows that more than 60% of the failed and delayed projects are caused by demand-related problems, and the requirements here include many aspects, among which the "performance requirements" can not be ignored. The quality of performance testing requirements directly affects the effect of performance testing. Inaccurate analysis of performance requirements will make it difficult to achieve the desired results of users even if the follow-up work goes smoothly.

Performance requirements are so important that how to obtain performance requirements is particularly critical. Next, we will introduce readers to what performance requirements are and the various ways to obtain them, especially the "method of obtaining requirements through server logs". The purpose of this paper is to enable readers to understand the performance requirements and sources, to master the methods of obtaining requirements through server logs, and to master the use of WebLog Expert tools and result analysis methods.

What are performance requirements?

Performance requirements can be divided into implicit performance requirements and explicit performance requirements. Implicit performance requirements are usually put forward by ordinary customers, who often do not understand the performance indicators and cannot clearly put forward the specific performance requirements, so this kind of requirements require the demand personnel to use a reasonable way to help the customers define the demand indicators. Even need the developer to provide the demand index, and then confirm it by the customer. Therefore, the implicit performance requirements need to be carefully analyzed by readers combined with the actual situation, and finally get the explicit performance requirements. Explicit performance requirements are generally put forward by professional customers, who often have their own development departments and testing teams. they are very clear about the distribution of the system's processing traffic and can clearly point out the goals that the system should achieve. Obviously, such requirements are more clear. It is worth mentioning that, objectively speaking, most of the customers we encounter are ordinary customers.

The following is explained with examples to make people more aware of these two types of performance requirements.

1) Hidden demand example: "the width of the entrance and exit staircase of an auditorium should be appropriate to avoid congestion" this demand seems to be a functional restriction, in fact, it also has a restriction on performance. Specifically, if the construction of the entrance and exit staircase is too narrow, it may lead to crowding or even accidents, while the construction of too wide is bound to lead to a waste of resources. The "appropriate evacuation flow capacity" required by users is essentially the throughput index to measure the processing capacity in the performance test, that is, there is an implicit performance requirement of "throughput" in the above requirements.

To cite another example, users propose that "Discuz forums will process posts as fast as xxx forums, allowing a large number of users to post at the same time without failure", which is also an implicit performance requirement.

2) examples of explicit requirements: the following is still using the Discuz forum to demonstrate explicit performance requirements.

Discuz Forum is 10% faster in processing posts than the previous version.

Discuz can handle 10000 posts per day.

Discuz login operation response time

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.