No description available.

No description available.

Component-based software engineering has been championed because they can be used to shorten the development cycle of system and therefore lower the costs. This research presents a modeling method that integrates the principle of divide and conquer and the use case concept to help model component-based software effectively. A real-world case is modeled and a system is developed to illustrate the concepts, application, and the advantages of using proposed methodology.

A Engenharia de Software Baseada em Componentes (ESBC) envolve os processos de desenvolvimento de software a partir de partes embutidas prontas, a fim de se obter produtividade, reduzindo-se custos e tempo de lançamento no mercado, garantindo (e melhorando) a qualidade intrínseca de produtos de software, bem como flexibilidade de implementação, manutenção e integração de sistemas. O ciclo de vida de um componente de software, projetado para uma determinada arquitetura, para ser reutilizado e reciclado dentro de uma infra-estrutura de componentes, e para satisfazer atributos de qualidade, dependerá de um ambiente que permita que seu código evolua de maneira controlada; que suas interfaces sejam publicadas através de documentos; e que seus artefatos estejam sempre acessíveis por partes interessadas, como desenvolvedores, projetistas e arquitetos de software, gerentes de projeto, usuários etc. Isto sugere a organização de um processo que apóie a reutilização de componentes através de um repositório comum, justificando esforços de se projetar, implementar, testar e instalar estes componentes em diferentes soluções. Este trabalho tem a intenção de definir e descrever, através da linguagem e dos elementos de um meta-modelo, e através de uma proposta de implementação de um repositório de componentes, um modelo de processo alinhado a um subconjunto de requisitos estabelecidos pelos padrões ISO/IEC 12207 e ISO/IEC 9126, com o propósito de suporte de componentes a processos de desenvolvimento de software. / Component-Based Software Engineering (CBSE)involves the software development from prepared built-in parts processes, in order to achieve productivity, reducing costs and time-tomarket, assuring (and improving) the intrinsic quality of software products, as well as implementation, maintenance and systems integration flexibility. The life cycle of a software component designed for a given architecture to be reused and recycled, within a component infrastructure, and to satisfy quality attributes, will depend on an environment to allow its code to evolve in a controlled manner; its interfaces to be published through documents; and its artifacts to be always accessible from interested parties, like developers, software designers and architects, project managers, users etc. This suggests the organization of a process that supports the reuse of components through a common repository, justifying efforts to design, implement, test and install them in different solutions. This work intends to define and describe, through a meta-model language and elements, and through a component repository implementation proposal, a process model aligned to a subset of requirements established by the ISO/IEC 12207 and the ISO/IEC 9126 standards, with the purpose of development software processes support of components.

A Engenharia de Software Baseada em Componentes (ESBC) envolve os processos de desenvolvimento de software a partir de partes embutidas prontas, a fim de se obter produtividade, reduzindo-se custos e tempo de lançamento no mercado, garantindo (e melhorando) a qualidade intrínseca de produtos de software, bem como flexibilidade de implementação, manutenção e integração de sistemas. O ciclo de vida de um componente de software, projetado para uma determinada arquitetura, para ser reutilizado e reciclado dentro de uma infra-estrutura de componentes, e para satisfazer atributos de qualidade, dependerá de um ambiente que permita que seu código evolua de maneira controlada; que suas interfaces sejam publicadas através de documentos; e que seus artefatos estejam sempre acessíveis por partes interessadas, como desenvolvedores, projetistas e arquitetos de software, gerentes de projeto, usuários etc. Isto sugere a organização de um processo que apóie a reutilização de componentes através de um repositório comum, justificando esforços de se projetar, implementar, testar e instalar estes componentes em diferentes soluções. Este trabalho tem a intenção de definir e descrever, através da linguagem e dos elementos de um meta-modelo, e através de uma proposta de implementação de um repositório de componentes, um modelo de processo alinhado a um subconjunto de requisitos estabelecidos pelos padrões ISO/IEC 12207 e ISO/IEC 9126, com o propósito de suporte de componentes a processos de desenvolvimento de software. / Component-Based Software Engineering (CBSE)involves the software development from prepared built-in parts processes, in order to achieve productivity, reducing costs and time-tomarket, assuring (and improving) the intrinsic quality of software products, as well as implementation, maintenance and systems integration flexibility. The life cycle of a software component designed for a given architecture to be reused and recycled, within a component infrastructure, and to satisfy quality attributes, will depend on an environment to allow its code to evolve in a controlled manner; its interfaces to be published through documents; and its artifacts to be always accessible from interested parties, like developers, software designers and architects, project managers, users etc. This suggests the organization of a process that supports the reuse of components through a common repository, justifying efforts to design, implement, test and install them in different solutions. This work intends to define and describe, through a meta-model language and elements, and through a component repository implementation proposal, a process model aligned to a subset of requirements established by the ISO/IEC 12207 and the ISO/IEC 9126 standards, with the purpose of development software processes support of components.

