A*.
a) Explain what use cases and use case diagrams are, and how they can be used to
capture the functional requirements for a software system.
(5 marks)
b) Explain the role of pre-conditions and post-conditions in detailed use case
descriptions.
(3 marks)
c) Using the example of a simple booking system for a local taxi company, discuss in
detail the process you might follow to identify use cases for a new software system.
You should assume that the business is already operating, but without a computer
system.
(8 marks)
d) Briefly explain the difference between a use case and a scenario. Illustrate your
answer with an example use case and related scenario from the taxi booking system
discussed in part c) above. You do not need to give full details of the use case or
scenario.
(4 marks)
e) Explain how use cases and scenarios can be used later in the software development
life-cycle after requirements elicitation.
(5 marks)
A2.
a) For large systems, software quality management can be structured into THREE main
activities: quality assurance, quality planning, and quality control. Describe EACH of
these activities.
(6 marks)
b) Describe THREE software quality attributes which might form part of a quality plan.
(6 marks)
c) Give TWO examples of software quality control techniques, and explain how they
would be included in the Software Development Life Cycle (SDLC).
(6 marks)
d) The cost of improving software quality can be divided between prevention costs,
appraisal costs and failure costs. For EACH of these, give at least TWO specific
examples of activities which incur such costs, and comment on the relative cost
values.
(7 marks