As a developer I want to use user story to represent the requirements that lead to the definition of MVP and creation of mockups

• Taynah Almeida UFAM
• Ana Carolina Oran UFAM
• Gleison Santos UNIRIO
• Tayana Conte UFAM

DOI: https://doi.org/10.5753/sbqs.2017.15105

Abstract

User stories reflect user’s necessities and the MVP (Minimun Viable Product) aims to validate a software product with its users. Aiming to evaluate if user stories help to define MVP, this paper presents the results of an empirical study. The study shows positive acceptance of user story as a way to specify requirements, to define MVP, and build mockups, due to its ease of use and simplicity. The results show that the defects found after mockups’ inspection are related to human factors. The results show that the defects found after mockups’ inspection were not generated from defects inserted in the user story’s specification, but due the fact that the participants did not follow the specification for the building of the mockups.

References

Agarwal, N. and Rathod, U. (2006). Defining ‘success’ for software projects: An exploratory revelation. International journal of project management, v. 24, n. 4, pages 358–370.

Almeida, T., Oran, A.C., Santos, G. e Conte, T. (2017). Relatório técnico: Como desenvolvedor quero utilizar user story para representar os requisitos que levam à definição do MVP e criação de Mockups. TR-USES-2017-0014. Disponível em: http://uses.icomp.ufam.edu.br/relatorios-tecnicos/.

Basili, V. R. and Rombach, H. D. (1988). The TAME project: Towards improvement oriented software environments. IEEE Transactions on software engineering, v. 14, n. 6, pages 758–773.

Beck, K. (1999). Embracing change with extreme programming. Computer, v. 32, n. 10, pages 70–77.

Breitman, K. and do Prado Leite, J. C. S. (2002). Managing user stories. In International Workshop on Time-Constrained Requirements Engineering, page 168.

Breitman, K. and do Prado Leite, J. S. (2000). Scenario-based software process. In Proceedings Seventh IEEE International Conference and Workshop on the Engineering of Computer Based Systems (ECBS 2000), pages 375–380.

Caroli, P. (2015). Direto ao ponto: criando produtos de forma enxuta. Casa do Código.

Carrera Barroso, A., Solitario, J. J. and Iglesias Fernandez, C. A. (2012). Behaviour driven development for multi-agent systems. In: International Workshop on Infrastructures and Tools for Multiagent Systems, page 107-120.

Cooper, B. and Vlaskovits, P. (2010). The Entrepreneur’s Guide to Customer Development. Paperback.

Davis, F. D. (1989). Perceived usefulness, perceived ease of use, and user acceptance of information technology. MIS quarterly, pages 319–340.

Duc, A. N. and Abrahamsson, P. (2016). Minimum viable product or multiple facet product? the role of mvp in software startups. In International Conference on Agile Software Development, pages 118–130. Springer.Höst, M., Regnell, B. and Wohlin, C. (2000). Using students as subjects—a comparative study of students and professionals in lead-time impact assessment. Empirical Software Engineering, pages 201–214.

Keogh, E. (2010). BDD: A Lean Toolkit. In: Proc. of Lean Software & Systems Conf..

Khanh, N. T., Daengdej, J. and Arifin, H. H. (2017). Human stories: A new written technique in agile software requirements. In Proceedings of the 6th International Conference on Software and Computer Applications (ICSCA 2017), pages 15–22.

Laitenberger, O. and Dreyer, H. M. (1998). Evaluating the usefulness and the ease of use of a web-based section data collection tool. In Proceedings of the 5th International Symposium on Software Metrics, pages 122 132.

Lanubile, F., Mallardo, T. and Calefato, F. (2003). Tool support for Geographically Dispersed Inspection Teams. In Software Process Improvement and Practice, pages 217 – 231.

Lazăr, I., Motogna, S. and Pârv, B. (2010). Behaviour-driven development of foundational UML components. Electronic Notes in Theoretical Computer Science, pages 91 – 105.

Luna, E. R., Panach, J. I. and Grigera, J. et al. (2010). Incorporating usability requirements in a test/model-driven engineering approach. Journal of Web Engineering, v. 9, n. 2, pages 132 – 156.

Moogk, D. R. (2012). Minimum viable product and the importance of experimentation in technology startups. Technology Innovation Management, v. 2, n. 3, page 23.

Münch, J., Fagerholm, F., Johnson, P., Pirttilahti, J., Torkkel, J. and Jäarvinen, J. (2013). Creating minimum viable products in industry-academia collaborations. In Lean Enterprise Software and Systems, pages 137-151.

North, D. (2006). “Introducing bdd”, http://dannorth.net/introducing-bdd/, Março.

Paternoster, N., Giardino, C., Unterkalmsteiner, M., Gorschek, T. and Abrahamsson, P. (2014). Software development in startup companies: A systematic mapping study. In Information and Software Technology, v. 56, n. 10, pages 1200–1218.

Ries, E. (2014). A startup enxuta, Leya, 1ª edição.

Silva, T. R. (2016). Definition of a behavior-driven model for requirements specification and testing of interactive systems. In Requirements Engineering Conference (RE), 2016 IEEE 24th International, pages 444–449. IEEE.

Solis, C. and Wang, X. (2011). A study of the characteristics of behaviour driven development. In Software Engineering and Advanced Applications, pages 383–387.

Sutcliffe, A. (1998). Scenario-based requirements analysis. In: Requirements engineering, v. 3, n. 1, pages 48-65.

Travassos, G., Shull, F., Fredericks, M. and Basili, V. R. (1999). Detecting defects in object-oriented designs: using reading techniques to increase software quality. In ACM Sigplan Notices, v. 34, n. 10, pages 47–56. ACM.

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