MASTER UNIVERSITARIO EN INGENIER IA DEL SOFTWARE - …pegaso.ls.fi.upm.es/emse/documentos/curso1617/... · 2016. 7. 5. · Agile Software Development: Agile Practices and Agile Usability

MASTER UNIVERSITARIO EN INGENIERIADEL SOFTWARE - EUROPEAN MASTER IN

SOFTWARE ENGINEERING

Educational Planning Course 2016-2017First Semester

Computer Science and Engineering SchoolUniversidad Politecnica de Madrid

CONTENTS i

Contents

1 Pre-enrollment Dates 1

2 Calendar 2

3 Schedule 3

4 Exam Calendar 4

5 Subject Coordinators 7

6 Subject Boards 8

7 Learning Guides 9

7.1 Software Development Module . . . . . . . . . . . . . . . . . 9

7.1.1 Requirements Engineering . . . . . . . . . . . . . . . . 9

7.2 Project Management and Organizational Processes Module . 20

7.2.1 Models and Methods for Process Improvement andAssessment . . . . . . . . . . . . . . . . . . . . . . . . 20

7.2.2 Software Project Management . . . . . . . . . . . . . 33

7.3 Support Processes Module . . . . . . . . . . . . . . . . . . . . 43

7.3.1 Software Metrics . . . . . . . . . . . . . . . . . . . . . 43

7.3.2 Verification and Validation . . . . . . . . . . . . . . . 55

7.4 Advanced Software Engineering Aspects Module . . . . . . . 65

7.4.1 Agile Software Development: Agile Practices and Ag-ile Usability . . . . . . . . . . . . . . . . . . . . . . . . 65

7.4.2 Challenges for Accessible Computing for People withFunctional Diversity . . . . . . . . . . . . . . . . . . . 75

7.4.3 Critical Software . . . . . . . . . . . . . . . . . . . . . 87

7.4.4 Data Engineering . . . . . . . . . . . . . . . . . . . . . 98

7.4.5 Distributed and Outsourced Software Engineering . . 109

7.4.6 Management, Relationships and Communication inWorking Groups . . . . . . . . . . . . . . . . . . . . . 120

ii CONTENTS

7.4.7 Rigorous Software Development . . . . . . . . . . . . . 120

7.4.8 Software Engineering Economics . . . . . . . . . . . . 131

1

1 Pre-enrollment Dates

• Ordinary period: from 1 February to 30 April 2016

• Extraordinary period: from 18 May to 30 June 2016

First semester starts on 12 September 2016Second semester starts on 6 February 2017

M T W T F S S M T W T F S S M T W T F S S M T W T F S S1 2 3 4 1 2 8 1 2 3 4 5 6 12 1 2 3 4

5 6 7 8 9 10 11 4 3 4 5 6 7 8 9 9 7 8 9 10 11 12 13 13 5 6 7 8 9 10 11

1 12 13 14 15 16 17 18 5 10 11 12 13 14 15 16 10 14 15 16 17 18 19 20 14 12 13 14 15 16 17 18

2 19 20 21 22 23 24 25 6 17 18 19 20 21 22 23 11 21 22 23 24 25 26 27 15 19 20 21 22 23 24 25

3 26 27 28 29 30 7 24 25 26 27 28 29 30 12 28 29 30 26 27 28 29 30 31

8 31

M T W T F S S M T W T F S S M T W T F S S M T W T F S S1 1 2 3 4 5 4 1 2 3 4 5 7 1 2

2 3 4 5 6 7 8 1 6 7 8 9 10 11 12 5 6 7 8 9 10 11 12 8 3 4 5 6 7 8 9

16 9 10 11 12 13 14 15 2 13 14 15 16 17 18 19 13 14 15 16 17 18 19 10 11 12 13 14 15 16

16 17 18 19 20 21 22 3 20 21 22 23 24 25 26 6 20 21 22 23 24 25 26 9 17 18 19 20 21 22 23

23 24 25 26 27 28 29 4 27 28 7 27 28 29 30 31 10 24 25 26 27 28 29 30

30 31

M T W T F S S M T W T F S S M T W T F S S11 1 2 3 4 5 6 7 15 1 2 3 4 1 2

12 8 9 10 11 12 13 14 16 5 6 7 8 9 10 11 3 4 5 6 7 8 9

13 15 16 17 18 19 20 21 12 13 14 15 16 17 18 10 11 12 13 14 15 16

14 22 23 24 25 26 27 28 19 20 21 22 23 24 25 17 18 19 20 21 22 23

15 29 30 31 26 27 28 29 30 24 25 26 27 28 29 30

Key: Enrollment:

School day 1st period: 18-31 July and 5-19 September 2016Evaluation process 2nd period: 30 January - 10 February 2017HolidayVacationExtraordinary examsComplementart activities; transversal competences development

EUROPEAN MASTER IN SOFTWARE ENGINEERING

COURSE 2016-17

September-15 October-16 November-16 December-16

Universidad Politécnica de MadridE.T.S. DE INGENIEROS INFORMÁTICOS

March-17 April-17

May-17 June-17 July-17

January-17 February-17

2 2 CALENDAR

2 Calendar

Monday Tuesday Wednesday Thursday Friday15:00

16:00

17:00

18:00

19:00

20:00

EMSE2016-2017·1stSemester (SEP)

21:00

RigorousSoftwareDevelopmentRoom6202

JulioMariño

RequirementsEngineeringRoom6202

ÓscarDieste

DataEngineeringRoom6202

ErnestinaMenasalvasJavierSegovia

ModelsandMethodsforProcessImprovementandAssessmentRoom6202

JoséA.Calvo-Manzano

CriticalSoftwareRoom6202

AndrésSilva

AssessmentActivities

MandatorySubjects(16weeks)

ElectiveSubjects(16weeks)

ElectiveSubjects(week1to8)

SpecialActivities(16weeks)

AgileSoftwareDevelopment:AgilePracticesandAgileUsabilityRoom6202

AnaMaríaMoreno

DistributedandOutsourcedSoftwareEngineeringRoom6202Óscar Dieste,NataliaJuristo

DistributedandOutsourcedSoftwareEngineeringRoom6202Óscar Dieste,NataliaJuristo

Sw Eng.Econo-micsRoomArtá

JuneAmillo

Sw EngineeringEconomicsRoomArtá

JuneAmillo

VerificationandValidationRoom6202

SiraVegas

SoftwareProjectManagementRoom6202

AnaMaríaMoreno

Management,RelationshipsandCommunicationinWorkingGroupsRoom 6202

SusanaMuñoz

ChallengesforAccessibleComputingforPeoplewithFunctionalDiversityRoom6205

LoïcMartínez,

JoséL.Fuertes

VerificationandValidationRoom6202

SiraVegas

RequirementsEngineeringRoom6202

ÓscarDieste

SoftwareMetricsRoom6202

Tomás SanFeliu

3

3S

ched

ule

1stand3rdSemester(FallTerm)JANUARY2017

MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY SUNDAY

16 17 18 19 20 21 22

RequirementsEngineering 15:00

ChallengesforAccessibleComputingforPeoplewithFunctionalDiversity

15:00 CriticalSoft-ware 15:00 Verification

andValidation 17:00

AgileSoftwareDevelopment:AgilePracticesandAgileUsability

15:00

Management,RelationshipsandCommu-nicationinWorkingGroups

18:00RigorousSoftwareDevelopment 19:00

23 24 25 26 27 28 29ModelsandMethodsforProcessIm-provementandAssess-ment

15:00SoftwareProjectMan-agement 15:00 DataEngi-

neering 15:00SoftwareEngineeringEconomics 15:00 MasterThesis 15:00

SoftwareMetrics 18:00

44

EXAM

CALENDAR

4E

xam

Cale

nd

ar

2ndSemester(SpringTerm)

JUNE2017 MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY SUNDAY

6 7 8 9 10 11 12

ExperimentalSoftwareEngineering 15:00 Interaction

Design 15:00SoftwareQualityMan-agement 15:00

FundamentalsofBusinessAdministra-tion

15:00

13 14 15 16 17 20 21 AgentBasedSoftwareDevelopment 15:00 Software

Architecture 15:00 SoftwareDesign 15:00 MasterThesis 15:00

5

Extraordinaryperiod(JUL)JUNE-JULY2017

MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY SUNDAY

26 27 28 29 30 1 2

SoftwareQualityMan-agement 15:00

SoftwareEngineeringEconomics 15:00 Verification

andValidation 15:00

DataEngi-neering 18:00 Software

Design 18:00 SoftwareArchitecture 18:00

3 4 5 6 7 8 9AgileSoftwareDevelopment:AgilePractic-esandAgileUsability

15:00SoftwareProjectMan-agement 15:00 Software

Metrics 15:00

Management,RelationshipsandCommu-nicationinWorkingGroups

15:00


15:00

ExperimentalSoftwareEngineering 18:00

AgentBasedSoftwareDevelopment 18:00 CriticalSoft-

ware 18:00 RequirementsEngineering 18:00

RigorousSoftwareDevelopment 18:00

10 11 12 13 14 15 16 ModelsandMethodsforProcessIm-provementandAssess-ment

15:00 InteractionDesign 15:00

FundamentalsofBusinessAdministra-tion

15:00 MasterThesis 15:00

VerificationandValidation 18:00

64

EXAM

CALENDAR

Máster Universitario en Ingeniería de Software - European Master in Software Engineering Subjects for Course 2016/2017

MODULE SOFTWARE DEVELOPMENT Course unit name Coordinator Type ECTS Term Requirements Engineering Óscar Dieste C 6 1, 3 Software Architecture Jaime Ramírez C 4 2 Software Design Nelson Medinilla C 4 2 MODULE PROJECT MANAGEMENT AND ORGANIZATIONAL PROCESSES Course unit name Coordinator Type ECTS Term Models and Methods for Process Improvement and Assessment

José A. Calvo-Manzano C 4 1, 3

