Dans une époque qui manifeste une exacerbation de la représentation de soi (àtravers les réseaux sociaux notamment), notre objet d'étude propose uneréflexion sur la mémoire et la reconstruction d'histoires dans les pratiquesartistiques. Utilisant comme point de départ une production photographiquepersonnelle (Reprises), nous proposons une articulation entre théorie etcréation, dans une dialectique qui part de l'analyse des oeuvres personnelles,pour établir un dialogue avec des théoriciens et des oeuvres contemporainestraitant ces problématiques. Dans ce type de démarches rétrospectives quiréinterprètent le passé, les artistes travaillent à partir des traces matérielles etmnésiques, telles les images d'albums de famille, les archives, les documents oules témoignages. Mêlant des univers esthétiques différents dans une nouvelleunité, ils font coexister leurs propres images avec des sources existantes, des viesdisparues avec leurs propres existences. Leurs oeuvres deviennent alors unerecréation artistique et postulent un espace narratif singulier qui évoque unepoétique de la mémoire. Partielles et fragmentaires, elles donnent à voir unrécit reconfiguré par l'imaginaire et le montage. Elles dépassent le champstrictement photographique et ouvrent leur langage au dialogue avec les autresarts, prenant la forme d'oeuvres hybrides. Quelle relation établir entre mémoire,reconstruction et identité, entre histoire individuelle et histoire collective ? Si lepassé est métamorphosé, comment le reconstruire ? / In a time of exacerbation of the self-representation (through the socialnetworks, among other things), our subject of study proposes a reflection onmemory and the reconstruction of histories in the artistic practices. Using as astarting point a personal photographical work (Reprises), we propose a linkbetween theory and creation, in a dialectic that starts from the analysis ofpersonal works, to establish a dialogue with theorists and contemporaryartworks dealing with these issues. In this kind of retrospective approaches thatreinterpret the past, the artists work from the material and memory traces, suchas the images of family albums, archives, documents, or testimonies. Mixingdifferent esthetical universes in a new unity, they make coexist their ownimages with existing sources, disappeared lives with their own existences. Theirworks thus become a artistic re-creation and postulate a special narrative spacewhich evokes a poetics of the memory. Partial and fragmentary, they show anarrative reconfigured by the imaginary and the editing. They exceed thestrictly photographical field and open their language to the dialogue with otherarts, taking the form of hybrid artworks. What relation can be set betweenmemory, reconstruction and identity, between individual and collectivehistory ? If the past is being transformed, how to rebuild it ?

Framework-specific modeling languages (FSMLs) help developers build applications based on object-oriented frameworks. FSMLs formalize abstractions and rules of the framework's application programming interfaces (APIs) and can express models of how applications use an API. Such models, referred to as framework-specific models, aid developers in understanding, creating, and evolving application code. We present the concept of FSMLs, propose a way of specifying their abstract syntax and semantics, and show how such language specifications can be interpreted to provide reverse, forward, and round-trip engineering of framework-specific models and framework-based application code. We present a method for engineering FSMLs that was extracted post-mortem from the experience of building four such languages. The method is driven by the use cases that the FSMLs under development are to support. We present the use cases, the overall process, and its instantiation for each language. The presentation focuses on providing concrete examples for engineering steps, outcomes, and challenges. It also provides strategies for making engineering decisions. The presented method and experience are aimed at framework developers and tool builders who are interested in engineering new FSMLs. Furthermore, the method represents a necessary step in the maturation of the FSML concept. Finally, the presented work offers a concrete example of software language engineering. FSML engineering formalizes existing domain knowledge that is not present in language form and makes a strong case for the benefits of such formalization. We evaluated the method and the exemplar languages. The evaluation is both empirical and analytical. The empirical evaluation involved measuring the precision and recall of reverse engineering and verifying the correctness or forward and round-trip engineering. The analytical evaluation focused on the generality of the method.

<p>Object-oriented frameworks are currently widely used in software application development. Unfortunately, they are known to be generally difficult to use because of the difficulty in understanding the concepts and constraints in different frameworks. With the formalization of framework concepts and constraints in domain-specific modeling languages called framework-specific modeling languages (FSMLs), previous works have shown that round-trip engineering between models of applications using frameworks and the application code is possible to aid framework application development.</p> <p>Framework-specific modeling languages only capture, however, framework concepts and constraints and hence, lack the expressiveness of general-purpose modeling languages. For this reason, the complete code for an entire framework application cannot be generated from the model in the model editor using round-trip engineering, and the user would need to switch to the code editor to program the application logic code. Also, since models are only abstractions of code, implementation details in code may be missing in models. Although default implementation details can be used when generating code from a model, the generated code might require further customization by the user, which would also require switching to the code editor.</p> <p>To reduce the need for the user to switch between the model editor and the code editor and to reduce the need to customize the generated code, this thesis presents a model-guided approach to providing code assistance for framework application development directly in the code editor, where additional implementation details can also be obtained. An approach to building a context-sensitive code assistant that aids the user in the implementation of framework concepts with the consideration of framework constraints is described. A prototype has further been implemented and applied on two widely popular frameworks. The evaluation in this thesis analyzes and characterizes framework concepts and shows that the framework-based code assistant can reduce the need to customize the generated code in the code editor when compared to code generation from the model editor.</p>

