A precise simulation requires a large amount of input data such as geometrical descriptions of the crystal structure, the external forces and loads, and quantitative properties of the material. Although some powerful applications already exist for research purposes, they are not widely used in education due to complex structure and unintuitive operation. To cater to the generic user base, a front-end application for material simulation software is introduced. With a graphic interface, it provides a more efficient way to conduct the simulation and to educate students who want to enlarge knowledge in relevant fields. We first discuss how we explore the solution for the front-end application and how to develop it on top of the material simulation software developed by mechanical engineering lab from Georgia Tech Lorraine. The user interface design, the functionality and the whole user experience are primary factors determining the product success or failure. This material simulation software helps researchers resolve the motion and the interactions of a large ensemble of dislocations for single or multi-layered 3D materials. However, the algorithm it utilizes is not well optimized and parallelized, so its performance of speedup cannot scale when using more CPUs in the cluster. This problem leads to the second topic on scientific computing, so in this thesis we offer different approaches that attempt to improve the parallelization and optimize the scalability.

The diploma thesis deals with the design, creation and implementation of a software application in the corporate environment of Velká Pecka s.r.o., better known as Rohlík. The first goal is to analyze the given company and find its shortcomings. The second, the main one, is to create and implement a software, which would eliminate them. The resulting solution is a mobile application, which improves issue reporting in their warehouses, thus saving resources overall.

User experience design is the process of improving the accessibility and use of a product during user’s interaction with it. This study investigates the issues that occur in the coordination of UX design and software development. Furthermore, it examines diverse types of conflicts between UX designers, front-end and back-end developers, factors contributing to these conflicts and their influence on the software development process. The method used in this study is a survey conducted in an online form with a target group of practitioners. The data show that task conflicts are the most common type of conflicts in teams, that gender of a person can influence its awareness of the project status and that age and geographical location do not affect the occurrence of the identified conflicts.

Made available in DSpace on 2016-06-02T19:50:25Z (GMT). No. of bitstreams: 1 6457.pdf: 3485036 bytes, checksum: 29d5a25444712bfd366a4807cf19ff2c (MD5) Previous issue date: 2014-12-12 / Universidade Federal de Sao Carlos / Pre- development phase and corresponds to the activities ranging from identifying opportunities to generate product concepts. Throughout these activities there is a dynamic and complex flow of information about business strategies, requirements and market trends, technological alternatives and resource allocation. At this stage important decisions are made, and if misleading may result in failures in the performance of the new product. The subject has gained importance in recent years, however, there is still not an understanding on how to coordinate the activities of the predevelopment or which results are expected in this phase, therefore being a gap in the literature. This thesis aims to identify and analyze the practices, technical and tools what are adopted in front-end development in a sample of manufacturing firms. Through systematic literature review identified ten reference models for the front end development. These were published between 1988 and 2013 and seek to systematize the activities of pre-development and guide managers in conducting phase, proposing technical and management support tools. 57 different techniques have been identified. Through multiple case studies it was observed that all studied companies adopt referential models for conducting the activities of front end development. As in literature these models followed by companies differ mainly in relation to the number of stages or activities, but adopt some techniques and tools as well diffused in the literature. We observe that the most common practices in all companies can be grouped into early, middle and end activities, which divide the front end development in three distinct phases. For every moment of the predevelopment can be selected a set of techniques and support tools. These techniques and tools do not necessarily have to be adopted together because they have different natures, but are a "package" of suggestions to be considered. In addition, internal and external factors in the companies affect such practices. It was also possible to identify, in the companies analyzed, finding it difficult to measure the performance of the activities of the pre-development phase itself, and the PDP as a whole, so some possible performance indicators for this phase were suggested. Another difficulty associated with the use of these techniques and tools is that they require financial and time resources, and all require the skills of those who lead. Therefore, the most modern and best potential for achieving results technique can be ineffective if conducted by people who do not have necessary skills and appropriate technical support. / O pré-desenvolvimento corresponde a fase e as atividades que vão da identificação de oportunidades à geração de conceitos de produtos. Ao longo destas atividades existe um fluxo dinâmico e complexo de informações sobre estratégias de negócios, requisitos e tendências do mercado, alternativas tecnológicas e alocação de recursos. Nesta fase importantes decisões são tomadas, e se equivocadas podem resultar em falhas no desempenho do novo produto. O tema ganhou importância nos últimos anos, no entanto, ainda não existe um entendimento sobre como coordenar as atividades do pré-desenvolvimento ou sobre quais resultados se esperarem desta fase, sendo, portanto uma lacuna na literatura. Esta Tese objetiva identificar e analisar as práticas, técnicas e ferramentas de pré-desenvolvimento adotadas em uma amostra de empresas industriais. Através de revisão bibliográfica sistematizada foram identificados dez modelos referenciais para o pré-desenvolvimento. Estes foram publicados entre 1988 e 2013 e buscam sistematizar as atividades do pré-desenvolvimento e orientar os gestores na condução da fase, propondo técnicas e ferramentas de apoio ao gerenciamento. Foram identificadas 57 diferentes técnicas. Por meio de estudo de múltiplos casos observou-se que todas as empresas estudadas adotam modelos referenciais para condução das atividades do pré-desenvolvimento. Assim como na literatura, estes modelos adotados pelas empresas diferenciam-se, principalmente, em relação ao número de fases ou atividades, mas adotam algumas técnicas e ferramentas bem difundidas pela literatura. Observa-se, deste modo, que as práticas mais comuns em todas as empresas podem ser agrupadas em atividades iniciais, intermediárias e finais, que dividem o prédesenvolvimento em três momentos distintos. Para cada momento do pré-desenvolvimento podem ser selecionadas técnicas e ferramentas de apoio. Estas técnicas e ferramentas não necessariamente devem ser adotadas em conjunto, pois possuem naturezas distintas, mas são um pacote de sugestões a ser considerado. Além disso, fatores internos e externos às empresas condicionam tais práticas. Também foi possível identificar que existem dificuldades por parte das empresas analisadas em medirem o desempenho das atividades do pré-desenvolvimento na própria fase e no PDP como um todo. Por isso foram sugeridos alguns possíveis indicadores para essa fase. Outra dificuldade associada ao uso destas técnicas e ferramentas é que muitas demandam recursos financeiros e tempo; e todas demandam habilidades de quem as conduz. Portanto, a técnica mais moderna e com melhor potencial para alcance de resultados pode ser ineficaz se conduzida por pessoas que não tenham habilidades necessárias e apoio técnico adequado.

