Software Design Patterns Code:  22.617    :  6
View general information   Description   The subject within the syllabus as a whole   Prior knowledge   Information prior to enrolment   Learning objectives and results   Content   View the UOC learning resources used in the subject   Additional information on support tools and learning resources   Guidelines on assessment at the UOC   View the assessment model  
This is the course plan for the second semester of the academic year 2023/2024. To check whether the course is being run this semester, go to the Virtual Campus section More UOC / The University / Programmes of study section on Campus. Once teaching starts, you'll be able to find it in the classroom. The course plan may be subject to change.
This course focuses on the study of patterns and their application during the analysis and design of the different layers (presentation, domain and technical services) of a software system. All the contents follow the Object Orientation methodology - currently the most accepted - and use the UML notation.
Patterns (for software analysis, design, and architecture, among others), are one of the innovations that have had the greatest impact on object-oriented development in recent years together with the introduction of UML. Their main advantages are that they save time and improve the quality of the system by applying solutions (called patterns), which have already been widely tested by other designers.

For this reason, the use of patterns is considered a basic skill that any object-oriented software designer must acquire today. However, the development of this skill requires practice, where the detailed information found in books about patterns - which are already increasing in number - is usually used. This way of working is recommended to students for their future professional work.

This course provides brief descriptions of many of the most well-known and accepted patterns today, as well as some general concepts about patterns and their use.


This course is strongly linked to the knowledge acquired in the Software Engineering course. It is also related to the Object Oriented Programming course, which deepens in the practical aspects of the behaviour of OO designs; and the Software Architecture course, which covers complementary aspects related to the engineering of distributed systems.


Solving a practical activity with UML and patterns requires students to have prior knowledge about the UML modeling techniques, object-oriented (OO) methodology, object-oriented programming (OOP), and relational databases.

In order to unify the prior knowledge of all students, and given that the object-oriented software development method will be used throughout the course, a collection of Review Exercises are provided as part of the classroom resources.

The concepts of the method and the corresponding UML notations are introduced by means of an example that is developed and discussed in detail. For those students who have already studied the content presented in this module, it will serve them as a review, which is especially convenient if they learned it some time ago and have not used it much since.


To enroll in this course, it is mandatory to have passed the Software Engineering course.


The general objective of the course is twofold. It aims to ensure that students master the analysis and design of software using object-oriented development methods, as well as to ensure that they acquire a solid understanding of the use of patterns. All of this as a way to simplify the software development thanks to the reuse of solutions to typical problems that appear in a recurrent manner.

The specific objectives that the student must acquire in this course are the following:
  • Assimilate the concept of pattern.
  • Get to know a selection of patterns applicable to the analysis and design phases of software development.
  • Be able to select the most suitable pattern for each situation.
  • Be able to apply a specific pattern in a specific situation.
  • Be able to analyze and design object-oriented software.
These objectives are related to the following competences of the Bachelor's Degree in Techniques for Software Development:  
  • Design and build computer applications using development, integration and reuse techniques.
  • Apply specific software engineering techniques to the different stages of a project's life cycle.
  • Propose and evaluate different technological alternatives for solving a specific software development problem.


The teaching material of the course consists of three didactic modules:

Module 1: Introduction to patterns
This module introduces UML by means of practical examples that cover the different modeling techniques. It includes an example of analysis and an example of design.

Module 2: Patterns catalogue

The most significant patterns are discussed in this module. Patterns covering mostly the entire life cycle of the software are described.

Module 3: Case study of pattern application

It includes the detailed development of a practical case similar to the Practical Exercise that students will need to solve.
The materials of this course are not designed to be studied sequentially. Once the introduction (Module 1) has been read, it is recommended to combine the study of theory (Module 2) and practice (Module 3) simultaneously. In the description of each activity, you will find a detailed description of which specific sections of each module must be studied for each activity.



The main resources for the course are the teaching modules, available in the Learning resources section in the classroom.

To carry out some of the course activities it is advisable to use a CASE (Computer Aided Software Engineering) tool, which allows to create well-formed UML diagrams. There are currently many CASE and modeling tools available on the market (both free and proprietary), as you can see in the following list: In any case, the course instructor does not offer technical support in the installation and use of these tools.


The assessment process is based on students' own work and the assumption that this work is original and has been carried out by them.

In assessment activities, the following irregular behaviours, among others, may have serious academic and disciplinary consequences: someone else being involved in carrying out the student's assessment test or activity, or the work being not entirely original; copying another's work or committing plagiarism; attempting to cheat to obtain better academic results; collaborating in, covering up or encouraging copying; or using unauthorized material, software or devices during assessment.

If students are caught engaging in any of these irregular behaviours, they may receive a fail mark (D/0) for the assessable activities set out in the course plan (including the final tests) or in the final mark for the course. This could be because they have used unauthorized materials, software or devices (e.g. social networking sites or internet search engines) during the tests, because they have copied text fragments from an external source (internet, notes, books, articles, other student's projects or activities, etc.) without correctly citing the source, or because they have engaged in any other irregular conduct.

In accordance with the UOC's academic regulations , irregular conduct during assessment, besides leading to a failing mark for the course, may be grounds for disciplinary proceedings and, where appropriate, the corresponding punishment, as established in the UOC's coexistence regulations.

In its assessment process, the UOC reserves the right to:

  • Ask the student to provide proof of their identity, as established in the university's academic regulations.
  • Request that students provide evidence of the authorship of their work, throughout the assessment process, both in continuous and final assessment, by means of an oral test or by whatever other synchronous or asynchronous means the UOC specifies. These means will check students' knowledge and competencies to verify authorship of their work, and under no circumstances will they constitute a second assessment. If it is not possible to guarantee the student's authorship, they will receive a D grade in the case of continuous assessment or a Fail in the case of final assessment.

    For this purpose, the UOC may require that students use a microphone, webcam or other devices during the assessment process, in which case it will be the student's responsibility to check that such devices are working correctly.


You can only pass the course if you participate in and pass the continuous assessment. Your final mark for the course will be the mark you received in the continuous assessment.