ABSTRACT Thou, Thee, Thy, Thine, Ye, You, Your, Yours: Second Person Pronouns in Two Bible Translations In the King James Version from 1611 there are eight different forms of personal pronouns for second person: the singular forms thou, thee, thy, thine and the corresponding plural forms ye, you, your and yours. Because of linguistic changes in the English language the number of the second person pronouns has declined during the centuries. Accordingly, in the New King James Version from 1990 these eight earlier pronouns are represented by only three pronouns: you, your, yours. Therefore, the hypothesis of this study was that the disappearance of so many different pronoun forms might have caused some ambiguity. To examine this, The Gospel of Luke of both Bible versions was studied and all the second person pronouns were first classified according to their case and number (nominative/accusative/dative/genitive, singular/plural) and thereafter counted. The verses of the Gospel of Luke, where both one or several persons are addressed, were read and carefully studied. Furthermore, when necessary, interesting or relevant, comparisons were also made to two other translations: Gustav V´s Bible from 1917 and the Swedish Bible Version from 2000. The results of this study show that there are differences in the numbers of the examined pronouns. These discrepancies depend on several different factors which have been discussed. In addition, the investigation gives evidence of the fact that the references of pronouns are not always completely clear: several verses, which might be perceived erroneously, were found in the modern English Bible translation.

The need for change of direction in Software Engineering has been suggested in severalresources [Power of Models]. In recent years many organizations have focused on ModelDriven Engineering (MDE) as an approach to application design and implementation.Model Driven Architecture (MDA) was introduced by Object Management Group (OMG) in2001 in support of MDE. Models are the basic elements in MDE. The focus on MDE is onthe concept of “Everything is a model”. So far several languages, tools and platforms havebeen created for MDE.In particular, models can be developed in a distributed environment, thus once they mergetogether, conflicts and inconsistencies should be detected in a convenient way to bereconciled (automatically by software or manually by developers). This project is based onprevious works that define difference and conflict metamodels of a source model. In thisreport, we introduce the benefits of versioning systems in MDE framework. A conflictmetamodel that is generated from the input metamodel and the architecture for detectingconflicts are represented. The proposed approach is metamodel independent that meansconflict metalmodel is created for any input model which conforms to Kernel Meta MetaModel (KM3). The concept of used conflict model can be also changed regardless ofmodels. The extended idea for conflicts detection, the presented architecture for modelcode management and the tools that can detect conflicts of concurrent models can help toimprove MDE in model code management. For this report, some implementation in Eclipseplatform has been rendered while some future works are suggested. / University of L'Aquila, Project group in Moedling with Alfonso Pierantonio

L’étude des amas globulaires (AGs) nous offre une opportunité d’appréhender l’histoire de leurs galaxies hôtes et ainsi l’histoire de l’univers. Dans cette thèse, je me suis intéressé aux propriétés des AGs dans différents environnements. Tout d’abord, je me suis concentré sur les AGs de l’amas de la Vierge, un amas de galaxies très dense situé à environ 16,5 Mpc. J’ai utilisé les données observées par le relevé NGVS (Next Generation Virgo Survey) pour définir un échantillon qui contient 1846AGs. J’ai ensuite comparé les couleurs de ces amas avec celles d’autres AGs originaires de la Voie Lactée et j’ai remarqué des différences de couleurs encore jamais observées, dont la nature exacte est encore énigmatique. Pour comprendre ces différences, j’ai ensuite comparé les AGs observés avec des AGs synthétiques basés sur 10 modèles de synthèse de populations stellaires. J’ai aussi étudié les âges et les métallicités ressortant de la confrontation directe des couleurs des AGs à ces modèles. En conclusion, en l’état actuel, les modèles ne rendent pas compte de la diversité identifiée dans ma thèse. Finalement, j’ai effectué une brève étude des propriétés spatiales des AGs autour de M87 pour repérer des marques d’accrétion. / Through the study of the globular cluster (GC) properties, it is possible to unravel the history of their host galaxies and by extension the history of the universe. During this thesis, I was interested in the GC properties in different environments. First, I looked at the GCs in the Virgo cluster, a dense galaxy cluster located at 16.5 Mpc. I used data from the survey NGVS (Next Generation Virgo Survey) to define a sample of 1846 GCs. Then, I compared the colors of these GCs with those of Milky Way GCs and I noted color differences never yet observed, which are still enigmatic. In order to understand these differences, I compared the observed GCs with synthetic GCs obtained with 10 stellar population synthesis models. I also studied the age and metallicity predictions of those models. In the end, in their current status, the models do not account for the diversity highlighted in my thesis. Finally, I assessed the spatial properties of the GCs around M87 in order to find any signatures of a recent accretion.

