MASTER UNIVERSITARIO EN INGENIER IA DEL SOFTWARE ...pegaso.ls.fi.upm.es/emse/documentos/curso1617/... · Software Project Management Ana M. Moreno C 4 1, 3 MODULE SUPPORT PROCESSES

MASTER UNIVERSITARIO EN INGENIERIADEL SOFTWARE - EUROPEAN MASTER IN

SOFTWARE ENGINEERING

Educational Planning Course 2016-17Second Semester

Computer Science and Engineering SchoolUniversidad Politecnica de Madrid

CONTENTS i

Contents

1 Pre-enrollment Dates 1

2 Calendar 2

3 Exam Calendar 4

4 Subject Coordinators 7

5 Subject Boards 8

6 Learning Guides 9

6.1 Software Development Module . . . . . . . . . . . . . . . . . 9

6.1.1 Software Architecture . . . . . . . . . . . . . . . . . . 9

6.1.2 Software Design . . . . . . . . . . . . . . . . . . . . . 21

6.2 Support Processes Module . . . . . . . . . . . . . . . . . . . . 31

6.2.1 Software Quality Management . . . . . . . . . . . . . 31

6.3 Advanced Software Engineering Aspects Module . . . . . . . 44

6.3.1 Agent Based Software Development . . . . . . . . . . 44

6.3.2 Experimental Software Engineering . . . . . . . . . . . 58

6.3.3 Fundamentals of Business Administration . . . . . . . 68

6.3.4 Interaction Design . . . . . . . . . . . . . . . . . . . . 78

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 212 8 9 10 11 12 13 14 16 5 6 7 8 9 10 11 3 4 5 6 7 8 913 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

March-17 April-17

May-17 June-17 July-17

January-17 February-17

EUROPEAN MASTER IN SOFTWARE ENGINEERING

COURSE 2016-17

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

Universidad Politécnica de Madrid

E.T.S. DE INGENIEROS INFORMÁTICOS

2 2 CALENDAR

2 Calendar

WednesdayMonday Tuesday Thursday Friday15:00

16:00

17:00

18:00

19:00

20:00

EMSE2016-2017·2ndSemester (FEB)

21:00

AgentBasedSoftwareDevelopmentRoom6202

Ricardo Imbert

InteractionDesignRoom6202

XavierFerré,Cristian Moral,ElenaVillalba

ExperimentalSoftwareEngineeringRoom6202

NataliaJuristo,Sira Vegas

InteractionDesignRoom6202

XavierFerré,Cristian Moral,ElenaVillalba

Software QualityManagementRoom6202

AngélicadeAntonio

SoftwareArchitectureRoom6202

JaimeRamírez AssessmentActivities

ExperimentalSoftwareEngineeringRoom6202

NataliaJuristo,Sira Vegas

Software DesignRoom6202

NelsonMedinilla

AgentBasedSoftwareDevelopmentRoom6202

Ricardo Imbert

MandatorySubjects(16weeks)

ElectiveSubjects(16weeks)ElectiveSubjects(week1to12)SpecialActivities(16weeks)

FundamentalsofBusinessAdministrationRoom6202

MartaOlea

3

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

43

EXAM

CALENDAR

3E

xam

Cale

nd

ar

2ndSemester(SpringTerm)

JUNE2017 MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY SUNDAY

12 13 14 15 16 17 18

ExperimentalSoftwareEngineering 15:00 Interaction

Design 15:00SoftwareQualityMan-agement 15:00

FundamentalsofBusinessAdministra-tion

15:00

19 20 21 22 23 24 25 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

63

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

4 Subject Coordinators

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

AnaMaríaMoreno

JoséA.Calvo-Manzano

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

JoséA.Calvo-Manzano

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 5 SUBJECT BOARDS

5 Subject Boards

9

6 Learning Guides

6.1 Software Development Module

6.1.1 Software Architecture

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_103000484_2S_2016-17

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

ASIGNATURASoftware architecture

CURSO ACADÉMICO - SEMESTRE2016-17 - Segundo semestre

10 6 LEARNING GUIDES





GA_10AM_103000484_2S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Software architecture

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 Segundo semestre

Carácter Obligatoria

Código UPM 103000484

Nombre en inglés Software architecture

Datos Generales

Créditos 4 Curso 1

Curso Académico 2016-17 Período de impartición Febrero-Junio

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

Object oriented design

6.1 Software Development Module 11





GA_10AM_103000484_2S_2016-17 2

Competencias

CE12 - Concebir y realizar el diseño de los sistemas software asegurando atributos relevantes de calidad.

Resultados de Aprendizaje

RA6 - Ability to document the software architecture

RA4 - To design the system according to the requirements, constraints, quality norms and organization goals.

RA5 - To apply the architectural concepts that are relevant in the architectural design






GA_10AM_103000484_2S_2016-17 3

ProfesoradoProfesorado

Nombre Despacho e-mail Tutorías

Ramirez Rodriguez, Jaime(Coordinador/a)

5112 [email protected] L - 11:00 - 13:00

M - 16:00 - 18:00

V - 11:00 - 13: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_103000484_2S_2016-17 4

Descripción de la Asignatura

The goal of the subject is to teach the basis of the software architectural design. For that purpose, it will be shown how thequality attribute requirements of the system can be satisfied by applying some tactics. In addition, architectural styles will beaddressed and their relationship with quality attributes will be explained. Then, some representative architectural patterns willbe explained showing how they can be reused to solve some design problems providing well proven solutions without the needof re-inventing the wheel. Throughout the course, application examples will be briefly described to illustrate the concepts.

Temario

1. Previous Concepts on Software Architecture

1.1. What is Software Architecture?

1.2. Architectural Views

1.3. Software Architecture in the Development Process

2. Defining a Software Architecture

2.1. Quality Attributes related to Software Architecture

2.2. Achieving Quality Attributes through Tactics

2.3. Architectural Styles

2.4. Architectural Patterns






GA_10AM_103000484_2S_2016-17 5

Cronograma

Horas totales: 108 horas Horas presenciales: 29 horas (27.9%)

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 PresentaciónDuración: 01:00

LM: Actividad del tipo LecciónMagistral

Previous concepts on SoftwareArchitectureDuración: 01:00


