Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Standard Way of Capturing Requirements Using Use Case
Previous Previous
 
Next Next
New Post 10/18/2016 5:35 AM
User is offline Baker
1 posts
No Ranking


Standard Way of Capturing Requirements Using Use Case 

What problems team faces if we do not follow the standard of writing the Use Case and if all the alternate and exception flows are not documented ? What further problems will the team face if we do not capture most of the System behavior in Use Case and try to capture them in NFR document? Need some evidence to convince the Management and team to follow the standard.

 
New Post 10/28/2016 1:09 PM
User is offline Sandy
74 posts
8th Level Poster




Re: Standard Way of Capturing Requirements Using Use Case 

The use case structure serves 2 very important purposes: 1) helps the BA analyze the documented requirements for accuracy and completeness (have all scenarios (flows) been captured, have business rules been captured for all flows & steps as needed, etc.); and 2) enables communication and interpretation of the defined requirements.

Putting functional requirements into an NFR doesn't work for these purposes. NFR format is typically quite different from functional requirements format - so chances are, something will be missed or improperly communicated.

The risk of not having or not using a standard format intended specifically for functional requirements (whether use case, user story, business requirements document or any other format) is much higher risk of missed requirements, missed business rules, and misinterpreted requirements. The associated costs of poor requirements management are nicely stated in a report from IAG available on ModernAnalyst:

http://media.modernanalyst.com/Mythbusting-the-Path-to-Requirements-Success-Jan-2011.pdf

Sandy

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Standard Way of Capturing Requirements Using Use Case

Community Blog - Latest Posts

SarikaA
SarikaA
Pega systems(Software Company) is the leading provider of business process management (BPM) and customer relationship management (CRM) software solutions. Pega systems motto is “Build For Change” and their goal is to “eliminate software coding” and “automate manual work”. Pega systems has bee...
0 Responses
Surbhi Mahnot
Surbhi Mahnot
Requirements define the needs of the project to provide best of its utility and benefits. If they aren’t clear or analysis is not done properly, it might lead to failure of the project no matter how good the concept and design is. Just as a system is composed of various functionalities, requirements too are identified in various forms. This ...
0 Responses
Sanjay Yadav
Sanjay Yadav
 Challenges in Implementation:     I’m a strong believer of putting finishing touch to any initiative. Project Initiation is always tough and complex and need lots of research but if BA is unable to give the finishing touch then he is not done yet. So, I thought to put few of my views, challenges and observations during...
1 Responses




Latest Articles

Business Analysis - Leading with Influence
Jun 26, 2017
0 Comments
What is Leading with Influence?... It is about the ability to affect the actions, decisions, and thinking of others to accomplish key goals or tasks t...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC