Syftet med detta projekt har varit att skapa en jämförelse mellan två olika webbutvecklingsmetoder, no code och klassisk webbprogrammering, jämförelsen har skapats via en fallstudie hos företaget Lyxrummet där två webbutiker har skapats med dessa två olika metoder. No code-plattformen som använts har varit Wordpress och den klassiska webbprogrammerings metoden som använts har varit med språken PHP, HTML och CSS. För att kunna få fram resultatet av jämförelsen mellan webbutikerna så har användartester med 8 deltagare utförts samt mätningar på utvecklingstiden och kodrader. Slut resultatet visade att klassisk webbprogrammering var en mer lockande sida för deltagarna från användartestet men no code webbutiken var en snabbare och billigare variant för utveckling då ingen teknisk kunskap krävs. / The purpose of this project has been to create a comparison between the two different web development methods, no code and classical web development. The comparing has been done through a case study with the company Lyxrummet where two web shops have been created with these two methods. The no code platform that has been used is WordPress who is a leading platform for web development, and for the classical web development the language PHP, HTML, and CSS has been used. To be able to reach a result by the comprising between the web shops user testing have been done of 8 participates and measurement of the development time and code lines. The finishing result showed that the classical web developed web shop was the most liked by the user testing, but the no code web shop was a faster and cheaper alternative for web development because no technical knowledge person is needed.

No-code tools are a method of development to make it easier and faster for someone to create a simple or specific product regardless of prior programming experience. No-code tools are primarily used today to make ordinary applications or websites, for use as is,  or to try out a business idea. In this paper we introduce the reader to the concept of no-code tools and if software engineering students should consider using no-code tools in conjunction with their studies in some form. We primarily focus on no-code tools related to web development. It is an area where there exist a lot of competitors which are often marketed online. The requirements validation process within software development has a prototyping technique which allows the customer and endusers to experiment with a functional prototype. However, this comes at the cost of additional effort, which no-code could possibly negate through its nature of quickly creating functional applications. We investigate and see if no-code tools can be viable within the requirements validation process by using it for prototyping. We find that no-code tools’ limitations do not prevent it from being a viable way of both allowing the developers andcustomer/end-users to quick and easy develop functional prototypes. However, this fact varies depending on the requirements and the used no-code tool as limitations vary.

No description available.

The use of no-code editors makes developing web applications more accessible since they are based on Graphical User Interface elements instead of conventional programming languages. This allows users without previous programming experience to design web-application interfaces. However, designing web applications with no-code editors can be a daunting process for beginners without design experience. This study therefore investigates which aspects of no-code editors can support novice designers when designing aesthetically pleasing web-application layouts. A usability analysis of three state-of-the-art no-code editors was conducted using the Cognitive Dimensions of Notations framework. The main aspect that impacted usability in the no-code editors was a difficulty aligning and positioning elements due to hidden dependencies and unforeseen actions. Based on this finding, a prototype was developed to address these issues. The prototype introduced the concept of a "Golden Ratio Guide", a visual guide intended to support the alignment and positioning of elements. A user study was conducted with inexperienced designers (n=5) to test if the Golden Ratio Guide helps with designing aesthetic web-application layouts. Contrary to expectations, a survey with users of such web-applications (n=36) showed that the web-layouts designed without the Golden Ratio Guide were preferred. / Att använda sig av programmeringsfria redigeringsprogram för att utveckla webbapplikationer bidrar till en större tillgänglighet då de är baserade på grafiska användargränssnittselement istället för konventionella programmeringsspråk. Detta tillåter användare utan tidigare programmeringserfarenhet att designa webbapplikationsgränssnitt. Men att designa webbapplikationer i ett programmeringsfritt redigeringsprogram kan vara en skrämmande process för nybörjare utan designerfarenhet. Denna studie undersöker därför vilka aspekter av programmeringsfria redigeringsprogram som stödjer nybörjare med att designa estetiskt tilltalande layouter för webbapplikationer. En användbarhetsanalys av tre programmeringsfria redigeringsprogram relevanta inom fältet genomfördes med hjälp av ramverket Cognitive Dimensions of Notations. Den huvudsakliga aspekten som påverkade användbarheten i programmeringsfria redigeringsprogram var svårigheten att anpassa och placera element på grund av dolda beroenden och oförutsedda händelser. Baserat på denna upptäckt utvecklades en prototyp för att lösa dessa problem. Prototypen introducerade konceptet med en "Gyllene Snittet Guide", en visuell guide avsedd att stödja anpassning och positionering. En användarstudie genomfördes med oerfarna designers (n=5) för att testa om guiden baserad på det Gyllene Snittet hjälper med att designa estetiska layouter för webbapplikationer. Tvärtemot förväntningarna visade en undersökning med användare av dessa webbapplikationer (n=36) att webblayouterna som designats utan guiden baserad på det Gyllene Snittet föredrogs.

