The students, organized into groups of 2 people, will submit a software project during the week from 2 to 6 of December of the course. This submission must include the UML diagrams of the final design, the code and the documentation about the implementation details. The software must run correctly on the computers of the educational laboratories. In the assessment, the professor will consider both the correct execution of the program and the designed adopted in the development.
With this test CE53, CE50, A6 (CG6), A9( CG9) and B5 competences will be assessed.
30
Case studies / analysis of situations
The students, organized into groups of 2 people, will submit and present in the computer room the design defined for the project software, including UML class diagrams. This design will be submitted during the week from 4 to 7 of November of the course.
With this test CE51, CE52 and A9 competences will be assessed.
10
Troubleshooting and / or exercises
Each student will take a final exam in the official date published in www.teleco.uvigo.es, which will consist of the following types of questions: resolution of problems, short-answer questions about the theoretical concepts explained in master sessions, true/false assessments, multiple-choice tests. Note that support materials are not allowed. The number and the combination of the aforementioned questions will be defined for each particular exam.
With this test, CE50, CE51 and CE53 competences will be assessed.
50
Practical tests, real task execution and / or simulated.
The students, organized into groups of 2 people, will submit the Java initiation practices proposed in the computer room. This submission will take place during the week from 21 to 25 of October of the course.
With this test, CE50, CE52 and CE53 competences will be assessed.
10
Other comments on the Evaluation
Thee are two modalities in the evaluation of this subject: continuous evaluation (EC) and traditional evaluation (ET).
The students will have to choose one of the two modalities taking into account the following restrictions:
The EC includes the 4 proofs described in the separated evaluation.
So much by EC as by ET, the students will have to realise a project of laboratory. To facilitate the election of EC or ET the students will have in Faitic platform of the project to realise from the day 20 September.
In ET the project will realise of individual form.
The students that opt by the EC will have to deliver in the first week of November, the UML design of the project posed in the laboratory (corresponding to the 3ª proof of evaluation). By means of said delivers the students engage to be followed the EC and renounce to the ET. From this moment, these students will not be able to appear as "No presented".
The students that do not deliver the UML design of the project in the week of the 4 to 7 November, renounce to the EC, so that they will be evaluated by means of the mechanism of ET. It does not exist the possibility to add to EC in the following intermediate proofs.
The proofs of EC will not be in no case recoverable, not being able to repeat out of the dates stipulated by the educational.
They will not save qualifications (of proofs of EC neither of practical projects or final examinations) of a course to another.
The EC only will apply in the first announcement, in the rest of announcements governs only the ET.
First announcement. Students that opt by EC. They will be evaluated as follows:
Theoretical part:
Examination written (50%). Individual examination. It corresponds with the proof 3 described in the separated "Evaluation". It will not allow material of support.
Practical part:
Practices of initiation in Java (10%). In groups of 2 students. It corresponds with the proof 4 described in the separated "Evaluation".
Project (40%). In groups of 2 students. Divided in two parts:
Design (10%). It corresponds with the proof 2 described in the separated "Evaluation".
Implementation (30%). It corresponds with the proof 3 described in the separated "Evaluation". This project will have to be delivered individually the first week of December of the educational period. For his evaluation will realise , like previous requirement, a proof or interview of authorship:
If the student does not surpass it, the evaluation of the implementation realised by an examination practise.
If the student surpasses the proof of authorship, his note of evaluation (that it will be the same for both members of the group) will take into account: correct design, correct functionality, quality of the code and use of technicians of OOP.
The requirements to approve will be:
A minimum of 1/3 on the total in the theoretical part.
A minimum of 1/3 on the total in the part of implementation of the project (or 1/3 on the total of the practical examination in his case).
A total note (sum of the 4 proofs) equal or upper to 5.
For the proof of authorship of the practical part (that it can suppose individual questions of diverse nature) will be compulsory that the code delivered can be compiled and executed in the teams of the educational laboratories.
First announcement. Students that opt by ET. They will be evaluated as follows:
Theoretical part:
An examination written (whose description coincides with the proof 3 of EC). The result of this examination will suppose 50% of the final qualification. It will not allow material of support.
Practical part:
The realisation of a software project that will suppose the other 50% of the final qualification. Of individual realisation. This project will consist of design (UML diagrams), the Java code and the documentation generated explanatory of the implementation. The note of evaluation will take into account: correct design, correct functionality, quality of the code and use of technicians of OOP model. This project will have to be delivered individually the first week of December.
The realisation of an interview with the tutor oriented to determine the authorship of the project. Said interview will take place in the laboratory thelast academic week of the course. If the student does not surpass the proof of authorship will have to go to an examination practise.
The requirements to approve will be:
A minimum of 1/3 on the total in the theoretical part.
A minimum of 1/3 on the total in the project or practical examination according to the case.
A total note (sum of the 2 proofs) equal or upper to 5.
For the proof of authorship of the practical part (that it can suppose individual questions of diverse nature) will be compulsory that the code delivered can be compiled and executed in the teams of the educational laboratories.
Second announcement / Announcement of end of course / extraordinary Announcement.
In this announcement that does not govern the EC. The evaluation will be as follows:
Theoretical part:
An examination written (whose description coincides with the proof 3 of EC). The result of this examination will suppose 50% of the final qualification. It will not allow material of support.
Practical part:
The students that do not deliver the project in the first announcement, will evaluate with an examination of individual programming in the laboratory that will take place in the date fixed by the Board of School for this. The evaluation of this proof will suppose 50% of the final qualification.
The part practises to realise for the students that deliver the project in the first announcement, will depend on the note of the project obtained in the first announcement, as the following:
It notices >= 1,5. It will keep them the note, not having to present to the practical examination of the second announcement. They will be able to, however, improve the punctuation of the project delivering a new version of the one of the first announcement together with the new functions to realise that they published in his moment in the Faitic platform. Likewise, they will have to deliver a document that collect the changes and updates realised to the project on the version that deliver in the first announcement.
Note between 1.5 and 1. They will be able to opt between going to the examination practise or realise the project of the second announcement. No it keeps them the note of the project of the first announcement, but if the one of initiation and the one of UML design.
It notices < 1. They will be able to opt between going directly to the examination practise or realise the project expanded. In any case loses the note of practices of the part of initiation and UML design. That is to say, it evaluated them on 5, independently of if they opt by the project or the practical examination.
The requirements to approve will be:
A minimum of 1/3 on the total in the theoretical part.
A minimum of 1/3 on the total in the project or examination according to the case.
A total note (sum of the 2 proofs) equal or upper to 5.
Universidade de Vigo
|
Reitoría |
Campus Universitario |
C.P. 36.310 Vigo (Pontevedra) |
España |
Tlf: +34 986 812 000
