Scribd Logo
Upload

Welcome to Scribd!

  • 950 views

    FURPS

    Uploaded by

    MNaveedsdk
    The document discusses non-functional requirements and how they are different from functional requirements. It explains that non-functional requirements place constraints on the system as a whole, such as usability, reliability, performance, and supportability. Specific non-functional requirements include the level of user expertise, interface standards, documentation, safety, security, availability, and response time.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    FURPS

    Uploaded by

    MNaveedsdk
    950 views3 pages
    The document discusses non-functional requirements and how they are different from functional requirements. It explains that non-functional requirements place constraints on the system as a whole, such as usability, reliability, performance, and supportability. Specific non-functional requirements include the level of user expertise, interface standards, documentation, safety, security, availability, and response time.

    Original Title

    FURPS.docx

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses non-functional requirements and how they are different from functional requirements. It explains that non-functional requirements place constraints on the system as a whole, such as usability, reliability, performance, and supportability. Specific non-functional requirements include the level of user expertise, interface standards, documentation, safety, security, availability, and response time.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    950 views3 pages

    FURPS

    Uploaded by

    MNaveedsdk
    The document discusses non-functional requirements and how they are different from functional requirements. It explains that non-functional requirements place constraints on the system as a whole, such as usability, reliability, performance, and supportability. Specific non-functional requirements include the level of user expertise, interface standards, documentation, safety, security, availability, and response time.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3

    Identifying Non-Functional Requirements

    Non-Functional Requirements
    In addition to the functions a system must perform, there are often constraints the system must
    satisfy.

    Some constraints may apply to individual use cases.

    For example, a constraint on opening an account at an online liquor store is that customers must
    be at least 21 years old.

    UML allows us to annotate elements by constraints. A constraint usually has the form:

    { condition }

    The condition can be expressed informally or formally.

    For example:

    The FURPS+ Model


    A system-wide constraint is called a non-functional requirement.

    The FURPS model organizes all requirements into five categories:

    F = Functional

    U = Usability

    R = Reliability
    P = Performance

    S = Supportability

    The FURPS+ model adds a few more categories.

    Non-Functional Requirements
    Usability

    Level of user expertise assumed.

    User interface standards used.

    Documentation provided.

    Reliability

    Safety and security requirements.

    Availability, robustness, and reliability of the system.

    Exception handling

    Mean time between failures

    Error tolerance

    Data loss tolerance

    Performance

    number of concurrent users supported

    response time

    number of transactions per second

    Supportability

    How will system be extended?

    Who maintains the system?

    Implementation
    Platform?

    Interfaces

    Interfaces to existing systems.

    Protocols used.

    Operation

    Who manages the running system?

    Packaging

    Who installs the system?

    How many installations are there?

    Legal

    Licensing?

    Liability issues?

    Licensing fees or liabilities incurred from using third-party components or algorithms?

    You might also like