From User Stories to Code in One Day?

  • Michał Śmiałek
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3556)


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.


Sequence Diagram Index Card Case Tool User Story Good Story 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Breitman, K., Leite, J.: Managing user stories. In: International Workshop on Time-Constrained Requirements Engineering (TCRE 2002) (2002),
  2. 2.
    Cohn, M.: User Stories Applied. Addison-Wesley, Reading (2004)Google Scholar
  3. 3.
    Cockburn, A.: Agile Software Development. Addison-Wesley, Reading (2002)Google Scholar
  4. 4.
    Cockburn, A.: Structuring use cases with goals. Journal of Object-Oriented Programming 5, 56–62 (1997)Google Scholar
  5. 5.
    Constantine, L.L.: What do users want? Engineering usability into software. Windows Tech Journal (1995) (revised in 2000),
  6. 6.
    Ambler, S.W.: Agile data modeling (2005),
  7. 7.
    Ambler, S.W.: Agile Modeling (AM) practices v2 (2005),
  8. 8.
    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) Google Scholar
  9. 9.
    Ś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)CrossRefGoogle Scholar
  10. 10.
    Fowler, M., Scott, K.: UML Distilled: A Brief Guide to the Standard Object Modeling Language. Addison-Wesley, Longman (2000)Google Scholar
  11. 11.
    Bell, A.E.: Death by UML fever. Queue 2, 72–80 (2004)CrossRefGoogle Scholar
  12. 12.
    Ambler, S.W.: A roadmap for Agile MDA (2005),
  13. 13.
    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)Google Scholar
  14. 14.
    Beck, K.: Extreme Programming Explained: Embrace Change. Addison-Wesley, Reading (2000)Google Scholar
  15. 15.
    Palmer, S.R., Felsing, J.M.: A Practical Guide to Feature-Driven Development. Prentice Hall PTR, Englewood Cliffs (2002)Google Scholar
  16. 16.
    Astels, D.: Refactoring with UML. In: XP 2002, The Third International Conference on eXtreme Programming (2002),

Copyright information

© Springer-Verlag Berlin Heidelberg 2005

Authors and Affiliations

  • Michał Śmiałek
    • 1
  1. 1.Warsaw University of Technology and Infovide S.AWarsawPoland

Personalised recommendations