What is good map design and how should information best be visualised for a human reader? This is a general question relevant for all types of design and especially for digital maps and various Geographic Information Systems (GIS), due to the rapid development of our digital world. This general question is answered in this thesis by presenting a number of principles and tips for design of maps and specifically interactive digital visualisation systems, such as a GIS. Furthermore, this knowledge is applied to the application dpPower, by Digpro, which present the tools to help customers manage, visualise, design and perform calculations on their electrical networks. The visualisation and design of the network was analysed together with the usage of two common background maps, GSD-Fastighetskartan by Lantmäteriet and Primärkartan by the municipalities, whose default appearances are defined by Digpro. The aim was to answer whether there is a more suitable design of the background maps and network to better complement the usage of dpPower and if so, what is the better design? When designing interactive systems that will later have various end-users, a user-centred design is important. Therefore, the initial step was to collect user inputs and feedback on the current design via customer interviews. This gave a set of user criteria for good map design of dpPower specifically. A study of existing relevant literature and previous work was also performed where several general key principles for good design could be identified. Finally, a comparison between the dpPower design and other existing map products, such as e.g. Google Maps and Eniro, was made where key similarities and dissimilarities were identified and discussed. These user criteria and design principles could be combined, both to present an answer to the general question “What is good design?” and to present a suggestion of new map appearance in dpPower. Key considerations in the new design suggestions were e.g. to have a toned down background map with all features in the same hue family. However, for GSD-Fastighetskartan the important convention of land classes, blue = water, green = vegetation \& yellow = open land, should be kept. Colour combinations and contrast is the most important design element and since a design cannot be optimally adapted for all types of colour vision deficiencies, the suggestion is to separate the designs to specifically target user groups of different colour vision abilities. Important map information such as e.g. detailed road data should be kept while unnecessary features such as contour lines and polygon borderlines should be hidden. Text positions should also be considered. The results were evaluated both via a survey, distributed to users of dpPower, GIT-students and users with no previous experience of GIT or dpPower, and a seminar with employees at Digpro. The conclusions drawn from the evaluation was that the presented design suggestions and principles are good, but adjustments should be made. E.g. a use of yellow for low voltage cables, as suggested for Red-Green impaired, is perhaps not the best solution. The results present a good foundation for design of dpPower but more adjustments should be made based on the evaluation and then another evaluation can be performed. It would give an even better result.

Software developers and teams typically rely on source code and tasks management tools for their projects. They tend to depend on different platforms such as GitHub, Azure DevOps, Bitbucket, and GitLab for task-tracking, feature-tracking, and bug-tracking to develop and maintain their software repositories. Individually, developers may lose concentration when having to navigate through numerous screens consisting of various platforms to perform daily tasks. Additionally, while in meetings (non-virtual), teams are often separate from their machines and often would have to rely on pure recollection of the tasks and issues related to their work. This can delay the decision-making process and take away valuable focus hours of developers. Although there is usually one person with their laptop to guide the meeting and has access to the source code management tools, this can take a lot of time as they are not familiar with all the developers’ independent works. Therefore, a new tool needs to be introduced to help accelerate individual and team meetings’ productivity. In this paper, we continued the work on Robin, a voice-assistant built to answer questions regarding GitHub issues and source code management. Robin has the ability to answer questions in addition to completing actions on the behalf of the developer. This thesis presents Robin's abilities, architecture, and implementation while also examining its usability through a user study. Our study suggests that some people love the idea of having a conversational agent for software development. However, a lot more research and iterations must be done to fully make Robin give the user experience we imagined. In this thesis, we were able to set the foundation of this idea and the lessons that we learned.

No description available.

No description available.

