master universitario en ingenier ia del software ... · curso acadÉmico - semestre 2014-15 -...

MASTER UNIVERSITARIO EN INGENIERIADEL SOFTWARE - EUROPEAN MASTER IN

SOFTWARE ENGINEERING

Educational Planning Course 2014/2015Second Semester

Computer Science and Engineering SchoolUniversidad Politecnica de Madrid

CONTENTS i

Contents

1 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 . . . . . . . . . . . . . . . . . . . . . 19

6.2 Support Processes Module . . . . . . . . . . . . . . . . . . . . 30

6.2.1 Software Quality Management . . . . . . . . . . . . . 30

6.3 Advanced Software Engineering Aspects Module . . . . . . . 43

6.3.1 Agent Based Software Development . . . . . . . . . . 43

6.3.2 Experimental Software Engineering . . . . . . . . . . . 57

6.3.3 Interaction Design . . . . . . . . . . . . . . . . . . . . 67

6.3.4 Management, Relationships and Communication inWorking Groups . . . . . . . . . . . . . . . . . . . . . 80

1

1 Enrollment Dates

• Ordinary period: from 30 January to 9 February 2015

Course starts on 15 September 2014

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 5 6 7 3 1 2 3 4 5 7 1 2 12 1 2 3 4 5 6 7

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

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

2 22 23 24 25 26 27 28 6 20 21 22 23 24 25 26 10 17 18 19 20 21 22 23 22 23 24 25 26 27 28

3 29 30 7 27 28 29 30 31 11 24 25 26 27 28 29 30 29 30 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 2 3 4 1 3 1 1 2 3 4 5

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

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

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

26 27 28 29 30 31 3 23 24 25 26 27 28 6 23 24 25 26 27 28 29 10 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 S M T W T F S S10 1 2 3 15 1 2 3 4 5 6 7 1 2 3 4 5 1 2

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

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

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

14 25 6 27 28 29 30 31 29 30 27 28 29 30 31 24 25 26 27 28 29 30

31

Key:

School dayEvaluation processHolidayVacationRegistrationExtraordinary examsComplementart activities; transversal competences development

March-15 April-15

May-15 June-15 July-15 August-15

January-15 February-15

EUROPEAN MASTER ON SOFTWARE ENGINEERING

COURSE 2014-15

September-14 October-14 November-14 December-14

E.T.S. DE INGENIEROS INFORMÁTICOSUniversidad Politécnica de Madrid

2 2 CALENDAR

2 Calendar

Wednesday Monday Tuesday Thursday Friday 15:00

16:00

17:00

18:00

19:00

20:00

EMSE 2014-‐2015 ·∙ 2nd Semester (FEB)

21:00

Agent Based SoKware Development Room 6202

Ricardo Imbert

InteracGon Design Room 6202

Xavier Ferré

Experimental SoKware Engineering Room 6202

Natalia Juristo, Sira Vegas

InteracGon Design Room 6202

Xavier Ferré

SoKware Quality Management Room 6202

Angélica de Antonio

SoKware Architecture Room 6202

Jaime Ramírez Assessment AcGviGes

Experimental SoKware Engineering Room 6202

Natalia Juristo, Sira Vegas

SoKware Design Room 6202

Nelson Medinilla

Agent Based SoKware Development Room 6202

Ricardo Imbert

Mandatory Subjects (16 weeks)

Elec9ve Subjects (16 weeks)

Elec9ve Subjects (week 1 to 12)

Special Ac9vi9es (16 weeks)

Management, RelaGonships and CommunicaGon in Working Groups Room 6202

Susana Muñoz

3

1st and 3rd Semester (Fall Term) JANUARY 2015

MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY SUNDAY

19 20 21 22 23 24 25

Rigorous Software Development 15:00 Software

Metrics 15:00

Challenges for Accessible Computing for People with Functional Diversity

15:00 Advanced Software Engineering Economics

15:00

Software Engineering Economics 18:00 Requirements

Engineering 18:00 Critical Soft-‐ware 18:00

Agile Software Development: Agile Practices and Agile Usability

18:00

26 27 28 29 30 31 1 Models and Methods for Process Im-‐provement and Assess-‐ment

15:00 Software Project Man-‐agement 15:00 Master Thesis 15:00

Verification and Validation 18:00 Data Engi-‐

neering 18:00

43

EXAM

CALENDAR

3E

xam

Cale

nd

ar

2nd Semester (Spring Term)

JUNE 2015 MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY SUNDAY

8 9 10 11 12 13 14

Master Thesis 15:00 Interaction Design 15:00

Experimental Software Engineering 15:00

Management, Relationships and Commu-‐nication in Working Groups

