Thesis (MTech (Information Technology))--Cape Peninsula University of Technology, 2011. / The adoption of Enterprise Architecture (EA) methodologies within organizations is causing an interest in the methodologies and supporting technologies available. Service Oriented Architecture (SOA) supports EA in many facets. However, there is much suspension with regard to the relationship between EA and SOA within organizations as well as the guidelines that organisations should follow in order for SOA to enable EA. There are potential problems that may arise if this relationship between SOA and EA is not agreed to at the outset of implementing an EA. The purpose of this research is to investigate the guidelines that are needed for SOA to enable EA, in order to provide practical steps that organisations can use to begin aligning SOA and EA, ensuring that these initiatives are driven from a business perspective. A qualitative approach using a case study was used as a methodology for this research. The data collection was conducted using semi-structured interviews, and the guidelines that were derived were validated through a survey that was distributed to industry architecture practitioners. The contribution of this research was a set of guidelines that can be used for SOA to enable EA. Further research areas were highlighted, including investigating the mapping of the guidelines that were derived from this research, into the EA frameworks that exist such as TOGAF and ZACHMAN.

Arquiteturas de software e teste de software desempenham um papel essencial no processo de desenvolvimento de produtos de software de alta qualidade. Com base em um mapeamento sistemático, pode-se observar que as atividades de estabelecimento de arquiteturas de software não consideram representar informações de teste de software associadas às visões da arquitetura, em particular de arquiteturas de referência. Este trabalho tem por objetivo propor um processo que induza a representação de informações de teste de software no estabelecimento de arquiteturas de referência. Dessa forma, além de se abstrair a essência de um conjunto de arquiteturas de software de um domínio de aplicação, facilitando o projeto de novas arquiteturas por meio do reúso e padronização de elementos arquiteturais, promove-se também o reúso e a padronização de informações de teste. Este trabalho é realizado a partir do modelo RAModel e do processo ProSA-RA. O RAModel apresenta um conjunto de elementos essenciais para o projeto de arquiteturas de referência. O ProSA-RA por sua vez apresenta um processo que sistematiza o estabelecimento de arquiteturas de referência, considerando os elementos do RAModel. Em particular, propõe-se um processo denominado ProSA-RAT . Esse processo viabiliza a definição de processos de teste adequados a domínios de aplicação específicos promovendo o reúso e padronização de informações de teste nas etapas iniciais de processos de desenvolvimento baseados em arquitetura. Um estudo de viabilidade do ProSA-RAT foi conduzido e um exemplo no domínio de robótica é apresentado. / Software architectures and software testing play an essential role in the development process of high quality software products. Based on a systematic mapping, it could be observed that the activities of establishing software architectures do not consider to represent software test information associated with the architecture views, in particular of reference architectures. The objective of this work is to propose a process that induces the representation of software test information in the establishment of reference architectures. Thus, in addition to abstracting the essence of a set of architectures of an application domain, facilitating the design of new architectures through the reuse and standardization of architectural elements, reuse and standardization of test information are also promoted. This work is carried out using the RAModel and the ProSA-RA. RAModel presents a set of essential elements for the design of reference architectures. ProSA-RA, on the other hand, presents a process that systematizes the establishment of reference architectures, considering the elements of the RAModel. In particular, a process named ProSA-RAT is proposed. This process facilitates the definition of test processes adequate to specific application domains by promoting the reuse and standardization of test information in the early stages of architecture based development processes. A feasibility study of ProSA-RAT has been carried out and an example in the field of robotics is presented.

