skip to main content
10.1145/2973839.2973855acmotherconferencesArticle/Chapter ViewAbstractPublication PagessbesConference Proceedingsconference-collections
research-article

Is a Picture worth a Thousand Words?: A Comparative Analysis of Using Textual and Graphical Approaches to Specify Use Cases

Published: 19 September 2016 Publication History

Abstract

Use cases specifications are artifacts employed in all stages of software development, from the requirements elicitation to implementation. During this process, issues related to ambiguity, redundancy, inconsistency, and incompleteness can affect these specifications. These issues can harm software engineers' understanding and, consequently, affect the software quality. Given this context, this paper describes an empirical study to evaluate two different use cases specifications approaches (textual and graphical-based forms). We compared the approaches by assessing the degree of correctness and the time spent to generate the specifications. In addition, we performed an analysis focusing on evaluating the ease of use and usefulness of each approach. The quantitative results showed that textual form and graphical-based specifications presented similar levels of correctness and the time spent to generate them were also similar. The qualitative results indicated that the subjects had difficulties using both approaches; however, subjects stated that graphic-based specifications were easier and more useful to specify use cases.

References

[1]
Achour C.B., Rolland C., Souveyet C., Maiden N.A. 1999. Guiding use case authoring: results of an empirical study. In 4th IEEE Intl Symp. on Requirements Engineering, pp. 36--43.
[2]
Almendros-Jiménez, J.M., Iribarne, L. 2004. Describing Use Cases with Activity Charts. In Metainformatics, Springer Berlin Heidelberg, pp. 141--159.
[3]
Anda, B., Dreiem, H., Sjøberg, D., Jørgensen, M. 2001. Estimating software development effort based on use cases --experiences from industry. In UML 2001 - The Unified Modeling Language. Modeling Languages, Concepts, and Tools. Springer, Berlin Heidelberg, v. 2185, pp. 487--502.
[4]
Anda, B., Hansen, K., Sand, G. 2009. An investigation of use case quality in a large safety-critical software development project. In Information and Software Technology, v. 51, n.12, pp. 1699--1711.
[5]
Anda, B.; Jørgensen, M. 2000. Understanding use case models. In Beg, Borrow or Steal: Using Multidisciplinary Approaches to Software Engineering Research, (ICSE) Workshop, pp. 94--102.
[6]
Anda, B.; Sjøberg, D. 2002. Towards an inspection technique for use case models. In 14th Intl. Conf. on Software Engineering and Knowledge engineering (SEKE). pp. 127--134.
[7]
Basili, V., Rombach, H. 1988. The TAME Project: Towards Improvement Oriented Software Environments. In IEEE Transactions on Software Engineering, v. 14, pp. 758--773.
[8]
Bolloju, N., Sun, S. X. Y. 2012. Benefits of supplementing use case narratives with activity diagrams---An exploratory study. In: JSS v. 85(9), pp. 2182--2191.
[9]
Cockburn, A. 2005. Escrevendo casos de uso eficazes. Trad. Roberto Vedoato. Porto Alegre: Bookman, 2005.
[10]
Cox, K.; Jeffery, R.; Aurum, A. 2004. A Use Case Description Inspection Experiment. In University of New South Wales, School of Computer Science and Engineering, Technical report.
[11]
El-Attar, M., Miller, J. 2009. A subject-based empirical evaluation of SSUCDs performance in reducing inconsistencies in use case models. Empirical Software Engineering, v. 14, n. 5, pp. 477--512.
[12]
Gutiérrez, J. J., Nebut, C., Escalona, M. J., Mejías, M., Ramos, I. M. 2008. Visualization of Use Cases through Automatically Generated Activity Diagrams. In Model Driven Engineering Languages and Systems. Springer Berlin Heidelberg, v. 5301, pp. 83--96.
[13]
Jacobson, I. 1987. Object-oriented development in an industrial environment. In Conference on Object-Oriented Programming, Systems, Languages & Applications, pp. 183--191.
[14]
Jacobson, I.; Christerson, M.; Jonsson, P.; Overgaard, G. 1992. Object-Oriented Software Engineering: A Use-Case Driven Approach, Addison-Wesley, Reading, MA.
[15]
Kulak, D.; Guiney, E. 2012. Use Cases: Requirements in Context, Addison-Wesley.
[16]
Laitenberger, O., Dreyer, D.M. 1998. Evaluating the usefulness and the ease of use of a web-based inspection data collection tool. In Intl Software Metrics Symposium, 122--132.
[17]
Lanubile, F., Mallardo, T., Calefato, F., 2003. Tool support for Geographically Dispersed Inspection Teams. In Software Process Improvement and Practice, v. 8, pp. 217--231.
[18]
Larman, C. 2005. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, 3/e, Pearson Education India, 1--616.
[19]
Massollar, J. L., De Mello, R. M., Travassos, G. H. 2012. Structuring and Verifying Requirements Specifications through Activity Diagrams to Support the Semi-automated Generation of Functional Test Procedures. In Intl Conf. on the Quality of Information and Communications Technology, 2012. p. 239--244.
[20]
Mello, R. M, Massollar, J., Travassos, G. H. 2011. Técnica de inspeção baseada em checklist para identificação de defeitos em diagramas de atividades. In Simpósio Brasileiro de Qualidade de Software (SBQS), pp. 168--177.
[21]
Mohagheghi, P., Anda, B., Conradi, R. 2005. Effort estimation of use cases for incremental large-scale software development. In 27th Intl. Conf. on Software Engineering, pp. 303--311.
[22]
Nascimento, E. S., Silva, W. A. F., Conte, T., Steinmacher, I., Massollar, J., Travassos, G. H., "Relatório Técnico: Estudo Experimental sobre Diferentes Abordagens para Especificação de Casos de Uso", Relatório de número 004, 2016. Disponível em:https://uses.induspam.com/relatoriostecnicos/.
[23]
OMG Unified Modelling Language Superstructure -- version 2.3. http://www.omg.org/spec/UML/2.3/, 2010.
[24]
Phalp, K.T., Vincent, J.; Cox, K. 2007. Assessing the quality of use case descriptions. In Software Quality Journal, v. 15, n. 1, pp. 69--97.
[25]
Strauss, A., Corbin, J. 1998. Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory. 2 ed. SAGE Publications, London
[26]
Tiwari S., Gupta A. 2015. A systematic literature review of use case specifications research. In Information and Software Technology, vol. 67, pp. 128--158.
[27]
Tiwari, S., Gupta, A. 2013. A controlled experiment to assess the effectiveness of eight use case templates. In Asia--Pacific Software Engineering Conference (APSEC), pp. 207--214.
[28]
Wiegers, K.E. 1999. Writing quality requirements. In Software Development, v. 7, n. 5, p. 44--48.
[29]
Wöhlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., Wessl, A. 2000. Experimentation in software engineering: an introduction. Kluwer Academic Publishers.
[30]
Yue, T., Briand, L., Labiche, Y. 2010. An automated approach to transform use cases into activity diagrams, in: T. Khne, B. Selic, M.-P. Gervais, F. Terrier (Eds.), Modelling Foundations and Applications, LNCS, vol. 6138, Springer, Berlin Heidelberg, 2010, pp. 337--353.
[31]
Zhang, X., Auriol, G., Baron, C. 2010. Requirements establishment for complex product development using value-focused thinking. In: Intl. Conf. on Industrial Engineering and Engineering Management (IEEM), pp. 2531--2535.

