Official course description:
AbstractThe design, development, and implementation of a software system requires the evaluation of several, often conflicting, aspects of the system and mastery of multiple tools and techniques. The aim of this course is to provide you with knowledge on how to design the architecture of software systems in a structured and systematic way that addresses the required functionality and supports the necessary system qualities. This requires a technical toolbox with concepts, methods, and principles to support the software design, implementation, and evaluation as much as a wider understanding of the context and domain of the system. Beyond the design of software architecture you will also learn about the tools and approaches that are used in recovering the architecture of a system by the analysis of its source code and version control information.
The design, development, and implementation of software system requires the evaluation of several, often conflicting, aspects of the system and mastery of multiple tools and techniques.
Successful students will acquire knowledge on how to design software systems from scratch in a structured and systematic way that addresses the required functionality and supports the necessary system qualities. Furthermore, they will be able to disseminate the architectural design as much as evaluate existing designs.
The students will also learn techniques and practices used for analyzing source code and related artifacts in order to recover the architecture of existing systems. In particular they will learn about data mining the meta-data present in version control repositories and programatically analyzing the source code of software systems.
Formal prerequisitesThe student should have attended and passed an introductory course in software development.
Intended learning outcomes
After the course, the student should be able to:
- Drive a software design process in a systematic and structured manner.
- Represent functionality and system qualities in an implementation by identifying how to make important decisions.
- Conduct architectural prototyping experiments.
- Recognize and apply architectural patterns and tactics.
- Evaluate an architectural design.
- Extract the architectural design of an existing system.
- Analyze and adapt the software design approach to support iterative and agile development
- Evaluate the appropriateness of a given architecture recovery techinque for a given scenario
Lectures, individual assignments and group-based project work.
Mandatory activitiesIn order for a course participant to be approved to participate in the final exam, he/she is required to have:
- Held at least one presentation of their work. A part of the deliverables (group and individual) have to be presented in the classroom either as group or as individual presentations.
- Have provided constructive feedback in the work of another group in the form of report review. Each of the course participants will have to review the report of another group and provide constructive feedback. Please note that the review of a report is only used as feedback offered from student to student and by no means affects the official assessment of the report or the participant´s grade. The same applies to the presentation.
The student will receive the grade NA (not approved) at the ordinary exam, if the mandatory activities are not approved and the student will use an exam attempt.
The course literature is published in the course page in LearnIT.
Student Activity BudgetEstimated distribution of learning activities for the typical student
- Preparation for lectures and exercises: 15%
- Lectures: 13%
- Exercises: 13%
- Assignments: 35%
- Project work, supervision included: 12%
- Exam with preparation: 12%
Ordinary examExam type:
D: Submission of written work with following oral, External (7-point scale)
D2G: Submission for groups with following oral exam supplemented by the submission. Shared responsibility for the report.
The student must:
- Submit the project report (as a group) The project report is the architectural description of the designed system. It serves as a documentation of the architectural design work and follows the methods applied in the course. The architectural description is submitted as a group and also contain sections of individual work (explicitly stated) where e.g. one member of the group has conducted an architectural reconstruction analysis. These sections are the individual assignment explained bellow.
- Submit at least one optional assignment (individual) The optional assignments are individual and submitted as part of the project report (group report) in a separate section/chapter where stated clearly the name of the student and subject of the assignment. Further information will be given during the course.
The oral exam is 30 minutes. The exam includes (a) a joint presentation of the deliverable as a group (10 minutes) and (b) an individual oral examination of each student based on the course curriculum (20 minutes incl. voting). The student assessment is based on the oral examination ((a) and (b) above) and takes weight on the deliverable (project report & individual assignment). M.Sc. students will be in particularly examined in the scope of the intended learning outcomes as defined for M.Sc. students.
Group and individual
- Group size: 2-5 students.
Mixed exam 2 : Joint student presentation followed by an individual dialogue. The group makes their presentations together and afterwards the students participate in the dialogue individually while the rest of the group is outside the room.