Software Project Management Ana M. Moreno C 4 1, 3 MODULE SUPPORT PROCESSES Course unit name Coordinator Type ECTS Term Software Metrics Tomás San Feliu C 4 1, 3 Software Quality Management Angélica de Antonio C 4 2 Verification and Validation Sira Vegas C 6 1, 3 MODULE ADVANCED SOFTWARE ENGINEERING ASPECTS Course unit name Coordinator Type ECTS Term Agent-Based Software Development Ricardo Imbert E 6 2 Agile Software Development: Agile Practices and Agile Usability

Ana M. Moreno E 4 1, 3

Challenges for Accessible Computing for People with Functional Diversity

Loïc Martínez E 4 1, 3

Critical Software Andrés Silva E 3 1, 3 Data Engineering Ernestina Menasalvas E 4 1, 3 Distributed and Outsourced Software Engineering

Óscar Dieste E 4 1, 3

Experimental Software Engineering Sira Vegas E 6 2 Fundamentals of Business Administration Marta Olea E 4 2 Interaction Design Xavier Ferré E 6 2 Management, Relationships and Communication in Working Groups

Susana Muñoz E 4 1, 3

Rigurous Software Development Julio Mariño E 4 1, 3 Software Engineering Economics June Amillo E 6 1, 3 PRACTICUM Course unit name Coordinator Type ECTS Term Software Project Xavier Ferré C 14 3 FINAL MASTER THESIS Course unit name Coordinator Type ECTS Term Master Thesis Ricardo Imbert C 30 4

Type: C - Compulsory; E - Elective

7

5 Subject Coordinators

SUBJECT PRESIDENT VOCAL SECRETARY Agent-BasedSoftwareDevelopment RicardoImbert XavierFerré JaimeRamírezAgileSoftwareDevelopment:AgilePracticesandAgileUsability

AnaMaríaMoreno


TomásSanFeliu


AuroraPérez LoïcMartínez JoséLuisFuertes

CriticalSoftware AndrésSilva XavierFerré RicardoImbertDataEngineering JavierSegovia Ernestina

MenasalvasLuisMengual

DistributedandOutsourcedSoftwareEngineering

NataliaJuristo SiraVegas ÓscarDieste

ExperimentalSoftwareEngineering NataliaJuristo SiraVegas ÓscarDiesteFundamentalsofBusinessAdministration MartaOlea RicardoImbert JaimeRamírezInteractionDesign XavierFerré RicardoImbert JaimeRamírezManagement,RelationshipsandCommunicationinWorkingGroups

SusanaMuñoz JulioMariño Lars-ÅkeFredlund

MasterThesis NataliaJuristo RicardoImbert XavierFerréModelsandMethodsforProcessImprovementandAssessment


TomásSanFeliu RicardoImbert

RequirementsEngineering NataliaJuristo SiraVegas ÓscarDiesteRigurousSoftwareDevelopment JulioMariño SusanaMuñoz Lars-Åke

FredlundSeminars JaimeRamírez RicardoImbert ÓscarDiesteSoftwareArchitecture Angélicade

AntonioNelsonMedinilla JaimeRamírez

SoftwareDesign NelsonMedinilla XavierFerré RicardoImbertSoftwareEngineeringEconomics JuneAmillo RicardoImbert XavierFerréSoftwareMetrics TomásSanFeliu JoséA.Calvo-

ManzanoRicardoImbert

SoftwareProject(Practicum) NataliaJuristo RicardoImbert XavierFerréSoftwareProjectManagement AnaMaría

MorenoJoséA.Calvo-Manzano

TomásSanFeliu

SoftwareQualityManagement AngélicadeAntonio

XavierFerré RicardoImbert

VerificationandValidation NataliaJuristo SiraVegas ÓscarDieste

8 6 SUBJECT BOARDS

6 Subject Boards

9

7 Learning Guides

7.1 Software Development Module

7.1.1 Requirements Engineering

UNIVERSIDAD POLITÉCNICA DE MADRID

Escuela Tecnica Superior de Ingenieros Informaticos

PROCESO DE COORDINACIÓN DE LAS ENSEÑANZAS

ANX-PR/CL/001-01: GUÍA DE APRENDIZAJE Código PR/CL/001

GA_10AM_103000482_1S_2016-17

ANX-PR/CL/001-01GUÍA DE APRENDIZAJE

ASIGNATURARequirements engineering

CURSO ACADÉMICO - SEMESTRE2016-17 - Primer semestre

10 7 LEARNING GUIDES





GA_10AM_103000482_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Requirements engineering

Titulación 10AM - Master Universitario en Ingenieria del Software

Centro responsable de la titulación Escuela Tecnica Superior de Ingenieros Informaticos

Semestre/s de impartición Primer semestre

Carácter Obligatoria

Código UPM 103000482

Nombre en inglés Requirements enginnering

Datos Generales

Créditos 6 Curso 1

Curso Académico 2016-17 Período de impartición Septiembre-Enero

Idioma de impartición Inglés Otros idiomas de impartición

Requisitos Previos ObligatoriosAsignaturas Previas Requeridas

El plan de estudios Master Universitario en Ingenieria del Software no tiene definidas asignaturas previas superadas para estaasignatura.

Otros Requisitos

El plan de estudios Master Universitario en Ingenieria del Software no tiene definidos otros requisitos para esta asignatura.

Conocimientos PreviosAsignaturas Previas Recomendadas

El coordinador de la asignatura no ha definido asignaturas previas recomendadas.

Otros Conocimientos Previos Recomendados

El coordinador de la asignatura no ha definido otros conocimientos previos recomendados.

7.1 Software Development Module 11





GA_10AM_103000482_1S_2016-17 2

Competencias

CE5 - Educir, analizar y especificar las necesidades de los clientes, usuarios y otras partes interesadas, teniendo en cuenta losposibles condicionantes que pudieran afectar al sistema a desarrollar

Resultados de Aprendizaje

RA74 - The students will be able to analize, specify and validate software requirements

RA73 - The students will be able to elicit and conceptualize customer and user's needs

RA75 - The students will be able to manage and negotiate requirements with project stakeholders






GA_10AM_103000482_1S_2016-17 3

ProfesoradoProfesorado

Nombre Despacho e-mail Tutorías

Dieste Tubio, Oscar (Coordinador/a) D6203 [email protected] M - 17:00 - 19:00

V - 13:00 - 17:00

Nota.- Las horas de tutoría son orientativas y pueden sufrir modificaciones. Se deberá confirmar los horarios de tutorías con elprofesorado.






GA_10AM_103000482_1S_2016-17 4

Descripción de la Asignatura

RE aims to teach or expand students' abilities regarding software requirements: elicitation, analysis, documentation, validationand management. The course will balance lectures and practical activities.

Temario

1. Requirements elicitation

1.1. Regular elicitation techniques

1.2. Contrived elicitation techniques

1.3. Prototyping

2. Requirements analysis

2.1. Weak techniques

2.2. Conceptual modelling

2.3. Natural language processing tools

3. Requirements documentation

3.1. Requirements properties

3.2. Jackson's RSK framework

3.3. Standards

3.4. Contracts

3.5. Requirements tools

4. Requirements validation

4.1. Reviews

4.2. Model checking

5. Requirements management

5.1. Change management

5.2. Prioritization

5.3. Negotiation






GA_10AM_103000482_1S_2016-17 5

Cronograma

Horas totales: 158 horas Horas presenciales: 48 horas (30.8%)

Peso total de actividades de evaluación continua:100%

Peso total de actividades de evaluación sólo prueba final:100%

Semana Actividad Prensencial en Aula Actividad Prensencial enLaboratorio

Otra Actividad Presencial Actividades Evaluación

Semana 1 Course goals and methodologyDuración: 01:00

LM: Actividad del tipo LecciónMagistral

Current state of requirementsengineeringDuración: 02:00


Semana 2 Requirements specificationDuración: 03:00

AC: Actividad del tipo AccionesCooperativas



Creation of a requirementsspecification documentDuración: 06:00

TI: Técnica del tipo Trabajo Individual

Evaluación continua

Actividad no presencial

Semana 4 Requirements validationDuración: 03:00


Validation of a specificationdocumentDuración: 04:00

PG: Técnica del tipo Presentación enGrupo



Semana 5 Requirements elicitationDuración: 03:00






Semana 6 Requirements elicitationDuración: 03:00


Paper writingDuración: 06:00




Semana 7 PrototypingDuración: 03:00











GA_10AM_103000482_1S_2016-17 6

Semana 8 AnalysisDuración: 03:00






Semana 9 Requirements managementDuración: 03:00


Requirements managementexerciseDuración: 05:00

OT: Otras técnicas evaluativas



Semana 10 Requirements managementDuración: 03:00


Requirements managementexerciseDuración: 05:00




Semana 11 Model checkingDuración: 03:00


Model checking exerciseDuración: 04:00




Semana 12 Model checkingDuración: 03:00


Model checking exerciseDuración: 04:00




Semana 13 Presentations & follow-upDuración: 03:00

OT: Otras actividades formativas

Requirements projectDuración: 15:00



























GA_10AM_103000482_1S_2016-17 7

Semana 17 ExamDuración: 02:00

EX: Técnica del tipo Examen Escrito

Evaluación sólo prueba final


Participation in classroomactivitiesDuración: 00:00




