JCL

FEUP/DEI & INESC TEC

User Tools

Site Tools


teach:lbaw:bylaws

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Previous revision
teach:lbaw:bylaws [10/02/2020 14:40]
teach:lbaw:bylaws [22/03/2021 13:22] (current)
Sérgio Nunes [5. Assessment]
Line 1: Line 1:
 +====== Project by-laws ======
  
 +**Master in Informatics and Computing Engineering\\
 +  Database and Web Applications Laboratory\\
 +  Instance: 2020/2021**
 +\\
 +---
 +\\
 +
 +===== - Introduction =====
 +
 +The evaluation in LBAW is focused on a practical work to be performed in **groups of four students** and an individual assessment based on a multiple choice test.
 +
 +The [[https://moodle.up.pt/mod/forum/view.php?id=96108|Discussion Forum at Moodle]] is the preferred means of electronic contact with teachers. 
 +The use of this forum allows a quick response by any of the teachers or by your colleagues.
 +
 +We also manage a [[https://feup-lbaw.slack.com|Slack workspace]] for immediate communication. Avoid using it for questions that require interaction and might be of interest to more students.
 +
 +
 +===== - Practical work =====
 +
 +LBAW is designed to consolidate the materials exposed in previous courses, in particular databases and web technologies, through the development of an information system with a web interface and supported by a relational database management system.
 +
 +The theme of the project should be chosen from a [[proposals|list of proposals]]. 
 +The project dimension should lead to the identification of approximately 10 organizational entities (15 to 25 tables in the database). 
 +All web applications must include features to allow the registration and administration of users, the management of access permissions, and non-trivial search features. 
 +The theme of the project cannot be repeated in the same class.
 +
 +The work of each group must be original. 
 +All used sources (code blocks, phrases, figures, etc.) and aids (documents, colleagues, etc.) must be clearly identified. 
 +Failing to do so will result in a penalty in the final assessment. 
 +
 +===== - Documentation =====
 +
 +This course will have a lot of written documentation. 
 +In addition to the written rules of the language (Portuguese or English), to better convey the ideas it is essential that a technical writing style is used, so that the simplicity of writing and the absence of ambiguity facilitates their understanding.
 +
 +Gross mistakes, easily preventable through the use of spell checkers, and grammar errors due to misuse of language, will be penalized. 
 +These errors impair the legibility making it difficult to read and understand the documents. 
 +In Portuguese, the rules of the new orthographic agreement should be used. 
 +
 +All components, required to be delivered for assessment, must be submitted in Moodle before the deadline. 
 +The suggested structure for documents and components is detailed and exemplified in lectures and in separate documents devoted to the delivery (templates), but it can be arranged differently from what is shown. 
 +Nevertheless, the components must follow the structure of the templates and be submitted **in PDF**.
 +
 +===== - Technologies =====
 +
 +The practical work that will be developed is based on a default technology stack. 
 +Key technologies to be used are:
 +[[http://www.postgresql.org/|PostgreSQL]] at the database level; 
 +[[http://www.php.net/|PHP]] as a programming language on the server;
 +[[http://docker.com|Docker]] as a virtualization environment;
 +[[https://laravel.com/|Laravel]] as the server framework;
 +[[http://git-scm.com/|Git]] for software versioning;
 +[[http://nginx.org/en/|NGINX]] as web server; and
 +[[http://www.w3.org/html/|HTML]], [[http://www.w3.org/css/|CSS]] and [[https://developer.mozilla.org/en-US/docs/Web/JavaScript|JavaScript]] as client languages.
 +
 +The use of other extensions or libraries, other than those identified herein, requires authorization by the teachers.
 +
 +The Vertical Prototype must be developed based on the prototype example provided. 
 +After the evaluation of the prototype, the group can discuss with the teachers the use of any other framework, provided that the final product can run in the production machine.
 +
 +However, the prototype delivered by the group must be large enough to demonstrate the mastery of the default technology stack, should include authentication and user management, and another complete not trivial module.
 +
 +===== - Assessment =====
 +
 +The practical assessment comprises the components (groups of artefacts), the product delivered, and its presentation.
 +
 +Details and the weight of each component in the evaluation are published in the course [[sheet#final_grade|Fact sheet]]. 
 +It should be noted that the assessment reflects the quality of the work produced rather than the amount of work (i.e., the number of hours spent).
 +
 +All students are expected to participate, with greater or lesser involvement, in all project tasks (analysis, design, coding, testing, presentation) in order to satisfy the minimum grade in each evaluation component (and also so that they can learn the concepts, methodologies and tools involved, and feel the main problems associated!). 
 +
 +The four evaluation components, Requirements (ER), Database (EBD) | Architecture (EAP) | Product (PA), are divided into 10 artefacts ([[.:artefacts:index|A1-A10]]). 
 +
 +All components must be delivered within the deadline published in the [[plan|Course plan]]. 
 +The deadline for delivery is <del>19h00</del> **12h00 of the day before** the practical class of the week. 
 +The components are delivered in Moodle and should be self-contained in PDF files to serve as a basis of evaluation (i.e., it cannot contain links to external documents).
 +
 +It is the group's responsibility to ensure that teachers will assess the correct materials and that all materials to review are submitted in Moodle (for example, links to download materials from external sites will not be considered). 
 +
 +The credentials required for using the product during the evaluation must be included in the final component (PA).
 +
 +===== - Conclusions =====
 +
 +The practical work of the course should follow the rules presented and the project to be developed by the working group should meet the goals and the user requirements.
 +
 +\\
 + --- //João Correia Lopes, Sérgio Nunes//