Framework-specific modeling languages (FSMLs) help developers build applications based on object-oriented frameworks. FSMLs formalize abstractions and rules of the framework's application programming interfaces (APIs) and can express models of how applications use an API. Such models, referred to as framework-specific models, aid developers in understanding, creating, and evolving application code. We present the concept of FSMLs, propose a way of specifying their abstract syntax and semantics, and show how such language specifications can be interpreted to provide reverse, forward, and round-trip engineering of framework-specific models and framework-based application code. We present a method for engineering FSMLs that was extracted post-mortem from the experience of building four such languages. The method is driven by the use cases that the FSMLs under development are to support. We present the use cases, the overall process, and its instantiation for each language. The presentation focuses on providing concrete examples for engineering steps, outcomes, and challenges. It also provides strategies for making engineering decisions. The presented method and experience are aimed at framework developers and tool builders who are interested in engineering new FSMLs. Furthermore, the method represents a necessary step in the maturation of the FSML concept. Finally, the presented work offers a concrete example of software language engineering. FSML engineering formalizes existing domain knowledge that is not present in language form and makes a strong case for the benefits of such formalization. We evaluated the method and the exemplar languages. The evaluation is both empirical and analytical. The empirical evaluation involved measuring the precision and recall of reverse engineering and verifying the correctness or forward and round-trip engineering. The analytical evaluation focused on the generality of the method.

<p>Object-oriented frameworks are currently widely used in software application development. Unfortunately, they are known to be generally difficult to use because of the difficulty in understanding the concepts and constraints in different frameworks. With the formalization of framework concepts and constraints in domain-specific modeling languages called framework-specific modeling languages (FSMLs), previous works have shown that round-trip engineering between models of applications using frameworks and the application code is possible to aid framework application development.</p> <p>Framework-specific modeling languages only capture, however, framework concepts and constraints and hence, lack the expressiveness of general-purpose modeling languages. For this reason, the complete code for an entire framework application cannot be generated from the model in the model editor using round-trip engineering, and the user would need to switch to the code editor to program the application logic code. Also, since models are only abstractions of code, implementation details in code may be missing in models. Although default implementation details can be used when generating code from a model, the generated code might require further customization by the user, which would also require switching to the code editor.</p> <p>To reduce the need for the user to switch between the model editor and the code editor and to reduce the need to customize the generated code, this thesis presents a model-guided approach to providing code assistance for framework application development directly in the code editor, where additional implementation details can also be obtained. An approach to building a context-sensitive code assistant that aids the user in the implementation of framework concepts with the consideration of framework constraints is described. A prototype has further been implemented and applied on two widely popular frameworks. The evaluation in this thesis analyzes and characterizes framework concepts and shows that the framework-based code assistant can reduce the need to customize the generated code in the code editor when compared to code generation from the model editor.</p>

Software development processes incorporate a variety of different artifacts (e.g., source code, models, and documentation). For multiple reasons the data that is contained in these artifacts does expose some degree of redundancy. Ensuring global consistency across artifacts during all stages in the development of software systems is required, because inconsistent artifacts can yield to failures. Ensuring consistency can be either achieved by reducing the amount of redundancy or by synchronizing the information that is shared across multiple artifacts. The discipline of software engineering that addresses these problems is called Round-Trip Engineering (RTE). In this thesis we present a conceptual framework for the design RTE systems. This framework delivers precise definitions for essential terms in the context of RTE and a process that can be used to address new RTE applications. The main idea of the framework is to partition models into parts that require synchronization - skeletons - and parts that do not - clothings. Once such a partitioning is obtained, the relations between the elements of the skeletons determine whether a deterministic RTE system can be built. If not, manual decisions may be required by developers. Based on this conceptual framework, two concrete approaches to RTE are presented. The first one - Backpropagation-based RTE - employs change translation, traceability and synchronization fitness functions to allow for synchronization of artifacts that are connected by non-injective transformations. The second approach - Role-based Tool Integration - provides means to avoid redundancy. To do so, a novel tool design method that relies on role modeling is presented. Tool integration is then performed by the creation of role bindings between role models. In addition to the two concrete approaches to RTE, which form the main contributions of the thesis, we investigate the creation of bridges between technical spaces. We consider these bridges as an essential prerequisite for performing logical synchronization between artifacts. Also, the feasibility of semantic web technologies is a subject of the thesis, because the specification of synchronization rules was identified as a blocking factor during our problem analysis. The thesis is complemented by an evaluation of all presented RTE approaches in different scenarios. Based on this evaluation, the strengths and weaknesses of the approaches are identified. Also, the practical feasibility of our approaches is confirmed w.r.t. the presented RTE applications.

