Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Taller de preparación de
propuestas para proyectos
de investigación
Xavier Franch, PhD.
franch@essi.upc.edu
Bio
2
Introducción a la programación
1
21/01/2019
Creado en 1992
Evolución desde Sistemas de Información a Ingeniería del
Software y de los Servicios
Actualmente también en temas Procesamiento de Datos
https://gessi.upc.edu/en
H2020
Acronym Name Partners End Position
OpenReq Intelligent Recommendation U. Hamburg, Dec. WP leader
Decision Technologies for Nokia, … 2019
Community-Driven RE
Q-Rapids Quality-aware rapid software Fraunhofer, Oct. Project
development Nokia, … 2019 coordinator
SUPERSEDE SUpporting evolution and FBK April Scientific
adaptation of PERsonalized Siemens- 2018 manager
Software by Exploiting Austria,
contextual Data and End-user ATOS, …
feedback
FP7
RISCOSS Managing Risk and Costs in FBK, OW2, Dec. Project
OSS Adoption Ericsson-Italy 2015 coordinator
S-Cube Software Services and Lead by M. Feb. UPC
Systems Network (NoE) Papazoglou and 2012 Represen-
K. Pohl tative
2
21/01/2019
Tarjeta de visita
Xavier Franch
Universitat Politècnica de Catalunya
franch@essi.upc.edu
https://www.essi.upc.edu/~franch/
@franch.xavier
xavier.franch
3
21/01/2019
4
21/01/2019
Informática 22
Informática 7
Ingeniería de sistemas 3
Tecnologías de la información 3
Ingeniería del software 2
Sistemas de información 2
Computer science 1
Seguridad de sistemas 1
Evaluación y auditoría 1
Gerencia de sistemas 1
Informática empresarial 1
Otras ingenierías 8
Telemática/Telecomunicacione 2
Ciencias de la ingeniería 2
Redes en comunicaciones 2
Electrónica 1
Automática 1
Sociales 10
Educación 6
Proyectos 2
Psicología 1
Calidad 1
5
21/01/2019
Agenda
11
Impacto
Conclusiones
Metodología docente
12
Presentación de conceptos
Ejemplificación mediante texto “real”
6
21/01/2019
Hora de comenzar
13
Pero antes...
DISCLAIMER
14
7
21/01/2019
8
21/01/2019
Concepto de proyecto de
investigación
Definición
2
Un proyecto de investigación es un
procedimiento científico destinado a
recabar información y formular
hipótesis sobre un determinado
fenómeno social o científico
1
21/01/2019
Proyecto individual
Concurso opositor a plaza universitaria
Petición de beca
2
21/01/2019
3
21/01/2019
Núcleo central
8
Estado de la cuestión
Método de investigación
4
21/01/2019
Comunicación
Colaboración
Explotación
Consorcio
Procedimientos
Recursos necesarios
5
21/01/2019
Éxito de la propuesta
11
No olvidemos:
Portada
Resumen
Referencias
Agradecimientos
Apéndices
Recursos adicionales
6
21/01/2019
El primer desafío…
13
Va a depender de la convocatoria:
Espacio total vs.
La convocatoria
14
7
21/01/2019
8
21/01/2019
9
21/01/2019
10
21/01/2019
11
21/01/2019
12
21/01/2019
Ya podemos empezar!
25
13
21/01/2019
Estructura
2
1
21/01/2019
Claro
Atractivo visualmente
Motivador
Sustanciado
Ejemplo
4
Open Source Software (OSS) has become a strategic asset for a number of
reasons, such as its short time-to-market software service and product delivery,
reduced development and maintenance costs, and its customization capabilities.
Open source technologies are currently embedded in almost all commercial
software – by 2013, they will be included in 85% of all commercial software
packages [Gar11b].
2
21/01/2019
Ejemplo
5
Evaluación:
Contexto bien descrito?
3
21/01/2019
Adjetivos clave:
Conciso
Claro
Atractivo visualmente
Motivador
Ejemplo
8
4
21/01/2019
Evaluación:
Problema alineado con contexto?
5
21/01/2019
Ejemplo
11
Ejemplo
12
Desafíos abiertos
6
21/01/2019
Ejemplo
13
Necesidad
The answer to these questions requires the clear
understanding of OSS-based ecosystems from a
strategic and operational perspective, with clear
identification of relevant strategic and operational
dependencies (i.e. not just software dependencies) in
order to control and mitigate all the risks coming from
the adoption of OSS components, throughout the lifetime
of the different products and components that are part of
the OSS ecosystems.
Evaluación:
El caso está alineado con el problema?
Es un caso comprensible?
Es un caso motivador?
7
21/01/2019
Esbozo de la solución
15
Ejemplo
16
8
21/01/2019
Evaluación:
La solución está alineada con el caso presentada?
Parece factible?
Estratificación
9
21/01/2019
Alternativa 1: descomposición
19
Alternativa 2: estratificación
20
10
21/01/2019
Objetivos transversales
21
Objetivos de evaluación
Objetivos de impacto
Ejemplo
22
11
21/01/2019
Evaluación:
Los objetivos parece correctos?
Desarrollo de la solución
24
12
21/01/2019
Ejemplo
25
Figura central
26
Interrelaciones
Plan de trabajo
…
13
21/01/2019
Ejemplo
27
Otros estilos
28
Más profesional
14
21/01/2019
Evaluación:
La figura comunica claramente la solución pensada?
15
21/01/2019
Ejemplo
31
The project results will have a high impact in relation to one of the topics mentioned
in the call, namely “Fast innovation cycles in service industry, e.g. through the
use of Open Source development models”. We are targeting the problems related
with OSS adoption whose solution is a must in order to implement those innovation
cycles. In other words, it is not enough for a project to claim that they deliver an
OSS solution if there are no clear means to deploy and manage over time this
solution in the adopting organization.
Ejemplo
32
Call text: Novel development approaches which would drastically increase development
productivity and various dimensions of software quality such as security, reliability,
performance, scalability and adaptability
The project proposes a novel development approach characterized by the management of NFRs in the
context of software processes with very short delivery cycles. The main novel traits are: 1) Evidence
based (SO1): Data gathered from several sources are used as evidence to drive the consideration of
quality aspects and the full development process. 2) Conceptual simplicity (SO2): The objective of
leveraging QRs with functional requirements in the software process addresses one of the most well-
known drawbacks in all type of software development methods, namely being waterfall based, agile or
rapid. 3) Strategic dimension (SO3): The elaboration of basic quality-related data into strategic key
indicators, together with the capabilities provided by a powerful dashboard, empower decision makers
to make more effective decisions regarding release planning, resource allocation and so on. All in all,
the project drastically increases development productivity. Given that the approach is generic with
respect to quality, it is well prepared to deal with the diversity of QR types, including security,
reliability, performance, scalability and adaptability.
16
21/01/2019
17
21/01/2019
Cadena de búsqueda
Herramientas
18
21/01/2019
Ejemplo
38
19
21/01/2019
Ejemplo
39
Ejemplo
40
20
21/01/2019
Método de evaluación
41
Casos piloto
42
Normalmente, experimentos
Proyecto de colaboración industrial
Mayor variedad de métodos
Es necesario asegurar diversidad de los pilotos
21
21/01/2019
Ejemplo
43
Ejemplo
44
22
21/01/2019
Desafíos actuales
Objetivos específicos
Instrumentación
Ejemplo
46
23
21/01/2019
Ejemplo
47
Context. The OSS project Moodbile aims to enable mobile learning applications (and other kinds
of applications for education) to work together with the Moodle Learning Management System
(LMS) (http://moodle.org, a high profile OSS LMS), which is used as host LMS platform in the
first stage of the project. Rather than just creating mobile applications that replicate the LMS
functionalities on a mobile device, Moodbile provides the developers of applications for
education with the necessary tools to communicate with the LMS (http://moodbile.org).
The motivation of the Moodbile project is to open up the most commonly used e-learning
platforms and LMS, originally designed as monolithic or layered systems, to the service
paradigm. This work is an interoperability solution to extend LMS to other environments such as
the mobile world. Its aim is to contribute in adapting LMS to the current generation of e-learning
2.0.
The Moodbile community also publishes the Moodbile Spec: a specification of a protocol
agnostic web services API. The Moodbile Spec is intended to be a bottom up breed standard for
integrating LMS with mobile apps.
Ejemplo
48
Current issues. The Moodbile server for Moodle is a component deeply integrated with the
official Moodle distribution. In 2010 Moodle.org adopted the SCRUM development methodology
and has started to ship new minor releases every six months. Moodbile has to keep compatibility
with each new release, while evolving the Moodbile feature set has to be done keeping backwards
compatibility with itself. On its last major release (v0.2) in November 2011, Moodbile is
supporting two versions of Moodle: 2.0 and 2.1, and Moodle.org just released a new version in
December 2011: Moodle 2.2 with significant changes in the core system and web services
component on which Moodbile Server for Moodle depends.
Moodbile’s purpose as a community is to innovate on LMS – Mobile Apps integration. Hence,
needs to iterate quickly incorporating new features and capabilities. But at the same time has to
provide a reliable product for the members of the community that have begun to use Moodbile in
education and training.
We expect difficulties maintaining compatibility with all versions of Moodle (and other host LMS
that will come into the scene), the own Moodbile clients and third part clients that have stared to
use Moodbile as a platform. The Moodbile community needs to correctly manage these risks in
order to succeed.
24
21/01/2019
Ejemplo
49
Specific Objectives. The Moodbile community has the following objectives for the project:
To manage the internal backwards compatibility risks between the 4 components developed
and maintained by the community (see below) without compromising the ability to innovate
and experiment.
To manage the compatibility with the on-going releases of Moodle and other host-LMS to be.
To manage the community requirements for evolution of the product balancing the resources
with the focus on reliability, stability and support for the released versions.
Instrumentation. This use case will work with the 4 main components that Moodbile currently
releases: (1) Moodbile server for Moodle, a plug-in for the Moodle LMS that implements a
protocol-independent web services API that allows integration with mobile clients. (2) Moodbile
HTML 5 Client Moodbile Client that runs on most mobile browsers. Moodbile HTML 5 Client
runs on the same web server as the LMS and provides a Mobile Web friendly limited front, using
the Moodbile Spec (web)services. (3) Android native client. (4) iOS native client.
Evaluación:
Adecuación del caso a los objetivos del proyecto
Diversidad de tipología
Diversidad de tamaño
Otras diversidades
25
21/01/2019
Métodos de investigación
51
Ejemplo
52
From the methodological perspective, the main type of instrument to be used in the
project is case studies. Case studies will provide a common platform for evaluating the
framework by focusing on different aspects of software development. According to [15],
case studies are “…an empirical inquiry that investigates a contemporary phenomenon
within its real-life context, especially when the boundaries between phenomenon and
context are not clearly evident” (p. 13). Case studies as applied in the use cases are
categorized as feasibility studies. For this context, the case studies will focus on
evaluating whether results can be applied in software development practice, whether the
different technological aspects are seamlessly integrated, whether the implemented tools
support the approach and on identifying improvement potential.
Other instruments that will be used in the project are the following [16]:
Surveys. Surveys enable the collection of standardized information from (or a sample
of) a specific population. They will be used to determine the current states of practice
with practitioners either through questionnaires or interviews.
…
26
21/01/2019
Proceso de evaluación
53
Características:
Recogida de requisitos
Evaluación:
Planteamiento general de la evaluación
27