In my opinion, there is incorrect use of terms:

User's requirements in the plain language should be called user's stories or etc.
Requirements for the hardware are often called system requirements.
Functional requirements cover what your Application need to do and in which way (i.e. its functions)

P.S. Also, you can read about retirements from the wiki: http://en.wikipedia.org/wiki/Requirement

In my opinion, there is incorrect use of terms:

User's requirements in plain language should be called user's stories or etc.
Requirements for the hardware are often called system requirements.
Functional requirements cover what your Application need to do and in which way (i.e. its functions)

P.S. Also, you can read about requirements from the wiki: http://en.wikipedia.org/wiki/Requirement

In my opinion, there is incorrect use of terms:

User's requirements in the plain language should be called user's stories or etc.
Requirements for the hardware are often called system requirements.
Functional requirements cover what your Application need to do and in which way (i.e. its functions)

In my opinion, there is incorrect use of terms:

User's requirements in the plain language should be called user's stories or etc.
Requirements for the hardware are often called system requirements.
Functional requirements cover what your Application need to do and in which way (i.e. its functions)

P.S. Also, you can read about retirements from the wiki: http://en.wikipedia.org/wiki/Requirement