|
|
|
Better Software Conference & EXPO 2006 Concurrent Sessions
Go To: Agile Development | Managing Projects and Teams | Measurement | Outsourcing | Plan-Driven Development |
Process Improvement | Quality Assurance | Security | Special Topics | System Requirements | Testing
View by Date
| System Requirements | | | Thursday, June 29, 2006 9:45 AM |
User Stories for Better Software Requirements
Mike Cohn, Mountain Goat Software
The technique of expressing requirements as user stories is one of the most broadly applicable techniques introduced by Extreme Programming. In fact, user stories are an effective approach on all time-constrained projects, not just those using Agile methods. Mike Cohn explains how to identify the functionality for a user story and how to write it well. He describes the attributes all good user stories must exhibit and presents guidelines for writing them. Learn to employ user role modeling when gathering a project�s initial stories. Whether you are a developer, tester, manager, or analyst, you can learn to write user stories that will speed up development and help you deliver the systems that users really need.
� Defining a user story and learning how to write one
• Six attributes of all user stories
• Thirteen guidelines for writing better user stories |
| | | Thursday, June 29, 2006 11:15 AM |
Why Are Requirements So Poorly Defined?
Richard Bender, Bender RBT Inc.
Studies have shown that the quality of the requirements is one of the most important factors in the quality of an application and also in the time and costs required to deliver a system. Yet requirements are almost always ambiguous, incorrect, incomplete, too high level, logically inconsistent, and communicated by rumor. The irony is that the various techniques�which have been around for decades�for writing better requirements have not been widely adopted. The culture and the management of the software process are equally to blame. Richard Bender gets to the root of the problem and discusses ways to address the poor requirements issues. Learn quantitative measures of the quality of the requirements specification and practical approaches to writing unambiguous requirements for your applications.
� Early validation of requirements through testing
• Moving user acceptance test design up prior to the start of coding
• Getting management�s support for improvements |
| |
|
|