Nota.- El cronograma sigue una planificación teórica de la asignatura que puede sufrir modificaciones durante el curso.Nota 2.- Para poder calcular correctamente la dedicación de un alumno, la duración de las actividades que se repiten en el tiempo(por ejemplo, subgrupos de prácticas") únicamente se indican la primera vez que se definen.






GA_10AM_103000482_1S_2016-17 8

Actividades de Evaluación

Semana Descripción Duración Tipo evaluación Técnicaevaluativa

Presencial Peso Notamínima

Competenciasevaluadas

3 Creation of a requirementsspecification document

06:00 Evaluacióncontinua

TI: Técnica deltipo TrabajoIndividual

No 5% 5 / 10 CE5

4 Validation of a specificationdocument


PG: Técnica deltipo Presentaciónen Grupo

No 5% 5 / 10




No 5% 5 / 10

6 Paper writing 06:00 Evaluacióncontinua


No 5% 5 / 10 CE5



No 5% 5 / 10 CE5



No 5% 5 / 10 CE5

9 Requirements managementexercise


OT: Otras técnicasevaluativas

No 5% 5 / 10 CE5

10 Requirements managementexercise



No 5% 5 / 10 CE5

11 Model checking exercise 04:00 Evaluacióncontinua


No 5% 5 / 10 CE5

12 Model checking exercise 04:00 Evaluacióncontinua


No 5% 5 / 10 CE5

13 Requirements project 15:00 Evaluacióncontinua


No 10% 5 / 10 CE5



No 10% 5 / 10 CE5



No 10% 5 / 10 CE5



No 10% 5 / 10 CE5

17 Exam 02:00 Evaluación sóloprueba final

EX: Técnica deltipo ExamenEscrito

No 100% 5 / 10 CE5

17 Participation in classroomactivities



No 10% 5 / 10

Criterios de Evaluación

The assessment of assignments will depend on (1) presentation made by the students at the classroom and (2) the●

correctness of the results.The final grade will be calculated using a weighted average as described before.●






GA_10AM_103000482_1S_2016-17 9

Recursos Didácticos

Descripción Tipo Observaciones

Course material Recursos web All required materials will be available at moodle



7.2 Project Management and Organizational Processes Mod-ule

7.2.1 Models and Methods for Process Improvement and Assess-ment





GA_10AM_103000486_1S_2016-17


ASIGNATURAModels and methods for process improvement and assessment


7.2 Project Management and Organizational Processes Module 21





GA_10AM_103000486_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Models and methods for process improvement and assessment






Nombre en inglés Models and methods for process improvement and assessments

Datos Generales

Créditos 4 Curso 1





Otros Requisitos





Knowledge about the software life cycle (processes and tasks)






GA_10AM_103000486_1S_2016-17 2

Competencias

CE10 - Evaluar de forma objetiva los procesos y productos frente a los estándares y normas aplicables.

CE4 - Aplicar los modelos de proceso de desarrollo a las características de un proyecto software

CE9 - Definir, evaluar y mejorar los procesos software de una organización.


RA35 - Es capaz de definir, evaluar y mejorar los procesos software de una organización

RA36 - Posee dotes para liderar el cambio dentro de la organización

RA37 - Está capacitado para introducir mejoras en la organización






GA_10AM_103000486_1S_2016-17 3



Calvo-Manzano Villalon, Jose Antonio(Coordinador/a)

5106 [email protected] L - 10:00 - 13:00

X - 10:00 - 13:00







GA_10AM_103000486_1S_2016-17 4


New technologies are changing our way of life:planes, trains, communications, e-commerce, etc, and all of them need softwareto run. However, software is developed with poor quality; overruns in resources, effort and budget; and delays in delivery. Itmeans that organizations must improve their way of producing software. In this context, it appears software processimprovement. It consists of applying consistently the practices that provide good results, and changing those that causeproblems.

So, enterprises should know their capacity/maturity level in order to develop software. First, enterprises must be assessedagainst a reference model. Some of these reference models are the constellations (CMMI Development, Acquisition and Services)provided by Carnegie Mellon University/Software Engineering Institute /CMMI Institute.

in this subject, and independently of the reference model used, a generic process improvement lifecycle will be explainedoriented to large enterprises as well as small and medium-sized enterprises. Also, a method to make an assessment will bedescribed.

Temario

1. Introduction

1.1. Maturity Profile

1.2. State of the practice

1.3. Process improvement concepts

2. Process Improvement life cycles

2.1. IDEAL, ISO 15504

2.2. Action Focus Improvement Model

3. Reference Process Models

3.1. CMMI Constellations: representations, maturity/capacity levels, institutionalization

3.2. Oriented to Development

3.3. Oriented to Services






GA_10AM_103000486_1S_2016-17 5

Cronograma






Semana 1 Chapter 1: Maturity ProfileReportDuración: 03:00


Discussion/Participating inclassDuración: 00:00



Actividad presencial

Semana 2 Chapter 1: State of thepractice. Process ImprovementconceptsDuración: 03:00






Semana 3 Chapter 1: Exercise related toReturn on investmentDuración: 01:00

PR: Actividad del tipo Clase deProblemas





Exercise related to calculatethe Return of InvestmentDuración: 02:00

TG: Técnica del tipo Trabajo en Grupo



Semana 4 Chapter 2: ProcessImprovement life cyclesDuración: 03:00






Semana 5 Chapter 2: ProcessImprovement life cycles: AFIM:CommitmentDuración: 03:00






Semana 6 Exercise related to ROI onCommitmentDuración: 01:00


Exercise related to ROI onCommitmentDuración: 02:00




Semana 7 Chapter 2: ProcessImprovement life cycles: AFIM:AssessmentDuración: 03:00











GA_10AM_103000486_1S_2016-17 6













Semana 10 Exercise related to ROI onAssessmentDuración: 01:00


Exercise related to ROI onAssessmentDuración: 02:00




Semana 11 Chapter 2: ProcessImprovement life cycles: AFIM:Action Plan andImplementationDuración: 03:00






Semana 12 Exercise related to ROI onAction Plan andImplementationDuración: 01:00


Exercise related to Action Planand ImplementationDuración: 02:00




Semana 13 Chapter 3: CMMIConstellationsDuración: 03:00






Semana 14 Chapter 3: Process Modelsoriented to development andservicesDuración: 02:00


CMMI ConceptsDuración: 01:00




Semana 15 Presentation on a ServiceProcessDuración: 03:00

PI: Técnica del tipo PresentaciónIndividual



Semana 16 Presentation on a ServiceProcessDuración: 03:00









GA_10AM_103000486_1S_2016-17 7

Semana 17 Final TestDuración: 03:00










GA_10AM_103000486_1S_2016-17 8





1 Discussion/Participating in class 00:00 Evaluacióncontinua


Sí 1.5% 1 / 10 CE10, CE9



Sí 1.5% 1 / 10 CE10, CE9



Sí 1.5% 1 / 10 CE10, CE9

3 Exercise related to calculate theReturn of Investment


TG: Técnica deltipo Trabajo enGrupo

Sí 10% 5 / 10 CE9



Sí 1.5% 1 / 10 CE4, CE10, CE9



Sí 1.5% 1 / 10 CE4, CE10, CE9

6 Exercise related to ROI onCommitment



Sí 10% 5 / 10 CE10, CE9



Sí 1.5% 1 / 10 CE4, CE10, CE9



Sí 1.5% 1 / 10 CE10, CE9



Sí 1.5% 1 / 10 CE4, CE10, CE9

10 Exercise related to ROI onAssessment



Sí 10% 5 / 10 CE10, CE9



Sí 1.5% 1 / 10 CE10, CE9

12 Exercise related to Action Planand Implementation



Sí 10% 5 / 10 CE10, CE9



Sí 1.5% 1 / 10 CE10, CE9

14 CMMI Concepts 01:00 Evaluacióncontinua


Sí 30% 5 / 10 CE10, CE9

15 Presentation on a ServiceProcess


PI: Técnica deltipo PresentaciónIndividual

Sí 15% 5 / 10 CE10, CE9

16 Presentation on a ServiceProcess



Sí 5 / 10 CE10, CE9

17 Final Test 03:00 Evaluación sóloprueba final


No 100% 5 / 10 CE4, CE10, CE9


The assessment activities are the following:

Attendance and Active participation of students during the classes (15%).●

Exercise related to Return on Investment (10%).●

Exercise related to ROI on Commitment (10%), Assessment (10%), and Action Plan and Implementation (10%).●

Individual or group research work (15%). This activity is divided into two ones. One related to the individual skills in●

communications (7.5%) and the other one related to the memory of the work itself (7.5%).






GA_10AM_103000486_1S_2016-17 9

Students should have a rate greater o equal to 5.00 (over 10.00) to pass the subject






GA_10AM_103000486_1S_2016-17 10



Subject Moodle Site Recursos web Students will be able to get the slides and other resources fromthe Moodle platform.

IDEAL Bibliografía McFeeley,B.;IDEALSM:AUsers?sGuideforSoftwareProcessImprovement;HandbookCMU/SEI-?96-?HB-?001;February1996

CMMI-DEV Bibliografía CMMIProductTeam;CMMI®forDevelopment,Version1.3,CMMI-?DEV,V1.3;CMU/SEI-?2010-?TR-?033;November2010

CMMI-SVC Bibliografía CMMIProductTeam;CMMIforServices,v1.3(CMMI-?SVC);CMU/SEI-?2010-?TR-?034;November2010






GA_10AM_103000486_1S_2016-17 11


SCAMPI Bibliografía SCAMPIUpgradeTeam;StandardCMMI®AppraisalMethodforProcessImprovement(SCAMPISM)A,Version1.3:MethodDefinitionDocument;HandbookCMU/SEI2011-?HB-?001;March2011

ITIL Bibliografía ITIL-?InformationTechnologyInfrastructureLibrary(ServiceStrategy,ServiceDesign,ServiceTransition,ServiceOperation,ContinualServiceImprovement)



7.2.2 Software Project Management





GA_10AM_103000485_1S_2016-17


ASIGNATURASoftware project management







GA_10AM_103000485_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Software project management






Nombre en inglés Software project management

Datos Generales

Créditos 4 Curso 1





Otros Requisitos











GA_10AM_103000485_1S_2016-17 2

Competencias

CE1 - Elaborar un plan de proyecto que permita coordinar y priorizar recursos y actividades para obtener los resultadosesperados en los plazos, costes y calidad establecidos

CE2 - Llevar a cabo la monitorización de un proyecto software y tomar acciones correctivas si fuera necesario

CE3 - Elaborar una estimación de los parámetros del proyecto software.

CG1 - Que los estudiantes sepan aplicar los conocimientos adquiridos y su capacidad de resolución de problemas en entornosnuevos o poco conocidos dentro de contextos más amplios (o multidisciplinares) relacionados con su área de estudio (RD)

CG17 - Habilidades de gestión y capacidad de liderar un equipo que puede estar integrado por disciplinas y niveles distintos

CG18 - Capacidad de trabajar y comunicarse también en contextos internacionales

CG2 - Que los estudiantes sean capaces de integrar conocimientos y enfrentarse a la complejidad de formular juicios a partir deuna información que, siendo incompleta o limitada, incluya reflexiones sobre las responsabilidades sociales y éticas vinculadasa la aplicación de sus conocimientos y juicios (RD)

CG3 - Que los estudiantes sepan comunicar sus conclusiones y los conocimientos y razones últimas que las sustentan a públicosespecializados y no especializados de un modo claro y sin ambigüedades (RD)

CG5 - Organización y planificación


RA2 - Facing a real problem, chooses an appropriate Software Engineering solution, analyzing its viability, what can and cannotbe achieved from the current state of development of the selected solution, and what is expected to advance in the future

RA25 - Communication skills in public SC13, SC14, CG3, CG18 S

RA58 - Development of a business case for a software project

RA59 - Development of a project plan using as input estimation data

RA26 - Group work skill SC13, SC14, CG17 A

RA60 - Re-plannification of a software project with monitoring information

RA61 - Identify the elements of a risk management plan and its rationale






GA_10AM_103000485_1S_2016-17 3



Moreno Sanchez-Capuchino, Ana Maria(Coordinador/a)








GA_10AM_103000485_1S_2016-17 4


Temario

1. Introduction to Software Project Management

1.1. 1.1 Psychological Model of Software Engineers

1.2. Leadership versus Management

1.3. The Basic Functions of Project Management

1.4. Developing the Business Case

2. Developing and Motivating the Project Team

2.1. What it Takes for a Team to be Effective

2.2. The Basics of Personalities

2.3. Motivating Software Engineers

3. Strategic Approaches to Project Planning

3.1. The Balanced Scorecard (BSC)

3.2. Using SWOT to Develop the BSC

3.3. Tracking Progress

4. Estimating Project Size, Cost, Schedule

5. Project Risk Management

5.1. What Risk is/is not

5.2. Strategies for Mitigating Risk

5.3. Risk Management Methods

6. Tracking the Progress of a Software Project

6.1. Earned Value Management

6.2. Time Value






GA_10AM_103000485_1S_2016-17 5

Cronograma




Semana Actividad Prensencial en Aula Actividad Prensencial en Laboratorio Otra Actividad Presencial Actividades Evaluación

Semana 1 Chapter 1Duración: 02:00


















Presentation of students workDuración: 02:00


Evaluación continua y sólo pruebafinal









GA_10AM_103000485_1S_2016-17 6



Chapter 6Duración: 02:00










Chapter 6Duración: 02:00


Semana 16 Presentation of students workDuración: 02:00




Active participation ofstudentsDuración: 00:00




Semana 17 Final ReportDuración: 00:00










GA_10AM_103000485_1S_2016-17 7





9 Presentation of students work 02:00 Evaluacióncontinua y sóloprueba final


Sí 5% 5 / 10 CE1, CE3,CG17, CG1,CE2, CG3, CG2,CG18, CG5

16 Presentation of students work 02:00 Evaluacióncontinua y sóloprueba final


Sí 35% 5 / 10 CE1, CE3, CE2,CG1, CG17,CG2, CG3,CG18, CG5

16 Active participation of students 00:00 Evaluacióncontinua y sóloprueba final


No 10% CG1, CG3, CG2

17 Final Report 00:00 Evaluacióncontinua y sóloprueba final


No 50% 5 / 10 CE1, CE3, CE2,CG17, CG1,CG3, CG2,CG18, CG5


The final grade of students will be calculated according to their performance in the reports to be done and their classparticipation.

- Active participation of students (10%)

- Content of the reports (50%)

- Presentation of the two reports (40%)

Students must get a minimum of 5 points (over 10) in the assessment of each report in order to pass the matter.

Students must get a minimum of 5 points (over 10) as final grade in order to pass the matter.






GA_10AM_103000485_1S_2016-17 8



Bibliography Bibliografía Getting results from software development teamsPeters, Lawrence. Microsoft Press. 2008ISBN: 978-0-7356-2346-0

SPM web page Recursos web Web page of the subjecthttp://www.grise.upm.es/docencia/estimacion/)


7.3 Support Processes Module 43

7.3 Support Processes Module

7.3.1 Software Metrics





GA_10AM_103000488_1S_2016-17


ASIGNATURASoftware metrics







GA_10AM_103000488_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Software metrics






Nombre en inglés Software metrics

Datos Generales

Créditos 4 Curso 1





Otros Requisitos











GA_10AM_103000488_1S_2016-17 2

Competencias

CE10 - Evaluar de forma objetiva los procesos y productos frente a los estándares y normas aplicables.


RA44 - Es capaz de liderar e implantar planes de medida para la evaluación de procesos y productos

RA45 - Es capaz de analizar datos para la estimación, planificación y control de calidad en proyectos software






GA_10AM_103000488_1S_2016-17 3



San Feliu Gilabert, Tomas(Coordinador/a)


M - 08:00 - 09:00

X - 08:00 - 09:00







GA_10AM_103000488_1S_2016-17 4


The students will:

Understand the theoretical aspects of software measurements.●

Demonstrate the knowledge of software metrics.●

Demonstrate the knowledge of using software metrics in software development, software maintenance, and software project●

management.Demonstrate the knowledge of developing and maintaining a measurement program.●

Temario

1. Introduction to quality control and planning needs

2. Measurement goals

3. Specify measures

4. Specify analysis procedures

5. Communicate Results






GA_10AM_103000488_1S_2016-17 5

Cronograma








Class ParticipationDuración: 00:00
























Paper presentationDuración: 01:00

























GA_10AM_103000488_1S_2016-17 6









Definition reportDuración: 02:00








































Analysis ReportDuración: 02:00













GA_10AM_103000488_1S_2016-17 7



Final testDuración: 01:00

ET: Técnica del tipo PruebaTelemática







Semana 17 Examen finalDuración: 02:00










GA_10AM_103000488_1S_2016-17 8





1 Class Participation 00:00 Evaluacióncontinua


No .69% 3 / 10



No .69% 3 / 10



No .68% 3 / 10



No .62% 3 / 10

5 Paper presentation 01:00 Evaluacióncontinua


Sí 15% 3 / 10 CE10



No .61% 3 / 10



No .61% 3 / 10



No .61% 3 / 10



No .61% 3 / 10

9 Definition report 02:00 Evaluacióncontinua


Sí 20% 3 / 10 CE10



No .61% 3 / 10



No .61% 3 / 10



No .61% 3 / 10



No .61% 3 / 10



No .61% 3 / 10



No .61% 3 / 10

15 Analysis Report 02:00 Evaluacióncontinua


Sí 30% 3 / 10 CE10



No .61% 3 / 10

16 Final test 01:00 Evaluacióncontinua

ET: Técnica deltipo PruebaTelemática

Sí 25% 3 / 10 CE10



No .61% 3 / 10

17 Examen final 02:00 Evaluación sóloprueba final


Sí 100% 3 / 10 CE10


The final evaluation of the students is based on the evaluation of a paper(15%), ameasurement definition report exam(20%),●

an analysis report(30%) and an individualwritten exam(25%).Class participation and additional activities in the classroomare performed. Theseadditional activities represent a 10% of the final scoring.






GA_10AM_103000488_1S_2016-17 9






GA_10AM_103000488_1S_2016-17 10



Metrics and Models in Software QualityEngineering

Bibliografía Stephen Kan, Metrics and Models in SoftwareQualityEngineering, Addison Wesley 2003

Measuring the Software Process Bibliografía Anita Carleton, Measuring the SoftwareProcess, Addison Wesley

The big book of Six Sigma training games Bibliografía Chris Chen and Hadley Roth, The big book ofSix Sigmatraining games, McGraw-Hill, 2005



7.3.2 Verification and Validation





GA_10AM_103000489_1S_2016-17


ASIGNATURAVerification and validation







GA_10AM_103000489_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Verification and validation






Nombre en inglés Verification and validation

Datos Generales

Créditos 6 Curso 1





Otros Requisitos





Lenguajes de programación C y JAVA






GA_10AM_103000489_1S_2016-17 2

Competencias

CE7 - Elaborar un plan de verificación y validación que permita coordinar y priorizar recursos y actividades para garantizar elnivel de calidad requerido.

CE8 - Aplicar las técnicas de verificación y validación más adecuadas para un proyecto de desarrollo software, enmarcadas enun plan de verificación y validación.


RA8 - Knows and determines the most appropriate verification and validation techniques to be applied in a softwaredevelopment project with the aim of assuring the quality level required

RA39 - Conoce y determina las técnicas de verificación y validación más apropiadas para aplicar en un proyecto de desarrollode software con el objetivo de garantizar el nivel de calidad requerido

RA12 - Knows and applies product and process quality control techniques






GA_10AM_103000489_1S_2016-17 3



Vegas Hernandez, Sira (Coordinador/a) 5105 [email protected] L - 13:00 - 16:00

J - 14:00 - 17:00







GA_10AM_103000489_1S_2016-17 4


Temario

1. Introduction

1.1. Introduction to V&V

1.2. V&V and the software development process

1.3. V&V and the software development products

2. Static evaluation

2.1. Introduction to static evaluation

2.2. Static evaluation techniques

2.3. Reading techniques

3. Dynamic evaluation: Software testing

3.1. Introduction to software testing

3.2. Testing levels

3.3. The testing process

3.4. Software verification and validation plan

3.5. Testing tools






GA_10AM_103000489_1S_2016-17 5

Cronograma






Semana 1 IntroducciónDuración: 03:00


Semana 2 IntroducciónDuración: 03:00


Semana 3 Evaluación estáticaDuración: 03:00


Semana 4 Evaluación estáticaDuración: 03:00


Static techniques exerciseDuración: 02:00




Semana 5 Evaluación dinámicaDuración: 03:00






White box exerciseDuración: 02:00










Black box exerciseDuración: 02:00









GA_10AM_103000489_1S_2016-17 6

Semana 11 Assignment: testing asoftware systemDuración: 02:00




Semana 12

Semana 13

Semana 14

Semana 15 Recopilación de la asignaturaDuración: 02:00


Student's attitude regardinglectures and course in generalDuración: 02:00




Semana 16 Final examDuración: 02:00




Semana 17







GA_10AM_103000489_1S_2016-17 7





4 Static techniques exercise 02:00 Evaluacióncontinua


No 10% 5 / 10 CE7, CE8

7 White box exercise 02:00 Evaluacióncontinua


No 10% 5 / 10 CE7, CE8

10 Black box exercise 02:00 Evaluacióncontinua


No 10% 5 / 10 CE7, CE8

11 Assignment: testing a softwaresystem



No 60% 5 / 10 CE7, CE8

15 Student's attitude regardinglectures and course in general



Sí 10% CE7, CE8

16 Final exam 02:00 Evaluación sóloprueba final


Sí 100% 5 / 10 CE7, CE8


The score of the course is calculated regarding the performance of the student in the different tasks that (s)he has beenassigned:

- Exercise applying static techniques to a program (10% of the score).

- Exercise applying white box techniques to a program (10% of the score).

- Exercise applying black box techniques to a program (10% of the score).

- Assignment performing testing on a software system (50% of the score).

It will also be taken into consideration for the score of the course the participation and attitude of the student during thelectures and regarding the course in general (10%).






GA_10AM_103000489_1S_2016-17 8



B. Beizer. "Software Testing Techniques" 2ª Edición. 1990 Bibliografía

G. J. Myers. "The Art of Software Testing" 2ª Edición. Wiley. 2004. Bibliografía

P.C. Jorgensen. Software Testing. A Craftsman?s Approach. CRC Press,1995.

Bibliografía

C. Kaner, J. Falk, H.Q. Nguyen. Testing Computer Software. Wiley,1999.

Bibliografía

W.E. Perry. Effective methods for software testing. Tercera edición.Wiley. 2006

Bibliografía

S.L. Pfleeger. Ingeniería de software: teoría y práctica. Segundaedición. Prentice Hall. 2002

Bibliografía

IEEE V&V standards Bibliografía

Moodle site of the course Recursos web


7.4 Advanced Software Engineering Aspects Module 65

7.4 Advanced Software Engineering Aspects Module

7.4.1 Agile Software Development: Agile Practices and Agile Us-ability





GA_10AM_103000545_1S_2016-17


ASIGNATURAAgile software development: agile practices and agile usability







GA_10AM_103000545_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Agile software development: agile practices and agile usability




Carácter Optativa


Nombre en inglés Non-classic software methodologies: project management and development strategies

Datos Generales

Créditos 4 Curso 1





Otros Requisitos











GA_10AM_103000545_1S_2016-17 2

Competencias

CE1 - Elaborar un plan de proyecto que permita coordinar y priorizar recursos y actividades para obtener los resultadosesperados en los plazos, costes y calidad establecidos

CE14 - Comprender lo que pueden y no pueden conseguir las prácticas actuales de ingeniería del software, y sus limitaciones ysu posible futura evolución.

CE2 - Llevar a cabo la monitorización de un proyecto software y tomar acciones correctivas si fuera necesario

CE3 - Elaborar una estimación de los parámetros del proyecto software.

CE5 - Educir, analizar y especificar las necesidades de los clientes, usuarios y otras partes interesadas, teniendo en cuenta losposibles condicionantes que pudieran afectar al sistema a desarrollar

CG10 - Capacidad de pensamiento creativo con el objetivo de desarrollar enfoques y métodos nuevos y originales

CG13 - Apreciación de los límites del conocimiento actual y de la aplicación práctica de la tecnología más reciente

CG17 - Habilidades de gestión y capacidad de liderar un equipo que puede estar integrado por disciplinas y niveles distintos


CG4 - Que los estudiantes posean las habilidades de aprendizaje que les permitan continuar estudiando de un modo que habráde ser en gran medida autodirigido o autónomo (RD)


RA25 - Communication skills in public SC13, SC14, CG3, CG18 S

RA62 - Identification of the differences between agile and traditional software development

RA1 - Within an application field of Software Engineering, uses and designs the appropriate solution to solve some of itsproblems, describing the technical difficulties and the application limits

RA63 - Identification of the most common agile methods and practices and their particularities


RA23 - Time organization capability SC13, SC14 K

RA64 - Identification of the implications of software quality and in particular software usability in the agile domain

RA27 - Negotiation skill SC13, SC14, CG18 C






GA_10AM_103000545_1S_2016-17 3



Moreno Sanchez-Capuchino, Ana Maria(Coordinador/a)








GA_10AM_103000545_1S_2016-17 4


Temario

1. Agile Artifacts

2. Fundamentals of Agile Development

3. Description of Agile Methods

3.1. XP

3.2. Scrum

3.3. Kanban

3.4. FDD

3.5. Comparisson of Agile Methods

4. Agile Usability

4.1. The User/Customer Role in Agile Methods

4.2. Implications of Usability Mechanisms in the Agile Artefacts

4.3. Implications of Usability in the Agile Process

5. Agile Project






GA_10AM_103000545_1S_2016-17 5

Cronograma






Semana 1 Unit 1Duración: 02:00














Presentation of Report 1Duración: 00:30




Description of Report 1Duración: 00:00















GA_10AM_103000545_1S_2016-17 6





Presentation of ProjectDuración: 00:30






Unit 5Duración: 02:00










Unit 5Duración: 02:00








Semana 17 Descrption of the ProjectReportDuración: 00:00




Active Participation ofStudentsDuración: 00:00










GA_10AM_103000545_1S_2016-17 7





7 Presentation of Report 1 00:30 Evaluacióncontinua y sóloprueba final


Sí 5% 5 / 10 CG4, CG18,CG10, CG13

7 Description of Report 1 00:00 Evaluacióncontinua y sóloprueba final


No 20% 5 / 10 CG13, CG4,CG18, CG10

12 Presentation of Project 00:30 Evaluacióncontinua y sóloprueba final


Sí 5% 5 / 10 CE1, CE3, CE5,CE14, CG10,CE2, CG18



Sí 5% 5 / 10 CG13, CE1,CE3, CE5, CE14,CG10, CE2,CG18



Sí 5% 5 / 10 CG13, CE5,CE14, CE1, CE3,CE2, CG10

17 Descrption of the Project Report 00:00 Evaluacióncontinua y sóloprueba final


No 50% 5 / 10 CE1, CE3,CG18, CG10,CE2, CE14, CE5,CG13, CG17

17 Active Participation of Students 00:00 Evaluacióncontinua y sóloprueba final


No 10% CG4, CG13,CG18, CE14,CG10


The final grade of students will be calculated according to their performance in the two reports to be done and their classparticipation.

- Active participation of students (10%)

- Content of two reports (20%, 50% each)

- Presentation of the two reports (5%, 15% each)

Students must get a minimum of 5 points in the assessment of each of the two reports in order to pass the matter.

Students must get a minimum of 5 points (over 10) as final grade in order to pass the matter.






GA_10AM_103000545_1S_2016-17 8



Bibliography Agile Bibliografía A. Cockburn. Agile Software Development, Addison Wesley,2002

Bibliography Scrum Recursos web http://scrumtraininginstitute.com/library

Process Agility and Software Usability Recursos web http://citeseer.ist.psu.edu/465732.html

Agile Ecosystems Bibliografía J. Higsmith. Agile Software Development Ecosystems.Addison-Wesley, 2005



7.4.2 Challenges for Accessible Computing for People with Func-tional Diversity





GA_10AM_103000603_1S_2016-17


ASIGNATURAChallenges for accessible computing for people with functional diversity







GA_10AM_103000603_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Challenges for accessible computing for people with functional diversity




Carácter Optativa


Nombre en inglés Challenges for accessible computing for people with functional diversity

Datos Generales

Créditos 4 Curso 1





Otros Requisitos











GA_10AM_103000603_1S_2016-17 2

Competencias

CE13 - Tener una visión de los distintos aspectos específicos y emergentes de la ingeniería del software, y profundizar enalgunos de ellos


CG13 - Apreciación de los límites del conocimiento actual y de la aplicación práctica de la tecnología más reciente


RA3 - Explains which are the Software Engineering limits and frontiers, and the base of new tendencies and developments andadvanced topics and their possible application

RA18 - Given a real problem, the student chooses the most appropriate software engineering solution, analyzing the solutionfeasibility, what can and cannot be achieved through the current status of the chosen solution, and what it can advance in thefuture.







GA_10AM_103000603_1S_2016-17 3



Martinez Normand, Loic Antonio D2303 [email protected] L - 11:00 - 13:30

M - 11:00 - 13:30

V - 16:00 - 17:00

Se recomienda pedir citaprevia por correo electrónico

Fuertes Castro, Jose Luis(Coordinador/a)

D4307 [email protected] L - 17:00 - 20:00

J - 17:00 - 20:00







GA_10AM_103000603_1S_2016-17 4


This module provides a specialization about the accessibility of information and communication technologies (ICT) for personswith functional diversity (disability). It is mainly focused on current research issues in the field.

The module will start with an introduction to basic ICT accessibiltiy concepts: functional diversity, design for all, legislation,standards and the assessment of the accessibility degree of ICT products and services.

After that, the students will work on current challenges in the field, such as:

Methods, techniques and tools for accessibility evaluation●

Applying user centred design and design for all in development methodologies●

New ICT accessibility standards●

Temario

1. Functional diversity, accessibility and design for all

1.1. Introduction

1.2. Functional diversity

1.3. Assistive products for ICT

1.4. Design for all

2. ICT accessibility standards

2.1. Introduction to standards

2.2. Relevant ICT accessibility standards

2.3. Deeper study of one accessibility standard

2.4. Conformity assessment

3. User centred design

3.1. Introduction to user centred design

4. State of the art in ICT accessibility

4.1. State of the art and future trends






GA_10AM_103000603_1S_2016-17 5

Cronograma






Semana 1 Module introductionDuración: 02:00


Semana 2 Chapter 1, 1.1 and 1.2Duración: 02:00


Semana 3 Chapter 1, 1.3 and 1.4Duración: 02:00


Semana 4 Chapter 2, 2.1 and 2.2.Explanation of exercise 1Duración: 02:00


Semana 5 Chapter 2, 2.3Duración: 01:30


Jigsaw evaluation (discussion)Duración: 00:30




Semana 6 Explanation of exercise 2Duración: 01:00


Test 1Duración: 01:00






Jigsaw evaluation (discussion)Duración: 00:30




Delivery of exercise 1Duración: 00:00






Semana 9 Classroom tutoring. Exercise 2Duración: 02:00







GA_10AM_103000603_1S_2016-17 6







Semana 11 Chapter 4, 4.1. Explanation ofexercise 3Duración: 02:00


Semana 12 Classroom tutoring aboutCollective revision of exercise2Duración: 02:00






Semana 15 Classroom presentation ofexercise 3Duración: 02:00




Semana 16 Classroom presentation ofexercise 3Duración: 02:00













GA_10AM_103000603_1S_2016-17 7

Semana 17 Test 1Duración: 01:00




Presentation of exercise 3Duración: 02:00




Test 2Duración: 01:00










GA_10AM_103000603_1S_2016-17 8





5 Jigsaw evaluation (discussion) 00:30 Evaluacióncontinua y sóloprueba final


Sí 5% CE14

6 Test 1 01:00 Evaluacióncontinua


Sí 10% CE13

7 Jigsaw evaluation (discussion) 00:30 Evaluacióncontinua y sóloprueba final


Sí 5% CE14

7 Delivery of exercise 1 00:00 Evaluacióncontinua y sóloprueba final


No 15% CE14



No 20% CE14

15 Classroom presentation ofexercise 3



Sí 7.5% CE13, CG13

16 Classroom presentation ofexercise 3



Sí 7.5% CG13, CE13



No 20% CE13, CG13

17 Test 1 01:00 Evaluación sóloprueba final


Sí 10% CE13

17 Presentation of exercise 3 02:00 Evaluación sóloprueba final


Sí 15% CE13, CG13

17 Test 2 01:00 Evaluacióncontinua y sóloprueba final


Sí 10% CE14, CG13


The assessment of this module is divided into two parts: theory and practice. Both parts have to be passed in order to pass themodule. The grades obtained in theory and practice are combined as described in the section on evaluation activities.

TheoryThe theoretical part of the module contains two different assessments. First, there will be two test-based assessments.Second, there is going to be assessment of the performance of the collaborative learning sessions that will be part of the studyof accessibility standards

Practical work

The practical work consists of 3 exercises:

Exercise 1: a document containing change proposals for an accessibility standard.●

Exercise 2: an accessibility assessment of an ICT product, using the standard studied during collaborative learning.●

Exercise 3: state of the art on one topic related to ICT accessibility. Students will make a short presentation in the classroom.●

All the exercises are individual.

Assessment procedure






GA_10AM_103000603_1S_2016-17 9

a) Continuous evaluation