Semana 2 2.1 Quality attributes relatedto software architectureDuración: 01:00


Practical exercises on topicsthat are being explained inclassroomDuración: 00:45

TG: Técnica del tipo Trabajo en Grupo

Evaluación continua

Actividad presencial

Semana 3 2.2 Achieving qualityattributes through tacticsDuración: 01:00





Actividad no presencial





Semana 4 2.3 Architectural stylesDuración: 02:00

















GA_10AM_103000484_2S_2016-17 6









Semana 8 2.4 Architectural patternsDuración: 01:00


Brief presentation of theprojectDuración: 00:45






ProjectDuración: 10:00
















Semana 12 Oral presentation on theprojectDuración: 02:00

PG: Técnica del tipo Presentación enGrupo




















GA_10AM_103000484_2S_2016-17 7



ExamDuración: 01:00

EX: Técnica del tipo Examen Escrito



Semana 16

Semana 17 Final ExamDuración: 01:00


Evaluación sólo prueba final


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_103000484_2S_2016-17 8

Actividades de Evaluación

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

Presencial Peso Notamínima

Competenciasevaluadas

2 Practical exercises on topics thatare being explained in classroom

00:45 Evaluacióncontinua

TG: Técnica deltipo Trabajo enGrupo

Sí




No 5% CE12




Sí




No 10% CE12




Sí




No 10% CE12

8 Brief presentation of the project 00:45 Evaluacióncontinua


Sí

9 Project 10:00 Evaluacióncontinua


No 10% 5 / 10 CE12



No 10% 5 / 10 CE12



No 10% 5 / 10 CE12

12 Oral presentation on the project 02:00 Evaluacióncontinua

PG: Técnica deltipo Presentaciónen Grupo

Sí



No 10% 5 / 10 CE12



No 10% 5 / 10 CE12

15 Exam 01:00 Evaluacióncontinua

EX: Técnica deltipo ExamenEscrito

Sí 25% 4 / 10 CE12

17 Final Exam 01:00 Evaluación sóloprueba final


Sí 100% 4 / 10 CE12

Criterios de Evaluación

Along the semester, in order to pass the course, the student will have to do the following assignments:

Practical exercises: the student will have to do some practical exercises where he/she will have to apply the concepts,●

techniques and principles explained in the classroom.Final exam: the student will have to do a final exam where he/she will show that he/she has acquired the basic concepts●

explained in the classroom.Project: the student will have to propose a project and an architectural solution for it. This work will have to be reflected in a●

document. In addition, before delivering this document, the student will have to do an oral presentation in classroom wherethe preliminary results of his/her work will be summarized.






GA_10AM_103000484_2S_2016-17 9

The final grade (FG) will be calculated from the practical exercises grade (PEG), the exam grade (EG) and project grade (PG) bymeans of the following formula:

FG=0.25*PEG+0.25*EG+0.5*PG if PEG>=4 and EG>=4 and PG>=5

FG = 0 otherwise

Where all the grades take value between 0 and 10

When failed, in the extra exam period the final grade will be obtained from the grade of a research work or project.






GA_10AM_103000484_2S_2016-17 10

Recursos Didácticos

Descripción Tipo Observaciones

Moodle site Recursos web http://moodle.upm.es/titulaciones/oficiales/course/view.php?id=2835

Bass, L. et al. (2003) SoftwareArchitecture in Practice.Addison-Wesley, Boston, MA,second edition

Bibliografía

Buschmann, F. et al. (1996)Pattern-Oriented SoftwareArchitecture: A System ofPatterns, volume 1 de SoftwareDesign Patterns. John Wiley &Sons.

Bibliografía

Taylor, R. N. et al. (2009)Software Architecture:Foundations, Theory and Practice.John Wiley & Sons.

Bibliografía

Bachmann, F. et al. (2007)Modificability Tactics. Inf. Téc.CMU/SEI-2007-TR-002, SoftwareEngineering Institute - CarnegieMellon University, Pittsburg, PA,USA.

Bibliografía

Gorton I. (2006) EssentialSoftware Architecture.Springer-Verlag.

Bibliografía



6.1.2 Software Design





GA_10AM_103000483_2S_2016-17


ASIGNATURASoftware design







GA_10AM_103000483_2S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Software design






Nombre en inglés Software design

Datos Generales

Créditos 4 Curso 1





Otros Requisitos





Object Oriented Programming






GA_10AM_103000483_2S_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


CE4 - Aplicar los modelos de proceso de desarrollo a las características de un 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

CE6 - Diseñar las pruebas de los módulos y ayudar a diseñar las pruebas de integración e instalación. Realizar la integración delsistema, las pruebas de integración y la instalación.

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

CG11 - Integración del conocimiento a partir de disciplinas diferentes, así como el manejo de la complejidad

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)

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)

CG7 E - Especificación y realización de tareas informáticas complejas, poco definidas o no familiares


RA16 - The student will be able to evaluate any software system design.

RA14 - The student will be able to design a software system according to requirements, restrictions, quality standards, anddeveloper criteria






GA_10AM_103000483_2S_2016-17 3



Medinilla Martinez, Nelson(Coordinador/a)








GA_10AM_103000483_2S_2016-17 4


The course Software Design is aimed at enhancing human efficiency in software development. Therefore, the purpose of thiscourse is to develop the skills to design software systems such that meet the following conditions (set by Parnas): Managerial,Flexibility, Comprehension.These are the skills that will be evaluated in the course.The course is essentially practical; it relies on a small and intense theoretical core: Near Decomposable Systems, InformationHiding Principle and Bi-dimensional Complexity.

Difficulties (hard):These skill are creative, no algorithms or recipes for a design that meets the conditions set by Parnas.Very often we have entrenched ideas that hinder the acquisition of the necessary skills.

Temario

1. Software Engineering Two-dimensional Complexity

2. System Software Design Features

3. Object Oriented Review

4. Design and Dominion Patterns






GA_10AM_103000483_2S_2016-17 5

Cronograma






Semana 1 Software EngineeringTwo-dimensional ComplexityDuración: 02:00


Semana 2 Object Oriented ReviewDuración: 02:00


Semana 3 WorkshopDuración: 02:00

