Relevant bibliographies by topics / Code source (informatique) – Documentation

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Code source (informatique) – Documentation'

Author: Grafiati
Published: 31 August 2024

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Code source (informatique) – Documentation.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Code source (informatique) – Documentation"

1

Wang 王冰, Bingjie 洁., Joel Leja, Ivo Labbé, Rachel Bezanson, Katherine E. Whitaker, Gabriel Brammer, Lukas J. Furtak, et al. "The UNCOVER Survey: A First-look HST+JWST Catalog of Galaxy Redshifts and Stellar Population Properties Spanning 0.2 ≲ z ≲ 15." Astrophysical Journal Supplement Series 270, no. 1 (December 28, 2023): 12. http://dx.doi.org/10.3847/1538-4365/ad0846.

Full text
Abstract:
Abstract The recent UNCOVER survey with the James Webb Space Telescope (JWST) exploits the nearby cluster A2744 to create the deepest view of our Universe to date by leveraging strong gravitational lensing. In this work, we perform photometric fitting of more than 50,000 robustly detected sources out to z ∼ 15. We show the redshift evolution of stellar ages, star formation rates, and rest-frame colors across the full range of 0.2 ≲ z ≲ 15. The galaxy properties are inferred using the Prospector Bayesian inference framework using informative Prospector-β priors on the masses and star formation histories to produce joint redshift and stellar populations posteriors. Additionally, lensing magnification is performed on the fly to ensure consistency with the scale-dependent priors. We show that this approach produces excellent photometric redshifts with σ NMAD ∼ 0.03, of a similar quality to the established photometric redshift code EAzY. In line with the open-source scientific objective of this Treasury survey, we publicly release the stellar population catalog with this paper, derived from our photometric catalog adapting aperture sizes based on source profiles. This release (the catalog and all related documentation are accessible via the UNCOVER survey web page: https://jwst-uncover.github.io/DR2.html#SPSCatalogs with a copy deposited to Zenodo at doi:10.5281/zenodo.8401181) includes posterior moments, maximum likelihood spectra, star formation histories, and full posterior distributions, offering a rich data set to explore the processes governing galaxy formation and evolution over a parameter space now accessible by JWST.
APA, Harvard, Vancouver, ISO, and other styles
2

Pan, Lu, Huy Q. Dinh, Yudi Pawitan, and Trung Nghia Vu. "Isoform-level quantification for single-cell RNA sequencing." Bioinformatics 38, no. 5 (December 2, 2021): 1287–94. http://dx.doi.org/10.1093/bioinformatics/btab807.

Full text
Abstract:
Abstract Motivation RNA expression at isoform level is biologically more informative than at gene level and can potentially reveal cellular subsets and corresponding biomarkers that are not visible at gene level. However, due to the strong 3ʹ bias sequencing protocol, mRNA quantification for high-throughput single-cell RNA sequencing such as Chromium Single Cell 3ʹ 10× Genomics is currently performed at the gene level. Results We have developed an isoform-level quantification method for high-throughput single-cell RNA sequencing by exploiting the concepts of transcription clusters and isoform paralogs. The method, called Scasa, compares well in simulations against competing approaches including Alevin, Cellranger, Kallisto, Salmon, Terminus and STARsolo at both isoform- and gene-level expression. The reanalysis of a CITE-Seq dataset with isoform-based Scasa reveals a subgroup of CD14 monocytes missed by gene-based methods. Availability and implementation Implementation of Scasa including source code, documentation, tutorials and test data supporting this study is available at Github: https://github.com/eudoraleer/scasa and Zenodo: https://doi.org/10.5281/zenodo.5712503. Supplementary information Supplementary data are available at Bioinformatics online.
APA, Harvard, Vancouver, ISO, and other styles
3

Couture, Stéphane. "L'écriture collective du code source informatique." Revue d'anthropologie des connaissances 6, 1, no. 1 (2012): 21. http://dx.doi.org/10.3917/rac.015.0061.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Boumann, K. "Terminologische Databank En Geautomatiseerde Informatie En Documentatie." Vertalen in theorie en praktijk 21 (January 1, 1985): 128–33. http://dx.doi.org/10.1075/ttwia.21.16bou.

Full text
Abstract:
This paper is essentially a progress report on - the European Community terminology data bank, known as Eurodicautom, - the machine translation projects Systran and Eurotra - access to Community, European and American data banks. Eurodicom is now a fully developed electronic dictionary, containing about 334.000 terminological units (single words, phrases and abbreviations) in English, 318.000 in French, 239.000 in German, 150.000 in Italian, 145.000 in Danish, 136.000 in Dutch, 64.000 in Spanish, 10.000 in Portuguese and 700 in Latin (5 November 1984). Translations are accompanied by descriptieve, linguistic and documentary information (viz. definition, context, source, originating office, author, subject code and reliability rating). Eurodicautom is also available to the public on-line (for details apply to Echo, Customer Service, 15 avenue de La Faïencerie, L-1510 Luxemburg, tel. 352-20764). At present Systran provides machine translations for the Language pairs English-French, French-English and English-Italian. English-German is being introduced and French-German will become available shortly. Consideration is being given to developing systems from either French or English into Greek, Danish or Dutch. (Report Ian M. Pigott, 29 May 1984). Rapid post-editing (emphasis on accuracy or full post-editing (thorough revision) is always required. Work on Eurotra, a machine translation system of advanced design, is now well under way (Preparatory phase, 2 years, is all but terminated). Unlike Systran (language pairs, one way) Eurotra will be set up to supply translations from any source language available in the system into a number of target languages. The first results are due by 1989, after a phase of basic and applied linguistic research (2 years) and a phase of stabilization of the linguistic models and evaluation of results (18 months). There is a brief outline of the objectives and the programme of work in Council Decision 82/752/EEC, Official Journal of the European Communities, 1982 No L 317, pp. 19-23. Translators can now be assisted by Information Officers to consult titles, abstracts and full articles in some 140 Community, European and American data systems.
APA, Harvard, Vancouver, ISO, and other styles
5

Al-Msie'deen, Ra'Fat, and Anas H. Blasi. "Supporting software documentation with source code summarization." International Journal of ADVANCED AND APPLIED SCIENCES 6, no. 1 (January 2019): 59–67. http://dx.doi.org/10.21833/ijaas.2019.01.008.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Sulír, Matúš, and Jaroslav Porubän. "Source Code Documentation Generation Using Program Execution." Information 8, no. 4 (November 17, 2017): 148. http://dx.doi.org/10.3390/info8040148.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Wu, Y. C., and T. P. Baker. "A source code documentation system for Ada." ACM SIGAda Ada Letters IX, no. 5 (July 1989): 84–88. http://dx.doi.org/10.1145/71340.71344.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Arthur, Menaka Pushpa. "Automatic Source Code Documentation using Code Summarization Technique of NLP." Procedia Computer Science 171 (2020): 2522–31. http://dx.doi.org/10.1016/j.procs.2020.04.273.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Carvalho, Nuno, Alberto Simões, and José Almeida. "DMOSS: Open source software documentation assessment." Computer Science and Information Systems 11, no. 4 (2014): 1197–207. http://dx.doi.org/10.2298/csis131005027c.

Full text
Abstract:
Besides source code, the fundamental source of information about open source software lies in documentation, and other non source code files, like README, INSTALL, or How-To files, commonly available in the software ecosystem. These documents, written in natural language, provide valuable information during the software development stage, but also in future maintenance and evolution tasks. DMOSS3 is a toolkit designed to systematically assess the quality of non source code content found in software packages. The toolkit handles a package as an attribute tree, and performs several tree traverse algorithms through a set of plugins, specialized in retrieving specific metrics from text, gathering information about the software. These metrics are later used to infer knowledge about the software, and composed together to build reports that assess the quality of specific features. This paper discusses the motivations for this work, continues with a description of the toolkit implementation and design goals. This is followed by an example of its usage to process a software package, and the produced report.
APA, Harvard, Vancouver, ISO, and other styles
10

Wang, April Yi, Dakuo Wang, Jaimie Drozdal, Michael Muller, Soya Park, Justin D. Weisz, Xuye Liu, Lingfei Wu, and Casey Dugan. "Documentation Matters: Human-Centered AI System to Assist Data Science Code Documentation in Computational Notebooks." ACM Transactions on Computer-Human Interaction 29, no. 2 (April 30, 2022): 1–33. http://dx.doi.org/10.1145/3489465.

Full text
Abstract:
Computational notebooks allow data scientists to express their ideas through a combination of code and documentation. However, data scientists often pay attention only to the code, and neglect creating or updating their documentation during quick iterations. Inspired by human documentation practices learned from 80 highly-voted Kaggle notebooks, we design and implement Themisto, an automated documentation generation system to explore how human-centered AI systems can support human data scientists in the machine learning code documentation scenario. Themisto facilitates the creation of documentation via three approaches: a deep-learning-based approach to generate documentation for source code, a query-based approach to retrieve online API documentation for source code, and a user prompt approach to nudge users to write documentation. We evaluated Themisto in a within-subjects experiment with 24 data science practitioners, and found that automated documentation generation techniques reduced the time for writing documentation, reminded participants to document code they would have ignored, and improved participants’ satisfaction with their computational notebook.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Code source (informatique) – Documentation"

1

Oumaziz, Mohamed Ameziane. "Cloning beyond source code : a study of the practices in API documentation and infrastructure as code." Thesis, Bordeaux, 2020. http://www.theses.fr/2020BORD0007.

Full text
Abstract:
Lors du développement de logiciels, la maintenance et l'évolution constituent une partie importante du cycle de vie du développement représentant 80% du coût et des efforts globaux.Au cours de la maintenance, il arrive que les développeurs aient copier-coller des fragments de code source afin de les réutiliser. Une telle pratique, apparemment inoffensive, est plus fréquente qu'on ne le pense.Communément appelés «clones» dans la littérature, ces doublons de code source sont un sujet bien connu et étudié en génie logiciel.Dans cette thèse, nous visons à mettre en lumière les pratiques du copier-coller sur les artefacts logiciels.En particulier, nous avons choisi de concentrer nos contributions sur deux types d'artefacts logiciels : Documentation d'API et fichiers de compilation (c.-à-d. Dockerfiles). Pour les deux contributions, nous suivons une méthodologie d'étude empirique commune.Tout d'abord, nous montrons que les documentations d'API et les fichiers de construction de logiciels (c.-à-d. Dockerfiles) sont confrontés à des problèmes de doublons et que de tels doublons sont fréquents.Deuxièmement, nous identifions les raisons derrière l'existence de ces doublons.Troisièmement, nous effectuons une enquête auprès de développeurs expérimentés et de constatons qu'ils sont conscients de ces doublons, et qu'ils les rencontrent souvent tout en ayant un avis mitigé sur eux.Enfin, nous montrons que les deux artefacts logiciels manquent de mécanismes de réutilisation pour faire face aux doublons, et que certains développeurs ont même recours à des outils ad-hoc pour les gérer
When developing a software, maintenance and evolution represents an important part of the development's life-cycle, making up to 80% of the overall cost and effort.During the maintenance effort, it happens that developers have to resort to copying and pasting source code fragments in order to reuse them.Such practice, seemingly harmless is more frequent than we expect.Commonly referred to as ``clones'' in the literature, these source code duplicates are a well-known and studied topic in software engineering.In this thesis, we aim at shedding some light on copy-paste practices on software artifacts. In particular, we chose to focus our contributions on two specific types of software artifacts: API documentation and build files (i.e. Dockerfiles).For both contributions, we follow a common empirical study methodology. First, We show that API documentations and software build files (i.e. Dockerfiles) actually face duplicates issues and that such duplicates are frequent.Secondly, we identify the reasons behind the existence of such duplicates.Thirdly, We perform a survey on experimented developers and find that they're aware of such duplicates, frequently face them. But still have a mixed opinion regarding them.Finally, We show that both software artifacts lack reuse mechanisms to cope with duplicates, and that some developers even resort to ad-hoc tools to manage them
APA, Harvard, Vancouver, ISO, and other styles
2

Latappy, Corentin. "Les pratiques de code : de la documentation à la détection." Electronic Thesis or Diss., Bordeaux, 2024. http://www.theses.fr/2024BORD0101.

Full text
Abstract:
Les pratiques de code sont de plus en plus utilisées dans le domaine du développement logiciel. Leur mise en place permet d’assurer la maintenabilité, la lisibilité et la consistance du code, ce qui contribue fortement à la qualité logicielle. La majorité de ces pratiques est implémentée dans des outils d’analyse statique, ou linters, qui permettent d’alerter automatiquement les développeurs lorsqu’une pratique n’est pas respectée. Toutefois, de plus en plus d’organisations, ayant tendance à créer leurs propres pratiques internes, rencontrent des problèmes sur leur compréhension et leur adoption par les développeurs. Premièrement, afin d’être appliquée, une pratique doit d’abord être comprise par les développeurs, impliquant donc d’avoir une documentation correctement rédigée. Or, ce sujet de la documentation n’a été que peu étudié dans la littérature scientifique. Ensuite, pour favoriser leur adoption, il faudrait pouvoir étendre les outils d’analyse existants pour y intégrer de nouvelles pratiques, ce qui est difficile compte tenu de l’expertise nécessaire pour apporter ces modifications. Packmind, société bordelaise, développe une solution pour accompagner les développeurs à faire émerger ces pratiques internes à l’aide d’ateliers. Cependant, elle souffre des mêmes problématiques citées précédemment. Dans cette thèse, nous nous sommes d’abord intéressés à fournir des recommandations aux auteurs de la documentation des pratiques. Pour cela, nous avons analysé la documentation de plus de 100 règles provenant de 16 linters différents afin d’en extraire une taxonomie des objectifs de documentation et des types de contenu présents. Nous avons ensuite réalisé une enquête auprès de développeurs afin d’évaluer leurs attentes en termes de documentation. Cela nous a notamment permis d’observer que les raisons pour lesquelles une pratique doit être appliquée étaient très peu documentées, alors qu’elles sont perçues comme essentielles par les développeurs. Dans un second temps, nous avons étudié la faisabilité de l’identification automatique de violations de pratiques à partir d’exemples. Notre contexte, nous contraignant à détecter des pratiques internes pour lesquelles nous avons peu d’exemples pour apprendre, nous a poussé à mettre en place du transfert d’apprentissage sur le modèle de machine learning CodeBERT. Nous montrons que les modèles ainsi entraînés obtiennent de bonnes performances dans un contexte expérimental, mais que la précision s’écroule lorsque nous les appliquons à des bases de code réelles
Coding practices are increasingly used in the field of software development. Their implementation ensures maintainability, readability, and consistency of the code, which greatly contributes to software quality. Most of these practices are implemented in static analysis tools, or linters, which automatically alert developers when a practice is not followed. However,more and more organizations, tending to create their own internal practices, encounter problems with their understanding and adoption by developers. First, for a practice to be applied, it must first be understood by developers, thus requiring properly written documentation. Yet, this topic of documentation has been little studied in the scientific literature. Then, to promote their adoption, it would be necessary to be able to extend existing analysis tools to integrate new practices, which is difficult given the expertise required to make these modifications. Packmind, a company based in Bordeaux, develops a solution to support developers in bringing out these internal practices through workshops. However, it suffers from the same issues mentioned above. In this thesis, we first focused on providing recommendations to the authors of practice documentation. To do this, we analyzed the documentation of more than 100 rules from 16 different linters to extract a taxonomy of documentation objectives and types of content present. We then conducted a survey among developers to assess their expectations in terms of documentation. This notably allowed us to observe that the reasons why a practice should be applied were very poorly documented, while they are perceived as essential by developers. Secondly, we studied the feasibility of automatically identifying violations of practices from examples. Our context, forcing us to detect internal practices for which we have few examples to learn from, pushed us to implement transfer learning on themachine learning model CodeBERT.We show that the models thus trained achieve good performance in an experimental context, but that accuracy collapseswhenwe apply them to real code bases
APA, Harvard, Vancouver, ISO, and other styles
3

Che, Denise. "Automatic documentation generation from source code." Thesis, Massachusetts Institute of Technology, 2016. http://hdl.handle.net/1721.1/112822.

Full text
Abstract:
Thesis: M. Eng., Massachusetts Institute of Technology, Department of Electrical Engineering and Computer Science, 2016.
This electronic version was submitted by the student author. The certified thesis is available in the Institute Archives and Special Collections.
Cataloged from student-submitted PDF version of thesis.
Includes bibliographical references (page 46).
Many systems lack robust documentation because writing documentation comes at a cost for developers and offers little immediate benefits. To motivate developers to write more documentation, we need a framework that beneficially incorporates documentation into the functionalities of the codebase. We explored this idea in the context of Exhibit, a data publishing framework developed at MIT CSAIL's Haystack group. Exhibit enables those without much programming experience to create data-rich interactive webpages. We created an automatic documentation system with an approach that motives the creation of rich specifications by developers, which leads to good documentation. The code required for documentation benefits developers by simplifying the codebase and providing fault tolerance through a modular error checking mechanism. This system intends to aid new and returning users of Exhibit in learning the Exhibit syntax and in creating their Exhibits by providing extensive, up-to-date documentation for all the available views and facets in Exhibit along with an interactive example component. The interactive example component provides an interface that allows users to experiment with combinations of the different settings and also aids developers during the unit testing process.
by Denise Che.
M. Eng.
APA, Harvard, Vancouver, ISO, and other styles
4

Jaeger, Julien. "Source-to-source transformations for irregular and multithreaded code optimization." Versailles-St Quentin en Yvelines, 2012. http://www.theses.fr/2012VERS0015.

Full text
Abstract:
Dans cette thèse, nous montrons que les optimisations source-à-source sont un moyen efficace pour générer des programmes irréguliers ou parallèles performants à partir d'une implémentation. Après avoir présenté l'évolution des architectures des processeurs, nous proposons deux méthodes distinctes. La première pour extraire des codelets d'un programme irréguliers, les optimiser et prédire les performances du programme modifié. L'autre pour limiter l'impact des problèmes d'alignements dus à la vectorisation ou aux conflits de bancs. Nous présentons aussi différentes techniques de parallélisation, l'une générant des codelets parallèles, l'autre ordonnançant un graphe de taches sur un système hétérogène
In this dissertation, we show that source-to-source optimization is an efficient method to generate a high performance program for irregular and heterogeneous code from a basic implementation. After describing the evolution of processor architectures, we provide two methods. The first one extract codelets from an irregular code, optimizing these codelets, and predicting the performance of the modified program. The other one limits the impact of alignment issues due to vectorization or bank conflicts. We also present two parallelization technics, one generating parallel codelets, the other scheduling a task graph on an heterogeneous system
APA, Harvard, Vancouver, ISO, and other styles
5

Tévar, Hernández Helena. "Evolution of SoftwareDocumentation Over Time : An analysis of the quality of softwaredocumentation." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-97561.

Full text
Abstract:
Software developers, maintainers, and testers rely on documentation to understandthe code they are working with. However, software documentation is perceivedas a waste of effort because it is usually outdated. How documentation evolvesthrough a set of releases may show whether there is any relationship between timeand quality. The results could help future developers and managers to improvethe quality of their documentation and decrease the time developers use to analyzecode. Previous studies showed that documentation used to be scarce and low inquality, thus, this research has investigated different variables to check if the qualityof the documentation changes over time. Therefore, we have created a tool thatwould extract and calculate the quality of the comments in code blocks, classes,and methods. The results have agreed with the previous studies. The quality of thedocumentation is affected to some extent through the releases, with a tendency todecrease.
APA, Harvard, Vancouver, ISO, and other styles
6

Depaz, Pierre. "The role of aesthetics in understanding source code." Electronic Thesis or Diss., Paris 3, 2023. http://www.theses.fr/2023PA030084.

Full text
Abstract:
Cette thèse examine comment les propriétés esthétiques du code source permettent la représentation d’espaces sémantiques programmés, et leur implication dans la compréhension de la fonction de processus computationels. Se basant sur un corpus de programmes-textes et des discours les accompagnant, nous montrons en quoi l’esthétique du code source est contingente d’autres domaines esthétiques littéraires, architecturaux et mathématiques, tout en demeurant dépendante du contexte au sein duquel circulent les programmes-textes, et se transformant à différentes échelles de lecture. En particulier, nous montrons que les propriétés esthétiques du code source permettent une certaine expressivité, en vertu de leur appartenance à une interface linguistique partagée et dynamique permettant de calculer le monde. Enfin, nous montrons comment une telle interface, organisée formellement, favorise la compression sémantique et l’exploration spatiale
This thesis investigates how the aesthetic properties of source code enable the representation of programmed semantic spaces, in relation with the function and understanding of computer processes. By examining program texts and the discourses around it, we highlight how source code aesthetics are both dependent on the context in which they are written, and contingent to other literary, architectural, and mathematical aesthetics, varying along different scales of reading. Particularly, we show how the aesthetic properties of source code manifest expressive power due to their existence as a dynamic, functional, and shared computational interface to the world, through formal organizations which facilitate semantic compression and spatial exploration
APA, Harvard, Vancouver, ISO, and other styles
7

Lebras, Youenn. "Code optimization based on source to source transformations using profile guided metrics." Thesis, Université Paris-Saclay (ComUE), 2019. http://www.theses.fr/2019SACLV037/document.

Full text
Abstract:
Le but est de développer d'un cadriciel permettant de définir les transformations de code source que nous jugeons judicieuses et sur la base de métriques dynamiques.Ce cadriciel sera ensuite intégré à la suite d'outil MAQAO, développée à l'UVSQ/ECR.Nous présentons des transformations source-à-source automatique guidées par l'utilisateur ansi que par les métriques dynamiques qui proviennent des différents outils d'analyse de MAQAO, afin de pouvoir travailler à la fois sur des objets sources et binaires.Ce cadriciel peut aussi servir de pré-processeur pour simplifier le développement en permettant d'effectuer certaines transformations simples mais chronophage et sources d'erreurs (i.e.: spécialisation de boucle ou fonction)
Our goal is to develop a framework allowing the definition of source code transformations based on dynamic metrics.This framework be integrated to the MAQAO tool suite developed at the UVSQ / ECR.We present a set of source-to-source transformations guidable by the end user and by the dynamic metrics coming from the various MAQAO tools in order to work at source and binary levels.This framework can also be used as a pre-processor to simplify the development by enabling to perform cleanly and automatically some simple but time-consuming and error-prone transformations (i.e .: loop/function specialization, ...)
APA, Harvard, Vancouver, ISO, and other styles
8

Chilowicz, Michel. "Recherche de similarité dans du code source." Phd thesis, Université Paris-Est, 2010. http://tel.archives-ouvertes.fr/tel-00587628.

Full text
Abstract:
La duplication de code source a de nombreuses origines : copie et adaptation inter-projets ou clonage au sein d'un même projet. Rechercher des correspondances de code copié permet de le factoriser dans un projet ou de mettre en évidence des situations de plagiat. Nous étudions des méthodes statiques de recherche de similarité sur du code ayant potentiellement subi des opérations d'édition telle que l'insertion, la suppression, la transposition ainsi que la factorisation et le développement de fonctions. Des techniques d'identification de similarité génomique sont examinées et adaptées au contexte de la recherche de clones de code source sous forme lexemisée. Après une discussion sur des procédés d'alignement de lexèmes et de recherche par empreintes de n-grams, est présentée une méthode de factorisation fusionnant les graphes d'appels de fonctions de projets au sein d'un graphe unique avec introduction de fonctions synthétiques exprimant les correspondances imbriquées. Elle utilise des structures d'indexation de suffixes pour la détermination de facteurs répétés. Une autre voie d'exploration permettant de manipuler de grandes bases indexées de code par arbre de syntaxe est abordée avec la recherche de sous-arbres similaires par leur hachage et leur indexation selon des profils d'abstraction variables. Des clones exacts de sous-arbres de forte proximité dans leurs arbres d'extraction peuvent alors être consolidés afin d'obtenir des correspondances approchées et étendues. En amont et en aval de la recherche de correspondances, des métriques de similarité sont définies afin de préselectionner les zones d'examen, affiner la recherche ou mieux représenter les résultats
APA, Harvard, Vancouver, ISO, and other styles
9

Habchi, Sarra. "Understanding mobile-specific code smells." Thesis, Lille 1, 2019. http://www.theses.fr/2019LIL1I089.

Full text
Abstract:
Au cours des dernières années, les applications mobiles sont devenues indispensables dans notre vie quotidienne. Ces applications ont pour particularité de fonctionner sur des téléphones mobiles, souvent limités en ressources (mémoire, puissance de calcul, batterie, etc). Ainsi, il est impératif de surveiller leur code source afin de s'assurer de l’absence de défauts de code, c.à.d., des pratiques de développement qui dégradent la performance. Plusieurs études ont été menées pour analyser les défauts de code des applications mobile et évaluer leur présence et leur impact sur la performance et l’efficience énergétique. Néanmoins, ces études n’ont pas examiné les caractéristiques et les motifs de ces défauts alors que ces éléments sont nécessaires pour la compréhension et la résolution de ce phénomène. L’objectif de cette thèse est de répondre à ce besoin en apportant des connaissances sur les défauts de code mobile. Pour cela, nous avons mené diverses études empiriques à caractère quantitatif et qualitatif pour comprendre ce phénomène et ses possibles résolutions. Les résultats de ces études montrent que les défauts de code mobile ne sont pas dus au pragmatisme, à la priorisation, ou aux comportements individuels des développeurs. En effet, l’essentielle raison derrière l’accumulation des défauts de code est l’ignorance générale de ces pratiques parmi les développeurs. Nos études ont aussi montré que le linter peut être un outil adéquat pour l’analyse des défauts de code et l’amélioration des performances. Cependant, certains défauts nécessitent une analyse dynamique pour une détection plus précise. Enfin, nous avons montré qu’il existe un écart entre les défauts de code étudiés par la communauté scientifique et les réelles mauvaises pratiques adoptées par les développeurs d’applications mobiles. Pour remédier à cet écart, nous recommandons à la communauté d’impliquer les développeurs dans le processus d’identification de défauts de code
Object-Oriented code smells are well-known concepts in software engineering. They refer to bad design and development practices commonly observed in software systems. With the emergence of mobile apps, new classes of code smells have been identified to refer to bad development practices that are specific to mobile platforms. These mobile-specific code smells differ from object-oriented ones by focusing on performance issues reported in the documentation or developer guidelines. Since their identification, many research works approached mobile-specific code smells to propose detection tools and study them. Nonetheless, most of these studies only focused on measuring the performance impact of such code smells and did not provide any insights about their motives and potential solutions. In particular, we lack knowledge about (i) the rationales behind the accrual of mobile code smells, (ii) the developers’ perception of mobile code smells, and (iii) the generalizability of code smells across different mobile platforms. These lacks hinder the understanding of mobile code smells and consequently prevent the design of adequate solutions for them. Therefore, we conduct in this thesis a series of empirical studies with the aim of understanding mobile code smells. First, we study the expansion of code smells in different mobile platforms. Then, we conduct a large-scale study to analyze the change history of mobile apps and discern the factors that favor the introduction and survival of code smells. To consolidate these studies, we also perform a user study to investigate developers’ perception of code smells and the adequacy of static analyzers as a solution for coping with them. Finally, we perform a qualitative study to question the established foundation about the definition and detection of mobile code smells. The results of these studies revealed important research findings. Notably, we showed that pragmatism, prioritization, and individual attitudes are not relevant factors for the accrual of mobile code smells. The problem is rather caused by ignorance and oversight, which are prevalent among mobile developers. Furthermore, we highlighted several flaws in the code smell definitions that are currently adopted by the research community. These results allowed us to elaborate some recommendations for researchers and tool makers willing to design detection and refactoring tools for mobile code smells. On top of that, our results opened perspectives for research works about the identification of mobile code smells and development practices in general
APA, Harvard, Vancouver, ISO, and other styles
10

Chaabane, Rim. "Analyse et optimisation de patterns de code." Paris 8, 2011. http://www.theses.fr/2011PA084174.

Full text
Abstract:
Our work is performed in the context of a financial company that develops and maintains legacy software. This software has been existing for more than twenty years, it was written in a proprietary, procedural and 4GL language called ADL (or Application Development Language). This software was initially developed for VMS system and deals with old generation of DBMS. For commercial reasons, the software has been ported to UNIX systems and to new RDBMS; Oracle and Sybase. It has also been extended to offer web interfaces. This legacy software has to face some new challenges as databases grow. During these last 20 years, some phenomenons like the merging of two companies, make data grow up to more than 1Terabyte and will reach 1Petabyte in a few years. In these new contexts, the ADL language shows limits to handle such a mass of data. Some patterns of code with database access have been suspected to be responsible for important decrease in performance. Our work consists in detecting all the instances of a suspected pattern of code in the source code or procedures, and identifying the instances of code, the most often called and the most time consuming. We developed a first tool called Adlmap, which is based on static analysis. It detects all DB accesses and flags those that are suspected patterns of code. The second tool we developed, named Pmonitor, is based on hybrid analysis; a combination of static and dynamic analysis. We use it to highlight inefficient code patterns instances
Notre travail consiste en l’analyse et l’optimisation du code source d’applications de type système hérité (ou legacy system). Nous avons particulièrement travaillé sur un logiciel, appelé GP3, qui est développé et maintenu par la société de finances Sungard. Ce logiciel existe depuis plus d’une vingtaine d’années, il est écrit en un langage propriétaire, procédural et de 4ème génération, appelé ADL (ou Application Development Language). Ce logiciel à été initialement développé sous VMS et accédait à des bases de données d’ancienne génération. Pour des raisons commerciales, il fut porté sous UNIX et s’adresse maintenant à des SGBD-R de nouvelles génération ; Oracle et Sybase. Il a également été étendu de manière à offrir une interface web. Ce système hérité doit maintenant faire face à de nouveaux défis, comme la croissance de la taille des bases de données. Durant ces 20 dernières années, nous avons pu observer la fusion de plusieurs entreprises, ce qui implique la fusion de bases de données. Ces dernières peuvent dépasser les 1 Téra de données et plus encore sont à prévoir à l’avenir. Dans ce nouveau contexte, le langage ADL montre des limites à traiter une aussi importante masse de données. Des patterns de code, désignant des structures d’accès en base, sont suspectés d’être responsables de dégradations des performances. Notre travail consiste à détecter toutes les instances de patterns dans le code source, puis d’identifier les instances les plus consommatrices en temps d’exécution et en nombre d’appels. Nous avons développé un premier outil, nommé Adlmap, basé sur l’analyse statique de code, et qui permet de détecter toutes les accès en base dans le code source. Les accès en base identifiés comme patterns de code sont marqués. Le second outil que nous avons développé, nommé Pmonitor, est basé sur une analyse hybride ; combinaison d’analyses statique et dynamique. Cet outil nous permet de mesurer les performances des patterns de code et ainsi, d’identifier les instances les moins performantes
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Code source (informatique) – Documentation"

1

Robinson, P. The CALIBRE source term code: Technical documentation for Project-90. Stockholm: Swedish Nuclear Power Inspectorate, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

C/C++ Treasure Chest: A Developer's Resource Kit of C/C++ Tools and Source Code. CMP Books, 1998.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Ada: 1.2 Gigabytes of Compilers, Documentation, Information, and Source Code, This Is a Valuable Resource for Any Ada Programmer. Walnut Creek, 1994.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

CP/M: Over 18000 Files With Executable Programs, Source Code, Documentation and Other Materials for the CP/m Operating System/Cd Rom in Jewel Box. Walnut Creek, 1994.

Find full text
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Code source (informatique) – Documentation"

1

Pauzi, Zaki, and Andrea Capiluppi. "Text Similarity Between Concepts Extracted from Source Code and Documentation." In Lecture Notes in Computer Science, 124–35. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-62362-3_12.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Xiong, Jay. "NSE Documentation Paradigm: Virtual, Traceable, and Consistent with the Source Code." In New Software Engineering Paradigm Based on Complexity Science, 489–515. New York, NY: Springer New York, 2010. http://dx.doi.org/10.1007/978-1-4419-7326-9_19.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Naus, Nico, Freek Verbeek, Dale Walker, and Binoy Ravindran. "A Formal Semantics for P-Code." In Lecture Notes in Computer Science, 111–28. Cham: Springer International Publishing, 2023. http://dx.doi.org/10.1007/978-3-031-25803-9_7.

Full text
Abstract:
AbstractDecompilation is currently a widely used tool in reverse engineering and exploit detection in binaries. Ghidra, developed by the National Security Agency, is one of the most popular decompilers. It decompiles binaries to high P-Code, from which the final decompilation output in C code is generated. Ghidra allows users to work with P-Code, so users can analyze the intermediate representation directly. Several projects make use of this to build tools that perform verification, decompilation, taint analysis and emulation, to name a few. P-Code lacks a formal semantics, and its documentation is limited. It has a notoriously subtle semantics, which makes it hard to do any sort of analysis on P-Code. We show that P-Code, as-is, cannot be given an executable semantics. In this paper, we augment P-Code and define a complete, executable, formal semantics for it. This is done by looking at the documentation and the decompilation results of binaries with known source code. The development of a formal P-Code semantics uncovered several issues in Ghidra, P-Code, and the documentation. We show that these issues affect projects that rely on Ghidra and P-Code. We evaluate the executability of our semantics by building a P-Code interpreter that directly uses our semantics. Our work uncovered several issues in Ghidra and allows Ghidra users to better leverage P-Code.
APA, Harvard, Vancouver, ISO, and other styles
4

Chardigny, Sylvain, and Abdelhak Seriai. "Software Architecture Recovery Process Based on Object-Oriented Source Code and Documentation." In Software Architecture, 409–16. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-15114-9_35.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Sarre, F., A. Myka, and U. Güntzer. "Hypertext for Software Engineering: Automatic Conversion of Source Code and its Documentation into an Integrated Hypertext." In Database and Expert Systems Applications, 463–68. Vienna: Springer Vienna, 1992. http://dx.doi.org/10.1007/978-3-7091-7557-6_79.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Gravino, Carmine, Michele Risi, Giuseppe Scanniello, and Genoveffa Tortora. "Do Professional Developers Benefit from Design Pattern Documentation? A Replication in the Context of Source Code Comprehension." In Model Driven Engineering Languages and Systems, 185–201. Berlin, Heidelberg: Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-33666-9_13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Santos, Geanderson, Amanda Santana, Gustavo Vale, and Eduardo Figueiredo. "Yet Another Model! A Study on Model’s Similarities for Defect and Code Smells." In Fundamental Approaches to Software Engineering, 282–305. Cham: Springer Nature Switzerland, 2023. http://dx.doi.org/10.1007/978-3-031-30826-0_16.

Full text
Abstract:
AbstractSoftware defect and code smell prediction help developers identify problems in the code and fix them before they degrade the quality or the user experience. The prediction of software defects and code smells is challenging, since it involves many factors inherent to the development process. Many studies propose machine learning models for defects and code smells. However, we have not found studies that explore and compare these machine learning models, nor that focus on the explainability of the models. This analysis allows us to verify which features and quality attributes influence software defects and code smells. Hence, developers can use this information to predict if a class may be faulty or smelly through the evaluation of a few features and quality attributes. In this study, we fill this gap by comparing machine learning models for predicting defects and seven code smells. We trained in a dataset composed of 19,024 classes and 70 software features that range from different quality attributes extracted from 14 Java open-source projects. We then ensemble five machine learning models and employed explainability concepts to explore the redundancies in the models using the top-10 software features and quality attributes that are known to contribute to the defects and code smell predictions. Furthermore, we conclude that although the quality attributes vary among the models, the complexity, documentation, and size are the most relevant. More specifically, Nesting Level Else-If is the only software feature relevant to all models.
APA, Harvard, Vancouver, ISO, and other styles
8

Saxena, Gaurav, Miguel Ponce-de-Leon, Arnau Montagud, David Vicente Dorca, and Alfonso Valencia. "BioFVM-X: An MPI+OpenMP 3-D Simulator for Biological Systems." In Computational Methods in Systems Biology, 266–79. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-85633-5_18.

Full text
Abstract:
AbstractMulti-scale simulations require parallelization to address large-scale problems, such as real-sized tumor simulations. BioFVM is a software package that solves diffusive transport Partial Differential Equations for 3-D biological simulations successfully applied to tissue and cancer biology problems. Currently, BioFVM is only shared-memory parallelized using OpenMP, greatly limiting the execution of large-scale jobs in HPC clusters. We present BioFVM-X: an enhanced version of BioFVM capable of running on multiple nodes. BioFVM-X uses MPI+OpenMP to parallelize the generic core kernels of BioFVM and shows promising scalability in large 3-D problems with several hundreds diffusible substrates and $$\approx $$ ≈ 0.5 billion voxels. The BioFVM-X source code, examples and documentation, are available under the BSD 3-Clause license at https://gitlab.bsc.es/gsaxena/biofvm_x.
APA, Harvard, Vancouver, ISO, and other styles
9

Hair, Joseph F., G. Tomas M. Hult, Christian M. Ringle, Marko Sarstedt, Nicholas P. Danks, and Soumya Ray. "Overview of R and RStudio." In Classroom Companion: Business, 31–47. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-80519-7_2.

Full text
Abstract:
AbstractComputational statistics is now an increasingly popular method of analysis for researchers that combines a vast array of algorithms, statistical methods, and the power of functional coding. The R programming language, in particular, has benefitted from this development alongside of traditional graphical user interface (GUI) software. Today, it has become the language of choice for empirical researchers. In this chapter, we introduce the R programming language as well as its popular development environment in the form of RStudio. We walk the reader through downloading both the R language and the RStudio integrated development environment (IDE). Then, we discuss the software layout and demonstrate how to interact with the software. Finally, we address creating and managing R projects and scripts, gaining access to documentation and help via various sources. This chapter is not intended as a tutorial on the writing of code in the R programming language. We do, however, provide useful open-source resources for learning R, which can be accessed from the R console RStudio environment.
APA, Harvard, Vancouver, ISO, and other styles
10

Breitmayer, Marius, Lisa Arnold, Stephan La Rocca, and Manfred Reichert. "Deriving Event Logs from Legacy Software Systems." In Lecture Notes in Business Information Processing, 409–21. Cham: Springer Nature Switzerland, 2023. http://dx.doi.org/10.1007/978-3-031-27815-0_30.

Full text
Abstract:
AbstractThe modernization of legacy software systems is one of the key challenges in software industry, which requires comprehensive system analysis. In this context, process mining has proven to be useful for understanding the (business) processes implemented by the legacy software system. However, process mining algorithms are highly dependent on both the quality and existence of suitable event logs. In many scenarios, existing software systems (e.g., legacy applications) do not leverage process engines capable of producing such high-quality event logs, which hampers the application of process mining algorithms. Deriving suitable event log data from legacy software systems, therefore, constitutes a relevant task that fosters data-driven analysis approaches, including process mining, data-based process documentation, and process-centric software migration. This paper presents an approach for deriving event logs from legacy software systems by combining knowledge from source code and corresponding database operations. The goal is to identify relevant business objects as well as to document user and software interactions with them in an event log suitable for process mining.
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Code source (informatique) – Documentation"

1

Kramer, Douglas. "API documentation from source code comments." In the 17th annual international conference. New York, New York, USA: ACM Press, 1999. http://dx.doi.org/10.1145/318372.318577.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

McBurney, Paul W. "Automatic Documentation Generation via Source Code Summarization." In 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering (ICSE). IEEE, 2015. http://dx.doi.org/10.1109/icse.2015.288.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Xiaofan Chen, J. Hosking, and J. Grundy. "Visualizing traceability links between source code and documentation." In 2012 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC 2012). IEEE, 2012. http://dx.doi.org/10.1109/vlhcc.2012.6344496.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Liu, Mingwei, Xin Peng, Xiujie Meng, Huanjun Xu, Shuangshuang Xing, Xin Wang, Yang Liu, and Gang Lv. "Source Code based On-demand Class Documentation Generation." In 2020 IEEE International Conference on Software Maintenance and Evolution (ICSME). IEEE, 2020. http://dx.doi.org/10.1109/icsme46990.2020.00114.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Durelli, Rafael S., Vinicius H. S. Durelli, Raphael W. Bettio, Diego R. C. Dias, and Alfredo Goldman. "Divinator: A Visual Studio Code Extension to Source Code Summarization." In Workshop de Visualização, Evolução e Manutenção de Software. Sociedade Brasileira de Computação - SBC, 2022. http://dx.doi.org/10.5753/vem.2022.226187.

Full text
Abstract:
Software developers spend a substantial amount of time reading and understanding code. Research has shown that code comprehension tasks can be expedited by reading the available documentation. However, documentation is expensive to generate and maintain, so the available documentation is often missing or outdated. Thus, automated generation of brief natural language descriptions for source code is desirable and has the potential to play a key role in source code comprehension and development. In particular, recent advances in deep learning have led to sophisticated summary generation techniques. Nevertheless, to the best of our knowledge, no study has fully integrated a state-of-the-art code summarization technique into an integrated development environment (IDE). In hopes of filling this gap, we developed a VS Code extension that allows developers to take advantage of state-of-the-art code summarization from within the IDE. This paper describes Divinator, our IDE-integrated tool for source code summarization.
APA, Harvard, Vancouver, ISO, and other styles
6

Moser, Michael, and Josef Pichler. "Documentation generation from annotated source code of scientific software." In ICSE '16: 38th International Conference on Software Engineering. New York, NY, USA: ACM, 2016. http://dx.doi.org/10.1145/2897676.2897679.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Favre, Jean-Marie, Ralf Lammel, Martin Leinberger, Thomas Schmorleiz, and Andrei Varanovich. "Linking Documentation and Source Code in a Software Chrestomathy." In 2012 19th Working Conference on Reverse Engineering (WCRE). IEEE, 2012. http://dx.doi.org/10.1109/wcre.2012.43.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Rebai, Soumaya, Oussama Ben Sghaier, Vahid Alizadeh, Marouane Kessentini, and Meriem Chater. "Interactive Refactoring Documentation Bot." In 2019 IEEE 19th International Working Conference on Source Code Analysis and Manipulation (SCAM). IEEE, 2019. http://dx.doi.org/10.1109/scam.2019.00026.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

McBurney, Paul W., and Collin McMillan. "Automatic documentation generation via source code summarization of method context." In the 22nd International Conference. New York, New York, USA: ACM Press, 2014. http://dx.doi.org/10.1145/2597008.2597149.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

McMillan, Collin, Denys Poshyvanyk, and Mark Grechanik. "Recommending source code examples via API call usages and documentation." In the 2nd International Workshop. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1808920.1808925.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Code source (informatique) – Documentation"

1

Gropp, W. Users manual for doctext: Producing documentation from C source code. Office of Scientific and Technical Information (OSTI), March 1995. http://dx.doi.org/10.2172/70803.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Code source (informatique) – Documentation' for particular source types:
Journal articles Dissertations / Theses
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography