En la actualidad, los entornos virtuales son una tecnología en constante evolución. Dicha evolución se relacionada en diferentes áreas de estudio, explayándose desde el área medica hasta el área de la arquitectura, siendo esta última, conformada por usualmente sistemas de simulación respecto a evacuaciones, flujos o mediciones de entornos.  No obstante, los sistemas existentes presentan cierto grado de complejidad en la interacción con el usuario, puesto que, la mayoría de estos cuenta con una interfaz de programación, en donde el usuario es el encargado de programar tanto los entornos, como el comportamiento del flujo de agentes simulados. Generando un nivel de complejidad en estos, pues desvía el conocimiento nato de los estudiantes de arquitectura, al nivel de aprender diferentes lenguajes de programación con el fin de poder simular sus entornos y el comportamiento de personas en estos.     Por otro lado, estos sistemas, a su vez, se centran en movimientos ya establecidos, en donde el usuario no aprecia o no tiene idea de cómo el recorrido realizado por el agente es el óptimo respecto otros existentes. Siendo este definido por el sistema y no por el usuario.   En consecuencia, como resultado de investigación, se propone un software de simulación, edición y análisis de afluencia de personas en edificaciones de alto tránsito para mejorar la calidad de aprendizaje de los estudiantes de arquitectura. Desarrollando el presente trabajo, en etapas. En donde, la primera etapa, consiste en definir el alcance del proyecto, necesidades y objetivos, así como oportunidades de negocio. En la segunda etapa, se listarán los framework necesarios, de la cuales se explicarán sus ventajas y desventajas correspondientes a las demandas de nuestra simulación. Y, en tercer lugar, tras haber seleccionado alguno, se procederá con la propuesta de investigación, así como su comparativo técnico con otras soluciones.  Finalmente, se tratará como problemática: “La necesidad de una herramienta de simulación de fácil uso, bajo costo, mantenimiento y libre de lenguajes de programación; respecto la afluencia de personas.” / Today the simulation of real environments is a process of constant evolution. This extends from research fields in medicine to architecture being in the latter a simulation system regarding evacuations flows or measurements of environments. However, the existing systems have given much to talk about in this context since most of them have a programming interface where the user oversees programming both the environments and the flow behavior of simulated agents. Generating a level of complexity in these as it diverts the natural knowledge of architecture students at the level of learning different programming languages ​​to be able to simulate their environments and the behavior of people in them. On the other hand, these systems in turn focus on already established movements where the user does not appreciate or has no idea of ​​how the route made by the agent is optimal compared to other existing ones. Being this defined by the system and not by the user. Consequently, because of research a software for the simulation editing and analysis of the influx of people in high-traffic buildings is proposed to improve the quality of learning of architecture students. Developing this work in stages. Where the first stage consists of defining the scope of the project needs and objectives as well as business opportunities. In the second stage the necessary frameworks will be listed of which their advantages and disadvantages corresponding to the demands of our simulation will be explained and thirdly after having selected one we will proceed with the research proposal as well as its technical comparison with other solutions. Finally, the following will be treated as problematic: “The need for a simulation tool that is easy to use low in cost, maintenance and free of programming languages regarding the influx of people. / Tesis

La plupart des applications robotiques, telles que les véhicules autonomes, sont développées à partir d’une page blanche avec quelques rares réutilisations de conceptions ou de codes issus d’anciens projets équivalents. Qui plus est, les systèmes robotiques deviennent de plus en plus critiques, dans la mesure où ils sont déployés dans des environnements peu structurés, et centrés sur l’humain. Ces systèmes à fort contenu logiciel qui utilisent des composants distribués et hétérogènes interagissent dans un environnement dynamique, et incertain. Or, il s’agit là d’étapes indispensables pour la mise en place de méthodes d’évaluation extensibles, ainsi que pour permettre la réutilisation de composants logiciels pré-existants. Le développement de structures logicielles et d’outils de conception d’architectures, orientés pour la robotique, coûte cher en termes de temps et d’effort, et l’absence d’une approche systématique pourrait conduire à la production de conceptions adhoc, peu flexibles et peu réutilisables. Faire de la meta-structure de l’architecture un point de convergence offre de nouvelles possibilités en termes d’interopérabilité, et de partage de la connaissance, au sein des communautés dédiées à la mise en place d’architectures et de structures. Nous suivons cette direction, en proposant un modèle commun, et en fournissant une approche méthodologique systématique aidant à spécifier les différents aspects du développement d’architectures logicielles, et leurs relations au sein d’une structure partagée. / Most innovative applications having robotic capabilities like self-driving cars are developed from scratch with little reuse of design or code artifacts from previous similar projects. As a result, work at times is duplicated adding time and economic costs. Absence of integrated tools is the real barrier that exists between early adopters of standardization efforts and early majority of research and industrial community. These software intensive systems are composed of distributed, heterogeneous software components interacting in a highly dynamic, uncertain environment. However, no significant systematic software development process is followed in robotics research. The process of developing robotic software frameworks and tools for designing robotic architectures is expensive both in terms of time and effort, and absence of systematic approach may result in ad hoc designs that are not flexible and reusable. Making architecture meta-framework a point of conformance opens new possibilities for interoperability and knowledge sharing in the architecture and framework communities. We tried to make a step in this direction by proposing a common model and by providing a systematic methodological approach that helps in specifying different aspects of software architecture development and their interplay in a framework.

