Print as pdf if you want a pdf! If you want a nicer printout, click off the browser's automatically added header and footer.

Blekinge Institute of Technology
Department of Software Engineering

Revision: 1
Reg.no: BTH.4.1.14-0179-2026


Course syllabus

Team Project in Secure Software Development

Team Project in Secure Software Development

8 credits (8 högskolepoäng)

Course code: PA1492
Main field of study: Software Engineering
Disciplinary domain: Technology
Education level: First-cycle
Specialization: G1F - First cycle, has less than 60 credits in first-cycle course/s as entry requirements

Language of instruction: English
Applies from: 2026-03-03
Approved: 2026-03-03

1. Descision

This course is established by Dean 2025-12-12. The course syllabus is approved by Head of Department of Software Engineering 2026-03-03 and applies from 2026-03-03.

2. Entry requirements

Admission to the course requires 12 completed credits in programming and 10 completed credits in security from courses in computer security, network security, cryptology or cybersecurity. In addition, taken courses in the following areas are required: algorithms and data structures, cryptology, data communication and network technology, operating systems and computer technology.

3. Objective and content

3.1 Objective

The ability to develop computer-based systems that meet or reinforce the security requirements that are set is a central and important part of every system. This requires knowledge of the different models that exist for both system development and models for securing these systems. The purpose of the course is for the student to achieve basic knowledge of how software system development is done. By developing a smaller system, or support system, in the security area in small work teams, the knowledge of how software system development occurs is applied. The course also deals with the concept of security of a system from the perspective of software development.

3.2 Content

  • Fundamental concepts and processes in software development.
  • Requirements engineering and management, software testing. architectural design
  • Project management, project monitoring and control, project documentation, and follow-up of software projects in teams, including commitment culture, project organization, roles within projects, project planning and tracking, test planning and reporting, and delivery planning.

4. Learning outcomes

The following learning outcomes are examined in the course:

4.1. Knowledge and understanding

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

  • define fundamental concepts and common processes used in software systems development.
  • explain the key activities in the requirements engineering process.
  • describe the main steps involved in project planning and project follow-up.

4.2. Competence and skills

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

  • demonstrate professional skills and competence relevant to the role of a practicing software developer in industry, within the context of team-based software development.
  • account for and apply how software is developed in teams by actively participating in the planning, organization, and execution of a software development project.
  • plan and deliver oral presentations.

4.3. Judgement and approach

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

  • demonstrate a professional approach to ways of working based on a commitment culture.
  • demonstrate a critical and reflective approach, including self-reflection and self-criticism.

5. Learning activities

The learning activities in the course consist of lectures, workshops, additional readings, and working on a software engineering project. Lectures introduce theoretical concepts related to software engineering processes, requirements, project planning, and professional practice. Practical skills are developed through project work, by learning to actively plan, design, implement, and deliver a software solution for a customer. Active participation is required through continuous work on the project assignment and participation in demonstrations. Learning is supported through regular feedback from teachers and customers throughout the project.

6. Assessment and grading

Modes of examinations of the course

Code Module Credit Grade
2610 Project 6 credits GU
2620 Report 2 credits GU

The course will be graded G Pass, UX Failed result, a little more work required, U Fail.

The examiner may carry out oral follow-up of written examinations.

The information before the start of the course states the assessment criteria and make explicit in which modes of examination that the learning outcomes are assessed.

An examiner can, after consulting the Disability Advisor at BTH, decide on a customized examination form for a student with a long-term disability to be provided with an examination equivalent to one given to a student who is not disabled.

7. Course evaluation

The course evaluation should be carried out in line with BTH:s course evaluation template and process.

8. Restrictions regarding degree

The course can form part of a degree but not together with another course the content of which completely or partly corresponds with the contents of this course.

9. Course literature and other materials of instruction

Sommerville, I. (2021). Engineering software products: an introduction to modern software engineering. (Global edition). Harlow: Pearson. - ISBN: 9781292376349