Tool support for essential use cases to better capture software requirements

Massila Kamalrudin, John Grundy, John Hosking

Research output: Chapter in Book/Report/Conference proceedingConference PaperResearchpeer-review

22 Citations (Scopus)


Capturing software requirements from clients often leads to error prone and vague requirements documents. To surmount this issue, requirements engineers often choose to use UML models to capture their requirements. In this paper we discuss the use of Essential Use Cases (EUCs) as an alternative, user-centric representation which was developed to ease the process of capturing and describing requirements. However, EUCs are not commonly used in practice because, to our knowledge, no suitable tool support has been developed. In addition, requirements engineers face difficulties in finding the correct "essential" requirements (abstract interactions) in a time efficient manner. In order to overcome these problems, we have developed a prototype tool for automated tracing of abstract interactions. We describe the tool and compare the performance and correctness of the results provided by it to that of manual essential use case extraction efforts by a group of requirements engineers. The results of an end user study of the tool's usefulness and ease of use are also discussed.

Original languageEnglish
Title of host publicationASE'10 - Proceedings of the IEEE/ACM International Conference on Automated Software Engineering
Number of pages10
Publication statusPublished - 10 Dec 2010
Externally publishedYes
EventAutomated Software Engineering Conference 2010 - Antwerp, Belgium
Duration: 20 Sep 201024 Sep 2010
Conference number: 25th (Proceedings)


ConferenceAutomated Software Engineering Conference 2010
Abbreviated titleASE 2010
Internet address


  • Automated tracing tool
  • Essential use cases
  • Requirements extraction

Cite this