research-article

Analysing Requirements Communication Using Use Case Specification and User stories

Authors:

Ana Carolina Oran,

Elizamary Nascimento,

Gleison Santos,

Tayana ConteAuthors Info & Claims

SBES '17: Proceedings of the XXXI Brazilian Symposium on Software Engineering

Pages 214 - 223

https://doi.org/10.1145/3131151.3131166

Published: 20 September 2017 Publication History

Abstract

Effective requirements communication is essential in software development projects due to the importance of understanding the requirements throughout the software development cycle. Software requirements can be specified in different formats, for instance using free texts or more structured forms, such as use cases and user stories used in Behavior Driven Development (BDD). We present a comparative analysis on the requirements communication dynamics using use case specification and user stories as the basis for mockups creation. We carried out an exploratory empirical study involving 16 students. The study comprised 3 steps: requirements specification, mockups construction, and inspection to investigate whether the mockups were in accordance with the specifications. Results show that there is no significant difference in using use case specification or user stories to communicate software requirements. Our findings suggest that different specification formats can provide similar results while communicating requirements, nonetheless the human factor should not be neglected.

References

[1]

A. Al-Rawasa and S. Easterbrook. 1996. Communication problems in requirements engineering: A field study, In Proc. of Conf. on Professional on Awareness in Software Engineering, London, 47--60.

[2]

B. Anda, H. Dreiem, D. Sjøberg and M. Jørgensen. 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, 487--502.

Digital Library

[3]

B. Anda, K. Hansen and G. Sand. 2009. An investigation of use case quality in a large safety-critical software development project. In Information and Software Technology, v. 51, n. 12, 1699--1711.

Digital Library

[4]

B. Anda and D. Sjøberg. 2002. Towards an inspection technique for use case models. In Proc. of the 14th Intl. Conf. on Software Engineering and Knowledge Engineering, ACM, NY, USA, 127--134.

Digital Library

[5]

A. Belgamo and Luiz E. G. Martins. 2000. Estudo comparativo sobre as técnicas de elicitação de requisitos do software. In XX Congresso Brasileiro da Sociedade Brasileira de Computação (SBC).

[6]

E. Bezerra. 2007. Princípios de Análise e Projeto de Sistemas com UML, Campus, 2a edição.

[7]

A. Ceverino e Fernando P. Nascimento. 2016. Utilização da técnica de desenvolvimento orientado por comportamento (BDD) no levantamento de requisitos. Revista Interdisciplinar Científica Aplicada, v.10, n.3, 40--51, TRIII 2016. ISSN 1980--7031.

[8]

D. Chelimsky, D. Astels, B. Helmkamp, D. North, Z. Dennis and A. Hellesoy. (2010). The RSpec Book: Behaviour Driven Development with Rspec. Cucumber, and Friends, Pragmatic Bookshelf.

Digital Library

[9]

A. Cockburn. 2001. Writing Effective Use Cases, Vol. 1, Addison-Wesley, Boston.

Digital Library

[10]

E. Evans. 2003. "Domain-Driven Design: Tacking Complexity In the Heart of Software". Boston, MA, USA: Addison-Wesley.

Digital Library

[11]

Daniel M. Fernández, S. Wagner, M. Kalinowski, M. Felderer, P. Mafra, A. Vetrò, T. Conte, et al. 2016. Naming the pain in requirements engineering. Empirical Software Engineering, 1--41.

[12]

K. Gohil, N. Alapati and S. Joglekar. 2011. Towards behavior driven operations (bdops). In: Intl. Conf. on Advances in Recent Technologies in Communication and Computing, 262 -264.

[13]

B. Hoisl, S. Sobernig and M. Strembeck. 2014. Comparing Three Notations for Defining Scenario-based Model Tests: A Controlled Experiment In 9th Intl. Conf. on the Quality of Information and Communications Technology (QUATIC 2014), 180--189.

[14]

M. Höst, B. Regnell and C. Wohlin. 2000. Using Students as Subjects -- A Comparative Study of Students and Professionals in Lead-Time Impact Assessment. In: Empirical Software Engineering. v. 5, n. 3, 201--214.

Digital Library

[15]

I. Ibriwesh, Sin-Ban Ho, I. Chai and Chuie-Hong Tan. 2017. A Controlled Experiment on Comparison of Data Perspectives for Software Requirements Documentation. Arabian Journal for Science and Engineering, 1--15.

[16]

I. Jacobson 1987. Object-oriented development in na industrial environment. In Conf. on Object-Oriented Programming, Systems, Languages & Applications, 183--191.

Digital Library

[17]

S. Lauesen and Mohammad A. Kuhail. 2012. Task descriptions versus use cases. Requirements Engineering, v. 17, n. 1, 3--18.

Digital Library

[18]

