Guia docente 2015_16
Escola de Enxeñaría de Telecomunicación
Grao en Enxeñaría de Tecnoloxías de Telecomunicación
 Subjects
  Programming II
   Assessment
  Description Qualification Training and Learning Results
Projects The students, organized in pairs, will submit the proposed software project before January 6. It must include the final design (UML diagrams), the code and the generated documentation about the implementation details. It is an indispensable condition to overcome this proof of evaluation that the code can be compiled and run on the computers of the laboratory.
During the last week of the course, the students will have an interview with the teacher in the laboratory hours, with the aim of proving the authorship of the project and to perform different functionality tests. Both members of the group must attend the interview. The issues raised therein must be answered individually to verify the degree of understanding and involvement of the student in the developed project.
If a student does not demonstrate the authorship adequately, the evaluation of the project will be done through an individual programming practical exam in the laboratory in the date published in www.teleco.uvigo.es for this purpose. If the student does not attend this exam he/she will lose a 30% of the mark of the subject.
For the students that demostrate the authorship adequately, the evaluation of the project will take into account the correct functionality, the quality of the code and the use of the techniques of object oriented programming.
30 B6
B14
C50
C53
Case studies / analysis of situations At the end of the 9th week of the academic course the students, organized in pairs, will submit the design of a software project. 10 C51
C52
Troubleshooting and / or exercises Written exam to be done individually in the date published in www.teleco.uvigo.es for this purpose, which will consist of the combination of the following types of questions: resolution of problems, short questions about the theoretical concepts explained in the master sessions, to justify reasonably if one or more statements are true or false, small tests about theoretical and application aspects. The number and combination of these questions will be defined for each particular exam. Support materials (notes, books, collections of problems) are not allowed. 50 C50
C51
C53
Practical tests, real task execution and / or simulated. At the end of the 7th week of the academic course the students, organized in pairs, will submit the Java initiation practices proposed in the laboratory. 10 C50
C51
C52
C53
 
Other comments on the Evaluation

There are two modalities of evaluation of this subject: continuous evaluation (CE) and traditional evaluation (TE). The students will have to choose one of the two modalities taking into account the following conditions:

- The CE includes the 4 proofs described in the evaluation section.

- Whether they opt for the CE or for the TE, students must develop a project. To facilitate the choice between CE and TE, the specifications of the project will be available in Faitic the 4th week of the academic course.

- In the TE the project will be carried out individually.

- The students that choose the CE will submit at the end of the 9th week of the academic course the UML design of the project (corresponding to the 2nd proof described in the evaluation section). By means of this submission the students agree to follow the CE and reject the TE. From this moment these students may not appear as if they have not taken the subject.

- The students that do not submit the UML design of the project in the stipulated date reject the CE, so that they will be evaluated by means of the modality of TE. It is not possible to join the CE in the following intermediate proofs.

- The proofs of CE are not recoverable in any case, and they can not be repeated outside the dates stipulated by the teachers.

- Marks (of proofs of CE or practical projects or exams) are not saved from one course to another.

First call. Students who opt for the CE. They will be evaluated as follows:

• Theoretical part:

- Written exam (50%). Individual exam. It corresponds to the 3rd proof described in the evaluation section. The mark of this exam will not be never saved for others convocatories.

• Practical part:

- Practices of initiation in Java (10%). To be done in pairs. It corresponds to the 4th proof described in the evaluation section.

- Project (40%). To be done in pairs. It is divided in two parts:

1. Design (10%). It corresponds to the 2nd proof described in the evaluation section.

2. Implementation (30%). It corresponds to the 1st proof described in the evaluation section.

• The requirements to pass will be:

- A minimum of 1/3 of the total in the theoretical part.

- A minimum of 1/3 of the total in the part of implementation of the project (or 1/3 of the total of the practical exam according to the case). 

- A total mark (sum of the 4 proofs) equal or higher than 5.

- If the total mark is equal or higher than 5 but the minimun in some part has not been reached, the final mark will be 4.5 points (failure).

First call. Students who opt for the TE. They will be evaluated as follows:

• Theoretical part:

- Written exam (50%). Individual exam. It corresponds to the 3rd proof described in the evaluation section. The mark of this exam will not be never saved for others convocatories.

• Practical part:

- Individual realization of a software project that will suppose the remaining 50% of the final mark. This project will consist of the design (UML diagrams), the Java code and the generated documentation about the implementation details. The evaluation will take into account correct design, correct functionality, quality of the code and use of techniques of OOP. It must be submitted before January 6.

- Realization of an interview with the teacher with the aim of proving the authorship of the project. This interview will take place in the laboratory hours during the last week of the course. If a student does not demonstrate adequately the authorship, the evaluation of the practical part will be done through a programming practical exam.

• The requirements to pass will be:

- A minimum of 1/3 of the total in the theoretical part.

- A minimum of 1/3 of the total in the part of the project (or 1/3 of the total of the practical exam according to the case). 

- A total mark (sum of the 2 proofs) equal or higher than 5.

- If the total mark is equal or higher than 5 but the minimun in some part has not been reached, the final mark will be 4.5 points (failure).

Second call. The students will be evaluated as follows:

• Theoretical part:

- Written exam (50%). Individual exam. It corresponds to the 3rd proof described in the evaluation section. The mark of this exam will not be never saved for others convocatories.

• Practical part:

It will depend on whether the student has delivered or not the project in the first call. For the students that have followed the CE in the first call, it will be considered that a student has delivered the project when, as least, he/she has submitted an UML design in which he/she has obtained a mark equal or higher than 0.6 of 1.

- The students that do not deliver the project in the first call will be evaluated through an individual programming practical exam, to be done in the laboratory in the date published in www.teleco.uvigo.es for this purpose. The evaluation of this exam will suppose a 50\% of the final mark.

- The practical part to be done for the students that deliver the project in the first call will depend on the mark obtained in the project in that call, as follows:

Mark >= 1.5 with CE or Mark >= 2.5 with TE. They will keep the mark, not having to attend the practical exam of the second call. However, they will be able to improve the mark of the project delivering a new version of the one of the first call together with the new functionalities to be done, that will be published in Faitic. In the same way, they will deliver a document that addresses the changes and updates in the project from the version delivered in the first call.

Mark between 1 and 1.5 with CE or Mark between 5/3 and 2.5 with TE. They may opt for doing the practical exam or the extended project of the second call. They will not keep the mark of the project of the first call, but they will keep the marks of the parts of initiation in Java and UML design if they have opted for the CE in the first call.

Mark < 1 with CE or Mark < 5/3 with TE. They may opt for doing the practical exam or the extended project of the second call. In any case, they will not keep the marks of the parts of initiation in Java and UML design if they have opted for the CE in the first call, that is, they will be evaluated on 5.

• The requirements to pass will be:

- A minimum of 1/3 of the total in the theoretical part.

- A minimum of 1/3 of the total of the project without taking into account the marks of the parts of initiation in Java and UML design if they have opted for the CE in the first call (or 1/3 of the total of the practical exam according to the case). 

- A total mark (sum of all the proofs) equal or higher than 5.

- If the total mark is equal or higher than 5 but the minimun in some part has not been reached, the final mark will be 4.5 points (failure).

Universidade de Vigo            | Reitoría | Campus Universitario | C.P. 36.310 Vigo (Pontevedra) | España | Tlf: +34 986 812 000