Les décisions architecturales ont émergé comme un moyen important pour maintenir la qualité de l’architecture pendant sa évolution. L’une des décisions les plus importantes faite par architecte sont celles à propos des approches de conception, à savoir des patrons ou des styles architecturales. La structure de ce genre de décision donne la possibilité d’être contrôlée automatiquement. Dans la littérature, il existe quelques travaux sur la vérification automatique de la violation des décisions architecturales. Dans cette thèse, nous montrons que ces travaux ne permettent pas de détecter toutes les violations possibles. Pour les compléter, nous proposons une approche qui i) décrit les patrons architecturaux qui contiennent la définition de la décision architecturale, ii) intègre les décisions architecturales au modèle architectural et iii) automatise la vérification de la conformité de la décision architecturale. Notre approche est implémentée en utilisant EMF et ses technologies accompagnées. Nous avons montré la possibilité de formaliser tous les patrons structuraux. A travers de deux expérimentes, nous avons montré que les décisions architecturales sont bien expliquées et toutes les violations sont détectées. Les systèmes logiciels composables sont prouvés capable de supporter l’adaptation aux nouvelles exigences grâce à leur flexibilité. Une méthode typique pour composer ces systèmes est de sélectionner et combiner des patrons qui adressent aux exigences de qualité attendues. Plusieurs propositions ont montré l’intérêt de la composition de patron. En revanche, l’un des défauts de ces propositions est la vaporisation de l’information de composition qui conduit au problème de la traçabilité et la reconstructibilité des patrons. Cette thèse a pour but de réserver le statut première classe aux opérateurs de composition pour stocker l’information de composition. L’approche est implémentée dans un outil et une étude empirique a été aussi conduite pour souligner ses intérêts. / Architectural decisions have emerged as a means to maintain the quality of the architecture during its evolution. One of the most important decisions made by architects are those about the design approach such as the use of patterns or styles in the architecture. The structural nature of this type of decisions give them the potential to be controlled systematically. In the literature, there are some works on the automation of architectural decision violation checking. In this thesis we show that these works do not allow to detect all possible architectural decision violations.To solve this problem we propose an approach which: i) describes architectural patterns that hold the architectural decision definition, ii) integrates architectural decisions into an architectural model and, iii) automates the architectural decision conformance checking. The approach is implemented using Eclipse Modeling Framework and its accompanying technologies. Starting from well-known architectural patterns, we show that we can formalize all those related to the structural aspect. Through two experiments, we show that architectural decisions are well explained and all of their violations are detected. Composable software systems have been proved to support the adaptation to new requirements thanks to their flexibility. A typical method of composable software development is to select and combine a number of patterns that address the expected quality requirements. A lot of work have shown the interest of pattern composition. Nevertheless, one of the shortcomings of these work is the vaporization of composition information which leads to the problem of traceability and reconstructability of patterns. This thesis also proposes to give first- class status to pattern merging operators to facilitate the preservation of composition information. The approach is tool-supported and an empirical study has also been conducted to highlight its interests

In our current environment, where we increasingly become dependent on the internet, the definition of living smart is widely used. Smart living involves original and innovative solutions to make life more efficient, controllable, economical, productive, integrated and sustainable. The Internet of Things (IoT) helps people with the lifestyle of smart living and helps them gain complete control. IoT does not only offer smart devices for the home, such as Google Home or Alexa. It is also essential for small and big businesses. The ability to transfer data over a network without any human interaction is needed in today's society. Organisations in multiple industries are using IoT to improve decision-making and overall quality of life for their employees. One way of using the IoT infrastructures is a concept called digital twin or a Digital Twin of an Organization (DTO). Since an organisation is constantly evolving, keeping the DTO aligned with the organisation will require an infrastructure that lends itself to be highly flexible and maintainable. The EA Blueprint Pattern was proposed to help achieve a flexible and maintainableDTO. However, there are limited practical instantiations of this pattern that can evaluate its utility. This project will therefore perform a practical evaluation and analysis of the pattern.

Recently, cloud computing has been gaining more and more popularity. Misunderstanding, misusing and underutilizing the cloud offerings, though, both from business and technical perspective still poses a threat to the success of cloud projects. On the technical side, one of the main reasons for success or failure is often the architectural design of the system – if a system is not architected the “cloud way”, using cloud’s special characteristics, the business benefits of such a system are often questionable at best. Software architecture through architectural patterns – reusable generic solutions to classes of problems – has for long been a good way to overcome the challenges of software architecture. This paper focuses on establishing the grounds and highlighting the differences of the knowledge transfer regarding architectural patterns from building pre-cloud (“traditional”) software systems to building cloud-native systems. The following 3 research questions drive this research: RQ1.     How does the existing knowledge on architectural patterns relate to the cloud computing environment? RQ2.     Which characteristics of architectural patterns make them suitable for the cloud environment? RQ3.     How can architectural pattern evolution be documented effectively for usage in the practice? In order to answer these 3 research questions and considering their focus is on utility i.e. creating a model which can be directly used in practice, the research uses design science research methodology (Peffers, et al., 2007-8). The emphasis in this methodology is iteratively building artefact(s) which can be improved and proven through practice that they actually help solving the problem at hand. This research contributes with building 4 inter-connected artefacts: a cloud applicability taxonomy of architectural patterns (CATAP) showing how applicable to a cloud environment an architectural pattern is and why; a pattern-to-characteristics mapping showing how using an architectural pattern affects the resulting system in traditional and cloud environments; a pattern form documenting the architectural patterns and the findings about them in the previous two artefacts; a wiki site, APE Wiki, which makes the results available to the public for reference and discussion and improvement. This research has a few interesting findings. First of all, the current architectural pattern knowledge seems to be very mature as no pattern has been found to have significantly evolved because of cloud – the architectural patterns are really generic and very flexible and only their effect on system characteristics has changed with the environment switch. On the other hand, a few new patterns were discovered and documented, which confirms the need for special attention to the new environment. Apart from that, the pattern-to-characteristics mapping provides interesting insights into which characteristics are most important for cloud and where there is a gap which may need to be filled. This paper presents both the process and the results of the research as equally important as replicating and extending this research could help in maturing the results and the knowledge about architecting systems for cloud thus increasing the chances of success of cloud projects.

