Official website of the course "Web Applications I" (code 01TXYOV) offered to students in the 1st year of the M.S. in Computer Engineering. Academic Year: 2020/2021
This page contains the archived version for the 2019/2020 edition of the course. Short link to the current edition: http://bit.ly/polito-wa1
Short link: http://bit.ly/polito-wa1
Latest news
- 2021-02-16: Welcome to the 2021edition of the course! Happy web to everybody!
Basic information
| Ttle: | Web Applications I |
| Credits: | 6 CFU |
| Year: | 1st year Computer Engineering |
| Semestre: | 2nd semester (March-June) |
| Language: | English |
| Main teacher: | Fulvio Corno |
| Other teachers: | Alberto Monge Roffarello, Juan Pablo Sáenz, Luca Mannella |
| Official link: | Portale della Didattica |
| GitHub Repository: | https://github.com/polito-WA1-AW1-2021 |
| Video lectures: | YouTube Playlist |
| Slack workspace: | WA1-2021 |
Class Hours
| Day | Hour | Location | Type | Note |
| Thursday | 08:30-10:00 | Virtual | Class | |
| Thursday | 10:00-11:30 | Virtual | Class | |
| Monday | 13:00-14:30 | Virtual | Lab | starts on March 15 |
| Monday | 14:30-16:00 | Virtual | Lab | starts on March 15 |
| Monday | 16:00-17:30 | Virtual | Lab | starts on March 15 |
Schedule
Reminder: slides are also available on GitHub (always update to the latest version, just clone the repository and 'pull' frequently)
Resources
Lecture slides
- Lecture slides are linked in the Schedule section, according to the lecture when they were first explained
- For easier download (and continuous update), all slides are also available from the course materials on GitHub
- Screencasts of the video lectures are available on the Portale della Didattica, on YouTube (playlist: https://www.youtube.com/playlist?list=PLqRTLlwsxDL9vSKdXgAm-_LMHl-AoK7ET)
Labs
- Lab 1: Getting Started with NodeJS (15/03/2021)
- Lab 2: Getting started with HTML and CSS (22/03/2021)
- Lab 3: JS in the browser (29/03/2021)
- BigLab1:
- GitHub Classroom Instruction
- General Specifications
- BigLab1A: Getting started with React (12/04/2021)
- BigLab1B: React Components' State (19/04/2021)
- BigLab1C: Filters and Forms (26/04/2021)
- BigLab1D: React Routes (03/05/2021)
- RESULTS
- BigLab2:
- GitHub Classroom Instruction
- General Specifications
- BigLab2A: APIs with Express (10/05/2021)
- BigLab2B: APIs Integration (17/05/2021)
- BigLab2C: Complete APIs Integration (24/05/2021)
- BigLab2D: Authentication (31/05/2021)
- RESULTS
- Lab 4: Deploying React+Express applications in Heroku (07/06/2021)
- No solution will be proposed
Software tools
- Node.js 14.15 (latest LTS) and npm
- Visual Studio Code
- Google Chrome or Mozilla Firefox (recent updates: Chrome 88+ or Firefox 85+)
- React Developer Tools (extension for Chrome and Firefox)
- DB Browser for SQLite
- git
On-line documentation
- Mozilla Developer Network (MDN)
- React official website
- Bootstrap 4.6 and React Bootstrap
- You Don't Know JS Yet (2nd edition)
- The Modern JavaScript Tutorial
Exam
Exam Assignments
- Exam #1: Survey (deadline: 2021-06-28 h 23:59)
- Video-chat for Q&A and clarifications: Thursday 10/06, h. 10:00 - video recording
- Slack channel for discussion and Q&A: #exam1-survey
- Live document with the answers to questions raised on Slack
- Link for project skeleton and exam submission (on GitHub Classroom)
- Exam #2: Meme Generator (deadline: 2021-07-12 h 23:59)
- Video-chat for Q&A and clarifications: Monday 28/06, h. 14:30 - video recording
- Slack channel for discussion and Q&A: #exam2-meme
- Link for project skeleton and exam submission (on GitHub Classroom)
- Exam #3: Study Groups (deadline: 2021-09-07 h 23:59)
- Video-chat for Q&A and clarifications: Monday 23/08, h. 10:00 - video recording
- Slack channel for discussion and Q&A: #exam3-studygroups
- Link for project skeleton and exam submission (on GitHub Classroom)
- Exam #4: Forms (extra exam session for terminal students - deadline: 2021-10-27, h 23:59)
- Slack channel for discussion and Q&A: #exam4-forms
- Link for project skeleton and exam submission (on GitHub Classroom)
- Exam #5: Crucipuzzle (deadline: 2022-01-19, h 23:59)
- Slack channel for discussion and Q&A: #exam5-crucipuzzle
- Link for project skeleton and exam submission (on GitHub Classroom)
- Oral discussions: 2022-01-27, starting at 14:30, in ACS-Lab room (besides LABINF)
Exams from previous years
Year 2019/2020
- Exam #1: Car Rental (deadline: 28/06/2020 23:59)
- Video-chat for clarifications: Friday 12/06 h 9:00-11:00
- Slack channel for discussion and Q&A: #exam1-car-rental
- On-line document with the answers to questions raised on Slack
- Link for project skeleton and exam submission (on GitHub Classroom)
- Exam #2: Kanban (deadline: 12/07/2020 23:59)
- Video-chat for clarifications: Friday 12/06 h 9:00-11:00
- Slack channel for discussion and Q&A: #exam2-kanban
- On-line document with the answers to questions raised on Slack
- Link for project skeleton and exam submission (on GitHub Classroom)
- Exam #3: Scheduling (deadline: 09/09/2020 23:59)
- Video-chat for clarifications: Wednesday 26/08 h 10:00 - see video recording
- Slack channel for discussion and Q&A: #exam3-scheduling
- On-line document with the answers to questions raised on Slack
- Link for project skeleton and exam submission (on GitHub Classroom)
- Exam #4: Pizza (deadline: 20/01/2021 23:59)
- Video-chat for clarifications: Thusday 07/01/2021 h. 15:00 see video recording
- Slack channel for discussion and Q&A: #exam4-pizza
- On-line document with the answers to questions raised on Slack
- Link for project skeleton and exam submission (on GitHub Classroom)
Additional information:
Exam Rules
The exam of Web Applications I (WA1), due to the COVID-19 pandemic, will take place as described in the following, typically from remote.
The exam consists in a web application project to be developed according to the specifications that will be published 20 days in advance with respect to each official exam date ("data appello"), plus an oral discussion of such project. For each official date a new assignment, different from the previous one, will have to be developed. The assignment is valid ONLY for the official exam date to which it is explicitly connected.
The web application project must be developed by each student INDIVIDUALLY. During the oral exam each student should be able to prove that he/she was able to develop the project in full autonomy by showing complete and full knowledge of every part of his/her project solution.
Before the deadline (typically, the official exam date), the final version of the project will have to be submitted according to the provided technical instructions.
If instructions are not carefully followed, for instance if the project cannot be run and tested as is by the teacher with the standard configuration (as per the technical instructions), the exam will be considered as failed.
A few days after publishing the assignment the teachers will be available in a video-chat to discuss potential doubts about the assignment (e.g., unclearly or ambiguously expressed requirements). Any interested student will be able to participate in the question-answer session, or to ask questions over Slack.
The submission deadline for the project is at 23:59 of the day before the official exam date.
For submitting the exam, it is mandatory to enroll in the exam booking ("prenotazione esami"). The students admitted to the exam will be those that are correctly enrolled AND have turned in the project before the deadline. There will be no penalty for students who enroll but do not submit the project (they will be marked as "absent").
After the submission deadline, the teachers will evaluate the submitted solutions and provide a score for each one of them. Depending on the number of submissions, such process might take some days. Also, projects which do not meet minimum criteria will be evaluated as insufficient, with consequent failure of the exam, without the possibility to access the oral exam.
The evaluation criteria for the submitted project will be: functional completeness, absence of unhandled errors, client-server organization, component architecture according to the React guidelines, clarity and organization of the code.
Then, a schedule will be published for the oral exam. Each student deemed sufficient for the project part will be allocated to a time slot, during which he/she will be remotely connected with the teacher (with some other students as witnesses as required by the official examination rules by the Politecnico). The student will have to show some form of identification (ID card or passport, etc.) before the discussion, and he/she will be alone in front of the computer with the webcam turned on. The aim of the oral exam is to ensure that each student developed the web application by him/herself, and to evaluate how much the student can explain the exact behaviour of the code. The source code will be opened by on the teacher's computer which will share the screen with the student. In the eventuality that the oral exam will be done in-person, we will follow the same procedure.
Therefore, during the oral exam the student must be able to explain everything about the project that is asked by the teacher. This includes, but is not limited to, the reasons behind the architectural choices for his/her own application, the details about how any specific fragment of code works, why it was implemented in that way, and what alternatives could have been used, etc.
The evaluation criteria for the oral will be: theoretical and practical knowledge of the project design, theoretical and practical knowledge of the project code base, readiness and clarity in the replies.
There will be 24 marks assigned to the project, and 6 marks assigned to the oral discussion. The minimum project score to be admitted to the oral discussion is 12. The oral is mandatory (students can refuse to take the oral, of course, and the score will be nullified). The final score after the oral can not be refused.
The final mark will be the sum of the scores for the submitted project, the score assigned at the end of the oral exam, and the results from the BigLabs (if submitted). If the exam results in a failure, even just for the oral part, the score for the project will NOT be carried over to the next official exam dates: the new project corresponding to the new exam date will have to be developed. Please, also notice that the score of the BigLabs will last for an entire year (i.e., 4 exam sessions, until the beginning of a new edition of the course).
Since the exam is essentially the design of an application with rather generic specifications, it is not acceptable that the submitted solutions are excessively similar among them, which would indicate that the solution has not been developed autonomously. Similarity checks will be run after the deadline. In this case the exam will be considered as failed and the students notified about the situation.
RECOMMENDATIONS:
Each student, during the oral exam, must be able to immediately find and carefully explain any part of the code in the project that implements a given feature asked by the teacher. Therefore, it is strongly recommended that the student carefully rehearse and review the code shortly before the oral exam. Situations in which the student claims not to be able to "remember" things (where the code is, in which file, why it works that way, etc.) due to any reason (for instance "it has been a few days since I developed it", or similar claims) will lead to immediate exam failure.
As in any programming assignment, during the development phase, it is possible to search online for suggestions and examples about how to solve specific programming issues, which can be incorporated in the final solution. However, regardless of the source, the student must be able to explain how the code submitted as the final solution works, regardless of the source (online examples, templates, etc.). Verbatim copy of portions of code without the student being able to explain how it works will be subject to strong penalty in the final mark if found during oral examination.
In the solution, it is recommended to employ all the good practices and good programming techniques explained during the lectures. Strong deviations from such patterns will have to be duly justified during the oral exam and, if not adequately justified, will cause a reduction of the final mark, and potentially also a failed exam.
Regarding the use of external libraries/templates/modules: as a general rule, the use of the techniques shown during the classes is preferred. The use of external modules and libraries for non-essential functions is allowed: examples are date/time handling, presentation aspects, predefined components (e.g., calendars), and similar items.
If React requires the use of certain programming patterns, those must be followed. As an example, it is NOT allowed to use JQuery or JS directly to modify DOM content within the browser. It is NOT allowed to use frameworks different from React (Vue, Angular, etc.). It is not allowed to use server-side technologies different from those shown in the classes: Express, with SQLite to implement DB access, and the React internal web server must be used. Also, remember that the solution MUST be submitted in a way that can be readily tested by the teacher with the commands specified in the technical instructions. Any solution not running in this way will be considered as failed.