Print

Semester Project 6 - Viborg

Code

IT-SEP6 (Viborg)

Version

1.1

Offered by

ICT Engineering

ECTS

10

Prerequisites

It is understood that students working on Semester Project in 6th Semester in Viborg have passed all courses offered in 4th semester of the AR specialization and successfully completed their internship.

Main purpose

The purpose of this course is to introduce the students into a project which solution will require them to put newly obtained knowledge to practical use.
 

Knowledge

After successfully completing the course, the student will have gained knowledge about:
  • More in depth working processes for production and planning
  • The importance of planning to avoid bottle necking
  • Experience using folder structure, pipeline and workflow
  • Experience in following the direction of the project
  • Team management
 

Skills

After successfully completing the course, the student will have acquired skills in:
  • Adapting their pipeline, folder structure and production plan from the given standards
  • Work successfully as a team with them
  • Give estimates of their worktime and track their progress
  • Present their project as presentations
  • How to write an analysis of the project and a reflection on their work
  • Implementation of projects
  • Communication with team members
  • Create and document tests for the developed products.

 

 

Competences

After successfully completing the course, the student will develop competence to:
 
Importance of making decisions in order to move forward in production
Working with advanced functionality
Set and meet deadlines based on a structured working process
Create, analyze and edit as needed the teams group work protocol and their role
Collaborate, delegate and communicate clearly within a group
 

Topics

Teaching methods and study activities

Teaching methods and study activities
 
Students will work in groups and they will take a role as Interaction Developer or Software Developer to implement an AVR production.
The students implement their solutions agreed with in the production team.
After the project period, each group presents their solution to the whole class. The presentation must be a PowerPoint with at least a project description, relevant images from product and reflections. The group must also present the working prototype.
Each group is evaluated with passed/not passed in the presentation and can go to the exam when passed.
The groups must contain at least two students.
For relevant roles to participate in see the following or document roles.pdf.
 
Roles descriptions
 
Roles for students of ICT Engineering:
  • Interaction Designer
  • Software Developer
Roles for students of ICT Engineering
Interaction Designer
Knowledge:
Students should acquire knowledge of:
  • the core principals of user experience design and the role of an interaction designer in a computer game, AVR production or other visual interactive productions
  • the role in relation to the other members and roles on a production team
  • game mechanics and the user journey
  • testing the design through usability tests created in an iterative production setup
Skills:
Students should acquire the skills to:
  • work with and facilitate the interaction design process on a game or AVR production
  • create interactive prototypes on an iterative level
  • curate user tests throughout production
Competences:
Students should develop competence to:
  • understand and describe the user journey and game mechanics of a game or AVR  production
  • further develop their understanding of interaction design and user experience design
  • give and receive constructive criticism
  • collaborate and communicate constructive and successfully with their team members
  • interpersonally reflect on their own professionalism and collaborative abilities
 
Software Developer

Knowledge:
Students should acquire knowledge of:
  • system framework and architecture design
  • extended C# scripting in Unity 3D
  • various code testing methods
  • the role in relation to the other members and roles on a production team
Skills:
Students should acquire the skills to:
  • apply software engineering principles and methods into practice
  • implement code to achieve desired functionality directed by interaction designer or director
  • further develop their coding skills
Competences:
Students should develop competence to:
  • understand and describe implementation methods and principles
  • give and receive constructive criticism
  • collaborate and communicate constructive and successfully with their team members
  • interpersonally reflect on their own professionalism and collaborative abilities

 
Student Activity Model

CATEGORY 1 
Participation of the lecturer and students
Initiated by the lecturer
8 hours - 10 %

  • Lessons, scheduled
  • Excursions
  • Project guidance
  • Laboratory work
  • Exam and test

CATEGORY 2
Participation of students
Initiated by the lecturer
8 hours - 10 %

  • Assignment, self-study
  • Project and group work
  • Homework and preparation for exams
  • Evaluation of the teaching

CATEGORY 3
Participation of students
Initiated by students
64 hours - 75 %

  • Homework and preparation for exams
  • Self-study
  • Project work
  • Study groups
  • Literature search

CATEGORY 4
Participation of lecturer and students
initiated by students
4 hours - 5 %

  • Debate meetings
  • Study guidance

 

Resources

Students choose relevant resources from previous semesters and select and study new resources when needed.
 
 

Evaluation

Permit criteria for attending examination:

None

Examination

Before exam the examiner and censor have read the report and the process-report. The handed-in product is also checked.

The evaluation at exam is then that report, process report, product, presentation at exam and answers at exam are evaluated in an equal manner with 20% for each.
The examination is an oral examination based on first a group presentation for the project. Each member must present at least one page. 10 minutes per group.
Then an individual examination for 20 minutes. The student first present his/her role(s) in the project and the code created. This is 5 minutes. Then 15 minutes of discussion
and questions and also including evaluation and grading.
 
Allowed tools: All
Please note that re-examinations may take a different form than the ordinary exams.

The course must be passed before 31/8 for spring semester and 31/1 for autumn semester.

 

Grading criteria

Examinations account for 100 % of final grade.
 
 
 

Additional information

Software Engineering course in collaboration with TAW (The Animation Workshop) or other organizations or companies. The course is only offered to students who choose to follow the AVR specialization.

Responsible

Michael Koch (MIKO)

Valid from

9/1/2019 12:00:00 AM

Course type

Project
6. semester
Compulsory for the specialization Cross Media

Keywords