The module will be assessed in a scale of 10 points, divided into 3 points for the theory and 7 points for the practical exercises.To pass the complete module it will be necessary to obtain a minimum of 1 point in theory, 3 points in the exercises and 5points in the addition of theory and practice.

All the practical exercises are mandatory and will be graded according to the section on evaluation activities.

The dates for the publication of grades and the ulterior exam revision will be notified as part of the corresponding exam. Theexam revision will be made based on prior enquiries made by the students.

b) Extraordinary evaluation period (July)

In the extraordinary evaluation period (July) the theory tests will be repeated and the pending exercises can be delivered again.The participation in collaborative learning will not be re-assessed, so the grades received previously will be reused.

The grades obtained will apply the same weights as described for continuous evaluation.

c) Non-continuous evaluation

In the case of non-continuous evaluation, there will be a theory exam and a classroom presentation of exercise 3 in week 17.The three exercises have to be delivered in the same time period as the one defined for continuous evaluation. The student willalso have to attend the two collaborative sessions (jigsaw) described above.






GA_10AM_103000603_1S_2016-17 10



Don't make me think!: aCommon Sense Approach to WebUsability

Bibliografía Krug, S. New Riders, ISBN: 0321344758, Sept., 2005.

The Principles of UniversalDesign

Bibliografía Connell, B.R.; Jones, M.; Mace, R.; Mueller, J.; Mullick, A.; Ostroff,E.; Sanford, J.; Steinfeld, E.; Story, M.; Vanderheiden, G. Version2.0. North Carolina State University. Abril 1997

