ECTS credits ECTS credits: 12
ECTS Hours Rules/Memories Student's work ECTS: 198 Hours of tutorials: 6 Expository Class: 48 Interactive Classroom: 48 Total: 300
Use languages Spanish, Galician
Type: Ordinary Degree Subject RD 1393/2007 - 822/2021
Departments: Electronics and Computing
Areas: Languages and Computer Systems
Center Higher Technical Engineering School
Call: Annual
Teaching: Sin docencia (Extinguida)
Enrolment: No Matriculable
At the end of the course, students must understand the construction of software as an engineering process and have a global vision of this process. With this objective, the student will be presented with the software as an engineering element that must be built in a framework that allows us to predict its qualities. The study of this framework defined as a set of processes, treated with different levels of depth, and its temporal chaining will constitute the basis of the course.
Theory:
1. The product (3 h.)
1.1. Topics and engineering software
1.2. Importance of the introduction of the Engineering software
1.3. Evolution of the industry of the software
1.4. Characteristics and attributes of the software
1.5. Types of software.
1.6. Inherited software
1.7. Main problems associated to the software
2. Process models for the construction of software (5 h.)
2.1. Definitions of engineering software
2.2. Process models
2.2.1. The Rule IEEE 1074
2.2.2. The ISO Rule 12207-1
2.2.3. The Rule ISO/IEC 15504-2
2.3. Software Process Assessment.
2.3.1. Introduction.
2.3.2. Standards.
2.3.3. Capability Madurity Model Integration CMMI.
2.3.4. “IDEAL” Model
3. Compulsory models for the development of software (5 h.)
3.1. Classical models
3.1.1. Cycle of life in cascade
3.1.2. Construction for prototypes
3.1.3. Cycle of incremental life
3.1.4. The model in spiral
3.2. Agile development
3.2.1. Shaped agile
3.2.2. Extreme programming.
4. Engineering requirement (5 h.)
4.1. Introduction
4.2. First questions
4.3. Techniques of apprehension of requirements
4.4. Analysis of requirements.
4.5. Specification of requirements
4.6. Validation of requirements
4.7. Administration of requirements
5. Shaped of Systems (6 h.)
5.1. Introduction
5.2. Techniques of shaped
5.3. Model consistency
5.4. Methodologies
6. Tests and software maintenance (5 h.)
6.1. Introduction and initial definitions
6.2. Philosophy of Software tests
6.3. The process of test
6.4. Techniques of design of test cases
6.5. Structural tests
6.6. Functional tests
6.7. Tests documentation
6.8. Execution of tests
6.9. Strategy in Tests application
6.10. Tests in developments orientated to objects.
Practices:
1.- Project planning
2.- Execution of processes
3.- Choice of life cycle
4.- Risk management
5.- Requirements engineering
6.- Software configuration management
7.- Tests
Basic Bibliography:
1.- Ian Sommerville; “Ingeniería de Software”. Ed. Addison Wesley, Madrid. 2005. ISBN: 84-7829074-5
2.- Roger S Pressman; “Ingeniería del Software. Un enfoque práctico”. Ed. Mc Graw Hill, España. 2005. ISBN: 970-10-5473-3.
Complementary Bibliography:
1.- Mario Piattini, José A. Calvo-Manzano, Joaquín Cervera, Luis Fernández; “Análisis y diseño detallado de aplicaciones Informáticas de Gestión. Una perspectiva de Ingeniería de Software”. Ed. RA-MA, España. 2003. ISBN: 84-7897-587-X.
3.- Antonio Colmenar, Manuel A. Castro, Julio Pérez; “Gestión de proyectos con Microsoft Project 2000”, Ed. RA-MA, España. 2001. ISBN: 84-7897-443-1.
After studying the subject, the student should be able to see a software project as a set of processes. It is claimed that the student acquires a vision of the scope that implies the development of a project, the involved processes and its need for the development of quality software.
The theoretical (expository) classes will be articulated in two one-hour lectures per week with the support of slides. Through the e-Learning tool of the USC (Virtual Campus), the students will be provided with the teaching material of the subject and it will be systematically used as a strategy for the delivery of practices and collaboration among the students who develop group works. The practical (interactive) classes will be developed in weekly sessions of two and a half hours and, depending on the case, individually or in small groups to which exercises will be proposed that will imply the development of the contents given in the theoretical classes or acquired autonomously by the student. The forums and the e-mail of the e-Learning tool will also be used as a communication channel between teachers and students, allowing for tutorials which, therefore, do not necessarily have to be in person. Finally, and whenever possible, conferences or visits to companies will be organized to give the student an idea of the impact that software engineering has on the companies in the environment.
The methodology described corresponds to Scenario 1, adapted normality, in which teaching as well as tutorials will be face-to-face, although in the latter case, as indicated, students will have telematic alternatives. The changes to adapt the methodology to Scenario 2, distance; and Scenario 3, closure of the facilities; are described in the contingency plan included in the observations section.
The competencies specific to the subject as well as all the general competencies except GC4, GC7; the competencies related to IT: RI1, RI2, RI3, RI8 and RI16; and the competencies related to IT1, TI2 and TI7, have specific contents in the subject that are introduced, as indicated, both in the expository and interactive classes. Subsequently, the student will develop these skills by carrying out practical work in which he or she will also work on the transversal skills, particularly in terms of analysis and synthesis, organisation and planning skills, oral and written communication, information management skills, problem solving and decision making, teamwork and motivation for quality.
To pass the subject, students must independently pass the practical part of the course, 60% of the total grade, and the theoretical part, 40% of the total grade.
The practical part of the subject will be evaluated based on the summary of each of the practices carried out and the continuous evaluation of the student's work in class, whose presence will be measured on the basis of a record of signatures in each session. Students who do not present more than 70% of the summary papers will have the status of NOT SUBMITTED in June.
In the evaluation of the work submitted by the students, the degree of achievement of the competences will be assessed, in particular the implementation of the contents contributed by the subject to those competences. In addition, the lack of transversal skills required for the development of the work will be assessed negatively.
The evaluation of the theory will be done by means of a follow-up test or a final exam. When the student does not present more than 70% of the follow-up exercises, he/she must take the final exam or will be considered NOT TO BE PRESENTED in June.
The questions in the theory exam will focus on the specific contents that have been developed in the subject in relation to the student's skills and that may have been acquired by the student in both the expository and interactive parts. The exam may consist of multiple choice questions, short and long questions and case study problem solving. The exam will evaluate the degree of assimilation of the teaching objectives established in the teaching programme for the subject.
The evaluation in July will be made, in its practical part, by means of the delivery of the summary of the practices, being essential to present more than 70% of the works. And, the evaluation in its theoretical part by means of a final exam.
Students who do not attend class during more than 50% of the internship must submit the summary individually, even if the work was done in a group. This is valid for both the June and July opportunities.
The student who misses more than 15% of the classes during the course will have the condition of NO SHOW in June and July.
Repeating students will be examined under the same conditions as students in the first call, except in those cases where they have passed the internship in a call from the two previous academic years. In this case, they will not be obliged to attend the practical classes and will present the report delivered the year in which they passed. The theory note will never be kept and the student will always have to take an exam on the theoretical contents of the subject under the same conditions as the students in the first call.
Extraordinary Call: The evaluation will take place in two complementary phases. In the first one with a weight on the final mark of 60%, the student will have to pass a practical case that will be equivalent to the practices carried out regularly during the course. In the second phase, a theory exam will be taken which will account for 40% of the final mark. In order to pass the subject in this call, as in any of the opportunities of the ordinary call, both parts have to be passed individually.
The evaluation system described corresponds to Scenario 1, adapted normality in which the evaluation will be carried out in person. In this scenario, the attendance recorded as indicated will also be required for the continuous assessment in the practical part of the course. The changes to adapt it to Scenarios 2, distancing; and 3, closure of the facilities, are described in the contingency plan included in the section on observations.
In the case of fraudulent exercises or tests, the provisions of the Regulations on the evaluation of student academic performance and the review of grades shall apply.
It is recommended between 2 and 3 hours per week of personal work of students to prepare the theoretical part of the subject. The practical part will imply the accomplishment of a series of works which load should not suppose more than other 2. weekly additional hours.
The student should take up to date the subject to be able to apply in the practical exercises the knowledge acquired through a theoretical way.
The subject will be taught in Spanish.
CONTINGENCY PLAN
In scenario 1, adapted normality, as described in its sections on teaching methodology and assessment system, the teaching and examination will be face-to-face, although all the documentation of the subject will be available from the beginning through the Moodle course of the subject.
In the case of scenarios 2 and 3 of distance and closure of the facilities respectively, the teaching methodology and assessment system will be modified as follows.
Scenario 2: Distancing.
Teaching Methodology: In this scenario the teaching of the subject will be exclusively non-presential using the Teams tool. The practical part of the course will be done in person unless the dynamics of the practice requires an extensive presentation of contents or the imposed measures of distance cannot be fulfilled. In these cases, the practices can also be carried out in a non-presential way for some part of the group, establishing in these circumstances the necessary turns to guarantee an equitable distribution of presential and remote classes among all the members. Tutorials, unless the student requests otherwise, will be carried out exclusively telematically through any of the means available to the student, e-mail or, videoconference or chat, through Teams.
Evaluation system: The delivery of internship assignments will also be made by telematic means through the Moodle tool. Class attendance for the continuous assessment will continue to be registered by means of signatures in the case of attendance and through the Teams utilities for the telematic case, being applicable the attendance criteria indicated in the assessment system. The theoretical examination of the subject will be carried out remotely using the utilities provided for this purpose by the Moodle tool.
Scenario 3: Facility closure
Teaching methodology: In this scenario, teaching will be exclusively remote. In the lectures, as in the previous scenario, the Teams tool will be used. The practical part will also be done remotely, for which channels will be generated in the Teams tool for the interaction of the practice teams within each group, so that students can communicate, exchange and share documents through their utilities. Through the meetings in these channels, which will take place at times that coincide with the corresponding practice schedules, the teaching staff of the subject will also interact with these teams, advising them and answering any doubts that may arise. The tutorials will be carried out exclusively by telematic means with the same tools indicated in the previous scenario.
Evaluation system: The final delivery of the documentation of the practices will continue to be made through the Moodle tool in order to standardize the deliveries against changes in scenarios. In this case, the theoretical examination of the course will be carried out remotely using the utilities provided for this purpose by the Moodle tool. With regard to the assessment of class attendance, in the case of non-attendance, the activity recorded by the tools used will be assessed and the same criteria that have already been established for the normal operation of the course will be applied to these measures.
The rest of the criteria and methodologies proposed for the subject, which have not been modified in this plan, will be applicable in any of the scenarios.
José Manuel Cotos Yáñez
Coordinador/a- Department
- Electronics and Computing
- Area
- Languages and Computer Systems
- Phone
- 881816461
- manel.cotos [at] usc.es
- Category
- Professor: University Lecturer
Julian Carlos Flores Gonzalez
- Department
- Electronics and Computing
- Area
- Languages and Computer Systems
- Phone
- 881816456
- julian.flores [at] usc.es
- Category
- Professor: University Lecturer
José Ángel Taboada González
- Department
- Electronics and Computing
- Area
- Languages and Computer Systems
- Phone
- 881816457
- joseangel.taboada [at] usc.es
- Category
- Professor: University Lecturer
Joaquín Ángel Triñanes Fernández
- Department
- Electronics and Computing
- Area
- Languages and Computer Systems
- Phone
- 881816001
- joaquin.trinanes [at] usc.es
- Category
- Professor: Temporary PhD professor
| Monday | |||
|---|---|---|---|
| 09:00-10:00 | Grupo /CLE_01 | Spanish | Classroom A4 |
| Tuesday | |||
| 09:00-10:00 | Grupo /CLE_01 | Spanish | Classroom A4 |
| 11:00-13:30 | Grupo /CLIL_03 | Spanish | Computer Room I2 |
| 17:30-20:00 | Grupo /CLIL_02 | Spanish | Computer Room I5 |
| Friday | |||
| 09:00-11:30 | Grupo /CLIL_01 | Spanish | Computer Classroom I3 |
| 07.12.2021 16:00-20:45 | Grupo /CLIL_03 | Classroom A1 |
| 07.12.2021 16:00-20:45 | Grupo /CLE_01 | Classroom A1 |
| 07.12.2021 16:00-20:45 | Grupo /CLIL_02 | Classroom A1 |
| 07.12.2021 16:00-20:45 | Grupo /CLIL_01 | Classroom A1 |
| 07.12.2021 16:00-20:45 | Grupo /CLIL_02 | Classroom A2 |
| 07.12.2021 16:00-20:45 | Grupo /CLIL_01 | Classroom A2 |
| 07.12.2021 16:00-20:45 | Grupo /CLE_01 | Classroom A2 |
| 07.12.2021 16:00-20:45 | Grupo /CLIL_03 | Classroom A2 |