Cited By

View all

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM Other conferences
SBES '16: Proceedings of the XXX Brazilian Symposium on Software Engineering
September 2016
167 pages
ISBN:9781450342018
DOI:10.1145/2973839
Publication rights licensed to ACM. ACM acknowledges that this contribution was authored or co-authored by an employee, contractor or affiliate of a national government. As such, the Government retains a nonexclusive, royalty-free right to publish or reproduce this article, or to allow others to do so, for Government purposes only.

In-Cooperation

  • SBC: Brazilian Computer Society

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 19 September 2016

Permissions

Request permissions for this article.

Check for updates

Author Tags

  1. UML
  2. Use cases specifications
  3. empirical study

Qualifiers

  • Research-article
  • Research
  • Refereed limited

Funding Sources

Conference

SBES '16
SBES '16: 30th Brazilian Symposium on Software Engineering
September 19 - 23, 2016
Maringá, Brazil

Acceptance Rates

Overall Acceptance Rate 147 of 427 submissions, 34%

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • 0
    Total Citations
  • 165
    Total Downloads
  • Downloads (Last 12 months)1
  • Downloads (Last 6 weeks)0
Reflects downloads up to 15 Feb 2025

Other Metrics

Citations

Cited By

View all

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Figures

Tables

Media

Share

Share

Share this Publication link

Share on social media