http://www.ncsu.edu/ncsu/design/cud/about_ud/udprinciples.htm

Information technology --Accessibility considerations forpeople with disabilities -- Part 1:User needs summary

Bibliografía Organización Internacional de Normalización (ISO), ComisiónInternacional de Electrotecnia (IEC). ISO/IEC TR 29138-1. 2009.Disponible de forma gratuita en:http://jtc1access.org/TR29138.htm

El modelo de la diversidad. LaBioética y los Derechos Humanoscomo herramientas para alcanzarla plena dignidad en la diversidadfuncional

Bibliografía Palacios, A.; Romañach, J. Ediciones Diversitas, ISBN:8496474402, 2007.

A Web for Everyone. Designingaccessible user experiences

Bibliografía Horton, S.; Quesenbery, W. Rosenfeld. 2014.

SIDAR Recursos web Fundación Sidar - Acceso Universal: http://www.sidar.org,España. 2016

Página web de la asignatura Recursos web http://www-lt.ls.fi.upm.es/dpt/



7.4.3 Critical Software





GA_10AM_103000540_1S_2016-17


ASIGNATURACritical software







GA_10AM_103000540_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Critical software




Carácter Optativa


Nombre en inglés Critical software

Datos Generales

Créditos 3 Curso 1





Otros Requisitos