AC: Actividad del tipo AccionesCooperativas

Semana 4 System Software DesignFeaturesDuración: 02:00




Semana 6 Oral presentation of the firststage of software developmentsystem and associatedtechnical documentsDuración: 02:00






Semana 8 Design and Dominion PatternsDuración: 02:00











GA_10AM_103000483_2S_2016-17 6

Semana 11 Oral presentation of thesecond stage of softwaredevelopment system andassociated technicaldocumentsDuración: 02:00












Semana 16 Oral presentation of the thirdstage of software developmentsystem and associatedtechnical documentsDuración: 02:00




Evaluating relevantcontributionsDuración: 00:00

OT: Otras técnicas evaluativas



Semana 17 Final testDuración: 02:00

TI: Técnica del tipo Trabajo Individual









GA_10AM_103000483_2S_2016-17 7





6 Oral presentation of the firststage of software developmentsystem and associated technicaldocuments



Sí 10% 5 / 10 CE1, CE4, CE5,CE6, CE12,CG7 E, CG10,CG11, CG3,CG4

11 Oral presentation of the secondstage of software developmentsystem and associated technicaldocuments




16 Oral presentation of the thirdstage of software developmentsystem and associated technicaldocuments




16 Evaluating relevant contributions 00:00 Evaluacióncontinua

OT: Otras técnicasevaluativas

Sí 5%

17 Final test 02:00 Evaluación sóloprueba final

TI: Técnica deltipo TrabajoIndividual

Sí 100% 5 / 10 CE4, CE5, CE12,CG7 E, CG10,CG11


The course applies a continuous evaluation through three evaluation activities around the development of a software system.Evaluates work as a team.The three activities evaluated oral presentations and technical documentation of the three stages of system development. Theweights of each activity will increase gradually.Reserves 5% of the assessment to consider relevant contributions, particularly associated with the ability of independentlearning.All assessment activities are mandatory.Each assessment activity includes the full set of competencies referred, given the integrative nature (holistic) of these activities.In accordance with established standards you may opt for an evaluation only for final test. In this case they can not assess theskills related to social issues.






GA_10AM_103000483_2S_2016-17 8



Moodle Bibliografía It contains or addresses the fundamental literature


6.2 Support Processes Module 31

6.2 Support Processes Module

6.2.1 Software Quality Management





GA_10AM_103000487_2S_2016-17


ASIGNATURASoftware quality management







GA_10AM_103000487_2S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Software quality management






Nombre en inglés Software quality management

Datos Generales

Créditos 4 Curso 1





Otros Requisitos





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






GA_10AM_103000487_2S_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

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

CE11 - Identificar, controlar, informar y auditar la configuración de un sistema y sus cambios


CG12 - Comprensión amplia de las técnicas y métodos aplicables en una especialización concreta, así como de sus límites

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

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)

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)


RA42 - Comprende la interrelación entre calidad del producto y calidad del proceso

RA43 - Conoce y aplica técnicas de control de calidad de productos y procesos

RA40 - Es capaz de identificar y establecer las prácticas necesarias para gestionar la configuración de un sistema software

RA7 - Knows and applies quality models to identify and specify the quality attributes a software system must satisfy

RA10 - Understands the mission of a quality system and knows the applicable standards and norms

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

RA9 - Is able to identify and determine the practices needed to manage a software system configuration

RA11 - Understands the interrelation between product quality and process quality

RA12 - Knows and applies product and process quality control techniques

RA38 - Conoce y aplica modelos de calidad para la identificación y especificación de los atributos de calidad a satisfacer por unsistema software

RA41 - Comprende la misión de un sistema de calidad y conoce los estándares y normas aplicables

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






GA_10AM_103000487_2S_2016-17 3



Antonio Jimenez, Angelica De(Coordinador/a)


V - 11:00 - 14:00

Previous appointment isrecommended







GA_10AM_103000487_2S_2016-17 4


The goal of the Software Quality Management subject is to provide the student with a broad overview about the differentaspects involved in the development of software with a required level of quality. The following questions are addressed:

- What is the meaning of quality in the software domain?

- How can we define precisely the quality required from a software system?

- How can we measure the quality of a software system?

- How can we measure the quality of a software process?

- How can we control quality during the development of a software system?

- How can we control the configuration and evolution of a software system?

- How can we build quality into the software being developed?

- How can we manage software quality from an organizational point of view?

- How can we evaluate the cost and benefits of quality?

- How can we make factual-based decisions about the quality of a software system?

Temario

1. Introduction to Software Quality

1.1. Software Quality Definition

1.2. Software Quality Models

1.3. Usage of a Quality Model

1.4. Defects and Defect Density

2. Software Quality Control Activities

2.1. Static Controls

2.2. Dynamic Controls

3. Quality Metrics

3.1. Product and Process Quality Metrics

3.2. Comparison of Quality Control Activities

4. Quality Management and Quality Systems

4.1. Introduction to Quality Management and related standards and norms

4.2. The Quality System and the Quality Manual

4.3. Quality Management Tools

4.4. The Cost of Quality






GA_10AM_103000487_2S_2016-17 5

5. Software Quality Assurance Activities

5.1. Introduction to Quality Assurance

5.2. Quality Construction

5.3. Quality Assurance Planning

6. Software Configuration Management

6.1. Basic Concepts of Software Configuration Management

6.2. Configuration Identification

6.3. Configuration Change Control

6.4. Configuration Status Accounting

6.5. Configuration Audits

6.6. Configuration Management Plan






GA_10AM_103000487_2S_2016-17 6

Cronograma




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

Semana 1 Chapter 1.1. Software QualityDefinitionDuración: 02:00


Reading 1 testDuración: 03:00

ET: Técnica del tipo PruebaTelemática



Semana 2 Chapter 1.2 Software QualityModelsDuración: 02:00


Semana 3 Chapter 1.2 Software QualityModels Chapter 1.3 Usage of aQuality ModelDuración: 02:00


Individual exercise on qualityattributesDuración: 04:00




Semana 4 Chapter 1.4 Defects andDefect DensityDuración: 02:00






Semana 5 Chapter 2.1 Static ControlsDuración: 02:00


Group work on defect trackingtoolsDuración: 03:00


