Skip to main content
Log in

Reconstructing the past: the case of the Spadina Expressway

  • Original Article
  • Published:
Requirements Engineering Aims and scope Submit manuscript

Abstract

In order to build resilient systems that can be operational for a long time, it is important that analysts are able to model the evolution of the requirements of that system. The Evolving Intentions framework models how stakeholders’ goals change over time. In this work, our aim is to validate applicability and effectiveness of this technique on a substantial case. In the absence of ground truth about future evolutions, we used historical data and rational reconstruction to understand how a project evolved in the past. Seeking a well-documented project with varying stakeholder intentions over a substantial period of time, we selected requirements of the Toronto Spadina Expressway. In this paper, we report on the experience and the results of modeling this project over different time periods, which enabled us to assess the modeling and reasoning capabilities of the approach, its support for asking and answering ‘what if’ questions, and the maturity of the underlying tool support. We also demonstrate a novel process for creating time-based models through the construction and merging of scenarios.

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

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1
Fig. 2
Fig. 3

adapted from [1]

Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8
Fig. 9
Fig. 10
Fig. 11
Fig. 12
Fig. 13

Similar content being viewed by others

Notes

  1. http://www.cs.toronto.edu/ amgrubb/archive/REJ19-SI

  2. https://github.com/amgrubb/BloomingLeaf

