Scribd Logo
Upload

Welcome to Scribd!

  • 125 views

    Understanding Requirements: Applying UML and Patterns - Craig Larman

    Uploaded by

    akbisoi1
    1) Requirements define the capabilities and conditions that a system, project, and product must provide and meet. Managing requirements is a best practice for project managers as requirements issues are a leading cause of project failure. 2) In the waterfall method, there is an attempt to fully describe requirements up front but this is unrealistic as requirements change constantly. The unified process realizes this and plans for managing change rather than freezing requirements. 3) Stakeholder requirements are often unclear and change over time. New requirements are frequently discovered during development. There must be a systematic approach to finding, documenting, organizing, and tracking changing requirements.

    Copyright:

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

    Understanding Requirements: Applying UML and Patterns - Craig Larman

    Uploaded by

    akbisoi1
    125 views8 pages
    1) Requirements define the capabilities and conditions that a system, project, and product must provide and meet. Managing requirements is a best practice for project managers as requirements issues are a leading cause of project failure. 2) In the waterfall method, there is an attempt to fully describe requirements up front but this is unrealistic as requirements change constantly. The unified process realizes this and plans for managing change rather than freezing requirements. 3) Stakeholder requirements are often unclear and change over time. New requirements are frequently discovered during development. There must be a systematic approach to finding, documenting, organizing, and tracking changing requirements.

    Original Description:

    Larman Chapter 5

    Original Title

    Larman Chapter 5

    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?

    1) Requirements define the capabilities and conditions that a system, project, and product must provide and meet. Managing requirements is a best practice for project managers as requirements issues are a leading cause of project failure. 2) In the waterfall method, there is an attempt to fully describe requirements up front but this is unrealistic as requirements change constantly. The unified process realizes this and plans for managing change rather than freezing requirements. 3) Stakeholder requirements are often unclear and change over time. New requirements are frequently discovered during development. There must be a systematic approach to finding, documenting, organizing, and tracking changing requirements.

    Copyright:

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

    Understanding Requirements: Applying UML and Patterns - Craig Larman

    Uploaded by

    akbisoi1
    1) Requirements define the capabilities and conditions that a system, project, and product must provide and meet. Managing requirements is a best practice for project managers as requirements issues are a leading cause of project failure. 2) In the waterfall method, there is an attempt to fully describe requirements up front but this is unrealistic as requirements change constantly. The unified process realizes this and plans for managing change rather than freezing requirements. 3) Stakeholder requirements are often unclear and change over time. New requirements are frequently discovered during development. There must be a systematic approach to finding, documenting, organizing, and tracking changing requirements.

    Copyright:

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

    Understanding Requirements

    Chapter 5 Applying UML and Patterns -Craig Larman

    Requirements
    These

    are the capabilities and conditions that the system, the project, and the product must provide and meet Managing re!uirements is a best practice "or project managers #e!uirement issues are the leading cause o" project "ailure $ven i" you do a per"ect job o" building the %rong thing, its no good&

    Not Waterfall Requirements


    There

    is an attempt in the %ater"all method to describe the re!uirements "ully and accurately and '"ree(e) them Uni"ied process reali(es that change is constant, so plans "or change instead o" setting an impossible goal

    Managing Requirements
    *ta+eholder

    re!uirements are "re!uently unclear and change over time ,re!uently ne% re!uirements are discovered as part o" the development process There must be a 'systematic approach to "inding, documenting, organi(ing, and trac+ing the changing re!uirements o" a system ) -#UP.

    FURPS+
    Functional

    -"eatures, capabilities, security. Usability -human "actors, help, documents. Reliability -"ailures, recovery, predictable. Per"ormance -response, throughput, etc. Supportability -maintainability, con"iguration. + ancillary and sub-"actors -ne/t slide.

    Ancillary and sub-factors


    0mplementation 0nter"ace 1perations Pac+aging Legal

    -includes limitations.

    #e!uirements

    Functional Requirements
    2etailed

    in the Use Case Model and in the *ystem ,eatures list o" the 3ision arti"act They are speci"ied in detail in 1peration Contracts %here necessary

    Non-functional requirements
    1"ten

    called the '-ilities) o" a system4 !uality, reliability, usability, per"ormance, etc The glossary, data dictionary and supplemental speci"ications describe many non-"unctional re!uirements 0n addition, architectural documents may have non-"unctional re!uirements

    You might also like