To research the relationship between Childhood obesity and infant feeding patterns, the Electrical Engineering Department at California Polytechnic State University has designed a SmartBottle device attaching to the bottom of a baby bottle to monitor the infant feeding process. This project mainly focuses on the software and firmware design, as well as the neural network design of the SmartBottle device. The SmartBottle device is designed to identify infant feeding activities and to record related data for overweight and obesity research on children. This device includes a 6-dimensional inertial sensor that contains a 3-axis digital accelerometer and a 3-axis digital gyroscope. The measurement of this inertial sensor is passed into a neural network to identify drinking events and to measure the bottle-feeding angle. This device also includes a load sensor, a real-time clock, and an SD card to measure feeding amounts, record feeding time, and store real-time data. To obtain training data for the NN, device firmware was written to record feeding event data with the aid of a lab assistant familiar with typical feeding actions. Once a large set of data was collected, it was separated into two groups for neural network training and testing. The resulting neural network was repeatedly evaluated by lab assistants and rebuilt until it fully satisfied all the requirements. Finally, according to users’ preferences, the last step was to optimize the software and have it ready to be used for laboratory-based research.

Modeling and simulation are becoming indispensable elements in drug development. Mechanistic modeling is susceptible to impacting several drug development and regulatory decisions through extrapolations beyond clinically researched scenarios by using its capacity to incorporate diverse data to provide a detailed and comprehensive understanding of a physiological and biological system. Physiologically based pharmacokinetic (PBPK) modeling is the fastest-growing Model-informed drug development subfield, and regulatory authorities currently demand or advocate its usage for specific applications. Shiny is based on the open-source software R, which is widely used in the statistics and data science communities, including finance, medicine, and pharmaceuticals. Shiny conveys complex models to non-technical audiences via interactive graphics and sensitivity analysis. The Shiny R package is a crucial development that opens up PBPK models developed in R to a wider audience. This project's main goal is to create a framework and, a user-friendly tool for PBPK model evaluations and performance comparisons during model development, customized for the Open System Pharmacology Suite. To develop the PBPK framework, a PBPK model was retrieved from the open system pharmacology repository on GitHub, and based on the model and parameter identification inputs, the shiny framework was coded in R.Principal diagnostic techniques such as visual predictive checks to match and correlate model-simulated concentration-time profiles with clinical data, the goodness of fit (GOF) analysis (e.g., residuals over time, residuals against predictions, etc.), and extensive precision and bias measures were used to assess and validate the performance robustness of the model. Various quantitative metrics such as root mean square error, mean absolute error, and concordance correlation coefficient were used to assess and evaluate the model performance. The PBPK-QSP shiny framework was developed, allowing users to do the model evaluation with minimal effort. Using frameworks such as Shiny can expedite and automate the PBPK procedure, saving a significant amount of money and time in the evaluation of model performance.

Background. Speed is getting more and more critical in modern Software Engineering to be able to respond to users’ expectations of product development. One practice that takes a significant amount of time in the process of releasing software to the customers is testing. It is a clear trend that organizations are increasing the amount of test automation compared to manual testing. However, manual testing is still prominent in GUI-based testing due to challenges interacting with a GUI from test scripts. One of the most prominent challenges is synchronizing test script execution with the system under test. Objectives. This research aims to compare static and dynamic synchronization of GUI-based tests. This comparison will be conducted by replicating an existing Selenium test suite using static synchronization to Playwright, which will use dynamic synchronization and run the test suites against a web-based application. These test suites will then be used to compare the two types of synchronization from the perspective of test execution efficiency, test output correctness, and maintenance cost.Methods. The research methodology we chose is experiment. We have chosen Selenium to represent static synchronization and Playwright to represent dynamic synchronization. We used an existing test suite in Selenium that was translated into Playwright. There are a total of 81 tests in the test suite. The test suites were used to compare test scripts that use static and dynamic synchronization from the perspective of test execution efficiency, test output correctness, and maintenance cost.Results. The data collected from the experiments shows that execution efficiency for test scripts using dynamic synchronization is significantly faster than static synchronization. A mean difference between the test suites showed a decrease of 87%. For defect identification, ten defects where used and both test suites managed to identify all of them, resulting in no difference could be found. Test maintenance cost was found that test scripts using dynamic synchronization had a positive effect with an average of 60% less time spent on maintenance.Conclusions. Based on the result, we found that test scripts using dynamic synchronization improved execution efficiency and maintenance costs without sacrificing the test output correctness.

No description available.

No description available.

