TDDD27 Advanced Web Programming
Examination
## Format
Final examination is from screncast presentations. You submit two screencasts, (a) one individual code and system demonstration which each team member records and (b) a project screencast that can be done together. Also the gitlab.liu.se repo code, version history, and commit comments are also used.
An individual live presentation may be requested by the staff if there are any uncertainties.
## Division of labour
You cannot divide the knowledge.
Every student must understand all parts of the project, such as frontend, backend, data storage, security and so forth. You cannot divide this knowledge.
You can divide functional development as long as everyone touches all parts of the system and gain the knowledge. Teach one another.
## Documentation
**We are coders, we read code and commits, commit-comments, branching and all is part of the examination. Make sure you commit/push frequently with comments that describe the work. This is very good practise and the best documentation.**
## Passing and getting good grades
Grades of 3 to 5 will be issued. International students (such as ERASMUS students) will also be graded according to ECTS (grades A-FX). For the higher grades 4, 5, and VG the project must be especially good. The projects are graded according to the following criteria:
* Maturity in development demonstrated by the students
* Proper use of programming techniques and correct use of frameworks
* Completion of a mid-size project
* The advanced use of technologies
* Good use of version control during development
* Code quality, refactored code - easy to read code (code is the documentation)
* The timely delivery of the project
All projects will need to fulfill the technical requirements. These can be regarded as a basic set of requirement for passing projects.
In this course, we grade your knowledge about web development in relation to the technological requirements, demonstrated through your project and your individual, presentations. It is impossible to give very concise criteria for grading of 4 and 5 since everyone is allowed to, within reason, choose frameworks on their own. It all really depends on your project and the way you use the technologies.
A project can be graded 5 or 4 from two criteria: volume and good / advanced programming and from technological experimentation beyond the basic requirements. These two ways can also be mixed.
What will **not help you pass the course or get a good grade** is a safe applications that constitutes a trivial programing task given the right choice of technology. Building a blog, for instance, takes 15-20 minutes in many frameworks according to screen-cast tutorials. You need to really drill down and learn what these frameworks are all about and have an application idea that enable you to do that. Go beyond the basics. IS you choose tools that automate steps, use them as a steping stone to a higher level of fouctionality.
Research on higher education show that deep but more limited learning is better than broad surface learning.
## Late submissions
If you are unable to complete your project before the given deadline, you will be given the opportunity to finish and demonstrate your project during the re-examination period in August and in October/November. After that you can come back to the course next year. For scheduling a new oppertunity for examination, **send email to the examiner to book time for demostration August 22 or October 15**.
Page responsible: Erik Berglund
Last updated: 2023-03-28