15:00 Software Quality Man-‐agement 15:00

15 16 17 18 19 20 21

Agent Based Software Development 15:00 Software

Architecture 15:00 Software Design 15:00

5

Extraordinary period (JUL) JUNE-‐JULY 2015

MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY SUNDAY

22 23 24 25 26 27 28

Master Thesis 15:00

29 30 1 2 3 4 5 Software Architecture 15:00

Software Project Man-‐agement 15:00 Software

Metrics 15:00 Rigorous Software Development 15:00

Software Quality Man-‐agement 15:00

Data Engi-‐neering 18:00

Agent Based Software Development 18:00 Critical Soft-‐

ware 18:00 Requirements Engineering 18:00 Software

Design 18:00

6 7 8 9 10 11 12

Agile Software Development: Agile Practic-‐es and Agile Usability

15:00 Software Engineering Economics

15:00 Experimental Software Engineering

15:00


15:00 Interaction Design 15:00

Management, Relationships and Commu-‐nication in Working Groups

18:00 Verification and Validation 18:00

Models and Methods for Process Im-‐provement and Assess-‐ment

18:00 Advanced Software Engineering Economics

18:00

63

EXAM

CALENDAR

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

MODULE SOFTWARE DEVELOPMENT Course unit name Coordinator Type ECTS Term Requirements Engineering Óscar Dieste C 6 1 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

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

Ana M. Moreno E 4 1


Loïc Martínez E 4 1, 3

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

Óscar Dieste E 4 1,3

Experimental Software Engineering Natalia Juristo E 6 2 Interaction Design Xavier Ferré E 6 2 Management, Relationships and Communication in Working Groups

Susana Muñoz E 4 2

Rigurous Software Development Julio Mariño E 4 1, 3 Software Economics June Amillo E 3 1 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 Advanced Software Engineering Economics June Amillo Xavier Ferré Ricardo Imbert Agent-‐Based Software Development Ricardo Imbert Xavier Ferré Jaime Ramírez Agile Software Development: Agile Practices and Agile Usability

Ana María Moreno

José A. Calvo-‐Manzano

Tomás San Feliu


Aurora Pérez Loïc Martínez José Luis Fuertes

Critical Software Andrés Silva Xavier Ferré Ricardo Imbert Data Engineering Javier Segovia Ernestina

Menasalvas Luis Mengual

Distributed and Outsourced Software Engineering

Natalia Juristo Sira Vegas Óscar Dieste

Experimental Software Engineering Natalia Juristo Sira Vegas Óscar Dieste Interaction Design Xavier Ferré Ricardo Imbert Jaime Ramírez Management, Relationships and Communication in Working Groups

Susana Muñoz Julio Mariño Lars-‐Åke Fredlund

Master Thesis Natalia Juristo Ricardo Imbert Xavier Ferré Models and Methods for Process Improvement and Assessment

José A. Calvo-‐Manzano

Tomás San Feliu Ricardo Imbert

Requirements Engineering Natalia Juristo Sira Vegas Óscar Dieste Rigurous Software Development Julio Mariño Susana Muñoz Lars-‐Åke

Fredlund Seminars Xavier Ferré Ricardo Imbert Óscar Dieste Software Architecture Angélica de

Antonio Nelson Medinilla Jaime Ramírez

Software Design Nelson Medinilla Xavier Ferré Ricardo Imbert Software Economics June Amillo Ricardo Imbert Xavier Ferré Software Metrics Tomás San Feliu José A. Calvo-‐

Manzano Ricardo Imbert

Software Project (Practicum) Natalia Juristo Ricardo Imbert Xavier Ferré Software Project Management Natalia Juristo Sira Vegas Ana María

Moreno Software Quality Management Angélica de

Antonio Xavier Ferré Ricardo Imbert

Verification and Validation Natalia Juristo Sira Vegas Óscar Dieste

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

E.T.S. de Ingenieros Informaticos

PROCESO DE SEGUIMIENTO DE TÍTULOS OFICIALES

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

GA_10AM_103000484_2S_2014-15

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

ASIGNATURASoftware architecture

CURSO ACADÉMICO - SEMESTRE2014-15 - Segundo semestre

FECHA DE PUBLICACIÓNDiciembre - 2014

10 6 LEARNING GUIDES





GA_10AM_103000484_2S_2014-15 1

Datos Descriptivos

Nombre de la Asignatura Software architecture

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

Centro responsable de la titulación E.T.S. de Ingenieros Informaticos

Semestre/s de impartición Segundo semestre

Carácter Obligatoria

Código UPM 103000484

Datos Generales

Créditos 4 Curso 1

Curso Académico 2014-15 Período de impartición Febrero-Junio

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

