Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Requirements Gathering Steps
Previous Previous
 
Next Next
New Post 10/18/2010 9:53 AM
User is offline GBusiness
35 posts
9th Level Poster


Re: Requirements Gathering Steps 
Modified By GBusiness  on 10/18/2010 12:00:20 PM)

Hello Larimar and K,

 

This is extremely helpful. Thank you very much!

 
New Post 10/31/2010 6:55 AM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: Requirements Gathering Steps 

 Its a start.  All knowledge is good.  Ask around the team for advice also.

 

I think the best writing on use cases is by alistair cockburn (who has lots of free stuff at his website)

 
New Post 11/18/2010 8:48 PM
User is offline SteveBoulanger
38 posts
9th Level Poster


Re: Requirements Gathering Steps 

According to me, necessities vary from scheme to scheme. But some fundamental requirements are premeditated business plan, situate for opening production, adequate capital for deal, fine promotional method etc.

 
New Post 2/1/2011 12:57 PM
User is offline peddi
3 posts
No Ranking


Re: Requirements Gathering Steps 

 There are many schools of thought on how best to gather requirements.

On one hand, there are those that don't document anything and get straight into code, there are others that cover absolutely everything in detail at the start. Both have their problems. The smaller the project, the less risk there is in not capturing requirements. In larger projects, the risk is increases dramatically. 

However, develompent is not an exact science and often requirements, even if written well can change due to unknown or unforeseen circumstances which makes you wonder why you bother in the first place! This is where common sense has to prevail. The amount of detail put into the requirements will depend on the scale and nature of the project.

Essentials in Requirement Gathering:

a) Focus and Clarity

b) A Format for Specifying Requirements

c) The Author of the Requirements Document

d) The Language of Requirements

e) Accuracy is Critical

f) Minimize the Risk of Errant Interpretation

 

Peddi.R.Akurati

::::::::::::::::::::::: www.mindmapinfo.net ::::::::::::::::::::::::::::::::

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Requirements Gathering Steps

Community Blog - Latest Posts

Salesforce has established itself as one of the most reputable CRM platforms, providing important customer data to assist businesses in effectively managing their operations. Salesforce is the world's best CRM platform that helps businesses to keep up the data in an arranged or structured manner. Salesforce is the world's most popular...
There are big differences between data exploration versus data presentation. And you need to be aware of these differences as you're creating data stories and data presentations. Let’s start by defining our terms: Data exploration means the deep-dive analysis of data in search of new insights. Data presentation means...
Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC