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 them credit card account charged. When the user presses the start button, a menu display of potential destinations are 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. 6. Suggest how an engineer responsible for drawing up a system requirements specification might keep track of the relationships between functional and non-functional requirements
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 them
credit card account charged. When the user presses the start button, a menu display of
potential destinations are 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.
6. Suggest how an engineer responsible for drawing up a system requirements specification
might keep track of the relationships between functional and non-functional requirements
The aforementioned statement has a number of ambiguities or omissions. I'm talking about a few of them.
a) It is not possible to cancel the ticket.
b) The ticket does not allow for the selection of a seat.
b) If the destination and source are the same, there is no choice for a return ticket.
d) Purchasing numerous tickets is not a possibility.
e) Receiving a credit card transaction receipt together with the ticket is not an option.
Step by step
Solved in 2 steps
