Analyze Requirements for Complex Software Systems in a New, Holistic Way: A Method to Resolve Conflicting Functional and Non-Functional Requirements
Source: IBM
This paper describes a method for systematically analyzing requirements of an IT system so one 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.
| Format: | HTML | Size: | 0.00 |
| Date: | Feb 2009 |
People who downloaded this item also downloaded
- Best Practices for Continuous Data Protection and E-Mail Discovery
- 77 Features for Windows 7 that Every IT Professional Should Know About
- Use of Business Modeling in Requirements Definition Phase
- The Critical Need for Email Archiving
- Six Common Mistakes that Plague IT Projects and Three Keys to Avoiding Them