This thesis discusses the extraction of information from version control systems. Its goal is to describe the implementation of a software application that facilitates this type of extraction, focusing on the version control system Git. The theoretical part of the thesis identifies and analyses data stored in repositories. It also evaluates the tools available on the market using specific criteria. The practical part specifies development requirements, describes the resulting software application, and contains a how-to manual for extending the application and implementing one's own metrics that lead to gaining information. The application is developed in the CoffeeScript programming language and Node.js engine. It contains several example metrics. The output is a graphical user interface with interactive graphs served by a built-in HTTP server. Another output option is a machine-readable export to a file.

The Target Positioning Sensor (TPS) is used by cranes to locate containers in ports and on cargo ships. The reliability of the communication network between the TPS and the Programmable Logic Controller (PLC) is important to optimise the productivity of the container terminal. Lost data messages between the network devices will lead to delays and production loss for the terminal. The main goal of this thesis project is to make the Ethernet-based network between the TPS and the PLC more reliable. The current sensor network protocol uses the User Datagram Protocol (UDP), and the project aims to replace that with the Transport Control Protocol (TCP). This includes designing a new message handling application and performing case studies on how to best handle compatibility issues between the TPS and the PLC, to improve the longevity of the application. The case studies led to considering an adaptable behaviour toward future software updates in different parts of the network. An application which used TCP to communicate between a PC and a PLC was developed, intended to be used as a reference during future integration into the actual sensor network. The TCP application works but needs to be improved before being implemented in a real system. In addition, the project also looked into Time-Sensitive Networking, which is a method of increasing link capacity and reliability in time-sensitive network implementations. This was done through a literature study on the IEEE Time-Sensitive Networking Standard, which showed that the application of the standard could be beneficial if more sensors are added to the network of if the sampling frequency of the TPS is increased.

Dependency problems for developers are like sneezing for people with pollen allergies during the spring, an everyday problem. This is especially true when working in multi-repositories. The dependency problems that occur do so as a byproduct of enabling developers to work on different components of a project in smaller teams, where everything is version controlled.Nearly all developers use version control systems, such as Git, Mercurial, or Subversion. While version control systems have helped developers for nearly 40 years and are constantly getting updated, there are still functionalities that do not exist. One example of that is having a good way of managing dependencies and allowing developers to download projects without having to handle dependency problems manually. The solutions that version control systems offer to help manage dependencies (e.g., Git’s submodules or Mercurial’s subrepositories), do not enable developers a fail-safe download or build the project if it contains dependency problems.In this study, a case study was conducted at Saab Training and Simulation to explore methods for dependency management as well as discuss and highlight some of the problems that emerge when working with dependencies in multi-repositories.An argument can be made that the functionality of dependency management systems, both package managers and version control systems’ solutions are not up to date on how dependencies are used in the development, during this time.In this paper, a novel approach to dependency management is introduced with the possibility to describe the dependencies dynamically by providing the utility to describes usages of a repository (such as simulation of hardware or the main project). As well as discussing the necessary functionalities that are required to handle such a system.By re-opening the dialog about dependency management as well as describing problems that arise in such environments, the goal is to inspire further research within these areas.

