Capturing business requirements using use cases
Seven principles that can make a difference
From the developerWorks archives
Date archived: April 7, 2017 | First published: December 15, 2004
from The Rational Edge: This article outlines seven practical principles for capturing business requirements, based on experiences with a business requirements engineering project for Simpay, a payment system that operates via mobile phone.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.