Requisitos Previos ObligatoriosAsignaturas Superadas

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_2014-15 2

Competencias

SC12 - To conceive and perform the design of software systems, assuring relevant quality attributes.

Resultados de Aprendizaje

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

RA6 - Ability to document the software architecture






GA_10AM_103000484_2S_2014-15 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 tutorias con elprofesorado.






GA_10AM_103000484_2S_2014-15 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 it will be explained their relationship with quality attributes. Then, some representative architectural patternswill be explained showing how they can be reused to solve some design problems providing well proven solutions without theneed of 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_2014-15 5

Cronograma

Horas totales: 68 horas y 30 minutos Horas presenciales: 28 horas y 30 minutos (27.4%)

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

Semana 2 Previous concepts on SoftwareArchitectureDuración: 01:00


Semana 3 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 4 2.2 Achieving qualityattributes through tacticsDuración: 01:00






Semana 5 2.3 Architectural stylesDuración: 02:00





Actividad no presencial





Semana 8 2.4 Architectural patternsDuración: 02:00













GA_10AM_103000484_2S_2014-15 6







Research work on advancetopics or ProjectDuración: 20:00








Semana 15 Oral presentation on theresearch worksDuración: 02:00

PG: Técnica del tipo Presentación enGrupo



Semana 16 ExamDuración: 01:00

EX: Técnica del tipo Examen Escrito



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_2014-15 7

Actividades de Evaluación

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

Presencial Peso Notamínima

Competenciasevaluadas

3 Practical exercises on topics thatare being explained in classroom

00:45 Evaluacióncontinua

TG: Técnica deltipo Trabajo enGrupo

Sí 2.5% 4 / 10 SC12




Sí 2.5% 4 / 10 SC12




No 20% 4 / 10 SC12




No 10% 4 / 10 SC12

12 Research work on advance topicsor Project



No 30% 5 / 10 SC12

15 Oral presentation on the researchworks


PG: Técnica deltipo Presentaciónen Grupo

Sí 10% 5 / 10 SC12

16 Exam 01:00 Evaluacióncontinua

EX: Técnica deltipo ExamenEscrito

Sí 25% 4 / 10 SC12

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


Sí 100% 4 / 10 SC12

Criterios de Evaluación

Across the semester, in order to pass the course, the student will have to do the following exercises and works:

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.

Research work/Project: the student will have to elaborate a state of the art on some advance topic or to propose a project and●

pose an architectural solution for it. This work will have to be reflected in a document. In addition, before delivering thisdocument, the student will have to do an oral presentation in classroom where the preliminary results of his/her work will besummarized.

The final mark (FM) will be calculated from the practical exercises mark (PEM), the exam mark (EM) and research work mark(RWM) by means of the following formula:

FM=0.35*PEM+0.25*EM+0.4*RWM if PEM>=4 and EM>=4 and RWM>=5

FM = 0 otherwise

Where all the marks take value between 0 and 10

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






GA_10AM_103000484_2S_2014-15 8

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_2014-15


ASIGNATURASoftware design








GA_10AM_103000483_2S_2014-15 1

Datos Descriptivos

Nombre de la Asignatura Software design






Datos Generales

Créditos 4 Curso 1





Otros Requisitos





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






GA_10AM_103000483_2S_2014-15 2

Competencias

SC12 - To conceive and perform the design of software systems, assuring relevant quality attributes


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

RA15 - The student will be able to document each new design.

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






GA_10AM_103000483_2S_2014-15 3



Medinilla Martinez, Nelson(Coordinador/a)

5109 [email protected]







GA_10AM_103000483_2S_2014-15 4


Temario

1. Chapter 1: Software Engineering Two-dimensional Complexity

1.1. 1.1 Software Engineering Complexity Concept Evolution. Software Engineering needs a Holistic Approach.

1.2. 1.2 Uncertainty as Tool

1.3. 1.3 Relationships between software, design and process models in the uncertainty dimension. EvolutionaryApproach.

2. Chapter 2: System Software Design Features

2.1. 2.1 Software as Design. Review of software design concept.

2.2. 2.2 Software Design from the system point of view. Relationships between software and other kinds of systems.Software Design based on the System General Theory. System structures.

2.3. 2.3 Divide and Conquer as systems simplification tool.

2.4. 2.4 Ambiguity as powerful systems simplification tool.

2.5. 2.5 Information Hiding Principle. The Ambiguity or Indifferent (don?t care) Dependent Relationship.

2.6. 2.6 Design Simplification by decrease the quantity of information using abstractions, symmetries, monotonicstructures, and others similar techniques.

2.7. 2.7 Influence of design structure on design properties. Allotropy.