References

  1. Alaney2k (Own work) (2009) Spadina Expressway route map. [CC BY 3.0], via Wikimedia Commons. https://commons.wikimedia.org/wiki/File:Spadina_Expressway_Route_Map.png. Accessed 05 Apr 2018

  2. Amyot D (2003) Introduction to the user requirements notation: learning by example. J Comput Netw 42(3):285–301

    Article  Google Scholar 

  3. Aprajita (2017) TimedGRL: specifying goal models over time. Master’s thesis, McGill University

  4. Aprajita, Luthra S, Mussbacher G (2017) Specifying evolving requirements models with TimedURN. In: Proceedings of the MiSE@ICSE’17, pp 26–32

  5. Aprajita, Mussbacher G (2016) TimedGRL: specifying goal models over time. In: Proceedings of MoDRE’16

  6. Baresi L, Pasquale L, Spoletini P (2010) Fuzzy goals for requirements-driven adaptation. In: Proceedings of the RE’10, pp 125–134

  7. Blazy B, DeLine A, Frey B, Miller M (2014) Software requirements specification (SRS) lane management system. CSE 435 Project, Michigan State University

  8. Chung L, Nixon BA, Yu E, Mylopoulos J (2000) Non-functional requirements in software engineering. Kluwer Academic Publishers, Norwell

    Book  Google Scholar 

  9. Colton TJ (1980) Big Daddy: Frederick G. Gardiner and the building of metropolitan Toronto. University of Toronto Press, Toronto

    Book  Google Scholar 

  10. Dalpiaz F, Borgida A, Horkoff J, Mylopoulos J (2013) Runtime goal models. In: Proceedings of the RCIS’13, pp 1–11

  11. Dardenne A, van Lamsweerde A, Fickas S (1993) Goal-directed requirements acquisition. Sci Comput Program 20(1–2):3–50

    Article  Google Scholar 

  12. Dutoit AH, Paech B (2001) Rationale management in software engineering. In: Chang S (ed) Handbook of software engineering and knowledge engineering, vol 1. World Scientific, Singapore

    Google Scholar 

  13. Ernst NA, Borgida A, Jureta I (2011) Finding incremental solutions for evolving requirements. In: Proceeding of the RE’11, pp 15–24

  14. Gans G (2008) An agent-based modeling and simulation methodology for strategic inter-organizational networks. Ph.D. thesis, RWTH Aachen University

  15. Giorgini P, Mylopoulos J, Nicchiarelli E, Sebastiani R (2003) Formal reasoning techniques for goal models. J Data Semant 1:1–20

    MATH  Google Scholar 

  16. Giorgini P, Mylopoulos J, Sebastiani R (2005) Goal-oriented requirements analysis and reasoning in the tropos methodology. J Eng Appl Artif Intell 18(2):159–171

    Article  Google Scholar 

  17. Grubb AM (2015) Adding temporal intention dynamics to goal modeling: a position paper. In: Proceedings of the MiSE@ICSE’15, pp 66–71

  18. Grubb AM (2019) Evolving Intentions: support for modeling and reasoning about requirements that change over time. Ph.D. thesis, University of Toronto

  19. Grubb AM, Chechik M (2016) Looking into the crystal ball: requirements evolution over time. In: Proceedings of the RE’16, pp 86–95

  20. Grubb AM, Chechik M (2017) Modeling and reasoning with changing intentions: an experiment. In: Proceeding of the RE’17, pp 164–173

  21. Grubb AM, Chechik M (2018) Bloomingleaf: a formal tool for requirements evolution over time. In: Proceedings of the RE’18, pp 490–491

  22. Hartmann T, Fouquet F, Nain G, Morin B, Klein J, Barais O, Le Traon Y (2014) A native versioning concept to support historized models at runtime. In: Proceedings of the MODELS’14, pp 252–268

  23. Horkoff J, Aydemir FB, Cardoso E, Li T, Maté A, Paja E, Salnitri M, Mylopoulos J, Giorgini P (2016) Goal-oriented requirements engineering: a systematic literature map. In: Proceedings of the RE’16, pp 106–115

  24. Jones S, Maiden N (2005) RESCUE: an integrated method for specifying requirements for complex socio-technical systems. In: Mate JL, Silva A (eds) Requirements engineering for sociotechnical systems. Information Resources Press, Arlington

    Google Scholar 

  25. Kang K, Cohen S, Hess J, Nowak W, Peterson S (1990) Feature-oriented domain analysis (FODA) feasubility study. Technical report, Software Engineering Institute, Carnegie Mellon University, Pittsburgh

  26. Kienzle J, Guelfi N, Mustafiz S (2010) Crisis management systems: a case study for aspect-oriented modeling. In: Katz S, Mezini M (eds) Transactions on aspect-oriented software development VII. Springer, Berlin, pp 1–22

    Google Scholar 

  27. Kuchcinski K, Szymanek R (2016) JaCoP—Java constraint programming solver. http://jacop.osolpro.com. Accessed 21 Feb 2016

  28. Lethbridge TC, Sim SE, Singer J (2005) Studying software engineers: data collection techniques for software field studies. Empir Softw Eng 10(3):311–341

    Article  Google Scholar 

  29. Letier E (2001) Reasoning about agents in goal-oriented requirements engineering. Ph.D. thesis, Universite Catholique de Louvain

  30. Luthra S, Aprajita, Mussbacher G (2018) Visualizing evolving requirements models with TimedURN. In: Proceedings of the MiSE@ICSE’18, pp 1–8

  31. Mens T, Demeyer S (2008) Software evolution, 1st edn. Springer, Berlin

    Book  Google Scholar 

  32. Naumann F, Freytag JC, Leser U (2003) Completeness of information sources. In: Proceedings of the DQCIS’03

  33. Nguyen CM, Sebastiani R, Giorgini P, Mylopoulos J (2017) Modeling and reasoning on requirements evolution with constrained goal models. In: Proceedings of the SEFM’17, pp 70–86

  34. Osbaldeston M (2008) Unbuilt Toronto: a history of the city that might have been. Dundurn, Saskatchewan

    Google Scholar 

  35. Paltor IP, Lilius J (1999) Digital sound recorder: a case study on designing embedded systems using the UML notation. Turku Centre for Computer Science, Turku

    Google Scholar 

  36. Rose A (1972) Governing metropolitan Toronto: a social and political analysis, 1953–1971. Institute of Governmental Studies, University of Berkley, Berkley

    Google Scholar 

  37. Runeson P, Höst M, Rainer A, Regnell B (2012) Case study research in software engineering—guidelines and examples. Wiley, New York

    Book  Google Scholar 

  38. Schmitz D (2010) Managing dynamic requirements knowledge : an agent-based approach. Ph.D. thesis, RWTH Aachen University

  39. Sebastiani R, Giorgini P, Mylopoulos J (2004) Simple and minimum-cost satisfiability for goal models. In: Proceedings of the CaiSE’04, pp 20–35

  40. Sewell J (1993) The shape of the city: Toronto struggles with modern planning. Heritage series. University of Toronto Press, Toronto

    Google Scholar 

  41. Sterman J (2000) Business dynamics: systems thinking and modeling for a complex world. McGraw-Hill, New York

    Google Scholar 

  42. van Lamsweerde A (2009) Requirements engineering—from system goals to UML models to software specifications. Wiley, New York

    Google Scholar 

  43. White R (2016) Planning Toronto: the planners, the plans, their legacies, 1940–1980. UBC Press, Vancouver

    Google Scholar 

  44. Yin RK (2003) Case study research: design and methods, 3rd edn. Sage, Thousand Oaks

    Google Scholar 

  45. Yu E (1997) Towards modeling and reasoning support for early-phase requirements engineering. In: Proceedings of the RE’97, pp 226–235

Download references

Acknowledgements

We thank the historical experts we interviewed, as well as the REJ reviewers. We also thank Boyue Caroline Hu for her assistance in conducting the expert interviews, and the members of the Modeling group in Toronto for their ongoing discussion of this work.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Alicia M. Grubb.

Additional information

Publisher's Note

Springer Nature remains neutral with regard to jurisdictional claims in published maps and institutional affiliations.

Rights and permissions

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Grubb, A.M., Chechik, M. Reconstructing the past: the case of the Spadina Expressway. Requirements Eng 25, 253–272 (2020). https://doi.org/10.1007/s00766-019-00321-0

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-019-00321-0

Keywords

Navigation