Download Solution: Click to Download Solution
Solution File Name: RequirementEngineering.docx
Unzip Password: prestobear.com
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.
Write a set of non-functional requirements for the ticket-issuing system, setting out its expected reliability and response time.
Suggest how an engineer responsible for drawing up a system requirements specification might keep track of the relationships between functional and non-functional requirements.
Explain why the best programmers do not always make the best software managers. You may find it helpful to base your answer on the list of management activities in Section 22.1.
In addition to the risks shown in Figure 22.1, identify at least six other possible risks that could arise in software projects.
Fixed-price contracts, where the contractor bids a fixed price to complete a system development, may be used to move project risk from client to contractor. If anything goes wrong, the contractor has to pay. Suggest how the use of such contracts may increase the likelihood that product risks will arise.