Scribd Logo
Upload

Welcome to Scribd!

  • 132 views

    Exercise Sheet 2 PDF

    Uploaded by

    Mariem Boussaadia
    This document provides an exercise sheet for a software engineering course covering requirement engineering. It includes review questions on requirements phases and characteristics as well as exercises analyzing functional vs. non-functional requirements and different levels and types of requirements for an online shopping application for a grocery store chain.

    Copyright:

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

    Exercise Sheet 2 PDF

    Uploaded by

    Mariem Boussaadia
    132 views2 pages
    This document provides an exercise sheet for a software engineering course covering requirement engineering. It includes review questions on requirements phases and characteristics as well as exercises analyzing functional vs. non-functional requirements and different levels and types of requirements for an online shopping application for a grocery store chain.

    Original Title

    Exercise sheet 2 (2).pdf

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides an exercise sheet for a software engineering course covering requirement engineering. It includes review questions on requirements phases and characteristics as well as exercises analyzing functional vs. non-functional requirements and different levels and types of requirements for an online shopping application for a grocery store chain.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    132 views2 pages

    Exercise Sheet 2 PDF

    Uploaded by

    Mariem Boussaadia
    This document provides an exercise sheet for a software engineering course covering requirement engineering. It includes review questions on requirements phases and characteristics as well as exercises analyzing functional vs. non-functional requirements and different levels and types of requirements for an online shopping application for a grocery store chain.

    Copyright:

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

    CS 321: Introduction to Software Engineering

    FALL2020

    Exercise Sheet 2
    Requirement Engineering

    Review Questions

    1. What is the basic goal of requirement phase?

    2. List out the important characteristics of a good SRS.

    3. The need for developing a complete specification may encourage an analyst to write detailed and lengthy
    documents. Which competing quality of specification (see Lecture) may encourage an analyst to keep the
    specification short?

    Exercise 1

    1. Specify which of the following statements are functional requirements and which are non-functional re-
    quirements:

    1. The ticket distributor must enable a traveller to buy weekly passes.

    2. The ticket distributor must be written in Java.

    3. The ticket distributor must be easy to use.

    2. Below are examples of non-functional requirements. Specify which of these requirements are verifiable and
    which are not

    1. The system must be usable.

    2. The system must provide visual feedback to the user within 1 second of issuing a command.

    3. The availability of the system must be above 95.

    4. The user interface of the new system should be similar enough to the old system such that users familiar
    with the old system can be easily trained to use the new system.

    Exercise 2

    Answer questions in accordance to the system definition given below.


    ABC Markets Chain E-Shopping Application (ESA):
    ABC Markets Chain wants to acquire custom software that enables e-shopping of its products by customers
    over the Internet in order to increase the amount of its sales. ABC Markets Chain has many stores and each

    1
    Exercise Sheet 2 2

    store has a Store Manager. ABC Markets Chain E-Shopping Application (ESA) is expected to support a Store
    Manager in maintaining information regarding the departments within the store and the products within the
    departments.
    ESA is also expected to support customers in their e-shopping. Customer can explore the products in the
    departments of the store (e.g. delicatessen, bakery, and cleaning), and add the products into his/her basket
    in the amounts that s/he wishes to buy. Customer can also search the store for specific products, or remove
    already added products from his/her basket. Customer can display the content and price of his/her basket
    during e-shopping. When the customer completes choosing products, s/he can buy the products in his/her
    basket by a credit-card. Purchased products are then delivered by a Store Assistant to the address that the
    customer provides during payment. If the customer is registered in ESA as a District Customer, the system
    will allow the District Customer to pay, alternatively, by cash or credit card at the time of product delivery to
    the address by the Store Assistant.
    Project Development: ABC Markets Chain awarded a contract to XYZ Software Company to develop ESA.
    The software will include two parts, namely “data management” and “e-shopping”. ABC Markets Chain wants
    “data management” part to be delivered earlier than “e-shopping part”.

    1. Explain each requirements level given below by a sentence. For each level, provide an example requirement
    for ESA. (Note that not every level of requirement is exemplified in the definition of ESA. You may need to
    create your own examples for some of them.)
    A. User requirements
    B. System requirements

    2. Explain each requirement type given below by a sentence. For each type, provide an example requirement
    for ESA. (Note that not every type of requirement is exemplified in the definition of ESA. You may need to
    create your own examples for some of them.)

    A. Functional requirements
    B. Non-Functional requirements
    C. Domain requirements
    D. Design Constraint

    You might also like