Denna studie är gjord med syftet att undersöka hur ett grafiskt användargränssnitt (GUI) håller måtten baserat på effektivitet jämfört med ett kommandoradsgränssnitt (CLI). Är det så att det generellt går snabbare att jobba i ett kommandoradsgränssnitt eller beror det på vilka uppgifter som skall utföras?Vi har baserat denna studie på en generell uppfattning hos CLI-expertanvändare att ett CLI är betydligt effektivare och snabbare att jobba i än ett GUI. Vi undersöker därför i denna studie expertanvändares tillvägagångssätt i deras arbete framför datorn. Detta i form av ett utförandetest mätt på hastighet och svar från en enkätundersökning som komplement till användartestets resultat.Det resultat vi får fram visar att val av gränssnitt i huvudsak är beroende på användningsområde och uppgifternas storlek, vilket enkätsvaren bekräftar. Ju mer uppgifterna ökar i storlek och omfång desto effektivare blir CLI i jämförelse med GUI. Användartestet visar att GUI i genomsnitt inte håller samma nivå som CLI när det gäller effektivitet. Vi analyserar dessutom vilka faktorer som påverkar gränssnittens effektivitet.Nyckelord: Expertanvändare, gränssnitt, CLI, GUI, effektivitet, operativsystem. / This paper has been made in order to examine how well a graphical user interface (GUI) measures compared to a command line interface (CLI). Is it true that a CLI generally is faster to work in or does it depend on the tasks to be performed?We have based this study on a general perception among CLI-expert users that a CLI is much more efficient and faster to work in than a GUI. Therefore, in this study we investigate expert users’ performance when they work with computers. We do this with thru performance test measured on the speed and from a survey response to complement the result of the usability test.The result we obtain show that the choice of interface is mainly dependent on the tasks and data size, which is confirmed by the survey replies. The more the data increases in size and scale, the more efficient CLI gets in comparison with the GUI. The user tests shows that the GUI, on average, don’t succeed to keep the same level of efficiency as CLI. We will also analyze the factors that affect the interfaces efficiency.Keywords: Expert users, interfaces, CLI, GUI, efficiency, operation system.

I denna uppsats har det undersökts vilka användbarhetsproblem som är framträdande i HRutan, samt vilka förbättringar som kan härledas i HRutan avseende användbarhetsproblemen. HRutan är en samlingsplats för allmän självservice och information i anknytning till arbetet inom HR-området inom Malmö stad och används av anställda inom Malmö stad för arbetsrelaterade uppgifter. Undersökningen har gjorts genom att analysera ett utvalt HR-system med hänvisningar till utvalda designanvisningar och direktiv. Designanvisningarna och direktiven presenterades för den utvalda målgruppen genom en undersökning i form av intervjuer. Syftet med den första genomförda intervjun var att samla åsikter och synpunkter från målgruppen angående potentiella användbarhetsproblem i det utvalda HR-systemet. Datainsamlingen kom sedan att användas vid utformningen av ett prototypbaserat användargränssnitt. I samband men den första genomförda intervjun genomfördes även en expertutvärdering av användargränssnittet vars syfte var att styrka de användbarhetsproblem som målgruppen tidigare uttryckt. Detta genom att jämföra resultatet från båda undersökningarna och därmed finna ett framträdande resultat av användbarhetsproblem. Avslutningsvis genomfördes ytterligare en intervju med målgruppen avseende det prototypbaserade användargränssnittet för att finna underlag för om några förbättringar skett. Syftet med undersökningen är att fastställa vilka designanvisningar och direktiv som är relevanta för att uppnå en högre grad av användbarhet i ett HR-system och därmed leva upp till användarnas krav och behov. Detta för att finna de förbättringar som är vid behov för att underlätta de grundläggande funktionerna i ett HR-system och därmed finna hur design, struktur och navigering i ett HR- system kan förbättras ur ett användbarhetsperspektiv. Resultat tyder på att det finns en varierande grad av relevans för samtliga designanvisningar och direktiv där kategorierna felhantering samt feedback och återkoppling påvisar en högre grad av relevans. Kategorin hjälpmedel och genvägar tyder på en lägre grad av relevans i samband med HRutan. Resultatet påvisar även att det finns ett behov av förbättringar för samtliga kategorier. Förslagen till förbättringar baseras bl.a. på en ny konsekvent layout och dess innehållande information samt tydliggörandet av aktuella händelser och platser genom en indelning av de olika kategorierna i menyn i s.k. flikar. Andra förslag till förbättringar bygger på en ny strukturering och placering av information som presenteras med fokus på dess väsentlighet, meddelandefönster som är anpassade för de olika handlingarna men även tillägg av utgångs och ångerfunktioner. Förslagen till förbättringar belyser även vikten av ett system som sköter de grundläggande justeringarna och inmatningarna i systemet, genväg för den mest frekventa arbetsuppgiften samt en ny layout av användargränssnittet. Ytterligare förslag till förbättringar baseras på utnyttjandet av symboler samt genvägar till funktioner med flervalsalternativ för att uppnå en mer målgruppsanpassad sida. Avslutningsvis framhävs förbättringar i form av flerstegsanvisningar för utförandet av arbetsuppgifter och en logisk utformning av layout, menyer, termer, symboler och fraser. / The thesis explores the most prominent usability problems in HRutan but also addresses the improvements that can be made. This has been accomplished by studying a specific/selected HR system with references to carefully selected design guidelines and directives. The design guidelines and directives were shown to the target group through a survey in the form of an interview. The aim of the first interview was to collect the opinions and the feedback of the target group regarding the usability problems of the selected HR system. These opinions and the feedback were later used in the design of a prototype-based user interface. Together with the first interview an expert evaluation was conducted which aimed to confirm the usability issues that the target group expressed. This was completed by combining the results of usability problems from both studies and thus find a prominent result of the usability problems on the selected HR system. Finally, one more interview regarding the prototype-based user interface was done by the target group. The intention of this interview was to examine if any improvements had been made. The aim of this study is first of all to determine what design guidelines and directives are relevant to achieve a higher degree of usability in an HR system and thus meet requirements and needs of the user. The second aim is to discover and determine the improvements necessary to simplify the basic features of an HR system from a usability perspective. The last part is the aim to identify how the design, structure and navigation of an HR system can be improved from a usability perspective. The results point out that there is a varying degree of relevance for each design guidelines and directives where the categories error handling, feedback and reconnection indicates a higher degree of relevance. The category tools and shortcuts point to a lower degree of relevance in the context of HRutan. The result show that there was a necessitate for a variable degree of improvement in all categories. The suggestions for improvements are for instance based on a new consistent layout of its information and a clarification of current events and places by division of the categories in tabs. Additional proposals for improvement are the structuring and placement of information based on essentiality, message windows for the various actions as well as the addition of a number of output and regret functions. The proposals for improvement give prominence to the importance of a system that handles the most basic adjustments and inputs but also highlight the weight of the shortcuts for the most frequent task. Shortcuts for functions with multiple choice options to achieve a more targeted custom page and multi-step directions, such as video clips for the execution of tasks, are further proposal of improvements. These improvements result in a new layout of the user interface with a consistent structure and design of the layout, the menus, terminology, symbols and phrases.