Depuis l'introduction au début des années 2000 du standard ARINC 661 (définissant les interfaces graphiques dans les cockpits), les avions modernes, tels que l'A380, l'A350 ou le B787, intègrent des systèmes interactifs permettant à l'équipage d'interagir avec des applications interactives. Ces applications sont affichées sur des écrans à travers l'utilisation d'un dispositif similaire à un clavier et une souris. Pour des raisons d'exigences de sûreté de fonctionnement, l'utilisation de ces systèmes est limitée, à l'heure actuelle, à la commande et au contrôle de fonctions avioniques non critiques. Cependant, l'utilisation de ces systèmes dans les cockpits d'avions civils apporte de nombreux avantages (tels qu'une amélioration de l'évolutivité du cockpit) qui amènent les industriels à chercher comment l'étendre à la commande et le contrôle de systèmes avioniques critiques. Dans cette optique, nous proposons une approche duale et homogène de prévention et de tolérance aux fautes pour concevoir et développer des systèmes interactifs tolérants aux fautes. Celle-ci repose, dans un premier temps, sur une approche à base de modèles permettant de décrire de manière complète et non ambiguë les composants logiciels des systèmes interactifs et de prévenir les fautes logicielles de développement. Dans un second temps, elle repose sur une approche de tolérance aux fautes naturelles et certaines fautes logicielles résiduelles en opération, grâce à la mise en œuvre d'une solution architecturale fondée sur le principe des composants autotestables. Les contributions de la thèse sont illustrées sur une étude de cas de taille industrielle : une application interactive inspirée du système de commande et contrôle de l'autopilote de l'A380. / Since the introduction of the ARINC 661 standard (that defines graphical interfaces in the cockpits) in the early 2000, modern aircrafts such as the A380, the A350 or the B787 possess interactive systems. The crew interacts, through physical devices similar to keyboard and mouse, with interactive applications displayed on screens. For dependability reasons, only non-critical avionics systems are managed using such interactive systems. However, their use brings several advantages (such as a better upgradability), leading aircraft manufacturers to generalize the use of such interactive systems to the management of critical avionics functions. To reach this goal, we propose a dual and homogeneous fault prevention and fault tolerance approach. Firstly, we propose a model-based approach to describe in a complete and unambiguous way interactive software components to prevent as much as possible development software faults. Secondly, we propose a fault tolerant approach to deal with operational natural faults and some residual software faults. This is achieved through the implementation of a fault tolerant architecture based on the principle of self-checking components. Our approach is illustrated on a real size case study: an interactive application based on the command and control system of the A380 autopilot.

