What are your requirements?

Why do we as testers spend so much time with functional requirements? What about the rest of the requirements which are numerous and important as well?

Why do we as testers spend so much time with functional requirements? What about the rest of the requirements which are numerous and important as well?

A functional requirement is 'A description of a behavior that a system will exhibit under specific conditions'.

So you have to think about the situations in which the program might be used and find solutions for getting out of those situations – is this the task of the tester?

At an abstract level all the requirements can be divided into four categories:
  • Business requirements
  • User requirements
  • Functional requirements
  • Anything that falls under the concept of "non-functional requirements."
You will still have comments such as: “In my opinion the functional requirements are...” or “Why are bothering me with functional requests, if they are that important why don’t you write them yourself.”

Of course you must have a separation between requirements and specifications – which aren’t the same thing. But what is taken into account must be written.

What are your requirements.jpeg


In alphabetical order, the most important specifications are:

Business requirement

A high-level business objective of the organization that builds a product or of a customer who procures it. This is the "Wish list", which still needs to be displayed correctly in the functional requirements (of which there may be more than one), which in turn have to become specifications.

The trouble is that this Wish list provides an answer to the question "Why should I do something?". The majority believes that the Wish list will tell why and how this product will be implemented.

Business rule

A policy, guideline, standard, or regulation that defines or constrains some aspect of the business. Not a software requirement in itself, but the origin of several types of software requirements.

Constraint

A restriction that is imposed on the choices available to the developer for the design and construction of a product.

Feature

One or more logically related system capabilities that provide value to a user and are described by a set of functional requirements.

Functional requirement
  
A description of a behavior that a system will exhibit under specific conditions. The keyword here is "the situation."

Nonfunctional requirement

A description of a property or characteristic that a system must exhibit or a constraint that it must respect. That is, should be considered.

Quality attribute

A kind of nonfunctional requirement that describes a service or performance characteristic of a product. Who takes this into account?

System requirement

A top-level requirement for a product that contains multiple subsystems, which could be all software or software and hardware. Who writes these requests?

User requirement

A goal or task that specific classes of users must be able to perform with a system, or a desired product attribute. No need to wait for users to come and present their claims. It will be very bad if users come to the requirements.

Alexey Lupan

Share the knowledge

Still have questions?
Connect with us
Thank you.
Your request has been received.
Thank you!
The form has been submitted successfully.