Table of Contents
Course Fact sheet
Master in Informatics and Computing Engineering
Database and Web Applications Laboratory
Course Unit: Database and Web Applications Laboratory
Programmes: MIEIC, 3º
Academic Year: 2018/2019
Credits: 7 ECTS
Hours/Weeks: 1x2T, 7x3P
Teachers: João Correia Lopes | Sérgio Nunes
Portuguese. Suitable for English-speaking students.
The unit aims at revisit 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:
- Specify the requirements of the information system;
- Obtain the conceptual model of the information system's data;
- Obtain and validate the logical relational database schema of the system's database;
- Obtain the physical schema of the database and tune the logical relational schema;
- Design and implement queries to access the database using SQL;
- Design and implement mechanisms for maintaining the integrity of the data;
- Specify the web interfaces and business logic of the information system;
- Implement the web components of the system using web-based, server-based and client-based technologies;
- Ensure that the web interfaces are in accordance with accessibility and usability standards.
Pre-requirements (prior knowledge) and co-requirements (common knowledge)
Databases: data modeling with UML, relational model, SQL language.
- Development of a web application supported by a database: requirements gathering, design, modelling, implementation and documentation.
- General notions on the architecture of web applications using client scripting languages and server languages.
- Use of frameworks and API for data access.
- Design of relational databases using data modelling 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 usability and Web Design.
- R. Ramakrishnan, J. Gehrke, Database Management Systems, McGRAW-Hill International Editions, 3rd Edition, 2003, ISBN=0-07-246563-8. Library
- Jeffrey D. Ullman, Jennifer Widom, A First Course in Database Systems, Prentice-Hall, 3rd Edition, 2008, ISBN=978-0-13-600-637-4. Library
- Scott Ambler, The Object Primer, Cambridge University Press, 3rd Edition, 2004, ISBN: 978-0-521-54018-6 Library
- Zalewski, Michal, The tangled Web: a guide to securing modern Web applications, No Starch Press, Inc. ed, 2011, ISBN=978-1-59327-388-0. Library
- Jakob Nielsen, Designing Web Usability: The Practice of Simplicity, New Riders Publishing, Indianapolis, 2000, ISBN=1-56205-810-X. Library
Teaching methods and learning activities
The lectures will be used for presentation of the scripts of the work and representative examples and their discussion, analysis of assessments and brief introductions to the technologies they use. The practical classes will be used for laboratory project development as a group project with the teacher as a consultant.
- PHP e Laravel
Physical sciences > Computer science > Informatics
Type of assessment
Distributed evaluation without final exam
Registered evaluation and occupation components
|Description||Type||Time (Hours)||Date of conclusion|
|User requirements specification||Laboratory work or fieldwork||20||18/03/2019|
|Database specification||Laboratory work or fieldwork||20||15/04/2019|
|Architecture specification and Vertical prototype||Laboratory work or fieldwork||36||05/05/2019|
|Product||Laboratory work or fieldwork||44||27/05/2019|
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% in the individual response questionnaire and 50% in each of the components of the practical assessment.
A student that does not participate in an evaluation component may have an assessment to that component different from the group to which he belongs.
Given the laboratory nature of the course and the work in teams, 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 = 20% NI + 80% NP
Being NP = 20% ER + 20% EBD + 20% EAP + 40% PA
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 2 values, based on the opinion of the teachers and the self-assessment performed by each group.
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 the enrolment regime.
Students exempted from classes must agree to conduct regular meetings with 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.
Students may improve the mark in the course's next edition.
— João Correia Lopes, Sérgio Nunes/