University Course in Software Requirements, Teacher's Notes
University Course in Software Requirements, Teacher's Notes
doc
Soren Lauesen 2005-06-14
university wanting a student administration system, the tennis club wanting a booking system.
Remember that there is no promise of delivering the system, only a promise of writing the
requirements specification.
Week 4. Chapter 6. Quality requirements. (Skip Chapter 5 for now.)
Home work: 6.9 (preferably case study 16.1, Journal Circulation, or 16.2, Ticket Machine).
Exercise 6.11 may be a good supplement.
Industry project: Monitor that the students make progress in establishing contacts.
Week 5. Chapter 7. Requirements in the product life cycle.
Run exercise 7.5 as an in-class exercise.
Home work:
Exercise 7.6 (not in the book): For the Journal Circulation project or the Ticket Machine, write
a plan for design, verification, and delivery of the product. In particular, describe in some
detail how you would verify each requirement.
Week 6. Chapter 8. Elicitation.
Run exercise 8.5 as an in-class exercise (for instance case study 16.5). If there are more than
13 students, make two or more focus groups.
Home work: 8.4 (preferably the industry project, but might also be case study 16.1, Journal
Circulation, or 16.2, Ticket Machine).
Industry project: Check that the projects are in a state where an elicitation plan can be made
(exercise 8.4).
Week 7. Chapter 9. Checking and validation.
Homework: 9.6 (preferably the student's own requirements for the case project, but the
Midland Hospital spec might be used too as explained in the exercise text).
Industry project: From this week and on, arrange for two or more project teams to present
some results of their industry project (preferably some requirements), their concerns and their
plans for the next weeks. The audience (or a pre-selected other team) should play the role of
customers asking questions about the requirements or the business consequences. Every now
and then they may change to the role of supportive sparring partners. (See the hints on page
xiii of the book.)
For the rest of the weeks, the pattern might be a supplementary topic followed by student presentations
of their industry projects, in the same way as in week 7.
Suggestions for supplementary topics
1.
Contracts and law, for instance as one or two guest lectures by a lawyer working in the IT
area.
2.
Chapter 5 and Lauesen (2004): COTS Tenders and Integration Requirements (available from
Lauesen's home page)
3.
User interface design, for instance based on Chapters 5-9 in Lauesen: User Interface Design A Software Engineering Perspective. These chapters show how to get from domain-level
requirements to a good user interface, i.e. a prototype with process descriptions for all buttons
and controls (mini-specs).
4.
Selected papers, for instance picked from the book's reference list. For each paper, discuss
how it relates to the industry projects.
Exam
Oral exam based on the student's requirements specification in the industry project.