Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Functional requirements vs System requirements
Previous Previous
 
Next Next
New Post 2/27/2020 12:48 PM
User is offline Gautam
1 posts
No Ranking


Functional requirements vs System requirements 

Greetings,

I am finding it hard to determine the difference between these two kinds as they both talk about what the system shall do with a very small line between them. I wonder if anyone can describe the difference between.

 
New Post 3/31/2020 2:20 AM
User is offline Stewart F
100 posts
7th Level Poster


Re: Functional requirements vs System requirements 

Hi Gautam, 

The following is a slightly 'dumbed down' approach, but is easier to understand to the 'proper' response.

Functional Requirements

These are requirements for things that do something. For example, "I want a button that if I click it prints out the Users' details". These are the most common requirement, but it does rather depend on what you are 'building' or what the project you are working on is.

Typically, each Functional requirement should have an end result due to that process.

System Requirements

System requirements are also sometimes called Non-functional requirements. However, they don't have to be. A system requirement may be that you wish to carry out an upgrade to a platform as a part of your project, It still has an end result, so it could fall under the functional requirement, but as it is purely system driven, you could place it under the System requirements. 

A non-functional requirement is something that doesn't, on its own, have a direct end result. So for example, a non-functional requirement might be "I want to improve the performance of the platform, so that I can process a work item quicker".

If you aren't sure, then feel free to post those that you would like clarification on. Also, there are quite a few good documents on this site that might help with such a question. Having said that, always happy to help.

Stewart  

 
New Post 4/15/2020 4:26 PM
User is offline Kimbo
450 posts
5th Level Poster


Re: Functional requirements vs System requirements 

Hi Stewart,

"I want a button, that if I click, prints out the user details" is NOT a requirement.

Its very poor practice to accept users perceived solution to their underlying requirement to view user details at face value. after further questioning, the BA may find the requirement is just the ability to view a summary of user details. the requirement may be something like:

"the solution shall allow viewing of user details"

The solution to this requirement may be a report, a screen to view the details and the ability to print the details.

One of the key things, if not the key thing, to learn as a BA is to look behind what the users are asking for to the real requirement. The solution may and often is, completely different to what is asked for.

Stewart's example of a functional requirement above is very poor practice.

Kimbo

 
New Post 4/22/2020 3:36 PM
User is offline d15bt_
2 posts
No Ranking


Re: Functional requirements vs System requirements 
 Kimbo wrote

Hi Stewart,

"I want a button, that if I click, prints out the user details" is NOT a requirement.

Its very poor practice to accept users perceived solution to their underlying requirement to view user details at face value. after further questioning, the BA may find the requirement is just the ability to view a summary of user details. the requirement may be something like:

"the solution shall allow viewing of user details"

The solution to this requirement may be a report, a screen to view the details and the ability to print the details.

One of the key things, if not the key thing, to learn as a BA is to look behind what the users are asking for to the real requirement. The solution may and often is, completely different to what is asked for.

Stewart's example of a functional requirement above is very poor practice.

Kimbo


 

Completely agree with Kimbo's comments.

One thing I wanted to add is understanding the current state is often critical in order to clearly see the reason for user's comments such as the one used above. Quite often users will be hindered by a lack of a certain function or feature and will come up with own workarounds, or will have an impression that having the ability to do X will make their lives easier. In this case it's important to understand what are they trying to achieve, and how does this fit with your understanding of the current vs future state.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Functional requirements vs System requirements

Community Blog - Latest Posts

So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...
Elicitation involves bringing out or drawing out information. Elicitation is a key task in business analysis as without proper elicitation the requirements for the solution to the business needs cannot be identified. 1. Not understanding underlying business need Organization’s business environment keeps changing with respect to Customer...
TOGAF is a certification that is handed over by The Open Group. It is an open corporate architecture means used to improvise upon the business effectiveness across the world’s leading business set-ups. Aspirants wishing for a successful career in corporate architecture must go for the TOGAF certification in order to explain the...

 



 

Copyright 2006-2021 by Modern Analyst Media LLC