Educational guide | ||||||||||||||||||||||||||||||||||||||||
IDENTIFYING DATA | 2024_25 | |||||||||||||||||||||||||||||||||||||||
Subject | SOFTWARE ENGINEERING II | Code | 00709036 | |||||||||||||||||||||||||||||||||||||
Study programme |
|
|||||||||||||||||||||||||||||||||||||||
Descriptors | Credit. | Type | Year | Period | ||||||||||||||||||||||||||||||||||||
6 | Compulsory | Fourth | Second |
|||||||||||||||||||||||||||||||||||||
Language |
|
|||||||||||||||||||||||||||||||||||||||
Prerequisites | ||||||||||||||||||||||||||||||||||||||||
Department | ING.MECANICA,INFORMAT.AEROESP. |
|||||||||||||||||||||||||||||||||||||||
Coordinador |
|
emcuef@unileon.es raferd@unileon.es |
||||||||||||||||||||||||||||||||||||||
Lecturers |
|
|||||||||||||||||||||||||||||||||||||||
Web | http://agora.unileon.es | |||||||||||||||||||||||||||||||||||||||
General description | This subject provides the student with a more advanced vision of Software Engineering, explaining tasks of the software construction process and other methodologies that help professionals in their task of developing high-quality software (agile methodologies). Provides quality knowledge of both the process and the product. Introduces the student to the rules and regulations of computing. | |||||||||||||||||||||||||||||||||||||||
Tribunales de Revisión |
|
|||||||||||||||||||||||||||||||||||||||
Competencias |
Code | |
A18098 | |
A18105 | |
A18109 | |
A18111 | |
A18112 | |
A18116 | |
A18124 | |
B5615 | |
B5617 | |
B5618 | |
B5619 | |
B5620 | |
B5626 | |
B5627 | |
B5682 | |
C3 | CMECES3 That students have the ability to gather and interpret relevant data (normally within their area of study) to make judgments that include reflection on relevant issues of a social, scientific or ethical nature. |
C4 | CMECES4 That students can transmit information, ideas, problems and solutions to both a specialised and non-specialised audience |
C5 | CMECES5 That students have developed those learning skills necessary to undertake further studies with a high degree of autonomy |
Learning aims |
Competences | |||
Students know and apply software engineering principles, methodologies and life cycles. | A18098 A18105 A18109 |
B5618 B5619 B5620 B5627 B5682 |
C3 |
Students know the rules and regulations of information technology at the national, European and international levels. | A18111 |
B5617 B5682 |
|
Students are capable of designing, developing, selecting and evaluating computer applications and systems, ensuring their reliability, security and quality, in accordance with ethical principles and current legislation and regulations. | A18124 |
B5620 B5626 |
C4 |
Students have developed those learning skills necessary to undertake further studies with a high degree of autonomy. | C5 |
||
Students understand the environment of an organization and its needs in the field of information and communication technologies. | A18112 A18116 |
C4 C5 |
|
Students are capable of conceiving, developing and maintaining computer systems, services and applications using software engineering methods as a tool for quality assurance, according to the knowledge acquired. | B5615 |
Contents |
Topic | Sub-topic |
Block I: Types of development | Topic 1: AGILE METHODOLOGIES Agile Manifesto, SCRUM, XP, KANBAN Topic 2: TESTING AND TDD Definition of testing, types of testing, test-driven development Topic 3: SOFTWARE EVOLUTION Software maintenance. Software reengineering. Refactoring |
Block II:SOFTWARE MANAGEMENT | Topic 1: CONFIGURATION MANAGEMENT Concepts Change Management Release management Release construction Release Management Continuous Integration, Continuous Delivery and Continuous Deployment Topic 2: PROJECT PLANNING Concepts, project plan, cost estimation Topic 3: SOFTWARE PROCESS QUALITY Concepts, CMMI, CMMI appraisal Topic 4: SOFTWARE PRODUCT QUALITY Concepts, metrics |
Block III: IT REGULATIONS AND STANDARDS | Tema 1 .- ÉTICA Y DEONTOLOGÍA INFORMÁTICA Tema 2 .- ASPECTOS LEGALES EN INFORMÁTICA RGPD, propiedad intelectual, peritajes Tema 3.- REGULACIÓN DE LA INFORMÁTICA EN EL ÁMBITO NACIONAL, EUROPEO E INTERNACIONAL |
Planning |
Methodologies :: Tests | |||||||||
Class hours | Hours outside the classroom | Total hours | |||||||
Personal tuition | 3 | 0 | 3 | ||||||
Practicals using information and communication technologies (ICTs) in computer rooms | 20 | 35 | 55 | ||||||
Lecture | 32 | 30 | 62 | ||||||
Extended-answer tests | 5 | 25 | 30 | ||||||
(*)The information in the planning table is for guidance only and does not take into account the heterogeneity of the students. |
Methodologies |
Description | |
Personal tuition | Teacher meeting with a small group of students, relying conceptually on learning theories rather than teaching. |
Practicals using information and communication technologies (ICTs) in computer rooms | Performance of a practice following the methodology of Software Engineering development exposed in the master session. This practice is mandatory in order to pass the course. |
Lecture | Exposition of the contents of the course. |
Personalized attention |
|
|
Assessment |
Description | Qualification | ||
Extended-answer tests | The maximum number of aspects that can be evaluated to obtain the final grade will be four: a. Theoretical knowledge b. Practical knowledge and skills c. Task/task solving d. Class presentations of assignments. Throughout the semester there will be 1.- Test type exams, short questions and/or practical exercises. Theoretical-practical exercises of obligatory delivery. 3. 3.- Theoretical-practical exercises of voluntary delivery. The evaluation of these activities will represent 70% of the final grade of the course. It is necessary to obtain a minimum score of 4 out of 10 in each of the partial exams in order to pass the course. |
70% | |
Others | The development of this final practice must be carried out following the guidelines set by the teacher regarding architecture, frameworks or technology to be used. It is necessary to obtain a minimum score of 3.5 out of 10 in this practice in order to pass the course. |
30% | |
Other comments and second call | |||
SECOND CALL: In this case the student must pass a final written exam(70%) divided in two parts, of the totality of the learning results of the course and present the practical work requested (30%). The conditions to pass are the same as in the first call. That is to say, they must obtain at least a 4 in each of the parts of the written exam. The grade of the partial exams passed in the first call is kept. The minimum grade for the final compulsory practicum is still 3.5 in order to pass the course. Both the papers and the practicals presented by the students may be reviewed with an anti-plagiarism program that can perform checks between the students' papers of the current exam, the previous exams and other external sources. If plagiarism is detected, the exam will be immediately withdrawn, the student will be expelled and the work or practice submitted will be graded as failed. In any case, the provisions of the internal regulations of the ULE included in the document "Guidelines for action in cases of plagiarism, copying or fraud in exams or evaluation tests" (Approved by the Standing Committee of the Governing Council 29/01/2015) will be taken into account. |
Sources of information |
Access to Recommended Bibliography in the Catalog ULE |
Basic |
Robert C. Martin, Clean Code: A handbook of Agile Software Craftsmanship, , Cuadra, D. et al;, Desarrollo de Bases de Datos: Casos prácticos desde el Análisis a la Implementación, Ra-Ma, 2013, McConnell, S., Desarrollo y gestión de proyectos informáticos, McGraw Hill, 1997, Molero, X. et al;, Evaluación y Modelado del Rendimiento de los Sistemas Informáticos, Pretice Hall, 2004, Kent Beck, Extreme Programming Explained: Embrace Change, 2ª Edición, Javier Garzás, Gestión ágil de proyectos Software, Kybele Consulting , Sommerville, L., Ingeniería del Software, Pearson, 2011, Pressman, R. S., Ingeniería del Software: un enfoque práctico, McGRaw hill, 2010, Sanchez, S. et al;, Ingeniería del Sw. un enfoque desde la guía SWEBOK, Garceta, 2011, Weitzenfeld,A., Ingeniería del Sw.Orientada a Objetos con UML,JAVA e INTERNET, Thomson, 2005, Martin Fowler, Refactoring: Improving the design of existing code, , |
Complementary |
Whitten, J.L., Análisis de Sistemas. Diseño y Métodos, McGraw hill, 2008, Lawrence, S., Ingeniería del Software: Teoría y Práctica, Prentice Hall, 2002, Skidmore, S., Introducing Systems Analysis, Macmillan C.S.S., 1997, |
Recommendations |
Subjects that it is recommended to have taken before | |||||||||
|