Jag kommer i denna uppsats beskriva den designprocess som pågått vid skapandet av en webbaserad informationsplattform från koncept till slutprodukt. Mitt uppdrag har varit att effektivisera en webbyrås nuvarande sätt att hantera och sprida information på, som bestod av en blandning mellan digital och analog information, och skapa en ny webbaserad informationsplattform. Den nya webbaserade informationsplattformen ska kunna samla all information på en plats och skapa ett effektivare informationsutbyte mellan de anställda på företaget. Jag har använt mig av två teoretiska ramverk; Nielsens tio heuristics samt Krugs visuella design hierarki. Jag har arbetat nära beställaren för att kunna skräddarsy webbplatsen till deras behov. Resultatet efter ett omfattande arbete med designmallar och front-end kodning blev grunden för webbyråns webbaserade informationsplattform, utvecklad för att effektivisera spridningen av information på företaget. / In this essay I will describe the design process during the creation of a web-based information platform, from concept to final product. My assignment has been to take a web agency’s current way of managing and distributing information, which consisted of a mix between digital and analog information, and create a new web-based information platform. The new web-based information-platforms purpose is to gather all information in one place for easier exchange of information between employees at the company and make it more efficient. I used two theoretical frameworks as a theoretical base working on the project; Nielsen's ten heuristics and Krugs visual design hierarchy. I have worked closely with the client to customize the platform to their needs. The result after extensive work with design templates and front-end coding became the foundation for the web agency’s web-based platform, developed to distribute information more efficiently within the agency.

Graphical User Interface, which is known as GUI, is a way for a person to communicate and interact with a system through icons or other visual indicators. A well designed and intuitive user interface is critical to the success of a system since it encourages a natural interaction between a user and a system, thus conveying information more clearly and efficiently to the user.The aim of this study is to design and develop a user interface that is used in a financial technology company in their credit risk assessment process. The current user interface contains a visualization of an individual credit assessment flow together with a lot of data that is generated in the process. Some of the data is not properly visualized, which leads to confusion among end users.In order to optimize the user experience, a user-centered design approach was used combined with a heuristic evaluation. A new user interface was designed and implemented and according to the heuristic evaluation result, the usability was greatly improved. The new interface is able to help the company to visualize their credit risk assessment process in a better way and facilitate credit officers to make credit decisions. The result could also provide insights to other companies or organizations in presenting their data more clearly and effectively. / Grafiskt användargränssnitt, som även kallas GUI, är ett sätt för en person att kommunicera och interagera med ett system genom ikoner eller andra visuella indikatorer. Ett väl utformat och intuitivt användargränssnitt är avgörande för framgången för ett system, eftersom det uppmuntrar till en naturlig interaktion mellan en användare och ett system och därmed förmedlar information tydligare och effektivare till användaren.Syftet med denna studie är att designa och utveckla ett användargränssnitt som används i ett finansiellt teknikföretag i deras kreditriskbedömningsprocess. Det nuvarande användargränssnittet innehåller en visualisering av ett individuellt kreditbedömningsflöde tillsammans med mycket data som genereras i processen. En del av data är inte korrekt visualiserade, vilket leder till förvirring bland slutanvändare.För att optimera användarupplevelsen användes en användarcentrerad designmetod i kombination med en heuristisk utvärdering. Ett nytt användargränssnitt designades och implementerades och enligt det heuristiska utvärderingsresultatet förbättrades användbarheten kraftigt. Det nya gränssnittet kan hjälpa företaget att visualisera sin kreditriskbedömningsprocess på ett bättre sätt och underlätta kreditansvariga att fatta kreditbeslut. Resultatet kan också ge andra företag eller organisationer insikter om att presentera sina uppgifter tydligare och mer effektivt.

