Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Eliciting Non-Functional (vs. business or functional) Requirements
Previous Previous
 
Next Next
New Post 11/1/2019 6:59 AM
User is offline TheProBA
1 posts
No Ranking


Re: Eliciting Non-Functional (vs. business or functional) Requirements 

I consider Roxanne Miller's book The Quest for Software Requirements the definitive book on the topic.  I strongly recommend you check it out.  In addition to process, it includes a library of 2,000 sample questions you can use in preparation for NFR elicitation.  Should be required reading for all BA's

 
New Post 11/11/2019 4:49 AM
User is offline Stewart F
96 posts
7th Level Poster


Re: Eliciting Non-Functional (vs. business or functional) Requirements 

Hi Pichaty, 

I would suggest that you stick with the same methodology that you use for Functional requirements - just note them as non-functional. In the 'good old days' of BRDs and the like, there would be a different section for Non-Functional requirements, but it was still in the same document. This should be carried forward for todays world where you may not be using a BRD (i.e. Agile). Keep to the same methodology otherwise the people who have to read your Non-functional requirements and carry them out may not understand what it is you are asking for. 

Sticking to the same methodology should remove this danger. A requirement us still a requirement - whether it is a functional or non-functional one. So why change methodology?

In an ideal world, a functional requirement should be linked to a non-functional one, and vice-versa. So splitting them out would probably make yours and other peoples lives,  working on your project harder.  

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Eliciting Non-Functional (vs. business or functional) Requirements

Community Blog - Latest Posts

m_anst
m_anst
What Does Success Look Like? I challenge Business Analysts to view requestors’ requirements as an opportunity to define success. Too often, teams fall into a trap focused on requestors’ prescriptive requirements that are meant to serve as roadmaps for developers and testers. When you limit your view of requirements to this prescripti...
0 Responses
Mariya Kotsupalova
Mariya Kotsupalova
They say the best criteria of Business Analyst’s success are a happy customer (business) and a happy engineering team. But what does it mean? How can we break down happiness and measure it? These are precisely the questions my 8 BAs team and I tried to answer this year. The result was a surprisingly efficient pair of surveys we developed and ...
0 Responses
Rajesh-N
Rajesh-N
Explore the Benefits of RPA's Adoption Across Segments In the past few years, we have seen steady growth in Robotic Process Automation (RPA). It gathered momentum in 2019 and became a hot topic in IT and business circuits in 2020. The power of process automation will be felt even more strongly, propelling its adoption as a replacement f...
0 Responses






Copyright 2006-2020 by Modern Analyst Media LLC