![]() Reliability, availability, maintainability. Which hardware, operating systems, browsers, and 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? We grouped some of them since the approaches to documenting these requirements overlap and some can’t be estimated without the other ones: Usually, such sources as BABOK list non-functional requirements in an isolated manner. In this article, we’ll cover only the most common types that should make it to your checklist. 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 a behavior of the product. BABOK, one of the main knowledge sources for business analysts, suggests the term non-functional requirements (NFR), which is currently the most common definition. For instance, the ISO/IEC 25000 standards framework defines non-functional requirements as system quality and software quality requirements. If you’ve ever dealt with non-functional requirements, you may know that different sources and guides use different terminology. We’ve already covered different types of software requirements, but this time we’ll focus on non-functional ones, and how to approach and document them. These may be speed, security, reliability, etc. Simply said, a non-functional requirement is a specification that describes the system’s operation capabilities and constraints that enhance its functionality. Be it a website, a mobile or a desktop app, it should have a set of quality attributes to meet end-user needs. Like motorcycles or any kind of machinery, software has its own non-functional requirements. ![]() ![]() While these requirements don’t directly describe the vehicle’s primary function - delivering a person from point A to point B - they are still important to satisfy your needs as the driver. What features do you have in mind? Do you expect it to travel at high speed of 170 miles per hour and not to fall apart? Can you attach a sidecar to it or expand luggage space by attaching a pull-behind trailer? And let’s not forget about security systems. ![]()
0 Comments
Leave a Reply. |