Abstract
In recent years, Agile methodologies have increased their relevance in software development, through the application of different testing techniques like unit or acceptance testing. Tests play in agile methodologies a similar role that in waterfall process models: check conformance. Nevertheless the scenario is not the same The contribution of this paper is to explain how the process can be modified to do early identification of hidden requirements (HR) using testing techniques in agile methodologies, specifically using failed tests. The result is an optimized agile process where it may be possible to reach the desired level of functionality in less iterations, but with a similar level of quality. Furthermore it might be necessary to re-think process elements role, e.g. tests, in the Agile context not assuming waterfall definition and scope.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Boehm, B.: A view of 20th and 21st century software engineering. In: ICSE 2006: Proceedings of the 28th international conference on Software engineering (2006)
Cohn, M.: User Stories Applied: For Agile Software Development. The Addison-Wesley Signature Series. Addison-Wesley Professional, Reading (2004)
Grünbacher, P., Hofer, C.: Complementing xp with requirements negotiation. In: Proceedings 3rd Int. Conf. Extreme Programming and Agile Processes in Software Engineering, pp. 105–108. Springer, Heidelberg (2002)
Dyba, T., Dingsoyr, T.: Information and Software Technology, no. 9-10 (August 2008)
Moore, J., Abran, A., Bourque, P., Dupuis, R.: Guide to the Software Engineering Body of Knowledge 2004 Version. IEEE Press, Los Alamitos (2004)
Rodriguez, P., Alarcon, P., Garbajosa, J.: Identification of hidden requirements from failed system test execution. In: STV 2008 6th Workshop on System Testing and Validation - In conjunction with ServiceWave (2008)
Rodriguez, P., Yague, A., Alarcon, P., Garbajosa, J.: Agile methodologies from the perspective of the specification of functional and not functional requirements. In: 13th Conference on Software Engineering and Databases (JISBD 2008) (2008)
Woit, D.M.: Requirements interaction management in an extreme programming environment: a case study. In: ICSE 2005: Proceedings of the 27th international conference on Software engineering, pp. 489–494 (2005)
Robinson, W.N., Pawlowski, S.D., Volkov, V.: Requirements interaction management. ACM Comput. Surv. 35(2), 132–190 (2003)
Zowghi, D., Paryani, S.: Teaching requirements engineering through role playing: Lessons learnt. In: IEEE International Conference on Requirements Engineering, p. 233 (2003)
Eberlein, A., Leite, J.: Agile requirements definition: A view from requirements engineering. In: International Workshop on Time-Constrained Requirements Engineering, Essen, Germany (September)
Boness, K., Harrison, R.: Goal sketching: Towards agile requirements engineering. In: International Conference on Software Engineering Advances, 2007. ICSEA 2007, pp. 71–71 (August 2007)
Beck, K., Andres, C.: Extreme Programming Explained: Embrace Change, 2nd edn. Addison-Wesley Professional, Reading (2004)
Gallardo-Valencia, R., Olivera, V., Sim, S.: Are use cases beneficial for developers using agile requirements? In: Fifth International Workshop on Comparative Evaluation in Requirements Engineering, 2007. CERE 2007, pp. 11–22 (October 2007)
Ribeiro, J.C., Araujo, J.: Asporas: A requirements agile approach based on scenarios and aspects. In: Second International Conference on Research Challenges in Information Science, 2008. RCIS 2008, pp. 313–324 (June 2008)
Connolly, D., Keenan, F., Ryder, B.: Tag oriented agile requirements identification. In: ECBS 2008: Proceedings of the 15th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems (ECBS 2008) (2008)
Gupta, A., Jalote, P.: An experimental evaluation of the effectiveness and efficiency of the test driven development. In: First International Symposium on Empirical Software Engineering and Measurement, 2007. ESEM 2007 (September 2007)
Desai, C., Janzen, D., Savage, K.: A survey of evidence for test-driven development in academia. SIGCSE Bull. 40(2), 97–101 (2008)
Ricca, F., Torchiano, M., Penta, M.D., Ceccato, M., Tonella, P.: Using acceptance tests as a support for clarifying requirements: A series of experiments. Information and Software Technology 51(2), 270–283 (2009)
Park, S.S., Maurer, F.: The benefits and challenges of executable acceptance testing. In: APOS 2008: Proceedings of the 2008 international workshop on Scrutinizing agile practices or shoot-out at the agile corral, pp. 19–22 (2008)
Ho, C.-W., Johnson, M., Williams, L., Maximilien, E.: On agile performance requirements specification and testing. In: Agile Conference, 2006 (July 2006)
Mugridge, R.: Managing agile project requirements with storytest-driven development. IEEE Software 25(1), 68–75 (2008)
Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice Hall PTR, Upper Saddle River (2001)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2009 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Yagüe, A., Rodríguez, P., Garbajosa, J. (2009). Optimizing Agile Processes by Early Identification of Hidden Requirements. In: Abrahamsson, P., Marchesi, M., Maurer, F. (eds) Agile Processes in Software Engineering and Extreme Programming. XP 2009. Lecture Notes in Business Information Processing, vol 31. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-01853-4_24
Download citation
DOI: https://doi.org/10.1007/978-3-642-01853-4_24
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-01852-7
Online ISBN: 978-3-642-01853-4
eBook Packages: Computer ScienceComputer Science (R0)