Kunskap om olika utvecklingsmetoder vid start av ett nytt mjukvaruutvecklingsprojekt äravgörande för utvecklarna, styrorganen och slutprodukten. Därför prioriteras ofta nya ochokända metoder ned för att säkerställa att arbetet blir gjort och att lösningen kommer attlevereras i tid och med hög kvalitet. Detta beteende gör på lång sikt att mjukvaruutvecklingsprojektgår miste om nya och bättre utvecklingsmetoder.För belysa nya utvecklingsmetoder och upplysa de som behöver, valde vi att undersökaskillnaderna i krav framställning inom området Open Source Software(OSS)1-utveckling.I vårt arbete ställer tre forskningsfrågor som ska belysa ämnet dessa bevarar vi genom attutföra en fallstudie. I fallstudien undersöker vi hur och av vilka som krav framställts i ettföretagsstyrt projekt jämfört med ett projekt drivet av en frivilligorganisation.Fallstudien visade att externa användare i frivilligorganisation OSS-projekt har lägredelaktighet, det vill säga bidrag till projektartefakter, jämfört med företagsdrivna projektdär deltagandet av externa användare är högre. Slutligen diskuterar vi implikationerna avresultaten för både OSS-projekt drivna av företag och frivilligorganisationer. Vi kan förbåda styrorganen dra slutsatsen att det är möjligt att öka både utvecklingshastighet ochproduktens värde för kunden. / Knowledge about different development methods when starting up a new software developmentproject is crucial for the developers, the governing bodies and the end product.Therefore new and unfamiliar options are taken out of the equation to make sure that thework gets done and that the solution will be delivered on time and with high quality. Thisbehaviour in the long term does, however, exclude new and better ways of executing thework in the process.To shine light upon new development methods and enlighten those who are in needof insight into a new viable option we chose to investigate the differences in requirementelicitation within the area of Open Source Software development. By examining how andby who requirements are elicited in a firm-driven project compared to a community drivenproject, we framed a total of three research questions to base our case study on.The case study showed that in community driven Open Source Software projects externalusers have low participation, in other words contributions to project artefacts, comparedto firm-driven projects where the participation of external users is high. Finally, wediscuss the potential implications of the findings for both community- and firm-driven OSSprojects. We could conclude for both types that it’s possible to increase both developmentspeed and customer product value.

Partial Post Quantum Cryptography migration of GitLab Community Edition source code with 3 main contributions 1. Devloped RubyCrypt - a simple scanner to assist the Cryptographic Inventory Compilation of Ruby apps 2. Configured git to use PQC signature (CRYSTALS-Dilithium) for commit signing 3. Included CRYSTALS-Dilithium to ssh_data, a common cryptographic Ruby gem used by GitLab (& GitHub):1. Introduction 2. Theoretical Background - Post Quantum Cryptography 2.1. Code-based Cryptography 2.1.1. McEliece Cryptosystem 2.2. Lattice-based Cryptography 2.2.1. CRYSTALS-Dilithium 3. Post Quantum Cryptography Migration of GitLab - a Case Study 3.1. Problem Statement 3.2. Related Work 3.2.1. Software Tools for Static Program Analysis 3.3. Chosen Approach 4. Implementation 4.1. Cryptographic Inventory Compilation 4.1.1. Results 4.2. Migration Planning 4.3. Migration Execution 4.3.1. PQC Commit Signatures in git 4.3.2. Including Dilithium to ssh_data 5. Conclusion and Outlook 6. References List of Tables List of Figures List of Source Code Acronyms Notation / Partielle Migration des GitLab Community Edition Source Codes auf Verfahren der Post-Quanten-Kryptographie mit 3 Hauptergebnissen 1. Entwicklung von RubyCrypt - einem simplen Scanner zur Unterstützung der Inventarisierung verwendeter Kryptographie in Ruby-Anwendungen 2. Konfiguration von git zur Verwendung des quantensicheren Signaturalgorithmus CRYSTALS-Dilithium zur Signatur von Commits 3. Integration von CRYSTALS-Dilithium in ssh_data, ein populäres kryptographisches Ruby gem welches in GitLab (und GitHub) verwendet wird:1. Introduction 2. Theoretical Background - Post Quantum Cryptography 2.1. Code-based Cryptography 2.1.1. McEliece Cryptosystem 2.2. Lattice-based Cryptography 2.2.1. CRYSTALS-Dilithium 3. Post Quantum Cryptography Migration of GitLab - a Case Study 3.1. Problem Statement 3.2. Related Work 3.2.1. Software Tools for Static Program Analysis 3.3. Chosen Approach 4. Implementation 4.1. Cryptographic Inventory Compilation 4.1.1. Results 4.2. Migration Planning 4.3. Migration Execution 4.3.1. PQC Commit Signatures in git 4.3.2. Including Dilithium to ssh_data 5. Conclusion and Outlook 6. References List of Tables List of Figures List of Source Code Acronyms Notation

