Conference Presentations
|
Cosmic Truths about Software Requirements The history of many software projects shows that requirements mistakes are the most expensive ones to correct late in development. So, why do we make big requirements errors over and over, even in mission-critical software projects? Karl Wiegers, author of a best-selling book on software requirements and a consultant on many such projects, shares his top ten requirements principles to help your organization produce accurate, consistent, and unambiguous requirements. Although there are few absolute truths in software development, Karl has found several that almost universally apply to software projects. These principles emphasize the critical contribution that good requirements make to a project's success, and the critical contribution that customer involvement makes to good requirements. |
Karl Wiegers, Process Impact
|
|
|
A Defined Process for Requirements Peer Reviews Most software projects include reviews-whether or not they are officially part of the development process. Unfortunately, these reviews are often inefficient, and even unproductive. Implementing a defined peer review process for requirements is an excellent means to both improve your requirements and kick-start overall process improvement because participants can immediately see timesaving and increased quality in work products. Find out how to measure benefits and potential savings from these reviews and how they can identify major gaps in other project processes. Take away a Peer Review Toolkit that allows your team members to start their first effective requirements review right away.
|
Rob Wyatt, Wachovia
|
|
|
Refining Requirements with Test Cases Requirements are supposed to be the basis of most test cases, but can you use test cases to define what the system needs to do--to improve or to actually become the requirements? To some degree, your development process dictates the opportunities you have for test cases to define or refine requirements. However, everyone can benefit from test case writing techniques to identify missing requirements, surface ambiguous statements, and expose implied requirements early in the process. Find out how Tanya Martin-McClellan produces test cases that accurately reflect the requirements, as they are understood at the time, and conducts team reviews to find the gaps and misunderstandings. Although more time is spent writing and rewriting test cases, less time is spent later discussing requirements.
|
Tanya Martin-McClellan, Texas Mutual Insurance Company
|
|
|
Expressing Requrirements as Users Stories - an Agile Approach Expressing requirements as user stories is one of the most broadly applicable techniques introduced by eXtreme Programming and adopted by other agile development processes. User stories are an effective approach for capturing requirements from an agile project, not just those using XP. In this session learn what user stories are, how they differ from other requirements approaches, and why you should consider using them. You also will learn the six attributes all good stories must exhibit and see how to get started with user stories. Whether you are a developer, requirements analyst, tester, manager, or even a customer interested in applying agile techniques to your projects, this session is for you.
|
Mike Cohn, Mountain Goat Software
|
|
|
RequireMINTS - Fresh Approach to Analyzing Requirements Studies show that most application defects are introduced before a single line of code is developed-with many (if not most) of these defects attributed to poor requirements. Studies also show that it is less costly to identify and correct these defects prior to code development. Despite this data, many of us have requirements analysis approaches that have become stale and are ineffective. Many analysts acknowledge that their processes need some improvement but feel helpless to do much about the problem. Dion Johnson offers a package of small yet effective "RequireMINTs" that will freshen up those stale requirements processes in a highly practical way. You will take away a road map for collecting metrics that make a case for requirements improvements, identifying necessary improvements, and implementing these improvements.
|
Dion Johnson, DiJiMax Consulting, Inc.
|
|
 |
Alter Your Requirements Process Fashioning a new requirements method is an almost impossible task, given budget and time constraints. But that doesn't mean you have to be stuck with an ill-fitting process. Learn about seven alterations that almost any organization can make. |
|
|
You Don't Say You've just developed and tested a system that meets each of the customer’s stated requirements. So why aren't they satisfied? Lisa Crispin shares her 5-step process for uncovering hidden assumptions and requirements so that everyone can have the happy ending they expected. |
||
|
Common Requirements Traps - And How to Avoid Them This article details common requirements traps that teams fall into. Tips to help your team avoid these traps are also included. |
Karl Wiegers, Process Impact
|
|
|
How to Test Without Testable Requirements This paper discusses why testing without requirements can create a problem for your project. Testing without the proper requirements can lead to less reliable software results and more software failures. |
Mark Taylor, Analex Corporation
|
|
|
Requirements-Based Testing: An Overview In this article, the author discusses how to deliver more function, in less time, and with fewer resources while maintaining a high level of quality. He details how poorly written requirements can lead to major system errors. This paper also explains why good requirements are a critical part of any successful project. |
Gary Mogyorodi, BIT, Inc.
|
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.