Syllabus for Software Engineering and Project Management

Metoder och projektledning för mjukvaruutveckling

A revised version of the syllabus is available.


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

    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 (3), Pass with credit (4), Pass with distinction (5)
  • Established: 2017-03-09
  • Established by:
  • Revised: 2018-08-30
  • Revised by: The Faculty Board of Science and Technology
  • Applies from: Spring 2019
  • Entry requirements:

    120 credits including 40 credits in computer science. 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:

  • describe the principal tasks of software project managers, and basic concepts in software projects
  • plan software projects, including risk and quality management
  • explain basic concepts and principles of components of software engineering, e.g., of requirements engineering, system design, software implementation, testing and maintenance, and how these components contribute to the software process
  • evaluate and relate different software processes, system models and architetural designs and assess their suitability in a given context
  • explain, using theory of group dynamics, how the project manager can act to influence success of the project
  • present and discuss course contents, orally and in writing.


Requirements definition and specification, prototypes, formal specification, design methods, reliability and safety, validation and verification, maintenance, reuse, project planning, quality assurance. Project management, group dynamics, risk management.


Lectures and guest lectures.


Written exam. Oral and written assignments.

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

Can not be included in the same degree as 1DL250 Software engineering.

Syllabus Revisions

Reading list

Reading list

Applies from: Spring 2019

Some titles may be available electronically through the University library.

  • Sommerville, Ian Software engineering

    9. ed., International ed.: Harlow: Addison-Wesley, cop. 2011

    Find in the library