DOCSLIB.ORG

Database Engineering Process Modelling

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Database Engineering Process Modelling FUNDP Institut d’Informatique rue Grandgagnage 21 B-5000 Namur Belgium Tél. +32 81 72 49 64 Fax. +32 81 72 49 67 http://www.fundp.ac.be Database engineering process modelling Didier Roland Supervisor Prof. Jean-Luc Hainaut Jury Jean Fichefet (president, FUNDP, Namur, Belgium) Jean-Luc Hainaut (FUNDP, Namur, Belgium) Colette Rolland (Sorbonne, Paris I, France) Éric Dubois (CRP Henri Tudor, Luxembourg) Naji Habra (FUNDP, Namur, Belgium) Academic year 2002-2003 A thesis submitted for the degree of PhD in sciences, computer science option iii Abstract An important research subject in Software engineering is concerned with modelling the develop- ment process of huge software in order to bring some help to engineers when designing and main- taining an application. In general, every design process is seen a rational application of transforma- tion operators to one or more products (mainly specifications) in order to produce new products that satisfy some given criteria: O=f(I). I and O being sets of products compliant with formalisable models, f is a transformation composition whose specifications are the properties of I and O. This modelling is a sound basis for a methodological guidance. Indeed, at each step of the process, the set of pertinent activities and types of products are proposed to the designer, without any other. This guidance can be reinforced with some help. Furthermore, this modelling allows to document the process with its history, i.e. with a representation of performed activities. This history is itself the basis of maintenance activities. The thesis holds in four phases: • elaboration of a general model of design processes, a method specification language (MDL), and a history representation • basic methodological recommendation proposals for the elaboration of engineering methods according to the defined model • development and integration of some methodological control functions in the DB-MAIN CASE tool, including an extension of the repository, the definition of the interface of the meth- odological functions, the development of the methodological engine and the development of history processors (recording, replay, analysis,...) • evaluation of this model with case studies using classical methods. Résumé Un sujet de recherche important dans le monde de l’ingénierie logicielle concerne la modélisation des processus de développement de grosses applications afin d’apporter de l’aide aux ingénieurs pour concevoir et maintenir leurs applications. En général, chaque processus de conception est vu comme l’application rationnelle d’opérateurs de transformation à un ou plusieurs produits (généra- lement des spécifications) pour obtenir de nouveaux produits qui satisfont un ensemble défini de critères: S=f(E). E et S étant des ensembles de produits conformes à des modèles formalisables, f est une composition de transformations dont les spécifications sont les propriétés de E et S. Cette modélisation permet, principalement, un suivi méthodologique. En effet, à chaque étape du proces- sus, seul l’ensemble des outils pertinents est mis à la disposition du concepteur. Ce guidage peut éventuellement être renforcé par des messages d’aide. De plus, cette modélisation permet de docu- menter le processus avec son historique, c’est-à-dire avec une représentation des actions entreprises. Cet historique peut lui-même être à la base d’activités de maintenance. La thèse tient en quatre parties : • élaboration d’un modèle général pour la définition de processus d’ingénierie, d’un langage de spécification de méthodes (MDL) et d’une représentation des historiques; • propositions de recommandations méthodologiques pour l’élaboration de méthodes d’ingénierie selon le modèle défini; • développement et intégration de fonctions de contrôle méthodologique dans l’atelier DB- MAIN; ceci inclut l’extension du référentiel, la définition de l’interface homme-machine pour les fonctions méthodologiques, le développement du moteur méthodologique et le développe- ment de processeurs d’historiques (enregistrer, rejouer, analyser,...); • évaluation de ce modèle avec des études de cas utilisant des méthodes classiques. iv v Acknowledgement This thesis is the result of a long work. A long time during which I met many people who helped me and who showed some interest. All these people deserve to be thanked. First of all I want to Thank Jean-Luc Hainaut, with who I did all the job. I want to thank him for the opportunity he gave to me, for his support and for his availability in the frame- work of this thesis, but also for his great job in founding and leading the LIBD research team. I want to thank all this team too, including its present and former members, for their support and collaboration. In particular, many thanks to Jean Henrard, Jean-Marc Hick and Vincent Englebert for the great job we did in the DB-MAIN project, and to Virginie Detienne with who I also worked on another interesting project. Many thanks to all the other people from the Insistut d'Informatique and from many other research labs for all the interesting discussion I had with them all. I will not list them all because I should fill several pages with all their names, but they can really be sure I do not forget them. Many thanks to the readers of this thesis and to the members of the jury for their interest in it. I also want to thank all the friends and family members who supported me along the years. Special thanks to Raoudha who particularly supported me along the whole work while pre- paring her own PhD and to Xia who particularly supported me in the last months. Many thanks to Renaud, Lysia, Sivilay, Olfa and many other friends who also supported me a lot. But this thesis could not have been written if I had not received a very good education before. For this education, and for supporting me all the time from my birth, many, many, many thanks to my parents. Many thanks too to all my other family members (in the broader sense) and to all the people who participated to this education, including all the teachers at kindergarten, primary school, secondary school, and all the years at university before PhD. vi vii Contents Glossary 14 Chapter 1 Introduction 1 1.1. Process modelling presentation 2 1.2. State of the art and related works 3 1.2.1. History of data and process engineering 3 1.2.2. Process modelling in the large 4 1.2.3. CASE tools and meta-CASE tools 7 1.2.4. History recording 7 1.3. Database specifics 8 1.4. Goals 9 1.5. Structure of the thesis 10 1.6. DB-MAIN 11 Part 1 Models and Methods 13 Chapter 2 Basics 15 2.1. Basic definitions 16 2.2. Architecture 19 Chapter 3 Product models 23 3.1. Basic considerations 24 3.2. The GER model 25 3.2.1. Schema 25 3.2.2. Entity types 26 3.2.3. Relationship types (rel-types) 26 3.2.4. Attributes 26 3.2.5. Roles 27 3.2.6. Constraints 28 3.2.7. Is-a relations 31 3.2.8. Processing units 32 3.2.9. Collections 32 3.2.10. Dynamic properties 32 3.3. Schema model 33 3.4. Text model 45 viii 3.5. Product model hierarchies 47 Chapter 4 Product types and process types 49 4.1. Defining product types 50 4.2. Modelling engineering process types 51 4.2.1. Engineering process type decomposition 51 4.2.2. Engineering process type interface 52 4.2.3. Engineering process type strategy 55 4.3. Comparison with other modelling techniques 70 Chapter 5 The MDL language 73 5.1. Requirements 74 5.2. Language definition 74 5.2.1. Generalities 74 5.2.2. Method 75 5.2.3. Product Models 76 5.2.4. Global product types 79 5.2.5. Toolboxes 80 5.2.6. External function declarations 81 5.2.7. Process types 82 5.3. Language analysis 96 5.3.1. The syntax is unambiguous 97 5.3.2. Syntactical analysis 98 5.3.3. The semantics is unambiguous 99 5.3.4. Compliance with the requirements 99 Part 2 Histories 101 Chapter 6 Histories 103 6.1. Usefulness of histories 104 6.1.1. Documentation 104 6.1.2. Undo 104 6.1.3. Database design recovery 104 6.1.4. Database evolution 105 6.1.5. History analysis 105 6.1.6. Method induction 105 6.2. Expectations for histories 106 6.3. Structure of histories 106 6.3.1. Products 106 6.3.2. Processes 107 6.3.3. Primitive processes 107 6.3.4. Engineering processes 112 6.3.5. Decisions 113 6.3.6. The history of a project 114 ix 6.4. History representation 116 6.4.1. Representation of the tree structure 116 6.4.2. Representation of primitive process histories 116 6.4.3. Representation of engineering process graphs 117 6.5. History construction 120 6.5.1. Primitive processes 120 6.5.2. Engineering processes 120 6.5.3. Hypotheses, versions and decisions 121 Chapter 7 History processing 125 7.1. Basic hypotheses 126 7.2. History replay 126 7.2.1. Replaying primitive processes of automatic basic type 126 7.2.2. Replaying primitive processes of automatic configurable type 126 7.2.3. Replaying primitive processes of automatic user configurable type 126 7.2.4. Replaying primitive processes of manual type 126 7.2.5. Replaying every primitive processes 128 7.2.6. Replaying engineering processes 129 7.3. History evolution 129 7.4. History transformation 132 7.4.1. History characteristics 132 7.4.2. Excerpts 135 7.4.3. Independent history excerpts 136 7.4.4. Equivalent history excerpts 137 7.4.5. Minimal history excerpts 137 7.4.6.
Load more

Recommended publications
  • Rugby - a Process Model for Continuous Software Engineering
    INSTITUT FUR¨ INFORMATIK DER TECHNISCHEN UNIVERSITAT¨ MUNCHEN¨ Forschungs- und Lehreinheit I Angewandte Softwaretechnik Rugby - A Process Model for Continuous Software Engineering Stephan Tobias Krusche Vollstandiger¨ Abdruck der von der Fakultat¨ fur¨ Informatik der Technischen Universitat¨ Munchen¨ zur Erlangung des akademischen Grades eines Doktors der Naturwissenschaften (Dr. rer. nat.) genehmigten Dissertation. Vorsitzender: Univ.-Prof. Dr. Helmut Seidl Prufer¨ der Dissertation: 1. Univ.-Prof. Bernd Brugge,¨ Ph.D. 2. Prof. Dr. Jurgen¨ Borstler,¨ Blekinge Institute of Technology, Karlskrona, Schweden Die Dissertation wurde am 28.01.2016 bei der Technischen Universitat¨ Munchen¨ eingereicht und durch die Fakultat¨ fur¨ Informatik am 29.02.2016 angenommen. Abstract Software is developed in increasingly dynamic environments. Organizations need the capability to deal with uncertainty and to react to unexpected changes in require- ments and technologies. Agile methods already improve the flexibility towards changes and with the emergence of continuous delivery, regular feedback loops have become possible. The abilities to maintain high code quality through reviews, to regularly re- lease software, and to collect and prioritize user feedback, are necessary for con- tinuous software engineering. However, there exists no uniform process model that handles the increasing number of reviews, releases and feedback reports. In this dissertation, we describe Rugby, a process model for continuous software en- gineering that is based on a meta model, which treats development activities as parallel workflows and which allows tailoring, customization and extension. Rugby includes a change model and treats changes as events that activate workflows. It integrates re- view management, release management, and feedback management as workflows. As a consequence, Rugby handles the increasing number of reviews, releases and feedback and at the same time decreases their size and effort.
    [Show full text]
  • Advances in Information Systems
    Tatyana Yakhno (Ed.) Advances in Information Systems Third International Conference, ADVIS 2004 Izmir, Turkey, October 20-22, 2004 Proceedings 4y Springer Table of Contents Databases and Data Warehouses Temporality in Databases Abdullah Uz Tansel 1 On Uncertainty and Data-Warehouse Design Panagiotis Chountas, Ilias Petrounias, Christos Vasilakis, Andy Tseng, Elia El-Darzi, Krassimir T. Atanassov, Vassilis Kodogiannis , 4 A Data Warehouse Engineering Process Sergio Lujdn-Mora, Juan Trujillo 14 Aggregation and Analysis of Spatial Data by Means of Materialized Aggregation Tree Marcin Gorawski, Rafal Malczok 24 An Object-Oriented Framework for Reconciliation and Extraction in Heterogeneous Data Federations Herman Balsters, Engbert 0. de Brock 34 On Optimising Data Access Via Materialised Methods in Object-Oriented Systems Juliusz Jezierski, Mariusz Masewicz, Robert Wrembel 47 Some Modifications of Bucket-Based Algorithms for Query Rewriting Using Views Qingyuan Bai, Jun Hong, Michael F. McTear 57 Data Mining and Knowledge Discovery A Data Mining Application on Air Temperature Database T. Tugay Bilgin, A. Yilmaz Qamurcu 68 Incremental Association Rule Mining Using Materialized Data Mining Views Mikolaj Morzy, Tadeusz Morzy, Zbyszko Krolikowski 77 Outlier Effects on Databases Ahmet Kaya 88 Finding Maximal Similar Paths Between XML Documents Using Sequential Patterns Jung- Won Lee, Seung-Soo Park 96 X Table of Contents Web Information Systems Development Using Ontologies for Collaborative Information Management: Some Challenges and Ideas Victor Guevara-Masis, Ozgul Unal, Ersin C. Kaletas, Hamideh Afsarmanesh, Louis O. Hertzberger 107 The Construction of Domain Ontology and Its Application to Document Retrieval Soo-Yeon Lim, Mu-Hee Song, Sang-Jo Lee 117 WetDL: A Web Information Extraction Language Benjamin Habegger, Mohamed Quafafou 128 Towards Building Knowledge Centres on the World Wide Web Zsolt T.
    [Show full text]
  • A Unified Framework for Modeling Cooperative Design Processes and Cooperative Business Processes
    A Unified Framework for Modeling Cooperative Design Processes and Cooperative Business Processes Colette Rolland, Selmin Nurcan, Georges Grosz Université Paris 1 - Panthéon - Sorbonne, Centre de Recherche en Informatique 17, rue de Tolbiac, 75013 Paris, FRANCE, email : {rolland, nurcan, grosz}@univ-paris1.fr Abstract during this process (goals, roles, etc.), why and how it We look at any cooperative design process as a decision should be analyzed (goal decomposition, role dependency making process, i.e. a non deterministic process. The study, etc.) following some relevant techniques process is performed by responsible agents having the (brainstorming, SWOT analysis, etc.). It also suggests freedom to decide how to proceed according to their which problem should be tackled next and provides some assessment of the situation they are faced to. However, the argument to help in the making of the most appropriate cooperative design process cannot be an ad-hoc and design decision. Finally, it includes means to support chaotic process. We look at it as a repeatable process cooperative design processes and cooperative business made of steps resulting each of the application of the same processes including brainstorming, exchange and pattern for decision making. The pattern views a decision emergence of ideas. Due to the tool support, some process as a choice of the way to proceed in a given situation to automation is possible and tracing facilities emphasize the achieve an intention. An intention can be fulfilled in recording of the rationale and argumentation provided different ways depending on the situation being throughout the process. considered. We propose a process meta-model for This approach, called EKD (Enterprise Knowledge Development), is currently being applied, in the ESPRIT describing such a pattern of decision making.
    [Show full text]
  • Are Methods Really Useful?
    Are Methods Really useful ? Colette Rolland To cite this version: Colette Rolland. Are Methods Really useful ?. International Conference on Software Engineering, 1998, Japan. pp.1-3. hal-00707939 HAL Id: hal-00707939 https://hal.archives-ouvertes.fr/hal-00707939 Submitted on 19 Jun 2012 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. CREWS Report Series 98 ARE METHODS REALLY USEFUL? C. Rolland University Paris-1 Sorbonne, 17, rue de la Sorbonne, 75005 Paris cedex 5, FRANCE email : [email protected] Proceedings of the 20th International Conference on Software Engineering ICSE'98, Kyoto, Japan, April 1998. Are Methods Really Useful? Colette Rolland Université de Paris1 Sorbonne 17, rue de la Sorbonne 75231 Paris Cedex 05 France [email protected] There are a large number of methods available for information systems development (ISD). These include structured approaches, prototyping approaches, systemic approaches, object- oriented, etc. Many of these methods have been comparatively analysed in books [OLLE88] and journals (e.g [HIRS92]). Despite a large body of work concerning details of systems development methods, there is still a poor understanding of how such methods are actually used in practice [WYNE93].
    [Show full text]
  • Situational Method Engineering
    Situational Method Engineering . Brian Henderson-Sellers • Jolita Ralyte´ • Pa¨rJ.A˚gerfalk • Matti Rossi Situational Method Engineering Brian Henderson-Sellers Jolita Ralyte´ School of Software CUI, Battelle - baˆtiment A University of Technology, Sydney University of Geneva Broadway Carouge New South Wales Switzerland Australia Pa¨rJ.A˚ gerfalk Matti Rossi Dept. of Informatics and Media Aalto University Uppsala University Aalto Uppsala Finland Sweden ISBN 978-3-642-41466-4 ISBN 978-3-642-41467-1 (eBook) DOI 10.1007/978-3-642-41467-1 Springer Heidelberg New York Dordrecht London Library of Congress Control Number: 2014941286 # Springer-Verlag Berlin Heidelberg 2014 This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Exempted from this legal reservation are brief excerpts in connection with reviews or scholarly analysis or material supplied specifically for the purpose of being entered and executed on a computer system, for exclusive use by the purchaser of the work. Duplication of this publication or parts thereof is permitted only under the provisions of the Copyright Law of the Publisher’s location, in its current version, and permission for use must always be obtained from Springer. Permissions for use may be obtained through RightsLink at the Copyright Clearance Center. Violations are liable to prosecution under the respective Copyright Law.
    [Show full text]
  • Conceptual Modelling in Information Systems Engineering
    Conceptual Modelling in Information Systems Engineering Bearbeitet von John Krogstie, Andreas Lothe Opdahl, Sjaak Brinkkemper 1. Auflage 2007. Buch. xiv, 346 S. Hardcover ISBN 978 3 540 72676 0 Format (B x L): 15,5 x 23,5 cm Weitere Fachgebiete > EDV, Informatik > Hardwaretechnische Grundlagen > Systemverwaltung & Management Zu Leseprobe schnell und portofrei erhältlich bei Die Online-Fachbuchhandlung beck-shop.de ist spezialisiert auf Fachbücher, insbesondere Recht, Steuern und Wirtschaft. Im Sortiment finden Sie alle Medien (Bücher, Zeitschriften, CDs, eBooks, etc.) aller Verlage. Ergänzt wird das Programm durch Services wie Neuerscheinungsdienst oder Zusammenstellungen von Büchern zu Sonderpreisen. Der Shop führt mehr als 8 Millionen Produkte. Contents Preface ....................................................................................................... V Short biography of Arne Sølvberg ........................................................VII List of Authors .........................................................................................IX From Information Algebra to Enterprise Modelling and Ontologies – a Historical Perspective on Modelling for Information Systems Janis A. Bubenko jr......................................................................................1 Fact-Oriented Modeling: Past, Present and Future Terry Halpin...............................................................................................19 Data Integration - Problems, Approaches, and Perspectives Patrick Ziegler, Klaus R.Dittrich
    [Show full text]
  • Business Process Lines to Deal with the Variability
    Business Process Lines to deal with the Variability 1 1 2 Colette Rolland Selmin Nurcan , 1 Université Paris 1Panthéon Sorbonne 2 IAE de Paris - Sorbonne Graduate Business School Centre de Recherche en Informatique 21, rue Broca 75005 Paris France 90, rue de Tolbiac 75634 Paris cedex 13 France [email protected] [email protected] Abstract goal-driven perspective as part of an holistic view of Variability proved to be a central concept in different organizational knowledge can be found in a number of domains, manufacturing, software development etc. in approaches such as EKD-CMM [3], [32] and to support order to develop solutions that can be easily adapted to business process reengineering [1], [17], [27], [45], as well different organizational settings and different sets of as in approaches to requirements engineering. The concern customers at a low price. We argue that families of is to establish a close relationship between the ‘Why’ and business process models can facilitate the installation of the ‘What’. The former captures the strategic goals of the situated models in different organizations. We propose a organization whereas the latter tells us how they are representation system called Map to capture variability achieved through tasks carried out by actors. Focusing on in process models expressed in an intentional manner the ‘Why’ is essential to avoid unnecessary details and to through business goals and strategies. The paper focus on the ‘essence’ of the business, on what needs to presents an intentional view of the business process be achieved and the strategies required to achieve it variability and illustrates it in an excerpt of a real case independently on how to organize the business in order to in the Electricity Supply Industry.
    [Show full text]
  • Capturing System Intentionality with Maps Colette Rolland
    Capturing System Intentionality with Maps Colette Rolland To cite this version: Colette Rolland. Capturing System Intentionality with Maps. Conceptual Modelling in Information Systems Engineering, Springer-Verlag, pp.141 - 158, 2007. hal-00706146 HAL Id: hal-00706146 https://hal.archives-ouvertes.fr/hal-00706146 Submitted on 15 Jun 2012 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Capturing System Intentionality with Maps Colette Rolland Université Paris1 Panthéon Sorbonne Abstract. Conceptual modelling has emerged as a means to capture the relevant as- pects of the world on which it is necessary to provide information. Whereas conceptual models succeeded in telling us how to represent some excerpt of the world in informa- tional terms, they failed to guide system analysts in conceptualising purposeful sys- tems, i.e. systems that meet the expectations of their users. This chapter aims to inves- tigate this issue of conceptualising purposeful systems and to discuss the role that goal driven approaches can play to resolve it. It considers the challenge of new systems having a multifaceted purpose and shows how intention/strategy maps help facing this challenge. 1 Introduction Traditionally Information System (IS) engineering has made the assump- tion that an information system captures some excerpt of world history and hence has concentrated on modelling information about the Universe of Discourse [43].
    [Show full text]
  • A Comprehensive View of Process Engineering Colette Rolland
    A Comprehensive View of Process Engineering Colette Rolland To cite this version: Colette Rolland. A Comprehensive View of Process Engineering. International Conference on Ad- vanced information Systems Engineering, 1998, Italy. pp.1-24, 10.1007/BFb0054216. hal-00707940 HAL Id: hal-00707940 https://hal.archives-ouvertes.fr/hal-00707940 Submitted on 19 Jun 2012 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. CREWS Report Series 98 A COMPREHENSIVE VIEW OF PROCESS ENGINEERING C. Rolland University Paris-1 Sorbonne, 17, rue de la Sorbonne, 75005 Paris cedex 5, FRANCE email : [email protected] Proceedings of the 10th International Conference CAiSE'98, B. Lecture Notes in Computer Science 1413, Pernici, C. Thanos (Eds), Springer. Pisa, Italy, June 1998 A Comprehensive View of Process Engineering Colette Rolland University Paris-1 Sorbonne, 17, rue de la Sorbonne, 75005 Paris cedex 5, FRANCE email : [email protected] Abstract. The paper proposes a faceted framework to understand and classify issues in system development process engineering. The framework identifies four different but complementary view-points. Each view allows us to capture a particular aspect of process engineering. Inter-relationships between these aspects allow us to show the influence that one aspect has on another.
    [Show full text]
  • A Meta-Modelling Approach to Express Change Requirements
    A META-MODELLING APPROACH TO EXPRESS CHANGE REQUIREMENTS Anne Etien, Colette Rolland, Camille Salinesi CRI - Université Paris 1 – Sorbonne, 90, rue de Tolbiac, 75013 Paris – France {aetien, rolland, camille}@univ-paris1.fr Keywords: Meta-modelling, Change requirements, Evolution. Abstract: Organisations have to evolve frequently in order to remain competitive and to take into account changes in their environment. We develop a co-evolution approach to jointly make evolve the information system and the business processes. This approach relies on an explicit specification of change requirements defined with operators expressing gaps between the As-Is and the To-Be situations. However, such gaps based approach can also be used in an other evolution context, when a database or a workflow model evolves. Thus, instead of specifying new operators associated to the Map meta-model used in this co-evolution approach, we propose to define a generic typology of gaps to facilitate a precise definition of change requirements under the form of gaps. The paper presents the approach to generate a gap typology and illustrates it with the Map meta-model. 1 INTRODUCTION Furthermore, developing a specific typology for each meta-model (e.g. XML DTD (Al-Jadir, 2003), Changes often affect an organization in its whole DB meta-model (Banerjee, 1987), process meta- from business processes to information system. If model (Soffer, 2004), workflow meta-model (Casati, they want to remain competitive, organisations have 1996)…), leads to a situation where the typologies to react quickly to changes of their clients’ needs or depend on different specific meta-models and are organization goals.
    [Show full text]
  • A Systematic Mapping Study in Microservice Architecture
    A Systematic Mapping Study in Microservice Architecture Nuha Alshuqayran, Nour Ali and Roger Evans Computing Engineering and Mathematics University of Brighton Brighton, UK fn.alshuqayran, n.ali2, [email protected] Abstract—The accelerating progress of network speed, reliabil- it to be very beneficial. Microservices is also considered as ity and security creates an increasing demand to move software an appropriate architecture for systems deployed on cloud and services from being stored and processed locally on users’ infrastructures, as it can take advantage of the elasticity machines to being managed by third parties that are accessible through the network. This has created the need to develop new and on-demand provisioning features of the cloud model. software development methods and software architectural styles Companies such as Netflix, and SoundCloud have adopted the that meet these new demands. One such example in software microservices style in the cloud and gained many benefits from architectural design is the recent emergence of the microservices it [42] [6]. architecture to address the maintenance and scalability demands of online service providers. As microservice architecture is a new research area, the need for a systematic mapping study is crucial in order to summarise the progress so far and identify the gaps B. The need for a systematic mapping study and requirements for future studies. In this paper we present a systematic mapping study of microservices architectures and their implementation. Our study focuses on identifying archi- Even though microservices have emerged from the software tectural challenges, the architectural diagrams/views and quality industry and have been the focus of practitioners in the attributes related to microsevice systems.
    [Show full text]
  • Guiding Goal Modeling Using Scenarios
    IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. 24, NO. 12, DECEMBER 1998 1055 Guiding Goal Modeling Using Scenarios Colette Rolland, Carine Souveyet, and Camille Ben Achour Abstract—Even though goal modeling is an effective approach to requirements engineering, it is known to present a number of difficulties in practice. The paper discusses these difficulties and proposes to couple goal modeling and scenario authoring to overcome them. Whereas existing techniques use scenarios to concretize goals, we use them to discover goals. Our proposal is to define enactable rules which form the basis of a software environment called L’Ecritoire to guide the requirements elicitation process through interleaved goal modeling and scenario authoring. The focus of the paper is on the discovery of goals from scenarios. The discovery process is centered around the notion of a requirement chunk (RC) which is a pair <Goal, Scenario>. The paper presents the notion of RC, the rules to support the discovery of RCs and illustrates the application of the approach within L’Ecritoire using the ATM example. It also evaluates the potential practical benefits expected from the use of the approach. Index Terms—Goal modeling, scenario authoring, goal discovery. ——————————F—————————— 1INTRODUCTION OAL MODELING is an effective way to identify require- scenarios help people in reasoning about complex systems G ments [25]. The argument of goal driven approaches is [24]. Since scenarios describe real situations, they capture that the rationale for developing a system is to be found real requirements. However, because they deal with exam- outside the system itself, in the enterprise [19] in which the ples and illustrations, scenarios only provide restricted re- system shall function.
    [Show full text]