We accept

Discover Ambiguities Or Omissions

  7. System Requirement

An automatic solution issuing system sells rail tickets. Users choose their vacation spot, and input a debit card and an individual identification number. The rail solution is issued and their visa or mastercard account charged with its cost. When an individual presses the beginning button, a menu screen of potential destinations is activated plus a message to the user to choose a vacation spot. Once a destination has been chosen, users are wanted to source their visa or mastercard. Its validity is checked out and the user is then wanted to input an individual identifier. If the credit business deal has been validated, the ticket is released.

Ambiguities and omissions include:

Can a person buy several tickets for the same vacation spot together or must they be bought individually?

Can customers cancel a demand if a mistake has been made?


How if the system respond if an invalid credit card is input?


What happens if customers make an effort to put their credit card in before choosing the destination (as they might in ATM machines)?


Must the user press the beginning button again if they desire to buy another ticket to a new destination?


Should the system only sell tickets between your station where in fact the machine can be found and direct cable connections or should it include all possible locations?


What kind of insight device (touchscreen vs. keyboard)?


Ticket prices


Room on coach (assumes tickets have times to them)


Train departure and introduction times. Do customers buy tickets for a specific train? Or for any trip along the way? (In case the latter, then no chance to tell if all the seats on the train are sold out, nor can you do seat assignments. )


Seat assignments (see above)


Print receipt?

Rewrite the above explanation using the set up approach referred to in the study text. Solve the recognized ambiguities in a few appropriate way.

Function - Give customer a rail solution, and fee credit account or take cash from customer and give the client, a rail ticket.

Description - Determine customer's destination, calculate the fee for the trip, and charge the customer the appropriate amount. If fee is complete, print out the ticket, often, print no solution, and report problem to customer.

Inputs - Destination, credit card quantity and PIN.

Outputs - Tickets, mistake messages

Action - Ask the customer for their destination, when input, calculate the total, and quick to insert a debit card, prompt customer for PIN, fast customer that the deal is taking place, if successful printing the solution and return to get started on status, if unsuccessful, ask customer to swipe their greeting card again and re-input the PIN. If unsuccessful again, prompt that the purchase has failed, and go back to start point out.

Requires - Destination, credit card quantity and PIN

Pre-condition - None

Post-condition - None

Side results - Charge to the customers' credit account

Write the user requirements definitions.

The services provided for the user and the non-functional system requirements should be detailed. Also description may use natural terminology, diagrams or other nations that are understandable by customers. Product and process criteria which must used should be specified

The stars in the machine are the passenger, the counter-top clerk and the reservation

system consisting of form processing, reservation, fare computation, solution processing,

ticket printing, assortment of fare amount and publishing as sub-systems.

The passenger is a passive user-actor who initiates the procedure and obtains the

ticket(s), an objective of measurable value. The counter-top clerk can be an dynamic user-actor,

who triggers the system and gets the role of issuing the tickets with the responsibility

of collecting the right fare amount from the passenger, which really is a measurable

value. Predesigned and deployed ticket reservation system at the trunk end is a

system actor-user to ensure that ticket processing is done effectively and different

system statuses are updated on issuing of tickets. This actor comes with an productive role and

responsibility at the back end.

Write the system requirements requirements.

System Requirement

The passenger has a preceding knowledge of the reservation and ticketing system.

The passenger finds the railway ticket counter and interacts with the

counter clerk first through an enquiry and then uses the process of form

filling, tendering, repayment and collecting the tickets.

Passenger accepts the solution or leaves the counter-top.

Passenger seeks home elevators fare, coach timings and availability of tickets.

Passenger can have solo solution or multiple tickets.

Journey begins on a day and will be over with one rest among.

Passenger is determined by name, age group, gender and address.

Trains are discovered by name and quantity.

No receipt is granted for the money transacted.

Output of the system is solution(s) with details.

The process is induced through a form filled up by the passenger detailing the

requirements of tickets, coach, date, etc.

A form is employed for each train. If the trip requires use of multiple trains,

separate forms are used for each train.

Draw a series diagram demonstrating the actions performed in the ticket-issuing system. You can create any fair assumptions about the system. Pay particular focus on specifying user problems.




Destination Request


Find Destination

Calculate Total

Credit Cards Request

Credit Cards No

Pin Request





Invalid Card


Insufficient Credit




Print Ticket

Write a couple of non-functional requirements setting out its expected consistency and its own response time.

The ticket system shall react to user inputs to provide tickets and demand accounts in a timely manner. The machine shall continue to function as long as roll of solution paper is at the device, and a network interconnection is provided for the destination databases and credit orders. Upon receipt of the destination from an individual, the database shall be accessed to look for the distance from the unit's location, to the required destination, and calculate the appropriate fee. The machine shall then fast an individual to input their credit card information, and the unit shall validate that the greeting card is a debit card, is valid, and has sufficient credit to be costed. Upon successful confirmation, the machine shall print a ticket, and return to its ready state, for the next transaction to take place. The reliability this technique relies on the toughness of the physical user interface, the network connection in the area the system is positioned, how big is the ticket rolls that the unit can admit, and the mechanism for dispensing the tickets. The approximated time for a full purchase would be about thirty seconds, giving twenty for an individual relationships, five for validation and confirmation of the users bank account, and five for printing and dispensing the solution.

Develop a set of use-cases that can serve as a basis for understanding the requirements for ticket-issuing system.

Briefly describe the requirements validation process. Discuss all the investigations that you have to perform to validate the aforementioned requirements in ticket-issue system

1. Customer inserts her credit card in to the machine.

2. ATM bank checks the card amount.

3. ATM requests the pin-code.

4. User enters the pin-code.

5. ATM requests repository to validate the credit card.

6. The action options are shown to the customer.

7. Customer chooses to print out account information.

8. ATM investigations if enough newspaper is present printing cartridge is not unfilled.

9. ATM directs demand to the database.

10. ATM designs out the info and informs user from it.

11. User takes away the printout from the device.

12. Action options are offered again.

13. Customer chooses a sum from the list.

14. Customer confirms that she desires to obtain the selected sum of money.

15. ATM checks the actually available money.

16. ATM investigations demands customer's balance data from the database.

17. ATM requests the databases to debit the customer's profile.

18. ATM comes back the user's cards.

19. User accumulates the card.

20. ATM provides cash.

21. User accumulates the cash.

22. ATM asks an individual whether she would like a receipt.

Create a semantic data model for these scenario

Payment Handling System

Ticket Concern System


Interface System

What is the impact if when the customer pays cash, he is allowed never to have the precise amount?

In such case there will be a problem as to how the customer would be delivered his staying amount. Thus such instances should also be considered in designing the machine.

More than 7 000 students trust us to do their work
90% of customers place more than 5 orders with us
Special price $5 /page
Check the price
for your assignment