Die zunehmende Verbreitung von Low-Code-Entwicklungsplattformen, exemplarisch vertreten durch Microsoft Power Apps, in Industrie und Wissenschaft verändert die traditionelle Softwareentwicklungslandschaft grundlegend. Standardisiertes Verfahren zur Codierung und Dokumentation existiert noch nicht, sind aber zwingend notwendig. Vor diesem Hintergrund wird in der vorliegenden Bachelorarbeit zunächst ein Überblick über etablierte Praktiken der Quellcodedokumentation in der traditionellen Softwareentwicklung gegeben, um anschließend die Grundlagen der Low-Code-Entwicklung und deren Dokumentation zu untersuchen. Das Ziel dieser Arbeit besteht darin, ein Verfahren zu konzipieren und zu entwickeln, welches auf Basis klassischer Dokumentationsansätze der Softwareentwicklung die Erstellung von Dokumentation im Low-Code-Bereich vereinfacht und zu einer Standardisierung von Dokumentationspraktiken in Low-Code-Umgebungen beiträgt. Dadurch sollen letztlich die Nutzung und Wartung von Low-Code-Anwendungen optimiert werden. Zentraler Bestandteil der Arbeit ist die Entwicklung eines Prototyps für einen Dokumentationsgenerator. Dieser extrahiert automatisch wesentliche Informationen und Dokumentationskommentare aus dem zugrundeliegenden Power Apps Code, um eine zugängliche und konsistente Dokumentation zu erzeugen. Indem Informationen aus dem zugrunde liegenden Code extrahiert und in eine lesbare und verständliche Dokumentation umgewandelt werden, soll die Lücke zwischen der intuitiven, visuellen Erstellung von Anwendungen und der erforderlichen technischen Dokumentation geschlossen werden. Die Besonderheiten der Dokumentationsstruktur im Kontext von Low-Code werden hervorgehoben, insbesondere die Darstellung von Komponenten und Screens anstelle traditioneller Einteilung in Klassen und Funktionen.:1.1 Problemstellung und Fragestellung 1.2 Struktur der Arbeit 2 Grundlagen 2.1 Erklärung und Einordnung von Softwaredokumentation 2.1.1 Quellcodedokumentation 2.1.2 Nutzen von Quellcodedokumentation 2.1.3 Anforderung an gute Quellcodekommentare 2.1.4 Probleme bei der Quellcodedokumentation 2.1.5 Dokumentationsgeneratoren 2.1.6 Anforderung an gute Dokumentation 2.2 Begriffsklärung Low-Code/No-Code-Application 2.2.1 Struktureller Aufbau und Allgemeine Funktionen von LCDP 2.2.2 Aktuelle Bedeutung und Entwicklungstendenz von LC 2.3 Developer Experience DE X und Designgrundlagen 2.3.1 nutzungsfreundliches und ansprechendes Informationsdesign 2.3.2 Gestaltgesetze 3 Stand der Technik 3.1 Prinzipien und Anwendung der klassischen Code-Dokumentation 3.1.1 JavaDoc 3.1.2 Doxygen 3.1.3 Kritische Analyse der Dokumentation mit Dokumentationsgeneratoren 3.2 Überblick über andere Low-Code-Plattformen 3.2.1 Mendix 3.2.2 OutSystem 3.3 Microsoft Power Apps 3.3.1 Power Apps Studio . 3.3.2 Power Apps Komponenten 3.3.3 Microsoft Power Fx 3.3.4 Application Lifecycle Management mit Power Plattform 3.4 Spezifische Herausforderungen in der Dokumentation von Low-Code 3.5 Ansätze zu Lösung der Dokumentation in Low-Code 3.5.1 Mendix - Dokumentation 3.5.2 OutSystem - Dokumentation 3.6 Lösungsansätze für die Dokumentation in Microsoft Power Apps 3.6.1 Microsoft Power Apps - manuelle Dokumentationansätze 3.6.2 Microsoft Power Apps - PowerDoku von R. Modery 3.6.3 Microsoft Power Apps - powerapps-docstring von S. Muthwill 3.7 Einordnung der Arbeit 4 metaDOCU - ein Verfahren zur Low-Code Dokumentation 4.1 Speicherstruktur Power App 4.2 Architekturdiagramm 4.3 Kernprinzipien 4.3.1 Pattern Matching 4.3.2 Rekursion 4.4 Ausführung von metaDOCU 5 Anforderungen an LC-Dokumentation und Spezifikationen in metaDOCU 5.1 Dokumentationskommentare 5.2 Dokumentationsaufbau 5.3 Individualisierungsmöglichkeiten durch den Nutzenden 5.4 Hinweise auf Fehler 6 Bewertung von metaDOCU . 7 Zusammenfassung / The increasing spread of low-code development platforms, exemplified by Microsoft PowerApps, within both industrial and scientific spheres, is catalyzing a fundamental shift in the software development paradigm. Despite the simplifications that these platforms offer through visual programming and abstraction of the underlying code, the necessity of documenting the developed program code and the logic behind it remains valid, both for traceability during project handover and team collaboration as well as for the long-term maintainability of the applications. \\ Due to the relative novelty of low-code compared to classical programming, there is a lack of clear structuring of concepts, methodologies, and management strategies. Consequently, it is not surprising that there is no standardized procedure for coding and documentation in this area. Against this background, this bachelor thesis first provides an overview of the source code documentation practices that are established in traditional software development and also sheds light on the basics of low-code development. The aim is to highlight the need for code documentation in low-code environments and to analyze existing approaches in this area, with a particular focus on Microsoft PowerApps. Central to this is the development and investigation of a prototype for a documentation generator that can automatically generate documentation in low-code environments.:1.1 Problemstellung und Fragestellung 1.2 Struktur der Arbeit 2 Grundlagen 2.1 Erklärung und Einordnung von Softwaredokumentation 2.1.1 Quellcodedokumentation 2.1.2 Nutzen von Quellcodedokumentation 2.1.3 Anforderung an gute Quellcodekommentare 2.1.4 Probleme bei der Quellcodedokumentation 2.1.5 Dokumentationsgeneratoren 2.1.6 Anforderung an gute Dokumentation 2.2 Begriffsklärung Low-Code/No-Code-Application 2.2.1 Struktureller Aufbau und Allgemeine Funktionen von LCDP 2.2.2 Aktuelle Bedeutung und Entwicklungstendenz von LC 2.3 Developer Experience DE X und Designgrundlagen 2.3.1 nutzungsfreundliches und ansprechendes Informationsdesign 2.3.2 Gestaltgesetze 3 Stand der Technik 3.1 Prinzipien und Anwendung der klassischen Code-Dokumentation 3.1.1 JavaDoc 3.1.2 Doxygen 3.1.3 Kritische Analyse der Dokumentation mit Dokumentationsgeneratoren 3.2 Überblick über andere Low-Code-Plattformen 3.2.1 Mendix 3.2.2 OutSystem 3.3 Microsoft Power Apps 3.3.1 Power Apps Studio . 3.3.2 Power Apps Komponenten 3.3.3 Microsoft Power Fx 3.3.4 Application Lifecycle Management mit Power Plattform 3.4 Spezifische Herausforderungen in der Dokumentation von Low-Code 3.5 Ansätze zu Lösung der Dokumentation in Low-Code 3.5.1 Mendix - Dokumentation 3.5.2 OutSystem - Dokumentation 3.6 Lösungsansätze für die Dokumentation in Microsoft Power Apps 3.6.1 Microsoft Power Apps - manuelle Dokumentationansätze 3.6.2 Microsoft Power Apps - PowerDoku von R. Modery 3.6.3 Microsoft Power Apps - powerapps-docstring von S. Muthwill 3.7 Einordnung der Arbeit 4 metaDOCU - ein Verfahren zur Low-Code Dokumentation 4.1 Speicherstruktur Power App 4.2 Architekturdiagramm 4.3 Kernprinzipien 4.3.1 Pattern Matching 4.3.2 Rekursion 4.4 Ausführung von metaDOCU 5 Anforderungen an LC-Dokumentation und Spezifikationen in metaDOCU 5.1 Dokumentationskommentare 5.2 Dokumentationsaufbau 5.3 Individualisierungsmöglichkeiten durch den Nutzenden 5.4 Hinweise auf Fehler 6 Bewertung von metaDOCU . 7 Zusammenfassung

