There is currently much UK government and industry interest towards the integration of complex computer-based systems, including those in the military domain. These systems can include both mission critical and safety critical applications, and therefore require the dependable communication of data. Current modular military systems requiring such performance guarantees are mostly based on parameters and system states fixed during design time, thus allowing a predictable estimate of performance. These systems can exhibit a limited degree of reconfiguration, but this is typically within the constraints of a predefined set of configurations. The ability to reconfigure systems more dynamically, could lead to further increased flexibility and adaptability, resulting in the better use of existing assets. Current software architecture models that are capable of providing this flexibility, however, tend to lack support for dependable performance. This thesis explores the benefits for the dependability of future dynamic systems, built on a publish/subscribe model, from using Quality of Service (QoS) methods to map application level data communication requirements to available network resources. Through this, original contributions to knowledge are created, including; the proposal of a QoS framework that specifies a way of defining flexible levels of QoS characteristics and their use in the negotiation of network resources, a simulation based evaluation of the QoS framework and specifically the choice of negotiation algorithm used, and a test-bed based feasibility study. Simulation experimentation conducted comparing different methods of QoS negotiation gives a clear indication that the use of the proposed QoS framework and flexible negotiation algorithm can provide a benefit in terms of system utility, resource utilisation, and system stability. The choice of negotiation algorithm has a particularly strong impact on these system properties. The cost of these benefits comes in terms of the processing power and execution time required to reach a decision on the acceptance of a subscriber. It is suggested, given this cost, that when computational resources are limited, a simpler priority based negotiation algorithm should be used. Where system resources are more abundant, however, the flexible negotiation algorithm proposed within the QoS framework can offer further benefits. Through the implementation of the QoS framework within an existing military avionics software architecture based emulator on a test-bed, both the technical challenges that will need to be overcome and, more importantly, the potential viability for the inclusion of the QoS framework have been demonstrated.

Kiekvienos sistemos kūrimo tikslas yra veikianti, gyvybinga ir saugi sistema, teikianti norimus ir patikimus rezultatus. Sistemos saugumas – tai sistemos savybė, reiškianti, kad sistemos funkcionavimo metu neįvyks jokia nenumatyta situacija. Gyvybingumas – sistemos reakcija į tam tikrus įvykius ir sugebėjimas atlikti nustatytas užduotis bei pateikti teisingus sprendimus arba rezultatus. Norint sukurti tokią sistemą, kuri ateityje tenkins nustatytus reikalavimus, yra labai svarbu iš anksto nustatyti jos formalią reikalavimų specifikaciją, nes nuo to priklauso galutinis produktas – kiek įvairių situacijų, į kurias sistema gali patekti, ar bus numatyta, kaip ji susidoros su atitinkamais išoriniais ar vidiniais įvykiais. Tokią specifikaciją galima praplėsti įvairiomis modifikacijomis, kurios gali padėti aptikti potencialias klaidas sistemoje, kurias įvertinus kūrimo metu, galima sistemai suteikti tolerancijos klaidoms savybę. / In order to create a fault tolerant system, very clear requirements should be prepared and all possible fault events should be analyzed. It can be properly made by using any of system modeling formalism. In this work alternating bit protocol system was chosen to formalize and analyzed in fault tolerant software aspects. Alternating bit protocol was modified in two ways – it’s functionality under perfect circumstances and with added faults, in order to make the system fault tolerant. These both cases were formalized by PLA and DEVS formalization methods. After the research of different formalisms and adjusting FDEVS to alternating bit protocol, FPLA formalization method was created.

Embedded systems are used in many critical applications where a failure can have serious consequences. Therefore, achieving a high level of dependability is an ultimate goal. However, in order to achieve this goal we are in need of understanding the interrelationships between the different dependability quality attributes and other embedded systems’ quality attributes. This research study provides indicators of the relationship between the dependability quality attributes and other quality attributes for embedded systems by identifying the impact of architectural tactics as the candidate solutions to construct dependable embedded systems.

Security is a relatively new topic in the automotive industry. In the former days, the only security defense methods were the engine immobilizer and the anti-theft alarm system. The rising connection of vehicles to external networks made it necessary to extend the security effort by introducing security development processes. These processes include, amongothers, risk analysis and treatment steps. In parallel, the development of ISO/SAE 21434 and UN-ECE No. R155 started. The long development cycles in the automotive industry made it necessary to align the development processes' early designs with the standards' draft releases. This work aims to design a new consistent, complete and efficient security development process, aligned with the normative references. The resulting development process design aligns with the overall development methodology of the underlying, evaluated development process. Use cases serve as a basis for evaluating improvements and the method designs. This work concentrates on the left leg of the V-Model. Nevertheless, future work targets extensions for a holistic development approach for safety and security.:I. Foundation 1. Introduction 2. Automotive Development 3. Methodology II. Meta-Functional Aspects 4. Dependability as an Umbrella-Term 5. Security Taxonomy 6. Terms and Definitions III. Security Development Process Design 7. Security Relevance Evaluation 8. Function-oriented Security Risk Analysis 9. Security Risk Analysis on System Level 10. Risk Treatment IV. Use Cases and Evaluation 11. Evaluation Criteria 12. Use Case: Security Relevance Evaluation 13. Use Case: Function-oriented Security Risk Analysis 14. Use Case: System Security Risk Analysis 15. Use Case: Risk Treatment V. Closing 16. Discussion 17. Conclusion 18. Future Work Appendix A. Attacker Model Categories and Rating Appendix B. Basic Threat Classes for System SRA Appendix C. Categories of Defense Method Properties

