Non-functional requirements refer to requirements that are hidden behind functional requirements and that need to be considered in development, also known as "cross-functional requirements". In the past few years of work, the most common scene is that bulk sms service QA partners are chasing developers and reporting bugs in the office. Sometimes developers will be unhappy, "I didn't say XXX at that time, but XXX." It seems that QA partners are always more attentive than developers. Even if the unit test coverage reaches 80%, QA can still find problems by changing methods. A large part of the reason for this comes from the "requirements behind the requirements", which the BA and QA partners think you have considered, or the default development needs to be considered. For example, the requirement of a new article in the CMS system is unlikely to be an AC (Acceptance bulk sms service Criteria) that needs to prevent the form from being submitted twice. However, if no one proposes it, who will know? (Recently hot iceberg map) Finally, QA or online users will tell us by reporting bugs.
We call these requirements that are hidden behind functional requirements or that BA defaults to consider for development as non-functional bulk sms service requirements, sometimes called cross-functional requirements. Let's talk about the common non-functional requirements and coping methods at work. 1. Interactive experience related Loading The loading state is one of the most easily overlooked requirements, especially in the current rich client development mode, data acquisition is asynchronously loaded. If you forget to consider this requirement, you will experience flickering when the network conditions are good, and appear to be stuttered and unresponsive when the network conditions are poor. To achieve unified Loading, you can add interceptors to the front-end network request bulk sms service library, but you need to pay attention to using a counter to keep the Loading icon in the middle of multiple network requests without interruption, otherwise there will be a flickering problem.
Secondary submission of the form Some QAs use extreme testing methods, such as quickly clicking a button multiple times, and triggering multiple form bulk sms service submissions if the page is not processed. Even if the backend API increases the limit, there may be both success and failure prompts, which will confuse users even more. There are several ways to deal with this problem: Using the masked Loading will have the effect of blocking the user's operation. Disable form events after click or programmatically increase state in request Depends on the backend to configure a one-time form token (usually used to prevent CRSF) 2. Output formatting The requirements generally tell the bulk sms service development how to display the data, but often forget how to format the data. For example, we want the numbers to be separated by thousands or other display methods to make the numbers less difficult to read;