Course syllabus for Software Architecture

Course syllabus adopted 2021-02-17 by Head of Programme (or corresponding).

Overview

  • Swedish nameMjukvaruarkitektur
  • CodeDAT360
  • Credits7.5 Credits
  • OwnerTKITE
  • Education cycleFirst-cycle
  • Main field of studyComputer Science and Engineering, Software Engineering
  • DepartmentCOMPUTER SCIENCE AND ENGINEERING
  • GradingTH - Pass with distinction (5), Pass with credit (4), Pass (3), Fail

Course round 1

The course round is cancelled. For further questions, please contact the director of studies
  • Teaching language English
  • Application code 52127
  • Maximum participants10
  • Open for exchange studentsNo
  • Only students with the course round in the programme overview.

Credit distribution

0117 Examination 4.5 c
Grading: TH
4.5 c
  • Contact examiner
  • Contact examiner
0217 Written and oral assignments 3 c
Grading: UG
3 c

    Examiner

    Eligibility

    General entry requirements for bachelor's level (first cycle)
    Applicants enrolled in a programme at Chalmers where the course is included in the study programme are exempted from fulfilling the requirements above.

    Specific entry requirements

    The same as for the programme that owns the course.
    Applicants enrolled in a programme at Chalmers where the course is included in the study programme are exempted from fulfilling the requirements above.

    Course specific prerequisites

    The course DAT257 Agile software project management, the course DAT356 Requirements and user experience, or equivalent.

    Aim

    The aim of this course is to equip students with basic knowledge and skills about software architecture design and its role in the development and maintenance of software systems.

    Learning outcomes (after completion of the course the student should be able to)

    Knowledge and understanding
    • describe the role of an architect in a software development project, and what may be expected from such a person
    • explain common quality requirements, such as performance, security, and modifiability
    • describe different architectural styles and how they relate to specific quality properties of the architecture
    Competence and skills
    • document architectures using established methods
    • solicit requirements from stakeholders and describe these as quality requirements
    • express quality requirements using quality scenarios
    • create an architectural design of a system based on a case description in natural language
    Judgement and approach
    • reason about how different architectural styles, tactics or design alternatives meet the quality goals of a system

    Content

    This course covers various definitions of software architecture. We discuss the role and relevance of software architecture at different stages of development projects; we discuss the relation of architecture to requirements and system implementation; we discuss software architecture quality properties; we discuss various architectural styles and tactics; we discuss general software design principles; we discuss how to document and how to evaluate software architectures.

    Organisation

    The teaching consists of lectures, exercises and examination parts, as well as supervision in connection to the exercises. The teaching takes place at Campus Lindholmen.

    Literature

    Course literature to be announced the latest 8 weeks prior to the start of the course.

    Examination including compulsory elements

    The course is examined by an individual written exam carried out in an examination hall and written assignments. The assignments part is examined on the basis of solutions to compulsory problems handed in during the course and on the basis of individual contribution to the group work. Students are required to complete written self- and peer assessment forms during the course which will be part of the assessment of the student's individual contribution to the project.

    The course examiner may assess individual students in other ways than what is stated above if there are special reasons for doing so, for example if a student has a decision from Chalmers about disability study support.

    Software Architecture | Chalmers