Requirements For Part Of A Ticket Issuing System

1059 Words5 Pages
1. Discover ambiguities or omissions in the following statement of requirements for part of a ticket-issuing system: An automated 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. 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. 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 Ans. The ambiguities…show more content…
Non-Functional Requirements: These are usually defined as the characteristics that a system should possess and these services are not concerned with the user requirements. These are more essential than the functional requirements The functional and the non-functional requirements are correlated with each other and hence there is a need to keep a track of the relationship between them. Maintaining a relationship between these two requirements is hard as the functional and non functional requirements may not work with each other. So, the engineer should first list all the requirements and should then identify the non functional requirements that are linked with the functional requirements. The systems engineer can also keep a track of this relationship by making a systems requirement document and maintaining a separate documentation for each of them. 3. How might you use a model of a system that already exists? Explain why it is not always necessary for such a system model to be complete and correct. Would the same be true if you were developing a model of a new system? Ans. The documentation of the existing system helps in understanding the functionality of the system and the pros and cons of the system which can be used as a basis when proposing a new system. Requirements of the new system can be derived from an existing systems. Utilization of the existing system reduces the cost and the time taken in developing a new system as the existing
Open Document