Collaboration is one of the most important topics regarding the evolution of the World Wide Web and thus also for the Web of Data. In scenarios of distributed collaboration on datasets it is necessary to provide support for multiple different versions of datasets to exist simultaneously, while also providing support for merging diverged datasets. In this paper we present an approach that uses SPARQL 1.1 in combination with the version control system Git, that creates commits for all changes applied to an RDF dataset containing multiple named graphs. Further the operations provided by Git are used to distribute the commits among collaborators and merge diverged versions of the dataset. We show the advantages of (public) Git repositories for RDF datasets and how this represents a way to collaborate on RDF data and consume it. With SPARQL 1.1 and Git in combination, users are given several opportunities to participate in the evolution of RDF data.

Configuration management is a process for establishing and maintaining consistency of a product's performance, as well as functional and physical attributes with regards to requirements, design and operational information throughout its lifecycle. The way configuration management is implemented in a project has a huge impact on the project’s chance of success. Configuration management is, however, notoriously difficult to implement in a good way, i.e. in such a way that it increases performance and decrease the risk of projects. What works well in one field may be difficult to implement or will not work in another. The aim of this thesis is to present a process for optimizing configuration management processes, using a telecom company as a case study. The telecom company is undergoing a major overhaul of their customer relationship management system, and they have serious issues with quality of the software that is produced and meeting deadlines, and therefore wants to optimize its existing CM processes in order to help with these problems. Data collected in preparation for the optimization revealed that configuration management tools were not used properly, tasks that could be automated were done manually, and existing processes were not built on sound configuration management principles. The recommended optimization strategy would have been to fully implement a version handling tool, and change the processes to take better advantage of a properly implemented version handling tool. This was deemed too big a change though, so instead a series of smaller changes with less impact were implemented, with the aim of improving quality control to minimize the number of bugs that reached production. The majority of the changes had the purpose of replicating the most basic functions of a version handling tool, as well as automating manual tasks that were error prone. / Configuration management är en process för att etablera och bevara konsistensen hos en produkts prestanda, så väl som funktionella och fysiska attribut med avseende på krav, design och driftinformation genom dess livscykel. Hur konfigurationshantering implementeras i ett projekt har en avsevärd betydelse för huruvida projektet kommer att lyckas eller ej. Configuration management är dock ökänt för att vara svårt att implementera på ett bra sätt, d.v.s. så att det ökar prestandan och minskar risken i projekt. Det som fungerar bra inom en bransch kan vara svårt att implementera eller fungerar inte i en annan. Målet med denna studie är presentera en process for optimering av konfigurationshanteringsprocesser där ett telekomföretag använts som en fallstudie. Telekomföretaget genomgår en stor upprusting av sitt kund-system. Företaget har stora problem med kvalitén på den mjukvara de tar fram och att möta levaranstidpunkter, och vill därför förbättra sina processer för att komma till rätta med dessa problem. Data som samlades in inför optimeringen visar att CM-verktyg ej användes på korrekt vis, arbetsuppgifter som kunde automatiserats gjordes manuellt, och existerande processer byggde ej på best practices inom CM. De rekommenderade optimeringsstrategin var att implementera och använda ett versionhanteringssystem, och ändra processerna för att dra nytta av fördelarna med ett korrekt implementerat versionshanteringssystem. Detta ansågs dock vara en allt för stor förändring, så istället genomfördes ett antal mindre ändringar med mindre påverkan, med målet att förbättra kvalitetskontrollerna och minimera antalet fel som nådde produktion. Majoriteten av ändringarna hade syftet att replikera de mest grundläggande funktionaliteten hos ett versionhanteringsverktyg, så väl som att automatisera felbenägna manuella rutiner.

