Scribd Logo
Upload

Welcome to Scribd!

  • 11 views

    Evolutionary Requirements: Applying UML and Patterns

    Uploaded by

    Anum Khawaja
    Requirements define what a system must do and be. Managing changing requirements is important to avoid building the wrong system. The Unified Process recognizes that requirements evolve over time rather than being fully defined up front. Stakeholders' needs are often unclear and change, so there must be a systematic process to track requirements. FURPS+ is a common framework that categorizes requirements as functional, usability, reliability, performance, supportability, and other factors like implementation details and legal obligations. Functional requirements are specified in use cases and features while non-functional requirements relate to qualities like usability and performance.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd

    Evolutionary Requirements: Applying UML and Patterns

    Uploaded by

    Anum Khawaja
    11 views9 pages
    Requirements define what a system must do and be. Managing changing requirements is important to avoid building the wrong system. The Unified Process recognizes that requirements evolve over time rather than being fully defined up front. Stakeholders' needs are often unclear and change, so there must be a systematic process to track requirements. FURPS+ is a common framework that categorizes requirements as functional, usability, reliability, performance, supportability, and other factors like implementation details and legal obligations. Functional requirements are specified in use cases and features while non-functional requirements relate to qualities like usability and performance.

    Original Title

    Chap5

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Requirements define what a system must do and be. Managing changing requirements is important to avoid building the wrong system. The Unified Process recognizes that requirements evolve over time rather than being fully defined up front. Stakeholders' needs are often unclear and change, so there must be a systematic process to track requirements. FURPS+ is a common framework that categorizes requirements as functional, usability, reliability, performance, supportability, and other factors like implementation details and legal obligations. Functional requirements are specified in use cases and features while non-functional requirements relate to qualities like usability and performance.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    11 views9 pages

    Evolutionary Requirements: Applying UML and Patterns

    Uploaded by

    Anum Khawaja
    Requirements define what a system must do and be. Managing changing requirements is important to avoid building the wrong system. The Unified Process recognizes that requirements evolve over time rather than being fully defined up front. Stakeholders' needs are often unclear and change, so there must be a systematic process to track requirements. FURPS+ is a common framework that categorizes requirements as functional, usability, reliability, performance, supportability, and other factors like implementation details and legal obligations. Functional requirements are specified in use cases and features while non-functional requirements relate to qualities like usability and performance.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 9

    Evolutionary Requirements

    Chapter 5 Applying UML and Patterns

    Requirements

    These are the capabilities and conditions that the system, the project, and the product must provide and meet. Managing requirements is a best practice for project managers. Requirement issues are the leading cause of project failure. Even if you do a perfect job of building the wrong thing, its no good!

    Not Waterfall Requirements

    There is an attempt in the waterfall method to describe the requirements fully and accurately and freeze them. Unified process realizes that change is constant, so plans for change instead of setting an impossible goal.

    Managing Requirements

    Stakeholder requirements are frequently unclear and change over time. Frequently new requirements are discovered as part of the development process. There must be a systematic approach to finding, documenting, organizing, and tracking the changing requirements of a system. (RUP)

    FURPS+

    Functional (features, capabilities, security) Usability (human factors, help, documents) Reliability (failures, recovery, predictable) Performance (response, throughput, etc) Supportability (maintainability, configuration) + ancillary and sub-factors (next slide)

    Ancillary and sub-factors

    Implementation (includes limitations) Interface Operations Packaging Legal Requirements

    Functional Requirements

    Detailed in the Use Case Model and in the System Features list of the Vision artifact. They are specified in detail in Operation Contracts where necessary.

    Non-functional requirements

    Often called the -ilities of a system; quality, reliability, usability, performance, etc. The glossary, data dictionary and supplemental specifications describe many non-functional requirements. In addition, architectural documents may have non-functional requirements.

    Hints for Vision Homework

    There is no UML or other formal format for a Vision Statement. Text has some examples. Make sure you cover scope, main functionality, and Go/No Go decision. A Business Case usually has financial metrics like IRR, while a Vision has less financial detail. You can do either.

    You might also like