Utveckling av digitala lösningar som smidigt integrerar och visar relevant informationhar blivit ett av de viktigaste verktygen för många företag. Low-code-plattformar harskapats för att förenkla detta arbete. Frågan är om dessa plattformar lyckas med dettamål och till vilken grad. Denna uppsats har som mål att bearbeta denna fråga och kommatill ett vägvisande svar. Inledande så undersöktes low-code-konceptet och sedan valdestre olika plattformar ut. Dessa plattformar var: OutSystems, Microsoft Power Apps, ochMendix. För att undersöka och utvärdera dessa plattformar designades en demoapplikationsom implementerades i var och en av plattformarna. Resultatet blev en beskrivningav utvecklingsarbetet och en utvärdering av de olika plattformarna. I utvärderingen avutvecklingsarbetet konstaterades att de undersökta low-code-plattformarna bidrar tillsmidigare utveckling med fokus på användargränssnitt men att de trots sina enklaresystem ändå kräver viss utvecklingsvana för effektivt utnyttjande. Förslag för framtidaarbete inom området och med arbetet presenterat i rapporten beskrivs. / Development of digital solutions that seamlessly integrate and display relevant informationhas become one of the most important tools for many companies. Low-codeplatforms have been created to simplify this work. The question is if these platformssucceed in this goal and to what extent. This paper has as its goal to process this questionand arrive at a guiding answer. Initially, the low-code concept was examined and thenthree different platforms were selected. These platforms were: OutSystems, MicrosoftPower Apps, and Mendix. To investigate and evaluate these platforms, a demo applicationwas designed and subsequently implemented in each of the platforms. The resultwas a description of the development work and an evaluation of the various platforms. Inthe evaluation of the development work, it was concluded that the investigated low-codeplatforms contribute to smoother development with a focus on user interfaces, but thatdespite their simpler systems, they still require a certain development habit for efficientuse. Proposals for future work in the area and with the work presented in the report aredescribed.

Resultatet från utvärderingsintervjuerna pekar mot att Low-code leder till ett antal positiva effekter. Ökad effektivitet, minskat beroende av Angular-kompetens och minskad förekomst av tekniska fel är några. Resultatet indikerar även några utmaningar, såsom en försämrad flexibilitet i validering av input-fält och minskad anpassningsförmåga av komponenter och allmän funktionalitet.  Utilizing semi-structured interviews, some of the organization's requirements were identified. These requirements formed the basis for the development of a prototype and a few test cases. The prototype and the test cases were created in a beta version of a Low-code tool, WebRatio. They were then demonstrated and explained to stakeholders at Kronofogden that evaluated to what extent WebRatio in particular and Low-code in general can fulfill their requirements.    The results from the evaluation-interviews shows that Low-code leads to a number of positive effects. Increased efficiency, decreased dependence on Angular-competence and a decrease in the number of technical mistakes being made. However, the results also point to a number of negative effects, such as an impaired flexibility in validation of input-fields and a reduced adaptability in regard to the usage of components and general functionalities. / The digitalization of today’s society is ongoing at full speed, and the question is not if, but how it will be done. Low-code is an increasingly popular way of building software. Instead of writing code by hand, Low-code allows the user to utilize graphical user interfaces and ready-to-use components, with the intention to increase productivity in the area of software development. This case study whose context is Kronofogdemyndigheten has researched which effects Low-code has on a state-owned organizations software development.   Utilizing semi-structured interviews, some of the organization's requirements were identified. These requirements formed the basis for the development of a prototype and a few test cases. The prototype and the test cases were created in a beta version of a Low-code tool, WebRatio. They were then demonstrated and explained to stakeholders at Kronofogden that evaluated to what extent WebRatio in particular and Low-code in general can fulfill their requirements.    The results from the evaluation-interviews shows that Low-code leads to a number of positive effects. Increased efficiency, decreased dependence on Angular-competence and a decrease in the number of technical mistakes being made. However, the results also point to a number of negative effects, such as an impaired flexibility in validation of input-fields and a reduced adaptability in regard to the usage of components and general functionalities.

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

Enterprise low-code plattformar är något som stora organisationer och företag använder för att möjliggöra organisationsförändringar, orkestrera affärsprocesser och utvinna potential med citizen development. Forskningen runt low-code plattformar ligger dock efter, vilket gör att organisationer blir beroende av marknadsanalytiker och konsulter i den utforskande fasen i deras implementation. För att möta den brist på tidigare forskning inom enterprise low-code plattformar så har vi designat och utfört en fallstudie där vi studerat Arbetsförmedlingens implementation och användning av PegaSystems low-code plattform. Baserat på resultatet från denna studie så har vi tagit fram rekommendationer för framtida implementationer av enterprise low-code plattformar. Vi fann att Pegakompetens, mognad och struktur är viktiga och avgörande faktorer i ett Pegaprojekt. Vi fann också att tidig satsning och prioritering av Pegas Situational Layer Cake är nyckeln för att kunna utnyttja och skapa återanvändning, öka effektivitet, bygga en generisk grund och kunna använda citizen development. Våra rekommendationer till framtida implementationer är därför att (1) prioritera utveckling av Situational Layer Cake (2) Ta fram en projekttidslinje och strategi som är medveten om organisationens egen nivå av Pegakompetens, mognad och struktur.

