Roskilde, March 2015

Elective courses: Individual project

This document is an add-on to the official curriculum, section 14.3 Elective: Specialisation

"The specialisation gives the student an opportunity to enhance his/her academic and professional competence by specialising and putting themes into perspective within the wider scope of information technology.  

The Academy organises the specialisation by identifying and offering a series of specialisation courses within the objective of the degree program. In this connection the Academy takes the needs of the local business community into consideration as well as student wishes and current trends.  

Examination is an internal exam in the form of individual course work comprising the full scope of the specialisation. The student submits a report of max. 25 standard pages. The report is assessed by an examiner and a mark is given according to the 7‐point grading scale."


Electives courses have two parts:

Sometime before the end of the course part you must write the teachers of your electives about your subject for the individual project. The subject must be something that has are relation to at least one of your electives (not all your electives). The subject must be something that was not covered in the course part.
The teachers must check that the ideas is relevant.

Based on the subject you will be assigned a supervisor, who can guide you through the process of making your individual project.

Each student makes ONE individual project - not one project per elective course.
Each elective course includes one or more mandatory assignments. In this way we check that you learned enough in each course, so that you do not have to repeat the course knowledge in the individual project.


Some important sections of your report


Briefly introduce your subject.

Motivation: Why do is this subject interesting to you - and to the rest of the World?

Problem definition

Ask some questions about the subject. Usually a single main question with about three sub-questions.

State this like real questions - ending with a real question mark.


Describe how you intend to find the answers to the questions, like:

The method described in this section must not be confused with a Systems Development Methodology like UP or XP.


Describe which activities you will go through to find the answers and write the report.

Sequence the activities: What will you do first, and then, and then ...
You can refer to a Systems Developments Methodology when you sequence your activities.

How much time will you spend on each activity.

Put the activities into a plan. Remember, you have a hard deadline: The day of submission cannot be postponed.

Once again: You have two sets of activities in the plan

Work, to answer the questions

This must be the main body of the report.

Describe the work you do to answer the questions.
If you do something, but don't describe it, then we don't know - and it doesn't count.

The work should include not only theory but also practical work - where you can gain your own experience - to answer the questions from the problem definition.

Conclusion: Answer the questions

In the conclusion you answer the questions.

Main question: Answer to main question!

If you cannot answer the questions, then you have a serious problem! One solution is to rephrase the questions!!

You should end the conclusion with a few words on how/if the knowledge you gained from you work is applicable in other areas, outside your problem definition.


After answering the questions you should have another look at what you did. With the knowledge you have now (hopefully more that when you started the project):

List of references

The list of references incudes all the books, web sites, etc. you used.

Each reference must include: Authors name + title + publisher + year of publication, etc. and a few lines on how you used the book, etc.

With web sites a URL is not enough: There must be at least a title, and maybe an author and/or a publisher.


Joseph Annuzzi et al. Introduction to Android Development, 4th edition, Addison Wesley 2014.
I used this book for some advanced examples on Android development.
Android Developers API Guides, Introduction to Android,
Used for examples on how to use the Android API.

In the project you should refer to a reference using footnotes.

What's not in the project?

No groups
This is an individual project.
No company
You don't have to work with a company, unless you chose to do so in your "Method".
Later, when you do your internship and dissertation you should work with a company.
Nobody needs a software product
According to the curriculum you submit a report, not a software product. In most cases you will make a software product, because you "Method" tells you to. But, you make the project to be able to answer the questions - not because somebody needs the product.
No plagiarism
Copying other peoples work is not allowed and may lead to your exclusion.
You are allowed to make small quotes on your report. The quote must be clearly marked, and you must state exactly where you quoted from (including page numbers, etc.)
No exam
The curriculum: "The student submits a report of max. 25 standard pages. The report is assessed by an examiner and a mark is given according to the 7‐point grading scale."
The is no oral exam. This means that you have no second chance of telling if something is missing from the report. Everything must be in the report - only the report counts.