[pt] Microsserviços é uma técnica industrial para promover melhor escalabilidade e manutenibilidade de pequenos e autônomos serviços. Estudos prévios sugerem que a arquitetura de microsserviços vem sendo amplamente usada para reduzir limitações encontradas em sistemas monolíticos legados tais como melhoria de inovação, uso de diferentes tecnologias, entre outras. O processo de migração para a arquitetura de microsserviços não é trivial. Este é particularmente o caso da tarefa de identificar candidatos a microsserviço e o código fonte associado com cada candidato que é dispendiosa e propensa a erro. Consequentemente, abordagens automatizadas têm sido propostas para reduzir o esforço relacionado a essa atividade. Essas abordagens comumente adotam um ou dois critérios para suportar a identificação de microsserviços com base no sistema monolítico legado. Contudo, existe uma falta de compreensão da utilidade desses critérios adotados na prática. Além disso, há limitado conhecimento em quais são os critérios que profissionais consideram relevantes. Levando em consideração esses limitantes existentes, nós conduzimos um survey e entrevista para melhor compreender a utilidade de critérios relatados em estudos empíricos (e.g, estudos de caso e relatos) do ponto de vista dos profissionais. Os resultados do survey e da entrevista mostram que as abordagens automatizadas e ferramentas existentes não são totalmente alinhadas com necessidades práticas. Para atender às necessidades deles, este trabalho define uma abordagem automatizada chamada toMicroservices. A abordagem baseia-se em uma combinação de análise estática e dinâmica do código legado. A abordagem visa indicar os candidatos a microsserviço e a fonte correspondente extraído do sistema legado. toMicroservices faz uso da engenharia de software baseada em busca para otimizar e balancear os cinco critérios comumente adotados por profisionais, nomeados de modularização de funcionalidade, redução de sobrecarga de rede, reúso, acoplamento e coesão. Além disso, um estudo de caso e grupo focal foram conduzidos a posteriori para avaliar e melhorar toMicroservices. / [en] Microservices is an industrial technique to promote better scalability and maintainability of small and autonomous services. Previous studies suggested that microservice architectures have been widely used to reduce limitations found in legacy monolithic systems such as the inclusion of innovation, use of a different stack of technologies, among others. The process of migrating to a microservices architecture is far from trivial. This is particularly the case for the task of identifying candidate microservices and the source code associated with each candidate, which is recognizably time-consuming and error-prone. Thus, automated approaches have been proposed to reduce the effort related to that task. These approaches commonly adopt one or two criteria to support the identification of microservices from a legacy monolithic system. However, there is a lack of understanding on the usefulness of these criteria in practical settings. Moreover, there is limited knowledge on what are the criteria that practitioners consider relevant. Taking into account these existing limitations, we conducted a survey and interviews to better understand the usefulness of criteria reported in empirical studies (e.g, case studies and reports) from the point of view of practitioners. The results of the survey and interviews revealed that existing automated approaches and tools are far from being aligned with practical needs. To fulfill these needs, this work defines a automated approach named toMicroservices. The approach relies on a combination of static and dynamic analysis of the legacy code. The approach aims at indicating the microservice candidates and the corresponding source extracted from the legacy system. toMicroservices makes use of search-based software engineering (SBSE) to optimize and balance the five criteria commonly adopted by practitioners, namely feature modularization, network overhead reduction, reuse, coupling and cohesion. Additionally, an industrial case study and a focus group were conducted a posteriori to support the evaluation and improvements of toMicroservices.

Indiana University-Purdue University Indianapolis (IUPUI) / Domain-specific models powered using domain-specific modeling languages are traditionally created manually by modelers. There exist model intelligence techniques, such as constraint solvers and model guidance, which alleviate challenges associated with manually creating models, however parts of the modeling process are still manual. Moreover, state-of-the-art model intelligence techniques are---in essence---reactive (i.e., invoked by the modeler). This thesis therefore provides two contributions to model-driven engineering research using domain-specific modeling language (DSML). First, it discusses how DSML semantic and constraint can enable proactive modeling, which is a form of model intelligence that foresees model transformations, automatically executes these model transformations, and prompts the modeler for assistance when necessary. Secondly, this thesis shows how we integrated proactive modeling into the Generic Modeling environment (GME). Our experience using proactive modeling shows that it can reduce modeling effort by both automatically generating required model elements, and by guiding modelers to select what actions should be executed on the model.

[pt] O objetivo deste trabalho é avaliar um sistema de componentes de software que oferece em seu modelo uma abstração de componentes compostos. O sistema de componentes estudado é o SCS, que define um conjunto de regras de aninhamento, encapsulamento e compartilhamento para reger o comportamento de seus componentes compostos. O foco deste estudo está na avaliação da eficácia dessas regras de composição para auxiliar o desenvolvedor de aplicações. Para realizar esta avaliação, adaptamos o sistema de Captura e Acesso CAS, construído com o middleware SCS, para utilizar componentes compostos, e criamos um cenário para analisar o modelo e a implementação do middleware. / [en] The aim of this work is to evaluate a software component system that provides in its model an abstraction of composite components. We chose for this study SCS as the components system, which defines a set of rules for nesting, encapsulation and sharing to manage the behavior of its composite components. The main focus of this study is to evaluate the effectiveness of these composition rules to assist application developers. To conduct this evaluation, we adapted the Capture and Access system CAS, developed via the middleware SCS in order to employ the composite components, and created a scenario to analyze the model and implementation of the middleware.

In the world, research on autonomous navigation vehicles (AGV) is growing by the day. The goal with this project was to create an AGV and explore the possibility of using infrared reflections as a navigational method and how to achieve distinct reflection measurements from a surface. The thesis also discusses the possibility of using several units on a larger scale. In the progress of the project, a prototype vehicle was built to conduct the experiments to identify the suitability of infrared navigation. The testing of the prototype shows that navigation by IR can be very reliable under controlled circumstances. The project also explored how hierarchical software architecture stands in comparison to purely local or centralized software architecture. / I världen växer forskning på självgående fordon dagligen. Målet med detta projekt var att skapa ett självgående fordon och utforska möjligheterna att använda infraröda reflektioner som navigeringsmetod och hur man kan uppnå distinkta mätvärden. Avhandlingen diskuterar även möjligheterna att använda flera prototyper i en större skala. Under projektets gång byggdes ett prototypfordon för att genomföra experimenten angående lämpligheten med navigering via infrarött ljus. Tester med prototypen visar att navigering via infrarött ljus är väldigt pålitligt under kontrollerade omständigheter. Projektet utforskar även hur hierarkisk mjukvaruarkitektur står sig mot helt lokal eller centraliserad mjukvaruarkitektur.

