Educational guide
IDENTIFYING DATA 2024_25
Subject SOFTWARE ENGINEERING Code 00717020
Study programme
0717 - GRADO INGENIERÍA DATOS INTELIGENCIA ARTIFICIAL
Descriptors Credit. Type Year Period
6 Compulsory Second Second
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 It offers the student an overview of the scope of software engineering: its origin, different types of software development processes, the phases of the software development process. It also works in depth the UML language for the realization of the necessary diagrams in each phase.
Tribunales de Revisión
Tribunal titular
Cargo Departamento Profesor
Presidente ING.MECANICA,INFORMAT.AEROESP. CASTEJON LIMAS , MANUEL
Secretario ING.MECANICA,INFORMAT.AEROESP. PANIZO ALONSO , LUIS
Vocal ING.MECANICA,INFORMAT.AEROESP. RODRIGUEZ LERA , FRANCISCO JAVIER
Tribunal suplente
Cargo Departamento Profesor
Presidente ING.MECANICA,INFORMAT.AEROESP. BARREIRO GARCIA , JOAQUIN
Secretario ING.MECANICA,INFORMAT.AEROESP. RODRIGUEZ DE SOTO , ADOLFO
Vocal MATEMATICAS GARCIA SIERRA , JUAN FELIPE

Competencias
Code  
A18969
A18970
B5800
B5805
B5810
B5812
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.
C4 CMECES4 That students can transmit information, ideas, problems and solutions to both a specialised and non-specialised audience

Learning aims
Competences
Student know and applie software engineering principles, methodologies and life cycles. A18969
A18970
B5800
C2
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. A18969
A18970
B5800
B5805
C2
C4
Students are able to design a software product by expressing it in a modeling language. A18969
A18970
Students work well in a team, assuming different roles within the group. B5810
B5812
C4

Contents
Topic Sub-topic
BLOCK I: Software Engineering
Topic 1: INTRODUCTION TO SOFTWARE ENGINEERING
Types of software processes, models and life cycles.
Agile methodologies

Topic 2: REQUIREMENTS ENGINEERING
Requirements engineering and analysis.
Use cases and user stories.

Topic 3: DESIGN AND IMPLEMENTATION.
Object Oriented Design
Design Patterns: GRASP, GOF
SOLID principles
Modeling language and diagrams: interaction, class, state diagrams...

Topic 4: TESTING
Types of testing. TDD

TOPIC 5: CONFIGURATION MANAGEMENT
Change management, version management, system construction and delivery management.

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 22 35 57
 
Lecture 30 30 60
 
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 a software product development methodology presented in the Master Session.
Lecture Presentation of the contents of the course

Personalized attention
 
Lecture
Personal tuition
Description

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 essential to obtain a minimum grade of 4 out of 10 in each of the exams in order to pass the course.


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%
This grade will be added to the final grade of the course when at least a 4 has been obtained in each of the developmental tests.

 
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 McConnell, S, IT Project Development and Management, Mc Graw Hill, 1997
Sommerville, L., Software Engineering, Addison-Wesley, 2005
Pressman, R.S., Software engineering: a practical approach, Mc Graw Hill, 2010
Larman, C., UML and Patterns, Pearson, Prentice Hall, 2002

Complementary


Recommendations


Subjects that it is recommended to have taken before
PROGRAMACIÓN / 00717005
ESTRUCTURAS DE DATOS / 00717009
DATABASES / 00717015