Print

Software Engineering

Code

IT-SWE1

Version

1.1

Offered by

ICT Engineering

ECTS

5

Prerequisites

IT-SDJ 1

Main purpose

The purpose is to qualify the student to understand software engineering concepts used to develop Object Oriented software with UML using the Unified Process to understand how to come from a problem to the final solution. This involves requirement capturing (Use Cases and non-functional requirements), analysis, domain models, interaction diagrams, design classes, design patterns etc.

Knowledge

The student should be able to understand:
  • Abstraction
  • UML
  • S.O.L.I.D Design principles
  • Unified Process
  • SCRUM
  • Design principles
  • Architecture design
  • Requirement capturing
  • Analysis vs. Design models
  • Understand the difference between software development and coding
 

Skills

The student should achieve the skills:
  • Analyse a problem and document the analysis and design for the solution in UML
  • Practical use of UML and Unified Process
  • Use UML to document requirements, analysis and design artefacts
  • Follow Unified Process in combination with agile software development
  • Use SCRUM together with Unified Process
  • Create a domain model from a problem description and requirement specification and the elements in the model
  • Create a design model and understand the elements within it
  • Use the S.O.L.I.D principles on a design model
  • Design for test
  • Create architectural design models
 

Competences

The student should achieve the competences:
  • Work on a high abstraction level – what is the problem to solve?
  • Understand a problem and be able to make a requirement specification with Use Cases and non-functional requirements
  • Cooperate in projects with many participants

 

Topics

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).
 
CATEGORY 1
Participation of lecturer and students
Initiated by the lecturer
56 hours - 40%
  • Lessons
  • Exercises in class
  • Exam
 
CATEGORY 2
Participation of students
Initiated by the lecturer
42 hours - 30%
  • Exercise, assignments and hand-ins
  • Project and group work
  • Homework
 
CATEGORY 3
Participation of students
Initiated by students
28 hours - 20%
  • Preparation for exam
  • Self-study
  • Group work
  • Literature search
 
CATEGORY 4
Participation of lecturer and students
Initiated by students
14 hours - 10%
  • Study guidance
  • Study group meetings
 

Resources

Evaluation

Permit criteria’s for attending examination:
 
Mandatory course activities completed
  • A number of presentations
Course assignment handed in before deadline

Examination

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 topics 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

ELSE

  • 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 do a prepared presentation about the course assignment (50%).

Allowed tools: All.

ENDIF

The course must be passed before graduation.

Grading criteria

Examinations account for 100% of final grade.

Additional information

Responsible

Ib Havn

Valid from

8/1/2018 12:00:00 AM

Course type

Compulsory Course for all ICT Engineering
2. semester

Keywords