3. Object Oriented Review

3.1. 3.1 Contrast between object and structured models.

3.2. 3.2 Ambiguity in: object, message, class and heritage. Substitution Liskov Principle

3.3. 3.3 Evolutionary Design using Objects.

3.4. 3.4 Use Cases Technique Review

4. Chapter 4: Design and Dominion Patterns

4.1. 4.1 Theoretical foundations of patterns.

4.2. 4.2 Analysis of Design Patterns.

4.3. 4.3 Domain Patterns.

5. Chapter 5: Design Documentation

5.1. 5.1 Documentation reasons.

5.2. 5.2 Software Design Legibility using objects. Suitable use of abstractions and their structure.

5.3. 5.3 Design Diagram Simplification using abstractions, patterns, symmetries and monotonic structures.

5.4. 5.4 Evolutionary Documentation.






GA_10AM_103000483_2S_2014-15 5

Cronograma

Horas totales: 78 horas Horas presenciales: 78 horas (72.2%)





Semana 1 Theory Class (Ch. 1)Duración: 01:30


Set up the groups.Duración: 00:30

OT: Otras actividades formativas

Individual workDuración: 02:00


Make up the software systemrequest.Duración: 03:00

AC: Actividad del tipo AccionesCooperativas

Semana 2 Request and Negotiation aboutthe System will be developed.Duración: 01:00

PR: Actividad del tipo Clase deProblemas

Software DevelopmentDuración: 01:00


Analysis of request andsynthesis of possible solutions.Make an initial decision.Delivery work. (4 hours)Duración: 02:00


Semana 3 Theory Class (Ch. 2)Duración: 02:00




Semana 4 Software development ingroups with client interaction.Duración: 01:00


Public discussion about designdeveloped up to date. (Ch. 2, 3,5)Duración: 01:00




Semana 5 Software development ingroups with client interactionDuración: 01:00

















GA_10AM_103000483_2S_2014-15 6





Preparing the First EvaluationDuración: 03:00


Semana 8 Assessment activity inclassroomDuración: 02:00




Semana 9 Public re-analysis of discusseddesign.Duración: 02:00


Analysis of design.Duración: 01:00


Analysis of design. As client,make up the request ofchanges to wanted systemDuración: 02:00


Semana 10 Request and Negotiation aboutthe changes will be done.Duración: 02:00


Individual work.Duración: 01:00


Analysis of changes wantedand synthesis of possiblesolutions. Make a decision.Delivery work.Duración: 02:00


Semana 11 Theory class (Ch. 4)Duración: 02:00


Software developmentDuración: 03:00






Semana 13 Public discussion about designdeveloped up to date. (Ch. 2, 3,4, 5)Duración: 01:00




Semana 14 Software developmentDuración: 03:00


Previous presentationDuración: 02:00









GA_10AM_103000483_2S_2014-15 7



Public discussion about designdeveloped up to date. (Ch. 2, 3,4, 5)Duración: 01:00






Public discussion about designdeveloped up to date. (Ch. 2, 3,4, 5)Duración: 01:00




Semana 17 Final EvaluationDuración: 02:00




Final AssessmentDuración: 02:00

TI: Técnica del tipo Trabajo Individual









GA_10AM_103000483_2S_2014-15 8





8 Assessment activity in classroom 02:00 Evaluacióncontinua


Sí 20% 5 / 10 SC12

14 Previous presentation 02:00 Evaluacióncontinua


Sí 20% 5 / 10

17 Final Evaluation 02:00 Evaluacióncontinua


Sí 60% 5 / 10 SC12

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

TI: Técnica deltipo TrabajoIndividual

Sí 100% 5 / 10 SC12


Indicators

I1: Design a small software system with client interaction. The system should work and fulfill the requirements, restrictions,quality standards and developer criteria

I2: Make up a document, effective and efficient, about the software design.

I3: Evaluate her/his owns design and any other software system design.

Evaluation Criteria

The Software Design subject is practical, based on solving problems, especially, the development of small software systems. Itis taught though seminar/workshop. The systems are development in group. Each group works as software developer and clientof another group.

The software system should satisfy their client and the criteria set out in I1 indicator. The evaluation of this system is theprincipal measure to grade the student respect to I1 indicator. The replays to oral questions complete the grade.

The I2 indicator on documentation will be graded according to the quality of the written document.

The I3 indicator on evaluation will be graded by the self criticism, include in the written document, and previous evaluations ofother designs.

Ninety percent of the grading will be done at the end of the term. This is because software development is evolutionary. Tenpercent of the grading will be done at half way through the term by a formal presentation of the systems developed up to date.