Os sistemas de televisão digital terrestre têm se estabelecido e expandido em várias regiões do mundo. A expectativa é de que 1,4 bilhão de televisores analógicas sejam substituídas por televisores e receptores digitais, também conhecidos como terminais de acesso. Daí a importância destes dispositivos que recebem e decodificam o sinal digital. Diante da diversidade de plataformas de hardware de diferentes fabricantes e perfis de terminais de acesso, existe a necessidade de um alto investimento para criar e desenvolver aplicações e software intermediário (Middleware) na medida em que existe a necessidade de diferentes códigos-fontes para cada uma das plataformas. Além desta fragmentação de implementações por conta das várias plataformas de hardware, existe a demanda crescente por desempenho e por soluções com um conjunto maior de funções. Para endereçar a estas questões, existem organizações, iniciativas e tecnologias emergentes em sistemas embarcados multimídia, algumas delas baseadas em componentes de software, que estão consolidando técnicas que podem ser aplicadas à estrutura de software de um terminal de acesso, dentre as quais destacamos a UHAPI, o M3W, o OpenMAX, a IOS e o GStreamer. Esta dissertação apresenta uma proposta de arquitetura de software denominada Arquimedia com base em uma análise comparativa destes trabalhos. Foram realizados e analisados ensaios de desempenho parciais para a validação da proposta. / The terrestrial digital television systems have been established and expanded by the worldwide. It is expected that 1.4 billion analog TV sets will be replaced by set-topboxes and digital receivers TV sets, also known as access terminals. This fact shows the relevance of these devices that receive and decode the digital signals. Given the diversity of the hardware platforms of different manufacturers and different set-topboxes profiles, there is a need for a major investment to create and develop applications and Middleware because for each hardware platform, different source codes need to be developed. Beside the fragmentation of implementations resulted by the diversity of hardware platforms, there is an increasing demand for performance and solutions with more functions. To address these questions, there are organizations, initiatives and emerging technologies, some of them based on software components, that are consolidating techniques that can be applied to the software stack of a set-top-box, from among we emphasize the UHAPI, M3W, IOS and GStreamer. This master thesis deals a comparative analysis of these technologies and presents a set-top-box software architecture proposal called Arquimedia. Performance tests were made and analyzed to validate the proposal.

Orientador: Cecília Mary Fischer Rubira / Dissertação (mestrado) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-23T21:56:13Z (GMT). No. of bitstreams: 1 Gayard_LeonelAguilar_M.pdf: 1532057 bytes, checksum: 8324b0d9bd3eebedc13daca6f31c7c6b (MD5) Previous issue date: 2013 / Resumo: Nos últimos anos, o desenvolvimento baseado em componentes (DBC) e a arquitetura de software emergiram como disciplinas complementares para promover o reuso no desenvolvimento de software. O desenvolvimento baseado em componentes promove o desenvolvimento de componentes reutilizáveis e a formação de novos sistemas de software a partir da integração de componentes existentes. A arquitetura de um sistema de software descreve o sistema em termos de seus componentes arquiteturais, das propriedades destes e das conexões entre eles. Modelos de componentes possibilitam concretizar elementos de DBC como componentes e conectores a partir de conceitos tradicionais de desenvolvimento de software, como por exemplo, orientação a objetos e arquivos, de modo que um conjunto de classes e arquivos complementares podem formar um componente se seguirem as regras do modelo. A adequação a um modelo de componentes oferece benefícios para o sistema de software: por exemplo, o modelo de componentes EJB possibilita que um componente seja implantado em um contêiner e se beneficie do gerenciamento de segurança e transparência de localização oferecidos pelo contêiner; o modelo Cosmos estabelece regras para a criação de componentes baseados em conceitos de linguagens orientadas a objetos, como classes, interfaces e pacotes. Assim, a integração de componentes para a composição de um sistema de software de acordo com uma arquitetura e um modelo de componentes se torna uma atividade importante no desenvolvimento de um novo sistema de software. Uma configuração concreta é um conjunto de determinadas versões de componentes de software conectados de acordo com uma arquitetura. No entanto, observa-se que, se modelos facilitam a criação de componentes de software, ainda é necessário um esforço de desenvolvimento para integrar componentes e formar novos sistemas. O uso de ambientes de desenvolvimento orientados a arquitetura e DBC, e também de ferramentas de automatização, reduzem o esforço necessário para a integração de componentes. O ambiente Bellatrix é um ambiente de desenvolvimento integrado que permite a especificação de elementos arquiteturais e a modelagem de arquiteturas de software. No entanto, ainda existe um hiato entre a arquitetura de um sistema modelada no ambiente Bellatrix e a configuração do sistema a partir de componentes concretos. Esta dissertação apresenta a ferramenta CosmosLoader, que auxilia o gerenciamento de configurações de componentes baseados no modelo Cosmos. A solução proposta se baseia na extensão do ambiente Bellatrix e no modelo de componentes Cosmos* ("Cosmos estrela"), que estende o modelo Cosmos com o conceito de composição hierárquica de componentes. Por fim, são descritos estudos de caso realizados com essas ferramentas / Abstract: In the last years, Component-Based Development (CBD) and Software Architecture emerged as complementary disciplines that promote reuse in software development. Component-Based Development promotes the development of reusable software components and the creation of new software systems by integrating existing software components. The architecture of a software system describes such system in terms of its architectural components, their properties and the connections between them. Component models materialize concepts from CBD such as components and connectors from traditional concepts of software development, such as object orientation and files, so that a set of classes and complementary files form a component if they follow the component model's rules. The adequacy to a component model brings benefits to a software system: for instance, the EJB component model allows a component to be deployed to a container and benefit from the security management and location transparency provided by the container; the Cosmos component model allows the creation of components using only concepts from object-oriented languages, such as classes, interfaces and packages. Therefore, the integration of components to compose a new software system according to an architecture and a component model becomes an important activity in the development of a new software system. A concrete configuration is the set of specific versions of software components connected according to an architecture. However, it can be observed that while models ease the creation of software components, a development effort is still necessary to integrate components and form new systems. The use of development environments oriented towards architecture and CBD, and also of automations tools, reduce the effort needed to integrate components. The Bellatrix development environment is an integrated development environment that allows the specification of architectural elements and modeling of software architectures. However, there still is a gap between the architecture of a system modeled in Bellatrix and the configuration of a system from concrete software components. This dissertation presents the CosmosLoader tool, which assists in managing the configuration of components based on the Cosmos model. The proposed solution is based on an extension to the Bellatrix development environment and on the Cosmos* component model ("Cosmos star"), which extends the Cosmos component model with hierarchical composition of components. Finally, case studies using these tools are described / Mestrado / Ciência da Computação / Mestre em Ciência da Computação

