Abstract
User stories in software engineering serve the purpose of discovering requirements and are used as units of system development. When applying stories in a project, two elements seem to be crucial: the ability to write coherent sequences of events and the ability to transform these sequences into code quickly and resourcefully. In this paper, these qualities are reflected in a notation that can be described as “stories with notions”. This notation separates the story’s sequence of events from the description of terms used in this sequence. Such a formal separation does not limit and rather enhances invention, at the same time rising the level of consistence, and facilitating translation into models of code. This translation maps domain notions into static code constructs (classes, interfaces) and also maps stories into dynamic sequences of messages. With such a mapping, programming becomes equivalent to skilled transformation of user stories, thus giving shorter development cycles.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
References
Breitman, K., Leite, J.: Managing user stories. In: International Workshop on Time-Constrained Requirements Engineering (TCRE 2002) (2002), http://www.enel.ucalgary.ca/tcre02/
Cohn, M.: User Stories Applied. Addison-Wesley, Reading (2004)
Cockburn, A.: Agile Software Development. Addison-Wesley, Reading (2002)
Cockburn, A.: Structuring use cases with goals. Journal of Object-Oriented Programming 5, 56–62 (1997)
Constantine, L.L.: What do users want? Engineering usability into software. Windows Tech Journal (1995) (revised in 2000), http://www.foruse.com/articles/whatusers.htm
Ambler, S.W.: Agile data modeling (2005), http://www.agiledata.org/essays/agileDataModeling.html
Ambler, S.W.: Agile Modeling (AM) practices v2 (2005), http://www.agilemodeling.com/practices.htm
Gryczon, P., Stańczuk, P.: Obiektowy system konstrukcji scenariuszy przypadków uzycia (Object-oriented use case scenario construction system). Master’s thesis, Warsaw University of Technology (2002)
Śmiałek, M.: Profile suite for model transformations on the computation independent level. In: Jardim Nunes, N., Selic, B., Rodrigues da Silva, A., Toval Alvarez, A. (eds.) UML Satellite Activities 2004. LNCS, vol. 3297, pp. 264–268. Springer, Heidelberg (2005)
Fowler, M., Scott, K.: UML Distilled: A Brief Guide to the Standard Object Modeling Language. Addison-Wesley, Longman (2000)
Bell, A.E.: Death by UML fever. Queue 2, 72–80 (2004)
Ambler, S.W.: A roadmap for Agile MDA (2005), http://www.agilemodeling.com/essays/agileMDA.htm
Baumeister, H., Knapp, A., Wirsing, M.: Property-driven development. In: Cuellar, J.R., Liu, Z. (eds.) Proc. 2nd IEEE Int. Conf. Software Engineering and Formal Methods (SEFM 2004), IEEE Computer Society Press, Los Alamitos (2004)
Beck, K.: Extreme Programming Explained: Embrace Change. Addison-Wesley, Reading (2000)
Palmer, S.R., Felsing, J.M.: A Practical Guide to Feature-Driven Development. Prentice Hall PTR, Englewood Cliffs (2002)
Astels, D.: Refactoring with UML. In: XP 2002, The Third International Conference on eXtreme Programming (2002), http://www.xp2003.org/xp2002/
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2005 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Śmiałek, M. (2005). From User Stories to Code in One Day?. In: Baumeister, H., Marchesi, M., Holcombe, M. (eds) Extreme Programming and Agile Processes in Software Engineering. XP 2005. Lecture Notes in Computer Science, vol 3556. Springer, Berlin, Heidelberg. https://doi.org/10.1007/11499053_5
Download citation
DOI: https://doi.org/10.1007/11499053_5
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-26277-0
Online ISBN: 978-3-540-31487-5
eBook Packages: Computer ScienceComputer Science (R0)