Skip to main content
Log in

Use cases – Yesterday, today, and tomorrow

  • Expert’s voice
  • Published:
Software & Systems Modeling Aims and scope Submit manuscript

Abstract

To my knowledge, no other software engineering language construct as significant as use cases has been adopted so quickly and so widely among practitioners. I believe this is because use cases play a role in so many different aspects of software engineering.

Although I first used the term in 1986, I had actually been working on and evolving the concept of use cases since 1967. So many people have asked me how I came up with this concept that I decided to write this article to explain the origins and evolution of use cases. I’ll also summarize what they have helped us achieve so far, and then suggest a few improvements for the future.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Subscribe and save

Springer+
from €39.99 /Month
  • Starting from 10 chapters or articles per month
  • Access and download chapters and articles from more than 300k books and 2,500 journals
  • Cancel anytime
View plans

Buy Now

Price includes VAT (Germany)

Instant access to the full article PDF.

Similar content being viewed by others

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Ivar Jacobson Founder and Member of Advisory Board.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Jacobson, I. Use cases – Yesterday, today, and tomorrow. Softw Syst Model 3, 210–220 (2004). https://doi.org/10.1007/s10270-004-0060-3

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s10270-004-0060-3

Keywords