Guilherme M. Tatibana
ABSTRACT
This paper aims to analyze and measure the effects caused in the software development process by approaching two different ways to present the specification of requirements to a team that follows agile practices and compare with the approach already used. The two approaches selected were to include the use case artifacts and activity diagram to the specification and perform measurement guided by the GQM approach. Finally, with the results obtained in the case study, the recommendation that was established for the team that participated is the use of the activity diagram artifact to specify user stories high value estimating.
- S. W. Ambler. 2017. Agile Modeling. http://agilemodeling.com. [Online; accessed March, 2018].Google Scholar
- V. Basili, A. Trendowicz, M. Kowalczyk, J. Heidrich, C. Seaman, J. Münch, and D. Rombach. 2014. Aligning Organizations Through Measurement: The GQM+Strategies Approach. Springer.Google Scholar
- D. Chappell. 201?. THE THREE ASPECTS OF SOFTWARE QUALITY: fUNCTIONAL, STRUCTURAL, AND PROCESS. http://www.davidchappell.com/writing/white_papers/The_Three_Aspects_of_Software_Quality_v1.0-Chappell.pdf. [Online; accessed March, 2018].Google Scholar
- I. Jacobson, M. Christerson, P. Jonsson, and G.r Overgaard. 1992. Object-Oriented Software Engineering: A Use-Case Driven Approach. Addison-Wesley.Google Scholar
- C. Larman. 2005. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development. Pearson Education.Google Scholar
- Elizamary Nascimento, Williamson Silva, Tayana Conte, Igor Steinmacher, Jobson Massollar, and Guilherme Horta Travassos. 2016. Is a Picture Worth a Thousand Words?: A Comparative Analysis of Using Textual and Graphical Approaches to Specify Use Cases. In Proceedings of the 30th Brazilian Symposium on Software Engineering (SBES '16). ACM, New York, NY, USA, 93--102. https://doi.org/10.1145/2973839.2973855Google ScholarDigital Library
- A. Rocha, G. Souza, and M. Barcellos. 2012. Medição de Software e Controle Estatístico de Processos. Ministério da Ciência, Tecnologia e Inovação.Google Scholar
- J. Sutherland and K. Schwaber. 2013. The Scrum Guide: The Definitive Guide to Scrum. Scrum.org and ScrumInc.Google Scholar
Index Terms
- Use case or activity diagram, that is the question!
Recommendations
UML diagram refinement (focusing on class- and use case diagrams)
ICSE '17: Proceedings of the 39th International Conference on Software EngineeringLarge and complicated UML models are not useful, because they are difficult to understand. This problem can be solved by using several diagrams of the same system at different levels of abstraction. Unfortunately, UML does not define an explicit set of ...
On well-formedness rules for UML use case diagram
WISM'10: Proceedings of the 2010 international conference on Web information systems and miningA software model is a widely used technique to specify software. A UML model may contain different diagrams and a diagram is built from different elements. Each element is restraint to certain constraint or well-formedness rules (WFR). Assurance to ...
Comments