Resumé Denna studie är gjord med syftet att undersöka hur ett grafiskt användargränssnitt (GUI) håller måtten baserat på effektivitet jämfört med ett kommandoradsgränssnitt (CLI). Är det så att det generellt går snabbare att jobba i ett kommandoradsgränssnitt eller beror det på vilka uppgifter som skall utföras? Vi har baserat denna studie på en generell uppfattning hos CLI-expertanvändare att ett CLI är betydligt effektivare och snabbare att jobba i än ett GUI. Vi undersöker därför i denna studie expertanvändares tillvägagångssätt i deras arbete framför datorn. Detta i form av ett utförandetest mätt på hastighet och svar från en enkätundersökning som komplement till användartestets resultat. Det resultat vi får fram visar att val av gränssnitt i huvudsak är beroende på användningsområde och uppgifternas storlek, vilket enkätsvaren bekräftar. Ju mer uppgifterna ökar i storlek och omfång desto effektivare blir CLI i jämförelse med GUI. Användartestet visar att GUI i genomsnitt inte håller samma nivå som CLI när det gäller effektivitet. Vi analyserar dessutom vilka faktorer som påverkar gränssnittens effektivitet. Nyckelord: Expertanvändare, gränssnitt, CLI, GUI, effektivitet, operativsystem. / This paper has been made in order to examine how well a graphical user interface (GUI) measures compared to a command line interface (CLI). Is it true that a CLI generally is faster to work in or does it depend on the tasks to be performed? We have based this study on a general perception among CLI-expert users that a CLI is much more efficient and faster to work in than a GUI. Therefore, in this study we investigate expert users’ performance when they work with computers. We do this with thru performance test measured on the speed and from a survey response to complement the result of the usability test. The result we obtain show that the choice of interface is mainly dependent on the tasks and data size, which is confirmed by the survey replies. The more the data increases in size and scale, the more efficient CLI gets in comparison with the GUI. The user tests shows that the GUI, on average, don’t succeed to keep the same level of efficiency as CLI. We will also analyze the factors that affect the interfaces efficiency. Keywords: Expert users, interfaces, CLI, GUI, efficiency, operation system.