Report on defect tracking toolsDuración: 03:00




Semana 6 Exercise on inspectionsDuración: 02:00

PL: Actividad del tipo Prácticas deLaboratorio

Semana 7 Exercise on walkthroughsDuración: 02:00


Report about exercise oninspectionsDuración: 02:00




Semana 8 Chapter 2.2 Dynamic ControlsDuración: 02:00


Report about exercise onwalkthroughsDuración: 02:00









GA_10AM_103000487_2S_2016-17 7

Semana 9 Chapter 2.2 Dynamic ControlsDuración: 02:00






Semana 10 Chapter 3.1 Product andProcess Quality MetricsChapter 3.2 Comparison ofQuality Control ActivitiesDuración: 01:00


First Partial examDuración: 01:00




Semana 11 Chapter 4.1 Introduction toQuality Management andrelated standards and normsChapter 4.2 The QualitySystem and the QualityManualDuración: 02:00


Semana 12 Chapter 4.3 QualityManagement Tools Chapter 4.4The Cost of QualityDuración: 02:00






Semana 13 Chapter 5.1 Introduction toQuality Assurance Chapter 5.2Quality Construction s Chapter5.3 Quality Assurance PlanningDuración: 01:00


Chapter 6.1 Basic Concepts ofSoftware ConfigurationManagement Chapter 6.2Configuration IdentificationDuración: 01:00


Group work on qualitymanagement toolsDuración: 03:00


Semana 14 Group work on qualitymanagement toolsDuración: 03:00


Presentation of group work onquality management toolsDuración: 02:00




Semana 15 Chapter 6.3 ConfigurationChange Control Chapter 6.4Configuration State ReportsChapter 6.5 ConfigurationAudits Chapter 6.6Configuration ManagementPlanDuración: 02:00






Semana 16






GA_10AM_103000487_2S_2016-17 8

Semana 17 Second partial examDuración: 02:00




Final examDuración: 02:00










GA_10AM_103000487_2S_2016-17 9





1 Reading 1 test 03:00 Evaluacióncontinua

ET: Técnica deltipo PruebaTelemática

No 3% CG12, CG13,CG4

3 Individual exercise on qualityattributes



No 7% CE12, CG4



No 3% CG12, CG13,CG4

5 Report on defect tracking tools 03:00 Evaluacióncontinua


Sí 10% CE11, CG12,CG3, CG4

7 Report about exercise oninspections



Sí 10% CE10, CG3

8 Report about exercise onwalkthroughs



Sí 8% CE10, CG3



No 3% CE1, CG12,CG13, CG4

10 First Partial exam 01:00 Evaluacióncontinua


Sí 20% 4 / 10 CE1, CE10,CE12



No 3% CE1, CE10,CG12, CG13,CG4

14 Presentation of group work onquality management tools



Sí 10% CE1, CE12,CG13, CG3,CG4



No 3% CE10, CG12,CG13, CG4

17 Second partial exam 02:00 Evaluacióncontinua


Sí 20% 4 / 10 CE1, CE10,CE11, CG12

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


Sí 100% 5 / 10 CE1, CE10,CE11, CE12,CG12, CG13,CG3, CG4


The subject is marked following continuous assessment.

The student passes the subject only if 5 or more points on 10 are obtained at the end of the course, regarding the followingcriteria:

FINAL GRADE = 45% Individual and group exercises in the classroom and Moodle + 15% Reading tests in Moodle+ 40% Exams

The maximum grade for each of these components and the minimum mark needed to compensate non-passed parts areindicated in the following table.






GA_10AM_103000487_2S_2016-17 10

MAXIMUMGRADE(andcorrespondenceover the finalgrade)

MINIMUMGRADE TOCOMPENSATENON-PASSEDPARTS(andcorrespondenceover the finalgrade)

Individual andgroupexercises inthe classroomand Moodle(45%)

10 (4,5) -

Reading tests(15%)

10 (1,5) -

Exams (40%) 10 (4,0) 4 (1,6)

Studentparticipation(10%)

10 (1,0) -

When failed, the exams can be repeated in the extra exam period, using the new marks together to the ones obtained inindividual and group exercises and student participation in the previous period to calculate the final grade of the subject.






GA_10AM_103000487_2S_2016-17 11



Schulmeyer, 2007 Bibliografía Gordon Schulmeyer, G. (2007) Handbook of Software QualityAssurance, Artech House Publishers, 4th ed.

Fagan, 1976 Bibliografía M.E. Fagan, Design and Code Inspections to Reduce Errors in ProgramDevelopment, IBM Systems Journal, Vol. 15, Nº 3, pp. 182-210, 1976

Galin, 2003 Bibliografía D. Galin (2003) Software Quality Assurance: From Theory toImplementation, Addison-Wesley

McCall, 1977 Bibliografía J.A. McCall, P.K. Richards,.G.F. Walters, Factors in Software Quality,RADC-TR-77-369, Rome Air Development Center, United States AirForce, 1977

Cianfrani, 2009 Bibliografía C.A. Cianfrani, J.J. Tsiakals, J.E. West (2009) ISO 9001:2008 Explained,ASQ Quality Press

ISO/IEC 9126-1:2001 Bibliografía ISO/IEC 9126-1:2001, Software engineering -- Product quality -- Part 1:Quality model

ISO/IEC TR 9126-2:2003 Bibliografía ISO/IEC TR 9126-2:2003, Software engineering -- Product quality --Part 2: External metrics

ISO/IEC TR 9126-3:2003 Bibliografía ISO/IEC TR 9126-3:2003, Software engineering -- Product quality --Part 3: Internal metrics

ISO/IEC TR 9126-4:2004 Bibliografía ISO/IEC TR 9126-4:2004, Software engineering -- Product quality --Part 4: Quality in use metrics

IEEE 983-86 Bibliografía IEEE Guide for Software Quality Assurance Planning, ANSI/IEEE std.983-1986, IEEE Computer Society, Software Engineering TechnicalCommittee, Software Engineering Standards Subcommittee, 1986

IEEE 1028-2008 Bibliografía IEEE Standard for Software Reviews and Audits, ANSI/IEEE IEEE std.1028-2008, IEEE Computer Society, Software Engineering TechnicalCommittee, Software Engineering Standards Subcommittee, 2008

