Meaning of Requirement
What is Requirement:
A requirement is a necessary condition to have access to something, or for a thing to happen. The word requirement comes from Latin requisitum, which means to pretend or require something.
The requirements can be tangible (have a car, deliver certain documentation, sign a contract, etc.) or intangible (good appearance, responsibility, punctuality).
On the other hand, the requirements can be of a natural nature (for example, it is an essential condition that most plants receive sunlight to be able to photosynthesize) or cultural.
In the case of the requirements imposed by cultural or social norms, these can be changing, since they depend on what each social group has established, but they can also vary according to the time, the historical context, political or legal changes, etc.
For example, the legal requirements to get married vary from country to country, but they can also change over time.
Requirement in informatics
In systems engineering, a requirement is a piece of information that is necessary in the design phase of a product. In this case, the requirements dictate the rule on what the product to be created must execute.
A requirement, in this case, also refers to a condition that the user must meet in order to run something on the system.
There are 2 types of requirements in systems engineering:
It is a description of something that the system should execute. In other words, without this requirement, the system cannot fulfill its task.
It is a condition that the system must meet in order to function properly. For example, maintenance requirements, performance requirements, etc.
As the requirements describe essential guidelines or conditions in the system, their writing must comply with certain standards so that their subsequent execution is carried out correctly.
- They must be concrete, as they have to explain what the system should run, but at the same time avoid unnecessary details.
- They have to be consistent: the requirements cannot conflict with each other. That is, when the system executes a requirement, it cannot affect the application of other conditions.
- Its wording must be complete, since no other document should be used for more information.
- The requirements have to be clearly explained, leaving no room for interpretation.
- All system conditions have to be achievable, realistic.
- The requirements have to be verifiable. In this way, it can be ascertained whether they are indeed applicable or not. Verification methods must also be described.