Hide menu

TDDD27 Advanced Web Programming

Deadlines and Deliverables

Deadlines

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

Create Project, register members

Go to gitlab.ida.liu.se online (this creates your user) and create a project with a name with a prefix TDDD272016 (e.g. TDDD272015_kickasswebproject). Add teammembers and also add eribe22, denpe11, sahsa74 as reporters.

gitlab.ida.liu.se is the only acceptable repo. Some students have pushed from github to gitlab.ida.liu.se automatically. That is OK. Since we look at version history and commit comments as part of the grading of the code make sure you use this and commit/push frequently to show us what in your head during development.


Functional and technological specification

Put your specification in your readme file - readme.md 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.

Technological specification:

Describe the technology basis of your project with (1) client framework (2) server framework. Working with testing and deployment systems like Selenium, Grunt/Gulp, Postman, Travis, Jenkins and deployment plaforms like Containers and Gears is very relevant (but not required).

Making intelligent framework choices of framework is part of the course. Take some time to research your options before choosing. Also, frameworks are varyingly complex and you need to choose something that fits your experience level, but also challenge you to reach higher knowledge levels. Grading is based on how far you go in terms of technical competence, which may relect from the framework you pick but mostly how well you use it. Remember also, the specification is a proposal, not a contract - you can change your project after submission. Grading is based on what you've done and what you know at the end of the course. This activity is for getting feedback on your ideas.



After the deadline we will give you feedback. Comments will relate to scope and complexity, not so much to functionality. Don't wait for our feedback, as a rule 99 out of 100 projects are acceptable. 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 look for technical risks and sesible scope of the project. Also, remember, 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. 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 - be prepared. 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, 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. Put the link you your screencast in your readme-file on gitlab.ida.liu.se. E-mails containing screen casts will not be accepted. You can find a Wikipedia article on software for screen casts here. You can also test Autocad Screencast service.


Final source code upload:

What's on gitlab.ida.liu.se on the deadline is your hand in. You don’t have to do anything special. We read code for grading - all of us are fluent in web-coders so we don’t want any documentation apart from clean code, tests, value-adding code-comments and commit comments that show what’s happening. Commit frequently.


Page responsible: Erik Berglund
Last updated: 2017-03-20