Is the system compatible with local specifics? How well are the system and its data protected against attacks? How often does the system experience critical failures? How much time does it take to fix the issue when it arises? And how is user availability time compared to downtime? Reliability, maintainability, availability. Which hardware, operating systems, and browsers, along with their versions does the software run on? Does it conflict with other applications and processes within these environments? How fast does the system return results? How much will this performance change with higher workloads? But there are quite a few types of non-functional requirements that can make it to your checklist too. The most common ones are performance, scalability, portability, compatibility, reliability, availability, maintainability, security, localization, and usability. What are the key types of non-functional requirements? Or you may have additional compliance requirements if you process payments. In some cases, this may not be relevant to you. For instance, if you intend to collect any user data and your website operates in the EU, you must meet GDPR compliance rules. And, frankly, it may differ for different products. The list of them also varies depending on the source. Nevertheless, these designations consider the same type of matter – the requirements that describe operational qualities rather than the behavior of the product. For instance, the ISO/IEC 25000 standards framework defines non-functional requirements as system quality and software quality requirements.īABOK, one of the main knowledge sources for business analysts, suggests the term non-functional requirements (NFR), which is currently the most common definition. If you’ve ever dealt with non-functional requirements, you may know that different sources and guides use different terminology. If you need a general recap on software documentation and planning, check out our video. This time we’ll focus on non-functional ones, provide examples, and explain how to approach and document them. We’ve already covered different types of software requirements as well as written a detailed post on the differences between functional and non- functional requirements. Continuing our messaging platform example, a non-functional requirement can be the speed with which a system must perform editing to satisfy user expectations, “The message must be updated for all users in a chat within 0.1 seconds, given that all users are online and have LTE connection or better.”
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |