Software requirements: Functional and Nonfunctional

flickr photo by Peter Morville https://flickr.com/photos/morville/3220969358 shared under a Creative Commons (BY) license
flickr photo by Peter Morville https://flickr.com/photos/morville/3220969358 shared under a Creative Commons (BY) license

To start the process of a software life cycle you need requirements, in other words, what the customer ask for. Before starting the development process, you have to know what the software is going to do, and how is going to do it. Functional and nonfunctional requirements answer those questions.

To be more precise, in software engineer, functional requirements define the functions of the system, is the description of the feature required. It also includes description of the required functions. Some examples of functional requirements are calculations, technical details, data manipulation and processing.

Functional requirements are supported by the nonfunctional requirements, which tells how you are going to make the functional requirements work. This does not mean that you will make something functional with whatever methods you have in mind; nonfunctional requirements also have detail constraints as well as what standard a function should be provided.

To summarize:

In the first step of the software life-cycle, like I wrote before on a previous post, you need to gather information about what the customer needs, those needs are the functional requirements, the description of the behavior of the system. Then, nonfunctional requirements are things that can be measured about the system.

It describes aspects of the system that don’t relate to its execution, but rather to its evolution over time (e.g. maintainability, documentation, etc).

From stack overflow

References:

http://www.sqa.org.uk/e-learning/SDM03CD/page_02.htm

http://www.dau.mil/publications/publicationsDocs/SEFGuide%2001-01.pdf

http://stackoverflow.com/questions/16475979/what-is-functional-and-non-functional-requirement

Advertisements

One thought on “Software requirements: Functional and Nonfunctional

  1. I think it is important to know what the customer wants and also to differentiate it that what can be done. Some times, the requirements are “non-possible goals” and it is the developer that is in charge of the project who needs to adjust it and talk with the customer.

    Acording F and NF requirements.

    Grat post!!

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s