In the last two decades, software designed to solve specific tasks for its user has seen a big rise and not least of these are mobile applications. Low-code development platforms have over the last few years been introduced as an alternative that provides lower development times and costs. These low-code development platforms do however trade features and functionality to reach these lower costs. This could affect the usability of the platform's end products. The goal of this thesis is to identify usability issues in a mobile application developed in a LCDP, analyze existing usability guidelines for native mobile applications and propose new or adapted usability guidelines for low-coded mobile applications.  To validate the gap in low-code development platform usability literature that led us to our initial problem statement we performed a literature review. Making use of individual interviews and focus groups we could produce the empirical data needed to identify potential user experienced usability issues within a low-code developed mobile application. We reviewed current native usability literature and found that most models, frameworks, and usability guidelines are in some way tied to the ISO 9241-11 standard. Individual interviews were held where we found that the overall experienced usability was positive. We then conducted seminars with focus groups which led to a thematic analysis. We summarized the quantitative data from the interviews and the qualitative data of the thematic analysis on the focus group seminars and then tied it to what we found in the literature review. Through our research, we found multiple areas of improvement in the application but the most discussed of these were that the users expected similar functionality to be presented in a similar fashion. With both the data from the literary analysis and empirical study we propose a new and adapted set of low-code usability guidelines with strong ties to the ISO 9241-11 standard and its core attributes.

Low-code is a modern approach to software development and has grown rapidly in recent years. By hiding complexity behind layers of abstraction, it allows inexperienced developers to create complex applications in a shorter amount of time. This thesis sets out to evaluate the current state of low-code as well as a few of the available low-code development platforms and how well their finished applications perform. A simple order management system was implemented in three low-code development platforms, Mendix, OutSystems, and Airtable, in order to gain experience in all of them. The platforms were then evaluated with respect to user experience and performance. The created applications load time and memory usage were measured in three different tests. It was found that there are plenty of low-code platforms that exist for different purposes, and that they all have their own learning curve depending on how flexible they aim to be. The performance of their respectively created applications is also similar to each other, with the only major differences being by design. / Low-code är en modern metod för mjukvaruutveckling och har vuxit snabbt under de senaste åren. Genom att dölja komplexitet bakom lager av abstraktion, kan oerfarna utvecklare producera komplexa applikationer på kort tid. Detta examensarbetet utvärderar den aktuella statusen för low-code, samt några av de tillgängliga low-code plattformarna och hur deras skapade applikationer presterar. Ett enkelt orderhanteringssystem implementerades på tre stycken low-code plattformar, Mendix, OutSystems och Airtable för att få olika erfarenheter. Plattformarna utvärderades sedan med avseende på användarupplevelse och prestanda. De skapade applikationernas laddningstid och minnesanvändning mättes i tre olika tester och utvärderades. Det visade sig att det finns flertalet low-code plattformar för olika ändamål. Plattformarna har olika inlärningskurva beroende på hur flexibla de är. Prestandan som uppmättes på vardera plattform när applikationen hade utvecklats visade sig vara väldigt likt sinsemellan. Den största skillnaden plattformarna emellan visade sig vara designvalen.

Låg-kod utvecklingsplattformer, på engelska low-code development platforms (LCDP), syftar till att göra det möjligt för företagsanställda med ingen eller begränsad programmeringserfarenhet, så kallade medborgarutvecklare, att utveckla applikationer. Professionella utvecklare, som idag är en bristvara, kan därmed avlastas och få utrymme till att fokusera på mer tekniskt krävande uppgifter. LCDP möter företagens ökade efterfrågan av snabbt kunna leverera digitala lösningar i takt med att verksamheten utvecklas. Syftet med denna uppsats är att undersöka vilka förbättringsmöjligheter och risker som finns vid införande av LCDP för företag. Uppsatsen avgränsas till artiklar i tidskrifter och branschtidningar mellan 2017 till 2022 från databasen Business Source Premier. För att uppnå uppsatsens syfte används en kvalitativ metod i form av en tematisk innehållsanalys. Sökordet ”low-code” resulterade i 93 artiklar där 30 valdes ut till den tematiska innehållsanalysen och sammanfattades i resultatkapitlet. Alla artiklar lästes igenom och de som valdes bort fokuserade på områden utanför uppsatsens syfte eller var otillgängliga. För de 30 utvalda artiklarna upprättades koder som sedan sorterades och sammanställdes till teman. Sju teman för förbättringsmöjligheter framkom; samarbete, tillgänglighet, produktivitet, utvecklingsresurser, marknadsanpassning, säkerhet och digitalisering. Fem teman för risker identifierades; säkerhet, utvecklingsstrategi, kodkompetens, utvecklingsprocess och upphovsskydd. Artiklarna framhöll övervägande fler förbättringsmöjligheter än risker vid införande av LCDP för företag vilket dels kan bero på att möjligheter lockar fler läsare och dels på att LCDP är en ny teknologi som inte har införts och använts under en längre tid.