Quality assurance is becoming increasingly important to implement in expanding development projects. The components being built must be tested regularly to ensure the functionality of the whole product. Leeroy applies scrum as a development method along with manual GUI tests that only are performed when all components belonging to each sprint are completed. This leads to shortage in time for a tester to apply the assigned test scenarios. Testers are therefore subjected to stress in their work as testing requires high accuracy and speed in order to effectively ensure that the components end up in a production environment. The purpose of this study is to streamline current test processes by replacing manual GUI tests with automated GUI regression tests using BDD principles. Specification of the requirements was carried out using data collection methods that were chosen for this study. The specifications were used both to evaluate the construction as well as the results obtained. The results show that it is important that both the tester and the rest of the agile team cooperate during each sprint, as the components are developed incrementally and tested regularly. The results show even the importance of prioritizing the test scenarios; this is done to ensure the efficiency of the workflow by first choosing the most important components to test. The tested aspects in this study have also proven that both frameworks Cucumber and Puppeteer have the potential to contribute to a smooth implementation of BDD in an agile development team. This is due partly to the reasonable results from the performance tests that measured the speed of feedbacks as an efficiency test, partly to a high degree of both usability and reusability. This study is limited to few test scenarios due to shortage of time given for this course and therefore the performance results doesn’t express all kind of testing scenarios. / Kvalitetssäkring blir allt viktigare att genomföra i växande utvecklingsprojekt. Komponenterna som byggs måste testas regelmässigt för att garantera funktionaliteten av produkten som utvecklas. Leeroy tillämpar idag Scrum som utvecklingsmetod med manuella tester som genomförs när alla komponenter är färdigbyggda vid slutet av varje sprint. Detta leder till att testaren har kortare tid på sig för att utföra testscenarierna. Testaren utsätts därför för stress i sitt arbete då uppdraget kräver en hög noggrannhet med snabbhet för att effektivt försäkra att komponenterna hamnar i en produktionsmiljö. Syftet med undersökningen är att effektivisera nuvarande testprocesser genom att ersätta de manuella GUI-tester med automatiserade GUI- regressionstester som tillämpar BDD principer. Specificering av kraven genomfördes med hjälp av datainsamlingsmetoder som valdes till denna undersökning. Kravspecifikationerna användes dels för utvärdering av konstruktionen och dels för utvärdering av de erhållna resultaten. Resultaten visar att det är viktigt att både testaren och resten av det agila teamet samarbetar under varje sprint, då komponenterna utvecklas inkrementellt och testas regelmässigt. Resultaten visar vikten av att prioritera testerna som kommer att utvecklas för att säkra effektiviteten i arbetsflödet och även säkra att de viktigaste funktionerna testas först. Undersökningen har visat att både Cucumber och Puppeteer kan bidra till en smidig implementation av BDD i ett agilt utvecklingsteam. Detta beror dels på de rimliga resultaten från prestandatesterna som mäter effektiviteten, dels en hög användbarhetsgrad vad gäller både läsbarhet och skrivbarhet i syntaxen och dels en hög återanvändbarhetsgrad. Denna studie avgränsades till få antal testscenarier på grund av brist på tid i undersökningen och därför visar resultaten från prestandatesterna inte alla slags testscenarier.

Background. With the development and popularization of mobile Internet, smartphones are becoming more and more popular. Android is one of the most popular platforms of smartphones.  And application is one of the most important part of a smartphone. There are a lot of money and human resources spent on Android application development every year. And quiet a big part of them goes to quality assurance of applications. Graphic user interface (GUI) testing is one important part of its quality assurance. Android phones use touch screen as the major I/O method. Therefore, GUI testing on android platform shall be different to conventional software applications that are designed to run on desktop environment. Objectives. The aim of this research is to assess the performance of two GUI testing approaches (2nd vs 3rd generation) of automated UI testing in terms of testing Android applications. By assessing these approaches, we could hopefully get insights of their advantages and limitations for using them in the context of Android development. And this aim can be divided into three objectives, to compare the time spent on implementing test cases of each tool, to compare the time costed when executing test cases of each tool, to compare the number of defects found by each tool. Methods. The research methodology we chose is controlled experiment. We have chosen UI Automator and Appium to represent 2nd generation GUI testing approach, EyeAutomate and SikuliX to represent 3rd generation GUI testing approach. We used each tool to implement and execute 120 test cases to compare them on the time spent on implementing test cases of each tool, the time costed when executing test cases of each tool, the number of real defects found by each tool, and the number of false positives found by each tool. Results. Tools using 3rd generation GUI testing approach take less time to implement test cases than tools using 2nd generation GUI testing approach. And there is no specific pattern when comparing tools using 2nd and 3rd generation GUI testing approaches in terms of time cost on executing test cases. It is different between different test cases. Besides false positive alerts appear at a much higher frequency in tools using 3rd generation GUI testing approach than tools using 2nd generation GUI testing approach. While, real defects found by each tool are the same. Conclusions. 3rd generation GUI testing approach is more efficient in terms of implementing test cases than 2nd generation GUI testing approach. But 3rd generation GUI testing approach finds much more false positives than 2nd generation approach. To decide if a defect alert is false positive or not requires human effort. In a long term, it may accumulate huge lost on human efforts. Therefore, to maintain test cases, 3rd generation approach consumes lots of human efforts.