Målet med det här arbetet är att presentera ett förslag på en komponentbaserad designsom skall användas för att lösa ett problem som finns hos företag som jobbar med flera affärssystemsAPI-komponenter. Lösningen som uppnås är ett komponentbaserat gränssnittsom låter sig anpassas, underhållas och utökas av användare. Vår lösning beskriver hur endesign ser ut som låter utvecklarna hos dessa företag arbeta mot ett komponentbaseratgränssnitt som programmatiskt ser identiskt ut oberoende mot vilket API-system utvecklarenarbetar mot eller med. Resultatet når vi genom att använda en blandad metodik,d.v.s. en metodik där både kvalitativa och kvantitativa metoder används. Anledningen tillvalet av en blandad metodik baseras på att det genererar mer underlag som vi sedan kananvända för att analysera och komma fram till ett välgrundat resultat.Vi presenterar den bakgrundsteori som läsaren behöver sätta sig in i för att lättarekunna tolka och förstå vårt resultat. Resultatet beskrivs och analyserar utifrån den teorisom vi tidigare har presenterats. Resultatet delas upp i tre kategorier: design, utvärderingav design och implementation. Dessa kategorier baseras på de metoder som vi har använtför att nå resultatet.Arbetet avslutas med en diskussion, metodutvärdering och sammanfattning som kortgår igenom hela arbetet med uppsatsen, vad resultatet kan betyda och hur valet av metodhar fungerat. Sist reflekterar vi kort över framtida forskning och hur det går att fortsättamed det här arbetet för att förstärka resultatet. / The aim of this thesis is to present a proposition of a component-based design whichwill be used to solve a problem for companies who works with several business systems’API-components. The solution that is achieved is a component-base inteface that can becustomized, maintained and expanded by the user. Our solution describes a design whichlet the developers at these companies to work against a component-based interface that,programatically, looks and works the same regardless of which business system API theywork against. We will use a mixed methodology, that is, we will use both qualitativeand quantitative methods to reach our result and conclusions. The choice to use a mixedmethodology is based on that it generates more groundwork for us to reach a better result.We will present the background theory for the reader to better understand and interpretour result. We will present our result in three ways: a design, an evaluation of the designand a implementation. Each based on one of the methods we used to reach it.The thesis will be concluded with a discussion, method evaluation and a summary,where we will discuss the work with the thesis and what the result tells us. There will alsobe a short summary of our choice of methods have worked for us. At last we will reflecton future work, and what might be the next step to take to strengthen and improve ourresult.