Esteban R. Luna, José I. Panach, J. Grigera, et al. 2010. Incorporating usability requirements in a test/model-driven web engineering approach. In: Journal of Web Engineering, v. 9, n. 2, 132--156.

Digital Library

[19]

M. Cohn. 2004. User stories applied: For agile software development. Addison-Wesley Professional.

Digital Library

[20]

Rafael M. Mello, Eldânae N. Teixeira, M. Schots, Cláudia M. L. Werner and Guilherme H. Travassos. 2014. Verification of Software Product Line Artefacts: A Checklist to Support Feature Model Inspections, Journal of Univ. Comp. Science, v. 20, 720--745.

[21]

V. Mikulovic and M. Heiss. 2006. How do I know what I have to do?: the role of the inquiry culture in requirements communication for distributed software development projects. In Proc. of the 28th Intl. Conf. on Software engineering, 921--925.

Digital Library

[22]

P. Mohagheghi, B. Anda, R. Conradi. 2005. Effort estimation of use cases for incremental large-scale software development. In 27th Intl. Conf. on Software Engineering, 303--311.

Digital Library

[23]

Ana C. Oran, E. Nascimento, G. Santos e T. Conte. 2017. Relatório técnico: Uma Análise sobre Comunicação de Requisitos Utilizando Especificação de Caso de Uso e User story. TR-USES-2017-0010. Disponível em: http://uses.icomp.ufam.edu.br/relatorios-tecnicos/.

[24]

Keith T. Phalp, J. Vincent and K. Cox. 2007. Assessing the quality of use case descriptions. In Software Quality Journal, v. 15, n. 1, 69--97.

Digital Library

[25]

Raquel O. Prates, Clarisse S. de Souza and Simone D. Barbosa. 2000. Methods and tools: a method for evaluating the communicability of user interfaces interactions, v. 7, n. 1, 31--38.

Digital Library

[26]

Carolyn B. Seaman. 1999. Qualitative methods in empirical studies of software engineering. IEEE Transactions on software engineering, v. 25, n. 4, 557--572.

Digital Library

[27]

Thiago R. Silva. 2016. Definition of a behavior-driven model for requirements specification and testing of interactive systems. In Requirements Engineering Conf., IEEE 24th Intl., 444--449.

[28]

J. Smart. 2014. BDD in Action: Behavior-Driven Development for the Whole Software Lifecycle. New York, USA: Manning Publications.

[29]

K. Stapel, E. Knauss and K. Schneider. 2009. Using flow to improve communication of requirements in globally distributed software projects. In Requirements: Communication, Understanding and Softskills. Collaboration and Intercultural Issues, 5--14. IEEE.

Digital Library

[30]

A. Strauss and J. Corbin. 2014. Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory, in Thousand Oaks, CA, SAGE publications.

[31]

S. Tiwari and A. Gupta. 2015. A systematic literature review of use case specifications research. In Information and Software Technology, v. 67, 128--158.

Digital Library

[32]

Guilherme H. Travassos, F. Shull, M. Fredericks and V. Basili. 1999. Detecting defects in object-oriented designs: using reading techniques to increase software quality, In Proc. of XIV ACM SIGPLAN conf. on Object-oriented programming, systems, languages, and applications, v. 34, n. 10, 47--56.

Digital Library

[33]

Yu-Cheng Tu, E. Tempero and C. Thomborson. 2016. An experiment on the impact of transparency on the effectiveness of requirements documents. Empirical Software Engineering, v. 21, n. 3, 1035--1066.

Digital Library

[34]

X. Wang, L. Zhao, Y. Wang and J. Sun. 2014. The Role of Requirements Engineering Practices in Agile Development: An Empirical Study. In Proc. of the Asia Pacific Requirements Engineering Symposium, ser. CCIS. Springer, v. 432, 195--209

[35]

A. Zeaaraoui, Z. Bougroun, M. G. Belkasmi and T. Bouchentouf. 2013. User stories template for object-oriented applications. In Innovative Computing Technology (INTECH), 407--410.

Cited By

Binamungu LMaro S(2023)Behaviour driven development: A systematic mapping studyJournal of Systems and Software10.1016/j.jss.2023.111749203(111749)Online publication date: Sep-2023
https://doi.org/10.1016/j.jss.2023.111749
Duarte JDamian AConte T(2022)What do students prefer - Use Cases, User Story or Design Thinking Techniques?Proceedings of the XXI Brazilian Symposium on Software Quality10.1145/3571473.3571475(1-10)Online publication date: 7-Nov-2022
https://dl.acm.org/doi/10.1145/3571473.3571475
de Oliveira DOliveira FPernencar Cde Morais BSilva JCosta APereira JSaboia I(2022)LICOR: Beyond the Design System. A Proposal to Empower Teams to Develop Software in Compliance with the Principles of Accessibility, Usability, and Privacy by Design in the Extreme Contexts and Challenging Domains Post-COVID-19HCI International 2022 – Late Breaking Posters10.1007/978-3-031-19679-9_18(139-147)Online publication date: 24-Nov-2022
https://doi.org/10.1007/978-3-031-19679-9_18
Show More Cited By

