• Software Architecture

    • Software Architecture is a part of the engineering process for building applications and it is a core subject for a Computer Engineer.This course is part of the Software Engineering field and it is transverse to the Specific Training Module (Software Engineering).Within this field are also the subjects as Software Engineering, Software Design, Quality, Validation and Verification of Software Requirements Engineering and Modeling in Software Engineering Process.

      With the support of the Lifelong Learning Programme of the European Union.

      Computer Science School Logo
  • Readings
    • Notice: This bibliografy is valid only for the chapters published in a complete version. For a detailled information, every lecture has its own bibliography.

    •  

      Garland, Jeff and Anthony, Richard. 2003. Large-Scale Software Architecture: A Practical Guide using UML. s.l.: John Wiley & Sons, LTD, 2003. ISBN: 0 470 84849 9.

      • (Garland, et al., 2003) (COMP 1. Introduction)

      • (Garland, et al., 2003) (COMP 2. Roles of the Software Architect)

      • (Garland, et al., 2003) (COMP 1. Introduction)

      • (Garland, et al., 2003) (COMP 1.3 Architectural Viewpoint Sumary)

      • (Garland, et al., 2003) (COMP 3.1 Overview of Iterative Development [only the introduction], 3.1.1 Overall process phases and 3.1.2 Lifecycle stages)

      • (Garland, et al., 2003) (COMP 3.1.4 Start early, refine constantly)

      • (Garland, et al., 2003) (COMP 3.2.2 Additional requirements that impact architecture)

      • (Garland, et al., 2003) (COMP 3.2.3 Requirements tracing)

      • (Garland, et al., 2003) (COMP 1.3 Architectural viewpoint summay)

      • (Garland, et al., 2003) (COMP 5. UML Quick Tour)

      • (Garland, et al., 2003) (COMP 5.4 Managing Complexity)

      • (COMP 10.1.1 A Standard Organization for Documenting a View)

      Gorton, Ian. 2006. Essential Software Architecture. New York: Springer Berlin Heidelberg, 2006. ISBN-13 978-3-540-28713-1.

      • (Gorton, 2006) (COMP pags. 1 to 8)

      • (Gorton, 2006) (COMP 5.3 Validation)

      Bass, Len, Clements, Paul and Kazman, Rick. 2003. Software Architecture in Practice, Second Edition. Boston : Addison Wesley, 2003. ISBN: 0-321-15495-9.

      • (Bass, et al., 2003) (COMP 7.2 Designing the Architecture)

      • (Bass, et al., 2003) (COMP 4.4 Quality Attribute Scenarios in Practice)

      Clements, Paul, et al. 2010. Documenting Software Architecture. Boston : Pearson Education, Inc., 2010. ISBN-13: 978-0-321-55268-6

      • Prologue P.4. Architecture Styles (Pages 25-36)

      • Epilogue E.4. Documenting Architecture in an Agile Project (Pages 414-418)

      • (COMP P.2.3 Architecture Documentation and Quality Attributes)

      • (COMP P.2.7 Architectures That Change Faster Than You Can Document Them)

      • (COMP P.3 Architecture Views)
      • Cap. 1 Module Views

      • Cap. 2 A tour of some module styles (Páginas 49-122)

      Humble, Jez, y David Farley. Continuous Delivery. Addison-Wesley, 2010.

      • Cap. 3. Continuous Integration. (Páginas 55 – 82)

      Paper: Gade4all: Developing Multi-platform Videogames based on Domain Specific Languages and Model Driven Engineering

      http://www.ijimai.org/journal/sites/default/files/files/2013/06/ijimai20132_2_4_pdf_13724.pdf