Syllabus for Project CS

Projekt DV

  • 30 credits
  • Course code: 1DT054
  • Education cycle: Second cycle
  • Main field(s) of study and in-depth level: Computer Science A1F, Technology A1F

    Explanation of codes

    The code indicates the education cycle and in-depth level of the course in relation to other courses within the same main field of study according to the requirements for general degrees:

    First cycle

    • G1N: has only upper-secondary level entry requirements
    • G1F: has less than 60 credits in first-cycle course/s as entry requirements
    • G1E: contains specially designed degree project for Higher Education Diploma
    • G2F: has at least 60 credits in first-cycle course/s as entry requirements
    • G2E: has at least 60 credits in first-cycle course/s as entry requirements, contains degree project for Bachelor of Arts/Bachelor of Science
    • GXX: in-depth level of the course cannot be classified

    Second cycle

    • A1N: has only first-cycle course/s as entry requirements
    • A1F: has second-cycle course/s as entry requirements
    • A1E: contains degree project for Master of Arts/Master of Science (60 credits)
    • A2E: contains degree project for Master of Arts/Master of Science (120 credits)
    • AXX: in-depth level of the course cannot be classified

  • Grading system: Fail (U), Pass (G)
  • Established: 2010-11-11
  • Established by:
  • Revised: 2018-08-30
  • Revised by: The Faculty Board of Science and Technology
  • Applies from: Spring 2019
  • Entry requirements:

    150 credits in computer science, including at least 30 credits at Master's level. Courses in programming, algorithms and data structures, operating systems, and computer networks must be included. Proficiency in English equivalent to the Swedish upper secondary course English 6.

  • Responsible department: Department of Information Technology

Learning outcomes

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

  • Act towards constructive collaboration based on different collaboration roles.
  • Show abilities necessary in order to participate in the conducting of a realistic software development project with external stakeholders.
  • Account for how a large project is run from the initial planning to the finish.
  • Use "state-of-the-art" design principles and programming methods.
  • Delimit an open assignment and choose applicable components to carry out the work based on an appropriate project methodology and carry out the planning accordingly in order to be done within the given constraints.
  • Account for an reflect on hie/his own role in the project group and in the development process.


Both breath and deep knowledge aspects of the following areas:

  • Distributed systems, e.g. distributed operating systems, distributed databases, fault tolerance, atomic actions and synchronisation.
  • Project methodology, comprising methods for planning, work methods within computer technology, project reporting, documentation and report writing.


The course is run as a project with lectures and study visits as requested by the participants and based on the issue addressed in the current project. There might be sections with compulsory participation.


Completed project and written and oral reports.

If there are special reasons for doing so, an examiner may make an exception from the method of assessment indicated and allow a student to be assessed by another method. An example of special reasons might be a certificate regarding special pedagogical support from the disability coordinator of the university.

Other directives

The course is intended to be taken just before doing the Master's thesis.

Reading list

The reading list is missing. For further information, please contact the responsible department.