GA_10AM_103000540_1S_2016-17 2

Competencias




RA19 - The student explains what are the software engineering limits and frontiers, and the base for new trends anddevelopments, and about the advanced issues and their application.

RA17 - Given a specific software engineering field, the student assesses and designs the most appropriate solution to solvesome of its problems, presenting the technical difficulties and applicability limitations.

RA18 - Given a real problem, the student chooses the most appropriate software engineering solution, analyzing the solutionfeasibility, what can and cannot be achieved through the current status of the chosen solution, and what it can advance in thefuture.






GA_10AM_103000540_1S_2016-17 3



Silva Vazquez, Andres (Coordinador/a) 5107 [email protected] M - 11:00 - 14:00

J - 11:00 - 14:00







GA_10AM_103000540_1S_2016-17 4


Temario

1. Safeware concepts

1.1. Normal Accidents theory

1.2. Basic Concepts

1.3. Reliability vs. Safety

1.4. Hazard & Risk Analysis

1.5. Common Techniques

2. Design and Safeware

2.1. Hazard elimination

2.2. Hazard reduction

2.3. Hazard control

2.4. Examples

3. Concepts from the IEC61508 Standard

3.1. Introduction to IEC61508

3.2. Concepts: SIL, functional safety, etc.

3.3. Hazard log

3.4. Limits of IEC61508

4. Human and Organizational Factors

4.1. Performance models

4.2. Human error

4.3. Organizational problems

4.4. Solution proposals






GA_10AM_103000540_1S_2016-17 5

Cronograma






Semana 1 Lecture/workshop on topics1.1 and 1.2Duración: 02:00


Elaboration of thepresentation and draft of theexpository writingDuración: 06:00




Semana 2 Lecture/workshop on topics1.3. 1.4 and 1.5Duración: 02:00










Semana 5 Lecture/workshop on topics3.1, 3.2Duración: 02:00















GA_10AM_103000540_1S_2016-17 6







Examen finalDuración: 05:00




Semana 9

Semana 10

Semana 11

Semana 12

Semana 13

Semana 14

Semana 15

Semana 16

Semana 17







GA_10AM_103000540_1S_2016-17 7





1 Elaboration of the presentationand draft of the expositorywriting



No 25% 3 / 10 CE13, CE14




No 25% 3 / 10 CE13, CE14




No 25% 3 / 10 CE13, CE14




No 25% 3 / 10 CE13, CE14



No 100% 3 / 10 CE13, CE14


The grading criteria for this subject are closely linked to the working methods. This method will be concept-oriented. For eachtopic and subtopic there will be a lecture/workshop in the classroom, and the teacher will choose a key concept. Later, thestudents, preferably in groups, will have one week for reading concept-related bibliography and elaborate a presentation and anexpository writing (8 pages max.).

Each group of students will present a draft of their work in the classroom, which may be evaluated (anonymously) by the otherstudents.The rhythm of work will be, approximately, as follows: every two weeks, each group of students will submit theexpository writing of past week's concept. In parallel, the students will attend the lectures/workshops that will be done in theclassroom, and possibly qualify them.

With more detail, the following two-week procedure will be followed for each concept:

The teacher will provide an introduction to a concept, relevant bibliography and documentation for the concept at hand. Such1.documentation will be a starting point for the student, who will explore other relevant sources of information.Each group of students will elaborate a presentation related to the concept. In parallel, they should start elaborating a draft2.document with the expository writing of the concept.The following week, in the classroom, the concept will be presented, the mistakes and problems detected in the presentation3.will be discussed and a consensus will be achieved. The rest of the students in the classroom may evaluate the presentations.The final expository writing (8 pages max.) will be uploaded to Moodle.4.

The concepts of the course are listed below, but they could be dynamically modified, along the course. For some topics theteacher will provide problems for being solved by the group: Hazard. Reliability vs. Safety. Risk. SafeWare and associatedtechniques. Concepts from the Std. IEC 61508: SIL, ALARP. Automation and Overautomation. Norman's Model. Latent errors andviolations. Models: STAMP (Leveson), ChiDeltas (Hall-Silva). Other concepts to be announced.

he mechanics of the course will be as follows:

The communication among the students and the teacher will be done through Moodle. The steps to be done at each point●

during the course will be announced always through Moodle.Problem resolution and clarification of student's questions will be done also through Moodle.●

The documentation for each concept will be provided on demand, via Moodle.●

The purpose of evaluating the presentations by other students is to get an idea on how clear the concept has been explained.●