I takt med att verksamheten snabbt måste kunna ställa om sig baserat på omvärldens alltmer snabba föränderlighet växer ärendehögen med utvecklingsinsatser hos IT- avdelningen. Under många år har olika verktyg kommit och gått där syftet varit att möjliggöra för personer utan programmeringskunskaper att kunna skapa applikationer. På senare tid har ett uppsving av så kallad utveckling med hjälp av low-code/no-code tagit fart där anställda ute i verksamheten själva ska kunna utveckla applikationer, ofta genom grafiska användargränssnitt. Syftet med denna studie är att titta på de fenomen som finns kopplade till användningen av dessa verktyg baserat på de artiklar som IDG- koncernen publicerat under år 2017-2021. Med avstamp i den aktuella rapporteringen studeras också den potentiella framtida synen kring användningen av dessa verktyg. Metodvalet i denna studie är den tematiska innehållsanalysen (Braun & Clarke 2006) där artiklarna lästes igenom och analyserades med hjälp av koder som sedan organiserades till teman. De fenomen som identifierades var ett ökat partnerskap verksamhet/IT, ökande trend, integrationsmöjligheter, flexibilitet, medborgarutvecklarens centrala roll, ökad utvecklingstakt, automatisering samt utmaningar kopplade till användningen av low-code/no-code. De effekter som uppnås med dessa verktyg är ett ökat partnerskap mellan verksamhet och IT vilket leder till en ökad utvecklingstakt i organisationer där medborgarutvecklaren får en central roll som också får större fokus vid den senare rapporteringen. Stor grad av flexibilitet och goda integrationsmöjligheter är något som nämns vid användning av low-code/no-code samt att de kan skapa förutsättningar för en ökad grad av automatisering. Utmaningarna är få och de avtar i den senare rapporteringen. Här nämns svårigheter att skapa vissa typer av integrationer eller specifik funktionalitet. En utmaning kan också vara att professionella utvecklare kan känna sig hotade av användningen av dessa verktyg men att detta förmodligen inte är ett problem då verktygen leder till att IT-avdelningen kan ägna sig åt mer komplexa uppgifter. Den framtida synen kring användningen av dessa verktyg är positiv i och med ett högt förhållande av positiva kontra negativa effekter samt att marknaden för dessa verktyg är växande vilket är något som ofta återkommer i rapporteringen.

This thesis investigates the concept of citizen developers, in which employees in an organisation take on the role of developers and create software using low-code tools. The primary focus of this report is to examine the necessary steps an organisation must take when introducing citizen developers, particularly regarding solution maintenance. The purpose, therefore, is to establish a foundation for utilising the concept of citizen developers in the workplace, bridging the gap between users and developers. Furthermore, this study aims to explore the organisational structure required to incorporate citizen developers and identify the advantages and drawbacks associated with an organisational structure tailored for citizen developers. Citizen developers possess distinct roles and responsibilities within an organisation, making them experts in their respective fields. This expertise renders citizen developers a valuable resource, as they develop solutions to enhance their own work efficiency and effectiveness. A case company has been selected for this study, and interviews have been conducted with multiple employees from the organisation. Through analysis of these interviews and a comprehensive literature review, a governance model has been developed. The governance model delineates the level of responsibility citizen developers should assume, and an evaluation of the model also uncovers potential advantages and drawbacks of introducing citizen developers within an organisation. Ultimately, this thesis aims to contribute to research on the subject of citizen developers, with particular emphasis on solution maintenance.

The amount of active websites on the internet is claimed to have increased by almost half a billion in the last decade. With that, the amount of tools available to help develop them has increased as well. One type of these tools is called website builders. In the past few years, the market has seen a big increase in software often referred to as no-code tools. By visualizing most, if not all, of the otherwise manual coding process, they aim to give users an increased amount of flexibility without having to possess a lot of previous web development knowledge. However, despite their current popularity, no-code tools do not seem to be the target of much research. This study aims to measure the performance of Webflow, a browser based software that fits both the category of a website builder as well as a no-code tool. This is done by comparing its performance to Wordpress, arguably the most established website builder on the market. The performance analysis is conducted through automated performance audits using Google Lighthouse and its 6 performance metrics. By developing an identical website using both builders, two versions of the website have been analyzed; one static snapshot deployed on the same hosting environment and one dynamic version deployed using Webflows’ internal cloud hosting environment, and Wordpress deployed on an AWS EC2 instance. The results showed that while Wordpress outperformed Webflow in a majority of individual performance metrics in both experiments, Webflow performed better overall on the desktop breakpoint on both the static and dynamic version of the websites.

