Juliana Medeiros
Alexandre Vasconcelos
Miguel Goulão
ABSTRACT
The agile manifesto highlights a frequent communication with the customer to detail his/her needs and to validate the software requirements through frequent software deliveries. So, the agile methods treat the Software Requirements Specification (SRS) differently from the traditional development methods. User stories are one of the most widely used approaches to specify requirements in agile projects. However, empirical studies in the industry point out that user stories are targeted to customers, only cover simple functional requirements visible to the users, and do not address system and non-functional requirements that are also required for coding, testing, and maintaining. We propose an approach to specify requirements based on design practices targeted to the developer. We conducted an industrial case study during eight months to evaluate the proposed approach. The initial findings indicate that the SRS is closer to what will be implemented, and it meets the developers' expectations.
- Agile Manifesto. Manifesto for Agile Software Development. Available: http://www.agilemanifesto.org/. 2001.Google Scholar
- VersionOne. 9TH Annual State of Agile Survey. Available: http://info.versionone.com/state-of-agile-development-survey-ninth.html. 2015.Google Scholar
- Heikkilä, V. T., Damian, D., Lassenius, C., and Paasivaara, M. A Mapping Study on Requirements Engineering in Agile Software Development, 41st Euromicro, Funchal. 2015. Google ScholarDigital Library
- Read, A. and Briggs, R.O. The Many Lives of an Agile Story: Design Processes, Design Products, and Understandings in a Large-Scale Agile Development Project. 45th Hawaü International Conference, pp.5319,5328. 2012. Google ScholarDigital Library
- Daneva, M., Van Der Veen, E., Amrit, C., Ghaisas, S., Sikkel, K., Kumar, R., Ajmeri, N., Wieringa, R. Agile requirements prioritization in large-scale outsourced system projects: An empirical study. J. Syst. Soft. 86, 5. 2013. Google ScholarDigital Library
- Medeiros, J., Goulão, M., Vasconcelos, A., and Silva, C. Towards a model about quality of software requirements specification in agile projects. 10th QUATIC. Lisbon, Portugal. 2016.Google Scholar
- Povilaitis, S. Acceptance Criteria. Available: http://www.leadingagile.com/2014/09/acceptance-criteria/. 2014.Google Scholar
- Heck, P. and Zaidman, A. A quality framework for agile requirements: a practitioner's perspective. http://arxiv.org/abs/1406.4692.2014.Google Scholar
- Bjarnason, E., Wnuk, K. and Regnell, B. A case study on benefits and side-effects of agile practices in large-scale requirements engineering. 1st AREW. ACM, USA. 2011. Google ScholarDigital Library
- Lee,J.C, Judge,T.K, McCrickard, D.S. Evaluating eXtreme scenario-based design in a distributed agile team. CHI EA. New York, USA, 863--877. 2011. Google ScholarDigital Library
- Haugset,B., Stalhane,T. Automated Acceptance Testing as an Agile Requirements Engineering Practice. 45th HICSS, Maui, HI, pp. 5289--5298. 2012. Google ScholarDigital Library
- Hirschheim, R., Klein, K., and Lyytinen, Kalle. Information Systems Development and Data Modeling: Conceptual and Philosophical Foundations. Cambridge Univ., USA. 1995. Google ScholarDigital Library
- Loucopoulos, P., Zicari, R. Conceptual Modeling, Databases and CASE: An Integrated View of Information System Development. John Wiley & Sons, New York, USA. 1992. Google ScholarDigital Library
- Olivé, A. Conceptual Modeling of Information Systems, Springer Verlag, ISBN 978-3-540-39389-7. 2007. Google ScholarDigital Library
- Schwaber, K. and Beedle, M. Agile Software Development with Scrum. Prentice Hall PTR, NJ, USA. 2001. Google ScholarDigital Library
- Beck, K. Extreme Programming Explained: Embrace Change. Addison-Wesley, Boston, MA, USA. 1999. Google ScholarDigital Library
- Agile Alliance. Practices Map. Available at: http://guide.agilealliance.org/subway.html. 2016.Google Scholar
- Cohn, M. User Stories Applied: For Agile Software Development. Addison Wesley, Redwood, CA, USA. 2004. Google ScholarDigital Library
- Ricca, F., Scanniello, G., Torchiano, M., Reggio, G., and Astesiano, E. Assessing the Effect of Screen Mockups on the Comprehension of Functional Requirements. ACM Trans. Softw. Eng. Methodol. 24, 1. 2014. Google ScholarDigital Library
- Rivero, J.M., Grigera, J., Rossi, G., Luna, E. R., Montero, F., Gaedke, M. Mockup-Driven Development: Providing agile support for Model-Driven Web Engineering, IST, 56,6. 2014. Google ScholarDigital Library
- Ferreira, J., Noble, J. and Biddle, R. Agile Development Iterations and UI Design, Agile Conference (AGILE), Washington, DC, pp. 50--58. 2007. Google ScholarDigital Library
- Whichard, G. Definition of Done vs. Acceptance Criteria, http://www.governmentciomagazine.com/2014/08/definition-done-vs-acceptance-criteria. 2014.Google Scholar
- Mamoli, S. On Acceptance Criteria for User Stories. Available: http://nomad8.com/acceptance_criteria/. 2010.Google Scholar
- Medeiros, J., Alves, D., Wanderley, E., Vasconcelos, A. and Silva, C. Requirements Engineering in Agile Projects: A Systematic Mapping based in Evidences of Industry. ESELAW, CIBSE. Peru, pp.460--476. 2015.Google Scholar
- Medeiros, F., Medeiros, J., Ayres, F., Viana, C., Rocha, J., Viegas, V., Mendes, E., Santos, A. An Information System to Support the Anti-doping Process. Information Science and Applications (ICISA). Springer Singapore. 2016.Google Scholar
- Wohlin, C., Höst, M., and Henningsson, K. Empirical Research Methods in Software Engineering. Lecture notes in Computer Science, 2765 7--23. 2003. Google ScholarCross Ref
- Runeson, P. and Martin, H. Guidelines for conducting and reporting case study research in software engineering. Empirical Software. Eng. 14, 2, 131--164. 2009. Google ScholarDigital Library
- ISO/IEEE 830-1998. Recommended Practice for Software Requirements Specifications, IEEE. 1998.Google Scholar
- Batool, A., Hafeez, Y., Asghar, S., Abbas, M.A., Hassan, M.S.. A Scrum Framework for Requirement Engineering Practices. ISSN: 2306-1448 (online). 2013.Google Scholar
- Gebhart, M., Giessler., P., Burkhardt, P., Abeck, S. Quality-Oriented Requirements Engineering for Agile Development of RESTful Participation Service. ICSEA. 2014.Google Scholar
- F. Wanderley, A. Silva, J. Araujo and D. S. Silveira. SnapMind: A framework to support consistency and validation of model-based requirements in agile development, IEEE 4th MoDRE, Karlskrona, Sweden. 2014.Google Scholar
Index Terms
- An approach based on design practices to specify requirements in agile projects
Recommendations
Best managerial practices in agile development
ACM SE '14: Proceedings of the 2014 ACM Southeast Regional ConferenceAgile development has been gaining momentum over the year. It practices are perceived by some to be the best for software development. This work investigates agile best development and managerial practices, specially the benefits for optimizing the ...
Scope Determined (D) and Scope Determining (G) Requirements: A New Categorization of Functional Requirements
Requirements Engineering: Foundation for Software QualityAbstractContext: Some believe that Requirements Engineering (RE) for a computer-based system (CBS) should be done up front, producing a complete requirements specification before any of the CBS’s software (SW) is written. Problem: A common complaint is ...
Adopting to Agile Software Development
Abstract Agile software development can be made successful, but there is no well-defined way how to achieve this. The problem is that the successful adoption of agile methods and practices is a complex process and this process should be customizable for ...
Comments