Software Architectures, 7.5 credits

Learning outcomes

Knowledge and understanding
After completing the course, the student should be able to

• describe principles for software architectures,
• explain relevant methods for developing software architectures, and
• describe and analyze the internal and external factors relevant to software architectures.

Skills and Abilities
After completing the course, the student should be able to

• apply methods for developing software architectures, and
• be able to present and discuss relevant information orally, in writing and graphically.

evaluation ability and approach
After completing the course, the student should be able to

• value good collaboration and clear communication with different stakeholders and project staff, and
• evaluate different methods that are relevant to software architectures.

Content

The following elements are dealt with in the course

• the purposes of software architecture and the role and competencies of the software architect
• development methodology: phases and iterations
• documentation: stakeholders, views and models
• reuse and design
• requirements specification
• stakeholder requests and feedback
• priorities
• risks, assumptions, questions and dependencies
• architectural development strategy, and
• verification and validation.

Examinations and grades

Theory, 3.5 credits (Code: A001)
Grades used are Fail (F), Sufficient (E), Satisfactory (D), Good (C), Very Good (B) or Excellent (A).

Exercises, 4 credits (Code: A002)
Grades used are Fail (U) or Pass (G).

According to the Higher Education Ordinance, Chapter 6, Section 18, a grade is to be awarded on the completion of a course, unless otherwise prescribed by the university. The university may determine which grading system is to be used. The grade must be determined by a teacher specifically nominated by the university (the examiner).

In accordance with university regulations on grading systems for first and second-cycle courses and study programmes (Vice-Chancellor’s decision ORU 2018/00929), one of the following grades is to be used: fail (U), pass (G) or pass with distinction (VG). For courses included in an international master’s programme (60 or 120 credits) or offered to the university’s incoming exchange students, the A to F grading scale is to be used. The vice-chancellor, or a person appointed by them, may decide on exceptions from this provision for a specific course, if there are special grounds for doing so.

The grades used on this course are Fail (F), Sufficient (E), Satisfactory (D), Good (C), Very Good (B) or Excellent (A).

Comments on grades

Grades for the course are given by the grade from test A001, given that test A002 is approved.

Modes of assessment

• Theory (code A001): Written examination
• Excercises (code A002): Written assignment and oral examination

A retake will be scheduled to take place within eleven weeks of the regular examination.

For students with a documented disability, the university may approve applications for adapted or other modes of assessment.

For further information, see the university's local examination regulations.

Specific entry requirements

Software Engineering for MSc in Engineering, 15 Credits. The applicant must also have qualifications corresponding to the course "English 6" or "English B" from the Swedish Upper Secondary School.

For further information, see the university's admission regulations.

Other provisions

The course may be given in English.

Students who have been admitted to and registered on a course have the right to receive tuition and/or supervision for the duration of the time period specified for the particular course to which they were accepted (see, the university's admission regulations (in Swedish)). After that, the right to receive tuition and/or supervision expires.

Reading list and other learning resources