The software system development is evolutionary for two reasons. The first one is technical: the systems are development innew or unknown contexts (from the student point of view). Moreover, this contexts are dynamic; i.e. its change their needs,frequently. The second reason is the learning process: The systems are modified as learning goes by. In short, the softwaredevelopment is evolutionary because the uncertainty presence.






GA_10AM_103000483_2S_2014-15 9



Readings Bibliografía Gamma Erich et al. ?Design Patterns? Ed. Addison Wesley1994

Book Bibliografía Larman Craig ?Applying UML and Patterns? Second Edition.Prentice Hall 2002.

Article Bibliografía Parnas David ?On the Criteria To Be Used in DecompositionSystems and Modules? Com. ACM Dec. 1972 Vol. 15 Nº 12 pp.1053-1058.

Subject material Recursos web Subject content on Moodle



6.2 Support Processes Module

6.2.1 Software Quality Management





GA_10AM_103000487_2S_2014-15


ASIGNATURASoftware quality management



6.2 Support Processes Module 31





GA_10AM_103000487_2S_2014-15 1

Datos Descriptivos

Nombre de la Asignatura Software quality management






Datos Generales

Créditos 4 Curso 1





Otros Requisitos











GA_10AM_103000487_2S_2014-15 2

Competencias

SC1 - To perform a project plan to coordinate and prioritize resources and activities, in order to obtain the expected resultswithin the deadlines, costs and quality required.

SC11 - To identify, control, inform and audit a system configuration and its changes.

SC6 - To design the unit tests and to learn to design integration and implantation tests. To perform the system integration,integration tests and implantation of the system.

SC7 - To produce a verification and validation plan to coordinate and prioritize resources and activities to assess the requiredquality level.


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

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

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

RA11 - Understands the interrelation between product quality and process quality

RA12 - Knows and applies product and process quality control techniques






GA_10AM_103000487_2S_2014-15 3


Nombre Despacho e-mail Tutorias

Antonio Jimenez, Angelica De(Coordinador/a)

1204 [email protected] L - 11:00 - 14:00

V - 10:00 - 13:00

Previous appointment isrecommended







GA_10AM_103000487_2S_2014-15 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_2014-15 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_2014-15 6

Cronograma

Horas totales: 71 horas Horas presenciales: 52 horas (50%)



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_2014-15 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: 02:00


First Partial examDuración: 02: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: 02: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.1 Basic Concepts ofSoftware ConfigurationManagement Chapter 6.2Configuration IdentificationDuración: 02:00






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







GA_10AM_103000487_2S_2014-15 8

Semana 17 Second partial examDuración: 02:00




Final examDuración: 02:00










GA_10AM_103000487_2S_2014-15 9





1 Reading 1 test 03:00 Evaluacióncontinua

ET: Técnica deltipo PruebaTelemática

No 3% SC1

3 Individual exercise on qualityattributes



No 7% SC1



No 3% SC1

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


Sí 10% SC7

7 Report about exercise oninspections



Sí 10% SC7

8 Report about exercise onwalkthroughs



Sí 8% SC7



No 3% SC7

10 First Partial exam 02:00 Evaluacióncontinua


Sí 20% 4 / 10 SC1, SC6, SC7



No 3% SC1, SC7

14 Presentation of group work onquality management tools



Sí 10% SC1, SC7



No 3% SC1, SC7

17 Second partial exam 02:00 Evaluacióncontinua


Sí 20% 4 / 10 SC1, SC6, SC7,SC11

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


Sí 100% 5 / 10 SC1, SC6, SC7,SC11


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_2014-15 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_2014-15 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 43

6.3 Advanced Software Engineering Aspects Module

6.3.1 Agent Based Software Development





GA_10AM_103000538_2S_2014-15


ASIGNATURAAgent-based software development








GA_10AM_103000538_2S_2014-15 1

Datos Descriptivos

Nombre de la Asignatura Agent-based software development




Carácter Optativa


Datos Generales

Créditos 6 Curso 1





Otros Requisitos











GA_10AM_103000538_2S_2014-15 2

Competencias

SC-13 - To have a vision of the different specific and emergent aspects of the Software Engineering, and to go further in some ofthem.

SC-14 - To understand what nowadays software engineering procedures can and cannot reach, their limitations and theirpossible future evolution.


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

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

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_2014-15 3


Nombre Despacho e-mail Tutorias

Imbert Paredes, Ricardo(Coordinador/a)

1209 /5112

[email protected] L - 11:00 - 14:00

X - 11:00 - 14:00







GA_10AM_103000538_2S_2014-15 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_2014-15 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_2014-15 6

Cronograma






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


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


3. Agent oriented analysisDuración: 01:00


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


Evaluación continua y sólo pruebafinal