Le code génétique est la table de correspondance entre codons (unité structurelle d'un gène) et acides aminés (brique élémentaire des protéines). Le code génétique est (1) universel, tous les êtres vivants ou presque partagent le même code; (2) univoque, chaque codon spécifie un seul acide aminé et (3) dégénéré, les acides aminés peuvent être codés par plusieurs codons. Ce code dégénéré est donc utilisé par l'ensemble du vivant mais pas de la même manière, certains codons synonymes étant utilisés préférentiellement chez des espèces et pas d'autres. Pour comprendre l'émergence des biais d'usage du code (BUC) génétique entre espèces, je me place dans un contexte évolutif.Dans ce manuscrit, je présente mes travaux de recherche en quatre parties. La première partie introductive décrit la mise en évidence et les propriétés du code génétique, son biais d'usage et les diverses caractéristiques de précédents modèles de codons. La deuxième partie présente le modèle d'évolution de codons SENCA pour Sites Evolution at the Nucleotides, Codons and Amino-acids layers que j'ai développé durant ma thèse. SENCA prend en compte la structure du code génétique. Je valide sa paramétrisation par des simulations numériques et une étude sur des espèces bactériennes ou archées. La partie suivante décrit deux extensions de SENCA qui modélisent plusieurs hypothèses d'origines évolutives du BUC et une application de SENCA sur les conséquences génomiques d'adaptations environnementales. La dernière partie étudie les origines de variations de BUC le long du génome humain par une approche de génomique comparative / In this manuscript, I introduce my doctoral research in four parts. The first introductive part highlights the properties of the genetic code and its usage bias but also the caracteristics of previous published codons models. The second part presents an evolutionary codons models named SENCA for Sites Evolution at the Nucleotides, Codons and Amino-acids layers that I developped. SENCA takes into account the genetic code structure. I perform simulations and study prokaryotes species to confirm its parametrization. The following part provides two extensions of SENCA to test the hypotheses concerning the evolutive origins of CUB and an application of SENCA to study the genomic consequences of an environmental adaptation. The last part studies the origins of CUB variation within the human genome using a comparative genomic strategy

Neste trabalho calculamos o peso e a dimensão de todos os códigos cíclicos de comprimento pn na álgebra de grupo FqCpn, onde p é um número primo e Fq é um corpo finito de característica q. Também calculamos o peso do código dado pela soma de dois códigos abelianos minimais em Fq(Cp × Cp), dessa forma foi possível fazer uma breve comparação entre códigos cíclicos e abelianos não cíclicos de comprimento p2. / In this work we compute the weight and the dimension of all cyclic codes of length pn in the group algebra FqCpn, where p is a prime number and Fq is a finite field of characteristic q. Furthermore, we compute the weight of codes which are given by the sum of two minimal abelian codes in Fq(Cp × Cp). In this way, it was possible to compare briefly cyclic codes and non-cyclic abelian codes of length p2.

No description available.

A mature code-base of 1 300 000 LOC for a period of 20 months has been examined. This paper investigates if churn is a significant factor in finding refactoring candidates. In addition it looks at the variables Lines of Code (LOC), Technical Debt (TD), Duplicated lines and Complexity to find out if any of these indicators can inform a coder as to what to refactor. The result is that churn is the strongest variable out of the studied variables followed by LOC and TD. / En kodbas på 1 300 000 rader kod har undersökts under 20 månader. Denna uppsats undersöker om kodens användningsfrekvens är en signifikant faktor för att finna refaktoreringskandidater. Uppsatsen tittar även antal kodrader, teknisk skuld, antal duplicerade kodrader och komplexitet för att undersöka om dessa indikatorer kan informera en programmerare om vad som ska refaktoreras. Resultatet är att kodens användningsfrekvens är den starkaste variabeln följt av antal kodrader samt teknisk skuld.

Le phénomène de l'alternance codique a été connu et étudié depuis le début du XXe siècle. L'intérêt psycholinguistique à l'alternance codique orale a été suivi par des perspectives socio-pragmatiques dans la seconde moitié du XXe siècle ; puis vers la fin du siècle, l'attention des chercheurs a été attirée sur l'alternance codique écrite. Même si l'alternance codique a été bien étudié depuis, il y a encore quelques lacunes. Par exemple, l'intersection de l'écriture bilingue et la critique génétique présente une source de données naturalistes bilingues écrites qui restent fortement peu étudiées. Cette thèse tente de combler cette lacune en fournissant une analyse qualitative et quantitative des brouillons d'examen des apprenants de langue seconde. L'approche multimodale englobe la perspective visuelle, pragmatique et linguistique. Les résultats montrent que l'alternance codique représente un outil que les élèves utilisent habilement dans leur écriture personnelle académique. Néanmoins, les objectifs de son utilisation diffèrent non seulement entre les individus mais aussi entre les sociétés / communautés. Cela souligne la valeur sociolinguistique de l'écriture personnelle bilingue. Ce travail démontre également l'alternance codique dans l'écriture personnelle comme un type indépendant de l'alternance codique, qui peut prendre une place égale à côté de l'alternance codique orale, écrite et littéraire et qui mérite d'être étudié en tant que tel. / The phenomenon of code-switching has been known and researched since the beginning of the 20th century. The psycholinguistic interest in spoken code-switching was followed by socio-pragmatic perspectives in the second half of the 20th century; then towards the end of the century, researchers' attention was drawn to code-switching in writing. Even though language alternation has been well studied since, there are still some lacunae. For example, the intersection of bilingual writing and genetic criticism presents a source of naturalistic bilingual written data which remains significantly under-studied. The present thesis attempts to fill this gap by providing a qualitative and quantitative analysis of second-language learners' examination drafts. The multimodal approach encompasses the visual, the pragmatic and the linguistic perspectives. The findings show that code-switching represents a tool which students skillfully use in their academic personal writing. However, the purposes of its use differ not only among individuals but also among societies/communities. This emphasizes the sociolinguistic value of bilingual personal writing. This work also recognizes code-switching in personal writing as an independent type of code-switching, which can be placed in line with the oral, written and literary code-switching and which merits to be studied as such.

The need for automated methods for identifying refactoring items is prelevent in many software projects today. Symptoms of refactoring needs is the concept of code smells within a software system. Recent studies have used single model machine learning to combat this issue. This study aims to test the possibility of improving machine learning code smell detection using ensemble methods. Therefore identifying the strongest ensemble model in the context of code smells and the relative sensitivity of the strongest perfoming ensemble identified. The ensemble models performance was studied by performing experiments using WekaNose to create datasets of code smells and Weka to train and test the models on the dataset. The datasets created was based on Qualitas Corpus curated java project. Each tested ensemble method was then compared to all the other ensembles, using f-measure, accuracy and AUC ROC scores. The tested ensemble methods were stacking, voting, bagging and boosting. The models to implement the ensemble methods with were models that previous studies had identified as strongest performer for code smell identification. The models where Jrip, J48, Naive Bayes and SMO. The findings showed, that compared to previous studies, bagging J48 improved results by 0.5%. And that the nominally implemented baggin of J48 in Weka follows best practices and the model where impacted negatively. However, due to the complexity of stacking and voting ensembles further work is needed regarding stacking and voting ensemble models in the context of code smell identification.

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.

L’utilisation des codes MDPC (Moderate Density Parity Check) quasi-cycliques dans le cryptosystème de McEliece offre un schéma de chiffrement post-quantique dont les clés ont une taille raisonnable et dont le chiffrement et le déchiffrement n’utilisent que des opérations binaires. C’est donc un bon candidat pour l’implémentation embarquée ou à bas coût.Dans ce contexte, certaines informations peuvent être exploitées pour construire des attaques par canaux cachés.Ici, le déchiffrement consiste principalement à décoder un mot de code bruité. Le décodeur utilisé est itératif et probabiliste : le nombre d’itérations de l'algorithme varie en fonction des instances et certains décodages peuvent échouer. Ces comportements ne sont pas souhaitables car ils peuvent permettre d’extraire des informations sur le secret.Une contremesure possible est de limiter le nombre d’instances de chiffrement avec les mêmes clés. Une autre façon serait de recourir à un décodage à temps constant dont la probabilité d’échec au décodage est négligeable. L’enjeu principal de cette thèse est de fournir de nouveaux outils pour analyser du comportement du décodeur pour la cryptographie.Dans un second temps, nous expliquons pourquoi l'utilisation des codes polaires n'est pas sûre pour le cryptosystème de McEliece. Pour ce faire, nous utilisons de nouvelles techniques afin de résoudre une équivalence de codes. Nous exhibons de nombreux liens entre les codes polaires et les codes de Reed-Muller et ainsi d'introduire une nouvelle famille de codes : les codes monomiaux décroissants. Ces résultats sont donc aussi d'un intérêt indépendant pour la théorie des codes. / Considering the McEliece cryptosystem using quasi-cylcic MDPC (Moderate Density Parity Check matrix) codes allows us to build a post-quantum encryption scheme with nice features. Namely, it has reasonable key sizes and both encryption and decryption are performed using binary operations. Thus, this scheme seems to be a good candidate for embedded and lightweight implementations. In this case, any information obtained through side channels can lead to an attack. In the McEliece cryptosystem, the decryption process essentially consists in decoding. As we consider the use of an iterative and probabilistic algorithm, the number of iterations needed to decode depends on the instance considered and some of it may fail to be decoded. These behaviors are not suitable because they may be used to extract information about the secrets. One countermeasure could be to bound the number of encryptions using the same key. Another solution could be to employ a constant time decoder with a negligible decoding failure probability, that is to say which is about the expected security level of the cryptosystem. The main goal of this thesis is to present new methods to analyse decoder behavior in a cryptographic context.Second, we explain why a McEliece encryption scheme based on polar code does not ensure the expected level of security. To do so, we apply new techniques to resolve the code equivalence problem. This allows us to highlight several common properties shared by Reed-Muller codes and polar codes. We introduce a new family of codes, named decreasing monomial codes, containing both Reed-Muller and polar codes. These results are also of independent interest for coding theory.

This research compares the energy performance of a code-built residential building within the moist climate zone classification in Canada, Europe, and the Northeastern United States. The primary objectives are to reveal how specific differences in code requirements in similar climates influence a building’s energy profile, offer a means to quantify and evaluate the extent of energy savings as a result of each requirement, and provide a comparison of each location’s building culture and how this affects the standards in place. Using the building energy simulation tool, DesignBuilder EnergyPlus Simulation, a model single-family home was created and input energy code requirements for each location. An evaluation of each location’s building culture is examined through such factors as the training of building professionals, commonly used materials and products, energy reduction goals, and cultural attitudes. The results of this study point to the need for more advanced building practices, stricter code mandates, and higher performing products based on energy savings achieved from buildings built to different standards in equivalent climate zones. This has the potential to drive the development and use of better performing building materials and assemblies in the future.