Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 37 views

    Lect Software Requirements

    Uploaded by

    Syed Muhammad Fawad
    In this slides, i introduced how can you gathered software requirement of any project and also describe the types of requirement and many more

    Copyright:

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

    Lect Software Requirements

    Uploaded by

    Syed Muhammad Fawad
    37 views29 pages
    In this slides, i introduced how can you gathered software requirement of any project and also describe the types of requirement and many more

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    In this slides, i introduced how can you gathered software requirement of any project and also describe the types of requirement and many more

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    37 views29 pages

    Lect Software Requirements

    Uploaded by

    Syed Muhammad Fawad
    In this slides, i introduced how can you gathered software requirement of any project and also describe the types of requirement and many more

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 29

    Mam saba sultan

    1
     Something required, something wanted or
    needed
     Webster’s dictionary

     There is a huge difference between wanted


    and needed and it should be kept in mind all
    the time!

    2
     Stakeholders
     People affected in some way by the system
     Documents
     Existing system
     Domain/business area

    3
    4
     Functional requirements
     Non-functional requirements
     Domain requirements
     Inverse requirements
     Design and implementation constraints

    5
    6
     Statements describing what the system does
     Functionality of the system

     Statements of services the system should


    provide
     Reaction to particular inputs
     Behavior in particular situations

     Customers and developers usually focus all


    their attention on functional requirements

    7
     The system shall solve a quadratic equation
    using the following formula
     x = (-b+sqrt(b2 – 4*a*c))/2*a

     The user shall be able to search either the


    entire database of patients or select a subset
    from it (admitted patients, or patients with
    asthma, etc.)

    8
     Incomplete and ambiguous requirements are
    open to multiple interpretations and
    assumptions

     This can lead to the development of poor


    quality, or faulty, software products

    9
     Functional requirements
     Non-functional requirements
     Domain requirements
     Inverse requirements
     Design and implementation constraints

    10
     Most non-functional requirements (NFRs)
    relate to the system as a whole. They include
    constraints on:
     Performance,
     Reliability,
     Security,
     Maintainability,
     Usability,
     Standards, etc.

    12
     They are often more critical than individual
    functional requirements.

     Must be built into the software product, as


    failure to meet a NFRs system requirement may
    make the whole system unusable.

    13
     For example, if an aircraft system does not
    meet reliability requirements, it will not be
    certified as ‘safe’.

     If a real-time control system fails to meet its


    performance requirements, the control
    functions will not operate correctly e.g.
    ATM in banking system

    14
     NFRs come up/depends through:
     User needs, budget & interoperability,
     Organizational policies(s/w developing),
     External factors such as safety regulations,
    privacy legislation, etc.

    15
     Non-functional requirements should be
    documented in SRS,
     so that they can be used to build the architecture of the
    software product

    16
    •Architecture: where non-functional decisions are cast, and
    functional requirements are partitioned
    •Design: where functional requirements are accomplished

    non-functional architecture
    requirements
    (“ilities”)

    functional
    requirements design
    (domains)

    Important : this is a general guideline – sometimes the borders are blurred


     Functional requirements
     Non-functional requirements
     Domain requirements
     Inverse requirements
     Design and implementation constraints

    18
     Requirements that come from the;
     Application domain and
     Reflect fundamental characteristics of that application
    domain.

     These can be both the functional or non-


    functional requirements.

    20
     Domain requirements can impose strict
    constraints on solutions

     Domain-specific terminology can also cause


    confusion.

    21
     Functional requirements
     Non-functional requirements
     Domain requirements
     Inverse requirements
     Design and implementation constraints

    22
     They explain what the system shall not do.
    Many people find it convenient to describe their
    needs in this manner.

     These requirements indicate the hesitant nature


    of customers about certain aspects of a new
    software product

    24
     Example:
    The system shall not use red color in the user
    interface, whenever it is asking for inputs from
    the end-user.

    25
     Functional requirements
     Non-functional requirements
     Domain requirements
     Inverse requirements
     Design and implementation constraints

    26
     They are development guidelines within which
    the designer must work.

     These requirements can seriously limit design


    and implementation options

     Can also have impact on human resources

    28
     The system shall be developed using the
    Microsoft .Net platform

     The system shall be developed using open


    source tools and shall run on Linux operating
    system

    29

    You might also like