Return to Answer

A functional requirement is about what the system shall do. The term "functional" comes from "function" meaning something that takes some input and produces some output.

A non-functional requirement is about how (well) the system shall do what it does. These are usually quality requirements, such as performance, reliability or ease of use, or general technical requirements that apply to the whole system (e.g. standards to be enforces, operating system compatibility, hardware limitations).

You may also be interested in the difference between functional and non-functional requirements.

Your requirement does not tell at all what the system does, but it tells how the system shall do it. It is hence without any doubt a non-functional requirement.

A functional requirement is about what the system shall do. The term "functional" comes from "function" meaning something that takes some input and produces some output.

A non-functional requirement is about how (well) the system shall do what it does. These are usually quality requirements, such as performance, reliability or ease of use, or general technical requirements that apply to the whole system (e.g. standards to be enforces, operating system compatibility, hardware limitations).

You may also be interested in the difference between functional and non-functional requirements.

Your requirement does not tell at all what the system does, but it tells how the system shall do it. It is hence without any doubt a non-functional requirement.

Edit: As you can see in the comments, it would be advisable to rephrase your non-functional requirement in order to make it objective, less ambiguous, and verifiable.

A functional requirement is about what the system shall do. The term "functional" comes from "function" meaning something that takes some input and produces some output.

A non-functional requirement is about how well the system shall do what it does. These are usually quality requirements, such as performance, reliability or ease of use.

Your requirement does not tell at all what the system does, but it tells how the system shall do it. It is hence without any doubt a non-functional requirement.

A functional requirement is about what the system shall do. The term "functional" comes from "function" meaning something that takes some input and produces some output.

A non-functional requirement is about how (well) the system shall do what it does. These are usually quality requirements, such as performance, reliability or ease of use, or general technical requirements that apply to the whole system (e.g. standards to be enforces, operating system compatibility, hardware limitations).

You may also be interested in the difference between functional and non-functional requirements.

Your requirement does not tell at all what the system does, but it tells how the system shall do it. It is hence without any doubt a non-functional requirement.

A functional requirement is about what the system shall do. The term "functional" comes from "function" meaning something that takes some input and produces some output.

A non-functional requirement is about how the system shall do what it does. These are usually quality requirements, sucha as performance, reliability or ease of use.

Your requirement does not tell at all what the system does, but it tells how the system shall do it. It is hence without any doubt a non-functional requirement.

A functional requirement is about what the system shall do. The term "functional" comes from "function" meaning something that takes some input and produces some output.

A non-functional requirement is about how well the system shall do what it does. These are usually quality requirements, such as performance, reliability or ease of use.

Your requirement does not tell at all what the system does, but it tells how the system shall do it. It is hence without any doubt a non-functional requirement.