Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-03-02T13:55:41Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação Final-Biblioteca_Brunno.pdf: 2392204 bytes, checksum: ade7199e37779e870f0c3d398da9bb4d (MD5) / Made available in DSpace on 2017-03-02T13:55:41Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação Final-Biblioteca_Brunno.pdf: 2392204 bytes, checksum: ade7199e37779e870f0c3d398da9bb4d (MD5) Previous issue date: 2016-02-25 / Neste trabalho, foram investigados e analisados conceitos fundamentais da metodologia de BPM (Business Process Modeling) através de sua notação BPMN (Business Process Modelling Notation), bem como o desenvolvimento de software por meio da UML (Unified Modeling Language), ambas atreladas à arquitetura SOA (Service-Oriented Architecture), com o objetivo de integrar as áreas de desenvolvimento de software e de gestão de empresas, a fim de possibilitar uma visão macro dos processos. Optou-se por analisar BPM, pois sua metodologia garante uma prática de desenvolvimento rápido do sistema, tornando-o flexível, e permite a sua reutilização, com uso de tecnologias legadas, pois empresas conseguem alcançar um maior controle dos processos de negócio. Já a UML possibilita a padronização na modelagem de software e, assim como BPM, com possível integração com SOA. O objetivo deste estudo é fazer a apresentação dos diversos cenários verificados a partir de um amplo levantamento da literatura que trata dessa integração. Dessa maneira, foi realizada uma comparação quantitativa e qualitativa dos cenários encontrados, a fim de definir qual é a melhor possibilidade de integração para uma empresa. Tudo isso para assegurar a interoperabilidade entre diferentes entidades, agregando valor e reduzindo custos de manutenção para as empresas. Através de descritores selecionados, foi feita uma busca em bases de dados específicas para levantar trabalhos publicados sobre a integração BPM-SOA e UML-SOA. Esse levantamento permitiu observar distintos cenários de integração, além das vantagens, desvantagens e problemas mencionados por seus autores. A finalidade é compreender quais os principais entraves relacionados à integração e implementação de BPM-SOA e UML-SOA que seja capaz de comprovar, quantitativa e qualitativamente, as integrações e apontar qual a melhor possibilidade. / In this study, we investigated and analyzed the fundamental concepts of BPM methodology (Business Process Modeling) through its BPMN notation (Business Process Modelling Notation) and software development through the UML (Unified Modeling Language), both linked to architecture SOA (Service-Oriented Architecture) with the aim of integrating the software development areas and business management, in order to provide a macro view of the processes. We chose to analyze BPM, because its methodology ensures a practice of rapid system development, making it flexible, and allows reuse, using legacy technologies, as companies can achieve greater control of business processes. Already the UML allows for standardization in software modeling and, as BPM, with possible integration with SOA. The aim of this study is to make the presentation of the various scenarios checked from a broad survey of the literature dealing with this integration. Thus, a quantitative and qualitative comparison of the scenarios found was carried out in order to define what is the best possibility of integration for a company. All this to ensure interoperability between different entities, adding value and reducing maintenance costs for companies. Through selected keywords, a search was made in specific databases for up papers on the integration BPM-SOA and UML-SOA. This survey allowed to observe different integration scenarios, beyond the advantages, disadvantages and problems mentioned by the authors. The purpose is to understand what the main obstacles related to the integration and implementation of BPM-SOA and SOA-UML to be able to prove quantitatively and qualitatively, the integrations and point out what the best possibility.

Enterprise Architectures (EA) are used to describe an enterprise’s structure in a standardized way. An Enterprise Architecture also provides decision-support when choosing a direction or making changes at different levels of an enterprise, such as the business architecture or technology architecture level. This can involve decisions such as: What kind of enterprise should this be, what kind of technologies should be used for new system developments etcetera. Therefore, using the Unified Modelling Language (UML) or Systems Modelling Language (SysML) together with standardized guidelines that help you decide what to do before, during, and after modelling could be important for producing correct and useful system models, which later on will be used to develop actual systems. At the moment, standardized guidelines of this kind do not really exist. However, there are a lot of information about why you should use UML or SysML, what kinds of UML or SysML diagrams that exist, or what notations to follow when creating a specific UML or SysML diagram. In this thesis, the objective has been to research about the usefulness and creation of standardized guidelines for UML or SysML modelling in an Enterprise Architecture (i.e. mainly intended for the automotive industry domain). For this reason, the two research questions: “how can you create useful standardized guidelines for UML or SysML modelling?” and “what do useful standardized guidelines for UML or SysML modelling look like?” were chosen. A case study was performed on a real-life project at the company Volvo Construction Equipment, which resulted in the two research questions being answered. Firstly, a three-step method (i.e. create guidelines – test guidelines – improve guidelines) was proven to create useful standardized guidelines. Secondly, useful standardized guidelines were created from this three-step method. Hopefully, these created standardized guidelines can be used by the targeted companies right away to make their modelling work more efficient, or serve as a foundation when creating their own standardized guidelines later on.