Due to rapid increasing in complexity of Internet, quantifying the performance of protocol helps in assessing the application behavior with respect to network performance. TCP is an important protocol that is used by some important applications on Internet such as HTTP, FTP and soon. To analyze TCP, Round trip times is one of the metric used. As it is a internal metric of TCP used to find the retransmission timeout of sent packet. Round trip times means measuring elapsed time between the sent packet and recieving its acknowledgment that covers the sequence number of the sent packet(i.e., from source to destination and vice-a-versa). Round trip times is a metric that is recognised by IETF as Quality of Service parameter. We design a tool here that will calculate the round trip times for each stream. This round trip times helps us to understand the protocol behavior. In this document, we discuss the design, implementation issues carried out while developing the tool. This tool is capable of reading offline as well as online streams and helps us to analyze the statistics obtained from collected round trip times of each stream. / 91-40-24023214

Indoor positioning is desired in many areas for various reasons, such as positioning products in industrial environments, hospital equipment or firefighters inside a building on fire. One even tougher situation where indoor positioning can be useful is locating a specific object on a shelf in a commercial setting. This thesis aims to investigate and design different network deployment strategies in an indoor environment in order to achieve both high position estimation accuracy and availability. The investigation considers the two positioning techniques downlink time difference of arrival, DL-TDOA, and round trip time, RTT. Simulations of several deployments are performed in two standard scenarios which mimic an indoor open office and an indoor factory, respectively. Factors having an impact on the positioning accuracy and availability are found to be deployment geometry, number of base stations, line-of-sight conditions and interference, with the most important being deployment geometry. Two deployment strategies are designed with the goal of optimising the deployment geometry. In order to achieve both high positioning accuracy and availability in a simple, sparsely cluttered environment, the strategy is to deploy the base stations evenly around the edges of the deployment area. In a more problematic, densely cluttered environment the approach somewhat differs. The proposed strategy is now to identify and strategically place some base stations in the most cluttered areas but still place a majority of the base stations around the edges of the deployment area. A robust positioning algorithm is able to handle interference well and to decrease its impact on the positioning accuracy. The cost, in terms of frequency resources, of using more orthogonal signals may not be worth the small improvement in accuracy and availability.

Software development processes incorporate a variety of different artifacts (e.g., source code, models, and documentation). For multiple reasons the data that is contained in these artifacts does expose some degree of redundancy. Ensuring global consistency across artifacts during all stages in the development of software systems is required, because inconsistent artifacts can yield to failures. Ensuring consistency can be either achieved by reducing the amount of redundancy or by synchronizing the information that is shared across multiple artifacts. The discipline of software engineering that addresses these problems is called Round-Trip Engineering (RTE). In this thesis we present a conceptual framework for the design RTE systems. This framework delivers precise definitions for essential terms in the context of RTE and a process that can be used to address new RTE applications. The main idea of the framework is to partition models into parts that require synchronization - skeletons - and parts that do not - clothings. Once such a partitioning is obtained, the relations between the elements of the skeletons determine whether a deterministic RTE system can be built. If not, manual decisions may be required by developers. Based on this conceptual framework, two concrete approaches to RTE are presented. The first one - Backpropagation-based RTE - employs change translation, traceability and synchronization fitness functions to allow for synchronization of artifacts that are connected by non-injective transformations. The second approach - Role-based Tool Integration - provides means to avoid redundancy. To do so, a novel tool design method that relies on role modeling is presented. Tool integration is then performed by the creation of role bindings between role models. In addition to the two concrete approaches to RTE, which form the main contributions of the thesis, we investigate the creation of bridges between technical spaces. We consider these bridges as an essential prerequisite for performing logical synchronization between artifacts. Also, the feasibility of semantic web technologies is a subject of the thesis, because the specification of synchronization rules was identified as a blocking factor during our problem analysis. The thesis is complemented by an evaluation of all presented RTE approaches in different scenarios. Based on this evaluation, the strengths and weaknesses of the approaches are identified. Also, the practical feasibility of our approaches is confirmed w.r.t. the presented RTE applications.

Software deployment is all of the activities that make a software system available for use. An examaple of such activites can be installations, updating and removing of software. Each deployment platform can differ in quality attributes such as performance, maintainability, etc. Docker, a deployment platform using container technology offering a more modular way of deployment has become increasingly popular over the past few years. The aim of the project is to find out how a deployment with Docker would affect the performance of a client­server application from the mining industry. Three scenarios were performed in a simulated environment for the existing as well as the potential deployment platform. Measures of round­trip time were made for both sets of the scenarios. Results show a general decrease in performance when running the application on Docker. This is especially seen in early stages of each scenario, where Docker in average has 15 times higher round­trip times than the existing platform. However, results gathered from each scenario suggests that while Docker does start much slower than the existing platform, in later stages of each scenarios, Docker manages to narrow the gap and be at most 1.14 times higher than the existing platform. In conclusion, while the deployment in which the existing platform is deployed on does out perform Docker, it still shows some promise and could potentially be a worthy option to look at for further work.