Medical devices used for surgical or therapeutic purposes require a high degree of safety and effectiveness. Software is critical component of many such medical devices. The software architecture of a system defines organizational structure and the runtime characteristic of the application used to control the operation of the system and provides a set of frameworks that are used to develop that. As such, the design of software architecture is a critical element in achieving the intended functionality, performance, and safety requirements of a medical device. This architecture uses object-oriented design techniques, which model the underlying system as a set of objects that interact to achieve their goals. The architecture includes a number of frameworks comprised of a set of classes that can be extended to achieve different functionality required for a medical device. The Input/ Output (IO) framework includes a number of core classes that implement periodic and a periodic input output with varying priority requirements, provides a hardware neutral interface to the application logic, and a set of classes that can be extended to both meet the hardware IO specifics of a target platform and create new sensor and actuator types for client applications. The Devices framework provides a blueprint to develop the controller logic of the medical device in terms of abstractions that parallel the hardware components of the medical device. The Configuration framework allows creation and configuration of a medical device from an XML (Extensible Markup Specification) specification that specifies the configuration of the device based on abstract factories that can be extended to meet requirements of a specific medical device. The Controller is the component of the architecture that defines classes that implement reception of commands from and transmission of status and data to a local or remote client and dictate the structure of threads, thread priorities and policies for this purpose. The Diagnostics package of the architecture defines a framework for developing components that monitor the health of the system and detect emergency conditions. The architecture is implemented in C++ and runs on a real-time LINUX operating system. At this time, the architecture is used in development of two of the St. Jude Medical Atrial Fibrillation Division’s medical devices; one of these has FDA class III and the other class II classification.

Software architecture (SA) smells are design problems in the internal structure and behavior of an SA. These can be seen as a specific category under the umbrella concept of technical debt (TD). TD is a central concept in software development projects and having the means to detect and measure the smells is essential to understand impairments they may cause. However, TD is only limited to the technical aspects and does not describe smells found on an enterprise level. Enterprise architecture debt (EAD) expands the concepts of TD beyond the technical aspects such that it covers the debts that can be found in all layers of an Enterprise Architecture (EA). EA smells give a measurement for EAD by providing means for identifying and detecting the smell, hence enabling a method to quantify the level of debt. The goal of this thesis is to find EA smells derived from existing SA smells. In total, three new EA smells were presented based on existing SA smells. Each new smell was described by a short description that informally summarizes the smell. This was followed by an indication of the smell’s origin and reasoning about the effects on the quality. Then, an illustrative example of the smell was provided. Finally, a detection algorithm was also provided and implemented in a prototype detection program. This thesis serves as a basis for measurements of the quality of an EA and motivation for future research in this area. It is argued that the finding of EA smells can facilitate quality assessment in an EA. / Mjukvaruarkitektursrötor (MA-rötor) är designproblem i den interna strukturen och beteende i en mjukvaruarkitektur. Dessa kan ses som en specifik kategori under samlingsbegreppet teknisk skuld (TS). TS är ett centralt begrepp inom projekt i mjukvaruutveckling och att ha en metod att upptäcka och mäta dessa rötor är viktigt för att förstå försämringar dessa kan orsaka. TS är dock enbart avgränsat till de tekniska aspekterna och beskriver inte rötorna som kan finnas på en verksamhetsnivå. Verksamhetsarkitektursskulder (VAS) expanderar konceptet av TS utöver de tekniska aspekterna så att de även täcker skulderna som kan finnas på alla nivåer i en verksamhetsarkitektur (VA). VA-rötor ger ett mätvärde för VAS, genom att förse ett sätt att upptäcka rötorna och därmed möjliggöra ett sätt att kvantifiera graden av skuld. Målet i denna avhandling är att hitta VA-rötor som är härledda från befintliga MA-rötor. Totalt har tre nya VA-rötor presenterats baserat på befintliga MA-röter. Varje ny röta har beskrivits med en kort beskrivning som informellt summerar rötan. Detta följt av en indikation av rötans ursprung och resonemang om dess effekt på kvalitén. Ett illustrativt exempel har även presenterats. Slutligen, har en algoritm för att upptäcka rötan också presenterats och implementerats i ett prototypprogram för att upptäcka rötan. Denna avhandling används som en grund för mätvärden av kvalité i en VA och motivation för framtida studier i detta område. Det argumenteras för att identifieringen av VA-rötor kan förenkla kvalitetsbedömningen av en VA.

No description available.