Requirements

Better Software Magazine Articles

Book Review: Mastering the Requirements Process

Brian Lawrence points to Mastering the Requirements Process as a valuable reference book. The book presents a complete step-by-step method for gathering, modeling, and specifying requirements. Along the way the authors offer easy-to-understand and appropriate examples that nicely illustrate how to apply their techniques.

Brian Lawrence
Test Design: Developing Test Cases from Use Cases

A use case is a sequence of actions performed by a system, which combined together produce a result of value to a system user. Use cases describe the "process flows" through a system based on its actual likely use, so the test cases derived from use cases are most useful in uncovering defects in the process flows during real-world use of the system. Here is an example of how a use case is used to derive and prioritize test cases.

Ross Collard's picture Ross Collard
Lo-Fi GUI Design

This article takes you from “what happens before Lo-Fi Design” (understand the user) to storyboarding (with post-it notes), through final implementation. Other steps include window design (get out the scissors) and simulated execution. This thorough, step-by-step explanation of design method is supplemented with graphics and a usability sidebar.

Luke Hohmann
Requirements When the Field Isn't Green

Most advice on requirements gathering is targeted for brand-new "green-field" projects. What about evolving projects? Here's a seven-point strategy for those of us working on maintenance, updates, and legacy documentation.

Karl E. Wiegers
Collaborate for Quality

Project teams are searching for ways to develop requirements that are as free from defects as possible. Here's how you can use collaborative workshops, along with walkthroughs and QA checklists, to develop high-quality requirements.

Ellen Gottesdiener's picture Ellen Gottesdiener
What's With These Buffer Overrun Bugs?

Many of the culprits responsible for security breaches found on corporate networks and the Internet today have used buffer overrun problems as the main way to exploit the system. Here is an examination of buffer overrun bugs and how to prevent them.

Bob Johnson
Testers and Developers Think Differently

Appreciating differences is critical for productive teams. Different approaches aid in finding solutions, and mutual respect dramatically improves group problem solving. Testers should not be judged according to developer criteria.

Bret Pettichord's picture Bret Pettichord
Automating Requirements Traceability

Developing software to meet users' specific needs can be a difficult task. Verification and validation activities can help ensure that you are building the right software right.

Bill Councill
Lessons in Test Automation

Elfriede Dustin has worked on many projects at various companies where automated testing tools were introduced to a test program lifecycle for the first time. In reviewing these projects, she has accumulated a list of "Automated Testing Lessons Learned," taken from actual experiences and test engineer feedback. In this article, she will share examples of this feedback, hoping that this information will help you avoid some typical false starts and roadblocks.

Elfriede Dustin's picture Elfriede Dustin
Testing in the Dark

How can you test software without knowing what it should do? Here is a step-by-step approach to overcoming undocumented requirements, including how to discover the requirements, how to define "quality" for the project, and how to create a test plan including release criteria.

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.