Software Engineering





Offered by

ICT Engineering




Main purpose

The purpose is to qualify the student to apply software engineering concepts used to develop Object Oriented software. Structure the software development process by applying  SCRUM and Unified Process to conduct Analyse, Design and Test-descriptions to exemplify a final solution from a real-lift problem. This involves requirement capturing (Use Cases and non-functional requirements), analysis, domain models, interaction diagrams, design classes, design patterns and test-descriptions etc.


The student should be able to account for:
  • Abstraction
  • UML
  • S.O.L.I.D Design principles
  • Unified Process
  • Design principles
  • Architecture design
  • Requirement capturing
  • Analysis vs. Design models
  • The difference between software development and coding
  • How to follow a test description


The student should exemplify:
  • Analysis of a problem and document the analyse- and design-process in UML
  • Practical use of UML
  • Practical use of Unified Process
  • UML to document requirements, analysis and design artefacts
  • Unified Process in combination with agile software development
  • SCRUM together with Unified Process
  • A domain model from a problem description and requirement specification and the elements in the model
  • A design model and understand the elements within it
  • The S.O.L.I.D principles on a design model
  • Design for test
  • Test descriptions
  • Architectural design models


The student should be able to:
  • Analyse a problem– what is the problem to solve?
  • Identify a problem and derive a requirement specification with Use Cases and non-functional requirements
  • Plan tests
  • Analyse and design a project to be implemented in teams with many participants


Teaching methods and study activities

The semester has 55 classroom lessons. These lessons will consist of teacher presentations and exercises.
The course will include one or more course assignment(s).
Study Activity Model
Participation of lecturer and students
Initiated by the lecturer
56 hours - 40%
  • Lessons
  • Exercises in class
  • Exam
Participation of students
Initiated by the lecturer
42 hours - 30%
  • Exercise, assignments and hand-ins
  • Project and group work
  • Homework
Participation of students
Initiated by students
28 hours - 20%
  • Preparation for exam
  • Self-study
  • Group work
  • Literature search
Participation of lecturer and students
Initiated by students
14 hours - 10%
  • Study guidance
  • Study group meetings




Permit criteria’s for attending examination:
Mandatory course activities completed before deadline.
The student must have an attendance of at least 75% in order to qualify for the exam. Students who do not have at least 75% attendance will automatically fail the ordinary exam. 


IF you are full degree Software Engineering student:

  • SWE 1 is evaluated together with SEP 2 project

  • The SEP 2 project and the exam must demonstrate understanding of SWE 1 skills and competencies and their use in practice
  • During the SEP 2 exam, specific SWE 1 questions will be asked, which must be answered satisfactorily to pass SEP 2
  • The grade for SWE 1 and SEP 2 will be the same, but be given as two grades
  • If a student fails the SWE1 or the SEP2 part of the exam, both courses are failed


  • Individual oral examination without preparation based upon course assignment(s)
  • Individual oral examination based upon a subject found by draw
  • No preparation

Oral examination where:

  • The student will pick a familiar question at random. The student must explain the concepts and theories about a subject from the course (50%).
  • The student will present a prepared presentation about the course assignment(s) (50%).

Allowed tools: All.


The course must be passed before graduation.

Grading criteria

Examinations account for 100% of final grade.

Additional information



Ib Havn

Valid from

9/1/2019 12:00:00 AM

Course type

Compulsory Course for all ICT Engineering
2. semester