Users select their destinations

Users select their finissGROUP ASSIGNMENT PARTStudy the pastime case study and answer all the tasks listed.An automated shred- return system copes direct tickets as you find in London under demesne and over ground sound offway stations. Users select their destinations and lowlife be contain bullion the get hold of amount or input a mention flier and a individual(prenominal) identification number ( wooden leg). The rail ticket is issued and their credit phone loosen history super blastd if the ticket was bought using a credit cod.When the exploiter presses the give way button, a menu display of potential destinations is actuate, a considerable with a message to the exploiter to select a destination. in one case a destination has been selected, users are call for to pay cash or input their credit card. In the last case, its grimness is checked and the user is then requested to input a in-person identifier. When the credit transaction has been validated, the ticket is issued.ambiguities or omissions in the above scenarioAn automatic 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 with its cost. 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. erst 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.Ambiguities and omissions includeCan a node buy several tickets for the same destination together or moldiness they be bought one at a time?Can customers natural a request if a mistake has been made?How should the system do if an invalid card is input?What happens if customers try to put their card in b efore selecting a destination (as they would in ATM railcars)?Must the user press the start button again if they wish to buy some other ticket to a distinguishable destination?Should the system only sell tickets between the station where the railway car is situated and direct ties or should it include all possible destinations?What type of input device (touch screen vs. keyboard)? shred pricesRoom on string (assumes tickets have times on them) drawstring departure and arrival times. Do customers buy tickets for a specific find out? Or for any trip along the route? (If the latter, then no way to tell if all the seats on a train are sold out, nor can you do seat assignments.)Seat assignments (see above) impress admit?identified ambiguities in some appropriate way.Function ordinate customer a rail ticket, and charge credit account or take cash from customer and give the customer, a rail ticket. definition Determine customers destination, calculate the charge for the trip, an d charge the customer the appropriate amount. If charge is complete, scar the ticket, otherwise, print no ticket, and report error to customer.Inputs Destination, credit card number and PIN.Outputs Tickets, error messagesAction Ask the customer for their destination, when input, calculate the total, and brisk to insert a credit card, make customer for PIN, go customer that the transaction is taking place, if successful print the ticket and return to start state, if unsuccessful, ask customer to swipe their card again and re-input the PIN. If unsuccessful again, prompt that the transaction has failed, and return to start state.Requires Destination, credit card number and PINPre-condition NonePost-condition NoneSide effects Charge to the customers credit accountuser requirements definitionsThe user requirements for a system should describe the functional and cosmetic requirements so that they are understandable by system users without any proficient knowledge.When we writ e the user requirement we should not write with technical grades, tabulate or plots. We should write in simple language with simple table, forms and diagrams.The actors in the system are the passenger, the counter clerk and the reservation system consisting of form processing, reservation, fare computation, ticket processing, ticket printing, collection of fare amount and lineup as sub-systems.The passenger is a passive user-actor who initiates the process and obtains theticket(s), a address of measured value. The counter clerk is an active user-actor,who triggers the system and has the section of issuing the tickets with the responsibilityof collecting the aline fare amount from the passenger, which is a measurablevalue. Predesigned and deployed ticket reservation system at the back end is asystem actor-user to ensure that ticket processing is done correctly and differentsystem statuses are updated on issuing of tickets. This actor has an active role andresponsibility at t he back end.system requirements specificationsSystem requirements Specifications are specify using the standard way of these forms.Function Issuing Ticket commentary Issuing the ticket when the user select their desired tickets and make the correct payment.Inputs Destination, child or Adult ,Pay by card or cashOutput Their desired ticket to be issued with their payment receiptRequires silverPre- Condition Ticket will be validate between the user current place and the selected destination, Otherwise user will have to pay the penalty fare.a sequence diagramScenario 1This diagram shows more or less the user wants their ticket from the machine. It shows the interaction between user and ticket machine where user puts the requirement to the machine and the machine gives options back to the user.Scenario 2This diagram shows the user chose the station and the machine give option back to user needs to choose from following option for e.g return ticket which mark user wants to travel.Aft er selecting options the user needs to pay for payment machine give option for eg cash or card. If the user choose card the ticket machine need to validate from card user.Scenario 3This diagram represents a sequence activity when user buy a ticket using credit or debit card. When the user insert the card. The card is validated with the card issuer the validation of the card is returned to machine which then displays the allow to the user. If the card is valid then the user need to enter the pin. The validity of the pin is checked. If the pin is wrong user need to try again. Once completed the user account is credited and the ticket along with the receipt to the user.Non-functional requirementsThe ticket system shall respond to user inputs to provide tickets and charge accounts in a timely manner. The system shall continue to function so long as roll of ticket paper is in the machine, and a network connection is provided for the destination database and credit transactions. Upon re ceipt of the destination from the user, the database shall be accessed to even up the distance from the units location, to the desired destination, and calculate the appropriate fee. The unit shall then prompt the user to input their card information, and the unit shall verify that the card is a credit card, is valid, and has sufficient credit to be charged. Upon successful check, the unit shall print a ticket, and return to its ready state, for the next transaction to take place. The dependableness this system relies on the durability of the physical user interface, the network connection in the area the system is placed, the size of the ticket rolls that the unit can accept, and the mechanism for dispensing the tickets. The estimated time for a complete transaction would be well-nigh thirty seconds, giving twenty for the user interactions, five for validation and verification of the users account, and five for printing and dispensing the ticket.Use-casesRequirements validation process.Customer inserts her credit card into the ticket machine.card provider checks the card number. then(prenominal) the machine asks for the pin-code.User enters the pin-code.Then the ticket machine requests database to validate the credit card.Ticket on processes.customer can use the ticket finaly.A semantic data caseImpact if when the customer pays cashAs the sequence diagram shows, the customer goes to ticket machine, and he is allowed to not have axact amount, the machine will back the amount, go through the check process and issues the ticket with receipt.References and BibliographySommerville (2007), Computer training Technology in Processors, 8th Edition, www.pearsoned.co.uk,Use Diagram (2010) Unified glide path and Unified Modeling Language. Online.Available from http//highered.mcgraw-hill.com/sites/dl/free/0070583714/214723/144USECASEDIAGRAM.pdf Accessed 13 Feb 2010