Q

Why document user requirements?

Documenting user requirements is important for a project's health. Expert Roxanne Miller explains why.

Why should we (the business analyst) document user requirements when we already know what we want the system (functional requirements) to do?
What this is really saying is that you as the business analyst "assume" that you know what the system should do based on what you "assume" the user wants. The Standish Group International has identified "user involvement" every year for the past decade as the most critical factor for project success. Without formally eliciting (seeking input directly from the user), analyzing (documenting assumptions and prioritizing the requirements), representing and validating the user requirements, the project team risks implementing the wrong system functionality. This, of course, equates to rework later on. Furthermore, without first looking at what the user role does to perform their business tasks, the "manual" aspects of what they do are completely overlooked and are not accounted for in the solution.

This was first published in January 2008

Dig deeper on Penetration Testing

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchSOA

TheServerSide

SearchCloudApplications

SearchAWS

SearchBusinessAnalytics

SearchFinancialApplications

SearchHealthIT

Close