Thesis (MScEng)--Stellenbosch University, 2011. / ENGLISH ABSTRACT: RoboCup promotes research in robotics and multi-robot systems (MRS). The RoboCup Small Size League (SSL), in particular, offers an entry level opportunity to take part in this field of study. This thesis presents a starting phase for research in robotics and MRS at Stellenbosch University. It includes the full documentation of the mechanical, electronic and software design of an omni-directional soccer robot for RoboCup SSL. The robot is also meant to operate as a hardware and software development platform for research in MRS. The platform was therefore designed with high-level programming language compatibility, a wide range of connectivity, and modularity in mind. The robot uses a single board computer (SBC) running a Linux operating system to accomplish these objectives. Moreover, a driver class library was written in C++ as a software application interface (API) for future development on the robot platform. The robot was also developed with a particular focus on a distributed control architecture. "Player" was implemented as the middleware, which can be used for communication between multiple robots in a distributed environment. Additionally, three tests were performed to demonstrate the functionality of the prototype: a PI speed control test, a direction accuracy test and a static communication test using the middleware. Recommendations for possible future work are also given. / AFRIKAANSE OPSOMMING: RoboCup bevorder navorsing in robotika en multi-robot-stelsels (MRS). Die RoboCup Klein Liga (KL) bied in die besonder die geleentheid om op intreevlak navorsing te doen in hierdie veld. Hierdie tesis verteenwoordig die eerste fase van navorsing in robotika en MRS by Stellenbosch Universiteit. Dit sluit die volledige dokumentasie van die meganiese, elektroniese en sagteware-ontwerp van ’n omnidireksionele sokker-robot vir die KL in. Die robot is ook veronderstel om te dien as ’n hardeware- en sagteware-ontwikkelingsplatform vir navorsing in MRS. Die platform is dus ontwerp met ’n verskeidenheid van uitbreingsmoontlikhede en modulariteit in gedagte asook die moontlikheid om gebruik te maak van ’n hoë-vlak programmeertaal. Om hierdie doelwitte te bereik, maak die robot gebruik van ’n enkel-bord-rekenaar met ’n Linux bedryfstelsel. Verder was ’n sagteware drywer in C++ geskryf om te dien as ’n sagteware-koppelvlak vir toekomstige ontwikkeling op die robot platform. Die robot is ook ontwikkel met die besondere fokus op ’n gedesentraliseerde beheerstels. Player was geïmplementeer as die middelware, wat gebruik kan word vir kommunikasie tussen verskeie robotte in ’n gedesentralliseerde beheerstelsel. Daar is drie toetse uitgevoer om die funksionaliteit van die prototipe te demonstreer, ’n PI spoed beheer toets, ’n rigting akkuraatheidstoets en ’n statiese kommunikasie toets deur van die middelware gebruik te maak. Aanbevelings vir moontlike toekomstige werk word ook verskaf.

Orientador: Luis Rogerio de Oliveira Hein / Resumo: Neste trabalho é apresentado o projeto e construção de uma Máquina Universal de Ensaios Mecânicos portátil, didática, de baixo custo, fácil construção seguindo a filosofia open-source com o intuito de dar suporte ao ensino de Mecânica e Resistência do Materiais. O equipamento foi projetado para ser construído com perfis modulares de alumínio e executado em uma oficina de ensino técnico em mecânica. A máquina é capaz aplicar de forma segura um carregamento máximo de 10 kN tanto em tração quanto em compressão, se mover em velocidades que variam de 0,5 a 70 mm/min com uma resolução no deslocamento de 0,57 μm a um custo total de US$ 1,000.00 incluindo material e fabricação. A máquina é controlada por uma placa Arduino® UNO, opera com acionamento eletromecânico, a aplicação de carga é feita por meio de fusos trapezoidais, a aquisição do deslocamento e velocidade da trave é feita por codificadores de quadratura e o controle de velocidade é feito por controle (Proporcional, Integral e Derivativo) PID e é capaz de realizar ensaios de tração, mas pode ser adaptada para outros ensaios como compressão, flexão e dobramento, entre outros. / Abstract: In this work is presented the design and construction of an easy to build low-cost portable Universal Testing Machine for educational purposes using the open-source philosophy. The intention of this project is to support the teaching in the subjects of Mechanics and Mechanics of Materials. The hardware was designed to be constructed with modular aluminum profiles and built in a conventional Mechanics Technical and Vocational Education and Training Laboratory. The machine can apply safely a maximum load of 10kN in both, traction and compression, move precisely in a range of speed from 0.5 to 70 mm/min with a resolution of 0,57 μm in a total cost of US$ 1,000.00 including necessary material and fabrication. The machine is controlled by an Arduino® UNO board, operated with an electromechanical activation. The loading is applied by trapezoidal lead screws, the displacement and speed acquisition are done by quadrature encoder and the speed is controlled by Proportional, Integral and Derivative (PID) control, it is capable do perform tensile tests, but may be adapted to other tests like compression, flexure and bending, and others. / Mestre