A utilização da Internet como um meio de automação de serviços de e-business tem sido adotada como estratégia por empresas em vários ramos da economia, diminuindo custos e propiciando uma melhoria no relacionamento com o cliente. Um requisito não-funcional importante a ser considerado no desenvolvimento de sistemas de software que possibilita esta automação é a disponibilidade. O nível de disponibilidade de um sistema pode ser influenciado pela arquitetura do sistema, e, em particular, pela arquitetura de software, pois as decisões arquitetônicas devem considerar aspectos relacionados à disponibilidade. No método de avaliação de arquitetura ATAM (Architecture Tradeoff Analysis Method Método de Análise de Compromissos de Arquitetura), esse requisito é analisado através da utilização de cenários de disponibilidade. Como a avaliação da disponibilidade é normalmente uma tarefa complexa, requerendo dos analistas a identificação de numerosos itens interdependentes, a geração e, conseqüentemente, a análise de cenários de disponibilidade na maioria das vezes não é uma tarefa trivial. O presente trabalho tem como objetivo elaborar uma técnica de análise de disponibilidade em sistemas de software para a Web, que auxilie a geração sistemática de cenários de disponibilidade requeridos no método ATAM. Para a elaboração da proposta, o trabalho aborda métodos para a elicitação, representação e análise de requisitos não-funcionais em uma determinada arquitetura de software, bem como conceitos e taxonomias relacionadas à dependabilidade. Ao final, a técnica é exercitada em um exemplo simplificado de sistema de software bancário na Web. / The use of Internet for e-business service automation has been adopted as a strategy by organizations in several sectors of the economy, reducing costs and providing a better relationship with the customer. Availability is an important nonfunctional requirement to be considered in the development of software systems offering this type of automation. The level of system availability may be affected by the system architecture, and, especially, by the software architecture, as architectural decisions must take availability-related aspects into account. In the ATAM (Architecture Tradeoff Analysis Method) architecture evaluation method, this requirement is analyzed by means of availability scenarios. As availability evaluation is normally a complex task, requiring analysts to identify several interdependent items, the generation and, consequently, the analysis of availability scenarios is often not a trivial task. This work aims to elaborate an availability technique analysis for web-based software systems, to aid in the systematic generation of availability scenarios required in the ATAM method. To elaborate the proposal, the work covers methods for elicitation, representation and analysis of non-functional requirements in a specific software architecture, as well as concepts and taxonomies related to dependability. In the end, the technique is applied on a simplified example of web banking software system.

A utilização da Internet como um meio de automação de serviços de e-business tem sido adotada como estratégia por empresas em vários ramos da economia, diminuindo custos e propiciando uma melhoria no relacionamento com o cliente. Um requisito não-funcional importante a ser considerado no desenvolvimento de sistemas de software que possibilita esta automação é a disponibilidade. O nível de disponibilidade de um sistema pode ser influenciado pela arquitetura do sistema, e, em particular, pela arquitetura de software, pois as decisões arquitetônicas devem considerar aspectos relacionados à disponibilidade. No método de avaliação de arquitetura ATAM (Architecture Tradeoff Analysis Method Método de Análise de Compromissos de Arquitetura), esse requisito é analisado através da utilização de cenários de disponibilidade. Como a avaliação da disponibilidade é normalmente uma tarefa complexa, requerendo dos analistas a identificação de numerosos itens interdependentes, a geração e, conseqüentemente, a análise de cenários de disponibilidade na maioria das vezes não é uma tarefa trivial. O presente trabalho tem como objetivo elaborar uma técnica de análise de disponibilidade em sistemas de software para a Web, que auxilie a geração sistemática de cenários de disponibilidade requeridos no método ATAM. Para a elaboração da proposta, o trabalho aborda métodos para a elicitação, representação e análise de requisitos não-funcionais em uma determinada arquitetura de software, bem como conceitos e taxonomias relacionadas à dependabilidade. Ao final, a técnica é exercitada em um exemplo simplificado de sistema de software bancário na Web. / The use of Internet for e-business service automation has been adopted as a strategy by organizations in several sectors of the economy, reducing costs and providing a better relationship with the customer. Availability is an important nonfunctional requirement to be considered in the development of software systems offering this type of automation. The level of system availability may be affected by the system architecture, and, especially, by the software architecture, as architectural decisions must take availability-related aspects into account. In the ATAM (Architecture Tradeoff Analysis Method) architecture evaluation method, this requirement is analyzed by means of availability scenarios. As availability evaluation is normally a complex task, requiring analysts to identify several interdependent items, the generation and, consequently, the analysis of availability scenarios is often not a trivial task. This work aims to elaborate an availability technique analysis for web-based software systems, to aid in the systematic generation of availability scenarios required in the ATAM method. To elaborate the proposal, the work covers methods for elicitation, representation and analysis of non-functional requirements in a specific software architecture, as well as concepts and taxonomies related to dependability. In the end, the technique is applied on a simplified example of web banking software system.