The how and why of auditing Recursos web http://videos.asq.org/the-how-and-why-of-auditing

Guidelines for the Application ofISO 9001:2000 to ComputerSoftware

Bibliografía IEEE Guide Adoption of ISO/IEC 90003:2004 Software Engineering-Guidelines for the Application of ISO 9001:2000 to ComputerSoftware

Subject web site Recursos web https://moodle.upm.es/titulaciones/oficiales/course/view.php?id=2999



6.3 Advanced Software Engineering Aspects Module

6.3.1 Agent Based Software Development





GA_10AM_103000538_2S_2016-17


ASIGNATURAAgent-based software development


6.3 Advanced Software Engineering Aspects Module 45





GA_10AM_103000538_2S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Agent-based software development




Carácter Optativa


Nombre en inglés Agent-based software development

Datos Generales

Créditos 6 Curso 1





Otros Requisitos











GA_10AM_103000538_2S_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

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.


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

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

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






GA_10AM_103000538_2S_2016-17 3



Imbert Paredes, Ricardo(Coordinador/a)

5112 [email protected] M - 15:00 - 18:00

X - 15:00 - 18:00







GA_10AM_103000538_2S_2016-17 4


The continuous search for more powerful and of a higher level new abstraction mechanisms has lead nowadays towards a newdevelopment paradigm, based on software agents. This approach, which has been so many times referred as the nal solutionfor all the previously unaffordable problems, far from being a "silver bullet", must be considered as another softwaredevelopment paradigm and, as such, sub ject to the Software Engineering discipline.

This subjects will introduce the students into this new paradigm, settling the basic concepts of the technology, offering them awide perspective of the current Software Engineering efforts in this area, always from a practical and applied perspective.

Temario

1. Introduction to agents

1.1. General concepts

1.2. Agent architectures

1.3. Social nature of agents

2. Agent oriented software engineering

2.1. Pitfalls of agent oriented development

2.2. Standards

2.3. Agent communication languages

2.4. Development frameworks

2.5. Methodologies

2.6. Development notations

3. Agent oriented analysis

3.1. Concepts for building agents

3.2. Analysis according to different methodologies

3.3. Goal identification

3.4. Role modelling

3.5. Interface description

4. Agent oriented architectural design

4.1. Architectural design according to different methodologies

4.2. Agent type decision

4.3. System architecture

4.4. Interaction model






GA_10AM_103000538_2S_2016-17 5

5. Agent oriented detailed design (part I)

5.1. Detailed design according to different methodologies

5.2. Detailed protocols

5.3. Process specifications

5.4. Ontology design

6. Agent implementation

6.1. Introduction to an agent oriented development framework

6.2. Administrative tools

6.3. Execution of an agent

6.4. Agent behaviors

6.5. Agent messaging

7. Agent oriented detailed design (part II)

7.1. Ontology construction

7.2. Specification of ACL messages

7.3. Packaging protocols

7.4. Agent detailed desing

8. Development process

8.1. Development scenario

8.2. Development strategy

8.3. Development team roles

8.4. Project startup stage

8.5. Project iteration stage






GA_10AM_103000538_2S_2016-17 6

Cronograma






Semana 1 1. Introduction to agentsDuración: 02:00


2 Agent oriented softwareengineeringDuración: 00:15


Exercise about risks on agentbased software engineeringDuración: 00:45


Evaluación continua y sólo pruebafinal


Semana 2 2 Agent oriented softwareengineeringDuración: 00:30


3. Agent oriented analysisDuración: 01:00


3. Agent oriented analysisDuración: 01:30

PR: Actividad del tipo Clase deProblemas

Semana 3 8. Development processDuración: 00:30


Meeting in the classroom forthe second practicalassignmentDuración: 00:30


Presentation in the classroomof the first practicalassignmentDuración: 02:00

PI: Técnica del tipo PresentaciónIndividual



Semana 4 4 Agent oriented architecturaldesignDuración: 01:15




Project coordinationDuración: 03:00

OT: Otras actividades formativas

Exercise about systemstopologyDuración: 00:45




Semana 5 Meeting in the classroom forthe second practicalassignmentDuración: 01:00









GA_10AM_103000538_2S_2016-17 7

Semana 6 5. Agent oriented detaileddesign (part I)Duración: 02:30


Exercise about agentcommunication protocolsDuración: 00:30




Semana 7 6. Agent implementationDuración: 01:00


7. Agent oriented detaileddesign (part II)Duración: 01:00


8. Development processDuración: 00:20






Semana 8 Integration test meeting in theclassroomDuración: 02:00





















GA_10AM_103000538_2S_2016-17 8




























GA_10AM_103000538_2S_2016-17 9

Semana 16 Presentation of the secondpractical assignment in theclassroomDuración: 02:00




Exercise about agent baseddevelopmentDuración: 01:00




Semana 17 Exercise about comparison ofagent based methodologiesDuración: 00:00




Student implication andparticipationDuración: 00:00










GA_10AM_103000538_2S_2016-17 10





1 Exercise about risks on agentbased software engineering

00:45 Evaluacióncontinua y sóloprueba final


Sí 4% CE14

3 Presentation in the classroom ofthe first practical assignment


PI: Técnica deltipo PresentaciónIndividual

Sí 15% 3 / 10 CE13, CE14

4 Exercise about systems topology 00:45 Evaluacióncontinua y sóloprueba final


Sí 4% CE13

6 Exercise about agentcommunication protocols



Sí 3% CE13

16 Presentation of the secondpractical assignment in theclassroom



Sí 60% 4 / 10 CE13, CE14

16 Exercise about agent baseddevelopment



Sí 4% CE13

17 Exercise about comparison ofagent based methodologies

00:00 Evaluación sóloprueba final


Sí 14% CE13, CE14

17 Student implication andparticipation



No 10% CE13


The subject is marked following continuous assessment.

The student passes the subject only if 5 or more points on 10 are obtained at the end of the course, regarding the followingcriteria:

FINAL GRADE = 3% Individual exercises in the classroom + 12% Group exercises in the classroom + 15% Firstpractical assignment + 60% Second practical assignment + 10% Student participation

