TUCCA: improving the effectiveness of use case construction and requirement analysis

Most of the delivered software products are delivered with defects usually introduce in the communications and transformations among different levels of abstraction along the software development phases. Defects remain in the artifacts even though high quality, rigorous design, inspections and testing activities are carried out during software development. Therefore, every software development activity should be systematic and rigorous and whenever possible should embody the aim of finding defects. This paper presents results of a feasibility study that was carried out aiming at evaluating TUCCA $Technique for use case model construction and construction-based requirements document analysis. TUCCA is composed of two reading techniques: AGRT - actor goal reading technique whose objective is to determine the actors of the system and their goals and UCRT - use case reading technique whose objective is to determine the use case model. These techniques support the construction of the use case model and also embody a review of the requirements document. In this paper we show that TUCCA is effective in use case construction and defect detection; we detailed the results of TUCCAS's contribution for finding defects, comparing this technique with Checklist and PBR-User (perspective based reading - user view). The results motivate to investigate the relationship of inspection techniques embodying construction steps with the construction techniques embodying inspection steps, such as TUCCA, aiming at reducing the overall cost and increasing the effectiveness of the software development.

[1]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[2]  Jeffrey C. Carver,et al.  Knowledge-Sharing Issues in Experimental Software Engineering , 2004, Empirical Software Engineering.

[3]  Neil A. M. Maiden,et al.  Guiding use case authoring: results of an empirical study , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[4]  Forrest Shull,et al.  Developing techniques for using software documents: a series of empirical studies , 1998 .

[5]  Anderson Belgamo,et al.  Constructing Use Case Model by Using a Systematic Approach: Description of a Study , 2004, WER.

[6]  Bente Anda,et al.  Towards an inspection technique for use case models , 2002, SEKE '02.

[7]  Forrest Shull,et al.  How perspective-based reading can improve requirements inspections , 2000, Computer.

[8]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[9]  Alistair Cockburn,et al.  Writing Effective Use Cases , 2000 .

[10]  Daryl Kulak,et al.  Use cases: requirements in context , 2000, SOEN.

[11]  Geri Schneider,et al.  Applying Use Cases: A Practical Guide , 1998 .

[12]  Forrest Shull,et al.  The empirical investigation of Perspective-Based Reading , 1995, Empirical Software Engineering.

[13]  Jeffrey C. Carver,et al.  An empirical methodology for introducing software processes , 2001, ESEC/FSE-9.

[14]  Claes Wohlin,et al.  State‐of‐the‐art: software inspections after 25 years , 2002, Softw. Test. Verification Reliab..