Hans-Georg Gadamer et l'herméneutique théologique : idées directrices pour la compréhension de soi de la théologie

Mémoire numérisé par la Division de la gestion de documents et des archives de l'Université de Montréal

Influence d’un atelier de prise de notes sur la capacité d’étudiants du collégial à restituer les idées principales d’un texte de philosophie : une vision contrastive étudiants – professeurs de philosophie.

Cette recherche avait pour but de déterminer quelle était l’influence de l’administration d’un atelier de prise de notes dans le cadre du premier cours de philosophie du collégial qui se donnait au début de la deuxième session des apprenants. Elle se situait dans le cadre d’une recherche intervention et le point de vue des parties prenantes, à savoir les apprenants et les enseignants, était recueilli de façon qualitative. Les premiers, forts d’une expérience d’une session au niveau collégial, ont exprimé le besoin de suivre une formation formelle liée à la prise de notes, quand bien même celle-ci leur demanderait un effort supplémentaire. Les deuxièmes nous ont fait part de leurs préoccupations en ce qui a trait à la qualité des notes de leurs étudiants. Nous avons demandé aux répondants de restituer les thèmes principaux de deux textes équivalents distribués de façon simultanée en fonction des rangées (première rangée – premier texte, deuxième rangée – deuxième texte, etc.), puis nous avons interverti l’ordre de distribution des textes après l’atelier. Lors de l’analyse des résultats, nous avons constaté que les répondants avaient restitué les thèmes dans un ordre d’importance plus approprié après l’atelier qu’avant celui-ci, mais nous avons surtout remarqué une amélioration significative dans l’emploi des stratégies de prise de notes et dans la constance de leur utilisation tout au long du second texte étudié.

Quelques idées sur le musée comme institution politique

Il n'y a rien de plus politique que la volonté de jouer un rôle dans le changement des sociétés, des techniques, des cultures, des économies, des relations internationales, des modes de développement. C'est même une idée subversive, qui ne plaît pas toujours aux politiciens et aux technocrates.

Indicador de desenvolvimento econômico e social (IDES) dos estados brasileiros

Estudo realizado com base no período de 2001 a 2007, contemplando todas as unidades federativas do Brasil, classificadas a partir de uma análise comparativa da performance de cada uma delas. Na elaboração deste Indicador, mais de trinta variáveis socioeconômicas foram consideradas, segmentadas em cinco subindicadores como renda e desigualdade, moradia e saneamento básico, trabalho e desemprego, educação e saúde. Todas estas variáveis foram prospectadas a partir das principais fontes de dados brasileiras como o PNAD (IBGE), IETS e DATASUS (Ministério da Saúde). Um dos principais objetivos norteadores deste estudo foi criar um indicador que pudesse avaliar, de maneira abrangente e estatisticamente consistente, o desenvolvimento socioeconômico e o progresso recente dos estados brasileiros.

Supporting Task-oriented Navigation in IDEs with Configurable HeatMaps

Mainstream IDEs generally rely on the static structure of a software project to support browsing and navigation. We propose HeatMaps, a simple but highly configurable technique to enrich the way an IDE displays the static structure of a software system with additional kinds of information. A heatmap highlights software artifacts according to various metric values, such as bright red or pale blue, to indicate their potential degree of interest. We present a prototype system that implements heatmaps, and we describe an initial study that assesses the degree to which different heatmaps effectively guide developers in navigating software.

Augmenting Static Source Views in IDEs with Dynamic Metrics

Mainstream IDEs such as Eclipse support developers in managing software projects mainly by offering static views of the source code. Such a static perspective neglects any information about runtime behavior. However, object-oriented programs heavily rely on polymorphism and late-binding, which makes them difficult to understand just based on their static structure. Developers thus resort to debuggers or profilers to study the system's dynamics. However, the information provided by these tools is volatile and hence cannot be exploited to ease the navigation of the source space. In this paper we present an approach to augment the static source perspective with dynamic metrics such as precise runtime type information, or memory and object allocation statistics. Dynamic metrics can leverage the understanding for the behavior and structure of a system. We rely on dynamic data gathering based on aspects to analyze running Java systems. By solving concrete use cases we illustrate how dynamic metrics directly available in the IDE are useful. We also comprehensively report on the efficiency of our approach to gather dynamic metrics.

Autumn Leaves: Curing the Window Plague in IDEs

Navigating large software systems is difficult as the various artifacts are distributed in a huge space, while the relationships between different artifacts often remain hidden and obscure. As a consequence, developers using a modern interactive development environment (IDE) are forced to open views on numerous source artifacts to reveal these hidden relationships, leading to a crowded workspace with many opened windows or tabs. Developers often lose the overview in such a cluttered workspace as IDEs provide little support to get rid of unused windows. AutumnLeaves automatically selects windows unlikely for future use to be closed or grayed out while important ones are displayed more prominently. This reduces the number of windows opened at a time and adds structure to the developer's workspace. We validate AutumnLeaves with a benchmark evaluation using recorded navigation data of various developers to determine the prediction quality of the employed algorithms.

Embedding Moose Facilities Directly in IDEs

Moose is a powerful reverse engineering platform, but its facilities and means to analyze software are separated from the tools developers typically use to develop and maintain their software systems: development environments such as Eclipse, VisualWorks, or Squeak. In practice, this requires developers to work with two distinct environments, one to actually develop the software, and another one (e.g., Moose) to analyze it. We worked on several different techniques, using both dynamic and static analyzes to provide software analysis capabilities to developers directly in the IDE. The immediate availability of analysis tools in an IDE significantly increases the likelihood that developers integrate software analysis in their daily work, as we discovered by conducting user studies with developers. Finally, we identified several important aspect of integrating software analysis in IDEs that need to be addressed in the future to increase the adoption of these techniques by developers.