Programming

1.   Extreme programming expresses user requirements as stories, with each story written on a card.  Discuss the advantages and disadvantages of this approach to requirements description.
2.  Identify and briefly describe four types of requirements that may be defined for a computer-based system.
3.  Who should be involved in a requirements review?  Draw a process model showing how a requirements review might be organized.
4.  Using the technique suggested here, where natural language descriptions are presented in a standard format, write plausible user requirements for the following functions:
a)    An unattended petrol (gas) pump system that includes a credit card reader.  The customer swipes the card through the reader then specifies the amount of fuel required.  The fuel is delivered and the customer’s account debited.
b)    The cash-dispensing function in a bank ATM.
c)    The spelling-check and correcting function in a word processor.
5.  List and discuss four ways to elicit requirements from a client.
6.  Suggest how an engineer responsible for drawing up a system requirements specification might keep track of the relationships between functional and non-functional requirements.
7.  When emergency changes have to be made to systems, the system software may have to be modified before changes to the requirements have been approved. Suggest a model of a process for making these modifications that will ensure that the requirements document and the system implementation do not become inconsistent.

8. Define all the stakeholders for your project (software system you are developing).

9. Using one of the formats discussed in Chapter 4, write all the user requirements for your project.

10. Using one of the formats discussed in Chapter 4, write all the system requirements that correspond to the user requirements listed in question 9 above.