Scribd
Upload
43 views2 pages

Any Requirement Which Specifies What The System Should Do.: Functional Requirements

The document discusses functional and non-functional requirements for systems. Functional requirements specify what a system should do, like sending emails or opening accounts. Non-functional requirements specify how a system should perform or behave, such as response time, security, or usability. Some examples of functional requirements include business rules and authentication, while non-functional requirements include performance, reliability, and data integrity. It is important to correctly specify both types of requirements to ensure systems meet expectations.

Uploaded by

ismail
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
43 views2 pages

Any Requirement Which Specifies What The System Should Do.: Functional Requirements

The document discusses functional and non-functional requirements for systems. Functional requirements specify what a system should do, like sending emails or opening accounts. Non-functional requirements specify how a system should perform or behave, such as response time, security, or usability. Some examples of functional requirements include business rules and authentication, while non-functional requirements include performance, reliability, and data integrity. It is important to correctly specify both types of requirements to ensure systems meet expectations.

Uploaded by

ismail
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

Functional requirements

The definition of a functional requirement is:


Any requirement which specifies what the system should do.
In other words, a functional requirement will describe a particular behaviour of
function of the system when certain conditions are met, for example: “Send email
when a new customer signs up” or “Open a new account”.
A functional requirement for an everyday object like a cup would be: “ability to
contain tea or coffee without leaking”.
Typical functional requirements include:
 Business Rules
 Transaction corrections, adjustments and cancellations
 Administrative functions
 Authentication
 Authorization levels
 Audit Tracking
 External Interfaces
 Certification Requirements
 Reporting Requirements
 Historical Data
 Legal or Regulatory Requirements

Non-functional requirements
The definition of a non-functional requirement is:
Any requirement which specifies how the system performs a certain
function.
In other words, a non-functional requirement will describe how a system should
behave and what limits there are on its functionality.
Non-functional requirements generally specify the system’s quality attributes or
characteristics, for example: “ Modified data in a database should be updated for all
users accessing it within 2 seconds.”
A non-functional requirement for the cup mentioned previously would be: “ contain
hot liquid without heating up to more than 45°C”.
Typical non-functional requirements include:
 Performance – for example: response time, throughput, utilization, static
volumetric
 Scalability
 Capacity
 Availability
 Reliability
 Recoverability
 Maintainability
 Serviceability
 Security
 Regulatory
 Manageability
 Environmental
 Data Integrity
 Usability
 Interoperability
It is important to correctly state non-functional requirements since they’ll affect
your users experience when interacting with the system.
One way to prevent missing out on important non -functional requirements is to use
non-functional requirement groups as a guide for listing them d own.This blog
post provides an explanation of each of the four main non -functional requirements
groups and how they are used.

You might also like