QUESTION 1
Discover ambiguities or omissions in the following statement of
requirements
for part of a ticket-issuing system:
An
automated ticket-issuing system sells rail tickets. Users select their
destination
and input a credit card and a personal identification number.
The
rail 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. Once a
destination
has been selected, users are requested to input their credit card.
Its
validity is checked and the user is then requested to input a personal
identifier.
When the credit transaction has been validated, the ticket is
issued.
Answer:
Ambiguities
and omissions include:
1.
Can a customer buy several tickets for the same destination together or must
they be bought one at a time?
2.
Can customers cancel a request if a mistake has been made?
3.
How should the system respond if an invalid card is input?
4.
What happens if customers try to put their card in before selecting a
destination
(as they would in ATM machines)?
5.
Must the user press the start button again if they wish to buy another ticket
to
a different destination?
6.
Should the system only sell tickets between the station where the machine is
situated
and direct connections or should it include all possible destinations?
add 3 more answer:
1. Can a
customer buy many ticket that have different destination in one transaction or
buy it separately?
2. Can
customer using cash to make the payment?
3. How
user know the process of how to make the payment?
QUESTION 2
Write
a set of non-functional requirements for the ticket-issuing system,
setting out
its expected reliability and response time.
Answer:
Possible
non-functional requirements for the ticket issuing system include:
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.
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.
6.
When validating credit cards, the display should provide a status message
for
customers indicating that activity is taking place.
7. The
maximum acceptable failure rate for ticket issue requests is 1: 10000.
add 3 more answer:
1. When
user cannot buy the ticket, user have about 7 minutes to repeat the process and
get the ticket.
2.
Another user that want the ticket must wait until 7 minutes, if the seat not
paid, the next user able to buy the ticket.
3. The
refresh time must be shorter because the another user is waiting.
Design BY :-
Arif, Adziim, Iqbal, Nik, Ashraf, Aiman, Faiq, Irshad, Wan Haniff
Comments
Post a Comment