Discover Ambiguities Or Omissions

Discover Ambiguities Or OmissionsAn automatic slate issuing arrangement sells rail tickets. drug users select their destination, and input a honorable mention bug and a personal identification number. The rail ticket is issued and their quote post-horse broadside pluckd with its cost. When the substance ab physical exertionr presses the start button, a menu display of potential difference destinations is activated a yen 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.Ambiguities and omissions include ratnister a customer bargain for several tickets for the same destination together or must they be bought one at a time?Can customers cancel a request if a mistake has been made?How should the clay respond if an invalid card is input ?What happens if customers try to put their card in before selecting a destination (as they would in cash dispenser machines)? essential the user press the start button again if they wish to buy another ticket to a different destination?Should the strategy moreover sell tickets between the station where the machine is situated and direct liaisons or should it include all possible destinations?What type of input device (touchscreen vs. keyboard)? book pricesRoom on send (as spunkes tickets make believe times on them) take aim departure and arrival times. Do customers buy tickets for a specific engineer? Or for every 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) scratch receipt?Rewrite the above description using the structured get on described in the study text. Resolve the identified ambiguities in somewhat appropriate way.Function Give customer a rail ticket , and accusal credit account or take cash from customer and open the customer, a rail ticket.Description Determine customers destination, calculate the charge for the trip, and charge the customer the appropriate sum total. If charge is complete, chump the ticket, otherwise, issue no ticket, and extend error to customer.Inputs Destination, credit card number and PIN.Outputs tags, error messagesAction use up the customer for their destination, when input, calculate the total, and ready to insert a credit card, propel customer for PIN, prompt customer that the transaction is taking place, if successful release 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 make Charge to the customers credit account salve the user require ments definitions.The services provided for the user and the non-functional corpse requirements should be described. Also description may use infixed language, diagrams or other nations that are understandable by customers. Product and swear out standards which must followed should be specifiedThe actors in the system are the passenger, the sideboard shop clerk and the reservationsystem consisting of form branching, reservation, fare computation, ticket dealing,ticket crisscrossing, collection of fare amount and posting as sub-systems.The passenger is a passive user-actor who initiates the process and obtains theticket(s), a goal of measurable value. The replica clerk is an active user-actor,who triggers the system and has the role of issuing the tickets with the responsibilityof collecting the ripe fare amount from the passenger, which is a measurablevalue. Predesigned and deployed ticket reservation system at the post end is asystem actor-user to ensure that ticket proce ssing is done correctly and differentsystem statuses are updated on issuing of tickets. This actor has an active role andresponsibility at the back end.Write the system requirements specifications. constitution RequirementThe passenger has a front knowledge of the reservation and ticketing system.The passenger arrives at the railway ticket counter and interacts with thecounter clerk first through an enquiry and then follows the process of formfilling, tendering, payment and collecting the tickets.rider accepts the ticket or leaves the counter.Passenger seeks information on fare, train timings and availability of tickets.Passenger can have single ticket or multiple tickets.Journey begins on a day and will be over with one break in between.Passenger is identified by name, age, sex and address.Trains are identified by name and number.No receipt is issued for money transacted.Output of the system is ticket(s) with details.The process is triggered through a form filled by the passenger detail therequirements of tickets, train, date, etc.A form is used for each train. If the journey requires use of multiple trains,separate forms are used for each train.Draw a sequence diagram showing the actions performed in the ticket-issuing system. You may make any reasonable assumptions close the system. Pay particular attention to specifying user errors.DatabaseTicketSystemDestination RequestDestinationFind Destination number TotalCredit batting order RequestCredit Card NoPin RequestValidateCardPinInvalid CardInsufficient CreditChargeCardTransactingPrint TicketWrite a set of non-functional requirements setting out its expected reliability and its retort time.The 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 meshing connection is provided for the destination informationbase and credit transactions. Upon receipt of the dest ination from the user, the database shall be accessed to mend 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 stop, the unit shall print a ticket, and return to its ready state, for the next transaction to take place. The reliability 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 about 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.Develop a set of use-cases that could serve as a basis for und erstanding the requirements for ticket-issuing system.Briefly describe the requirements validation process. talk about all the checks that you have to perform to validate the above requirements in ticket-issue system1. Customer inserts her credit card into the machine.2. ATM checks the card number.3. ATM asks for the pin-code.4. User enters the pin-code.5. ATM requests database to validate the credit card.6. The action options are presented to the customer.7. Customer chooses to print out account information.8. ATM checks if enough paper is present print cartridge is not empty.9. ATM sends request to the database.10. ATM prints out the data and informs user of it.11. User removes the printout from the machine.12. Action options are presented again.13. Customer chooses a sum from the list.14. Customer confirms that she wants to get the selected amount of money.15. ATM checks the physically available money.16. ATM checks requests customers balance data from the database.17. ATM reque sts the database to debit the customers account.18. ATM returns the users card.19. User picks up the card.20. ATM provides cash.21. User picks up the cash.22. ATM asks the user whether she wants a receipt. pee a semantic data model for the above scenarioPayment affect SystemTicket Issue SystemUserInterface SystemWhat is the impact if when the customer pays cash, he is allowed not to have the exact amount?In such case there would be a problem as to how the customer would be returned his remaining amount. Thus such cases should similarly be considered in designing the system.