Bachelor Project 2 (Viborg)





Offered by

ICT Engineering




BPR1, general conditions for ECTS credits.

Main purpose

The purpose of the Bachelor Project 2 is to evolve the student’s ability to solve a relevant ICT Engineering problem and document the solution. In a group, students must be able to analyze, design, implement and test complex problems and be able to carry out well-documented and tested solutions.


After successfully completing the course, the student will have gained knowledge about:
• Searching and scoping relevant project information
• Project and teamwork planning
• Communication and documentation skills
• Testing


After successfully completing the course, the student will have acquired skills in:
• Identifying, justifying, and delimiting problems and their context
• Analyzing a problem to define use cases and requirements for a solution
• Selecting and arguing for choice of method and reflect critically on those methods
• Finding and assessing relevant literature within the problem domain
• Presenting the result for an audience of engineers
• Implementing a software solution to a problem
• Planning and structuring the project within the BPR2 timeframe


After successfully completing the course, the student will have acquired competencies in working in a group with the objective of defining and solving an engineering problem. The student will be able to take the role of software engineer in a project group with all the aspects that includes.


The Bachelor Project (BPR2) is based on an ICT Engineering problem with a project description made in the BPR1 course.

Topics to focus on in the BPR2 project include:
• Data collection
• Brainstorm techniques
• Project methods
• Reference/citation model and literature search
• Document version control
• Requirements: How can you test the requirements, which test results do you expect for each test case.
• Analysis: Risk analysis (technology challenges, error implementations, Data loss, delays in order ful-fillments), Actor/persona description, Use cases
• Design: System architecture, Class diagram, Layer model, Mockup model, Usability, GUI, Excep-tions
• Implementation: Coding of project
• Test: Unit test, Integration test, System test, GUI test
• Automatic build servers – including automated tests
• Project results
• Evaluation/discussion of project results
• Time schedule and milestones
• Workflow management
• Group dynamics
• Report writing
• Presentation techniques

Teaching methods and study activities

Students will do project work in groups and receive supervision and guidance through meetings that they themselves must arrange. The expected workload per student is about 412.5 hours.

Student Activity Model
Participation of lecturer and students
Initiated by the lecturer
10 hours - 2 %
  • Lessons, scheduled
  • Excursions
  • Project guidance
  • Laboratory work
  • Exams and tests
Participation of students
Initiated by the lecturer
0 hours - 0 %
  • Assignments, self-study
  • Project and group work
  • Homework and preparation for exams
  • Evaluation of the teaching
Participation of students
Initiated by students
382.5 hours - 93 %
  •  Homework and preparation for exams
  •  Self-study
  •  Project work
  •  Study groups
  •  Literature search

Participation of lecturer and students

Initiated by students

20 hours - 5 %

  • Debate meetings
  • Study guidance


Relevant literature from the problem domain selected by the students



Students must hand in a project report documenting the solution on WISEflow. The project report must be 10 pages + 20 pages per student plus appendices. This is a maximum page number, and more pages will reduce the grade.
Additionally, any appendices along with a process report and the source code for the solution must be zipped and up-loaded to WISEflow as well. It is also recommended to include a build of the solution and a video showing the solution.
Type of exam:
Oral ​examination.
Group presentation of the project (20 minutes). After that there will be questions (20 minutes per student). The questioning session can be individual at the students request.
The questions typically start from topics in the report and may involve all the topics from 1st to 7th semester.
External assessment.
Allowed tools:
A prepared presentation, personal notes, reports from the project and appendices.

Grading criteria

Examination accounts for 100 % of final grade, but examination is based on project report, product, and to some degree process report, source code and other appendices.

Additional information


Nicolai Brobak (NBRO)

Valid from

8/1/2021 12:00:00 AM

Course type


Bachelor Project, Software Engineering