Efficiency. Efficiency is indicative of how effectively the system uses processor performance, disk space, memory, or connection bandwidth. Efficiency is related to performance, a class of non-functional requirements. If the system spends too much available resources, users will see a decline in performance – a visible indicator of its inefficiency. Insufficient performance annoys users who wait for the result of the query on the database to be displayed. Besides, performance problems also compromise security, for example, if the real-time monitoring system is overloaded. Determine the minimum equipment configuration, with the help of which you can achieve the specified efficiency, throughput and performance. To make it possible to use the lower limit in case of unforeseen conditions and determine the subsequent growth, you can use this wording:
Efficiency-1, at least 25% of processor bandwidth and the RAM available to the application should not be used in the planned peak load conditions.
Typical users do not formulate performance requirements in such technical terms. The most that they are capable of is to mention the response time or amount of the occupied disk space. The analyst’s task is to ask questions that will define the users’ expectations as to decline in performance, possible peak loads and expected growth. Stress testing services help to verify performance of digital products under peak loads. If the expectations are not met, the necessary work is done to improve stability and effectiveness of apps under test.
Haste makes waste
One large corporation developed a sophisticated graphic store model for their e-business components. The buyer could visit the e-store on the website, view the services offered and purchase various products. The graphics were great, the model – of high-quality, but the performance was terrible. The user interface worked perfectly for developers who used a high-speed Internet connection with local servers. Unfortunately, with standard modem connections at 14.4 or 28.8 kbps, which at that time were used by most users, huge image files were loaded incredibly slowly.
All beta testers lost interest in the site even before the main page had time to be fully loaded. Fascinated by the graphic model, the developers did not think about the limitations of the operating environment, efficiency and performance requirements. It was necessary to abandon this decision after its completion – an expensive lesson, which confirmed the importance of discussing the attributes of software quality at the beginning of the project.
Add Comment