Sedan smarta mobiltelefoner introducerades har användningen och likaså behovet av mobilapplikationer ökat exponentiellt. När utvecklingsprocessen för en mobilapplikation påbörjas måste en utvecklare utvärdera ett antal faktorer som kan påverka mobilapplikationens användning eller prestanda, till exempel utvecklingsplattform som denna studie fokuserar på. Syftet med denna studie är att fastställa prestandaskillnaderna för native Android och Xamarin cross-compile med hjälp av en experimentell studie. Tesen för denna studie är baserad på tidigare forskning som tyder på att cross-platform och Xamarin cross-compile har sämre prestanda än native Android, resultatet av denna studie kan bidra till valet av utvecklingsplattform för utvecklare. Avgränsningar har valts i form av Android som plattform, exekveringstid, CPU-användning samt RAM-användning för prestandamätning. Beräkningar som utförs är iterativ bubble sort i form av best case, worst case och random case med varierande antal nummer och en rekursiv Fibonaccisekvens med olika utgångspunkter. Resultatet av denna studie stämmer överens med tesen, Xamarin har i dagsläget sämre prestanda än native Android. / Throughout the last decade the mobile phone market has grown rapidly and with it, the need for mobile applications has grown as well. When the development process for a mobile application starts, a developer must review various factors that can affect the mobile applications usage or performance, for example the development platform to use which is the focus of this study. The purpose of this study is to determine the difference in performance between native Android and Xamarin cross-compile with the use of an experimental study. The hypothesis of this study is based on previous research which shows that cross-platform and Xamarin cross-compile have worse performance than native Android, the result of this study can contribute can help a developer make the decision on what development platform to choose. The delimitations have been chosen as Android as platform, execution time, CPU-usage and RAM-usage for performance testing. The algorithms that were chosen were an iterative bubble sort, in form of best case, worst case and random case with varying numbers, and a recursive Fibonacci sequence with different starting points. The result of this study is consistent with the hypothesis, Xamarin shows worse performance than native Android.

Hydropower is a flexible energy source that is essential for balancing the electrical power system on all timescales, from seconds to years. In addition to intra-hour regulation, it provides frequency containment reserves (FCR-N,FCR-D) and frequency restoration reserves (mFRR, aFRR) to the grid. The turbine governor is a device responsible for controlling the power output and delivering frequency control to the system. The aim of this Master’s Thesis project is to develop a new hydropower turbine governor in MATLAB/Simulink, which contains all critical functionality from the existing governor and with the same performance. The new governor should as far as possible comply to the well-established communication standard IEC 61850. A working model of the turbine governor has been built in Simulink that supports normal operation with frequency control, start and stop, load rejection, operation mode as synchronous condenser and more. Validations of the model against data from Akkats powerplant shows that the model behaves as a real governor during normal operation. Validations of the start sequence showed deviations during sequence 3 and 4 which can be explained by usage of different PID parameters. Using IEC 61850 as a nomenclature and as a way of structuring functions in the governor has also been possible. Implementing the whole standard for communication, requires that the control system also is renewed according to IEC 61850. Certain functions, as sequencing has thus not been done according to the standard. MATLAB and Simulink provide tools for building, simulating and testing implementations of the turbine governor. The contributions this platform can provide are; ease of implementation, optimization and testing of control strategies. Simulink also provides a graphical interface, which reduce system complexity. An optimal implementation requires a hardware with support for Simulink to get a transparent platform. Ultimately, these benefits could result in better frequency quality at a lower cost, which is essential for successful and cost-effective integration of other renewable energy sources such as wind- and solar power.

Brain of Materials ist eine Plattform für innovative und smarte Materialien, die Designern, Entwicklern und Ingenieuren diverser Branchen dabei hilft, ihre Produktentstehungsprozesse zu optimieren und zu beschleunigen.

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