The final grade will be obtained from five components: (1) individual exercises and (2) group exercises performed in theclassroom; (3) a first practical assignment consisting in a brief document and a classroom presentation about applications ofagents (proposed by the professor); (4) a second practical assignment about a group development of a multiagent system, withweekly classroom meetings and weekly software integration group activities, also in the classroom; and (5) participation andimplication of the student in the subject.

The maximum grade for each of these components and the minimum mark needed to compensate non-passed parts areindicated in the following table.

MAXIMUMGRADE(andcorrespondenceover the finalgrade)

MINIMUMGRADE TOCOMPENSATENON-PASSEDPARTS(andcorrespondenceover the finalgrade)

Individualexercises in theclassroom (3%)

10 (0,3) -






GA_10AM_103000538_2S_2016-17 11

Groupexercises in theclassroom (12%)

10 (1,2) -

First practicalassignment(15%)

10 (1,5) 3 (0,45)

Secondpracticalassignment(60%)

10 (6) 4 (2,4)

Studentparticipation(10%)

10 (1) -

When failed, first and second practical assignment could be repeated in the extra exam period, using the new marks together tothe ones obtained in individual and group exercises in the classroom and student participation in the previous period tocalculate the final grade of the subject.






GA_10AM_103000538_2S_2016-17 12



de Antonio, A. and Imbert, R. (2005) Combining RequirementsEngineering and Agents. In A. Silva and J. L. Maté (eds.) RequirementsEngineering for Sociotechnical Systems, pp. 68-83. Idea GroupPublishing, Hersey, PA, USA.

Bibliografía Agent oriented analysis

Bellifemine, F., Caire, G. and Greenwood, D. (2007) DevelopingMulti-Agent Systems with JADE. John Wiley & Sons Ltd, England.

Bibliografía Agent implementation

Bratman, M. E., Israel, D. and Pollack, M. (1988) Plans andResource-Bounded Practical Reasoning. Computational Intelligence,4(4): pp. 349-355.

Bibliografía Introduction to agents:concepts

Brooks, R. A. (1991) Intelligence without Representation. ArtificialIntelligence, 47: p. 139-159.

Bibliografía Introduction to agents:reactive architectures

Franklin, S. and Graesser, A. (1996) Is It an Agent, or Just a Program?:A Taxonomy for Autonomous Agents. In Intelligent Agents III. AgentTheories, Architectures and Languages (ATAL-96), vol. 1193.Springer-Verlag, Berlin, Germany.

Bibliografía Introduction to agents:definition

Jennings, N. R., Sycara, K. and Wooldridge, M. (1998) A Roadmap ofAgent Research and Development. Journal of Autonomous Agents andMulti-Agent Systems, 1(1): pp. 7-38.

Bibliografía Introduction to agents:general view

Müller, H. J. (1997) Towards Agent Systems Engineering. Data &Knowledge Engineering, 23: pp. 217?245.

Bibliografía Architectureconceptualization anddesign

Padgham, L. and Winikoff, M. (2004) Developing Intelligent AgentSystems. John Wiley & Sons Ltd, England.

Bibliografía Agent orienteddevelopment

Rao, A. S. and Georgeff, M. P. (1995) BDI Agents: From Theory toPractice. In V. Lesser (ed.), Proceedings of the First InternationalConference on Multi-Agent Systems, ICMAS-95, pp. 312-319. MIT Press,San Francisco.

Bibliografía Introduction to agents:BDI

Shoham, Y. and Leyton-Brown, K. (2009) Multiagent Systems.Algoritmic, Game-Theoretic, and Logical Foundations. CambridgeUniversity Press, USA.

Bibliografía Design of multiagentsystems

Sterling, L.S. and Taveter, K. (2009) The Art of Agent-OrientedModeling.The MIT Press, Cambridge, Massachusetts, USA.

Bibliografía Modeling of multiagentsystems

Sycara, K. (1998) Multiagent Systems. AI Magazine, 19(2): pp. 79-92. Bibliografía Social nature of agents

Wooldridge, M. (2002) An Introduction to MultiAgent Systems. JohnWiley & Sons Ltd. Chichester, England.

Bibliografía Introduction to agents:general view

Wooldridge, M., Jennings, N. R., Kinny, D. (2000) The GaiaMethodology For Agent-Oriented Analysis And Design. AutonomousAgents and Multi-Agent Systems, 3(3), pp. 285-312. Kluwer Academicpublishers.

Bibliografía Agent orientedmethodology: Gaia

Zambonelli, F., Jennings, N. R. and Wooldridge, M. (2003) DevelopingMultiagent Systems: The Gaia Methodology. ACM Transactions onSoftware Engineering and Methodology, 12(3): pp. 317-370.

Bibliografía Agent orientedmethodology: Gaia

http://moodle.upm.es/titulaciones/oficiales/course/view.php?id=1054 Recursos web Subject Moodle site

Room 6202 Equipamiento Lecture and group workroom



6.3.2 Experimental Software Engineering





GA_10AM_103000542_2S_2016-17


ASIGNATURAExperimental software engineering







GA_10AM_103000542_2S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Experimental software engineering




Carácter Optativa


Nombre en inglés Experimental software engineering

Datos Generales

Créditos 6 Curso 1





Otros Requisitos





Basic knowledge of statistics.






GA_10AM_103000542_2S_2016-17 2

Competencias




RA13 - Given a particular software engineering field, the student will be able to design and evaluate the most adequateapproach to solve some of the related problems, highlighting the technical difficulties and limits of application.






GA_10AM_103000542_2S_2016-17 3



Juristo Juzgado, Natalia D-5104 [email protected]

Vegas Hernandez, Sira (Coordinador/a) D-5105 [email protected] M - 14:00 - 17:00

J - 12:00 - 15:00







GA_10AM_103000542_2S_2016-17 4


Temario

1. Introduction to Experimental Software Engineering

1.1. Basics of experimentalism

1.2. The scientific method

1.3. Scientific rules: cause-effect relationships

1.4. Scientific immaturity of software engineering

2. Laboratory and Experiment

2.1. The concept of laboratory

2.2. The concept of experiment

2.3. A lab for software engineering

