Download Ticket Issuing System Requirements-Software Requirements-Assignment Solution and more Exercises Software Project Management in PDF only on Docsity!
Instructions to Solve Assignments
The purpose of assignments is to give you hands on practice. It is expected that students will solve the assignments themselves. Following rules will apply during the evaluation of assignment.
- Cheating from any source will result in zero marks in the assignment.
- Any student found cheating in any two of the assignments submitted will be awarded "F" grade in the course.
- No assignment after due date will be accepted.
Incomplete and ambiguous requirements are open to multiple interpretations and assumptions which can lead to the development of poor quality or faulty software products. Consider the following set of requirements for a ticket issuing system and discover incomplete and ambiguous requirements. 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 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. 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.
Solution:
Following are incompleteness and ambiguities in the provided requirements:
- Is there an option to buy more than one tickets for a destination or only one ticket can be bought at one time?
- Is there an option to cancel the request?
- How should the system respond if an invalid card is input?
- What happens if customers try to put their card in before selecting a destination?
- Must the user press the start button again if they wish to buy another ticket to a different destination?
- Should the system only sell tickets between the station where the machine is situated and direct connections or should it include all possible destinations?
- What type of input device (touchscreen vs. keyboard) system supports?
- Train departure and arrival times. Do customers buy tickets for a specific train? 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.)
- Print receipt?
Question 2: Total Points (20)
The paper " A Structured Approach for Extracting Functional Requirements from Unclear Customers " describes a new approach to extract requirements specification in a systematic way. Your task is to find out the weaknesses in the previous approach and how this new structured approach overcomes these weaknesses to produce a well documented specification.
