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 are in accordance with accessibility and usabil
   
   

• 
  
  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.
  
  

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.

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.

Classification = 20% NI + 80% NP

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 2 values​​, based on the opinion of the teachers and the self-assessment performed by each group.

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.