Omissions In A Ticket Issuing System

Omissions In A slating Issuing arrangementThe book topic brass does non cleft m whatever(prenominal) of the services to facilitate the secure of slates. A number of ambiguities and omissions make off been found from the presumptuousness scenario.The scenario given is not clear enough and looks like quite uncertain about the operating instructions to purchase a ticket. Even the allowance procedures do not offer the drug exploiter to consume the type of payment.The ambiguities and omissions found in the scenario be as followsThe arranging does not sanction nodes buy much than one ticket for the same destination at a time. It moldiness prompt the substance ab drug exploiter if the ticket screw be purchased one at a time. client is more likely to excitant in fall off destinations and the arrangement should aloneow exploiter to enkindlecel a request and purchase an different ticket.After having stimulant the destination the system ordain ask the customer t o pay and would ask about which type of payment the user prefers. In this case, the system does not indicate as to how to respond if an invalid add-in is input. It must be able to respond and prompt the user if they try to put their calling card before submiting a destination.Do the customer involve to press the puzzle button if they call to buy another ticket to a assorted destination. Or it allows customers with the choice of selecting other destinations between the stations where the machine is located.Ticket system is going to allow customers to input their destination through a touch screen or keyboard. The existing system does not allow the user to view the ticket prices. It is vital to publish the ticket prices accordingly, as customers affect to know the amount that they depart be charged. It does not immortalize the train departure and arrival times, and whether the customer wishes to buy ticket for a specific train. It must allow customers to choose their seats. Finally, the system should prompt customer to print the reception which includes the destination details and payment type. A recognise should cause been issued to state whether the purchase has been made successfully.In the send-off paragraph, the system does not check for systemation, such as when the user inserts their card, and the severity unavoidably to be checked as to whether the payment could be made hold that particular card.According to the second paragraph, when the user clicks on the start button, a menu of potential destinations pop up on the screen, along with a message asking the user to select a destination. erstwhile a destination has been selected, users ar prompted to input their credit card. However, the credit card game validity is checked and if the card is good, thusly user has ed to input a personal identifier as requested by the machine. The ticket is issued when the credit cards transaction has been buckramise successfully.In the second parag raph, the ticket system prompts the user with potential destinations whereas it could have provided with popular destinations. In such terminals popular destinations are normally displayed to help the user to select his destination quickly. Usually an impedance or an Over ground cover all destinations which can be reached by interchanging and taking number of trains then the user should be able to purchase ticket in aver to reach any destination. It could have excessively provided the user with a choice to search from a arguing of A-Z of stations. As mentioned before that there should be two types of payment methods The governing body procedure involves some(prenominal) validating the card as to whether the card is nonoperational valid in damage of not cancelled by the issuer referable to fraud lost/stolen reasons. The second type of validity is the PIN validity. If both ecesiss are successful then the issuer must authorise the payment in order to purchase the ticket.2. S olutions identifiedTo gain a clear and conk out understanding of the scenario, a more structured approach has been written as followsUser walks to a ticket machine and presses any button to set out a menu which displays a list of popular destinations accompanied by a message to select a destination. User can select their destination if listed in the popular destination otherwise they can choose to search for their destination from a list of stations in the A-Z of stations.As user finds their desired destination they then can choose to have their preferred type of ticket, this can be such as first/standard class ticket and/or return/single ticket.Once the destination and the type of ticket is selected the ticket machine prompts the user to watch payment. There are two types of payments can be made, likely by card or cash.If the customer chooses to pay by cash, and it can be inserted into the machine in the form of notes or coins. If the exact amount is remunerative the ticket wil l be issued, if more than essential is paid then the change will be given along with the ticket. If the customer chooses to pay by card as requested by the system, user can insert the card into the terminal. As the card is being inserted the validity of that card is checked with the issuer. Once the card is validated the user is then required to check the amount and enter the PIN in the terminal. The PIN is validated locally and upon correct entry of the PIN the ticket is issued along with the receipt and the cardholders account is charged accordingly with the correct amount.The aim of writing a structured approach gives a more clear understanding of the scenario and shows the events drop dead as a sequence.3. User unavoidablenesss definitionsThe User Requirement Specification specifies the prerequisites of the user taking the individual aspects into consideration in terms of the facility, equipment, and systems in terms of business office, throughput, operability, and applic able standards, which are the functions to be carried out, the data on which the system will operate, and the operating environment.The user requirements for a system should describe the utilitarian and non useful requirements so that they are understandable by system users without any adept knowledge.When we write the user requirement we should not write with practiced forms, flurry or diagrams. We should write in sincere language with simple table, forms and diagrams.4. System Requirements SpecificationsSystem requirements specification assist potential users to determine if the system condition touchs their needs or how the system must be modified to meet their needs. The system requirements help to consider all of the requirements before design begin. elaborate reviews of the requirements reveal omissions, misunderstanding and inconsistencies. System requirements specification should be correct, unambiguous, complete, consistent, verifiable, modifiable, and traceable, s pecify performance, and determine detailed functionality of the system.A specification can be in form of a written document, a set of graphical model, a formal mathematical model, and a collection of usage scenarios, prototype, or any junto of these. However, a standard template should be developed and use for a specification, arguing that this leads to requirements that are presented in a consistent and therefore more understandable manner.The requirement engineer gives final work product produced which is cognise as specification. It acts as the foundation for subsequent software program engineering activities. It describes all the related functions and the performance of a computer based system and the constrains that will govern its using.In the given scenario, we would consider all the omissions and ambiguities.First of all, the system did not provide all the functionality which usually a ticket egress system should contain. It does not function as it should and does not provide the user with any choice such as to cancel a ticket and buy another one. At times, there are new users who wish to purchase rail ticket from the machine and this system does not be given and provide any kind of help.Function Issuing Ticket comment Issuing the ticket when the user select their desired tickets and make the correctmoneyInputs Destination, child or Adult, Pay by card or cashOutput Their desired ticket to be issued with their payment receiptRequire Money, form of paymentPre- Condition Ticket will be validating between the user current place and the selected destination, otherwise user will have to pay the penalty fare.5. Actions performed in the ticket-issuing system6. Non-functional requirementsThe non functional requirements define system properties and constrains for an fashion model reliability, reception time and storage requirement. Constraints are I/O device capability, system representation, extra. Process requirement may also be specified mandating a particular CASE system, computer programming language. This non functional requirement may be more critical than function requirements. If these are not met the system is useless and the non functional requirement can be classified as three type of requirement6.1 ware requirement these requirement specify that the delivered product must behave in a particular way for example execution speed, and reliabilityThe user interface for Library system shall be implemented as simple HTML without frames or Java applets6.2. Organisational requirements which are a consequence of organisational policies and procedures example for these, process standard used, implementation requirementsThe system development process and deliverables define in XYZCo-SP-Stan-956.3. External requirements these could be from factors which are external to the system and its development process example interoperability requirements, legislative requirements.The system shall not disclose any personal informatio n about customer apart from their name and destination number to the operator of the systemAfter we discussed with all above mentioned Non-functional requirements, therefore we considered the product requirements should be determined for especially this scenario which include reliability and response time and should be contrasted with functional requirements that specify specific behavior or functions. And the product requirements have some additional attributes which areEfficiency alter the system to perform under different situation or context of useReliability This could be very useful for ATM or ticket issuing systemUsability This would help the user to access the system without any trouble or inconveniencePerformance This is almost relevant to reliability and check the system is able to work or not in the different environmentSpace Requirement This part of product requirement is very useful for the ticket issuing system when the system is bad-tempered or full occupied with user needs. So there it is need to be expanded or stabilized number of machine at the station8. Requirements ValidationProcess requirements validation is an integral part of software engineering. The main activity is to check requirements needed and available to start any particular project. As a consequence of requirements engineering however, the work products produced need to undergo an assessement for quality during a validation sequence. The purpose of requirements validation is to catch the specification to ensure that all software requirements have been stated unambiguously, such as consistencies, omissions, and error detected and corrected and that work products conform to the standards realized for the process, the project and the productThe autochthonic requirements validation mechanism is the formal technical review. The review team that validates requirements includes software engineers, customers, user and others stakeholders who examine the specification look for errors in content or interception, area may be clearing required. The process of requirements needs to check for consistency and completeness. During this process errors and inconsistencies will be identified and reduces future error.Basically the system should have requirement validation checklist which would help to the system to identify the accurate information whichAre requirement started clearly and Can they be misinterpreted?Is the source of the requirement identified e.g. a person, a regulation, or a document and the final stamen been examined by the primary source?Is the requirement bounded by any quantities terms?What other requirements match to this requirement?Does the requirement violate any system field of force?Properties of requirements validation are as follows Validity Consistency CompletenessIn order to validate the ticket issuing system requirements all the above properties of the requirements validation must be met. And when the user pay by card the system should validate whether it is valid for making the particular payment and validate the free fall no which has accepted or not therefore the validation must work out with final product it could be ticket or receipt10. The impact on cash paymentAfter having input the payment type which is cash, in this instance the customer may not have the exact amount to make the payment. If the user is making payment with a note, the machine should prompt the customer to take his change. However, the machine could also have displayed the amount to be charged and change to be given to the customer.