Software Patterns
Faculteit | Science and Engineering |
Jaar | 2020/21 |
Vakcode | WMCS014-05 |
Vaknaam | Software Patterns |
Niveau(s) | master |
Voertaal | Engels |
Periode | semester I b |
ECTS | 5 |
Rooster | rooster.rug.nl |
Uitgebreide vaknaam | Software Patterns | ||||||||||||||||||||||||||||||||||||
Leerdoelen | At the end of the course, the student is able to: 1. Communicate the notion of a pattern and associate patterns through pattern languages. 2. Formulate an overview of the most prominent categories of patterns and characteristic examples for each one of them. 3. Construct software engineering artefacts by reasoning and communicating in terms of software problems & solutions. 4. Analyze, synthesize (or recover) and evaluate a software architecture based on patterns through groupwork. |
||||||||||||||||||||||||||||||||||||
Omschrijving | Fundamental to any science or engineering discipline is a common vocabulary and a language for relating the vocabulary terms together. In software engineering this is attempted through the emergence of patterns: software patterns create a body of literature to help software developers resolve recurring problems encountered throughout all of software development. In contrast to other Software Engineering fields, the focus of Software Patterns is not on technologies but on creating a culture to document and support sound engineering designs & best practices. The course is aimed at presenting the paradigm of patterns in software engineering, advocating the offer of valuable, reusable knowledge in manageable chunks. The course covers a broad range of the most prominent types of patterns: architecture patterns, design patterns, analysis patterns, enterprise application patterns etc. It aims at introducing the students to the basic theory of patterns as well as ways to apply the patterns in the software engineering context. Finally it aims at software architecting through the use of patterns, providing a more in-depth study of recurring problem-solution pairs and links to the wider corpus of patterns. | ||||||||||||||||||||||||||||||||||||
Uren per week | |||||||||||||||||||||||||||||||||||||
Onderwijsvorm |
Hoorcollege (LC), Practisch werk (PRC)
(Plenary lectures (2 or 3 hours a week), and two practical assignments) |
||||||||||||||||||||||||||||||||||||
Toetsvorm |
Opdracht (AST)
(The grade is composed from the result of two group projects: Assignment 1 (35%) and Assignment 2 (65%). Both projects require the delivery of a written report as well as oral presentations by the individual students. The grades are weighted by the assessment of the individual contributions. In the case of failing the course, a student may be re-assessed by working on an extra project.) |
||||||||||||||||||||||||||||||||||||
Vaksoort | master | ||||||||||||||||||||||||||||||||||||
Coördinator | prof. dr. ir. P. Avgeriou | ||||||||||||||||||||||||||||||||||||
Docent(en) | prof. dr. ir. P. Avgeriou | ||||||||||||||||||||||||||||||||||||
Verplichte literatuur |
|
||||||||||||||||||||||||||||||||||||
Entreevoorwaarden | The course unit assumes prior knowledge acquired from a course in Software Architecture, from a MSc in Software Engineering or Computer Science. | ||||||||||||||||||||||||||||||||||||
Opmerkingen | The mandatory and optional literature is described in a literature list. There is an article compendium on Nestor, containing research articles for further study. This course was registered last year with course code INMSP-08 |
||||||||||||||||||||||||||||||||||||
Opgenomen in |
|