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

Peter
Peter
If you are building a reusable Security Product tool to specifically address Security Technical Implementation Guide (STIG)  Findings, should the requirements be considered Non Functional Requirements or Functional Requirements? For example if there are a number of STIGs such as: The minimum password length shall be 15 characters ...
1 Responses
Bert Wagner
Bert Wagner
It’s 4:30 pm on Friday and Mr. Manager comes along to tell you that he needs you to run some important ad-hoc analysis for him. Previously this meant having to stay late at the office, writing cumbersome queries to extract business information from transactional data. Lucky for you, you’ve recently started using Temporal Tables in SQL...
0 Responses
Ronak Sanghavi
Ronak Sanghavi
Current State For many years now, the most commonly used metaphor on Business Analysis has been the “Bridge”. However, in recent past, some in the BA community have started revisiting the metaphor resulting in a debate on how relevant it is. Of course, the value business analysis can provide for an organization does not depend on how i...
2 Responses


Upcoming Live Webinars



Latest Articles

Requirements for Devices Around Us: Embedded Systems, Part 2
Oct 22, 2017
0 Comments
 In this article we look at some quality attributes that are particularly vital to explore when specifying requirements for embedded systems proj...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC