1 / 8

Requirements Quality Attributes

Requirements Quality Attributes. Quality Attributes. A superset of nonfunctional req. Drive architectural and design decisions Often not explicitly described by the customer Quality attributes may conflict with one another, and trade-offs may need to be explored (and possibly negotiated).

shelbyr
Download Presentation

Requirements Quality Attributes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements Quality Attributes

  2. Quality Attributes • A superset of nonfunctional req. • Drive architectural and design decisions • Often not explicitly described by the customer • Quality attributes may conflict with one another, and trade-offs may need to be explored (and possibly negotiated)

  3. Characterizing Requirements: FURPS+ • One way to categorize requirements: FURPS+ • Functionality • Usability • Reliability • Performance • Supportability • “+” • Design constraints • Implementation requirements • Interface requirements • Physical requirements Quality requirements “-ilities” Non-functional Requirements [RUP]

  4. Operational categories Capability Reliability Usability Performance Installability Compatibility Developmental categories Supportability Testability Maintainability Portability Localizability Another Way to Characterize Requirements: CRUPIC STMPL [RUP] • Developer and support requirements • Mostly visible at build-time • Customer and user requirements • Mostly visible at run-time

  5. Capability. Can it perform the required functions? Reliability. Will it work well and resist failure in all required situations? Usability. How easy is it for a real user to use the product. Performance. How speedy and responsive is it? Installability. How easily can it be installed onto its target platform? Compatibility. How well does it work with external components &configurations? CRUPIC STMPL

  6. Supportability. How economical will it be to provide support to users of the product? Testability. How effectively can the product be tested? Maintainability. How economical will it be to build, fix or enhance the product? Portability. How economical will it be to port or reuse the technology elsewhere? Localizability. How economical will it be to publish the product in another language? CRUPIC STMPL

  7. Attaining balance to quality attributes • Identify • Specify • Prioritize • Assess conflicting goals

  8. Table 12-2 Translating Quality Attributes into Tech. Specs

More Related