[pt] O presente trabalho contém o projeto da arquitetura de hardware e software de um Processador de Comunicação (PC) que tem como finalidade a realização do protocolo X.25 para a ligação de um computador, em particular o sistema de multimicrocomputadores (MULTIPUC) da Pontifícia Universidade Católica do Rio de Janeiro, a uma rede de comunicação de dados comutada por pacotes. O Processador de Comunicação é baseado no microprocessador 8085 e no controlador de linha 8273 da Intel. A arquitetura de software do PC é composta de um conjunto de processos e monitores que implementam os procedimentos da recomendação X.25 do CCITT, aliviando assim o computador hospedeiro das tarefas de comunicação de dados. / [en] Communication processors are used to alleviate the main processor from data communications tasks. This work presens the design an implementation of a communications processor which serves as a front-end between a host computer and a packet switched network. The host computer is a local microprocessor network, MULTIPUC, under development at the Laboratório de Engenharia e Sistemas de Comunicação of the Pontifícia Universidade Católica do Rio de Janeiro. The Communication Processor implements the three levels of the X.25 CCITT recommendation. The software architecture, composed of several processes and monitors, is also described here.

Architectural design decisions are known to be crucial for the success of a system in development. An early design decision will most likely be expensive to change at a later stage of the development if the software engineers needs to get back to the drawing board. If a quality attribute has been neglected during architectural design it may ruin the entire project. This work describes a way of increasing the availability of a software service, that have already been put into use, by adding a middle layer of replication logics represented by third party application servers and replicated Enterprise JavaBeans. The approach called Three-tier replication is assessed and compared to the origin architectural design by using a qualitative scenario based assessment. In addition, we have also implemented the new architectural design to be able to validate the assessment results. The validation is done by testing the scenarios on the two architectures. The software service used is an industrial system for sending text messages from computers to mobile phones. / Tidiga designbeslut är extremt viktiga för utgången av ett utvecklingsprojekt. Felaktiga beslut kommer att kosta företaget eller organisationen mycket tid och pengar om det visar sig att de måste omarbetas. Detta arbetet beskriver ett sätt att öka åtkomsten på en tjänst genom att lägga till ett mellan-lager som sköter replikering av tjänstenoden. Relplikeringslogiken sköts av applikationsservrar och Enterprise Javabeans. Vi har använt ett befintligt industriellt system för att utveckla och jämföra metoden. Tjänsten ifråga är en SMS-tjänst för kommunikation mellan dator och mobil-telefon och vise versa.