Index Terms

Analysing Requirements Communication Using Use Case Specification and User stories
1. Software and its engineering
  1. Software notations and tools
    1. System description languages
      1. Specification languages
      2. Unified Modeling Language (UML)

Recommendations

A framework for evaluating and improving requirements specifications based on the developers and testers perspective
Abstract
Requirements specifications are essential to properly communicate requirements among the software development team members. However, each role in the team has different informational needs in order to perform their activities. Thus, the ...
User Centered Non-Functional Requirements Specification – An Extended Use-Case Diagram
Abstract
Requirements Engineering (RE) activity is often initiated with vaguely specified software requirements. The ambiguities must be overcome to the extent possible when the requirements are specified. Both functional (FRs) and non-functional (NFRs) ...
Enriching user stories with usability features in a remote agile project: a case study
SBQS '22: Proceedings of the XXI Brazilian Symposium on Software Quality

Considering usability aspects in the early phases of software development can avoid rework to solve usability problems identified late. We can adopt Requirements Engineering methods to identify usability requirements that explore the end users’ ...

Comments

Information & Contributors

Information

Published In

cover image ACM Other conferences

SBES '17: Proceedings of the XXXI Brazilian Symposium on Software Engineering

September 2017

409 pages

ISBN:9781450353267

DOI:10.1145/3131151

Program Chairs:
José Carlos Maldonado
ICMC-USP
,
Fabiano Cutigi Ferrari
UFSCar
,
Uirá Kulesza
DIMAp/UFRN
,
Tayana Uchôa Conte
UFAM

Copyright © 2017 ACM.

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
CNPq: Conselho Nacional de Desenvolvimento Cientifico e Tecn
CAPES: Brazilian Higher Education Funding Council

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 20 September 2017

Permissions

Request permissions for this article.

Request Permissions

Check for updates

Author Tags

Qualifiers

Research-article
Research
Refereed limited

Conference

SBES'17

SBES'17: 31st Brazilian Symposium on Software Engineering

September 20 - 22, 2017

CE, Fortaleza, Brazil

Acceptance Rates

SBES '17 Paper Acceptance Rate 42 of 134 submissions, 31%;

Overall Acceptance Rate 147 of 427 submissions, 34%

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

6
Total Citations
View Citations
440
Total Downloads

Downloads (Last 12 months)25
Downloads (Last 6 weeks)2

Reflects downloads up to 08 Mar 2025

Other Metrics

View Author Metrics

Citations

Cited By

Binamungu LMaro S(2023)Behaviour driven development: A systematic mapping studyJournal of Systems and Software10.1016/j.jss.2023.111749203(111749)Online publication date: Sep-2023
https://doi.org/10.1016/j.jss.2023.111749
Duarte JDamian AConte T(2022)What do students prefer - Use Cases, User Story or Design Thinking Techniques?Proceedings of the XXI Brazilian Symposium on Software Quality10.1145/3571473.3571475(1-10)Online publication date: 7-Nov-2022
https://dl.acm.org/doi/10.1145/3571473.3571475
de Oliveira DOliveira FPernencar Cde Morais BSilva JCosta APereira JSaboia I(2022)LICOR: Beyond the Design System. A Proposal to Empower Teams to Develop Software in Compliance with the Principles of Accessibility, Usability, and Privacy by Design in the Extreme Contexts and Challenging Domains Post-COVID-19HCI International 2022 – Late Breaking Posters10.1007/978-3-031-19679-9_18(139-147)Online publication date: 24-Nov-2022
https://doi.org/10.1007/978-3-031-19679-9_18
Oran ASantos GGadelha BConte T(2021)A framework for evaluating and improving requirements specifications based on the developers and testers perspectiveRequirements Engineering10.1007/s00766-021-00352-626:4(481-508)Online publication date: 25-Jun-2021
https://dl.acm.org/doi/10.1007/s00766-021-00352-6
Marques AFerreira BLopes ASilva WCavalcante EDantas FBatista T(2020)Stimulating the development of soft skills in Software Engineering Education through Design ThinkingProceedings of the XXXIV Brazilian Symposium on Software Engineering10.1145/3422392.3422488(690-699)Online publication date: 21-Oct-2020
https://dl.acm.org/doi/10.1145/3422392.3422488
Oran AValentim NSantos GConte T(2019)Why use case specifications are hard to use in generating prototypes?IET Software10.1049/iet-sen.2018.523913:6(510-517)Online publication date: Dec-2019
https://doi.org/10.1049/iet-sen.2018.5239

View Options

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Publication

View options

PDF

View or Download as a PDF file.

eReader

View online with eReader.

Figures

Tables

Media

View Table of Conten