Hide menu

TDDD27 Advanced Web Programming

Deliverables

Deadlines

  • Create Project, register members. April 3.
  • Functional and technological specification. April 3.
  • Project seminar. May 7-13 (book on webreg).
  • Individual oral examination. June 1 - 5 (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 create a project with a name with a prefix TDDD272015 (e.g. TDDD272015_kickasswebproject). Add teammembers. Add eribe22 and sahsa74 as developers to the project so we can see the code. Also set up your web server on openshift.ida.liu.se using the OpenShift rhc-tool. Together this means you have a git-repository for the code and developemnt and a git on openshift.ida.liu.se for production.


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 vision and core functions. Don't mention every little detail - this is for us to help you define a suitable scope in the course. Also note that this is not a contract you should fulfil. Examination is based on what you deliver, not what you promis.

Technological specification:

Describe the technology basis of your project with (1) clinet framework, (2) server 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 (while meeting hte technical requirements). Making intelligent framework choices is part of the course though so I'd like to stress that you will 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. 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 - examination is based on the end-result only.


Project seminar:

Sign up will be announced on course info.

You participate in a 2 hour workshop, presenting your project. Live demonstration and code demonstration. PPTs are not really appreciated. Also, talk briefly about your frameworks. Make time for questions and discussion. Here you run your system on openshift.ida.liu.se. Don't miss that.

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 on course info.

Every student will individually present the system and code. We will spend about 20 minutes per person for this examination. 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. Examinations start .00 sharp.


Screen cast:

In your final screen cast you should present your web project. Use the keywords {TDDD27, 2015, LiU, projectname } in the title to make it easier to find. 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).

The screen cast should be published online somehow, 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. You can also test Autocad Screencast service.


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