Quality assurance and software testing of software artifacts is as important as ever and this is especially so the case in web applications. The web applications of today are more complex and are used in more critical systems at a larger scale than ever before. However, testing of these applications is very challenging due to their dynamic nature. It is somewhat challenging to find clear and up-to-date guidelines on how to implement and evaluate regression software testing in small and medium-size enterprises (SME’s) developing web applications. The purpose of this thesis was to investigate the problem at hand and propose an approach to implementing software regression testing in web applications for SME’s. That is, recommending what to test, recommending what kind of software testing could be implemented and using what state of the art front end testing frameworks. An in-depth literature study was conducted to see what had been done in the past and present. Two rounds of semi structured in-depth interviews were conducted with software developers at the company where this thesis was conducted. The main purpose of the first interview was to find business goals from which to derive and subsequently create a testing suite in four different testing frameworks; Cypress, Jest, Playwright and Vitest. The purpose of the second interview was to evaluate and compare the aforementioned testing suites in order to propose an approach on software testing in web applications. In addition, code coverage and mutation scoring was also considered when evaluating the testing suites. The findings of this thesis is that a reasonable approach of introducing software testing into an SME which develops a web application, is to use business requirements for generating test cases and prioritizing end-to-end testing since the perceived benefits of the latter in this thesis far outweigh the benefits of the component testing suites although a combination of both would be the best of both worlds. Although this thesis was conducted on a web application written in React, the findings and recommendations can be applied to any front end framework such as Angular or Vue. / Kvalitetssäkring och testning av mjukvara är lika viktigt som alltid och detta är i synnerhet även fallet i webbapplikationer. Dagens webbapplikationer är mer komplexa och används i mer kritiska system på en större skala än någonsin tidigare. Dessvärre är det svårt att testa dessa applikationer eftersom att de är dynamiska. Det är svårt att hitta riktlinjer för hur man ska implementera och utvärdera regressionstester på små och medelstora företag (SMF) som utvecklar webbapplikationer. Syftet med denna uppsats var att undersöka problemet och föreslå en riktlinje för hur man kan implementera regressionstestning i SMF och i webbapplikationer. Detta innebär att föreslå vad man kan testa, vilken form av mjukvarutestning man kan implementera och med vilka moderna testningsramverk man kan göra detta med. En ingående litteraturstudie genomfördes för att ta reda på vad som hade gjorts tidigare inom området. Två rundor av semistrukturerade intervjuer genomfördes med mjukvaruutvecklarna på företaget där uppsatsen genomfördes. Syftet med den första intervjun var att hitta företagsmål som sedan agerade grund till testningssviter i fyra olika ramverk; Cypress, Jest, Playwright och Vitest. Syftet med den andra intervjun var att utvärdera och jämföra dessa testsviter för att rekommendera ett tillvägagångssätt för att implementera mjukvarutestning i webbapplikationer. Utöver intervjuerna så bidrog mutationspoäng och kodtäckning till rekommendationerna. Uppsatsen finner att ett rimligt sätt att implementera regressionstester i ett SMF och en webbapplikation är att generera testfall utifrån affärskrav och att prioritera testning på användarnivå eftersom att fördelarna från denna nivå av testning överväger fördelarna från komponenttestning. Allra helst bör man implementera en kombination av båda nivåerna. Fastän denna uppsats undersökte en webbapplikation i React så kan dessa upptäckter och rekommendationer även tillämpas på vilket frontendramverk som helst så som exempelvis Angular eller Vue.

