Conference Presentations

Gathering Requirements in a Low-Process Environment

Knowing the requirements for a system means understanding the problem to be solved. If the problem isn't understood, the solution can't address it. Not taking time for requirements discovery at the beginning will cost far more time and money in the end. This paper explains requirements gathering techniques.

Elisabeth Hendrickson, Quality Tree Software, Inc.
Testing and Implicit Requirements: Expanding the Unwritten Specification

Testers should be encouraged to test against and report deviations from implicit specifications. There is a Universal Implicit Specification that is based on
fundamental principles. These principles are: the system will not lie, the system will impose no gratuitous keyholes or other constraints, and the system won’t do anything that’s just plain stupid.It’s worthwhile to identify, elaborate, and make explicit the fundamental principles and
common manifestations of deviations from these principles.

Scott Meyers,
The Innovative Tester

Historically, the development team considers themselves the creators of the system and the QA community is considered as a necessary evil, more so when there is an independent testing group. Since test engineers sometimes work in a hostile atmosphere, they need to equip themselves with more knowledge in both functional and testing skills. This article discusses the importance of developing those skills.

Gunasekaran Veerapillai's picture Gunasekaran Veerapillai
STAREAST 2003: Rapid Web Testing in a High-Velocity Environment

This paper discusses implementing METS (Minimal Essential Testing Strategy) for your test team. METS is a strategy to help get the essential testing for your project done within the time frame allowed. Step by step instructions for using this methodology are included.

Greg Paskal, Kinko's
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.
The Product Champion: Making Sure that Customer, Team, and Business Needs Are Well Represented in the Development Process

Having a close relationship with the customer is always a good idea. But with that relationship comes risks. Most projects could use a knight in shining armor to protect their product's future. Discover how a product champion can help your organization stay focused on the customer without losing sight of the big picture.

Linda Rising's picture Linda Rising
Visual Requirements

Instead of wading through requirements documents, try drawing them instead. Learn about three simple diagrams and how to turn them quickly into valuable models. The diagrams presented here represent the most commonly used types for each of the three software dimension perspectives: data flow diagrams for function, class diagrams for information, and state transition diagrams for behavior.

Becky Winant
Give 'em the Business

Miscommunication is at the heart of most software defects. Being knowledgeable about a company as a whole, and not just about the specs of a particular project, is just one more way to safeguard against failures. Read on as Elisabeth Hendrickson explains the importance of technical people staying informed about business strategies.

Elisabeth Hendrickson's picture Elisabeth Hendrickson
Requirements Workshop Agenda (template)

This template for a requirements workshop includes preparation tasks and, a place for listing workshop tools and participants.

Ellen Gottesdiener's picture Ellen Gottesdiener


StickyMinds is a TechWell community.

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