No description available.

Traditionally the dominant formalist school in mathematics has considered diagrams as merely heuristic tools. However, the last few years have seen a renewed interest in visualisation in mathematics and, in particular, in diagrammatic reasoning. This has resulteQ from the increasing capabilities of modern computers, the key role that design and modelling notations play in the development process of software systems, and the emergence of the first formal diagrammatic systems. Constraint diagrams are a diagrammatic notation for expressing constraints that can be used in conjunction with the Unified Modelling Language (UML) in object-oriented modelling. Recently, full formal semantics and sound and complete inference rules have been developed for Venn-Peirce diagrams and Euler circles. Spider diagrams emerged from work on constraint diagrams. They combine and extend Venn-Peirce diagrams and Euler circles to express constraints on sets and their relationships with other sets. The spider diagram system SDI developed in this thesis extends the second Venn-Peirce system that Shin investigated, Venn II, to give lower bounds for the cardinality of the sets represented by the diagrams. A sound and complete set of reasoning rules is given. The diagrammatic system SD2 extends SD 1 so that lower and upper bounds can be inferred for the cardinalities of the set represented by the diagrams. Soundness and completeness results are also given extending the proof strategies used in SD 1. The system SD2 is also shown to be syntactically rich enough to express the negation of any diagram. Finally, the ESD2 system incorporates syntactic elements from the spider diagram notation, so that information within a diagram can be expressed more compactly, and is proved equivalent to SD2. Two important innovations are introduced with respect to Venn I, Venn II, and Higraphs: two levels of syntax - abstract and concrete - and a proof of completeness that omits the use of maximal diagram used in these systems. This work will help to provide the necessary mathematical underpinning for the development of software tools to aid the reasoning process . and the development and formalisation of more expressive diagrammatic notations.

No description available.

L'accession a l'éducation d'un nombre toujours plus grand d'individus a conduit a considérer la performance des systèmes de formation comme un véritable facteur de développement économique. C'est dans ce contexte que s'inscrivent nos travaux de thèse qui ont visé au développement de méthodes et outils pour l'aide à la conception de la partie opérationnelle d'un système de formation et notamment tout le système de transformation permettant l'accroissements de compétences chez les apprenants. Après avoir présenté un bilan des systèmes de formation en définissant leur périmètre puis leur fonctionnement et résultats, nous précisons alors les facteurs qui nous ont conduits a nous préoccuper des processus opérationnels des systèmes de formation. Dans un deuxième chapitre, nous précisons la démarche que nous avons choisi d'adopter et déclinons ainsi l'ensemble de notre méthode, associée a des outils spécifiques, qui vise à l'aide a la conception et la mise en oeuvre des formations. Nous nous éloignons de la logique de l'offre pour migrer vers une logique de la demande. Nous proposons une identification contraintes subies par un système de formation (ressources à capacité finie, cohérence pédagogique, indisponibilité de ressources, compétences et aptitudes des ressources, etc.) - - Dans une troisième partie, nous illustrons notre propos en appliquant les méthodes et outils développes a un cas pratique. Enfin, nous concluons sur l'apport scientifique constitué par ces travaux et ouvrons la voie vers de nombreuses perspectives, le domaine de l'ingénierie de la formation étant encore à ses balbutiements / The accession with the education of a number increasingly larger indivlduals resulted in regarding the performance of the systems of formation as a true factor of economic development. It is in ths context that our work of thesis is registered which aimed to the development of methods and tools for the assistance with the design of the operational part of an education system and in particular al the transformation s y s t v leading to the increase of students competences. After having presented an assessment of the education systems by defining their perimeter, their operation and results, we specify the factors whch led us to worry us about operational processes of the education systems. In a second chapter, we specifi the steps whch we chose to adopt and we decline the whole of our method, associated to specific tools, which aims to the assistance to the design and the setting of formations. We move away from the logic of supply to migrate towards logic of demand. We propose an identification of constraints in education systems (resources with limited capaciîy, teachmg coherence, unavailability of resources, competences and aptitudes of the resources, etc.) In a third part, we illustrate our concept by applying methods and tools developed with a practical case. Lastly, we conclude on the scientific contribution made up by t h work and open the way towards rnany prospects, the field of the engineering of the formation being still to its beginnings

