Non Linear Software Documentation with Interactive Code Examples

Documentation enables sharing knowledge between the developers of a technology and its users. Creating quality documents, however, is challenging: Documents must satisfy the needs of a large audience without being overwhelming for individuals. We address this challenge with a new document format, named Casdoc. Casdoc documents are interactive resources centered around code examples for programmers. Explanations of the code elements are presented as annotations that the readers reveal based on their needs. We evaluated Casdoc in a field study with over 300 participants who used 126 documents as part of a software design course. The majority of participants adopted Casdoc instead of a baseline format during the study. We observed that interactive documents can contain more information than static documents without being distracting to readers. We also gathered insights into five aspects of Casdoc that can be applied to other formats, and propose five guidelines to improve navigability in online documents.Comment: 29 page

A Study of Documentation for Software Architecture

Documentation is an important mechanism for disseminating software architecture knowledge. Software project teams can employ vastly different formats for documenting software architecture, from unstructured narratives to standardized documents. We explored to what extent this documentation format may matter to newcomers joining a software project and attempting to understand its architecture. We conducted a controlled questionnaire-based study wherein we asked 65 participants to answer software architecture understanding questions using one of two randomly-assigned documentation formats: narrative essays, and structured documents. We analyzed the factors associated with answer quality using a Bayesian ordered categorical regression and observed no significant association between the format of architecture documentation and performance on architecture understanding tasks. Instead, prior exposure to the source code of the system was the dominant factor associated with answer quality. We also observed that answers to questions that require applying and creating activities were statistically significantly associated with the use of the system's source code to answer the question, whereas the document format or level of familiarity with the system were not. Subjective sentiment about the documentation format was comparable: Although more participants agreed that the structured document was easier to navigate and use for writing code, this relation was not statistically significant. We conclude that, in the limited experimental context studied, our results contradict the hypothesis that the format of architectural documentation matters. We surface two more important factors related to effective use of software architecture documentation: prior familiarity with the source code, and the type of architectural information sought.Comment: accepted to EMSE

Le traitement du trouble délirant et ses aspects cognitifs

Cet article fait état de la phénoménologie cognitive du trouble délirant (TD) et examine les modèles cognitifs actuels. Des études de cas ont mis à jour des résultats forts prometteurs concernant l'utilisation de la thérapie cognitivo-comportementale (TCC) pour traiter le TD, même si cette dernière n'en est qu'à ses débuts dans ce domaine. Bien que les étapes de la TCC pour traiter le TD soient très similaires à ceux de la TCC pour les autres troubles psychotiques, son approche comporte des différences considérables. Toutefois, il est primordial de combiner plusieurs stratégies afin de pouvoir modifier les inférences propres au TD. L'évaluation clinique des délires ainsi que l'application de la TCC comme traitement seront illustrées par deux études de cas comportant des diagnostics de TD à thème prédominant de persécution. Les cas ont requis des périodes de temps différentes lors des diverses étapes de la TCC, suggérant l'importance de poursuivre la TCC au besoin.Cognitive aspects and treatment of delusional disorders This article reviews the cognitive phenomenology of delusional disorders (DD) and examines the current cognitive models. Some case studies have shown considerable promise concerning the utilisation of cognitive behavioral therapy (CBT) for the treatment of DD, even if this approach is in its infancy. Although the stages of CBT to treat DD are very similar to that of other psychotic disorders, there are also considerable differences. However, it is essential to combine several strategies in order to modify inferences specific to DD. The clinical evaluation of delusions as well as the application of CBT as a treatment is illustrated in two cases with a diagnosis of DD with persecutory subtype. The cases required different time periods for different stages of CBT and highlight the importance of tailoring CBT according to need.El tratamiento del trastorno delirante y sus aspectos cognitivos Este artículo tiene en cuenta la fenomenología cognitiva del trastorno delirante (TD) y examina los modelos congnitivos actuales. Investigaciones recientes han puesto al día resultados prometedores referente a la utilisación de la terapia cognitiva-comportamiento (TCC) para tratar el TD, aunque esta última esté empesando en este campo. Aunque las etapas de la TCC para tratar el TD sean similares a los de la TCC para otros trastornos psicóticos, su aproximación comporte diferencias considerables. Sin embargo es primordial combinar varias estrategias para modifiar las inferencias propias al TD. La evaluación clínica de los delirios asi que la aplicación de la TCC como tratamiento son ilustrados por dos estudios de casos incluyendo diagnósticos de TD con tema predominante de persecusión. Los casos han requerido periodas de tiempo diferentes durante las varias etapas de la TCC, sugeriendo la importancia de seguir con la TCC si es preciso

Cellulose Gum: a new additive for wine tartaric stability. Tentative of structures determination involved in the haze formation after CMC addition in wine

International audienceCellulose gum (or sodium carboxymethylcellulose / CMC) is a new additive permitted by the European Community for tartaric stabilization (maximum dosage: 10g/HL). CMC is known to have a high eciency for potassium bitartrate and calcium tartrate crystallization inhibition in white and sparkling wines. Hypotheses suggest an inhibition of the nuclei growth at the beginning of their formation. However some problems remain, such as the formation of a low increase of the turbidity in white wine (from 0,1 to 0,4 NTU at room temperature) requiring a ltration step and the formation of a high lumps volume when CMC is used in some red wines. The goal of the following experiments was to determine which molecules are involved in the haze formed in white or red wines. 1. On white wines: A unique Sauvignon wine is treated from 0 up to 600mg/L of activated bentonite. After ltration, each batch was added (or not) with 100mg/L of CMC previously dissolved in tap water (conc.:50g/L). After 1 week of storage at 13°C, samples were heated at 80°C during ½ h and then stored at RT during 24h before running turbidity. 2. On red wines: 1L of red wine (blend of Cinsault, Merlot and Cab. Sauvignon) was added with 100mg/L of CMC (see above) and stored at-4°C for 4 days. After this time, the wine showed a high level of red clouds. At negative temperature, the deposit was ltered on 0.2 µm nitrocellulose lter membrane and extensively washed with a hydro-alcoholic solution (12% ethanol v/v-pH: 3,5/HCl) kept at-4°C. The membrane was then dried under vacuum and the deposit was collected and exchanged 3 times with D2O for H1-NMR study (HRMAS)

Overcoming Language Dichotomies: Toward Effective Program Comprehension for Mobile App Development

Mobile devices and platforms have become an established target for modern software developers due to performant hardware and a large and growing user base numbering in the billions. Despite their popularity, the software development process for mobile apps comes with a set of unique, domain-specific challenges rooted in program comprehension. Many of these challenges stem from developer difficulties in reasoning about different representations of a program, a phenomenon we define as a "language dichotomy". In this paper, we reflect upon the various language dichotomies that contribute to open problems in program comprehension and development for mobile apps. Furthermore, to help guide the research community towards effective solutions for these problems, we provide a roadmap of directions for future work.Comment: Invited Keynote Paper for the 26th IEEE/ACM International Conference on Program Comprehension (ICPC'18