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

Arash
Arash
Let me start by saying that a business rule is far more granular than a business decision, and that the two should never be confused. Today, it is an unfortunate fact that some vendors would have potential clients believe that there is synergy between business rules and business decisions. Perhaps this is because in an effort to differentiate one b...
0 Responses
LN Mishra, CBAP
LN Mishra, CBAP
Traceability is one of the lesser understood aspects of business analysis. It is indeed quite hard to maintain good traceability unless automated. This is why BABoK® warns us being theoretical about traceability. In this article, I would like to explain traceability concepts with help of an example. BABoK® definition of traceability: ...
4 Responses
Hitendra 01
Hitendra 01
Most IT jobs have a clear, specific job description and career path. However, the business analyst career path tends to vary, as do the descriptions from job to job. The business analyst career path is best. Because, “There are career tracks that zigzag back and forth between IT and business. Someone might start as a business analyst, and the...
0 Responses




Latest Articles

Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC