Go to:
Logótipo
You are here: Start > EIC0085

Database and Web Applications Laboratory

Code: EIC0085     Acronym: LBAW

Keywords
Classification Keyword
OFICIAL Information Systems

Instance: 2020/2021 - 2S Ícone do Moodle

Active? Yes
Web Page: http://web.fe.up.pt/~jlopes/doku.php/teach/lbaw/index
Responsible unit: Department of Informatics Engineering
Course/CS Responsible: Master in Informatics and Computing Engineering

Cycles of Study/Courses

Acronym No. of Students Study Plan Curricular Years Credits UCN Credits ECTS Contact hours Total Time
MIEIC 166 Syllabus since 2009/2010 3 - 7,5 70 202,5

Teaching Staff - Responsibilities

Teacher Responsibility
João António Correia Lopes
Sérgio Sobral Nunes

Teaching - Hours

Lectures: 2,00
Laboratory Practice: 3,00
Type Teacher Classes Hour
Lectures Totals 1 2,00
João António Correia Lopes 1,00
Sérgio Sobral Nunes 1,00
Laboratory Practice Totals 7 21,00
Fernando José Cassola Marques 3,00
João António Correia Lopes 6,00
Sérgio Sobral Nunes 6,00
Tiago Boldt Pereira de Sousa 6,00
Mais informaçõesLast updated on 2020-07-31.

Fields changed: Learning outcomes and competences, Métodos de ensino e atividades de aprendizagem, Software de apoio à Unidade Curricular, Obtenção de frequência, Programa, Fórmula de cálculo da classificação final

Teaching language

Portuguese

Objectives

This unit revisits the learning outcome of the previous courses in databases and web languages ​and technologies, providing a practical perspective on these core areas​ of computer engineering.

In this course, the students will learn how to design and develop web-based information systems backed by database management systems.

Learning outcomes and competences

After completing this course, the student will be able to:

  1. Specify the requirements of the information system;
  2. Obtain the conceptual model of the information system's data;
  3. Obtain and validate the logical relational database schema of the system's database;
  4. Obtain the physical schema of the database and tune the logical relational schema;
  5. Design and implement queries to access the database using SQL;
  6. Design and implement mechanisms for maintaining the integrity of the data;
  7. Specify the web interfaces and business logic of the information system;
  8. Implement the web components of the system using web-based, server-based and client-based technologies;
  9. Ensure that the web interfaces adopt accessibility and usability standards.
  10. Package and distribute the information system in a portable and reconfigurable way.

Working method

Presencial

Pre-requirements (prior knowledge) and co-requirements (common knowledge)

Databases: data modelling with UML, relational model, SQL language.

Web languages ​​and technologies: HTTP protocol, HTML, CSS and JavaScript languages.

Program


  • Development of a web application supported by a database: requirements gathering, design, modeling, implementation and documentation;

  • Design and implementation of a web application's architecture. Use of client scripting languages and server languages;

  • Use of framework and API for data access;

  • Design of relational databases using data modeling languages (UML), the SQL language and procedural extensions to SQL;

  • Identification and maintenance of business rules: on the interface, on the business logic and in the database (triggers); define transactions;

  • General notions of web usability and accessibility.

Mandatory literature

Ramakrishnan, Raghu; Database management systems. ISBN: 0-07-116898-2

Complementary Bibliography

Jeffrey D. Ullman, Jennifer Widom; A First course in database systems. ISBN: 978-0-13-600-637-4
Russ Miles and Kim Hamilton; Learning UML 2.0. ISBN: 978-0-596-00982-3
Michal Zalewski; The tangled Web. ISBN: 978-1-59327-388-0
Nielsen, Jakob; Designing web usability. ISBN: 1-56205-810-X

Teaching methods and learning activities

The lectures will be used to present the work scripts, to discuss representative examples, to analyze the evaluations carried out, and to present the technologies and concepts to be used. The practical classes will be used for the laboratory development of the project, in a group, with the teacher as a consultant. In each practical class, the artifacts produced by the group are presented and discussed.

Software

Laravel
Git
PostgreSQL
Docker
PHP

keywords

Physical sciences > Computer science > Informatics

Evaluation Type

Distributed evaluation without final exam

Assessment Components

Designation Weight (%)
Teste 20,00
Trabalho laboratorial 80,00
Total: 100,00

Amount of time allocated to each course unit

Designation Time (hours)
Elaboração de projeto 122,00
Frequência das aulas 70,00
Total: 192,00

Eligibility for exams

The practical work will be assessed during the laboratory classes, through the delivery of the artefacts.

The theoretical concepts are evaluated using an individual questionnaire with multiple choice questions.

The approval for the course is conditional on the student obtaining 40% (8,0 in 20) in the individual response questionnaire and 50% in each of the components of the practical assessment.

It should be noted that a student, depending on the individual contribution to an evaluation component, may have a classification in that component different from the classification of the group to which he belongs.

Given the laboratory nature of the course, it is not possible to make an overall evaluation based on a single moment and therefore the practical work can not be replaced by a single exam.

Calculation formula of final grade

Classification = 80% NP + 20% NI

Being

NP = 20% ER + 20% EBD + 20% EAP + 40% PA

Legend:

  • NI - Individual multiple choice questionnaire
  • NP - Practical work
  • ER - Requirements Specification
  • EBD - Database Specification
  • EAP - Architecture Specification and Vertical Prototype
  • PA - Product and Presentation

The final classification of the practical component (NP) can vary from element to element in the same group, plus or minus 3 values​​, based on the opinion of the teachers and the self-assessment performed by each group.

Students who do not get approved in the final classification have to repeat the two evaluation components (NI and NP) in a new enrolment to the unit. This means that the classifications obtained in one occurrence of the course cannot be used in another occurrence of the course.

Examinations or Special Assignments

There are no special works or tests.

Special assessment (TE, DA, ...)

The project evaluation, conducted in a group, is the same for all students regardless of enrollment regime.

Students exempted from classes must agree to conduct regular meetings with the teachers to keep up with the practical work. Regarding the final presentation and the individual assessments, the rules are the same as for the regular students.

Classification improvement

Students may improve the mark in the course's next edition.

Recommend this page Top
Copyright 1996-2022 © Faculdade de Engenharia da Universidade do Porto  I Terms and Conditions  I Accessibility  I Index A-Z  I Guest Book
Page generated on: 2022-08-16 at 23:28:36 | Reports Portal