Software Architecture

2019-2020

Course Objective

Get acquainted with the field of software- and information architecture.
Understand the drivers behind architectural decisions. Be able to design
and reason about the architecture of non-trivial software systems.
Appreciate the role of the software architect.

Course Content

Students work in groups to design an architecture for a fictitious
software-intensive system. They have to develop different
representations (called views) of the architecture. These different
representations emphasize different concerns of people or organizations
that have a stake in the system. Each group will also be asked to
present their progress and engage in an architecture debate with the
class.

Teaching Methods

Two hours per week Lectures (l). Groupwork with a number of assignments
(pro) with 2 contact hours per week. Two hours per week Seminar (s).

Attendance of the first lecture is compulsory! Students are expected to
attend all presentation sessions and to engage in the architecture
debate with the presenting teams. Students are required to participate
in groupwork. Attendance of the scheduled contact hours is highly
recommended.

Method of Assessment

Type: Project assignments (A), Presentation (P), Written examination
(E).

Weight of each component: The main project assignments will be done as
groupwork and will account jointly for 75% of the final grade. The
weighted average score of the assignments should be at least 5.5.
Additional assignments may be "pass" or "fail". Presentations will be
prepared and performed as groupwork. They will be graded as either
“pass” or “fail”. The final written exam will regard the material
covered by the lectures. The score should be at least 5.5. It will
account for 25% of the final grade.

Compensation: Both the weighted average of the project assignments and
the final written exam MUST be 5.5 or higher. Compensation between the
two is not possible. Additionally, any "pass"/"fail"-assignments and
presentations must be "pass" in order to pass the course. Individual
project assignment grades may be lower than 5.5 and can be compensated
through other project assignments.

Mode of re-examination: failed project assignments can be revised and
resubmitted once; failed presentations and other pass/fail-assignments
can be retried once. The written exam can be recovered in the resit.

Literature

Len Bass et al, Software Architecture in Practice, 3rd Edition, 2012

Target Audience

mCS, mIS

Custom Course Registration

Registration is compulsory at least 4 weeks before the course starts. Group enrolment takes place in Canvas.

Explanation Canvas

Further information for this course will be made available online
(Canvas). All students must be enrolled in the course Canvas community.

Recommended background knowledge

Software Design (BSc)

General Information

Course Code X_400170
Credits 6 EC
Period P2
Course Level 400
Language of Tuition English
Faculty Faculty of Science
Course Coordinator prof. dr. P. Lago
Examiner prof. dr. P. Lago
Teaching Staff

Practical Information

You need to register for this course yourself

Last-minute registration is available for this course.

Teaching Methods Seminar, Lecture
Target audiences

This course is also available as: