Les développeurs d'applications Web ne sont pas tous des experts. Même s'ils utilisent des méthodes telles que UWE (UML web engineering) et les outils CASE, ils ne sont pas toujours capables de prendre de bonnes décisions concernant le contenu de l'application web, le schéma de navigation et / ou la présentation des informations. La littérature leur fournit de nombreuses lignes directrices (guidelines) pour ces tâches. Cependant, ces connaissances sont disséminées dans de nombreuses sources et non structurées. Dans cette dissertation, nous capitalisons sur les connaissances offertes par ces lignes directrices. Notre contribution est triple: (i) nous proposons un méta-modèle permettant une représentation riche de ces lignes directrices, (ii) nous proposons une grammaire permettant la description des lignes directrices existantes, (iii) sur la base de cette grammaire, nous développons un outil de gestion des lignes directrices . Nous enrichissons la méthode UWE avec cette base de connaissances menant à une approche basée sur la qualité. Ainsi, notre outil enrichit les prototypes existants d'ingénierie logicielle assistée par ordinateur basés sur UWE avec des conseils ad hoc. / Web application developers are not all experts. Even if they use methods such as UWE (UML web engineering) and CASE tools, they are not always able to make good decisions regarding the content of the web application, the navigation schema, and/or the presentation of information. Literature provides them with many guidelines for these tasks. However this knowledge is disseminated in many sources and not structured. In this dissertation, we perform a knowledge capitalization of all these guidelines. The contribution is threefold: (i) we propose a meta-model allowing a rich representation of these guidelines, (ii) we propose a grammar enabling the description of existing guidelines, (iii) based on this grammar, we developed a guideline management tool. We enrich the UWE method with this knowledge base leading to a quality based approach. Thus, our tool enriches existing UWE-based Computer Aided Software Engineering prototypes with ad hoc guidance.

The Covid-19 pandemic has affected us in different ways and expose the weaknesses of our ecosystem. Some groups of people are more vulnerable to the virus meaning they have to follow the public health authority recommendations with extra caution. At the start of this project, they recommended keeping distance and avoid a crowded environment which makes everyday living harder, especially for groups more vulnerable to the virus. In this thesis, I aim to solve this issue with a web application that extends Coops home delivery of groceries and makes it possible to order extra services as well. The project resulted in an application that is stable enough to use in production today.

The goal is to design and to implement a library for developing Java applications controlled over WWW. This library provides a virtual graphical user interface and it implements the network communication with a real remote graphical user interface. The remote graphical user interface is implemented as a Java applet. The proposed solution is based on the Remote Method Invocation (RMI) framework that provides the communication between the applet and the application running on the server.

This thesis deals with design and implementation of two web applications for BUT portal. The first is called the map of studies. It shows for student all his studies in well-arranged graphical form. The second application is the map study programme graphical viewer. It shows in graphical form the relationships between study programs and departments for each BUT faculty.

No description available.

No description available.

The primary aim of this study was to examine the effects of a web application’s navigability on user satisfaction. This was studied by developing a web application for the rental of pri- vate belongings such as tools, party equipment, outfits, et cetera. The study’s scope was hav- ing students at Linköping University as the target group. During the development phase, two different user tests were conducted on two different versions of the web application to obtain feedback on important factors within navigability such as functionalities, design, and layout. Said factors were tested with methods such as Concurrent Think-Aloud (CTA), Smith’s Mea- sure of Lostness, and Likert-styled questions. The first test provided a variety of feedback that, by applying retrospective probing, resulted in major improvements for the second user test. The study shows that in designing user tests it is important to have a widespread test group, test users without relations, and longer than one week between different iterations of a test. The study concludes that a thumbnail system is preferred over displaying products in a list. Moreover, tests showed that feedback and communication from the system improved the user experience. / Studiens huvudsakliga syfte var att undersöka hur en webbapplikations navigerbarhet påverkar användarupplevelsen. Detta gjordes genom att en webbapplikation för uthyrning av privatägda prylar såsom verktyg, festutrustning, utklädnader, etcetera utvecklades. Stu- dien hade en tydlig omfattning med studenter från Linköpings Universitet som målgrupp. Under utvecklingsfasen utfördes användartester på två olika iterationer av webbapplikatio- nen vid separata tillfällen. Detta gjordes för att samla in respons och åsikter kring centrala faktorer inom navigerbarhet, såsom funktionalitet, design och layout. Dessa faktorer testades med en rad metoder, till exempel Concurrent Think-Aloud (CTA), Smith’s Measure of Lost- ness och Likert-Styled questions. Det första testet tillhandahöll respons som då retrospektiv sondering applicerades medförde betydande förbättringar av webbapplikationen inför det andra testet. Studien visar på en rad premisser som är centrala då användartester utförs. Det är då viktigt att ha en hög variation på testgruppens deltagare, att utföra tester på deltagare som inte har någon relation till varandra, samt att vänta längre än en vecka mellan olika test. Ett antal slutsatser dras från studien. En av dessa är att thumbnail-system föredras över att visa produkterna i en lista. Testen visade också att tydlig kommunikation från systemet ökade användarvänligheten.

Nowadays, web application attacks have increased tremendously due to the large number of users and applications. Thus, industries are paying more attention to using Web application Firewalls and improving their security which acts as a shield between the app and the internet by filtering and monitoring the HTTP traffic. Most works focus on either traditional feature extraction or deep methods that require no feature extraction method. We noticed that a combination of an unsupervised language model and a classic dimension reduction method is less explored for this problem. Inspired by this gap, we propose a new unsupervised anomaly detection model with better results than the existing state-of-the-art model for anomaly detection in WAF security. This paper focuses on this structure to explore WAF security: 1) feature extraction from HTTP traffic packets by using NLP (natural language processing) methods such as word2vec and Bert, and 2) Dimension reduction by PCA and Autoencoder, 3) Using different types of anomaly detection techniques including OCSVM, isolation forest, LOF and combination of these algorithms to explore how these methods affect results.  We used the datasets CSIC 2010 and ECML/PKDD 2007 in this paper, and the model has better results.

This study is conducted to evaluate the Blazor WebAssembly framework for the Progressive Web Application (PWA) methodology. A comparative study is conducted with a ReactJS PWA as a baseline. The two frameworks are evaluated in their front-end performance and documentation of PWA-focused subjects. Front-end performance is measured between two experimental applications that test the loading times, heap memory usage and loading consistency during layout generation. It is found that a Blazor WebAssembly PWA takes on average a range of 0.34, 0.18, and 0.06 seconds less time to generate a layout than a ReactJS PWA. The Blazor WebAssembly PWA was less consistent in its loading times when handling many elements. Documentation that covers Progressive Web Application terminology was found to be different between the frameworks. The Blazor WebAssembly documentation covers more topics and provides first-hand knowledge while the ReactJS documentation covers fewer topics and relies on external sources to provide the necessary explanations. These findings indicate that Blazor WebAssembly is a faster framework when updating large amounts of elements in comparison to ReactJS. However, the ReactJS PWA was found to be overall more consistent in its loading times. Documentation varied between the two frameworks. Documentation in Blazor WebAssembly covers more Progressive Web Application subjects and is more in-depth than ReactJS.  This study only evaluates applications developed in ReactJS and Blazor WebAssembly. Both are tested on Google Chrome in a desktop environment.

No description available.