FACULTY OF COMPUTER SYSTEMS & SOFTWARE MARKS:

ENGINEERING

COURSE: SOFTWARE
ENGINEERING
CODE: BCS1033 /20
TOPIC: Chapter 3
ASSESSMENT: Tutorial #3 NUM: - DURATION: 2 hours
MATRIC NUM: IC NUM:
_______CD19057________________________ _______990113435402_________________________

General Instructions:

1. This task should be done individually.

2. Answer all questions based on specified case.

Case study: Airline Ticket-Issuing System

An automated ticket machine sells airline tickets. Users select their destination and
input a credit card and a personal identification number. The airline ticket is issued
and their credit card account charged. When the user presses the start button, a
menu display of potential destinations is activated, along with a message to the user
to select a destination and the type of ticket required. Once a destination has been
selected, the ticket price is displayed and customers are asked to input their credit
card. Its validity is checked and the user is then asked to input their personal
identifier (PIN). When the credit transaction has been validated, the ticket is issued.

Question 1
Consider payment using credit card is one of the user requirements. Identify TWO (2) system
requirements associated to payment via credit card.
Apart from payment using credit card, there are two other system requirements associated
to this. Firstly, the system should support airplanes of various types, with the assumption
that the number of seats in a row for a single airplane type is constant. The number of rows
and the number of seats in a row defines an airplane type. Next, the system should also
support on-line access to the system by the customer. The customer can only check on-line
the flight schedule and check the status of his/her own reservation.
(5 Marks / Chapter 3 / System requirement)

1
 FACULTY OF COMPUTER SYSTEMS & SOFTWARE MARKS:
ENGINEERING

COURSE: SOFTWARE
ENGINEERING
CODE: BCS1033 /20
TOPIC: Chapter 3
ASSESSMENT: Tutorial #3 NUM: - DURATION: 2 hours
MATRIC NUM: IC NUM:
_______CD19057________________________ _______990113435402_________________________

Question 2
Based on the ticket-issuing system, write FIVE (5) functional requirements (FR)
a) Use case name : User Registration
 Description : The use case describes the scenario where the user registers with the
application by providing all the necessary details, in order to make reservations or bookings
for flights.
 Actor : User or Customer
 Input : The user or the customer will have to provide all the necessary details present in the
customer registration form of the application.
b) Use case name : User Login
 Description : This use case describes the scenario where user logs into the application, with
the username and password.
 Actor : User or the Customer
 Input : The user or the customer creates a username and password. He then uses them to
login to the system and make reservations or view any information.
c) Use case name : Book Flights
 Description : This use case describes the scenario where the user books airline tickets.
 Actor : User or the Customer
 Input : After logging into the application, the customer looks up the information related to
various airlines and checks the availability of seats on flights. If he finds that there are any
available tickets, he then purchases them.
d) Use case name : Login / Logout
 Description : This use case describes the scenario where the administrator of the
application, logs into the system and logs out after the work is done.
 Actor : Administrator

2
 FACULTY OF COMPUTER SYSTEMS & SOFTWARE MARKS:
ENGINEERING

COURSE: SOFTWARE
ENGINEERING
CODE: BCS1033 /20
TOPIC: Chapter 3
ASSESSMENT: Tutorial #3 NUM: - DURATION: 2 hours
MATRIC NUM: IC NUM:
_______CD19057________________________ _______990113435402_________________________

 Input : The administrator logs into the application with the username and password provided
to him.
 Output : The application verifies the authenticity and displays the home page of the
administrator.

e) Use case name : Add/Delete or Modify Customer Information

 Description : This use case describes the scenario where the administrator adds, deletes or
modifies customer information in the system database.
 Actor : Administrator
 Input : The administrator of the applications logs onto the system with his username and
password.
 Output : the application authenticates the administrator, and then displays the page where
the administrator can add new customers to the database, or delete existing customers or
modify details of customers in the database.

(5 Marks / Chapter 3 / FR)

Question 3

Write FIVE (5) functional requirements with ambiguities or omissions for airline ticket-issuing
system.
a)Can a customer buy several tickets for the same destination together or must they be
bought one at a time?
b)Can customers cancel a request if a mistake has been made?
c)How should the system respond if an invalid card is input?
d)What happens if customers try to put their card in before selecting a destination?
e) Must the user press the start button again if they wish to buy another ticket to a different
destination?
3
 FACULTY OF COMPUTER SYSTEMS & SOFTWARE MARKS:
ENGINEERING

COURSE: SOFTWARE
ENGINEERING
CODE: BCS1033 /20
TOPIC: Chapter 3
ASSESSMENT: Tutorial #3 NUM: - DURATION: 2 hours
MATRIC NUM: IC NUM:
_______CD19057________________________ _______990113435402_________________________

(5 Marks / chapter 3 / disadvantage of natural language requirements)

Question 4

Figure 1: Type of NFR

Based on the ticket-issuing system, write FIVE (5) non-functional requirements (NFR) for the
type of NFR used.
1) Between 0600 and 2300 in any one day, the total system down time should not exceed 5
minutes.
2) Between 0600 and 2300 in any one day, the recovery time after a system failure should
not exceed 2 minutes.

4
 FACULTY OF COMPUTER SYSTEMS & SOFTWARE MARKS:
ENGINEERING

COURSE: SOFTWARE
ENGINEERING
CODE: BCS1033 /20
TOPIC: Chapter 3
ASSESSMENT: Tutorial #3 NUM: - DURATION: 2 hours
MATRIC NUM: IC NUM:
_______CD19057________________________ _______990113435402_________________________

3) Between 2300 and 0600 in any one day, the total system down time should not exceed 20
minutes.
4) After the customer presses a button on the machine, the display should be updated within
0.5 seconds.
5) The ticket issuing time after credit card validation has been received should not exceed
10 seconds.

(5 Marks / Chapter 3 / NFR)

-END-