A common problem in the workplace is sharing digital documents with coworkers. Forsome companies the problem extends to wanting the documentskept internally backedup and controlling which people in the company has rights to read and revise certaindocuments.This paper shows different systems and models for access control, version control,and distribution of the documents that can be used to create asystem that solves theseproblems.One requirement for this system was a user interface where users can upload, down-load and manage access to their documents. Another requirement was a service thathandles version control for the documents, and a way to quickly connect and distributethe documents. The system also needed to be able to handle access control of the ver-sioned documents on document level, referred to as "fine grained access control" in thispaper.These models and systems were evaluated based on aspects of the access control mod-els, version control systems, and distribution systems andprotocols. After evaluating,appropriate selections were made to create a prototype to test the system as a whole.The prototype ended up meeting the goals that Nordicstationset for the project butonly with basic functionality. Functionality for retrieving any version from a docu-ments history, controlling access for the documents at document level, and a simpleweb based user interface for managing the documents. / Att enkelt dela dokument med arbetskollegor är något alla företag har ett behov utav.Ofta är dessa dokument interna och skall hållas inom företaget. Även inom företagetkan det finnas behov av att styra vem som har rätt att läsa ellerrevidera dokumenten.Denna examensarbetesrapport beskriver olika tekniker ochmodeller för accesskon-troll, versionshantering och distribution som kan användas för att implementera ettsystem som kan lösa de nämnda problemen.Ett av kraven för systemet var ett användargränssnitt där användare kan ladda upp ochned sina dokument. Ytterligare krav var att systemet skulleversionshantera dokumenetenoch att användare skall kunna komma åt de olika versionerna.Systemet skulle ocksåkunna hantera åtkomstkontroll på dokumentnivå, något denna examensrapport definerarsom "fine grained access control".För att designa ett sådant system så utredes och utvärderades olika tekniker kringåtkomstkontroll och versionshantering samt distributionav dokumenten. För att testasystemet så utvecklads en prototyp baserad på de valda lösningsmetoderna.Den resulterande prototypen uppfyllde de mål som Nordicstation satte för projektet,dock endast med grundläggande funktionalitet. Stöd för atthämta olika versioner avdokument, kontrollera access till dokumentet nere på dokument nivå och ett webbaseratgränssnitt för att administrera dokumenten.

A common problem in the workplace is sharing digital documents with coworkers. Forsome companies the problem extends to wanting the documentskept internally backedup and controlling which people in the company has rights to read and revise certaindocuments.This paper shows different systems and models for access control, version control,and distribution of the documents that can be used to create asystem that solves theseproblems.One requirement for this system was a user interface where users can upload, down-load and manage access to their documents. Another requirement was a service thathandles version control for the documents, and a way to quickly connect and distributethe documents. The system also needed to be able to handle access control of the ver-sioned documents on document level, referred to as "fine grained access control" in thispaper.These models and systems were evaluated based on aspects of the access control mod-els, version control systems, and distribution systems andprotocols. After evaluating,appropriate selections were made to create a prototype to test the system as a whole.The prototype ended up meeting the goals that Nordicstationset for the project butonly with basic functionality. Functionality for retrieving any version from a docu-ments history, controlling access for the documents at document level, and a simpleweb based user interface for managing the documents. / Att enkelt dela dokument med arbetskollegor är något alla företag har ett behov utav.Ofta är dessa dokument interna och skall hållas inom företaget. Även inom företagetkan det finnas behov av att styra vem som har rätt att läsa ellerrevidera dokumenten.Denna examensarbetesrapport beskriver olika tekniker ochmodeller för accesskon-troll, versionshantering och distribution som kan användas för att implementera ettsystem som kan lösa de nämnda problemen.Ett av kraven för systemet var ett användargränssnitt där användare kan ladda upp ochned sina dokument. Ytterligare krav var att systemet skulleversionshantera dokumenetenoch att användare skall kunna komma åt de olika versionerna.Systemet skulle ocksåkunna hantera åtkomstkontroll på dokumentnivå, något denna examensrapport definerarsom "fine grained access control".För att designa ett sådant system så utredes och utvärderades olika tekniker kringåtkomstkontroll och versionshantering samt distributionav dokumenten. För att testasystemet så utvecklads en prototyp baserad på de valda lösningsmetoderna.Den resulterande prototypen uppfyllde de mål som Nordicstation satte för projektet,dock endast med grundläggande funktionalitet. Stöd för atthämta olika versioner avdokument, kontrollera access till dokumentet nere på dokument nivå och ett webbaseratgränssnitt för att administrera dokumenten.