Applying Rational Unified Process (RUP) in a project means to develop a set of models before the system could be implemented. The models depict the essentials of the system from requirements to detailed design. They facilitate getting a system that has appropriate and rich documentation (therefore highly maintainable) and addresses user needs. However, creation of the models may cause overheads since a lot of work has to be put to elaborate the artefacts. In this paper a method that makes RUP more efficient is proposed. The method makes use of the fact that every subsequent model is developed basing on the previous model. In other words, models are successively transformed from requirements up to executable code. In particular, design model bases on an analysis model. The proposed method applies automatic model transformation from an analysis model to a design model. Firstly, an approach for performing automatic transformation is chosen. Secondly, a tool applying this approach is implemented. Finally, the transformation tool is tested and evaluated in an empirical study. The results show that automation of model transformation may be beneficial, and therefore can help in getting better systems in shorten time.

The architecture of a software system is defined by significant decisions that drive the way in which the software is designed implemented and maintained. In the context of software product lines, these decisions will determine the design of an architec- ture that provides the software with the ability to be configured for different product variants and extended to accommodate future requirements. Although, variability models describe the different configurations of current and fu- ture products that the product line supports, the knowledge of how the architecture was designed to support variations of a product in space and time exists only in the architects’ mind or remains implicit in architectural models. This thesis argues that the knowledge found in architectural models and design rationale can be used to facilitate the derivation of product variants and the evolution of the product line. To support this notion, we propose the AKinSPL method for capturing the architec- tural knowledge in software product lines. The method is founded on the factors that architects take into consideration when designing the architecture, and a meta-model that represents the mental models and processes architects follow during the creation of a product line architecture. To validate the concepts of AKinSPL, its guidelines were mapped to activities of the PuLSE-DSSA methodology and new artifacts were created to capture architectural knowledge on the basis of those guidelines. Next, it was applied to capture the archi- tectural knowledge of an embedded software system for automatic control of agricul- tural equipment. The results showed that diagrams augmented with design rationale enable a faster understanding of the purpose of the architectural models. Similarly, the prescriptions of the architecture with respect to the implementation are conveyed more easily. / jmercadoh@gmail.com Tel: +4916099058545

Software architecture design as an engineering field has evolved greatly during the last 15 years, which is evident by the number of methods, styles, patterns, and guidelines available for its practitioners in industry. This paper takes a closer look at the purposes behind this field to reveal the level of discrepancy in pursued purposes between industrial practitioners and published methods for software architecture design. In our research surveys of architecture design methods and of purposes at a number of industrial practitioners resulted in two sets of purposes which were eventually compared and the level of discrepancy identified. / Mjukvarudesign är ett område inom mjukvaruindustrin som utvecklats omfattande under de senaste 15 åren, vilket synliggjorts av de nya metoder, designstilar, designmönster och paradigmer som gjorts tillgängliga för mjukvaruutvecklare idag. Den här uppsatsen gör en djupgranskning av syftena bakom detta arbetsområde för att upptäcka eventuella skillnader mellan de syften som framhålls av befintliga arkitekturmetoder och de syften som åtsträvas av utövare inom mjukvaruindustrin.

This thesis have two tasks: one is to help in the development of the ArchWiztool at ABB and the other is to find a way of how to formalise security related architecturalresponsibilities in a general way so that they can be incorporated in the tool. This thesis report focuses on thesoftware quality attribute security.The ArchWiz tool is developed at ABB Corporate Research in Västerås. The scopeof the tool is to serve as a software architecture guidance and knowledge tool for all softwarearchitecture professionals within ABB. The ArchWiz tool is a way of helping the architects of ABB to matchtheir product requirements with a list of general reusable requirements. The matched productrequirements can then use the reusable requirement's architectural solutions, which are also presentedin the tool. The tool focuses on usability, security and safety in this first version but it isconstructed so that the user can add their own general requirements regarding any quality.The architecture design phase in the development of a software system is a keypart in the development process, it gives the first design decisions and gives informationon if the system will have potential to meet its key requirements. Security is a software quality thathas grown in importance for the architectural design of the system. There exist a number of potentialthreats and attacks that might breach the security of the software and these threats needs to beprotected against. The ArchWiz project closed in December 2009 and at that time the tool was notfinished. A good foundation and a GUI framework for further implementations were developed but toget a fully functioning tool more implementations need to be made. Security is one of thequality attributes, which the ArchWiz is supposed to support. Suggestions on how to formalise securityresponsibilities in the tool have in this thesis been created and analysed. However, the suggestionsneed to be in incorporated in the tool and tested through users tests with the ABB architects.With the user tests as basis, the best suggestion can be selected. / Architectural Wizard project