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.

Translating customer requests into software requires exploration, learning, and discovery. As such, this Reference Point lists resources you can use to learn more about requirements exploration and modeling. Ellen Gottesdiener—a recognized authority on software requirements—provides her top recommendations for books, journals, and online resources on the subject.

While working at a telecommunications company, Linda Hamm had the task of developing and automating tests in a very short time with high-quality expectations. One of the projects was a rule-based expert system for switch maintenance. To help nail down the requirements, the group wrote state diagrams. This article is about what they are and how the group used them.

Prototypes can help you deliver the right software. Here, Technical Editor Brian Lawrence gives examples of prototypes and some guidelines for prototyping.