TDDD27 Advanced Web Programming

Deliverables

• Create project on project portal. Deadline March - 22.
• Functional and technological specification. Deadline March - 22.
• Project seminar presentation. May 7-11.
• Individual oral examination. May 21 - June 1. .
• Screen cast of your project June 1.
• Final soruce code upload June 1

Create Project, register members

Go to the TDDD27 Redmine and register with your LiU student identity. Create a project and optinally add a team mate as a member. To do this, your team mate must firts register as a user in the Project Portal.

Functional and technological specification

Functional specification:

Describe your project in detail. The project proposal should describe what core functionality your project web application intends to deliver. Use about 1-2 pages to describe the features , making sure to make your proposal focused on visualizing the core. You dont have to mention every lite meny alternative but instead make sure you try to make the vision of your web application very clear, perhaps examplify with user scenarios and give visual examples. Write your proposals directly on wiki in you project portal or upload as a file (see TDDD27 Redmine).

Technological specification:

Once you have a project idea you need to discover what technologies to use: in relation to the technical requirements in the course and additional components that will help you deliver your web application. Pick a set of technologies and describe what they bring to the table for your project. In this course, using external systems, libraries and components are regarded valuable and a core component in the delivery of good software. It is reuse. But at the same time, the course runs for limited amount of time and thus you will have a hard time reading up on many systems at once. It is your choice, we will see this and take that into account when judging projects for the examination.

You don't need arguments for picking a framework other than your own desire (as long as the framework is considered acceptable for the course and 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 and may be more or less suitable for your project, making it harder or easier for you to implement your vision.

After the deadline we will read through your proposal and make comments. These comments will relate to scope and complexity, not so much functionality. As a rule, projects usually pass with some form of addition or subtraction which is focused ensuring you do enough work but not to much and that the level of complexity is advanced enough but not complicated for a 6hp A-level course. The comments will be in the form of cautions and suggestions, not judgments. We will give feadback on choices you have made and point out issues about these framworks in the cases where we can. Since you are free to make your own choice about what technology to use we cannot know every detail but we will look for technichal risks and underline abilities of the technologies you are using. You may also expects some potential commetns about finding other technologies or specific tools to look into more.

Project seminar presentation:

Sign up:here

You will participate in a 2 hour seminar with up to 5 other projects, spending 20 minutes doing your own walkthrough and presentation, saving 5 minutes for questions. This will run back-to-back som make sure you are on times and the demonstrations start .00 sharp.

Individual oral examination:

Sign up :here

Every student will be individually examined, even when working in teams. You and a member of the course staff meet and have a discussion about the project and the project code, where you must be able to answer detailed questions about any part of your project. Estimate 20-30 minutes per student. You source code should be avaliabe at this time from the proejct portal for discussion.

Screencast:

In your final screencast 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 it to the point).

The screencast must be published online, on youtube, vimeo or some other protal. E-mails containing screencasts will not be accepted. 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 in a .zip filen on the Project Protal. This should be done before June 2.

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