Ziel dieser Arbeit ist es, die Entwicklung von RDF-Wissensbasen in verteilten kollaborativen Szenarien zu unterstützen. In dieser Arbeit wird eine neue Methodik für verteiltes kollaboratives Knowledge Engineering – „Quit“ – vorgestellt. Sie geht davon aus, dass es notwendig ist, während des gesamten Kooperationsprozesses Dissens auszudrücken und individuelle Arbeitsbereiche für jeden Mitarbeiter bereitzustellen. Der Ansatz ist von der Git-Methodik zum kooperativen Software Engineering inspiriert und basiert auf dieser. Die Analyse des Standes der Technik zeigt, dass kein System die Git-Methodik konsequent auf das Knowledge Engineering überträgt. Die Hauptmerkmale der Quit-Methodik sind unabhängige Arbeitsbereiche für jeden Benutzer und ein gemeinsamer verteilter Arbeitsbereich für die Zusammenarbeit. Während des gesamten Kollaborationsprozesses spielt die Data-Provenance eine wichtige Rolle. Zur Unterstützung der Methodik ist der Quit-Stack als eine Sammlung von Microservices implementiert, die es ermöglichen, die Semantic-Web-Datenstruktur und Standardschnittstellen in den verteilten Kollaborationsprozess zu integrieren. Zur Ergänzung der verteilten Datenerstellung werden geeignete Methoden zur Unterstützung des Datenverwaltungsprozesses erforscht. Diese Managementprozesse sind insbesondere die Erstellung und das Bearbeiten von Daten sowie die Publikation und Exploration von Daten. Die Anwendung der Methodik wird in verschiedenen Anwendungsfällen für die verteilte Zusammenarbeit an Organisationsdaten und an Forschungsdaten gezeigt. Weiterhin wird die Implementierung quantitativ mit ähnlichen Arbeiten verglichen. Abschließend lässt sich feststellen, dass der konsequente Ansatz der Quit-Methodik ein breites Spektrum von Szenarien zum verteilten Knowledge Engineering im Semantic Web ermöglicht.:Preface by Thomas Riechert Preface by Cesare Pautasso 1 Introduction 2 Preliminaries 3 State of the Art 4 The Quit Methodology 5 The Quit Stack 6 Data Creation and Authoring 7 Publication and Exploration 8 Application and Evaluation 9 Conclusion and Future Work Bibliography Web References List of Figures List of Tables List of Listings List of Definitions and Acronyms List of Namespace Prefixes / The aim of this thesis is to support the development of RDF knowledge bases in a distributed collaborative setup. In this thesis, a new methodology for distributed collaborative knowledge engineering – called Quit – is presented. It follows the premise that it is necessary to express dissent throughout a collaboration process and to provide individual workspaces for each collaborator. The approach is inspired by and based on the Git methodology for collaboration in software engineering. The state-of-the-art analysis shows that no system is consequently transferring the Git methodology to knowledge engineering. The key features of the Quit methodology are independent workspaces for each user and a shared distributed workspace for the collaboration. Throughout the whole collaboration process data provenance plays an important role. To support the methodology the Quit Stack is implemented as a collection of microservices, that allow to integrate the Semantic Web data structure and standard interfaces with the distributed collaborative process. To complement the distributed data authoring, appropriate methods to support the data management process are researched. These management processes are in particular the creation and authoring of data as well as the publication and exploration of data. The application of the methodology is shown in various use cases for the distributed collaboration on organizational data and on research data. Further, the implementation is quantitatively compared to the related work. Finally, it can be concluded that the consequent approach followed by the Quit methodology enables a wide range of distributed Semantic Web knowledge engineering scenarios.:Preface by Thomas Riechert Preface by Cesare Pautasso 1 Introduction 2 Preliminaries 3 State of the Art 4 The Quit Methodology 5 The Quit Stack 6 Data Creation and Authoring 7 Publication and Exploration 8 Application and Evaluation 9 Conclusion and Future Work Bibliography Web References List of Figures List of Tables List of Listings List of Definitions and Acronyms List of Namespace Prefixes

Sofiaängen är en psykoterapeutisk dagverksamhet och skola som ligger på Södermalm i Stockholm. Sofiaängen riktar sig till ungdomar mellan 13–20 år med psykiska och sociala problem. Sofiaängen var i behov av ett fullständigt journalsystem för att kunna underlätta deras arbetsrutiner med bokföring av patientbehandlingar. Då deras nuvarande system inte är färdigställd och behövs vidareutvecklas. Detta ledde till att arbetet delades upp i två delar, först att ta fram ett förslag på en generell processmodell för hantering av en icke färdigställda IT-system till akademin och därefter att leverera ett fullt fungerande journalsystem åt Sofiaängen. Examensarbetet har resulterat till att man har tagit fram ett förslag på generell processmodell för hantering av icke färdigställda projekt samt ett fullt fungerande journalsystem åt Sofiaängen som kan sättas direkt i drift. / Sofiaängen is a psychotherapeutic day school and school located at Södermalm in Stockholm. Sofiaängen is aimed at young people between 13-20 years with mental and social problems. Sofiaängen needed a complete journal system to facilitate their work routines with records of patient treatments. Their current system is not completed and needed further development. Thus, the work was divided into two parts, first to develop a proposal for a general process model for managing an unfinished IT system to the academy and then to deliver a fully functioning journal system for Sofiaängen. The thesis has resulted in a proposal for a general process model for handling unfinished projects as well as a fully functioning journal system for Sofiaängen, which can be put into operation immediately.

