Course contents *

Programmes as compositions of functions. Comparison between functional and object-oriented programming. Handling and identification of code complexity.

The open-closed principle.

Modelling of information.

Business logic and rules compared with handling of state.

APIs. Documentation of entities.

Testability and the importance of tests. Tests as documentation. Mutability and persistent data structures. Clean functions. Thread safe programming.

Intended learning outcomes *

After completion of the course, the student should be able to:

• structure, using functional programming, large programs so that they become easier to understand and manage,
• identify the need of design patterns in development of new or in administration of existing code, as well as implement these where appropriate,
• design and document public APIs with a clear responsibility,
• design entities so that they become testable and write tests for them,
• protect internal design of a program from the public APIs,
• develop a programme in collaboration with others,
• review and reflect on source code,
• develop given source code

in order to be able to

• understand and master the parameters in software development that make source code sustainable, re-usable and flexible during changing requirements.

Course Disposition

No information inserted

Specific prerequisites *

Object-oriented software development equivalent to one of the courses DD2480, DD1392/DD1393, DD1346, DD1387/DD1388/DD2387 or DD1385/DD2385.

Recommended prerequisites

Objectt oriented program development corresponding to one of the courses DD2480, DD1392/DD1393, DD1346, DD1387/DD1388/DD2387 eller DD1385/DD2385.

Equipment

No information inserted

Literature

No information inserted

If the course is discontinued, students may request to be examined during the following two academic years.

Grading scale *

P, F

Examination *

• PRO1 - Software engineering project, 7.5 credits, Grading scale: P, F

Based on recommendation from KTH’s coordinator for disabilities, the examiner will decide how to adapt an examination for students with documented disability.

The examiner may apply another examination format when re-examining individual students.

Other requirements for final grade *

Passed software development project including peer assessment.

Opportunity to complete the requirements via supplementary examination

No information inserted

Opportunity to raise an approved grade via renewed examination

No information inserted

Examiner

Stefan Nilsson

Ethical approach *

• All members of a group are responsible for the group's work.
• In any assessment, every student shall honestly disclose any help received and sources used.
• In an oral assessment, every student shall be able to present and answer questions about the entire assignment and solution.

Course web

Further information about the course can be found on the Course web at the link below. Information on the Course web will later be moved to this site.

Offered by

EECS/Computer Science

Main field of study *

Computer Science and Engineering

Education cycle *

Second cycle

Add-on studies

No information inserted

Contact

Tomas Ekholm (tomase@kth.se)

Supplementary information

The course is replacing DD2386 and cannot be combined with it.

In this course, the EECS code of honor applies, see:
http://www.kth.se/en/eecs/utbildning/hederskodex