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:
- Software Engineering | Classification of Software Requirements
- Software Engineering | Requirements Engineering Process
- Software Engineering | Requirements Elicitation
- Software Engineering | Challenges in eliciting requirements
- Software Engineering | Requirements Validation Techniques
- Software Testing | Non-functional Testing
- Software Engineering | Functional Point (FP) Analysis
- Software Testing | Functional Testing
- Differences between Functional and Non-functional Testing
- Requirements and feature of Good Prototyping CASE tool
- Different Sources of Understanding Software Requirements
- Functional Modelling in object oriented analysis and design
- Functional modeling and Information Flow modeling
- Non-functional Requirements in Software Engineering
Following are the differences between Functional and Non Functional Requirements
|Functional Requirements||Non Functional Requirements|
|A functional requirement defines a system or its component.||A non-functional requirement defines the quality attribute of a software system.|
|It specifies “What should the software system do?”||It places constraints on “How should the software system fulfill the functional requirements?”|
|Functional requirement is specified by User.||Non-functional requirement is specified by technical peoples e.g. Architect, Technical leaders and software developers.|
|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 the software.||Helps you to verify the performance of the software.|
|Functional Testing like System, Integration, End to End, API testing, etc are done.||Non-Functional Testing like Performance, Stress, Usability, Security testing, etc are done.|
|Usually easy to define.||Usually more difficult to define.|
1) Authentication of user whenever he/she logs into the system.
1) Emails should be sent with a latency of no greater than 12 hours from such an activity.
Don’t stop now and take your learning to the next level. Learn all the important concepts of Data Structures and Algorithms with the help of the most trusted course: DSA Self Paced. Become industry ready at a student-friendly price.
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.