Person in charge: | (-) |
Others: | (-) |
Credits | Dept. |
---|---|
7.5 (6.0 ECTS) | ESSI |
Person in charge: | (-) |
Others: | (-) |
To understand the need and to learn how to determine, specify and validate the requirements (both functional and non-functional) of a software system.
Estimated time (hours):
T | P | L | Alt | Ext. L | Stu | A. time |
Theory | Problems | Laboratory | Other activities | External Laboratory | Study | Additional time |
|
T | P | L | Alt | Ext. L | Stu | A. time | Total | ||
---|---|---|---|---|---|---|---|---|---|---|
14,0 | 0 | 0 | 0 | 0 | 14,0 | 0 | 28,0 |
|
T | P | L | Alt | Ext. L | Stu | A. time | Total | ||
---|---|---|---|---|---|---|---|---|---|---|
0 | 0 | 0 | 10,0 | 0 | 24,0 | 0 | 34,0 |
|
T | P | L | Alt | Ext. L | Stu | A. time | Total | ||
---|---|---|---|---|---|---|---|---|---|---|
0 | 0 | 0 | 10,0 | 0 | 30,0 | 0 | 40,0 |
|
T | P | L | Alt | Ext. L | Stu | A. time | Total | ||
---|---|---|---|---|---|---|---|---|---|---|
0 | 0 | 0 | 4,0 | 0 | 25,0 | 0 | 29,0 |
|
T | P | L | Alt | Ext. L | Stu | A. time | Total | ||
---|---|---|---|---|---|---|---|---|---|---|
0 | 0 | 0 | 4,0 | 0 | 5,0 | 0 | 9,0 |
Total per kind | T | P | L | Alt | Ext. L | Stu | A. time | Total |
14,0 | 0 | 0 | 28,0 | 0 | 98,0 | 0 | 140,0 | |
Avaluation additional hours | 10,0 | |||||||
Total work hours for student | 150,0 |
The course will be taught using the PBL (Project-Based Learning, or Problem-Based Learning) approach.
There is a conventional class (one hour a week) in which the teacher explains general themes (e.g. the nature of requirement engineering) or -more often- the students themselves formulate and discuss central points of the course or aspects not adequately dealt with in the other two course activities.
One of the two main parts of the course covers the determination of a given software engineering system. The teacher will set out a specific situation (which will vary between courses) in which students have to determine and specify software system requirements, using previously learnt methods and languages. This work will be carried out in groups. The number of students in each group and its precise make-up will be established at the beginning of the course. Each grup nominates a coordinator,a secretary and two responsibles of quality. Each group will meet at least once a week for two hours, at a pre-arranged time. There will be at least two submissions of the group's work during the course.
The other important part of the course involves carrying out short exercises. The teacher will set around ten exercises during the course. Each student must submit his or her own solution to the exercises within the set deadlines (students are given roughly a week to do each exercise). Carrying out the exercises involves the learning of new knowledge. The exercises are corrected soon, and the best solutions are published.
Note: The teaching method employed for the course requires students to acquire new knowledge in an autonomous fashion, using bibliographic sources that are normally in English. Accordingly, students' level of English must be up to the task of using such technical bibliography without special difficulties.
Continuous assessment comprises three parts: Group work (30%), individual exercises (35%), student participation (25%) and the cross competence (10%).
Assessment of group work is applied equally to all the group members. It is based on the work done (documents or, where applicable, presentations). As indicated earlier, there will be at least two submissions of the group"s work during the course. The main part of the work group grade (about 90%) is obtained at the end of the course. The other one (about 10%) is obtained at half the course, once the first results presentation is done.
Each student is assessed on the individual exercises. At least six exercises must be submitted during the course and before the deadline established in each case, and at least three of them must get a grade of five or more. The grade awarded is the average of all the handed out exercises.
Students are also graded on their individual participation. This is based on their contribution to group work, the role in the group (coordinator, secretary, presenter, quality responsible, etc.), the level of assistance to the work meetings and classes, the number of individual exercises carried out correctly, and their general participation in the various activities making up the course. A student is evaluated on participation only if the student attends at least the 80% of the scheduled meetings and classes.
The evaluation of the cross competence is also individual. It is based on a part of the group work that will be specifically evaluated. The evaluation takes into account the quality of the work done (this is the same for all members of the group) and the participation of each student in that part of the group work (individual evaluation).
Students should be aware that software engineering in an integral part of the course. Students also need to have a good grounding in (formal) specifications of object-oriented information systems, using UML and OCL.
In view of the foregoing, Software Engineering I is a prerequisite for this course.