Chapter 11 Non-Functional Requirements by Hassan
Non-Functional Requirements
Non-Functional Requirements can be generalized as "what a
product/system is supposed to be. these requirements tend to be qualities that
the product should have and they should specify how well the product does what
it does. the requirements should either make the product usable, fast,
reliable, attractive or safe and they should describe the character/ the way
the functions should behave.
Look and Feel Requirements
the look and feel requirements are key to
the non-functional requirements and as a BA one must consider them for every
project. These requirements can describe how a product/system's desired
appearance, mood, spirit or overall style/ appearance. The look and feel
requirements can further specify what the product/system intends to appear as
and is not a detailed design of the product/system itself. The typical look and
feel requirement should be simple to use, professional looking, attractive to
its market, consistent with previous product branding as well as other things.
An example of a look and feel requirement would be " The product should
comply with corporate branding standards."
Usability and Humanity Requirements.
The usability requirement can often be
left out of the final list of requirements because of the assumption that the
designer of the system/product would design a product/system that wouldn't be
hard to use generally, but the truth is that the usability of the
system/product could be a key factor. it is not safe to assume that the product
will be usable. This requirement asks the question; "Who will use this
product". This question is asked because what we can assume to be usable
for a 15 year old boy will not be the same as what is usable for a 60 year old
mother. This requirement can affect efficiency, error rates, productivity and
overall acceptance of the new system/product.
Performance Requirements
Performance requirements should be used
when a product/system needs to do a task or tasks in a specific amount of time.
Performance requirements should consider the speed to complete a task, the
ranges of allowable values, the volumes that the product shall hold, the
accuracy of the results and the efficiency of resources being used. other
considerations should be how fast the product or system should be also how
strong and big they should be.
Security Requirements
The security requirement is one of the
most important but also one of the most difficult of the non-functional
requirements to specify. This requirement could use a security expert to
help and maintain protection from malware and other kinds of internet viruses
and data breaches, if not correctly done the security requirement can pose a
significant risk to the product/system. There are three main aspects to the
security requirement: Access, Privacy, and integrity.
This comment has been removed by the author.
ReplyDeleteThanks for providing this useful information. In addition to security purposes the number of incident such as data hacking, data leakage is increasing in these days. The companies are now investing more and more money to safely secure their data. In the past, security concerns were basically around network infrastructure layers. Currently, due to the growing use of networks and the Internet concept dominance, such as cloud computing, Software as a Service, serious vulnerabilities are being discovered by attackers in the application layer. Therefore, the concept of application security layer emerged as an essential task in the development process.
ReplyDeleteVery good information about no-functional requirements. Before working on identifying the requirements is very important to clearly understand the difference between the functional and no-functional requirements. Non-functional requirements are the ones that do not alter the product’s essential functionality. So the functional requirements remain the same no matter which properties you attach on them.
ReplyDeleteThis is great information about different type of non functional requirements. For our Scotia Pay app, it's non functional requirement will be that Scotia pay app should be displayed in white and red just like the Scotiabank logo and this requirement is type of look and feel requirements. Due to classification of various non functional requirements, it become more clear that how non functional requirements relate to product and how these are different from functional requirements.
ReplyDeleteThanks to have these information which is very helpful but Adding to more, Performance requirements are written when your product needs to carry out a few responsibilities in a given quantity of time, a few obligations need to be done to a unique level of accuracy, or the product wishes to have positive information garage capacity, or it has to attain a certain volume of throughput.
ReplyDeleteOperational necessities specify what the product has to do if it's miles to function effectively in its surroundings. In some cases the operating surroundings creates special circumstances that have an impact on the manner the product must be constructed.