Semana 3 3. Agent oriented analysisDuración: 01:00


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

PI: Técnica del tipo PresentaciónIndividual



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


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


Project coordinationDuración: 03:00


Semana 5 3. Agent oriented analysisDuración: 02:00






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






Exercise about systemstopologyDuración: 00:45









GA_10AM_103000538_2S_2014-15 7

Semana 7 5. Agent oriented detaileddesign (part I)Duración: 01:00




Semana 8 5. Agent oriented detaileddesign (part I)Duración: 01:30


6. Agent implementationDuración: 01:00




Exercise about agentcommunication protocolsDuración: 00:30




Semana 9 7. Agent oriented detaileddesign (part II)Duración: 02:00


8. Development processDuración: 00:20






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

















GA_10AM_103000538_2S_2014-15 8

















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




Exercise about agent baseddevelopmentDuración: 01:00




Semana 16






GA_10AM_103000538_2S_2014-15 9

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




Student implication andparticipationDuración: 00:00

OT: Otras técnicas evaluativas









GA_10AM_103000538_2S_2014-15 10





2 Exercise about risks on agentbased software engineering

01:00 Evaluacióncontinua y sóloprueba final


Sí 4% SC-14

3 Presentation in the classroom ofthe first practical assignment


PI: Técnica deltipo PresentaciónIndividual

Sí 15% 3 / 10 SC-13, SC-14

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


Sí 4% SC-13

8 Exercise about agentcommunication protocols



Sí 3% SC-13

15 Presentation of the secondpractical assignment in theclassroom



Sí 60% 4 / 10 SC-13, SC-14

15 Exercise about agent baseddevelopment



Sí 4% SC-13

17 Exercise about comparison ofagent based methodologies

00:00 Evaluación sóloprueba final


Sí 14% SC-13, SC-14

17 Student implication andparticipation


OT: Otras técnicasevaluativas

No 10% SC-13


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_2014-15 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_2014-15 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_2014-15


ASIGNATURAExperimental software engineering








GA_10AM_103000542_2S_2014-15 1

Datos Descriptivos

Nombre de la Asignatura Experimental software engineering




Carácter Optativa


Datos Generales

Créditos 6 Curso 1





Otros Requisitos











GA_10AM_103000542_2S_2014-15 2

Competencias

CE13 - To have a vision of the different specific and emergent aspects of the Software Engineering, and to go further in some ofthem.

CE14 - To understand what nowadays software engineering procedures can and cannot reach, their limitations and theirpossible future evolution.


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_2014-15 3



Juristo Juzgado, Natalia (Coordinador/a) D-5104 [email protected]

Vegas Hernandez, Sira D-5105 [email protected] M - 14:00 - 17:00

J - 12:00 - 15:00







GA_10AM_103000542_2S_2014-15 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_2014-15 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_2014-15 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_2014-15 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_2014-15 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 Interaction Design





GA_10AM_103000543_2S_2014-15


ASIGNATURAInteraction design








GA_10AM_103000543_2S_2014-15 1

Datos Descriptivos

Nombre de la Asignatura Interaction design




Carácter Optativa


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_2014-15 2

Competencias

CE-13 - To have an overview of the software engineering emerging and specific aspects, and to know in depth some of them.

CE-14 - To understand what current software engineering practices can and cannot achieve, their limitations and possible futureevolution.


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_2014-15 3



Ferre Grau, Xavier (Coordinador/a) 5112 [email protected] L - 15:30 - 17:30

J - 10:00 - 14:00

Moral Martos, Cristian L5101 [email protected] L - 11:00 - 14:00

X - 11:00 - 14:00







GA_10AM_103000543_2S_2014-15 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

9. Internationalization

10. Integration of usability into the software development process






GA_10AM_103000543_2S_2014-15 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_2014-15 6

























Semana 7 Team tutoringDuración: 04:00






Team presentationDuración: 03:00

























GA_10AM_103000543_2S_2014-15 7



























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

































GA_10AM_103000543_2S_2014-15 8

























Semana 17 Final assignmentDuración: 00:00




ExamDuración: 00:00










GA_10AM_103000543_2S_2014-15 9





1 Participation showing criticalability in the classroom or in thevirtual forum



No .63% CE-14

2 Blog entry 00:00 Evaluacióncontinua


No 3% CE-13, CE-14




No .63% CE-14



No 3% CE-13, CE-14




No .63% CE-14



No 3% CE-13, CE-14




No .62% CE-14



No 3% CE-13, CE-14




No .63% CE-14



No 3% CE-13, CE-14




No .63% CE-14



No 3% CE-13, CE-14

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


Sí 15% CE-13, CE-14