Active technology in database management systems (DBMS) enables the movement of behaviour dependent on the system’s state, from the application software to a rule base in the DBMS. With active technology in database systems, the problem of how to design active behaviour has become an important issue. Modelling processes do not foresee support for design of active rules which can lead to conflicts between the event-condition-action (ECA) rules representing the active behaviour and the application systems, using the active DBMS. The unified modelling language (UML) is a widely used notation language and is the main subject in this project. Its features will be investigated to acknowledge to what extend UML modelling diagrams provide information that can be used to formulate ECA rules. To achieve this, two methods where developed. One of the methods was applied on use-case UML modelling diagrams. The use-case models were developed by means of reflecting a real-life organisation. The results from applying the method on the use-case models were that there are features in UML that can be expressed with ECA rules. Active technology in database management systems (DBMS) enables the movement of behaviour dependent on the system’s state, from the application software to a rule base in the DBMS. With active technology in database systems, the problem of how to design active behaviour has become an important issue. Modelling processes do not foresee support for design of active rules which can lead to conflicts between the event-condition-action (ECA) rules representing the active behaviour and the application systems, using the active DBMS. The unified modelling language (UML) is a widely used notation language and is the main subject in this project. Its features will be investigated to acknowledge to what extend UML modelling diagrams provide information that can be used to formulate ECA rules. To achieve this, two methods where developed. One of the methods was applied on use-case UML modelling diagrams. The use-case models were developed by means of reflecting a real-life organisation. The results from applying the method on the use-case models were that there are features in UML that can be expressed with ECA rules.

In recent years, a number of laws and regulations (such as the Basel II accord or SOX) demand that organizations record certain activities or decisions to fulfill legally enforced reporting duties. Most of these regulations have a direct impact on the information systems that support an organization's business processes. Therefore, the definition of audit requirements at the modeling-level is an important prerequisite for the thorough implementation and enforcement of corresponding policies in a software system. In this paper, we present a UML extension for the specification of audit properties. The extension is generic and can be applied to a wide variety of UML elements. In a model-driven development (MDD) approach, our extension can be used to generate corresponding audit rules via model transformations. (author's abstract)

Software modeling with unified modeling language (UML) and model driven architecture (MDA) concept have become the new paradigm of modern systems analysis and design. Some Several CASE tools have been introduced to facilitate the transformation from platform independent model (i.e., class diagram, and sequence diagram) to platform specific model, and thereby enhance the efficiency of system development. This research depends on MDA concept, and presents a systematic methodology which integrated the UML and MDA concept with Patterns to refine PIM cohesively. A real-world case using the integrated techniques is presented. With this approach, the system developer can increase the reuse of PIM and thereby enhance the efficiency of system development.

<p>Active technology in database management systems (DBMS) enables the movement of behaviour dependent on the system’s state, from the application software to a rule base in the DBMS. With active technology in database systems, the problem of how to design active behaviour has become an important issue. Modelling processes do not foresee support for design of active rules which can lead to conflicts between the event-condition-action (ECA) rules representing the active behaviour and the application systems, using the active DBMS. The unified modelling language (UML) is a widely used notation language and is the main subject in this project. Its features will be investigated to acknowledge to what extend UML modelling diagrams provide information that can be used to formulate ECA rules.</p><p>To achieve this, two methods where developed. One of the methods was applied on use-case UML modelling diagrams. The use-case models were developed by means of reflecting a real-life organisation. The results from applying the method on the use-case models were that there are features in UML that can be expressed with ECA rules.</p><p>Active technology in database management systems (DBMS) enables the movement of behaviour dependent on the system’s state, from the application software to a rule base in the DBMS. With active technology in database systems, the problem of how to design active behaviour has become an important issue. Modelling processes do not foresee support for design of active rules which can lead to conflicts between the event-condition-action (ECA) rules representing the active behaviour and the application systems, using the active DBMS. The unified modelling language (UML) is a widely used notation language and is the main subject in this project. Its features will be investigated to acknowledge to what extend UML modelling diagrams provide information that can be used to formulate ECA rules.</p><p>To achieve this, two methods where developed. One of the methods was applied on use-case UML modelling diagrams. The use-case models were developed by means of reflecting a real-life organisation. The results from applying the method on the use-case models were that there are features in UML that can be expressed with ECA rules.</p>