In the fast-growing software development market, where there is a lack of software developers, they need to be as efficient as possible with their time. Low Code platforms growing fast, and there is considerable interest from industry and science. Therefore this report’s goal is to shine some light on the topic of Low Code platforms, especially Camunda, and how further development in Camunda compares to traditional Java development. Can the Low Code platform Camunda be a better alternative than Java for software development? This report will show significant benefits, such as increased development speed and easy interpretation in comparison to Java development. Camundadevelopment is not as flexible as Java and is not a replacement but a tool to make development faster and easier.

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.

This study examines how systems development operations manage the Software Development Life Cycle (SDLC) in a Low-Code Platform (LCP) and how these descriptions relate to today's SDLC standards. To investigate this, a case study for a specific LCP has been made. Semi-structured interviews have been carried out with the aim of investigating theSDLC managed in the investigated LCP. An analysis model based on ISO/IEC/IEEE12207:2017 has been used for a deductive thematic analysis. The analysis shows a great breadth regarding how system development operations can integrate an LCP into their IT infrastructure and work with it. The choice of strategy will control how the system development operation works with the SDLC for IT artifacts that are developed in theplatform. In order for the organization to be able to enjoy the benefits of the LCP, business processes need to be possible to model in the platform. Complex and extensive business rulesaffect the possibilities to model business logic through low-code in the platform. Addressing this through traditional code can increase the complexity of certain elements of the SDLC and the need for expertise, which can significantly increase resource requirements and the time required for the system development process. / Denna studie undersöker hur systemutvecklings-verksamheter hanterar SoftwareDevelopment Life Cycle (SDLC) i en Low-Code Platform (LCP) och hur dessa beskrivningarrelaterar till dagens standarder för SDLC. För att undersöka detta har en fallstudie för enspecifik LCP genomförts. Semistrukturerade intervjuer har utförts i syfte att undersöka hurolika projekt hanterat SDLC i den undersökta LCP:en. En analysmodell baserad påISO/IEC/IEEE 12207:2017 har använts för en deduktiv tematisk analys. Analysen visar på enstor bredd gällande hur systemutvecklings-verksamheter kan integrera en LCP i sinIT-infrastruktur och arbeta med denna. Valet av strategi kommer styra hursystemutvecklings-verksamheten arbetar med SDLC för IT-artefakter som utvecklas iplattformen. För att organisationen ska kunna åtnjuta fördelarna med LCP:en behöveraffärsprocesser vara möjliga att modellera i plattformen. Komplexa och omfattandeaffärsregler påverkar möjligheterna att modellera affärslogik genom low-code i plattformen.Att åtgärda detta genom traditionell kod kan öka komplexiteten i vissa moment i SDLC ochpåverka behovet av kompetens vilket avsevärt kan öka resurskrav och tidsåtgången försystemutvecklingsprocessen.

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.

Актуальность темы обусловлена потребностью предприятия АО «Альфа-Банк», для улучшения процесса работы системы оповещений, для увеличения осведомленности пользователей системы SFA о новых обновлениях системы. Цель работы: улучшение качества работы системы оповещений и увеличении количества читаемости оповещений пользователями с целью увеличения осведомленности об обновлениях SFA, чтобы уменьшить количество консультаций с пользователями по поводу обновлений системы. Объектом исследования данной выпускной работы является информационная система SFA для работы с клиентами банка, а именно с системой оповещений пользователей о новых обновлениях системы. Предметом исследования является бизнес-процесс работы с системой оповещений. Научная новизна исследования состоит в том, что созданы новые методы для запуска модальных окон при загрузке приложения в low-code платформе Pega, создан метод для работы слайдеров изначально не заложенных в систему. Тем самым были выполнены уникальные доработки платформы Pega. Практическая значимость заключается в том, что данную систему оповещений можно применить в любой компании, в которой есть платформа PEGA и необходимость оповещать пользователей об обновлениях системы. / The relevance of the topic is due to the need of Alfa-Bank JSC to improve the process of the notification system, to increase the awareness of users of the SFA system about new system updates. The purpose of the work: to improve the quality of the alert system and increase the amount of readability of alerts by users in order to increase awareness of SFA updates in order to reduce the number of consultations with users about system updates. The object of study of this graduation work is the SFA information system for working with bank customers, namely, with a system for alerting users about new system updates. The subject of the study is the business process of working with the notification system. The scientific novelty of the research lies in the fact that new methods have been created for launching modal windows when loading an application in the Pega low-code platform, a method has been created for the operation of sliders that were not originally included in the system. Thus, unique improvements to the Pega platform were made. The practical significance lies in the fact that this notification system can be applied in any company that has a PEGA platform and the need to notify users about system updates.

This master's thesis is focusing to create an operational CRM system in web interface of SystemBaker application in company environment – specifically for company named Mathesio s.r.o. In theoretical part there are explained concepts and technologies, which are needed to know to fully comprehend background of the developed application. Then there are introduced possible forms of developing this application, which serve for later assessment of economic benefits of this development form. In practical part there is de-scribed structure of database, use-cases and operational solution of this application and then economical assessment of benefits of this style of development.