User interfaces are a crucial point in the usage of products. A user interface is developed to make a product easy to use and understand while also presenting data, feedback and functionality to the user. In this thesis we present and explain the whole development process of a front end project. The Swedish company, Kemizares, was searching for a user interface for their finance module in their upcoming application. In this work we developed the user interface for such a module with regards to Kemizares’ functional requirements as well as the necessity that the user interface of the module could be integrated into the their application which already had an existing user interface. The solution to the problem began with a literature study in which we researched tools and programs we would use to develop the module as well as researching national and international requirements for invoices to identify necessary data to use in the finance module. Afterwards we set up a timeline with deadlines to guide us throughout the development. An agile iterative feedback method was used during the implementation of the module with Kemizares. The finance module was created and with the iterative feedback method we used during development we were able to ensure that Kemizares was satisfied with the product. However, due to limiting factors we were not able to finish the whole module and hence not able to fulfill all the requirements. The conclusion is that the module in its current state is not a viable solution for Kemizares since it was left undone but a good ground to continue from that has taken required financial data, functional requirements, and design compatibility with the rest of the application into consideration. / Användargränssnitt är en viktig punkt i användningen av produkter. Ett användar-gränssnitt är utvecklat för att göra en produkt enkel att använda och förstå samtidigt som den presenterar data, feedback och funktionalitet för användaren. I denna rapport presenterar och förklarar vi hela utvecklingsprocessen för ett frontend-projekt. Det svenska företaget Kemizares letade efter ett användargränssnitt för sin finansmodul i sin kommande applikation. I detta arbete utvecklade vi användargränssnittet för en sådan modul med avseende på Kemizares funktionella krav samt behovet av att modulens användargränssnitt kunde integreras i deras applikation som redan hade ett befintligt användargränssnitt. Lösningen på problemet började med en litteraturstudie där vi undersökte verktyg och program som vi skulle använda för att utveckla modulen samt undersökte nationella och internationella krav på fakturor för att identifiera nödvändiga data att använda i finansmodulen. Därefter satte vi upp en tidslinje med deadlines för att vägleda oss genom hela utvecklingen. En agil iterativ återkopplingsmetod användes under implementeringen av modulen med Kemizares. Finansmodulen skapades och med den iterativa återkopplingsmetoden som vi använde under utvecklingen kunde vi säkerställa att Kemizares var nöjd med produkten. Men på grund av begränsande faktorer kunde vi inte avsluta hela modulen och kunde därför inte uppfylla alla krav. Slutsatsen är att modulen i sitt nuvarande tillstånd inte är en lönsam lösning för Kemizares eftersom den lämnades ofärdig, men en bra grund att fortsätta från som har tagit hänsyn till nödvändiga ekonomiska data, funktionella krav och designkompatibilitet med resten av applikationen.

The diploma thesis on Development of Front-end Applications focuses on the design of computerization of enterprise processes covered by a unified front-end application. Exploratory research was used to suggest working methods to solve technological growth of the enterprise and how to evaluate business need of a front-end application. Later chapters present basic summary of development methodology used for automation of business processes. The diploma thesis innovatively proposes a role of a front-end specialist who does not need to create a program code and has closer relation to business departments. There are recommend analytical standards and development tools for automation of business processes as well as front-end implementation. Finally the work attaches a model example demonstrating relative simplicity and practical realization of new techniques for front-end application development. Powered by TCPDF (www.tcpdf.org)

Sweden produced 215 kilotons of electronic waste in 2016. One way to reduce this amount is to repair electronic devices when they fail instead of replacing them. The company Mavenoid has a troubleshooting service in the form a web application to help troubleshoot machines like for example consumer electronics. The company desired a tool to visualize data about the usage of the troubleshooting models in their web app. The prospect was that the users who build the troubleshooting models would be able to analyse how their models are being used and how well they work with the tool. To implement the tool, a method with three phases was used. An initial preparation phase with requirements elicitation via a domain analysis and set-up of the development environment, a development phase with iterative development and requirements management with weekly meetings and an analysis phase with evaluation of the tool according to the requirements and the status of a pull request. The product met eight out of ten requirements and was of a sufficiently high quality that it could be integrated into the company’s system. The use of the library C3 resulted in a 21% increase of the web application’s build size. / Sverige producerade 2016 215 kiloton elektronikavfall. Ett sätt att minska denna mängd är att reparera elektronik när den fallerar istället för att byta ut den. Företaget Mavenoid erbjuder en tjänst i form av en React webapplikation för att underlätta felsökning av maskiner som t.ex. hemelektronik. Företaget eftersökte ett verktyg för att visualisera data om användningen av felsökningsmodellerna i sin webbapplikation. Förhoppningen var att de användare som bygger modellerna via det nya verktyget skulle kunna analysera hur deras modeller används och väl de fungerar. För att utveckla verktyget användes en metod med tre faser. En inledande förberedelsefas med kravinsamling via en domänundersökning och uppbyggnad av utvecklingsmiljö, en utvecklingsfas med iterativ utveckling och kravhantering med veckomöten och en analysfas med utvärdering av verktyget efter kraven och status på en pull-request. Produkten uppfyllde åtta utav tio av de insamlade kraven och var av tillräckligt hög kvalitet att integreras i företagets system. Användningen av biblioteket C3 medförde att webapplikationens transaktionsstorlek ökade med ca 21%