This paper introduces the topic of use cases for the capture and representation of requirements and then focuses on the associations between use cases. Specifically it makes clear the difference between the include and extend associations, and then goes on to argue why use case modellers should incorporate the more familiar aggregation and specialisation associations between use cases for the explicit representation of models at different levels of goal abstraction. The modelling experience reported here is drawn from a number of industrial case studies that specifically employ early lifecycle use case modelling for the purpose of improving project delivery through improvements to IT procurement.
|Number of pages||20|
|Journal||Journal of Object Technology|
|Publication status||Published - 2005|