This thesis proposes a framework to support the inexperienced student user to undertake the elicitation, analysis and specification of web user requirements. It is designed to support the student during web projects and to encourage more rigorous analysis by documenting web user requirements before the student commences design and implementation. The framework comprises a process meta-model, object model, rules model, support and guidance model, consistency, completeness and correctness model, learning model, student data model and a requirements specification model. The framework was transformed into an automated Computer Aided Web Environment (CAWE) tool and tested on a number of web modules within a Higher Education Institute (HEI). The research programme adopts the Canonical Action Research (CAR) methodology, which involves one or more iterations of diagnosing, action planning, action taking, evaluating and specifying what has been learned through reflection and allows interventions to take place within the next research cycle. Students were active participants in the research programme and contributed to the development of the intervention with continuous feedback. Analysis of usage data generated by the CAWE tool provided a valuable insight into how the framework and support mechanism was used by the students. Main contributions include the extension of knowledge and understanding of Web User Requirements in Web Engineering. Contribution is made to the curriculum of Web Engineering by identifying gaps in knowledge and understanding regarding the lack of analysis techniques used by the student. ii Contribution is also made to Web and User Requirements Engineering by proposing, implementing and evaluating a range of novel methods and frameworks through student collaboration.

This thesis presents an exploration into current web browser technologies for graphicsdevelopment, and offers a framework-like solution to integrate WebGL basedgraphical features into any web application based on those findings. It is builtlargely of the 2017 investigative graduate work done at Explizit Solutions (an ITfirm based in Skellefteå, Sweden), where the goal was to discover how 3D graphicstechnology in web browsers could be incorporated into and improve the front-endof their booking system services. A refined version of the solution produced in thatwork is presented, discussed and evaluated in this dissertation along with the investigativework done to produce it.

Data collecting and preparing is generally considered a crucial process in data science projects. Especially for image data, adding semantic attributes when preparing image data provides much more insights for data scientists. In this project, we aim to implement a general-purpose central image data repository that allows image researchers to collect data with semantic properties as well as data query. One of our researchers has come up with the specific challenge of collecting images with weight data of infants in least developed countries with limited internet access. The rationale is to predict infant weights based on image data by applying Machine Learning techniques. To address the data collecting issue, I implemented a mobile application which features online and offline image and annotation upload and a web application which features image query functionality. This work is derived and partly decoupled from the previous project – ImageSfERe (Image Sharing for Epilepsy Research), which is a web-based platform to collect and share epilepsy patient imaging.

CoyoteLab is an exploration in the use of Linux container technology as a means to simplify the way students in computing fields access and complete laboratory work in their educational career. This project provides two main benefits: creating a simple way for students to log in and access their coursework without anything more than their web browser, and providing course instructors a way to verify that assigned work is completed successfully. Thanks to advances in container technology and the advent of WebSockets, this becomes a middle layer between a WebSocket opened up on the client’s browser and the SSH daemon running in the user’s container on a remote server.

<p>The use of Web applications is a growing area. While the possibilities and functionalities are increasing, so is the complexity of them, together with the threats against them because the complexity also opens up the application to vulnerabilities. It is therefore important for developers to know how a web application can be developed with security in mind.</p><p>This study’s intention has been to create an introductory documentation of what kind of techniques that exists which can produce higher security, which methods there can be within the development process and what to think about when programming secure web applications. In this paper we have investigated how theoretical manuals in the IT security department handles that area, and interviewed two developers from two different companies to see how they use security in their web applications.</p><p>The study has an exploratory technical perspective and does not explain how to practically use and interconnecting different security-enhancing technologies, but is more suppose to give a first glance at what is available and sow a seed for those interested to continue reading further about the subject. The results of the study was generated through comparison of the theoretical material with the empirical material, to then conclude the most prominent points of what are different and similar between those materials.</p><p>During the study some key points has been revealed for development: Responsibility for safety in the application lies, in the cases we looked at, with the developers to describe the technical possibilities and hence vulnerabilities when the client usually does not possess the same technical skills for that. The customer was, as the cases we studied, often not so proactive on safety and does not value it very high (if it was not a security-critical business such as being involved with defense technology). Because the customer in such cases didn’t put security as high priority, there existed a lack of motivation to spend extra money to combat threats that were not considered significant. In cases where extra recourses were spent on security, a measurement was developed that security should not cost more than the value of what it protects else the cost is unjustified. Finally it is noted that it is technically difficult to protect against human errors that can disarm the security, for example a simple or misplaced password.</p>

