Unified Scenario-Based Design, Part 1, Methodological principles
From the developerWorks archives
Date archived: December 20, 2016 | First published: November 29, 2005
Did you ever wonder how to provide crisp requirements to system architects, designers, and developers? Do the written scenarios ever completely explain to you and your teams all the context of the environment in which the systems will run? How can you quickly adapt to continuous business requirement changes? How can you create the best interfaces for a system? Unified Scenario-Based Design is an end-to-end methodology that addresses the above questions, with the aim of creating systems that more easily fit the needs of the business that requires them.
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.