users_has_groups ▼ users 1 1.. 1.." 1 users_id INT id INT groups_id INT groups id INT 1 1.." services_has_groups services_username VARCHAR(50) groups_id INT 1.. services username VARCHAR(50) Please consider that the above diagram is a simplified version, i.e., it only contains the relevant information (e.g., primary and foreign keys). Important: not fulfilling this requirement corresponds to a rejection of the project. 4. Graphic Layout It is not requested that the HTML/CSS graphic layout is realized on your own. The candidate is prescribed to adopt one layout chosen from template repositories or even from existing website. The evaluation of this aspect corresponds in assessing whether the chosen layout is appropriate for the proposed web application, i.e., the layout evaluation will contribute to the overall evaluation. Please note how the evaluation will be on the chosen layout regardless whether it has been downloaded from an existing layout or it is realized from scratch by the student. 5. Administration dashboa Depending on the kind of application, the backend (see next Section) can have a different layout. In this case, the following factors will be evaluated: coverage: the application must provide all the CRUD operation that are needed to manage any dynamic aspect usability: the application must be usable and provide a comfortable environment functionality: the application must be well-thought and organized to maximize productivity 6. Material to be submitted for the examination The project must be managed on GitHub and all the commits must be performed with individual accounts, i.e., each member of the project team must use her/his own account (no team account admitted). It must be possible to assess an equal contribution to the project by all team members. TECNOLOGIE DEL WEB 2023/2023 (VER 1.1) Prof. Alfonso Pierantonio 1. Project Requirements The project consists in designing and implementing a Web application according to the methodology and the technologies illustrated and developed during the course. This document describe cross-cutting requirements the application must satisfy. The application must be realized with a combination of the following technologies: PHP MySQL HTML/CSS JavaScript, jQuery, etc templating The requirements are 2. Project size The application must have at least 18 SQL tables The number of SQL tables refers to the overall number of tables (including relation normalizations). 3. Methodology The application must be realized by adopting separation of logics, session management, and generic user management (authentication/permissions). Missing one of the above might correspond to a non sufficient score for the project. More in details: 3.1 Separation of Logics The separation of logics has to be realizse by using template2.inc.php illustrated and distributed during the course Important: other template engines must be agreed with the lecturer. 3.2 Session Management The application must use session management for realizing session persistent abstractions, e.g., e- commerce chart, authentication, preference management, etc. 3.3 Generic User Management The application must have an advanced user management, which relies on the classical model users-groups-services as outlined in the following diagram: