Software Quality

What are Functional & Non-Functional Requirements?

When gathering requirements for software application/module development, requirements gathering remain as one of the key challenges for stakeholders at different levels including project manager, tech lead, software developers and test engineers. Interestingly, due to inefficient requirement gathering, most of the project fails.

Following is definition of functional requirements as per wikipedia:

In software engineering, a functional requirement defines a function of a software system or its component. A function is described as a set of inputs, the behavior, and outputs (see also software). Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish. Read further here.

Following is definition of non-functional requirements as per wikipedia:

In systems engineering and requirements engineering, a non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. Read further here.

Software requirements shall be gathered keeping in mind following:

  • Stated needs: There are requirements that are specifically mentioned at the time of requirements gathering.
  • Implied needs: These represent the requirements which are implicit and need to be confirmed with the end customers.

Requirements can be gathered keeping in mind following aspects of software quality:

  1. Functional suitability: This is covered under functional requirements.
  2. Maintainability: This is covered under non-functional requirements.
  3. Efficiency: This is covered under non-functional requirements.
  4. Security: This is mostly covered under non-functional requirement. However, at times, this also forms part of functional requirements.
  5. Reliability: Non-functional
  6. Usability (or Operability): Non-functional
  7. Compatibility: Non-functional
  8. Portability: Non-functional

If one sees above, its makes much more important for both, software and the test engineers have clear understanding about all the non-functional characteristic of software to be able to deliver software that can match or exceed customer satisfaction and achieve “customer delight”.

Ajitesh Kumar

I have been recently working in the area of Data analytics including Data Science and Machine Learning / Deep Learning. I am also passionate about different technologies including programming languages such as Java/JEE, Javascript, Python, R, Julia, etc, and technologies such as Blockchain, mobile computing, cloud-native technologies, application security, cloud computing platforms, big data, etc. I would love to connect with you on Linkedin. Check out my latest book titled as First Principles Thinking: Building winning products using first principles thinking.

Share
Published by
Ajitesh Kumar

Recent Posts

Agentic Reasoning Design Patterns in AI: Examples

In recent years, artificial intelligence (AI) has evolved to include more sophisticated and capable agents,…

1 month ago

LLMs for Adaptive Learning & Personalized Education

Adaptive learning helps in tailoring learning experiences to fit the unique needs of each student.…

2 months ago

Sparse Mixture of Experts (MoE) Models: Examples

With the increasing demand for more powerful machine learning (ML) systems that can handle diverse…

2 months ago

Anxiety Disorder Detection & Machine Learning Techniques

Anxiety is a common mental health condition that affects millions of people around the world.…

2 months ago

Confounder Features & Machine Learning Models: Examples

In machine learning, confounder features or variables can significantly affect the accuracy and validity of…

2 months ago

Credit Card Fraud Detection & Machine Learning

Last updated: 26 Sept, 2024 Credit card fraud detection is a major concern for credit…

2 months ago