Of course, those qualifications are just informative for the teacher, who will have a final decision on the overall evaluation.

The final qualification will be an average of the teacher's qualifications for each submitted work, taking into account also the






GA_10AM_103000540_1S_2016-17 8

effort and overall attitude of each group of students.






GA_10AM_103000540_1S_2016-17 9



Bibliografía Bibliografía Bibliografía recopilada por el profesor de la asignatura ydisponible en http://www.citeulike.org/user/asilva/tag/emse yenhttp://www.citeulike.org/user/asilva/tag/safety



7.4.4 Data Engineering





GA_10AM_103000541_1S_2016-17


ASIGNATURAData engineering







GA_10AM_103000541_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Data engineering




Carácter Optativa


Nombre en inglés Data engineering

Datos Generales

Créditos 4 Curso 1





Otros Requisitos





? Conocimiento adecuado del concepto de empresa, su organización y gestión.

? Conocimiento y aplicación de las características, funcionalidades y estructura de las bases de datos, que permitan suadecuado uso, y el diseño y el análisis e implementación de aplicaciones basadas en ellos.

? Conocimiento y aplicación de los principios fundamentales y técnicas básicas de los sistemas inteligentes y su aplicaciónpráctica.

? Aptitud para aplicar los conocimientos sobre estadística y optimización.






GA_10AM_103000541_1S_2016-17 2

? Design and implementation of relational databases

SQL






GA_10AM_103000541_1S_2016-17 3

Competencias

CG19 - Aproximación sistemática a la gestión de riesgos

CG2 - Que los estudiantes sean capaces de integrar conocimientos y enfrentarse a la complejidad de formular juicios a partir deuna información que, siendo incompleta o limitada, incluya reflexiones sobre las responsabilidades sociales y éticas vinculadasa la aplicación de sus conocimientos y juicios (RD)

CG3 - Que los estudiantes sepan comunicar sus conclusiones y los conocimientos y razones últimas que las sustentan a públicosespecializados y no especializados de un modo claro y sin ambigüedades (RD)

CGP22 - Capacidad para comprender el mercado, sus hábitos y necesidades de productos o servicios tecnológicos



RA21 - Listening capability SC13, SC14, CG10 A

RA30 - Ante un problema real, elegir la solución de ingeniería del software más apropiada, analizando la viabilidad de susolución, lo que se puede y no se puede conseguir a través del estado actual de desarrollo de la solución seleccionada, lo quese espera que avance en el futuro

RA22 - Observing capability SC13, SC14, CG10 C

RA23 - Time organization capability SC13, SC14 K







GA_10AM_103000541_1S_2016-17 4



Segovia Perez, Fco.javier 2305 [email protected] L - 10:00 - 11:00

Hablar con el profesor

Menasalvas Ruiz, Ernestina(Coordinador/a)


hablar con la profesora







GA_10AM_103000541_1S_2016-17 5


The course is mainly dedicated to Data Mining Project development and data mining for improvement of software engineeringprojects

It will be evaluated taking into account the evaluation of the development of a project

Temario

1. Introducción. El valor de los datos: variedad, velocidad, volumen

1.1. Big Data

1.2. Data Mining

2. Procesos de Data Mining

2.1. Proceso de KDD

2.2. CRISP-DM: fases

2.3. El preproceso

3. Tipos de problemas de data mining

3.1. Clasificación

3.2. Clustering

3.3. Asociación

4. . Evaluación de los resultados

4.1. Técnicas de evaluación






GA_10AM_103000541_1S_2016-17 6

Cronograma






Semana 1 Tema 1Duración: 03:00




Tema 2Duración: 01:00










proyecto 1Duración: 02:00









































GA_10AM_103000541_1S_2016-17 7

























Semana 17 examen continuaDuración: 00:00




examen finalDuración: 00:00










GA_10AM_103000541_1S_2016-17 8





4 proyecto 1 02:00 Evaluacióncontinua


Sí 25% 5 / 10 CG2, CG3,CGP22



Sí 25% 5 / 10 CG19, CG2



Sí 25% 5 / 10 CGP22, CG19,CG3, CG2

17 examen continua 00:00 Evaluacióncontinua


Sí 25% 5 / 10 CG2, CG3,CGP22, CG19

17 examen final 00:00 Evaluación sóloprueba final


Sí 100% 5 / 10 CG19, CG2,CG3, CGP22


La asignatura de Procesos de data mining se evaluara mediante 1 proyectos, un examen y la asistencia y participación en clase.

Los proyectos se realizarán en grupos de hasta 3 alumnos de entre los matriculados de la asignatura al inicio del curso.

Para poder superar la asignatura, en la convocatoria de junio, se establecen los siguientes requisitos:

Obtener un mínimo de 50 puntos sobre los 100 disponible en el cómputo global de la evaluación sumativa1.Es OBLIGATORIO realizar el examen y completar todas las entregas de los proyectos2.En los informes y presentaciones de proyectos y casos prácticos se debe obtener una nota mínima igual o superior al 50% de3.la valoración del mismo (ver tabla de valoración sumativa)En los exámenes se debe obtener una nota mínima igual o superior al 50% de la valoración de mismo (ver tabla de4.valoración sumativa)El aspecto Participación en clase forma un 10% de la nota que se conformará a partir de la asistencia a clase, la participación5.en la misma y la respuesta correcta a las preguntas planteadas por los profesores de la asignatura, pudiéndose realizar encualquier momento a lo largo del curso

Para poder superar la asignatura en la convocatoria extraordinaria de julio, se establecen los siguientes requisitos:

Haber entregado los informes de proyectos y casos prácticos habiendo obtenido la nota mínima.1.Realizar las presentaciones de los casos prácticos y proyectos2.Realizar un examen de cada uno de los módulos de la asignatura3.Obtener un mínimo de 50 puntos sobre los 100 disponibles en el cómputo global de los dos módulos4.

Para aquellos alumnos que de forma extraordinaria, no puedan realizar la evaluación continua, y previa petición por escritodurante los primeros 15 días del curso, la forma de evaluación de la asignatura será la siguiente, siendo excluyente con laevaluación continua. Estos alumnos solo realizarán el examen final.






GA_10AM_103000541_1S_2016-17 9



Principles of Data Mining (Adaptive Computation and MachineLearning), D Hand, MIT Press, 2001.

Bibliografía

Jiawei Han, Micheline Kamber, Data Mining : Concepts and Techniques,2nd edition, Morgan Kaufmann, ISBN 1558609016, 2006.

Bibliografía

Data Mining Techniques: Marketing, Sales and Customer Support,Michael J. A. Berry, Gordon Linoff, John Wiley & Sons, 1997.

Bibliografía

Pang-Ning Tan, Michael Steinbach, Vipin Kumar, Introduction to DataMining, Pearson Addison Wesley (May, 2005). Hardcover: 769 pages.ISBN: 0321321367

Bibliografía

Ian Witten, Eibe Frank, Mark Hall, Data Mining: Practical MachineLearning Tools and Techniques, 3nd Edition, Morgan Kaufmann, ISBN978-0-12-374856-0, 2011.

Bibliografía

Página web de la asignatura en moodle Recursos web

WEKA Otros

Sala de trabajo en grupo con ordenadores Equipamiento

aula Equipamiento



7.4.5 Distributed and Outsourced Software Engineering





GA_10AM_103000604_1S_2016-17


ASIGNATURADistributed and outsourced software enginnering







GA_10AM_103000604_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Distributed and outsourced software enginnering




Carácter Optativa


Nombre en inglés Distributed and outsourced software enginnering

Datos Generales

Créditos 4 Curso 1





Otros Requisitos











GA_10AM_103000604_1S_2016-17 2

Competencias





RA71 - The students will be able to plan, manage and execute a distributed software development project

RA72 - The students will be able to assess the pros and cons of several technologies for distributed development






GA_10AM_103000604_1S_2016-17 3



Dieste Tubio, Oscar (Coordinador/a) D6203 [email protected] M - 17:00 - 19:00

V - 13:00 - 17:00







GA_10AM_103000604_1S_2016-17 4