Purpose: This study aims to identify the operational and financial outcomes of companies implementing the no-code manufacturing execution system (MES). Methods: This study has been conducted using inductive reasoning to develop new theories in this unexplored subject. The thesis has conducted a multiple case study to collect qualitative, empirical data. Qualitative data has been collected through conducting three interviews from two separate companies. The Research Background and Findings section was then cross analyzed to find commonalities to form conclusions.  Conclusion: Implementing a no-code MES offers operational and financial benefits for manufacturing companies. It improves productivity, reduces lead times, increases flexibility, and enhances quality efforts. Cost savings are achieved through paper reduction and lower implementation costs compared to traditional MES solutions, which do not have no-code features. Overall, a no-code MES delivers advantageous outcomes efficiently and eliminates the need for significant capital investments and technical skills. Theoretical Contribution: This thesis contributes to the field of science by unifying Manufacturing Execution System (MES) with the existent subject of low-code/no-code. This study creates a deeper knowledge by merging science with empirics.  Practical Contribution: The thesis contributes to practitioners in the manufacturing industry by indicating the relevance and importance of the beneficial operational and financial outcomes of adopting a no-code MES. Firstly, there are strong indications that a no-code MES could be a possible solution for companies that could be impacted by the labor shortage in software developer jobs. Secondly, as the no-code MES mitigates the barriers with traditional MES solutions, having the MES built on no-code makes the solution more cost-effective and easy-to-maintain. Limitations & Future Research: This study is limited to two case companies and three interviews. The study’s findings are limited by the short duration of a no-code MES implementation in the case companies, preventing a full investigation of financial outcomes. Further research is necessary to fully examine the financial outcomes of implementing a no-code MES.

In the data-driven landscape of modern business, predictive analytics plays a pivotal role inanticipating and mitigating customer churn—a critical challenge for organizations. However, thetraditional complexities of machine learning hinder accessibility for decision-makers. EnterMachine Learning as a Service (MLaaS), offering a gateway to predictive modeling without theneed for extensive coding or infrastructure.This thesis presents a comprehensive evaluation of cloud-based and cloud-agonostic AutoML(Automated Machine Learning) platforms for customer churn prediction. The study focuses onfour prominent platforms: Azure ML, AWS SageMaker, GCP Vertex AI, and Databricks. Theevaluation encompasses various performance metrics including accuracy, AUC-ROC, precision,recall to assess the predictive capabilities of each platform. Furthermore, the ease of use andlearning curve for model development are compared, considering factors such as data preparation,training steps, and coding requirements. Additionally, model training times are analyzed toidentify platform efficiencies. Preliminary results indicate that AWS SageMaker exhibits thehighest accuracy, suggesting strong predictive capabilities. GCP Vertex AI excels in AUC,indicating robust discriminatory power. Azure ML demonstrates a balanced performance,achieving notable accuracy and AUC scores. Databricks being platform independent is a winnerand has also shown good metrics. Its capability to generate notebook is an added advantage whichcan be modified by experts to fine tune the results more. This research provides valuable insightsfor organizations seeking to implement different AutoML solutions for customer churnprediction.

This study investigates how small and medium sized enterprises (SMEs) and other resource-lacking organisations can utilise automated machine learning (AutoML) to lessen the development hurdles associated with machine learning model development. This is achieved by comparing the performance, cost of usage, as well as usability and documentation for machine learning models developed through two AutoML frameworks: Vertex AI on Google Cloud™ and the open-source library AutoGluon, developed by Amazon Web Services. The study also presents a roadmap and a time plan that can be utilised by resource-lacking enterprises to guide the development of machine learning solutions implemented through AutoML frameworks. The results of the study show that AutoML frameworks are easy to use and capable in generating machine learning models. However, performance is not guaranteed and machine learning projects utilising AutoML frameworks still necessitates substantial development effort. Furthermore, the limiting factor in model performance is often training data quality which AutoML frameworks do not address.