Degree | Type | Year |
---|---|---|
2502441 Computer Engineering | OB | 2 |
You can view this information at the end of this document.
Since the subject is an introduction to the block of software engineering subjects, it will be assumed that there is no prior knowledge about the subject. It is the responsibility of the subject to provide the students with a means to acquire the knowledge described in the contents section of the subject (section 6 of this guide). In spite of this it is advisable to have passed the subjects of Foundations of Computing and of Methodology of the Programming of first course, and the subject of Databases of second course.
This subject introduces the block of subjects on the software engineering process. The general objective is to give a global and orderly view of the software development process that is not simply that of programming (which is, only, a phase within the whole process of software engineering). The fundamental activities that constitute the development process will be introduced (requirements analysis, design, implementation, testing and maintenance), most of which are treated in more depth in subsequent subjects.
It is, therefore, that the student acquires an overview of what is a software development process, how software is modeled, what tools are used, how quality is managed and how a project is managed. More specifically, the objectives are:
BLOCK 1. THE SOFTWARE AND SOFTWARE ENGINEERING
Topic 1. Principles of software engineering.
BLOCK 2. SOFTWARE MODELING
Topic 2. Software Requirements Analysis.
Topic 3. Design of the Software.
Topic 4. UML (Unified Modeling Language)
BLOCK 3. ADMINISTRATION OF THE QUALITY OF THE SOFTWARE
Topic 5. Software quality.
BLOCK 4. ADMINISTRATION AND DEVELOPMENT OF SOFTWARE PROJECTS
Topic 6. SCRUM.
Title | Hours | ECTS | Learning Outcomes |
---|---|---|---|
Type: Directed | |||
Preparation and study | 30 | 1.2 | 11, 8, 10, 7, 4, 12 |
Seminars / Problems | 15 | 0.6 | 8, 6, 7, 4 |
Theory lectures | 30 | 1.2 | 11, 8, 10, 7, 12 |
Type: Supervised | |||
Follow up meetings for the practical work | 15 | 0.6 | 1, 6, 5, 13 |
Tutoring | 15 | 0.6 | 11, 8, 10, 7, 12 |
Type: Autonomous | |||
Practical work | 38 | 1.52 | 1, 9, 8, 6, 7, 5, 13 |
The course of Software Engineering has a strong applied component. For this reason, after introducing the fundamental theoretical concepts, the subject is developed according to an ABP (Problem Based Learning) methodology. In this way, the student will acquire the knowledge from a practical case (problem guide) of real dimension. The guide problem will guide the learning process throughout the course, so that the practical work or the seminars will be structured around this case. The student must acquire the analyst / architect profile of the software to make the necessary decisions to conclude in the construction of a proposed design of the proposed system. The teacher will take the role of tutor and, in certain situations, of client, fomenting simulations of developer-client dialogue.
The subject consists of 4 hours per week. There is no distinction between theory hours, problems and laboratory practices. During class hours, theory classes, problems or practices will be alternated according to the planning that will be indicated on the day of the planning of the subject. In general, the explanation of the fundamental theoretical contents will be concentrated during the first sessions of the course (approximately the first 6 weeks). Once the theoretical contents are distributed, all sessions will be devoted to work based on problems, identifying some compulsory attendance sessions where the practice will be carried out on teams of 5 people or they will be made problems at the end of the session.
THEORY
It consists of master classes with multimedia material available at the Virtual Campus of the UAB. The main objective of these classes is tointroduce the basic notions about the processes, methods and tools related to the vision of the software life cycle from an engineering point of view. The principles and paradigms of software engineering, the different activities and the tasks to be carried out in each activity will be exposed. The theory classes must allow the student to take a real vision of rigor, planning and systematic that requires the professional development of the software. It will not be deepened in the subjects since in subjects of later courses these already are developed, but the necessary concepts will be explained so that the student understands the process of development of complete software. The theory sessions will assume that the students follow the materials distributed through the virtual campus, so that they will be oriented to explain the key concepts, and to foment the critical debate on the contents. To make the classes more dynamic, pre-learning materials are usually distributed to the students for self-learning (videos, web links, presentations, etc.) and they are asked to work before class, so that the class is addressed to discuss. knowledge, resolving doubts, focusing on the most essential and working on practical examples.
SEMINARS/PROBLEMS
The seminars are classes with participatory work of the students. According to the objective of the seminars, the group's students will be divided into smaller subgroups. They have a dual function, linking on one side with the masterclasses and on the other with the practical sessions on the problem to be solved in teams. On the one hand, the seminars will complement the technological contents exposed to the master classes, completing their understanding. On the other hand, they will be the framework for discussing, laying the foundations and developing the guide problem. The student will be given the necessary knowledge to carry out the practical work or will be indicated where to obtain them. The seminars essentially promote the capacity for analysis and synthesis, as well as the critical reasoning and decision making of the student in the resolution of the guide problem. Since itis a very practical subject and where the theoretical content is of low complexity, practical work is often reinforced with solving problems or the work of participatory activities. The contents of the seminars will be coordinated with the stages to be resolved in the work of the practice. Since theory sessions, problems and practices will be alternated throughout the course, for a better organization, the students will have at the beginning of the course through the virtual campus of the programming of all the sessions.
FOLLOW UP OF PRACTICAL WORK
There will be no face-to-face sessions of the laboratory. Students will solve the guide problem autonomously in small groups, and the monitoring will be done during class hours during regular hours. The practice bands (6 sessions of 2 hours during the course) will consist of two parts. First, each practice team will present to the rest of the class the progress of its work (the one in charge of presenting will be the person that does of scrum master in that iteration). In the second part of the session, the practice tutor will have an individual interview with each team to follow up and evaluate. A development based on SCRUM is followed, where each increment, called sprint, corresponds to a session. Assistance to the follow-up interviews will be COMPULSORY for all students. The non-presence will adversely affect the evaluation of the practical work, entailing not exceeding the evaluation if the number of non-presences exceeds 15% of the sessions. In case of justified absence, the teaching staff will consider mechanisms of compensation. The size of the practice teams will be determined at the beginning ofthe course. As an indication they will be teams of 5 people. Since attendance to the follow-up sessions is mandatory, and it will be done during the attendance hours, it is important that all the members of a team of internships are enrolled and attend the same group.
PRACTICAL WORK
Students will be given a guiding problem at the beginning of the course. This problem will have two functions. First, use it as an example in theory classes and seminars, solving appropriate parts for the contents of each moment. Secondly, it can be understood as the statement of a practice that is resolved by stages throughout the course. The students will be organized in work teams of 5 people (according to number of students enrolled). The resolution of the work will be carried out autonomously, with the weekly follow-up described above.
ACHIEVEMENT OF COMPETENCES
ONLINE LECTURES
Although it is hoped that all teaching can be carried out in person, the class sessions may have to be adapted to online mode through video conferencing platforms. Any changes that affect the format and schedules will be reported through the virtual campus and at the beginning of the course.
Annotation: Within the schedule set by the centre or degree programme, 15 minutes of one class will be reserved for students to evaluate their lecturers and their courses or modules through questionnaires.
Title | Weighting | Hours | ECTS | Learning Outcomes |
---|---|---|---|---|
Individual evaluation (theory exam) | 50 | 3 | 0.12 | 1, 11, 8, 10, 6, 7, 2, 12, 5, 13 |
Joint evaluation (practical work) | 50 | 4 | 0.16 | 9, 8, 10, 6, 7, 4, 3 |
The evaluation will be carried out based on the practical work developed by the student and included in his portfolio (final resolution of the guide problem, material generated in the seminar activities), the degree of involvement in seminars and knowledge Technological achievements from the subject to study. The following evaluation instruments will be contemplated:
So, AI = 50% Note_Partial1 + 50% Note_Partial2.
It should be noted that while the AI and AC1 instruments value the student's performance and the level of achievement of the knowledge, the AC2 instrument values the student's effort.
INDICATORS AND VALUATION:
The final grade will be obtained according to the following scale:
QF = 50% AI + 50% AC |
To pass the subject it is necessary to have achieved a minimum score of 5 in the two grades (AI and AC), as well as in the partial tests to release material that is established throughout the course. At the discretion of the teacher, however, it may be possible to establish compensation between the notes of the partial deliveries of the activities (corresponding to AC ).
The subject will be evaluated as a Not evaluated only in the case that the student has not been submitted to any of the assessment tests contemplated nor has he delivered all or part of the work.
In case of do not passing the subject because any of the assessment activities do not reach the minimum grade required, the numerical note of the file will be the lowest value between 4.5 and the weighted average of the notes. With the exceptions that the "non-evaluable" qualification will be awarded to students who do not participate in any of the assessment activities, and that the numerical note of the file will be the lowest value between 3.0 and the average Weighted notes in case the student has committed irregularities in an evaluation act (and therefore not approved for compensation).
They will be awarded with Honor mark within the maximum levels admitted by the UAB regulations (depending on the number of students enrolled) at higher grades equal to or greaterthan 9.
For each assessment activity, a place, date and time of revision will be indicated in which the student will be able to review the activity with the teacher. In this context, claims can be made about the activity note, which will be evaluated by the teachers responsible for the subject. If the student does not submit to this review, this activity will not be reviewed later.
See section "PLAGIARISM" in cases of irregularities due to plagiarism in the evaluation activities.
VOLUNTARY EVALUATION ACTIVITIES:
During the course, students will be offered optional delivery activities that will serve to complement the notes of the mandatory activities.
REVISIONS:
EVALUATION DATES:
The dates of continuous assessment and work delivery will be published in Virtual campus and may be subject to changes of programming for reasons of adaptation to possible incidents. Always the virtual campus will be informed about these changes as it is understood to be the usual mechanism for exchanging information between teacher and students.
REPEATING STUDENTS:
Partial notes (theory or practices) are not saved from one course to the next. However, according to the professor's criteria and in accordance with previous course evaluations, compensation may be established. This information will be announced on the day of the presentation of the subject, and on the virtual campus.
PLAGIARISM:
Notwithstanding other disciplinary measures that are considered opportune, and in accordance withthe current academic regulations, the irregularities committed by a student who can lead to a variation of the qualification will be qualified with zero (0). Les Assessment activities qualified in this way and by this procedurewill not be recoverable. If it is necessary to pass any of these assessment activities to pass the subject, this subject will be suspended directly, without opportunityof recover it in the same course. These irregularities include, among others:
- the total or partial copy of a practice, report, or any other evaluation activity;
- let copy;
- present a group work not done entirely by the members of the group;
- Present as own materials prepared by a third party, though are translations or adaptations, and generally works with non-original and exclusive elements of the student;
- Have communication devices (such as mobile phones, smartwatches , etc.) accessible during the theoretical evaluation tests or the individual practices (exams).
In summary: copying or plagiarizing in any of the assessment activities is equivalent to a FAIL in the full subject with a score of less than 3.0.
UNIQUE ASSESSMENT:
The single evaluation of the subject will consist of the following evaluation activities:
- Activity 1: Final theory exam (50% of the grade)
- Activity 2: Delivery of a practical project (50% of the grade)
The same recovery system will be applied as for continuous evaluation. The review of the final grade follows the same procedure as for continuous evaluation. Although the contents of the final theory exam coincide with those of students who follow continuous assessment, the format could be different. Students who opt for continuous evaluation must contact the subject coordinator at the beginning of the semester to talk in more detail about how the evaluation of the theory and the practical project will be carried out.
FINAL DISPOSAL:
For any doubt or discrepancy, the most up-to-date information that will be communicatedon the day of the presentation of the subject will be prevailed and will be published on the virtual campus.
La comunicació amb els alumnes es farà mitjançant el Campus Virtual de la UAB
Name | Group | Language | Semester | Turn |
---|---|---|---|---|
(PAUL) Classroom practices | 411 | Catalan/Spanish | second semester | morning-mixed |
(PAUL) Classroom practices | 412 | Catalan/Spanish | second semester | morning-mixed |
(PAUL) Classroom practices | 431 | Catalan/Spanish | second semester | morning-mixed |
(PAUL) Classroom practices | 432 | Catalan/Spanish | second semester | morning-mixed |
(PAUL) Classroom practices | 451 | Catalan/Spanish | second semester | afternoon |
(PAUL) Classroom practices | 511 | Catalan/Spanish | second semester | morning-mixed |