Author Topic: What are the Non Functional Requirements  (Read 9374 times)

1200474101

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: What are the Non Functional Requirements
« Reply #60 on: April 01, 2020, 01:30:45 pm »
Non Functional Requirement: As the name says, so is the meaning. When a functionality tends to be a feature of the application, the opposite being non-functional can be termed as focusing on functionality's behavior.
When every functional requirement says, "action" to be done, while every non-functional requirement defines the quality to be delivered of that functionality.
For ex: We have a functionality, "Admin should be able to view all the orders in the system"
Some non-functionality requirements samples could be,
1) Performance - In what time should the system take to load the data?
2) Usability - Is the screen usable enough for the end user?
3) Security - How secured are we in showing the customer data?

Usually, the non-functional requirements would be defined by client or in some organizations, they define a standard for themselves and follow them.

1192167712

  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: What are the Non Functional Requirements
« Reply #61 on: May 19, 2020, 10:32:59 am »
A non-functional requirement describes a feature or trait that a business solution must have, but that is not directly related to the core business functions of the solution.

1200684702

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: What are the Non Functional Requirements
« Reply #62 on: May 22, 2020, 02:19:43 pm »
A non-functional requirement is a specification that depicts the system’s operation capabilities and constraints which would enhance its functionality.
common types are:
Performance and scalability,
Reliability,
availability,
maintainability,
Security,
Localisation,
usability,
Portability & compatibility,

1192168812

  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Non Functional Requirements
« Reply #63 on: May 29, 2020, 12:43:25 pm »
Basically, non-functional requirements relate to qualities of the system that cut across user-facing features, such as security, reliability, and performance. Non-functional is probably a bad name because it sounds like these requirements are intangible, simply properties of a static system. However, these requirements do affect the function of the system and it is possible to design tests that these qualities are present.

The difference from functional requirements is that these qualities must be present throughout the system rather than delivered in a one-shot like a user-facing feature. Alternative terms for non-functional requirements are "constraints", "quality attributes", "quality goals" and "quality of service requirements" but let’s stick to calling them "non-functional requirements" (NFR) for now. So they have to be considered in every development cycle and factored into our test strategy.

NFR can be grouped into:

Execution qualities, such as security and usability, which are observable at run time.
Evolution qualities, such as testability, maintainability, extensibility, and scalability, which are embodied in the static structure of the software system.

1202990202

  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: What are the Non Functional Requirements
« Reply #64 on: May 30, 2020, 11:20:16 am »
Nonfunctional Requirements define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system.