Skip to main content

Introduction to Software Architecture

  • Chapter
Software Architecture

Part of the book series: Advanced Topics in Science and Technology in China ((ATSTC))

  • 2563 Accesses

Abstract

Compared to the traditional software several decades ago which were simple machine instructions or the combination of data structures and algorithms, current software are more complicated and harder to control and maintain. Normally, software systems are constructed through the assembly of components, whatever those which are developed according to new specifications or those which are stored in the libraries. In this circumstance, a team is needed to face different facets of the system. Some of them deal with the necessary functions to be implemented or reused in components, while others have to focus on how the work from different divisions can be coordinated and communicated correctly. Meanwhile, in this process some qualities of software must be guaranteed in order to approach the success.

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

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 149.00
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Bass, L., Clements, P. & Kazman, R. Software Architecture in Practice, 2nd ed.: Addison-Wesley/Pearson. 2003.

    Google Scholar 

  2. Bosch, J. Design and Use of Software Architecture: Adopting and Evolving a Product Line Approach: Addison-Wesley. 2000.

    Google Scholar 

  3. Brooks, F. P. The Mythical Man-Month: Essays on Software Engineering: Addison-Wesley. 1975.

    Google Scholar 

  4. Clements, P. & Northrop, L. Software Product Lines: Practices and Patterns: Addison-Wesley. 2002.

    Google Scholar 

  5. Clements, P., Bachmann, F. & Bass, L. Documenting Software Architectures: Views and Beyond Addison Wesley/Pearson. 2003a.

    Google Scholar 

  6. Clements, P., Kazman, R. & Klein, M. Evaluating Software Architectures: Methods and Case Studies: Pearson Education. 2003b.

    Google Scholar 

  7. Dijkstra, E. W. The Structure of the “THE” Multiprogramming System. Communications of the ACM 1968a(18).

    Google Scholar 

  8. Dijkstra, E. W. Goto Statement Considered Harmful. Communications of the ACM 1968b(11): 147–148.

    Article  Google Scholar 

  9. Fuggetta, A., Picco, G. P. & Vigna, G. Understanding Code Mobility. IEEE Transactions on Software Engineering, 1998(24): 342–361.

    Article  Google Scholar 

  10. Gacek, C., et al. On the Definition of Software System Architecture. Proceeding of the 1st International Workshop on Architectures for Software Systems, New York.1995:85–95.

    Google Scholar 

  11. Garlan, D. & Shaw, M. An Introduction to Software ArchitectureAdvances in Software Engineering and Knowledge Engineering. World Scientific. 1993.

    Google Scholar 

  12. Gilb, T. Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage, Butterworth-Heinemann 2005.

    Google Scholar 

  13. IEEE. IEEE Standard for a Software Quality Metrics Methodology. 1998.

    Google Scholar 

  14. Joyner, I. C++: A Critique of C++, 3rd ed.: http://burks.brighton. ac.uk/burks/p cinfo/p rogdocs/cp p crit/. 1996.

    Google Scholar 

  15. Kazman, R., et al. Saam: A Method for Analyzing the Properties of Software Architectures. Proceedings of 16th International Conference on Software Engineering, Sorrento, Italy.1994:81–90.

    Google Scholar 

  16. Kruchten, P., Obbink, H. & Stafford, J. The Past, Present, and Future of Software Architecture. IEEE Software, 2006(23): 22–30.

    Article  Google Scholar 

  17. Kruchten, P. B. The 4+1 View Model of Architecture. Software, IEEE, 1995(12): 42–50.

    Article  Google Scholar 

  18. Mei, H., Chang, J. & Yang, F. Software Component Composition Based on Adl and Middleware. Science in China (F) 2001(44): 136–151.

    Google Scholar 

  19. Ning, J. Q. A Component-Based Software Development Model. Proceedings. The Twentieth Annual International Computer Software and Applications Conference (COMPSAC’ 96) (Cat. No.96CB35986) 1996(389–394).

    Google Scholar 

  20. Parnas, D. L. On the Criteria for Decomposing Systems into Modules. Communications of the ACM 1972(15): 1053–1058.

    Article  Google Scholar 

  21. Parnas, D. L. On a “Buzzword“: Hierarchical Structure. Proceeding of lFIP Congress 1974, Amsterdam, North Holland.1974:336–339.

    Google Scholar 

  22. Parnas, D. L. On the Design and Development of Program Families. Software Engineering, IEEE Transactions on 1976(SE-2): 1–9.

    Article  Google Scholar 

  23. Perry, D. E. & Wolf, A. L. Foundations for the Study of Software Architecture. SIGSOFT Software Engineering Notes 1992(17): 40–52.

    Article  Google Scholar 

  24. Royce, W. E. & Royce, W. Software Architecture: Integrating Process and Technology. Quest 1991 (14): 2–15.

    Google Scholar 

  25. Shaw, M. & Garlan, D. Software Architecture: Perspectives on an Emerging Discipline, Prentice Ha11.1996.

    Google Scholar 

Download references

Rights and permissions

Reprints and permissions

Copyright information

© 2008 Zhejiang University Press, Hangzhou and Springer-Verlag GmbH Berlin Heidelberg

About this chapter

Cite this chapter

(2008). Introduction to Software Architecture. In: Software Architecture. Advanced Topics in Science and Technology in China. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-74343-9_1

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-74343-9_1

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-74342-2

  • Online ISBN: 978-3-540-74343-9

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics