Discover ambiguities or omissions in the following statement of requirements for part of a ticket-issuing system:
An automated ticket machine 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 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.
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?
You might also like to view...
Which of the following is correct syntax to declare C++ class B to be a public base class for derived class D
a. public base class B: class D {/*…*/}; b. class D : public class B {/* … */}; c. class D : public B {/* … */}; d. class B: public D { }; e. None of the above
Programs written in low-level languages usually execute ____ than programs written in high-level languages.
A. more accurately B. less accurately C. faster D. slower