<p>This thesis presents new techniques for data management of run-time data objectsin component-based embedded real-time systems. These techniques enabledata to be modeled, analyzed and structured to achieve data managementduring development, maintenance and execution.The evolution of real-time embedded systems has resulted in an increasedsystem complexity beyond what was thought possible just a few years ago.Over the years, new techniques and tools have been developed to manage softwareand communication complexity. However, as this thesis show, currenttechniques and tools for data management are not sufficient. Today, developmentof real-time embedded systems focuses on the function aspects of thesystem, in most cases disregarding data management.The lack of proper design-time data management often results in ineffectivedocumentation routines and poor overall system knowledge. Contemporarytechniques to manage run-time data do not satisfy demands on flexibility,maintainability and extensibility. Based on an industrial case-study that identifiesa number of problems within current data management techniques, bothduring design-time and run-time, it is clear that data management needs to beincorporated as an integral part of the development of the entire system architecture.As a remedy to the identified problems, we propose a design-time data entityapproach, where the importance of data in the system is elevated to beincluded in the entire design phase with proper documentation, properties, dependenciesand analysis methods to increase the overall system knowledge.Furthermore, to efficiently manage data during run-time, we introduce databaseproxies to enable the fusion between two existing techniques; ComponentBased Software Engineering (CBSE) and Real-Time Database ManagementSystems (RTDBMS). A database proxy allows components to be decoupledfrom the underlying data management strategy without violating the componentencapsulation and communication interface.</p> / INCENSE

Le sujet de cette thèse est l'étude de la vérification et de la correction de spécifications B dans le contexte d'une approche CBSE ("Component-Based Software Engineering"). La méthode B est reconnue comme une méthode formelle bien outillée pour développer formellement des logiciels, elle dispose du raffinement et de prouveurs permettant un développement rigoureux. L'approche CBSE consiste à développer des logiciels par assemblage de composants, elle trouve son intérêt pour des systèmes de grandes tailles. Cette thèse comprend trois contributions principales. La première est la mise en évidence de schémas de constructions B basés sur le raffinement et l'inclusion de machines B ainsi que l'étude de ces schémas pour modéliser des relations entre des Systèmes de Transitions Etiquetés (STEs). La deuxième contribution consiste en l'utilisation de deux formalismes : (i) le formalisme UML pour spécifier l'assemblage de deux interfaces (fournie et requise) et de plusieurs composants ainsi que les communications entre composants, (ii) le formalisme B pour vérifier les assemblages. La troisième contribution étudie l'aide à la correction des spécifications B à partir de l'échec de la preuve en B. Cette étude est d'abord générale et indépendante du contexte, puis elle tient compte du contexte CBSE et s'intérresse à la détection et la correction des incompatibilités : pour l'assemblage de deux interfaces, on corrige les adaptateurs en considérant les trois niveaux syntaxique, sémantique et protocole, pour l'assemblage et la coordination de plusieurs composants, on corrige les médiateurs en considérant les niveaux syntaxique et protocole.

Using AOP to model non-modular concerns in CBSE ensures better modularity and reusability of components. In this thesis, we provide a model independent approach for modeling aspects in component models. In the approach we model aspects as wrappers on views of component systems. A view describes an adequate component system configuration where all the components of interest of an aspect are encapsulated in the same composite.For declarative definition of views, we provide a declarative language VIL. We illustrate how views are implemented in component models(e.g., Fractal). We provide a formal framework for aspect interferences analysis. In the framework component systems and aspects are modeled as automata and Uppaal model checker is used for the detection of aspect interferences. For interferences resolution, we provide a set of composition operators as templates to be instantiated for any two arbitrary aspects. Our approach is illustrated with an airport wireless access example.

Reuse is considered as one of the most crucial software engineering concerns. It allows for delivering software systems faster with less effort. Therefore, the thesis explores limits of reuse in the context of component systems. It analyzes in depth contemporary component systems, finds their commonalities and variation points, and introduces a meta-component system -- a software product line which allows for producing a tailored component system based on a set of requirements. The thesis addresses the meta-component system definition and focuses on its crucial aspects which play the key role in component systems preparation- (1) a configurable execution environment and (2) generation of implementation artifacts. To address the first aspect, the thesis proposes a model-driven method for creating configurable execution environments. Motivated by creating execution environments, the thesis contributes to (2) by introducing a notion of domain-specific languages interoperability in the context of the code generation. Furthermore, the thesis elaborates the proposed notion resulting into a family of interoperable domain-specific languages which is parametrized by a general purpose language.