Application Requirement

Introduction

The requirements should not to be too excessive. For now, make sure to take the absolute minimum set of requirements. Not the things that "nice to have" and optional. Just the minimum requirements for the minimum viable product.

It's okay to not have a complete requirements in the beginning. The requirements can always be changed as the project development grows.

Take note that, the requirements should not contain anything related with classes, object orientation yet for this stage.

To show how the system requirements works, let's have an imaginary application idea that we want to build.

Example Application ⇒ Restaurant Reservation and Food Delivery Application

FURPS+ Requirements

One of the most commonly used model is acronym FURPS+. The FURPS+ requirement can fulfilled the functional and non functional requirements of an application.

Functionality ⇒ Capability, Reusability, Security (main features of an app)
Usability ⇒ Human Factors, Aesthetics, Consistency, Documentation (affects the user)
Reliability ⇒ Availability, Failure Rate & Duration, Predictability
Performance ⇒ Speed, Efficiency, Resource Consumption, Scalability
Supportability ⇒ Testability, Extensibility, Serviceability, Configurability
Design (the system design)
Implementation (how to implement the system)
Interface (the interface of internal system)
Physical (hardware and physical constraints)

Functional Requirements

The functional requirements should describes "what the application must do".
The requirements should start with:

The system must do...
The application must do...

Examples:

Allow customers to reserve a table in the restaurant before they arrived.
Allow customers to go through the menu list
Show the date availability for reservation
Show the menu availability and prices
Have the menu category
Have options for dine in, take away or delivery
Allow customers to have their account in the system
Allow customers to save any menu they want
Allow customers to view the detail and progress of food delivery
Allow customers to view the reservation details
Allow customers to change the reservation
Allow customers to cancel the reservation
Have contact section

Non-Functional Requirements

The non functional requirements should describes, maintainability, reliability, usability and availability.
So, each non functional requirements should start with:

The application should be...

Examples:

Accessible from mobile and desktop
User friendly and responsive
Available during peak hours (lunch and dinner)

Conclusion

These requirements might not be the final one and can always be changed in the future. But at least, start writing some requirements before doing anything so that you know what you want to develop later on.

The next steps will be creating Use Cases and User Stories to refine the requirements a little bit more before start designing and developing anything.

Anyway, hope this article give some useful information to you. I'm still learning and will continue creating article here so that I really understand what I'm currently learning.

If something not right in this article, please comment below so that I learn some new stuff to improve my skill.

Thank you for reading my article.