DOSE aims teaching students how to perform distributed software development and face its challengues. Methodology isessentially practical. UPM students carry out a project with other students from several international universities (seehttp://se.inf.ethz.ch/research/dose/). The goal is creating a fully functional system working in distributed teams, starting from aset of requirements created by another remote team.

Temario

1. Requirements specification

2. Requirements validation

3. Design by contract

4. OO programming with Eiffel

5. Unit testing

6. Challengues in distributed development






GA_10AM_103000604_1S_2016-17 5

Cronograma






Semana 1 Course goals and methodologyDuración: 02:00






Creation of a requirementsspecification documentDuración: 06:00




Semana 4 Requirements validationDuración: 03:00






Semana 5 Design by contractDuración: 02:00






Semana 6 OO with EiffelDuración: 01:00


Follow-up & presentationsDuración: 01:00


Definition of an API based ondesign by contractDuración: 04:00




Eiffel puzzlesDuración: 02:00









GA_10AM_103000604_1S_2016-17 6





Definition of an API based ondesign by contractDuración: 04:00
















Semana 9 Follow-up & presentationsDuración: 01:00


Semana 10 Unit testingDuración: 02:00




Distributed developmentDuración: 09:00




Semana 11 Distributed softwaredevelopment challenguesDuración: 01:00




















Unit testingDuración: 05:00




Semana 14 Follow-up & presentationsDuración: 01:00


Unit testingDuración: 05:00




Semana 15 Wrap-up and retrospectiveDuración: 02:00


Assessment of papersDuración: 00:00




Semana 16






GA_10AM_103000604_1S_2016-17 7

Semana 17 Examen finalDuración: 01:00










GA_10AM_103000604_1S_2016-17 8





3 Creation of a requirementsspecification document



No 10% 5 / 10 CE14




No 5% 5 / 10 CE14, CG18




No 5% 5 / 10 CE14, CG18

6 Definition of an API based ondesign by contract



No 7.5% 5 / 10 CE14, CG18

6 Eiffel puzzles 02:00 Evaluacióncontinua


No 5% 5 / 10 CE14

7 Definition of an API based ondesign by contract



No 7.5% 5 / 10 CE14, CG18



No 5% 5 / 10 CE14



No 5% 5 / 10 CE14

10 Distributed development 09:00 Evaluacióncontinua


No 10% 5 / 10 CE13, CE14,CG18



No 10% 5 / 10 CE13, CE14,CG18



No 10% 5 / 10 CE13, CE14,CG18

13 Unit testing 05:00 Evaluacióncontinua


No 5% 5 / 10 CE14

14 Unit testing 05:00 Evaluacióncontinua


No 5% 5 / 10 CE14

15 Assessment of papers 00:00 Evaluacióncontinua


No 10% 5 / 10



No 100% 5 / 10 CE13, CE14,CG18


The assessment of assignments will depend on (1) presentation made by the students at the classroom and (2) the●

correctness of the results.The final grade will be calculated using a weighted average as described before●






GA_10AM_103000604_1S_2016-17 9



Course material Recursos web All required materials will be available at moodle



7.4.6 Management, Relationships and Communication in Work-ing Groups

7.4.7 Rigorous Software Development





GA_10AM_103000546_1S_2016-17


ASIGNATURARigorous software development







GA_10AM_103000546_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Rigorous software development




Carácter Optativa


Nombre en inglés Rigorous software development

Datos Generales

Créditos 4 Curso 1





Otros Requisitos





First-order logic, formal proofs, declarative programming, reasoning about properties of algorithms.

All students willing to take this course are encouraged to get in touch with one of the instructors prior to enrollment.






GA_10AM_103000546_1S_2016-17 2

Competencias

CG10 - Capacidad de pensamiento creativo con el objetivo de desarrollar enfoques y métodos nuevos y originales


RA65 - RA-AV-1 - Acquaintance with design requirements and implementation requirements.

RA70 - RA-AV-5 - Effective use of rigorous software development techniques.

RA68 - RA-AV-3 - Knowledge of languages for formal specification

RA69 - RA-AV-4 - Knowledge of techniques for formally proving code correctness.

RA66 - RA-AV-2 Acquaintance with various techniques for formal software development

RA67 - RA-AV-2 - Acquaintance with various techniques for formal software development






GA_10AM_103000546_1S_2016-17 3



Carro Liñares, Manuel D2304 [email protected] Please send an e-mail toensure an appointmentbefore going to theinstructor's office.

Mariño Carballo, Julio (Coordinador/a) D2308 [email protected] Please send an e-mail toensure an appointmentbefore going to theinstructor's office.







GA_10AM_103000546_1S_2016-17 4


Software is getting more and more complex and is becoming responsible for critical tasks.Therefore, any technology aimed at ensuring the reliability and quality of software will beincreasingly relevant.There are many ways to approach these goals. The declarative approach relies on languagesand logics with a solid mathematical foundation. This includes specificacion languages (VDM, Z,B, Event-B, OBJ, Alloy, ...), functional programming languages (Haskell, Erlang, ?-calculi?), logicprogramming languages (Prolog, CLP, ASP,?) among others.

Some basic knowledge of logic and functional and logic programming is assumed as aprerequisite.

Some goals of the course are:To motivate the use of technologies in software development under the●

correctness-by-construction paradigm.To study different families of languages aimed at easing the process of building correct●

software.To understand the differences between declarative and procedural languages and the impact●

of these aspects in software development.To identify the better niches for the industrial application of declarative / correctness by●

construction technologies.

Temario

1. Introduction

1.1. Overview, motivation, and challenges for rigorous SW development

1.2. Review of background: formal logic, proofs...

2. Correctness by Construction

2.1. Event-B: Theory and development methods.

2.2. Event-B: the Rodin tool

3. Verification.

3.1. Classical program verification

3.2. The Dafny tool

3.3. The Alloy tool

3.4. Property-based testing

4. Specifications

4.1. Algebraic specifications

4.2. The Maude algebraic specification language






GA_10AM_103000546_1S_2016-17 5






GA_10AM_103000546_1S_2016-17 6

Cronograma






Semana 1 Course introductionDuración: 02:00


Semana 2 Rigorous softwaredevelopment: a broadlandscapeDuración: 01:45


Exercises, questions, andanswersDuración: 00:15




Semana 3 Event-BDuración: 01:45






























Semana 8 Program VerificationDuración: 01:45











GA_10AM_103000546_1S_2016-17 7













Semana 11 Algebraic specificationsDuración: 01:45


















Semana 14 AlloyDuración: 01:45






Semana 15 Exercises and problemsDuración: 02:00


Semana 16 Project presentationDuración: 02:00




Semana 17 Project presentation/ExamDuración: 02:00










GA_10AM_103000546_1S_2016-17 8





2 Exercises, questions, andanswers



Sí 3.85% CG10




Sí 3.85% CG10




Sí 3.85% CG10




Sí 3.85% CG10




Sí 3.85% CG10




Sí 3.85% CG10




Sí 3.85% CG10




Sí 3.85% CG10




Sí 3.85% CG10




Sí 3.85% CG10




Sí 3.85% CG10




Sí 3.85% CG10




Sí 3.8% CG10

16 Project presentation 02:00 Evaluacióncontinua


Sí 50% CG10

17 Project presentation/Exam 02:00 Evaluación sóloprueba final


Sí 100% CG10


Depending of the number of students, the final grade will be obtained either from:

A suite of short, individual practical exercises periodically proposed which will be worth 50% of the final grade. The remaining●

50% will come from short presentations.Individual practical exercises, if the number of students is too high to allow for the extra sessions needed for the presentations.●

Exercises for each unit will have the same relative weight for the overall grade, although individual exercises in a given unit canhave different weights.






GA_10AM_103000546_1S_2016-17 9



Event B development environment Otros

Dafny Otros

Maude Otros

Alloy Otros

Modeling in Event-B: System and Software Engineering. Jean-RaymondAbrial. Cambridge University Press.

Bibliografía

http://wiki.event-b.org/ Bibliografía

The Dafny web page at Microsoft RiSE: http://www.rise4fun.com/Dafny Recursos web

All About Maude -- A High Performance Logical Framework. Clavel, M.,Durán, F., Eker, S., Lincoln, P., Martí-Oliet, N., Meseguer, J., Talcott, C.Lecture Notes in Computer Science, vol. 4350.

Bibliografía

Alloy: A Lightweight Object Modelling Notation. Daniel Jackson. ACMTransactions on Software Engineering and Methodology (TOSEM'02),volume 11, issue 2, pages 256-290.

Bibliografía

Seven Myths of Formal Methods. Anthony Hall. IEEE Software,September 1990

Bibliografía

Seven More Myths of Formal Methods. Jonathan P. Bowen, Michael G.Hinchey. IEEE Software, July 1995.

Bibliografía

First Steps in the Verified Software Grand Challenge. Cliff Jones, PeterO'Hearn, Jim Woodcock. IEEE Computer, April 2006.

Bibliografía

Otra Información

All students willing to take this course are encouraged to get in touch with one of the instructors prior to enrollment, in order toverify their background.



7.4.8 Software Engineering Economics





GA_10AM_103000547_1S_2016-17


ASIGNATURASoftware engineering economics







GA_10AM_103000547_1S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Software engineering economics




Carácter Optativa


Nombre en inglés Software engineering economics

Datos Generales

Créditos 3 Curso 1





Otros Requisitos











GA_10AM_103000547_1S_2016-17 2

Competencias

CG5 - Organización y planificación


RA58 - Development of a business case for a software project






GA_10AM_103000547_1S_2016-17 3



Amillo Gil, June (Coordinador/a) 1317 [email protected] L - 16:00 - 17:00

or By appointment







GA_10AM_103000547_1S_2016-17 4


Temario

1. The Time Value of Money

1.1. Compounding and discounting

1.2. Nominal and effective interest rates

1.3. Composite cash flows

1.4. Bond and stock valuation

2. Value based decision making

2.1. Project analysis and figures of merit

2.2. Net present value

2.3. Mutually exclusive alternatives

2.4. Equivalent annual value

2.5. IRR and incremental analysis

2.6. ROI and Benefit/Cost analysis

3. Generating a project cash flow

3.1. What to discount

3.2. Equity cash flow

3.3. Cash flows and inflation

3.4. Effects of Depreciation and Taxes

3.5. Free cash flow and the cost of capital

3.6. Review case study

4. Project Financing

4.1. Equity Financing

4.2. Debt and Equity Financing

4.3. Adjusted Present Value

4.4. The CAP Model and The Cost of Equity

4.5. Estimating the Cost of Equity

4.6. The Cost of Capital

5. Assessing Project Risk

5.1. Scenario Analysis

5.2. Sensitivity Analysis

5.3. Break-even Analysis






GA_10AM_103000547_1S_2016-17 5

6. Understanding Financial Statements

6.1. The Three Basic Financial Statements

6.2. Using Ratios to Make Business Decisions






GA_10AM_103000547_1S_2016-17 6

Cronograma




Semana Actividad Prensencial en Aula Actividad Prensencial en Laboratorio Otra Actividad Presencial Actividades Evaluación



Case studyDuración: 02:00

PL: Actividad del tipo Prácticas deLaboratorio













AssessmentDuración: 02:00

EP: Técnica del tipo Examen dePrácticas








































GA_10AM_103000547_1S_2016-17 7





























Semana 17







GA_10AM_103000547_1S_2016-17 8





4 Assessment 02:00 Evaluacióncontinua y sóloprueba final

EP: Técnica deltipo Examen dePrácticas

Sí 25% CG5



Sí 25% CG5



Sí 25% CG5



Sí 25% CG5


First assessment 25%second assessment 25%Final assessment 50%






GA_10AM_103000547_1S_2016-17 9



Tockey, Steve. Return on Software. Addison-Wesley, 2005. Bibliografía


Documents

MASTER UNIVERSITARIO EN INGENIER IA DEL SOFTWARE - …pegaso.ls.fi.upm.es/emse/documentos/curso1617/... · 2016. 7. 5. · Agile Software Development: Agile Practices and Agile Usability