No description available.

Aplicações ditas não convencionais, como, por exemplo, CAD, CASE, Automação de Escritórios, entre outras, freqüentemente exigem a manutenção de diversos estados da base de dados, retendo o histórico das modificações realizadas. Como resposta a tal requisito, é empregado o conceito de Versão. Neste trabalho o Modelo de Versões proposto por Golendziner é empregado no contexto da evolução de esquemas. Versões são utilizadas para armazenar os diferentes estados do esquema, de suas classes e métodos e, ainda, para posterior adaptação das instancias vigentes no banco de dados, mantendo um histórico da evolução do esquema do banco de dados. É proposto um modelo flexível de suporte a evolução de esquemas em bancos de dados orientados a objetos, bem como estratégias de propagação das instancias vigentes na base de dados. O histórico das modificações é representado pela derivação de versões do esquema e de seus elementos. Os estados anteriores as transformações são preservados, permitindo aos usuários a navegação retroativa e proativa entre versões, para realização de operações consistentes de modificação e consulta. / Non-conventional applications such as CAD, CASE, office automation often require the maintenance of various database states, to keep track of the history of the performed updates. The concept of version is employed to support such requirement. In this work, the version model proposed by Golendziner is used in the schema evolution context. Versions are used to store the different states of the schema, classes and methods, as well as for the mapping of database instances among the various schema versions, thus keeping the history of the database schema evolution. A flexible model is proposed to support schema evolution in object-oriented databases, as well as the strategies to propagate the corresponding changes to the database instances. Versions of schema, as well as versions of the schema elements represent their evolution history. In the proposed model, previous states are preserved allowing the user to make queries about consistency and modifications in both backward and forward version.

Aplicações ditas não convencionais, como, por exemplo, CAD, CASE, Automação de Escritórios, entre outras, freqüentemente exigem a manutenção de diversos estados da base de dados, retendo o histórico das modificações realizadas. Como resposta a tal requisito, é empregado o conceito de Versão. Neste trabalho o Modelo de Versões proposto por Golendziner é empregado no contexto da evolução de esquemas. Versões são utilizadas para armazenar os diferentes estados do esquema, de suas classes e métodos e, ainda, para posterior adaptação das instancias vigentes no banco de dados, mantendo um histórico da evolução do esquema do banco de dados. É proposto um modelo flexível de suporte a evolução de esquemas em bancos de dados orientados a objetos, bem como estratégias de propagação das instancias vigentes na base de dados. O histórico das modificações é representado pela derivação de versões do esquema e de seus elementos. Os estados anteriores as transformações são preservados, permitindo aos usuários a navegação retroativa e proativa entre versões, para realização de operações consistentes de modificação e consulta. / Non-conventional applications such as CAD, CASE, office automation often require the maintenance of various database states, to keep track of the history of the performed updates. The concept of version is employed to support such requirement. In this work, the version model proposed by Golendziner is used in the schema evolution context. Versions are used to store the different states of the schema, classes and methods, as well as for the mapping of database instances among the various schema versions, thus keeping the history of the database schema evolution. A flexible model is proposed to support schema evolution in object-oriented databases, as well as the strategies to propagate the corresponding changes to the database instances. Versions of schema, as well as versions of the schema elements represent their evolution history. In the proposed model, previous states are preserved allowing the user to make queries about consistency and modifications in both backward and forward version.

Aplicações ditas não convencionais, como, por exemplo, CAD, CASE, Automação de Escritórios, entre outras, freqüentemente exigem a manutenção de diversos estados da base de dados, retendo o histórico das modificações realizadas. Como resposta a tal requisito, é empregado o conceito de Versão. Neste trabalho o Modelo de Versões proposto por Golendziner é empregado no contexto da evolução de esquemas. Versões são utilizadas para armazenar os diferentes estados do esquema, de suas classes e métodos e, ainda, para posterior adaptação das instancias vigentes no banco de dados, mantendo um histórico da evolução do esquema do banco de dados. É proposto um modelo flexível de suporte a evolução de esquemas em bancos de dados orientados a objetos, bem como estratégias de propagação das instancias vigentes na base de dados. O histórico das modificações é representado pela derivação de versões do esquema e de seus elementos. Os estados anteriores as transformações são preservados, permitindo aos usuários a navegação retroativa e proativa entre versões, para realização de operações consistentes de modificação e consulta. / Non-conventional applications such as CAD, CASE, office automation often require the maintenance of various database states, to keep track of the history of the performed updates. The concept of version is employed to support such requirement. In this work, the version model proposed by Golendziner is used in the schema evolution context. Versions are used to store the different states of the schema, classes and methods, as well as for the mapping of database instances among the various schema versions, thus keeping the history of the database schema evolution. A flexible model is proposed to support schema evolution in object-oriented databases, as well as the strategies to propagate the corresponding changes to the database instances. Versions of schema, as well as versions of the schema elements represent their evolution history. In the proposed model, previous states are preserved allowing the user to make queries about consistency and modifications in both backward and forward version.