No .63% CE-14



No 3% CE-13, CE-14




No .63% CE-14



No 3% CE-13, CE-14




No .63% CE-14



No 3% CE-13, CE-14



Sí 15% CE-13, CE-14




No .62% CE-14






GA_10AM_103000543_2S_2014-15 10






No 3% CE-13, CE-14




No .62% CE-14




No .62% CE-14




No .62% CE-14




No .62% CE-14



Sí 15% CE-13, CE-14




No .62% CE-14




No .62% CE-14

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


No 15% CE-13, CE-14

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


Sí 40% CE-13, CE-14


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_2014-15 11



Interaction Design: Beyond Human-ComputerInteraction. Helen Sharp, Yvonne Rogers, Jenny Preece.John Wiley & Sons, 2007.

Bibliografía

Designing the User Interface. Strategies for EffectiveHuman-Computer Interaction. 4th ed. BenShneiderman, Catherine Plaisant. Addison Wesley,2005.

Bibliografía

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

Bibliografía

Mobile User Experience: Patterns to Make Sense of itAll. Adrián Mendoza. Morgan Kaufmann, 2013.

Bibliografía

Usability Planner Recursos web http://raptor.ls.fi.upm.es/usabilityplanner/



6.3.4 Management, Relationships and Communication in Work-ing Groups





GA_10AM_103000544_2S_2014-15


ASIGNATURAManagement, relationships and communication in working groups








GA_10AM_103000544_2S_2014-15 1

Datos Descriptivos

Nombre de la Asignatura Management, relationships and communication in working groups




Carácter Optativa


Datos Generales

Créditos 4 Curso 1





Otros Requisitos











GA_10AM_103000544_2S_2014-15 2

Competencias

CG10 - Skill of creative thinking with the goal of developing new and original focus and methods.

CG17 - Ability of management and capacity of team leadership integrated in different disciplines or levels.

CG18 - Ability of working and communicating in international contexts.

CG3 - To communicate their conclusions and the knowledge and last reasoning to technical and non-technical audiences in aclear and non-ambiguous way.

SC13 - To have a vision of the different specific and emergent aspects of the Software Engineering, and to go further in some ofthem.

SC14 - To understand what nowadays software engineering procedures can and cannot reach, their limitations and theirpossible future evolution.


RA21 - Listening capability SC13, SC14, CG10 A

RA22 - Observing capability SC13, SC14, CG10 C

RA23 - Time organization capability SC13, SC14 K

RA24 - Conflict solving capability SC13, SC14, CG18 C

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

RA26 - Group work skill SC13, SC14, CG17 A

RA27 - Negotiation skill SC13, SC14, CG18 C






GA_10AM_103000544_2S_2014-15 3



Mu?oz Hernandez, Susana(Coordinador/a)

2310 [email protected] X - 10:00 - 11:00

X - 13:00 - 16:00

V - 13:00 - 15:00

Las tutorías se concertaránpor mail previamente.







GA_10AM_103000544_2S_2014-15 4


OutlineWithin the sphere of business, research or development and cooperation, finishing a project successfully depends on severalfactors. So does efficiency and effectiveness of the project. One of the most important of these factors is the human factor.Communication and management skills, together with the relationship between workgroup members are some of the decidingelements for developing a well-done job. Social skills are a key aspect during the development of a task in an environmentwhere the different members don't necessarily need to share the same characteristics.

Learning GoalsThis course studies in depth the factors that determine the human skills for managing and administering a work group, asidefrom its supervision and smooth running assurance. It will emphasize the importance of communication (motivational,negotiation) and self-control processes, as well as the methods connected to the decision-making processes and teammanagement abilities (leadership, conflict mediation, etc.).

Temario

1. Introduction

1.1. Motivation I3

1.2. Topics Definition I3, I1

2. Communication Basis

2.1. Communication I1, I2, I4

2.2. Relation I1, I2, I4

2.3. Team Group I1, I2, I4






GA_10AM_103000544_2S_2014-15 5

3. Personal Skills

3.1. Assertiveness I1, I2, I4

3.2. Negotiation I1, I2, I4

3.3. Conflict Solving I1, I2, I4

3.4. Intercultural differences management I1, I2, I4

3.5. Time Management I1, I2, I4

3.6. Body Language & Non verbal communication I1, I2, I4

3.7. Public Presentations I1, I2, I4

3.8. Meeting Management I1, I2, I4

3.9. Emotional Intelligence I1, I2, I4

3.10. Motivation I1, I2, I4

3.11. Coaching I1, I2, I4

3.12. Social Engineering I1, I2, I4

3.13. Creativity I1, I2, I4

3.14. Leadership I1, I2, I4






