Requirements Gathering



Email    print   
September 15, 2005 —  (Page 1 of 2)
At the center of the design process is the notion of “requirements gathering,” but I think the entire notion is misguided. There is no such thing as a “requirement,” at least not in the way that most programmers or marketing people use the term. The only real requirement is that the program solve a real problem that vexes real users, that the program provide answers to specific questions about the real world.

When you focus on gathering discrete “requirements,” you focus on the minutiae: menu items, dialog-box contents and the like. All too often, the big picture—the problem that you’re trying to solve—gets lost and the program is a failure. It doesn’t actually do anything useful.

When designing, I think about problem definition, not requirements gathering. If presented with a specific requirement, I always ask: “Why do you need that? What task are you doing or what problem are you solving that would be made easier were that requirement implemented.” That, is I focus on the problem itself. The methodologies I use don’t use requirements lists. Instead, they use two documents that look more like essays than bullet lists.

First, a “problem statement” defines the user’s problem and any solution to that problem that can be expressed in domain terminology. It doesn’t describe a computer program; rather, it focuses on the real-world problems of the users. For example, I’m currently working on a system that solves problems associated with secondary-school administration—grant management in particular. The problem statement describes how the grants are administered, not how the program will look. In fact, words like “computer,” “system,” “database” and “user interface” don’t even appear in the problem statement. The audience is a school administrator, not a programmer.

The second piece of the puzzle is “use-case analysis.” The use cases define the tasks that the user has to perform to solve the problem you just identified. Like the problem statement, the use cases are defined using the vocabulary of the users, and are written in the context of the problem. They don’t describe how you might use a computer program; they describe how you solve the problem at hand. How do grant administrators set up and administer the grants? At the core of the use-case analysis are the activities that the user performs, and the sequence in which the activities are performed. There’s even a UML diagram for capturing this information, called an activity diagram.




Pages 1 2 


Share this link: http://sdt.bz/28847
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Collaboration and requirements: Better together
Software makes it easier for developers to work with other stakeholders to ensure what’s built matches what was requested Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb