Educational guide
IDENTIFYING DATA 2024_25
Subject SOFTWARE ENGINEERING Code 00709022
Study programme
0709 - GRADO EN INGENIERÍA INFORMÁTICA
Descriptors Credit. Type Year Period
6 Compulsory Third First
Language
Castellano
Prerequisites
Department ING.MECANICA,INFORMAT.AEROESP.
Coordinador
CUERVO FERNÁNDEZ , EVA MARÍA
E-mail emcuef@unileon.es
jmalip@unileon.es
Lecturers
ALIJA PÉREZ , JOSÉ MANUEL
CUERVO FERNÁNDEZ , EVA MARÍA
Web http://agora.unileon.es
General description Software engineering
Tribunales de Revisión
Tribunal titular
Cargo Departamento Profesor
Presidente ING.MECANICA,INFORMAT.AEROESP. PEREZ GARCIA , HILDE
Secretario ING.MECANICA,INFORMAT.AEROESP. FERNANDEZ DIAZ , RAMON ANGEL
Vocal ING.MECANICA,INFORMAT.AEROESP. SANCHEZ GONZALEZ , LIDIA
Tribunal suplente
Cargo Departamento Profesor
Presidente ING.MECANICA,INFORMAT.AEROESP. RODRIGUEZ DE SOTO , ADOLFO
Secretario ING.MECANICA,INFORMAT.AEROESP. PANIZO ALONSO , LUIS
Vocal ING.MECANICA,INFORMAT.AEROESP. MATELLAN OLIVERA , VICENTE

Competencias
Code  
A18097
A18109
A18110
A18112
A18116
A18126
B5618
B5619
B5623
B5627
B5682
C2 CMECES2 That students know how to apply their knowledge to their work or vocation in a professional manner and possess the skills that are usually demonstrated through the development and defense of arguments and the resolution of problems within their area of study.
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
A18109
 B5618
A18126
 B5623
 C5
A18097
 B5682
A18110
 B5619
 C2
A18097
A18112
A18116
 C3
B5619
B5627
 C4

Contents
Topic Sub-topic
Bloque I: Ingeniería del software Topic 1: INTRODUCTION TO SOFTWARE ENGINEERING

Topic 2: TYPES OF SOFTWARE PROCESSES
Types of Software Processes, Unified Development Processes

Topic 3: REQUIREMENTS ENGINEERING

Topic 4: USE CASES
Use Cases, System Sequence Diagrams, Contracts

Topic 5: OBJECT ORIENTED ANALYSIS
OO analysis, domain diagram

Topic 6: OBJECT ORIENTED DESIGN AND IMPLEMENTATION
OO design, UML diagrams: interaction diagrams, class diagrams, state diagrams...
Design Patterns: GRASP, GOF
Persistence Framework Design

Topic 7: IMPLEMENTATION
Code implementation, Deployment model, UML diagrams of components and deployment.

Topic 8: SOFTWARE ARCHITECTURES

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
Methodologies   ::  
  Description
Personal tuition Teacher meeting with a small group of students conceptually based on learning theories rather than teaching.
Practicals using information and communication technologies (ICTs) in computer rooms Carrying out of a practical exercise following the Software Engineering development methodology presented in the Master Session.
Lecture

Personalized attention
 
Personal tuition
Lecture
Description
Problem solving/exercises in the regular classroom.
Resolution of doubts related to the content of the course and individual evaluation.

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. In order to pass the course, it is essential to obtain a minimum grade of 4 out of 10 in each of the exams. 		70%
Others Compulsory Final Practice: to be submitted on the date and in the manner established by the professor. It will represent 30% of the final grade of the course.
It is essential to obtain a minimum grade of 3.5 out of 10 in this practical 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 Skidmore, S., Introducing Systems Analysis, .Macmillan Computer Sciencie Series, 1997
McConnell, S., IT Project Development and Management, Mc Graw-Hill , 1997
Yourdon, E., Modern Structured Analysis, Prentice Hall, 1999
Sommerville, L., Software Engineering, Addison-Wesley, 2005
Pressman, R.S., Software Engineering: a practical approach., Mc Graw Hill, 2010
Larman, C, UML y patrones, Pearson- Prentice Hall, 2002

Complementary Whitten, J.L. et al., Análisis de Sistemas Diseño y Métodos, Mc Graw-Hill, 2008
Bruegge, B. Et al., Ingeniería de Software Orientado a Objetos, Prentice Hall, 2002
Lawrence, S., Ingeniería del Software: Teoría y Práctica, Prentice Hall, 2002


Recommendations


Subjects that it is recommended to have taken before
COMPUTER PROGRAMMING I / 00709009
COMPUTER PROGRAMMING II / 00709011
DATABASES / 00709012
DATA STRUCTURES / 00709018