GA_10AM_103000544_2S_2014-15 6

Cronograma






Semana 1 Section 1.1 and Section 1.2Duración: 02:00


Participation in classdiscussions Topic selectionDuración: 01:00




Semana 2 Section 2.1Duración: 02:00


Participation in classdiscussions. GrouporganizationDuración: 01:00




Semana 3 Section 2.2Duración: 02:00


Participation in classdiscussions. CalendaragreementDuración: 01:00




Semana 4 Section 3.1, Section 3.6 andSection 3.7Duración: 01:30


Indivitual work and groupwork.Duración: 01:00


Participation in classdiscussions. Grouppresentation. Classmatesfeedback.Duración: 00:30




Semana 5 Section 3.2, Section 3.6 andSection 3.7.Duración: 01:30





















GA_10AM_103000544_2S_2014-15 7

























Semana 10 Section 3.9, Section 3.6 andSection 3.7Duración: 01:30





































GA_10AM_103000544_2S_2014-15 8























Semana 17 Work evaluationDuración: 02:00




Exam evaluationDuración: 02:00










GA_10AM_103000544_2S_2014-15 9





1 Participation in class discussionsTopic selection



Sí 5% CG17, CG18

2 Participation in class discussions.Group organization



Sí 5% CG10, CG17,CG18

3 Participation in class discussions.Calendar agreement



Sí 5% SC13, SC14,CG3, CG10,CG17, CG18

4 Participation in class discussions.Group presentation. Classmatesfeedback.



Sí 5%




Sí 5%




Sí 5%




Sí 5%




Sí 5%




Sí 5%




Sí 5%




Sí 5%




Sí 5%




Sí 5%




Sí 5%




Sí 5%




Sí 5%

17 Work evaluation 02:00 Evaluacióncontinua


Sí 20% SC13, SC14,CG10, CG17,CG18

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


Sí 20%


The attendance to the classes is mandatory. A high number of absents classes will be enough for failing the course.

The final grade will be calculated taking into account:






GA_10AM_103000544_2S_2014-15 10

the participation of the students during the classes. Specially during the discussions.●

the work in group that the students should prepare related one of the topics of the course●

the presentation in public of that work●

the feedback to the classmates during the presentations of the rest of the groups●






GA_10AM_103000544_2S_2014-15 11



Recommended reading Bibliografía Recommended books and references related to the topic.

Subject web site Recursos web http://babel.ls.fi.upm.es/~susana/teaching/Gestion/

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

Equipment for presentations Equipamiento Beamer, speakers, blackboard.

Library Equipamiento Library for consulting reference books and papers.

Group work room Equipamiento Room for working in group.

Classroom Equipamiento Classroom for the presential classes and the presentations.

Otra Información

Some references:

ROBSON, MIKE: Problem Solving in Groups. Gower. Aldershot. (1993).

EALES-WHITE, R: Building Your Team, Kogan Page. Londres. (1995).

MACKAY, I: A Guide to Listening, Bacie. Londres. (1984).

PEASE, A: Body Language: How to Read Others Thoughts by Their Gestures, Sheldon Press. Londres. (1981).G

OMAN, CAROL KINSEY: Creative Thinking in Business, Kogan Page, Londres, (1989).

MONTEBELLO, A y BVZZOTTA, V: "Work Teams that Work", Training and Development Journal (marzo de 1993), AmericanSociety for Training and Development Inc. Alexandra. EE UU. (1993).

ZENGER, J. MUSSELWHITE, E. HUDSON, K. y PERRION, C: "Leadership in a Team Environment", Training and Development. EEUU. (1991).

EALES-WHITE, R: The Power of Persuasion: Improving Your Performance and Leadership Skills, Kogan Page. Londres. (1992).

WEISS, DONALD H.: Creative Problem Solving, AMACOM, Nueva York. (1988).

HONEY, P. y MUMFORD, A.: Manual of Learning Styles. P. Honey. Maidenhead. (1982, rev. 1992).

BIRD, MALCOLM: Problem Solving Techniques That Real1y Work, Piatkus Books, Londres, (1993).

COK, GEOF: Practical Guide to Solving Business Problems, Pitman/The Institute of Management, Londres, (1995).

KENNEOY, G., BENSON. J. y MCMILLAN. J.: Managing Negotiations, 3ª ed., Hutchinson. Londres. (1980).

WHITMORE, J.: Coaching for Performance, Nicholas Brealey, Londres. (1996).

ARAOZ, D. L., Y SUTTON, W. S.: Reengineering Yourself. Bob Adams, Inc., Massachusetts, (1994).


master universitario en ingenier ia del software ... · curso acadÉmico - semestre 2014-15 -...

Documents