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 6: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 2: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

Limor Wainstein
Limor Wainstein
Business analysts typically gather and interpret data from many areas within an organization, finding solutions to business problems and improving business processes with all that data. A business analyst may measure and improve on such disparate things as warehouse efficiency and cloud software implementation. A marketing analyst, on the other...
0 Responses
EA Learning
EA Learning
My current, favourite question for Executives and Architects is “How do you see Architecture operating in an Agile environment.” This question usually elicits a wry smile and a response along the lines of “I will need to get back to you on that!” Many people are wondering how Architecture will fair in the world of Agile. My ...
0 Responses
Limor Wainstein
Limor Wainstein
The age of cloud computing is now so firmly established that research firm Gartner predicted by 2020, a corporate "no-cloud" policy will be as rare as a "no-internet" policy is today. In the same press release, Gartner went on to predict that spending on compute power sold by cloud providers will exceed that of compute power sold and deployed into ...
0 Responses


Upcoming Live Webinars



Latest Articles

Intelligent Business Requirements
Jan 21, 2018
0 Comments
Intelligent Business Requirements are business needs and objectives that were designed to add business value and promote scalability and innovation. ...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC