Application that combines crowdsourcing and gamification elements should be usable by as many passengers as possible, considering all the different smartphones available on the market and people with disabilities. Thus, most popular platforms for cross-platform mobile application development should be compared in order to choose the appropriate one for this project. Finally, application prototype should be further tested to gather more feedback about design and concept for improvements and future studies.  Such solution is not meant to replace current methods of information gathering, but instead should be one of the available tools.

Web development is receiving increasing attention among all kinds and sizes of companies. Web presentation has become a hygiene factor for companies nowadays. Fortunately, nowadays web developers can choose from a great number of ready-made technologies instead of developing everything from scratch. However, web development technologies have evolved much in the past 20 years. Due to the increased complexity and diversity of the alternatives, it is getting more and more difficult for companies to make an overall good choice of technologies, especially small and medium-sized enterprises (SMEs) that usually do not have resources to make a thorough research before choosing. This thesis creates WeTS - Web Technology Stack Guidelines, which contains three parts: process, algorithm and software quality characteristics. By following WeTS, inexperienced web developers, especially in SMEs, can select web technology stacks in an optimal way. Meanwhile, WeTS could be used for experienced practitioners and researchers as a reference to have an overview about modern web development technologies. Based on WeTS Guidelines, this thesis evaluated a number of technology stacks. Then a case study was performed with a startup company named Sqore. By comparing WeTS with Sqore’s technology selection process step by step, this thesis evaluated WeTS Guidelines.

Mobile application development has grown in the past few years, and instead of native development, some developers have moved to a new strategy; cross-platform mobile development using frameworks. There are many frameworks that all have their use case, but whether or not these frameworks are ready to be used in production applications is hard to decide on . This research aims to find the strengths and weaknesses of cross-platform mobile development frameworks, and how they can be improved to better suit the needs of developers. To gather data in this topic a survey was created to analyze developer experiences on frameworks in key areas such as front-end design, platform maturity and more. The results reveal that there are many areas that can be improved, but frameworks are a great tool for smaller teams and are being used extensively already to create applications for multiple platforms.

When developing applications, developers face a challenge when they have to select the technologies that best fit the requirements gathered for the application that is going to be developed. New programming languages, frameworks, stacks, etc., have arisen in recent years making the choice even harder. Cloud computing is a new technology that has gained popularity in the last two decades providing computing resources to developers and companies. As with the other technologies, there are many cloud service providers to choose from. In this thesis, the two biggest cloud service providers Amazon Web Services and Microsoft Azure are compared. Furthermore, after comparing the providers a prototype of a customer relationship management system was deployed to the selected provider. From the data gathered it could be seen that further research needs to be done to decide which provider might fit better for application development.

The main goal of this research is to facilitate end-user and expert developer collaboration in the creation of a web application. This research created a reverse engineering toolset and integrated it with Click (Component-based Lightweight Internet-application Construction Kit), an end-user web development tool. The toolset generates artifacts to facilitate collaboration between end-users and expert web developers when the end-users need to go beyond the limited capabilities of Click. By supporting smooth transition of workflow to expert web developers, we can help them in implementing advanced functionality in end-user developed web applications. The four artifacts generated include a sitemap, text documentation, a task model, and a canonical representation of the user interface. The sitemap is automatically generated to support the workflow of web developers. The text documentation of a web application is generated to document data representation and business logic. A task model, expressed using ConcurTaskTrees notation, covers the whole interaction specified by the end-user. A presentation and dialog model, represented in User Interface Markup Language (UIML), describe the user interface in a declarative language. The task model and UIML representation are created to support development of multi-platform user interfaces from an end-user web application. A formative evaluation of the usability of these models and representations with experienced web developers revealed that these representations were useful and easy to understand. / Master of Science

The efficient management of storage units requires a reliable and streamlined move-out process. Manual validation methods are resource intensive. Therefore, the task is to introduce an automated approach that capitalises on modern smartphone capabilities to improve the move-out validation process. Hence, the purpose of this thesis project. The proposed solution is a Proof of Concept (POC) application that utilises the Light Detection and Ranging (LiDAR) sensor and camera of a modern iPhone. This is performed through RoomPlan, a framework developed for real-time, indoor room scanning. It generates a 3D model of the room with its key characteristics. Moreover, to increase the number detectable object categories, the solution is integrated with the image classifier Tiny YOLOv3. The solution is evaluated through a quantitative evaluation in a storage unit. It shows that the application can validate whether the storage unit is empty or not in all the completed scans. However, an improvement of the object detecition is needed for the solution to work in a commercial case. Therefore, further work includes investigation of the possibilities to expand the object categories within the image classifier or creating a similar detection pipeline as RoomPlan adjusted for this specific case. The usage of LiDAR sensors indicated to be a stable object detector and a successful tool for the assignment. In contrast, the image classifier had lower detection accuracy in the storage unit.

An increasing amount of companies and organizations are starting to implement the use of cloud computing in their business. This trend results in that software, which was previously sold and distributed to the customers whom then had to install the software on their own computers, now is being replaced with Software as a Service (SaaS). SaaS makes software available through the customers’ browsers, which results in that the service providers only have to administer a single application. The process to migrate a distributed application to a service delivered as a SaaS lacks sufficient investigation; this paper will provide some guidelines for conducting such a pro- cess. During the work on this paper, a prototype of a service delivered as a SaaS has been devel- oped with the intention to test, among other things, how a distributed relational database can be converted to a key/value pair storage. A conversion of this kind enables data to be stored locally in the customers’ browsers, which relieves some pressure on the server as well as enables the application to be used in offline-mode. The paper results in three guidelines which should be considered when planning to migrate software to a service delivered as a SaaS with a local data- base; Think before you act, Don’t expose your soul and Size matters. These guidelines describe how a migration process should be planned, when an application is not deemed appropriate to migrate and when a conversion of the database is not appropriate. / Allt fler företag och organisationer börjar implementera användandet av olika molntjänster i sin verksamhet. Den här trenden medför att programvaror, som tidigare sålts och distribuerats till kunder vilka sedan själva får installera dem på sina egna datorer, nu börjar ersättas med en Soft- ware as a Service (SaaS). Det innebär att programvaran istället finns tillgänglig på Internet via kundernas webbläsare, något som medför att tjänsteleverantören enbart behöver administrera en enda programvara. Processen att migrera en distribuerad programvara till en SaaS-tjänst saknar ordentlig utredning, det här arbetet syftar därför till att ta fram några vägledande riktlinjer för en sådan process. Under arbetets gång har en prototyp av en SaaS-tjänst utvecklats med syfte att testa bland annat hur en tidigare distribuerad relationsdatabas kan konverteras till nyckel/värde- par. En sådan konvertering möjliggör lokal lagring av data i kundernas webbläsare, vilket mins- kar belastningen på servern samt erbjuder möjligheten att arbeta offline. Arbetet resulterar i tre riktlinjer att beakta då en migration till en SaaS-tjänst med lokal databas planeras; Tänk efter, före, Blotta inte din själ och Storleken har betydelse. Riktlinjerna beskriver hur en migrations- process bör planeras, när en applikation inte anses lämplig att migrera samt när en konvertering av databasen inte anses lämplig.

This thesis aims to to see if its possible to meet some of the complex needs of people with ADHD, in the form of aiding them with remembering to complete tasks and chores. Current studies have mainly focused on either assessing or treating ADHD rather than looking at aiding people already diagnosed. In order to evaluate if the needs can be met the participants of the paper are first interviewed to determine some of the needs. A mobile application was then developed based on the data collected from the interviews and later evaluated by the participants in a second round of interviews. The result of this paper showed that these complex needs can be met, in this paper the needs managed to be met with the use of mobile notifications that server as reminders and also by letting the participants prioritize the importance of the task. However the application did not fully suit all participants and had some shortcomings which could lead to further research that looks at trying to meet more of these needs, either by continued development of the application or by mapping out what the needs are.

<div>In the modern era where technology is constantly evolving, it is important to evaluate new technological tools and approaches in order to gauge their potential for adoption. Rapid Application Development (RAD) has highly evolved over the years, but it has not seen much response at the university level. Several studies show that perceptions of usability form the basis of acceptance or rejection of new tools and applications. Thus, running a usability study on a specific RAD tool coupled with autoethnographic documentation of specific development experience with that tool has the potential to encourage university faculty/staff to consider teaching/using it.</div><div><br></div><div>This research study seeks to understand developers' perceptions regarding the usability aspect of Mendix, a Rapid Application Development (RAD) tool. Both qualitative and quantitative approaches were employed to discover and understand the extent of perceived usefulness, ease of use and satisfaction with the tool. The results of the study presented a case for academicians on the viability of teaching RAD or using Mendix for their web application development needs. The study ultimately sought to help university faculty understand what to expect while teaching RAD to students from computing background and also help them decide if they would like to use tools like Mendix for their software development projects or continue to use specific coding languages (traditional software development) for software development projects. </div><div><br></div>

No abstract provided