Skip to main content

Methodological Framework for the Transition from Requirements to Software Architectures

  • Conference paper
  • First Online:
  • 1448 Accesses

Abstract

The quality of information systems heavily depends on software requirements engineering and software architecting. Both activities are the foundation for subsequent tasks, such as software development project planning, implementation, or maintenance. This paper introduces a methodological framework to support the transition from requirements to architectures. The framework consists of a process and different process modules (e.g., for systematic software architecture style selection). We also present a case study which shows higher modularity and lower coupling of architectures created using the proposed framework when compared to architectures created without the framework.

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

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   169.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   219.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD   219.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

References

  1. Amyot D, Mussbacher G (2001) Bridging the requirements/design gap in dynamic systems with use case maps (UCMs). In: 23rd International conference on software engineering, Toronto, Canada, pp 743–744

    Google Scholar 

  2. Avgeriou P, Grundy J, Hall JG, Lago P, Mistrik I (2011) Relating software requirements and architectures. Springer, Berlin

    Book  Google Scholar 

  3. Buschmann F (2009) Introducing the pragmatic architect. IEEE Software 26(5):10–11

    Article  Google Scholar 

  4. Dromey RG (2003) From requirements to design: formalizing the key steps. In: First international conference on software engineering and formal methods, Brisbane, Australia. IEEE Computer Society, pp 2–11

    Google Scholar 

  5. Feather MS, Fickas S, Finkelstein A, van Lamsweerde A (1997) Requirements and specification exemplars. Auto Software Eng 4(4):419–438

    Article  Google Scholar 

  6. Finney K (1996) Mathematical notation in formal specification: too difficult for the masses? IEEE T Software Eng 22(2):158–159

    Article  Google Scholar 

  7. Galster M, Eberlein A (2011) Facilitating software architecting by ranking requirements based on their impact on the architecture process. In: 18th IEEE international conference and workshops on the engineering of computer-based systems (ECBS), Las Vegas, NV, IEEE Computer Society, pp 232–240

    Google Scholar 

  8. Galster M, Eberlein A, Moussavi M (2007) Atomic requirements for software architecting. In: International conference on software engineering and applications (SEA'07), Cambridge, MA, Acta Press, pp 143–148

    Google Scholar 

  9. Galster M, Eberlein A, Moussavi M (2008) Defining the output of a software architecture process. In: International conference on software engineering and applications (SEA'08), Orlando, FL, Acta Press, pp 64–69

    Google Scholar 

  10. Galster M, Eberlein A, Moussavi M (2008) Early assessment of software architecture qualities. In: 2nd IEEE international conference on research challenges in information science, Marrakech, Morocco, IEEE Computer Society, pp 81–86

    Google Scholar 

  11. Galster M, Eberlein A, Moussavi M (2010) Systematic selection of software architecture styles. IET Software 4(5):349–360

    Article  Google Scholar 

  12. Galster M, Eberlein A, Moussavi M (2010) Textual software requirements specifications in the context of software architecting. In: 22nd International conference on software engineering and knowledge engineering, Redwood City, CA, KSI, pp 42–47

    Google Scholar 

  13. Gonzalez-Perez C, Henderson-Sellers B, Dromey RG (2005) A metamodel for the behavior trees modelling technique. In: Third international conference on information technology and applications, Sydney, Australia, IEEE Conputer Society, pp 35–39

    Google Scholar 

  14. Herrmann A, Paech B, Plaza D (2006) ICRAD: an integrated process for the solution of requirements conflicts and architectural design. Int J Softw Eng Know 16(6):917–950

    Article  Google Scholar 

  15. Kitchenham B, Pickard L, Pfleeger SL (1995) Case studies for method and tool evaluation. IEEE Software 12(4):52–62

    Article  Google Scholar 

  16. Kitchenham BA, Pfleeger SL, Pickard LM, Jones PW, Hoaglin DC, Emam KE, Rosenberg J (2002) Preliminary guidelines for empirical research in software engineering. IEEE T Software Eng 28(2):721–734

    Article  Google Scholar 

  17. Lau K-K, Nordin A, Rana T, Taweel F (2010) Constructing component-based systems directly from requirements using incremental composition. In: 36th EUROMICRO conference on software engineering and advanced applications, Lille, France, IEEE Computer Society, pp 85–93

    Google Scholar 

  18. Nuseibeh B (2001) Weaving together requirements and architectures. IEEE Software 34(3):115–117

    Google Scholar 

  19. Pohl K, Sikora E (2007) COSMOD-RE: supporting the co-design of requirements and architectural artifacts. In: 15th IEEE international conference on requirements engineering, Delhi, India, IEEE Computer Society, pp 258–261

    Google Scholar 

  20. Radice RA, Roth NK, O'Hara AC, Ciarfella WA (1985) A programming process architecture. IBM Syst J 24(2):79–90

    Article  Google Scholar 

  21. Rapanotti L, Hall JG, Jackson M, Nuseibeh B (2004) Architecture-driven problem decomposition. In: 12th International requirements engineering conference, Kyoto, Japan, IEEE Computer Society, pp 80–89

    Google Scholar 

  22. Runeson P, Hoest M (2009) Guidelines for conducting and reporting case study research in software engineering. Empir Softw Eng 14(2):131–164

    Article  Google Scholar 

  23. Sangwan R, Neill C, Bass M, Houda ZE (2008) Integrating a software architecture-centric method into object-oriented analysis and design. J Syst Softw 81(5):727–746

    Article  Google Scholar 

  24. Sommerville I, Sawyer P (1997) Requirements engineering – a good practice guide. Wiley, New York, NY

    MATH  Google Scholar 

  25. Svahnberg M, Aurum A, Wohlin C (2008) Using students as subjects – an empirical evaluation. In: 2nd International symposium on empirical software engineering and management, Kaiserslautern, Germany, ACM, pp 288–290

    Google Scholar 

  26. van Heesch U, Avgeriou P (2011) Mature architecting – a survey about the reasoning process of professional architects. In: 9th Working IEEE/IFIP conference on software architecture, Boulder, CO, IEEE Computer Society, pp 260–269

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Matthias Galster .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2013 Springer Science+Business Media, LLC

About this paper

Cite this paper

Galster, M., Eberlein, A., Jiang, L. (2013). Methodological Framework for the Transition from Requirements to Software Architectures. In: Linger, H., Fisher, J., Barnden, A., Barry, C., Lang, M., Schneider, C. (eds) Building Sustainable Information Systems. Springer, Boston, MA. https://doi.org/10.1007/978-1-4614-7540-8_11

Download citation

  • DOI: https://doi.org/10.1007/978-1-4614-7540-8_11

  • Published:

  • Publisher Name: Springer, Boston, MA

  • Print ISBN: 978-1-4614-7539-2

  • Online ISBN: 978-1-4614-7540-8

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics