J. Correia Lopes

FEUP/DEI & INESC TEC

User Tools

Site Tools


teach:lbaw:bylaws

Project by-laws

Master in Informatics and Computing Engineering
Database and Web Applications Laboratory
Instance: 2018/2019


1. Introduction

The evaluation in LBAW focuses on a practical work to be performed in groups of four students and an individual assessment in a multiple choice test.

The Unit's Moodle Discussion forum 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 colleagues.

2. Practical work

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

3. 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 artefacts, required to be delivered for assessment, must be accessible in the Moodle of the group before the deadline. The suggested content for documents and artefacts 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 artefacts must follow the structure of the templates and submitted in PDF.

4. Technologies

The project is based on a default technology stack. Key technologies to be used are: PostgreSQL at the database level; PHP as a programming language on the server; Laravel as the server framework; Git for software versioning; NGINX as web server; Bootstrap as the front-end framework; and HTML, CSS and 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 base technologies, should include authentication and user management and another complete not trivial module. In these cases, when using different technologies, the support provided by the teachers is limited. The group is at its own risk as to the timely completion of the final Product to be delivered.

5. Assessment

The practical assessment comprises the artefacts, the product delivered, and its presentation.

Details and the weight of each component in the evaluation are published in the course 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 per week).

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 (ER, EBD, EAP, PA) are divided into 11 artefacts (A1-A11). The artefacts are classified with 0 to 10 values in the pre-established dates and can be improved by up to 2 values in the following laboratory class. Initial ratings exceeding 7 may only be improved in 1 value. The grades of the artefacts after re-submission and the grade of each assessment component is published when all its artefacts are graded.

All work must be delivered within the deadline published in the Course plan. The deadline for delivery is 24 hours before the start of the corresponding practical class of the week.

The artefacts should be self-contained to serve as a basis of evaluation (i.e., they 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 contained in the deliverable (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 placed on the artefact A11, to be used by teachers during assessment.


João Correia Lopes, Sérgio Nunes

teach/lbaw/bylaws.txt · Last modified: 01/03/2019 15:24 by Correia Lopes