Hide menu

TDDD27 Advanced Web Programming



  • Create Project, register members. April 2.
  • Functional and technological specification. April 2.
  • Project seminar. May 13-16 (book on webreg).
  • Individual oral examination. May 29 - June 4 (book on webreg).
  • Screen cast of your project. June 5.
  • Final source code upload. June 5

Create Project, register members

Go to the gitlab.ida.liu.se and register with your LiU student identity. Create a project with a name with a prefix TDDD272014 (e.g. TDDD272014_kickasswebproject) and if you need to add a team member. Invite eribe22 and sahsa74 as a member to the project.

Functional and technological specification

Put your specification in your readme file in your gitlab.ida.liu.se repo. Submissions by email will not be considered.

Functional specification:

Describe your project concretely. The project proposal should describe what core functionality your project web application intends to deliver. Don't mention every little detail and don't consider this a contract - this is for us to help you define a suitable scope in the course. Also note that this is not a contract that you should fulfil. You will be examined only on the end result.

Technological specification:

Describe the technology basis of your project with (1) server framework, (2) client framework. Also, describe how (3) persistence with data storage and ORM or other solutions for NoSQL-type persistence and how (4) authentication will be handled (framework authentication, oAuth/openID and so forth). If you intend to implement (5) multiple clients with different functionality and if you intend to use a (6) testing framework like Selenium is very relevant and beneficial to the project grade but considered extra.

You don't need arguments for picking a framework (as long as you meet all the technical requirements in the course). Taste and desire to learn a technology is a good argument as any. Bear in mind, however, that generally frameworks are good at different things. Making intelligent framework choices is part of the course and you'll have to live with your choices.

After the deadline we will read through your proposal and give you feedback. These comments will relate to scope and complexity, not so much to functionality. As a rule, projects usually are acceptable so don't wait for our feedback. The comments will be in the form of cautions and suggestions, not judgements. Since you are free to make your own choice about technology, we do not and cannot know every detail, but we will look for technical risks and underline abilities of the technologies you are using. Our approval doesn't mean you have a contract to pass the course - the examination is based on the end-result.

Project seminar:

Sign up will be announced:in webreg.

you (or the team of 2) participate in a 2 hour workshop, presenting your project. Prepare to do live demonstration of the actual system. Also talk briefly about your frameworks. Make time for questions and discussion.

This will run back-to-back so you must be prepared and practice demonstrating your system. Demonstrations start .00 sharp.

Individual oral examination:

Sign up will be announced:in webreg.

Every student will individually present the system and code. We will spend about 20 minutes per person for this examination and for feedback. You must be able to answer any question with regards to the project. It is not OK to say your team-mate implemented that or that it was a long time ago - prepare. In the past we have both given different grades to team members and approved only one in a team. Examination is individual.

This will run back-to-back so you must be prepared. Demonstrations start .00 sharp.

Screen cast:

In your final screen cast you should present your web project. Give a general overview what you have done but also present some technical challenges and how you have solved them (feel free to show code, but keep to the point).

The screen cast should be published online, on youtube, vimeo or some other place. E-mails containing screen casts will not be accepted. Provide the link to your screen-case in your readme fil on gitlab.ida.liu.se. You can find a Wikipedia article on software for screen casts here.

Final source code upload:

Hand in your project by uploading the final source on gitlab.ida.liu.se. Gitlab.ida.liu.se is the only acceptable place so make sure it gets up there. You cannot hand in by hosting on github och bitbucket or some other service. Some students have pushed from github to gitlab.ida.liu.se automatically. That is OK.

Page responsible: Erik Berglund
Last updated: 2012-03-01