2.4. An experiment for software engineering

3. Elements of an Experiment

3.1. Response variables

3.2. Factors and levels

3.3. Types of empirical studies

4. Designing Experiments

4.1. Types of variables

4.2. Types of control

4.3. Validity

5. Data Analysis

5.1. Basics of inferential statistics

5.2. Parametric tests for independent samples

5.3. Parametric tests for related samples

5.4. Non parametric tests






GA_10AM_103000542_2S_2016-17 5

Cronograma




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

Semana 1 Lecture: Chapter 1Duración: 04:00




Problem-solving activity:Chapter 3Duración: 02:00






Lecture: Chapter 5Duración: 02:00






Semana 5 Brainstorming and groupdiscussion of assignment 1Duración: 02:00








Semana 7



Semana 9 Presentation of assignments1-3Duración: 04:00









GA_10AM_103000542_2S_2016-17 6





Semana 12 Presentation of assignment 4Duración: 04:00




Semana 13

Semana 14

Semana 15

Semana 16

Semana 17 Examen finalDuración: 04:00










GA_10AM_103000542_2S_2016-17 7





9 Presentation of assignments 1-3 04:00 Evaluacióncontinua


Sí 50% 5 / 10 CE13, CE14

12 Presentation of assignment 4 04:00 Evaluacióncontinua


Sí 50% 5 / 10 CE13, CE14

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


Sí 100% 5 / 10 CE13, CE14


Students will be evaluated using the assignments only. No examination will be made.●

The assessment of assignments will depend on (1) presentation made by the students and (2) the correctness of the results.●

The final grade will be calculated using a weighted average as described before.●






GA_10AM_103000542_2S_2016-17 8



Natalia Juristo, Ana Moreno. Basics of software engineeringexperimentation. Kluwer 2001

Bibliografía

Claes Wohlin et al. Experimentation in software engineering: anintroduction. Kluwer 2000.

Bibliografía

Course Moodle site Recursos web www.moodle.upm.es

Laboratory Equipamiento TBD

Room Equipamiento MUIS room



6.3.3 Fundamentals of Business Administration





GA_10AM_103000680_2S_2016-17


ASIGNATURAFundamentals of business administration







GA_10AM_103000680_2S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Fundamentals of business administration




Carácter Optativa


Nombre en inglés Fundamentals of business administration

Datos Generales

Créditos 4 Curso 1


Idioma de impartición Castellano Otros idiomas de impartición



Otros Requisitos











GA_10AM_103000680_2S_2016-17 2

Competencias




RA77 - Understands basic business principles






GA_10AM_103000680_2S_2016-17 3



Olea De Cardenas, Marta(Coordinador/a)

4203(ETSISI)

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

X - 10:00 - 13:00

Tutorías por email todos losdías


Profesorado Externo

Nombre e-mail Centro de procedencia

Olea De Cárdenas, Marta [email protected] ETSISI






GA_10AM_103000680_2S_2016-17 4


The course introduces the student to the contemporary business world, the management of people in organizations, theprinciples of marketing, managing information and financial issues.

The primary objective is to give the student an understanding of basic business principles.

Temario

1. The world business environment

1.1. Economic basics

1.2. Microeconomics: Supply and Demand

1.3. Macroeconomics: The Global Context of Business

1.4. Understanding Business Ethics and Social Responsability

2. Entrepreneurship

3. The Management Process

3.1. Objectives

3.2. Internal and External Analysis: SWOT

4. Organizing the Business

5. Operations Management

6. Human Resource Management

6.1. Employee Behavior and Motivation

6.2. Leadership

6.3. Labor Relations

7. Marketing

8. Accounting Information

9. Finance

9.1. Financial Decisions

9.2. Investment Decisions: Net Present Value






GA_10AM_103000680_2S_2016-17 5

Cronograma



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



Semana 1 Presentation.Duración: 01:00


Setting groups for work.Creativity tools to think abouta new company creation.Duración: 01:00


Semana 2 1. The World BusinessEnvironmentDuración: 02:00


Semana 3 1. The World BusinessEnvironmentDuración: 02:00


Semana 4 2. EntrepreneurshipDuración: 02:00


Semana 5 3. The Management ProcessDuración: 02:00


Semana 6 Writing down the first draft ofthe strategic plan. And SWOT.Duración: 02:00


Semana 7 4. Organizing the BusinessDuración: 02:00


Semana 8 5. Operations ManagementDuración: 02:00


Semana 9 5. Operations ManagementDuración: 02:00


Semana 10 6. Human ResourcesDuración: 02:00


Semana 11 Writing down the first draft ofthe organization plan andresources requirements.Duración: 02:00







GA_10AM_103000680_2S_2016-17 6

Semana 12 7. MarketingDuración: 02:00


Semana 13 Writing down the first draft ofthe marketing planDuración: 02:00


Semana 14 8. Accounting informationDuración: 02:00


Semana 15 9. FinanceDuración: 02:00


Semana 16 Writing down the first draft ofthe financial plan and resultsDuración: 02:00


Semana 17 Final document.Duración: 00:00




Final PresentationDuración: 02:00










GA_10AM_103000680_2S_2016-17 7





17 Final document. 00:00 Evaluacióncontinua y sóloprueba final


No 60% 5 / 10 CE14

17 Final Presentation 02:00 Evaluacióncontinua y sóloprueba final


Sí 30% CE13, CE14


Students will complete a group project. This project is a written plan about the creation of a new company. Every week, we willopen the document in the computer and will try to add new items to the plan. A final presentation to the group is compulsory.

The written project will be printed. The grading scale to evaluate it will be from 0 to 10 and the grade will be common for thewhole group.

The oral presentation will be in groups, although it will be evaluated individually.

There will be also a 10% added to the final grade to those who actively participate in class.






GA_10AM_103000680_2S_2016-17 8



Ebert and Griffin (2016): Business Essentials. Prentice Hall Bibliografía Handbook

Samuelson and Nordhaus (2009): Economics. McGraw Hill. Bibliografía 1. The World Business Environment

Friedlob and Plewa (2000): Financial and BusinessStatements. Barrons.

Bibliografía 8. Accounting Information9. Finance

Johnson et al. (2014): Exploring Strategy: Text and Cases.Pearson

