Scribd
Upload
672 views2 pages

Non Functional Requirements

This document discusses non-functional requirements which define quality attributes of a software system rather than specific functions. Non-functional requirements are essential to ensure usability and effectiveness. They allow constraints to be imposed on the system design across agile backlogs. Examples given are load time and simultaneous user thresholds. Describing non-functional requirements is as critical as functional requirements.

Uploaded by

orbit projects
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
672 views2 pages

Non Functional Requirements

This document discusses non-functional requirements which define quality attributes of a software system rather than specific functions. Non-functional requirements are essential to ensure usability and effectiveness. They allow constraints to be imposed on the system design across agile backlogs. Examples given are load time and simultaneous user thresholds. Describing non-functional requirements is as critical as functional requirements.

Uploaded by

orbit projects
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Non Functional Requirements

A non-functional requirement defines the quality attribute of a software system. They represent a
set of standards used to judge the specific operation of a system. Example, how fast does the
website load?

A non-functional requirement is essential to ensure the usability and effectiveness of the entire
software system. Failing to meet non-functional requirements can result in systems that fail to
satisfy user needs.

Non-functional Requirements allows you to impose constraints or restrictions on the design of


the system across the various agile backlogs. Example, the site should load in 3 seconds when
the number of simultaneous users are > 10000. Description of non-functional requirements is just
as critical as a functional requirement.

Usability
The system is designed with completely automated process hence there is no or less user
intervention.
Reliability
The system is more reliable because of the qualities that are inherited from the chosen platform
java. The code built by using java is more reliable.
Performance
This system is developing in the high level languages and using the advanced front-end and
back-end technologies it will give response to the end user on client system with in very less
time.
Supportability
The system is designed to be the cross platform supportable. The system is supported on a wide
range of hardware and any software platform, which is having JVM, built into the system.
Implementation
The system is implemented in web environment using struts framework. The apache tomcat is
used as the web server and windows xp professional is used as the platform.
Interface the user interface is based on Struts provides HTML Tag.
Difference Between Functional Requirement and Non-Functional Requirement

Parameters Functional Requirement Non-Functional Requirement


It is mandatory
Requirement It is non-mandatory

Capturing type It is captured in use case. It is captured as a quality attribute.


Product feature Product properties
End-result

Easy to capture Hard to capture


Capturing

Helps you verify the Helps you to verify the performance of


Objective
functionality of the software. the software.
Area of focus Focus on user requirement Concentrates on the user's expectation.
Documentation Describe what the product does Describes how the product works
Functional Testing like System, Non-Functional Testing like
Type of Testing Integration, End to End, API Performance, Stress, Usability, Security
testing, etc. testing, etc.
Test Execution is done before
Test Execution After the functional testing
non-functional testing.
Product Features
Product Info Product Properties

Functional Requirements :-

Modify Modules as a functional requiremtns

You might also like