Scribd
Upload
70 views2 pages

Requirement Analysis

Requirements analysis is critical for assessing the success of a software project. There are two types of requirements: functional and non-functional. Functional requirements define what the system should do and are specified by users. Non-functional requirements define quality attributes and place constraints on how the system should fulfill functional requirements; they are specified by technical teams and deal with issues like portability, security, and performance. The differences between functional and non-functional requirements include what they define, who specifies them, and how they are tested.

Uploaded by

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

Requirement Analysis

Requirements analysis is critical for assessing the success of a software project. There are two types of requirements: functional and non-functional. Functional requirements define what the system should do and are specified by users. Non-functional requirements define quality attributes and place constraints on how the system should fulfill functional requirements; they are specified by technical teams and deal with issues like portability, security, and performance. The differences between functional and non-functional requirements include what they define, who specifies them, and how they are tested.

Uploaded by

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

Requirements analysis is very critical process that enables the success of a system or software

project to be assessed. Requirements are generally split into two types: Functional and Non-
functional requirements.
Functional Requirements: These are the requirements that the end user specifically demands
as basic facilities that the system should offer. All these functionalities need to be necessarily
incorporated into the system as a part of the contract. These are represented or stated in the form
of input to be given to the system, the operation performed, and the output expected. They are
basically the requirements stated by the user which one can see directly in the final product, unlike
the non-functional requirements.
Non-functional requirements: These are basically the quality constraints that the system must
satisfy according to the project contract. The priority or extent to which these factors are
implemented varies from one project to other. They are also called non-behavioral requirements.
They basically deal with issues like:

• Portability
• Security
• Maintainability
• Reliability
• Scalability
• Performance
• Reusability
• Flexibility
Following are the differences between Functional and Non Functional Requirements

Functional Requirements Non Functional Requirements

A non-functional requirement defines


A functional requirement defines a the quality attribute of a software
system or its component. system.

It places constraints on “How should


It specifies “What should the the software system fulfill the
software system do?” functional requirements?”

Non-functional requirement is
specified by technical peoples e.g.
Functional requirement is specified Architect, Technical leaders and
by User. software developers.
Functional Requirements Non Functional Requirements

It is mandatory. It is not mandatory.

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

Defined at a component level. Applied to a system as a whole.

Helps you verify the functionality of Helps you to verify the performance
the software. of the software.

Functional Testing like System, Non-Functional Testing like


Integration, End to End, API testing, Performance, Usability, Security
etc are done. testing, etc are done.

Usually easy to define. Usually more difficult to define.

Example Example
1) Authentication of user whenever 1) Emails should be sent with a
he/she logs into the system. latency of no greater than 12 hours
2) System shutdown in case of a from such an activity.
cyber attack. 2) The processing of each request
3) A Verification email is sent to should be done within 10 seconds
user whenever he/she registers for 3) The site should load in 3 seconds
the first time on some software when the number of simultaneous
system. users are > 10000

You might also like