M.A. / This study investigates the connection between the biblical references to the Gospels in Actae Thoma, or the Apocryphal Acts of Judas Thomas, and the text of the Vetus Syria. The main objective is to verify whether the author of Actae Thoma was dependent on the Vetus Syria which was one of the largest and oldest Syriac text families containing the separate Gospels. An independent study in this regard has not yet been undertaken. Both Klijn and Burkitt touched on the biblical references in Actae Thoma but they did not attempt to investigate the references as the sole object of their research. The present study attempts to investigate all the biblical references in order to verify whether the author of Actae Thoma was indeed dependent on the Vetus Syria. The function of these references within the new context of Actae Thoma is also investigated. The value of the study lies in its contribution to our understanding of the Syriac textual history and of the function of these references. It seems that they were used to propagate the ideals of asceticism, to enhance the figure of the Apostle and bring the reader under the impression that he finds himself in a Biblical milieu. A basis for further study is also provided.

- Pourquoi vous aimez faire des vidéos ? - Bah parce que... on me voit et ça fait du bien de voir les gens ! - Moi, c’est parce que… moi j’ai envie d’être une star de cinéma. Depuis quelques semaines dans cette classe de CP, l’enseignant cherche avec ses élèves comment son téléphone portable peut médiatiser efficacement l’apprentissage de l’écriture. Nous le rencontrons en novembre 2015 et introduisons dans la classe un artefact numérique qui vise à instrumenter les activités de production de contenus numériques des élèves.Cette thèse interroge la conception et l’évaluation d’artefacts numériques, et contribue à répondre à la question suivante : comment concevoir pour contribuer au développement des activités scolaires de manière durable ? Et comment les artefacts numériques participent-ils de ce développement ? Nous dessinons une approche développementale de la conception, qui propose de déplacer l’objet de la conception des artefacts aux formes de l’agir collectif ; approche que nous mettons en œuvre à travers une recherche action longitudinale ancrée en ergonomie dans la classe de CP d’une école publique. Nous proposons son pendant méthodologique, qui entend transformer autant que comprendre : une démarche de « recherche par version », construite à partir des démarches participatives en design d’interaction et de la théorie socio-culturelle de l’activité, qui met en avant la dimension développementale et sociale de l’agir. Notre étude a pour objet l’interrelation du développement des artefacts numériques et des personnes au sein de la classe de CP. Nous nous appuyons sur les concepts issus de l’approche instrumentale, qui permettent d’étudier les transformations des activités des personnes dans la classe, en considérant l’histoire socialement distribuée de la création de leurs instruments. Nous concluons sur l’intérêt de considérer la conception d’artefacts techniques comme un processus continu, situé et distribué. / - Why do you like making videos?- Mmmh, because… I can be seen, and it feels good to see people.- Me, it is because I would like to be a movie star. In a first graders classroom, a teacher and his pupils experiment the use of a smartphone to efficiently enhance the way pupils learn to write. I meet with him in November 2015 and I introduce a digital system in the classroom, aiming at mediating pupils’ production of digital content. This dissertation focuses on the design and evaluation of digital tools and addresses the following issue: how to design in order to develop educational activities in a sustainable way? And what roles do the artifacts play in this development?I propose a developmental approach to design, that envisions a change of object: instead of focusing on artifacts, I suggest that designing in a developmental perspective is concerns by the configurations of new forms of collective action. In this study, I apply this perspective in an elementary classroom in a public school in Paris. Aligned with this approach to design, I draw a methodology that helps me transform as much as study situated ways of acting. This methodology, closely related to action research, borrows from Participatory Design practices and values combined with a Cultural-Historical Activity Theory framework (CHAT). This study investigates the developmental processes of both artifacts and people in this first graders classroom, by tracking how artifacts are used and redesigned through the classroom’s practices, as much as they transform them. I conclude by discussing the benefit of adopting such a design approach, considering design as a situated, continuous and distributed process.

This master's thesis deals with the design and implementation of a database versions management process for software development team. The main task of this thesis is to set up tools and processes, used to help the team to manage their versions of database changes. In the first part, you may find theoretical foundations and comparison of the Liquibase and Flayway tools. In the second part, the design and solution implementation is proposed, using Jenkins, Liquibase and specially crafted Java tools.

We introduce end-to-end support of co-existing schema versions within one database. While it is state of the art to run multiple versions of a continuously developed application concurrently, it is hard to do the same for databases. In order to keep multiple co-existing schema versions alive|which are all accessing the same data set|developers usually employ handwritten delta code (e.g. views and triggers in SQL). This delta code is hard to write and hard to maintain: if a database administrator decides to adapt the physical table schema, all handwritten delta code needs to be adapted as well, which is expensive and error-prone in practice. In this paper, we present InVerDa: developers use the simple bidirectional database evolution language BiDEL, which carries enough information to generate all delta code automatically. Without additional e_ort, new schema versions become immediately accessible and data changes in any version are visible in all schema versions at the same time. InVerDa also allows for easily changing the physical table design without a_ecting the availability of co-existing schema versions. This greatly increases robustness (orders of magnitude less lines of code) and allows for signi_cant performance optimization. A main contribution is the formal evaluation that each schema version acts like a common full-edged database schema independently of the chosen physical table design.

A look into song identity and the building blocks of music through a process of analysing five different punk songs and then repackaging them into a modern pop production. After completing these new versions, I compared them to their original recordings and discovered that there are more similarities between the two genres than one might initially think, and that each song’s identity was preserved on slightly different levels and in different forms. I discuss my analyses and process in terms of both music theory and non-musical descriptions, leading to generally positive results. Each song was recognizable, but I discovered that some identities were stronger than others because of factors such as original arrangement, era of release or differences in experience from person to person.

No description available.