In this article, we explore the important non functional requirement called Portability.
What you will learn
- What are non functional requirements?
- Why are non functional requirements important?
- What are the different kinds of non functional requirements?
- How do you ensure that you adhere to non functional requirements?
- What are the best practices in implementing non functional requirements?
Non Functional Requirements and Microservices
This is the first article in a series of articles on Non Functional Requirements:
- 1 - Microservices Architectures - Non Functional Requirements
- 2 - Security
- 3 - Web Application Security And OWASP - Top Ten Security Flaws
- 4 - Maintainability
- 5 - Scalability
- 6 - Performance
- 7 - Reusability
- 8 - Reliability
- 9 - Modularity
- 10 - Availability
- 11 - Portability
What are Non Functional Requirements?
In this article, we focus on the most important non functional requirements and why there are needed.
What Are Non Functional Requirements?
Whenever you talk to a user who needs a web interface, he will mainly describe what needs to happen when the page loads, what it needs to look like, and what should happen when a button on it is clicked. These are the application’s functional requirements.
There is also one other set of requirements that users might not typically specify. For instance:
- You need to page to load up within 2 seconds (Performance)
- You require the application to support up to 100,000 concurrent users (Scalability)
- It should be easy to extend the functionality of the application (Maintainability)
There come under the category of non functional requirements.
As a developer, it is very important that you give due attention to these as well.
Categories Of Non Functional Requirements
Following are some of the important non functional requirements:
- Authentication & Authorization
Adhering To Best Practices
It is important to adhere to a few best practices, when it comes to implementing the non functional requirements. Here is a list of the most important practices.
- Have clearly stated non functional requirements
- Build vertical slices wherever possible, with a view to eliminating non functional risks such as scalability and performance.
- Make sure that the framework used in your application is able to withstand a particular load.
- Check for compliance to security requirements right from the project inception stage.
- Perform static analysis of the code right from project inception.
- Use Secure Code static analysis tools right from the start of the project.
Do check out our video on this:
In this article, we discovered what non functional requirements are, and how they are different from the functional requirements. We had a brief look at the types of non functional requirements. Finally, we had a glimpse of the best practices to follow while implementing these requirements.
10 Step Reference Courses
- Spring Framework for Beginners in 10 Steps
- Spring Boot for Beginners in 10 Steps
- Spring MVC in 10 Steps
- JPA and Hibernate in 10 Steps
- Eclipse Tutorial for Beginners in 5 Steps
- Maven Tutorial for Beginners in 5 Steps
- JUnit Tutorial for Beginners in 5 Steps
- Mockito Tutorial for Beginners in 5 Steps
- Complete in28Minutes Course Guide
Top 5 Recommended in28Minutes Courses
in28Minutes is helping 300,000 Learners across the world reach their learning goals. Click here for the complete catalogue of 30 Courses.