TDDD27 Advanced Web Programming

Deliverables

Create Project, register members. April 15.
Functional and technological specification. April 15.
Project seminar. May 13 - May 17.
Code seminar. May 27 - June 1.
Screen cast of your project. June 1.
Final soruce code upload. June 1

Create Project, register members

Go to the Project Server and register with your LiU student identity. Create a project and add tema members. Also register on webreg here.

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. 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.

Technological specification:

Describe the (1) server framework, (2) client framework, (3) JSON, XML or other protocol to send data between the server and client. Also describe if you will use (4) AJAX or web sockets for communication and which (4) ORM or data storage technique you will use. Also, detail how (5) authentication will be handled (framework authentication, oAuth/openID and so forth). If you intend to implement (6) multiple clients with different functionality and if you intend to use a (7) testing framework like Selenium is very relevant and beneficial to the project but to be considered extra functionality.

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. Making intelligent framework choices is part of the grading in the course.

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 are acceptable so don't wait for our feedback to get started. The comments will be in the form of cautions and suggestions, not judgments. Since you are free to make your own choice about what technology to use we cannot know every detail but we will look for technical risks and underline abilities of the technologies you are using.

Project seminar:

You will individually participate in a 2 hour workshop, pitching and presenting your project and showing it. Team mates do this in different sessions. 8 minutes walkthrough and 2 minutes for questions. Everyone does this. Practice! You should do live demonstration of the actual system. Also talk briefly about your frameworks and say one thing about your experience.

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

Code seminar:

Every student will individually present code and answer any question on your project. This is an important part of your examination process and team members must all do an individual demonstration during one of the sessions.

The code presentatiosn will be made frmo a standard computer from the code on the project server, so practise this format.

You will use 6 minutes to demonstrate your code and 4 minutes for questions. Focus on central how one user-initiated interaction travels through the systems from client, to server, to backend database or external service and back again, where the data from the server is build into GUI components. Spend 1 minute detailing the most complicated parts of your system. For questions, you must be able to answer any question along for the client and server side framework of relevance to your project, you cannot say someone else is responsible for this in the team.

Practice this presentation at least 4 times before presenting so you are well prepared. Practice live and loud at home, practice makes perfect! Short quality presentations are highly relevant to engineers.

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

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 to the point).

The screencast should be published online, on youtube, vimeo or some other place. 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 like a "stable" version easy to find on the TDDD27 Project Server.

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

Department of Computer and Information Science