This site uses only proprietary and third party technical cookies. By continuing to browse the site you are agreeing to our use of cookies. I agree I want to find out more
Browse the Department site:
Browse the Teaching site:

Programme of Course "Software Architectures"



Type of course unit:

Master Degree in Computer Science curriculum NEDAS: Compulsory
Master Degree in Computer Science curriculum UBIDIS: Compulsory

Level of course unit:

Postgraduate Degrees


1st semester

Number of credits:

Master Degree in Computer Science: 6 (workload 150 hours)


Henry Muccini (henrydotmucciniatdidotunivaqdotit)

2. Course Contents and learning outcomes (Dublin Descriptors)

Topics of the course include:

  • Components and Connectors
  • Architectural Styles
  • Architectural Views and Viewpoints
  • Architecture Descriptions and Architecture Description languages
  • Architecture Design Decisions
  • Architecting Situational Aware Applications

On successful completion of this course, the student should

  • KNOWLEDGE: This course introduces advanced concepts on Software Architecture. The first part of this course will provide advanced basic and advanced knowledge on software architecture, together with examples, and with a specific focus on architecture description language, and multi-view modeling. The second part will focus on architectural design decisions, architectural patterns, and architecture for adaptive systems. An objective is also to gain familiarity with software languages and tools which make easier the specification of component-based systems and architectures

ABILITY (ability to do): From the perspective of the "ability students will gain", the main objective of this course is to acquire a good knowledge on both theory and practice of Software Architecture and their usage in practice. At the end of this course, students will be able to correctly model a Software Architecture by using the appropriate tools. Through projects, students will practice the theoretical concepts previously described.

BEHAVIOR (ability to be): at the end of the learning process, the students will be conscious of how architectural choices impact on the quality of the developed software system.

4. Teaching methods and language


Reference textbooks

  • Len Bass, Paul Clements, and Rick Kazman, Software Architecture in Practice (3rd Edition). . Addison Wesley Professional. 2012.

Course information last updated on: 17 ottobre 2017, 00:34