Analyze requirements for complex software systems in a new, holistic way
A method to resolve conflicting functional and non-functional requirements
From the developerWorks archives
First published: February 17, 2009
This article describes a method for systematically analyzing requirements of an IT system so you can create a component model that addresses the requirements in a holistic way. Explore sample requirements with uses cases and "stress cases" to identify potential conflicts between functional and non-functional requirements. Stress cases must be addressed by defining an optimum solution that resolves the conflict. Learn how functional and non-functional requirements are opposing forces that are handled similarly to forces in civil engineering structures.
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 content, steps, or illustrations may have changed.