ARF6 et ARF1 sont des petites GTPases de la famille des ARF(s) qui régulent plusieurs voies de signalisation comprenant, la formation et le mouvement des vésicules, la transformation des lipides membranaires et la réorganisation du cytosquelette d’actine. À ce jour, le rôle de la protéine ARF6 et de la protéine ARF1 dans la signalisation des récepteurs couplés aux protéines G (RCPG) et des récepteurs à activité tyrosine kinase (RTK) dans les cellules endothéliales est encore très peu étudié. Le but de cette étude a été de caractériser le rôle de la protéine ARF6 dans la migration des cellules endothéliales induite par l’endothéline-1, ainsi que le rôle de la protéine ARF1 dans la sécrétion du monoxyde d’azote (NO) stimulées par le VEGF. Dans cette étude, nous montrons qu’ARF6 est essentielle à la migration des cellules endothéliales induite par l’endotheline-1. L’inhibition de l’expression d’ARF6 par interférence à l’ARN entraîne une activation marquée de la kinase FAK et son association constitutive avec Src. Par ailleurs, cette inhibition affecte l’association entre GIT1 et la kinase FAK. Ceci se traduit par une inhibition du désassemblage des contacts focaux et une augmentation de l’adhésion cellulaire menant à une diminution de la motilité. De plus, nos résultats montrent que la protéine ARF1 est essentielle à l’activation d’eNOS et à la sécrétion du NO suite à l’activation du VEGFR2 dans les cellules endothéliales BAEC. En effet, l’inhibition de l’expression d’ARF1 par interférence à l’ARN entraîne une inhibition du recrutement de la kinase Akt à la membrane plasmique et une inhibition de son activation induite par le VEGF. L’inhibition de l’activation de la kinase Akt par le VEGF conduit à une inhibition de l’activation de eNOS et de la sécrétion du NO. Dans l’ensemble, nos résultats montrent que les protéines ARF6 et ARF1 sont essentielles à la signalisation de l’ETB et du VEGFR2 pour les processus menant à la migration cellulaire et à la sécrétion du NO respectivement, deux évènements essentiels à l’angiogenèse. / ARF6 and ARF1 are small GTPases of the ARF family(s) that regulate several signalling pathways including vesicles trafficking, lipid membrane remodelling and actin cytoskeleton reorganization. To date, the role of ARF6 and ARF1 in GPCR and RTK signalling, in endothelial cells, is little known. In this thesis, we aimed to characterize the role of ARF6 in the migration of endothelial cells induced by Enodothelin-1, and the role of ARF1 in the secretion of NO induced by VEGF. We show that ARF6 is essential for endothelial cell migration induced by endothelin-1. Inhibition of ARF6 expression using RNA interference markedly impaired basal and ET-1 stimulated cell migration. In this condition, FAK is found constitutively associated with Src. In contrast, depletion of ARF6 impairs the ability of GIT1 to form an agonist-promoted complex with FAK, thereby preventing disassembly of focal adhesions. As a consequence, adhesion of ARF6-depleted endothelial cells is increased and their motility is reduced. Furthermore, our result shows that ARF1 GTPase is essential for the activation of eNOS and the secretion of NO following VEGFR2 activation in endothelial cells. Inhibition of ARF1 expression using RNA interference markedly impaired the recruitment of Akt to the plasma membrane and its phosphorylation by the VEGF. As a consequence, the inhibition of Akt leads to an inhibition of eNOS, a well known downstream target, which in turn leads to inhibition of NO production. All together, our results indicate that ARF6 and ARF1 are essential for the ETB and the VEGFR2 signalling leading to cell migration and NO secretion respectively, two required steps for angiogenesis.

Syndromic craniosynostosis is most commonly associated with mutations in Fibroblast Growth Factor Receptor genes (FGFR)-1, 2 and 3. Clinical and animal reports suggest a link between FGFR-associated craniosynostosis and defects in the gastrointestinal tract (GIT). Objective: to determine whether GIT malformations occur more frequently in the craniosynostosis population with a known FGFR mutation when compared to the general population. Methods: A retrospective chart review of patients diagnosed with Crouzon, Pfeiffer or Apert syndromes between 1990 and 2011 was performed at the Hospital for Sick Children in Toronto. Thirty-two charts meeting inclusion criteria were analyzed for any history of GIT abnormalities. Results: Three out of 32 patients had documented intestinal/bowel malrotations while 7 had gastroesophageal reflux disease. All patients had documented FGFR2 mutations, a finding in line with previous studies and published case reports. Conclusions: Results suggest an association between FGFR-associated craniosynostosis and GIT malformations.