Users choose their destinations

GROUP ASSIGNMENT PART

Study the following case study and answer all the responsibilities listed.

An computerized ticket-issuing system sells rail seat tickets as you discover in London underground and over earth railway stations. Users choose their locations and can be pay cash the exact amount or insight a debit card and a personal identification quantity (PIN). The rail ticket is issued and their charge card account costed if the solution was bought utilizing a charge card.

When the user presses the start button, a menu screen of potential places is activated, along with a message to the user to choose a vacation spot. Once a vacation spot has been decided on, users are requested to pay cash or source their credit card. Within the last case, its validity is checked out and an individual is then wanted to input an individual identifier. When the credit business deal has been validated, the solution is released.

ambiguities or omissions in the above mentioned scenario

An automatic solution issuing system sells rail seat tickets. Users choose their destination, and input a credit card and an individual identification number. The rail ticket is granted and their bank card account charged with its cost. When an individual presses the start button, a menu display of potential places is activated along with a message to an individual to choose a vacation spot. Once a vacation spot has been picked, users are wanted to input their bank card. Its validity is checked out and the user is then wanted to input an individual identifier. When the credit deal has been validated, the solution is granted.

Ambiguities and omissions include:

  • Can a person buy several tickets for the same destination along or must they be bought individually?
  • Can customers cancel a submission if a blunder has been made?
  • How should the system respond if an invalid card is source?
  • What happens if customers try to put their cards in before selecting a 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 machine only sell tickets between the place where the machine can be found and direct contacts or should it include all possible destinations?
  • What type of source device (touchscreen vs. keyboard)?
  • Ticket prices
  • Room on train (assumes tickets have times to them)
  • Train departure and entrance times. Do customers buy seat tickets for a specific train? Or for just about any trip along the way? (When the latter, then no chance to inform if all the chairs on a teach are sold out, nor is it possible to do seat projects. )
  • Seat projects (see above)
  • Print receipt?
  • identified ambiguities in some appropriate way.
  • Function - Give customer a rail solution, and demand credit consideration or take cash from customer and present the customer, a rail ticket.
  • Description - Determine customer's destination, calculate the charge for the trip, and impose the customer the correct amount. If demand is complete, printing the ticket, normally, print no ticket, and report problem to customer.
  • Inputs - Vacation spot, credit card amount and PIN.
  • Outputs - Tickets, error messages
  • Action - Ask the client for their vacation spot, when input, analyze the full total, and quick to insert a credit card, quick customer for PIN, prompt customer that the transfer is occurring, if successful print the ticket and return to start out point out, if unsuccessful, ask customer to swipe their card again and re-input the PIN. If unsuccessful again, fast that the business deal has failed, and go back to start talk about.
  • Requires - Destination, credit card amount and PIN
  • Pre-condition - None
  • Post-condition - None
  • Side effects - Charge to the customers' credit account

user requirements definitions

The customer requirements for something should illustrate the efficient and nonfunctional requirements in order that they are understandable by system users without any complex knowledge.

When we write an individual requirement we ought to not write with technological forms, table or diagrams. We ought to write in simple dialect with simple stand, forms and diagrams.

The celebrities in the system are the passenger, the counter clerk and the reservation system consisting of form processing, reservation, fare computation, solution processing, ticket printing, assortment of fare amount and submitting as sub-systems.

The passenger is a unaggressive user-actor who initiates the process and obtains the ticket(s), a goal of measurable value. The counter clerk can be an active user-actor, who triggers the machine and gets the role of issuing the seat tickets with the duty of collecting the right fare amount from the passenger, which 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 appropriately and different system statuses are up to date on issuing of tickets. This actor comes with an dynamic role and responsibility at the trunk end.

system requirements specifications

  • System requirements Specs are specified using the standard way of these forms.
  • Function: Issuing Ticket
  • Description: Issuing the solution when the user select their desired tickets and make the right payment.
  • Inputs: Destination, child or Adult, Pay by greeting card or cash
  • Output: Their desired solution to be issued with their payment receipt
  • Requires : Money
  • Pre- Condition: Ticket will be validate between the customer current place and the determined destination, Otherwise individual must pay the charges fare.
  • a collection diagram

Scenario 1

This diagram shows about an individual wants their ticket from the device. It shows the connection between user and ticket machine where consumer puts the necessity to the machine and the device gives options back again to the user.

Scenario 2

This diagram shows the user chose the place and the device give option back to user needs to choose from pursuing option for e. g return ticket which school user wants to visit.

After selecting options an individual needs to pay for payment machine give option for eg cash or credit card. If an individual choose cards the solution machine need to validate from card user.

Scenario 3

This diagram presents a series activity when user buy a ticket using credit or debit greeting card. When the user insert the card. The greeting card is validated with the card issuer the validation of the greeting card is delivered to machine which in turn displays the effect to an individual. If the credit card is valid then your user need to enter into the pin. The validity of the pin is checked out. When the pin is incorrect end user need to try again. Once completed the user account is credited and the solution along with the receipt to the user.

Non-functional requirements

The solution system shall react to end user inputs to provide seat tickets and charge accounts in a timely manner. The system shall continue steadily to function as long as roll of ticket paper is in the machine, and a network interconnection is provided for the vacation spot repository and credit deals. Upon receipt of the vacation spot from the user, the database shall be accessed to determine the distance from the unit's location, to the required destination, and compute the appropriate fee. The unit shall then prompt the user to input their credit card information, and the machine shall check that the card is a debit card, is valid, and has sufficient credit to be charged. Upon successful verification, the unit shall printing a ticket, and return to its ready status, for another transaction to occur. The reliability this system depends on the durability of the physical interface, the network interconnection in the region the system is positioned, how big is the solution rolls that the unit can recognize, and the system for dispensing the seat tickets. The believed time for a full deal would be about thirty secs, supplying twenty for the user connections, five for validation and confirmation of the users accounts, and five for printing and dispensing the solution.

  • Use-cases
  • Requirements validation process.
  • Customer inserts her charge card into the ticket machine.
  • card provider bank checks the card quantity.
  • Then the machine asks for the pin-code.
  • User enters the pin-code.
  • Then the ticket machine requests repository to validate the visa or mastercard.
  • Ticket on processes.
  • customer may use the ticket finaly.
  • A semantic data model

Impact if when the client pays cash

As the collection diagram shows, the client goes to ticket machine, and he's allowed to not need axact amount, the machine will confirm the total amount, go through the check process and issues the ticket with receipt.

References and Bibliography:

  1. Sommerville (2007), Computer Information Technology in Processors, 8th Model, www. pearsoned. co. uk,
  2. Use Diagram (2010) Unified Procedure and Unified Modeling Vocabulary. [Online]. Available from: http://highered. mcgraw-hill. com/sites/dl/free/0070583714/214723/144USECASEDIAGRAM. pdf [Accessed 13 Feb 2010]

Also We Can Offer!

Other services that we offer

If you don’t see the necessary subject, paper type, or topic in our list of available services and examples, don’t worry! We have a number of other academic disciplines to suit the needs of anyone who visits this website looking for help.

How to ...

We made your life easier with putting together a big number of articles and guidelines on how to plan and write different types of assignments (Essay, Research Paper, Dissertation etc)