Syllabus for |
|
| TDA593 - Model-driven software development |
| |
| Syllabus adopted 2014-02-25 by Head of Programme (or corresponding) |
| Owner: TKITE |
|
|
7,5 Credits |
| Grading: TH - Five, Four, Three, Not passed |
| Education cycle: First-cycle |
|
Major subject: Computer Science and Engineering, Information Technology
|
|
Department: 37 - COMPUTER SCIENCE AND ENGINEERING
|
Teaching language: English
Open for exchange students
Block schedule:
B
| Course module |
|
Credit distribution |
|
Examination dates |
|
Sp1 |
Sp2 |
Sp3 |
Sp4 |
Summer course |
No Sp |
| 0109 |
Project |
7,5 c |
Grading: TH |
|
|
7,5 c
|
|
|
|
|
|
|
In programs
TKITE SOFTWARE ENGINEERING, Year 3 (compulsory)
MPSOF SOFTWARE ENGINEERING, MSC PROGR, Year 2 (elective)
Examiner:
Docent
Rogardt Heldal
Replaces
TDA590
Object oriented system development TDA591
Object oriented system development TDA592
Object oriented system development
Go to Course Homepage
Eligibility:
In order to be eligible for a first cycle course the applicant needs to fulfil the general and specific entry requirements of the programme(s) that has the course included in the study programme.
Course specific prerequisites
The student must know Java programming and must have taken one course in data structures and a least one of the courses EDA497 Software engineering fundamentals or DAT255 Software engineering project or an equivalent course. Courses which students might benefit from having done are: project courses and Human - computer interaction.
Aim
Model-driven system development has become a popular way of building software systems. Correctly used, models leads to software systems which are easy to extend, reuse, and maintain. The purpose of this course is to provide knowledge about how to develop software system through models.
Learning outcomes (after completion of the course the student should be able to)
Apply different kinds of models and diagrams in the context of an object oriented software development process, to be able to use modeling to obtain abstractions of a software system on different levels. More precisely, a student will be able to
* write a pre-study for the development of a software system.
* write a domain model according to domain descriptions.
* given a pre-study and a domain model, write UML use-cases that show the intended usage of the system to be developed.
* realise use-cases using UML interaction diagrams, state charts and class diagrams.
* produce an executable software model
* verify the behaviour and structure of the executable software model
* understand how the different analysis and design methods make up a development process.
Content
In this course we will study how to develop a software system by using analysis and design principles, and also how models can be made executable. We will model both static and dynamic behaviours, for example interaction among objects (components), state changes of objects and the class structure of a system. The focus of this course is on the analysis and design phase.
Organisation
There will be about two lectures a week. A project will be carried out during the course. There will be a compulsory weekly project meeting with a supervisor. There will be individual assessments during the course in order to have individual grades.
Literature
Information about literature can be found on the course web-page.
Examination
The student must attend the weekly meetings and participate in the project work. The final grade will be decided on the project report and the contribution to the project. Apart from a report the project will be orally presented. During the course students will be asked theoretical questions regarding literature and/or lectures.