Functional and Non-Functional Specifications

In any software developments, the technical team is mainly focusing on the business requirement document from Customer on how these required functions to be behaved/specify as in system and requirement engineering so that development team is able to developed, tested and configured for them as final deliverables to Customers. The term we often used to define these development scopes is known as “Functional Requirement/Specifications”. However much of these requirements do not cover on ‘non-functional’ requirements. Non-functional requirement is to describe/judge the operations of a system and it is important to cover as it will determine the minimum, possible criteria to sign-off for the deployment. A solution cannot operate successfully if the infrastructure/configurations are done incorrectly, even though it may meet the functional requirements.

Some Areas that define as Non-Functional Requirements/Specification:

  • Accessibility
  • Performance/Response Time
  • Usability
  • Scalability
  • Compatibility
  • Reliability
  • Maintainability
  • Robustness
  • Documentation
  • Effectiveness
  • Efficiency

Reference: http://www.ics.uci.edu/~taylor/ics52_fq01/vdh-qualities.pdf

The splitting of functional and non-functional modules enable different organization/team based on their specialization to conduct thorough, detailed setups, configurations and testings. For example, the system team or may known as Infrastructure team will take care on the standard setups for the equipment, network design, database/repositories for the usage of that solution. Configuration team works with the Development team to understand the configuration parameters required to setup to run the solution. Application testing team takes charge of the testings of the functions that are designed to perform expected behaviors.

The scopes for functional and non-functional requirements are also to be captured in the Master Project Plan so that the stakeholders are aware these modules must be reviewed, covered and achieved at each milestone of the project phase.


7 Responses to “Functional and Non-Functional Specifications”

  1. August 9, 2009 at 3:25 pm

    Greetings. I am a teacher from Hyderabad, India. You have touched a subject which is grossly neglected by software engineers. There is a lot of work to do in this area.

    I would appreciate getting copies of your papers/publications on this subject.

    My address is:: drpartha AT gmail DOT com.

    Thank you,


  2. 3 saranya
    July 13, 2010 at 10:18 pm

    not bad..its k all the beat for ur future…

  3. May 1, 2011 at 4:04 am

    Thank you for the good writeup. It in fact was a amusement account it. Look advanced to far added agreeable from you! By the way, how can we communicate? I’ll just check back at aquarelles.wordpress.com for you later. play texas hold em poker online

  4. 5 zahida86
    May 23, 2012 at 2:18 pm

    functional requirement mean, what i do and non-functional requirement mean, what i thought.

  5. February 27, 2014 at 3:43 pm

    Thank you so much! That was beneficial

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 )


Connecting to %s

March 2008
« Feb   Apr »


Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 464 other followers


%d bloggers like this: