Oficina: ML 767
Extensión: 2834
2024
2024
2024
2024
2023
2023
2022
2022
2022
2022
2022
2021
2021
2021
2021
2021
2021
2020
2020
2020
2020
2020
2020
2020
2020
2019
2019
2019
2019
2018
2018
2018
2018
2018
2018
2017
2017
2017
2017
2017
2017
2017
2016
2016
2016
2016
2016
2016
2015
2015
2015
2015
2015
2015
2015
2015
2015
2015
2015
2015
2015
2014
2014
2014
2014
2014
2014
2014
2014
2014
2014
2014
2013
2013
2013
2013
2013
2013
2013
2013
2013
2013
2013
2012
2012
2012
2012
2012
2012
2012
2012
2012
2012
2011
2011
2011
2011
2011
2009
2009
2009
2008
2008
2008
2008
2007
2007
I’m deeply involved with the organization of Programming Contests. Particularly, I participate in the organization of ACIS/Redis’s National Programming Contest, ACM’s Regional Programming Contest, and the REDIS national circuit of programming contests.
I also organize several training activities for our teams. All the relevant information about the activities and results of our group is published in the groups’ official web site: http://maraton.uniandes.edu.co/
ARQUITECTURA PROCESOS NEGOCIO
ALG. Y PROGR. OBJ. I (HONORES)
PROYECTO 2
ARQUITECTURA PROCESOS NEGOCIO
ALG. Y PROGR. OBJ. I (HONORES)
ANALISIS Y DISEÑO SOFTWARE
PROYECTO 2
ARQUITECT.EMPRESAR.Y DE INTEGR
ALG. Y PROGR. OBJ. I (HONORES)
ARQUITECTURA PROCESOS NEGOCIO
PROYECTO 2
ENTERPRISE MODELING
ANALISIS Y DISEÑO SOFTWARE
PROYECTO FINAL
ARQUITECTURA PROCESOS NEGOCIO
ALG. Y PROGR. OBJ. I (HONORES)
PROYECTO FINAL
ANALISIS Y DISEÑO SOFTWARE
ALG. Y PROGR. OBJ. I (HONORES)
INTEGRACIÓN SIST. INFORMAC.
ARQUITECTURA PROCESOS NEGOCIO
PROYECTO 2
PROYECTO FINAL
ALG. Y PROGR. OBJ. I (HONORES)
INTEGRACIÓN SIST. INFORMAC.
ARQUITECT.EMPRESAR.Y DE INTEGR
ARQUITECTURA PROCESOS NEGOCIO
ANALISIS Y DISEÑO SOFTWARE
INTEGRACIÓN SIST. INFORMAC.
PROYECTO FINAL
ARQUITECTURA EMPRESARIAL
ALG. Y PROGR. OBJ. I (HONORES)
ARQUITECTURA PROCESOS NEGOCIO
ANALISIS Y DISEÑO SOFTWARE
INTROD. INGENIERIA DE SISTEMAS
INTROD. INGENIERIA DE SISTEMAS
PROYECTO FINAL
ARQUITECTURA EMPRESARIAL
ALG. Y PROGR. OBJ. I (HONORES)
ARQUITECTURA PROCESOS NEGOCIO
ARQUITECT.EMPRESAR.Y DE INTEGR
INTEGRACIÓN SIST. INFORMAC.
NUEVAS TIC NEGOCIOS DIGITALES
ARQUITECTURA PROCESOS NEGOCIO
PROYECTO FINAL
ARQUITECTURA EMPRESARIAL
INTROD. INGENIERIA DE SISTEMAS
ALG. Y PROGR. OBJ. I (HONORES)
PROYECTO FINAL
INTROD. INGENIERIA DE SISTEMAS
ARQUITECTURA PROCESOS NEGOCIO
ARQUITECTURA EMPRESARIAL
ALG. Y PROGR. OBJ. I (HONORES)
PROYECTO FINAL
INTROD. INGENIERIA DE SISTEMAS
ARQUITECTURA EMPRESARIAL
INTRODUCCIÓN A LA PROGRAMACIÓN
ARQUITECTURA PROCESOS NEGOCIO
ARQUITECTURA PROCESOS NEGOCIO
PROYECTO FINAL
ARQUITECTURA EMPRESARIAL
INTROD. INGENIERIA DE SISTEMAS
INTRODUCCIÓN A LA PROGRAMACIÓN
INTRODUCCIÓN A LA PROGRAMACIÓN
ARQUITECTURA EMPRESARIAL
ARQUITECTURA PROCESOS NEGOCIO
PROYECTO FINAL
INTROD. INGENIERÍA DE SISTEMAS
ARQUITECTURA EMPRESARIAL
FRAMEWORKS Y LENGUAJES
INTRODUCCIÓN A LA PROGRAMACIÓN
PROYECTO FINAL
ARQUITECTURA PROCESOS NEGOCIO
INTRODUCCIÓN A LA PROGRAMACIÓN
DISEÑO Y PROGRAMACIÓN O.O.
PROYECTO FINAL
FRAMEWORKS Y LENGUAJES
ARQUITECTURA PROCESOS NEGOCIO
DISEÑO Y PROGRAMACIÓN O.O.
PROYECTO FINAL
PROYECTO DE GRADO
ARQUITECTURA PROCESOS NEGOCIO
DISEÑO Y PROGRAMACIÓN O.O.
INTROD. INGENIERÍA DE SISTEMAS
PROYECTO FINAL
ARQUITECTURA PROCESOS NEGOCIO
DISEÑO Y PROGRAMACIÓN O.O.
PROYECTO FINAL
ARQUITECTURA PROCESOS NEGOCIO
DISEÑO Y PROGRAMACIÓN O.O.
PROYECTO FINAL
PROYECTO FINAL
DISEÑO Y PROGRAMACIÓN O.O.
PROYECTO DE GRADO
ARQUITECTURA PROCESOS NEGOCIO
PROYECTO DE GRADO
ARQUITECTURA PROCESOS NEGOCIO
DISEÑO Y PROGRAMACIÓN O.O.
PROYECTO FINAL
DESARROLLO DE SW EN EQUIPO
PROYECTO DE GRADO
PROYECTO FINAL
DISEÑO Y PROGRAMACIÓN O.O.
Executable Models, Model Driven Engineering, Workflow Engines, Workflow Specification Languages, Concern Specific Workflow Languages.
In recent years, workflows have started to be used in many domains such as business processes, scientific applications, and e-learning. Accordingly, various workflow specification languages have needed to be designed in each one of those domains. Corresponding infrastructures (like editors, engines, and monitoring applications) to utilize and enact those languages have been implemented as well. Among the benefits commonly associated with workflows, one that stands out is the possibility of modifying workflow definitions by manipulating only high level or domain specific concepts. This is extremely positive because it enables domain experts to introduce changes to the systems without requiring the intervention of software developers. However, this flexibility is not always enough. Workflow users often encounter new requirements that cannot be properly solved with existing tools and languages because they depend on new concepts or should use different structures. In those cases, their only options are to change or extend the workflow languages, or to develop entire new ones. Unfortunately, nowadays there is poor support to implement either alternative. With the former, the biggest problem is that workflow languages and their associated tools have very limited extensibility capabilities. With the latter, there are two different problems. The first one is the scarcity of frameworks or libraries available to support the development of new workflow engines to enact the newly created languages. The second problem is that existing engines are tightly coupled to the languages they were developed for. Therefore, by creating a new language one looses existing tool support (editors, simulators, monitoring applications, and others).
The goal of this dissertation is to solve these limitations by offering a platform that serves as the foundation for extensible workflow engines. In this way, the enactment of new workflow languages will be more easily supported, because the implementation of every engine will not start from scratch. Furthermore, this platform is geared towards supporting extensible and flexible workflow languages, and thus changing requirements will be more easily accommodated. The proposed platform supports various kinds of workflow languages. In the first place, there are general purpose workflow languages that can be used in many domains, such as BPEL or BPMN. Another kind is that of domain specific workflow languages, such as IMS-LD or Sedna. Finally, the proposed platform also supports concern specific workflow languages, which modularize workflow descriptions in accordance with various possible criteria.
There are three ideas that are central to the proposal. First of all, there is the idea of using metamodels to define the structure of workflow languages, and using models to represent specific workflows. The second idea is that of making the models executable by establishing executable semantics for every element in the metamodels, and following the semantics of the language. Finally, the third idea is that of coordinating the execution of several executable models in order to support the aforementioned concern specific languages. To support these three ideas we developed the notion of `open objects’, which are used to define the behavior of elements of the metamodels in a special way. By using open objects, each element defines its own semantics. However, the actual coordination between those elements is specified in an explicit and flexible way. It is the responsibility of a special kernel in the platform to use this information to coordinate the behavior of the elements and thus execute the workflows. Furthermore, this kernel also provides other features common to workflow systems. Therefore, these features do not have to be reimplemented for every language.
The ideas presented in this dissertation have been implemented in the Cumbia platform, which encompasses a Java based development framework, and two components called Cumbia Kernel and Cumbia Weaver. Concretely, the framework is what workflow language developers need to build their own metamodels based on open objects. The Cumbia Kernel is the component that loads and runs the models. The Cumbia Weaver is what establishes relationships between models conformant to different metamodels, thus allowing the interaction of concern specific languages.
This approach has been validated with the construction of engines for well known workflow languages, which include BPEL, BPMN and YAWL. Other experiments include the implementation of engines for concern specific workflow languages (miniBPMN, XPM, and XTM), and for domain specific workflow languages (IMS-LD and PaperXpress).
Dissertation: Download.pdf