In the world of software development, there is an increasing demand for software to keep up with rapid changes in its real-world context. A Resilient Digital Twin of an Organization is a type of software whose purpose is to digitally represent an organization or a component of an organization - as a Digital Twin -, and to keep doing so accurately throughout the real-world organization’s changes - a Resilient Digital Twin. An architectural pattern, called the EA Blueprint Pattern, has recently been proposed as a pattern to use for developing Resilient Digital Twins that can change together with the changes in the organization. However, software architecture is not the only factor that enables continuous change and adaptability in software. For software development teams to be able to deliver software rapidly and reliably, the software development process itself must be adapted to allow for frequent and fast changes. From this need, the Agile methodology and subsequently the set of work practises called DevOps has emerged. DevOps leverages automation and fast feedback as tools to facilitate a shorter system development life cycle and continuous delivery. The usage of DevOps is becoming increasingly popular in the software development field. It stands to reason that there is a need to ensure that the EA Blueprint Pattern is appropriate even in a DevOps context, where different tools and routines may be used than in traditional development. To complete this project, a use case of the EA Blueprint Pattern has been moved from a traditionally developed and deployed setting to a DevOps setting that includes essential DevOps tools such as Infrastructure as Code, a cloud environment, and a CI/CD pipeline that enables automatic deployment and therefore a shorter system development life cycle. By doing this, it can be gauged how well the EA Blueprint Pattern is adapted to a modern software development process which utilises the advantages of DevOps.

[pt] A tecnologia de software está passando por uma transição de arquiteturas monolíticas e coesas para arquiteturas compostas por agentes e sistemas multiagentes semi-autônomos e heterogêneos. Estas arquiteturas são marcadas pela existência de propriedades adicionais no nível do sistema, como comunicação, coordenação, mobilidade, adaptabilidade e persistência. No entanto, o gerenciamento e controle destas propriedades e dos diferentes agentes de software não é uma tarefa simples e exige uma abordagem mais sofisticada desde a fase arquitetural deste tipo de sistema. Neste contexto, neste trabalho, propomos a definição de um padrão arquitetural, denominado Reflective Blackboard. Este padrão é o resultado da composição de dois outros padrões arquiteturais bem conhecidos: o padrão Blackboard e o padrão Reflection. Através da utilização do padrão, uma melhor separação de responsabilidades é atingida pelo tratamento separado, por meio de técnicas de reflexão computacional, das diferentes estratégias de controle incorporadas no sistema. De forma complementar à definição do padrão foi desenvolvida uma infra-estrutura para o desenvolvimento de sistemas multi-agentes que utilizam a arquitetura proposta pelo padrão apresentado. Esta infra- estrutura, além de funcionar como uma implementação do padrão Reflective Blackboard, provê suporte a diferentes propriedades do nível do sistema como mobilidade, comunicação, coordenação e persistência. A utilização do padrão e da infraestrutura desenvolvida foi aplicada em uma aplicação de Marketplace com o objetivo de validar os conceitos propostos. / [en] Software technology is undergoing a transition from monolithic architectures, constructed according to a single overall design, into open architectures composed of conglomerates of collaborative, heterogeneous, and independently designed agents and multi-agent systems (MAS). These architectures are driven by additional system- wide properties, such as communication, coordination, adaptability, mobility and persistence. However, controlling these properties and managing different application agents is not an easy task, requiring a more sophisticated software architectural approach. In this context, we propose the Reflective Blackboard architectural pattern, which is the result of the composition of tho other well-known architectural patterns: the Blackboard pattern and the Reflection pattern. The pattern allows a better separation of concerns, supporting the separate handling of control strategies, by means of the computational reflection technique. An infrastructure, which implements the proposed pattern and provides support to multiple system-level properties, such as mobility, communication, coordination and persistence, was also developed. The Reflective Blackboard pattern was applied together with this infrastructure to the development of a Marketplace application in order to validate de concepts proposed in this work.

The goal of this master's thesis is creating a concept of architecture for new information system of the Academic Center for Students Activities. New information system of the Academic Center should be well documented and better maintainable. The first part deals with software maintenance and software architecture design. The second part contains analysis of current information system of Academic Center for Students Activities and also the architecture of new system is designed. The next parts are design of framework for the new system and also design of particular modules. Then there are implementation of designed parts and testing on real data.

This master's thesis deals with analysis, design and implementation of an information system that allows easy extensibility with three-tier architecture.   System is developed using object oriented approach by programming language PHP, relational database server MySQL and web services and protocol SOAP. The View tier is implemented by web technologies XHTML and CSS. Analysis and design of this system is done with using the modeling language UML.     In this thesis is described the problem of multi-tier software architecture, theory of development information's systems and described design and implementation of an information system with a three-tier architecture and it's application in the society SDC.