Bibliografía 3. The management process

Schroeder et al (2010): Operations Management:contemporary concepts and cases. McGraw Hill

Bibliografía 5. Operations Management



6.3.4 Interaction Design





GA_10AM_103000543_2S_2016-17


ASIGNATURAInteraction design







GA_10AM_103000543_2S_2016-17 1

Datos Descriptivos

Nombre de la Asignatura Interaction design




Carácter Optativa


Nombre en inglés Interaction design

Datos Generales

Créditos 6 Curso 1





Otros Requisitos





Basic knowledge on Human-Centered Design and the Human-Computer Interaction discipline






GA_10AM_103000543_2S_2016-17 2

Competencias




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.

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.






GA_10AM_103000543_2S_2016-17 3



Villalba Mora, Elena 5110 [email protected] L - 15:00 - 18:00

X - 15:00 - 18:00

Ferre Grau, Xavier (Coordinador/a) 5112 [email protected] L - 12:00 - 14:00

L - 15:30 - 17:30

J - 10:00 - 12:00

It is advisable to ask for atutoring meeting in advance.

Moral Martos, Cristian 5110 [email protected] L - 12:00 - 14:00

L - 15:00 - 19:00


Profesorado Externo

Nombre e-mail Centro de procedencia

Sanchez Sanchez, Alberto [email protected] Centro de Tecnología Biomédica






GA_10AM_103000543_2S_2016-17 4


The course addresses the topic of how to design the interactive part of a software system as part of the overall softwaredevelopment process to achieve a good level of usability and User eXperience (UX). Some knowledge on the Human-ComputerInteraction field and User-Centered approach to software development is a requirement for the course. Advanced interactiondesign topics will be discussed in the classroom, giving special attention to novel interactive systems like mobile applications.The students will extend their knowledge on each topic carrying out information research and highlighting the aspects of higherinterest through an individual blog. The blog will be updated weekly with reflections on each week lectures topic. Teamassignments will consist on choosing and applying the most appropriate HCI methods for a case study. Each team will becomposed of 3 students.

The main objective of the course is for the student to be able to identify what HCI methods can offer in a software developmenteffort, and to develop criteria to choose the most appropriate HCI methods for a given project/organization.

Temario

1. Interaction design as part of the software development process

1.1. Interaction design, usability, HCI and User-Centered Design (UCD)

1.2. UCD process characteristics

1.3. Cost-justifying usability

2. Specification of the context of use

3. Envisioning design

3.1. Design

3.2. Detailed interaction design

3.3. Visual design

4. Usability requirements

5. A broadened scope for usability

6. Prototyping

7. Usability and UX evaluation

7.1. Usability evaluation

7.2. Interaction design guidelines

8. Specific interaction paradigms

8.1. Mobile apps

8.2. Interaction in 3D environments

8.3. e-Health systems

9. Internationalization

10. Integration of usability into the software development process






GA_10AM_103000543_2S_2016-17 5

Cronograma






Semana 1 Theory classes: Ch. 1Duración: 03:00


Participation showing criticalability in the classroom or inthe virtual forumDuración: 00:00






Team tutoringDuración: 02:00


Blog entryDuración: 00:00





































GA_10AM_103000543_2S_2016-17 6

























Semana 7 Team tutoringDuración: 04:00






Team presentationDuración: 03:00

























GA_10AM_103000543_2S_2016-17 7



























Semana 11 Theory classes: Ch. 6.Duración: 03:00

































GA_10AM_103000543_2S_2016-17 8

























Semana 17 Final assignmentDuración: 00:00




ExamDuración: 00:00










GA_10AM_103000543_2S_2016-17 9





1 Participation showing criticalability in the classroom or in thevirtual forum



No .63%

2 Blog entry 00:00 Evaluacióncontinua


No 3%




No .63%



No 3%




No .63%



No 3%




No .62%



No 3%




No .63%



No 3%




No .63%



No 3%

7 Team presentation 03:00 Evaluacióncontinua y sóloprueba final


Sí 15%




No .63%



No 3%




No .63%



No 3%




No .63%



No 3%



Sí 15%




No .62%






GA_10AM_103000543_2S_2016-17 10






No 3%




No .62%




No .62%




No .62%




No .62%



Sí 15%




No .62%




No .62%

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


No 15% CE13, CE14

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


Sí 40% CE13, CE14


The work in the course is mainly based on the reflections and practical application of the concepts dealt with in the weeklylectures. Some assignments are individual, while some others are done in teams of 3 students. Regular work and attendance toclasses is recommended for an adequate elaboration of the individual weekly assignments.

Grading for the course will be composed by the combination of the following activities in the stated percentage:

How students show their understanding and critical analysis ability, through the written impressions on every week subject●

through the individual blog (30%) and through participation (10%), both in the classroom and in the moodle virtual forum.Team assignments and their presentation in the classroom will show how students have applied the methods discussed, and●

that they have understood the main principles behind the subjects studied. (45%)Individual final assignment, were the student will show his/her understanding and critical analysis ability about the course●

subjects from a holistic point of view (15%).

Cheating and plagiarism will be severely punished, according to UPM reglamentation.






GA_10AM_103000543_2S_2016-17 11



Interaction Design: Beyond Human-Computer Interaction. HelenSharp, Yvonne Rogers, Jenny Preece. John Wiley & Sons, 2007.

Bibliografía

Designing the User Interface. Strategies for EffectiveHuman-Computer Interaction. 4th ed. Ben Shneiderman, CatherinePlaisant. Addison Wesley, 2005.

Bibliografía

Designing Visual Interfaces. Communication Oriented Techniques.Kevin Mullet, Darrell Sano. Prentice Hall, 1994.

Bibliografía

Mobile User Experience: Patterns to Make Sense of it All. AdriánMendoza. Morgan Kaufmann, 2013.

Bibliografía

Usability Planner Recursos web http://usabilityplanner.org/v2/


Documents

MASTER UNIVERSITARIO EN INGENIER IA DEL SOFTWARE ...pegaso.ls.fi.upm.es/emse/documentos/curso1617/... · Software Project Management Ana M. Moreno C 4 1, 3 MODULE SUPPORT PROCESSES