Elizamary Nascimento
Igor Steinmacher
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.
- 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. Google Scholar
Digital Library
- Almendros-Jiménez, J.M., Iribarne, L. 2004. Describing Use Cases with Activity Charts. In Metainformatics, Springer Berlin Heidelberg, pp. 141--159. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- 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.Google Scholar
- 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. Google ScholarDigital Library
- Basili, V., Rombach, H. 1988. The TAME Project: Towards Improvement Oriented Software Environments. In IEEE Transactions on Software Engineering, v. 14, pp. 758--773. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- Cockburn, A. 2005. Escrevendo casos de uso eficazes. Trad. Roberto Vedoato. Porto Alegre: Bookman, 2005.Google Scholar
- 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.Google Scholar
- 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. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- Jacobson, I. 1987. Object-oriented development in an industrial environment. In Conference on Object-Oriented Programming, Systems, Languages & Applications, pp. 183--191. Google ScholarDigital Library
- Jacobson, I.; Christerson, M.; Jonsson, P.; Overgaard, G. 1992. Object-Oriented Software Engineering: A Use-Case Driven Approach, Addison-Wesley, Reading, MA. Google Scholar
- Kulak, D.; Guiney, E. 2012. Use Cases: Requirements in Context, Addison-Wesley. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- 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.Google ScholarCross Ref
- 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. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- 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.Google ScholarCross Ref
- 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. Google ScholarDigital Library
- 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/.Google Scholar
- OMG Unified Modelling Language Superstructure -- version 2.3. http://www.omg.org/spec/UML/2.3/, 2010.Google Scholar
- 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. Google ScholarDigital Library
- Strauss, A., Corbin, J. 1998. Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory. 2 ed. SAGE Publications, LondonGoogle Scholar
- Tiwari S., Gupta A. 2015. A systematic literature review of use case specifications research. In Information and Software Technology, vol. 67, pp. 128--158. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- Wiegers, K.E. 1999. Writing quality requirements. In Software Development, v. 7, n. 5, p. 44--48. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- 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.Google ScholarCross Ref
Recommendations
Using the Base Semantics given by fUML for Verification
MODELSWARD 2014: Proceedings of the 2nd International Conference on Model-Driven Engineering and Software DevelopmentThe lack of formal foundations in the UML results in imprecise models, since UML defines the graphical notations and an abstract syntax for them, but not their formal semantics. Semantics for the key parts of activities and classes is defined by the ...
A New Approach for Generating LOTOS Specifications from UML Dynamic Models
C3S2E '15: Proceedings of the Eighth International C* Conference on Computer Science & Software EngineeringThe use of UML Statechart and Communication diagrams for modeling dynamic behaviors of systems is very widespread. UML diagrams support developers by means of visual conceptual illustrations. However, the lacks of firm semantics for these diagrams make ...
Formalizing the Semantics of UML Statecharts with Z*
CIT '04: Proceedings of the The Fourth International Conference on Computer and Information TechnologyUML is a semi-formal laguage, with a precisely defined syntax and static semantics but with an only informally specified dynamic semantics. UML statechart diagrams are a notation for describing behaviors in the framework of UML. UML statechart diagrams ...
Comments