Background: Starting up a business is not an easy task; it requires the translation of an idea into reality and requires discipline and a clear goal setting. Moreover with the increasing need of professionalism for outstanding web development and information technology, the plan of an enterprise with high end development and low cost is generated. Purpose: This thesis has a dual purpose; firstly it sets the basis of understanding the terms of entrepreneurship and the environment where a business is created; moreover it explains the acquirement of resources and the structure of the business plan. The second objective is to develop a path for creating a web related business. This document will help to establish the goals and objectives for the performance of the company. Method: The theory presents the relevant information that has to be considered inside the firm. After the theory a business plan was created with the objective of setting the direction of the company over the next years. It is important to mention that business plans are evolving documents that have to be updated according to changes in the environment or changes in the objectives.

The use of Web applications is a growing area. While the possibilities and functionalities are increasing, so is the complexity of them, together with the threats against them because the complexity also opens up the application to vulnerabilities. It is therefore important for developers to know how a web application can be developed with security in mind. This study’s intention has been to create an introductory documentation of what kind of techniques that exists which can produce higher security, which methods there can be within the development process and what to think about when programming secure web applications. In this paper we have investigated how theoretical manuals in the IT security department handles that area, and interviewed two developers from two different companies to see how they use security in their web applications. The study has an exploratory technical perspective and does not explain how to practically use and interconnecting different security-enhancing technologies, but is more suppose to give a first glance at what is available and sow a seed for those interested to continue reading further about the subject. The results of the study was generated through comparison of the theoretical material with the empirical material, to then conclude the most prominent points of what are different and similar between those materials. During the study some key points has been revealed for development: Responsibility for safety in the application lies, in the cases we looked at, with the developers to describe the technical possibilities and hence vulnerabilities when the client usually does not possess the same technical skills for that. The customer was, as the cases we studied, often not so proactive on safety and does not value it very high (if it was not a security-critical business such as being involved with defense technology). Because the customer in such cases didn’t put security as high priority, there existed a lack of motivation to spend extra money to combat threats that were not considered significant. In cases where extra recourses were spent on security, a measurement was developed that security should not cost more than the value of what it protects else the cost is unjustified. Finally it is noted that it is technically difficult to protect against human errors that can disarm the security, for example a simple or misplaced password.

The objective of the following research is to investigate the problem of information management and conveyed experience on the World Wide Web (WWW) when multi-modal sensors and media are available. After studying related areas of work about the web and heterogeneous media, it became apparent that one of the main challenges of the area is the semantic unification of heterogeneous media. This thesis will introduce an event-based model to semantically unify media. An event is defined as something of significance that takes place at a given time and location. Using this definition and the corresponding model, a system will be designed to illustrate practical use cases for events.

<p>Information systems are getting more and more multimedia-based as well as network-based. This evolution, as well as an increased rate of change, put new demands on methods and competencies required for developing future information systems. In this work, we give an overview of the different types of information systems and methods for information systems development, especially with respect to multimedia aspects. Multimedia systems development is discussed particularly with respect to the dual processes of software engineering and content development. Possible future directions are pointed out, in which information systems development seems to become an even more multidisciplinary effort. As a result we present a list of competencies required for multimedia information systems development as well as possible research areas of interest. These research areas cover the following issues regarding the development of multimedia information systems: project management, conceptual modelling, content maintenance, requirement treatment and development approaches.</p>

<p>The aim of this thesis is the research in modern web development tools to demonstrate in which ways can this raised technologies help to make a real application more user friendly, easy to maintain and extend, and more reliable.</p><p>Some new approaches to Web applications will be presented in comparison with the traditional way, and a real application will be redesigned for including the lasts advances in Web technologies.</p> / Analysis and improvement of a publication System