Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


Tip of the Day
Language: Visual Basic
Expertise: Beginner
Jan 28, 1999

Collect User Requirements With Scenarios

When talking to the user or subject-matter expert about an application's requirements, write the requirements in the form of scenarios. A scenario both defines the requirement and provides a list of steps detailing how the resulting feature will be used. For example, instead of writing a requirement to "process payroll," your scenario might be to select an employee from a list of existing employees, to enter the time allocated to the project for each employee, and so on. This clarifies requirements and helps you better visualize how users will use the feature. Once you understand the reasoning behind the request, you might even find a better way to meet the requirement. You can then use these scenarios as the test plan for the feature.
Deborah Kurata
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date