DOCSLIB.ORG

A Conceptual Model and Prototype for a Case-Based

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Conceptual Model and Prototype for a Case-Based A CONCEPTUAL MODEL AND PROTOTYPE FOR A CASE-BASED ADAPTIVE ANALYST SUPPORT SYSTEM by WILLIAM H. GWINN, B.A., M.S. A DISSERTATION IN BUSINESS ADMINISTRATION Submitted to the Graduate Faculty of Texas Tech University in Partial Fulfillment of the Requirements for the Degree of DOCTOR OF PHILOSOPHY Approved Accepted May, 1999 Copyright 1999, William H. Gwinn ACKNOWLEDGMENTS 1 would like to take this opportunity to thank my wife Amie G. Gwinn for her encouragement and support throughout this endeavor I express my gratitude to Dr. Surya B. Yadav, my dissertation chair for his guidance and extreme patience over the long haul. I also thank my dissertation committee. Dr. Ralph R. Bravoco, Dr. Glenn J. Browne, and Dr. Rich L. Sorenson for their pertinent comments and recommendations and Dr. Nirup Menon and Mr. Harold Webb T.A. for their comments on improving the clarity of the screens which comprise the user interface for the prototype system. A special thanks to Ms. Barbi Dickensheet, Thesis Coordinator of the Texas Tech Graduate School for her preliminary and final dissertation review and helpful tips along the way 11 TABLE OF CONTENTS ACKNOWLEDGMENTS ii ABSTRACT viii LIST OF TABLES ix LIST OF FIGURES x CHAPTER 1 INTRODUCTION 1 Background 1 Requirement Definition 1 Requirement Determination Process o Importance of Fact Gathering and Analysis Activities 3 The Nature of Fact Gathering Activities .1 Why an Analyst Needs Support 4 Nature of Fact Gathering and Analysis Support 5 Problem Statement 6 Research Questions 7 Research Objectives 7 Research Deliverables 8 Significance of the Research 9 Structure of the Dissertation 10 II. LITERATURE REVIEW 12 Introduction 12 Works on Requirement Determination Processes and Analyst Activities 13 G. B.Davis 13 Yadav 15 Alan M. Davis 15 iii Byrd, Cossick, and Zmud 16 Works on Expert Analyst Assistants 17 Systems Analysis Expert Aide (SYS-AIDE) 17 Analyst Assistant 18 Analyst Assist 19 Expert Modeling Support System 20 Dalal/Yadav EMSS Modification 20 Works on Case-Based Learning 23 CYRUS 24 PLEXUS 25 CABSYDD 25 Summary 25 HI RESEARCH METHODOLOGY 27 Introduction 27 Formulating the Problem 29 Constructing the Knowledge Level Principles 29 Constructing the Symbol Level Principles 30 Developing the Prototype System 31 Evaluating and Validating the System 32 A Validation Framework 34 Summary 3 8 IV. CONCEPTUAL DEVELOPMENT OF A CASE-BASED ADAPTIVE ANALYST SLT^PORT SYSTEM 39 Introduction 39 Fact Gathering Activities 39 System Behavior 47 Knowledge Level Concepts and Principles ^6 Knowledge Level Concepts 58 Knowledge Level Principles 62 iv Requirement Specification 63 Requirement Set 63 A Conceptual Model of a CAASS 64 The Dialog Management Subsystem (DMS) 65 The Fact Gathering Coordinator Subsystems (FGCS) 66 Organization Base Management Subsystem (OBMS) 66 The Case Base Management Subsystem (CBMS) 66 The Domain Knowledge Base Management Subsystem (DKBMS) 67 The Basic Knowledge Base Management Subsystem (BKBMS) 67 The Resource Base Management Subsystem (RBMS) 67 Summary 68 \' SYMBOL LEVEL ARCHITECTURE FOR A CASE-BASED ADAPTIVE ANALYST SUPPORT SYSTEM (CA.ASS) 69 Introduction 69 Symbol Level Concepts and Principles 69 Symbol Level Concepts 69 Symbol Level Principles 73 Symbol Level Architecture of CAASS 74 Case-based Reasoning and Learning 76 Case Knowledge Frame Base 1~! Knowledge Frame Base 78 Structure Design 80 Summary 87 VI. DESIGN .AND IMPLEMENTATION OF THE PROTOTYPE 88 Introduction 88 Logical Flow Design 88 Implementation Languages 97 Visual BASIC 5.0 M7 The Haley Enterprise Products ^;8 CAASS Prototype Components 99 User Interface Module 100 System Control Module 115 Knowledge Frame Base 116 Case Knowledge Frame Base 116 Executables 116 Summary 116 VII. VERIFICATION AND VALIDATION 117 Introduction 117 Conceptual Model Verification 117 Prototype Verification 119 Verifying the Input Capability and User Interface 119 Verifying the Knowledge Base 120 Verifying Case-based Learning 120 Verifying Case-based Retrieval 121 Verifying Template Modification 121 Conceptual Model Validation 121 Prototype Validation 121 Summary 122 Vin. EXPERIMENTAL DESIGN 123 Introduction 123 Experiment Design 123 Group Selection 124 Testing Instrument 125 Experiment Layout and Model 126 Hypothesis Testing 128 User Survey 129 Summary 132 IX. RESULTS AND CONCLUSIONS VI Introduction 133 Experimental Results 133 Analysis of Variance (ANOVA) 133 User Survey Results 136 Conclusions 139 Summary 139 X RESEARCH CONTRLBUTIONS, LIMITATIONS. AND FUTURE RESEARCH 142 Introduction 142 Research Deliverables 142 Research Contributions 143 Research Limitations 146 Future Work 147 REFERENCES 148 APPENDIX. ORGANIZATIONAL CASE FACT LISTS FOR MEDIA TECHNOLOGY SERVICES AND HOMEOU^^TRS OF AMERICA 152 \ii ABSTRACT ¥c\\ researchers have addressed the question of how information system requirements should be derived. The rapidly changing needs of increasingly complex organizations are pressuring the analyst to rapidly produce information requirements This means the analyst needs the capability to rapidly acquire, organize and analyze organizational facts from which information requirements are derived. This research concerns the development of an adaptive analyst support system to assist the analyst with the gathering and managing of organizational facts. A check-list for analyst fact gathering activities is suggested. The knowledge needs, conceptual model, and architecture for a case-based adaptive analyst support system are developed and a prototype support system is implemented. This tool provides a means for an analyst to recall facts and information requirements from previously analyzed organizations rapidlv and adapt the recalled information to current organizational needs. The prototype demonstrates the feasibility of a case-based approach to an adaptive support system. The implemented prototype's adaptability is demonstrated b\' the growth of its case-base with repeated use. The primary contribution of this research is to provide the MIS communitv with a new analysis tool concept. The research describes the toofs ability to gather, organize store, recall, and adapt organizational facts to a current situation rapidly and efficientK This enhances the analyst's ability to rapidly produce information requirements Vlll LIST OF TABLES 4.1 Fact Gathering Activities 41 4.2 System Functions 49 4 3 System Functions and Supported Activities 57 5.1 Mapping Conceptual Model to Symbol Level Components 74 9 1 Responses to CAASS End-User Survey 137 9 2 Question 12 Responses 138 IX LIST OF FIGURES 2.1 Dalai and Yadav EMSS 21 3 1 A Validation Framework for CAASS 35 4 1 Knowledge Level Concepts 60 4.2 CAASS Conceptual Model 65 5.1 Frame and Slots 71 5.2 Frame Network 72 5.3 Symbol Level Architecture for CAASS 75 5 4 Structure Chart Symbols 81 5.5 CAASS Structure Chart 82 5.6 Begin New Case 83 5.7 Adapt Check-List 84 5.8 Resume Existing Case 85 5.9 Learn Case, Perform Case Matciiing, and Analyze Case Facts 86 6.1 CAASS System Control Module Logical Diagram 89 6.2 System Control Module Case Comparison Process 90 6.3 System Control Module Inference Engine Processes 91 6.4 System Control Module Case-Based Reasoner and General Utility Processes 92 6.5 User Interface Module Check-List and Print Check-List Processes 93 6.6 User Interface Module Display Info and Begin New Case Processes *^)4 6.7 User Interface Module Build Current Case, Resume Case, and Display Current Case Processes 95 X 6.8 User Interface Module Modify Case Slots and Display Match Processes 96 6.9 Screen Hierarchy 101 6.10 Opening Screen 102 6.11 Information Screen 103 6.12 Begin New Case Screen 105 6.13 Check-List Screen 106 6.14 Parameters and Objectives Screen 108 6.15 Strategy and Properties Screen 109 6.16 Identify'Entities Screen 110 6.17 Functions and Processes Screen 111 6.18 Case Comparison Screen 114 6.19 Case Comparison Screen with Case Suggested 114 7.1 A VaUdation Framework 118 8.1 Experiment Layout 127 8.2 CAASS User Survey Questionnaire 131 XI CHAPTER I INTRODUCTION Background One of the most difficult tasks in developing information systems is the determination of an organization's information requirements. Requirement specifications should deal with three basic questions (Yadav and Chand, 1989): 1. What should requirements be'^ 2. How should requirements be derived? 3. How should requirements be stated? The first and third questions address the actual content of each requirement and the form used to state the content of each requirement. The second question is concerned with the processes used to determine the contents of the requirements. Although a number of professionals have discussed the first and third questions, few researchers have addressed the second question (Yadav and Chand, 1989). Requirement Definition Webster's Dictionary defines requirement as "something required; something demanded or needed" (Webster, 1997, p. 1141). IEEE standard 729 (1983) defines requirement as: "(1) a condition or capability needed by a user to solve a problem or achieve an objective; (2) a condition or capability that must be met or possessed by a system ... to satisfy a contract, standard, specification, or other formally imposed document" (p. 29). This research concerns the process by which the organization's information requirements are derived. Requirement Determination Process The requirements determination phase of system analysis begins with the recognition of an organizational problem that requires a solution and ends when there is a complete description of the external behavior of the system needed to solve the organization's problem. The process seeks to describe what the system should do to support the organization's goals, not how it will do it (Davis, 1990). The requirements determination process is complex because it spans multiple organizational domains. The organization's executive, middle manager and the user technician domains are intimately involved with the requirements determination process (Yadav and Chand, 1989). The process used to complete the requirements determination phase is composed of three steps (Dalai and Yadav, 1989). The first step is to obtain the raw requirements from the organization.
Load more

Recommended publications
  • Conceptual Modelling and Humanities
    Joint Proceedings of Modellierung 2020 Short, Workshop and Tools & Demo Papers Modellierung 2020: Short Papers 13 Conceptual Modelling and Humanities Yannic Ole Kropp,1 Bernhard Thalheim2 Abstract: Humanities are becoming a hyping field of intensive research for computer researchers. It seems that conceptual models may be the basis for development of appropriate solutions of digitalisation problems in social sciences. At the same time, humanities and social sciences can fertilise conceptual modelling. The notion of conceptual models becomes enriched. The approaches to modelling in social sciences thus result in a deeper understanding of modelling. The main aim of this paper is to learn from social sciences for conceptual modelling and to fertilise the field of conceptual modelling. 1 The Value of Conceptual Modelling 1.1 Computer science is IT system-oriented Computer system development is a complex process and needs abstraction, separation of concerns, approaches for handling complexity and mature support for communication within development teams. Models are one of the main artefacts for abstraction and complexity reduction. Computer science uses more than 50 different kinds of modelling languages and modelling approaches. Models have thus been a means for system construction for a long time. Models are widely used as an universal instrument whenever humans are involved and an understanding of computer properties is essential. They are enhanced by commonly accepted concepts and thus become conceptual models. The main deployment scenario for models and conceptual models is still system construction (with description, prescription, and coding sub-scenarios) although other scenarios became popular, e.g. documentation, communication, negotiation, conceptualisation, and learning. 1.2 Learning from Digital Hunanities Digital humanities is becoming a hyping buzzword nowadays due to digitalisation and due to over-applying computer technology.
    [Show full text]
  • Conceptual Model Evaluation. Towards More Paradigmatic Rigor Jan Recker1
    Conceptual Model Evaluation. Towards more Paradigmatic Rigor Jan Recker1 1 Centre for Information Technology Innovation Queensland University of Technology 126 Margaret Street, Brisbane QLD 4000, Australia [email protected] Abstract. Information Systems (IS) research has so far been primarily con- cerned with the development of new modeling languages, techniques, and methods. Also, evaluation approaches have been developed in order to assess the appropriateness of a modeling approach in a given context. Both modeling and evaluation approaches, however, lack epistemological rigor, leading to problems regarding the applicability of a certain modeling language in a given context on the one hand, and regarding the feasibility of certain evaluation ap- proaches towards certain modeling questions on the other hand. We therefore argue for a philosophical-paradigmatic discussion of evaluation methods for conceptual modeling languages in order to assess their applicability in given modeling contexts and present our research in progress towards a framework for paradigmatic discussion on model evaluation. Keywords. Philosophy, modeling methods, information modeling, research evaluation 1 Introduction The importance of information systems (IS) for successful businesses is widely rec- ognized [1]. Their implementation is preceded by their development through design methodologies which utilize information models to specify IS on a conceptual level. Such conceptual models have been successfully employed throughout IS theory and practice. This has led, however, to the proliferation of an enormous amount of avail- able modeling approaches. The “flooding” of the IS discipline with a multiplicity of conceptual modeling approaches consequently leads to an immanent need for com- paring and evaluating existing modeling methods in order to determine which ap- proach is most appropriate for a given modeling task.
    [Show full text]
  • Conceptual Modeling
    Conceptual Modeling Laurens Van Damme Table of contents • What are Conceptual models? • Conceptualization • Mental model • Conceptual model • How are Conceptual models different from others? • Nonnecessity • Requirements 2 What are Conceptual models? 3 Overview 4 Overview We all know what this is! 5 Overview 6 Conceptualization = set of concepts in the mind of an agent 7 Concept • Aristotle ±340BC • Cognitive processes ↳ makes, uses and transforms ↳ mental representations • Mental representations • Refer to / are about something • Non-conceptual (sensation) • Conceptual (thoughts/believes) https://www.nytimes.com/2016/05/27/world/europe/greece-aristotle-tomb.html 8 Concept Conceptual mental representation → Rely on representation primitives = concepts Concept • Reflects regularities in reality that are cognitively relevant to us • Cognitive filter → strip out properties unnecessary for the problem 9 Concept Example Navigating on the Belgian’s highways Ordering of road segments Road segment Intersection between road segments Filtered: width, distance of or traffic on the road segments https://en.wikipedia.org/wiki/List_of_motorways_in_Belgium 10 Conceptualization = set of concepts in the mind of an agent • Individual concepts (e.g., E19) • Relational concepts: associations that relate individual concepts https://thesaurus.plus/antonyms/conceptualization 11 Overview 12 Mental Model The external reality filtered through the lens of a conceptualization Different levels of generality: • Reflect general beliefs (e.g., every road segment has
    [Show full text]
  • On Using Conceptual Modeling for Ontologies
    On Using Conceptual Modeling for Ontologies S. Spaccapietra1, C. Parent2, C.Vangenot1 and N. Cullot3 1 Database Laboratory, EPFL, 1015 Lausanne, Switzerland [email protected], [email protected] 2 HEC-INFORGE, University of Lausanne, 1015 Lausanne, Switzerland [email protected] 3LE2I Laboratory of Business, University of Burgundy, 21000 Dijon, France [email protected] Abstract. Are database concepts and techniques suitable for ontology design and management? The question has been on the floor for some time already. It gets a new emphasis today, thanks to the focus on ontologies and ontology services due to the spread of web services as a new paradigm for information management. This paper analyzes some of the arguments that are relevant to the debate, in particular the question whether conceptual data models would adequately support the design and use of ontologies. It concludes suggesting a hybrid approach, combining databases and logic-based services.1 1. Introduction Nowadays, all major economic players have decentralized organizational structures, with multiple autonomous units acting in parallel. New information systems have to handle a variety of information sources, from proprietary ones to those available in web services worldwide. Their complexity is best controlled using a network of coordinated web services capable of grasping relevant information wherever it may be and exchanging information with all potential partners. Data semantics is at the heart of such multi-agent systems. Interacting agents in an open environment do not necessarily share a common understanding of the world at hand, as used to be the case in traditional enterprise information systems.
    [Show full text]
  • A Multi-Paradigm Modeling Framework for Modeling and Simulating Problem Situations
    Proceedings of the 2014 Winter Simulation Conference A. Tolk, S. Y. Diallo, I. O. Ryzhov, L. Yilmaz, S. Buckley, and J. A. Miller, eds. A MULTI-PARADIGM MODELING FRAMEWORK FOR MODELING AND SIMULATING PROBLEM SITUATIONS Christopher Lynch Jose Padilla Saikou Diallo John Sokolowski Catherine Banks Virginia Modeling, Analysis and Simulation Center Old Dominion University 1030 University Boulevard Suffolk, VA 23435, USA ABSTRACT This paper proposes a multi-paradigm modeling framework (MPMF) for modeling and simulating problem situations (problems whose specification is not agreed upon). The MPMF allows for a different set of questions to be addressed from a problem situation than is possible through the use of a single modeling paradigm. The framework identifies different levels of granularity (macro, meso, and micro) from what is known and assumed about the problem situation. These levels of granularity are independently mapped to different modeling paradigms. These modeling paradigms are then combined to provide a comprehensive model and corresponding simulation of the problem situation. Finally, the MPMF is implemented to model and simulate the problem situation of representing the spread of obesity. 1 INTRODUCTION When building models and simulations, it is desirable to have a well-defined problem and an agreed upon solution for representing that problem, yet most models depart from this premise. This is difficult to achieve when representing problem situations where there is no agreed upon specification due to differences in opinions of the team (Vennix, 1999). Modeling this type of problem has been addressed by reaching a consensus on what the problem is as proposed in soft-systems methodology (Checkland, 2000).
    [Show full text]
  • A Conceptual Model of Software Development
    Extracted form Ph. Kruchten: Software project management with OpenUP Draft April 2007 A Conceptual Model of Software Development A software project is temporary endeavour intended to create a new software product or service, or the software part of a software-intensive system. It is temporary in the sense that it has a definite beginning and a definite end, in contrast with a continuous endeavour, such as running the IT operations of an organization. A software project has specific and sometimes conflicting objectives and many constraints of diverse nature, mainly technical, temporal and financial. Software project management is therefore the art of balancing competing objectives, managing risks, and overcoming constraints to successfully deliver a product which meets the needs of both customers and users (the customer paying the bill not always being the end-user). A conceptual model of software development To explore the many facets of software project management, we will first introduce a conceptual model of software development. This model (or ontology) of software projects is organized around eight key concepts and their relationships: 1. Intent 2. Product 3. Work 4. People 5. Time 6. Quality 7. Risk 8. Project Intent The concept of Intent denotes what the project is trying to achieve. The Intent defines the scope of the project, the intentions and hopes of the key stakeholders, the objectives. While we think of the intent as “the requirements” or “the specification”, in practice Intent may take many diverse forms: a set of tests that the product must pass contributes to define Intent. A set of software problem reports that must be dealt with also indirectly defines Intent.
    [Show full text]
  • Conceptual Modeling for Virtual Reality
    Conceptual Modeling for Virtual Reality Olga De Troyer, Frederic Kleinermann, Bram Pellens, and Wesley Bille WISE Research Lab Vrije Universiteit Brussel Pleinlaan 2, B-1050 Brussel, Belgium {olga.detroyer,frederic.kleinermann,bram.pellens, Wesley.Bille}@vub.ac.be Abstract that the development of VR applications directly starts at the implementation level. The virtual world that needs to This paper explores the opportunities and challenges for be created must be expressed in terms of low level VR Conceptual Modeling in the domain of Virtual Reality building blocks, such as textures, shapes, sensors, (VR). VR applications are becoming more feasible due to interpolators, etc. This requires a considerable amount of better and faster hardware, and due to new technology and background knowledge in VR. In addition, it makes the faster network connections they also start to appear on the gap between the application domain and the level at Internet. However, the development of such applications which the virtual world needs to be specified very large, is still a specialized, time-consuming and expensive and this makes the translation from the concepts in the process. By introducing a Conceptual Modeling phase application domain into implementation concepts a very into the development process of VR applications, a difficult issue. number of the obstacles preventing a quick spread of this type of applications can be removed. However, existing Like for other domains, introducing a Conceptual Design Conceptual Modeling techniques are too limited for phase in the development process of a VR application modeling a VR application in an appropriate way. The may help the VR community in several ways.
    [Show full text]
  • Conceptual Model Building -101 November 2018 Overview
    Conceptual Model Building -101 November 2018 Overview Introduction to Health Behavior Theory Basics of designing a theory-informed conceptual model to better understand health behavior Understanding the link between a theory-informed conceptual model and a logic model Part 1. Introduction to Health Behavior Theory What health behaviors help to prevent chronic disease? What factors facilitate these health behaviors? What factors prevent these health behaviors? As you can see…there are many factors that influence behavior. So, where do you start? Social Ecological Model CDC’s version of Social Ecological Model Ecological Model of Predictors of Childhood Overweight Community, demographic, and societal characteristics Ethnicity Socioeconomic Parenting styles and status family characteristics School foods& Child feeding Peer and sibling drinks practices interactions Child characteristics Crime rates and Types of foods and child risk factors Family TV neighborhood available in the viewing safety Gender Age home Parent CHILD monitoring of Work hours Nutritional DIETARY WEIGHT SEDENTARY child TV knowledge INTAKE STATUS BEHAVIOR viewing Knowledge & School PHYSICAL Parent preference physical Parent dietary Attitudes Familial ACTIVITY for activity education intake susceptibility to program weight gain Parent activity Leisure time Parent food patterns preferences Parent Parent weight encouragement of status child activity Accessibility of Family leisure recreational time activity facilities Accessibility of convenience Adapted from: Davison & Birch. foods and restaurants 2001 Decision-Oriented Theories Underlying Psychology Core Insight - Behavior is determined by perceptions of costs and benefits that would occur if one performed the behavior -HBM and other theories differ in how they calculate the benefits and the costs Modifications -Behavior is determined by perceptions of costs and benefits if one performed the behavior and about ability to perform the behavior.
    [Show full text]
  • 3 Scientific Models
    Name Class Date CHAPTER 1 The World of Life Science SECTION3 Scientific Models BEFORE YOU READ After you read this section, you should be able to answer these questions: • How do scientists use models? • What are scientific theories and laws? What Are Models? You need a microscope to see inside most cells. How STUDY TIP can you learn about the parts of a cell if you don’t have Learn New Words As you a microscope? One way is to use a model. Scientists use read, underline words you models to learn about things that they cannot see or don’t know. When you fi gure out what they mean, touch. write the words and their A model is something scientists use to represent an defi nitions in your notebook. object or event to make it easier to study. Scientists study models to learn how things work or are made in the natural world. However, you cannot learn everything by studying a model, because models are not exactly like the objects they represent. Some types of scientific models are physical models, mathematical models, and conceptual models. READING CHECK 1. Explain Why can’t you PHYSICAL MODELS learn everything about an A toy rocket and a plastic skeleton are examples of object or event by studying a physical models. Physical models are models that you model? can see or touch. Many physical models look like the things they represent. The figure shows students using a model of a human body to learn how the body works. However, because the model is not alive, the students cannot learn exactly how the body functions.
    [Show full text]
  • Ontology and Information Systems
    Ontology and Information Systems 1 Barry Smith Philosophical Ontology Ontology as a branch of philosophy is the science of what is, of the kinds and structures of objects, properties, events, processes and relations in every area of reality. ‘Ontology’ is often used by philosophers as a synonym for ‘metaphysics’ (literally: ‘what comes after the Physics’), a term which was used by early students of Aristotle to refer to what Aristotle himself called ‘first philosophy’.2 The term ‘ontology’ (or ontologia) was itself coined in 1613, independently, by two philosophers, Rudolf Göckel (Goclenius), in his Lexicon philosophicum and Jacob Lorhard (Lorhardus), in his Theatrum philosophicum. The first occurrence in English recorded by the OED appears in Bailey’s dictionary of 1721, which defines ontology as ‘an Account of being in the Abstract’. Methods and Goals of Philosophical Ontology The methods of philosophical ontology are the methods of philosophy in general. They include the development of theories of wider or narrower scope and the testing and refinement of such theories by measuring them up, either against difficult 1 This paper is based upon work supported by the National Science Foundation under Grant No. BCS-9975557 (“Ontology and Geographic Categories”) and by the Alexander von Humboldt Foundation under the auspices of its Wolfgang Paul Program. Thanks go to Thomas Bittner, Olivier Bodenreider, Anita Burgun, Charles Dement, Andrew Frank, Angelika Franzke, Wolfgang Grassl, Pierre Grenon, Nicola Guarino, Patrick Hayes, Kathleen Hornsby, Ingvar Johansson, Fritz Lehmann, Chris Menzel, Kevin Mulligan, Chris Partridge, David W. Smith, William Rapaport, Daniel von Wachter, Chris Welty and Graham White for helpful comments.
    [Show full text]
  • Conceptual Modeling of Time for Computational Ontologies
    IJCSNS International Journal of Computer Science and Network Security, VOL.20 No.6, June 2020 1 Conceptual Modeling of Time for Computational Ontologies Sabah Al-Fedaghi [email protected] Computer Engineering Department, Kuwait University, Kuwait 1.1 Ontologies and Conceptual Modeling Summary To provide a foundation for conceptual modeling, To provide a foundation for conceptual modeling, ontologies have been introduced to specify the entities, the ontologies have been introduced to specify the entities, the existences of which are acknowledged in the model [4]. existences of which are acknowledged in the model. Conceptual modeling involves “representing aspects of the Ontologies are essential components as mechanisms to world for the purpose of understanding and communication model a portion of reality in software engineering. In this context, a model refers to a description of objects and [, and hence] the contribution of a conceptual modeling notation rests in its ability to promote understanding about processes that populate a system. Developing such a description constrains and directs the design, development, the depicted reality among human users” [5]. Conceptualization refers to abstracting a given portion of and use of the corresponding system, thus avoiding such difficulties as conflicts and lack of a common reality that “exists beyond our concepts” [6], i.e., entities and processes that “exist” in the domain of the modeled understanding. In this cross-area research between modeling and ontology, there has been a growing interest system (note that what there may not be what exists – see [7]). It is also stated that ontology is “an explicit in the development and use of domain ontologies (e.g., Resource Description Framework, Ontology Web specification of a conceptualization” [8].
    [Show full text]
  • Rapid Application Development
    Rapid Application Development Contact at EsperantoXL Ewoud Stuurman [email protected] +31 6 4835 3537 EsperantoXL BV. Rijnzathe 30 3454 PV DE MEERN Executive summary Rapid application development platforms provide a graphical model driven approach with pre-built application components which allow users to visually construct complex processes and applications without coding. This enables both technical and business individuals to orchestrate and deploy business applications with ease and speed. The right model driven development platform provides significant productivity advantages over traditional development methods and enables project delivery by smaller yet faster teams. Whether your business processes are unique, you need to distinguish yourself from the competition or you need the ability to adapt to fast changes in the market you operate in; rapid application development supports these needs. Key benefits: ✓ Cost effective and time saving ✓ Accelerate innovation by 9-12 months ✓ Easy to make adjustments ✓ Tailor made; use what you need ✓ Easy to integrate with current IT systems ✓ Simplified lifecycle management ✓ No coding ✓ Fast delivery ✓ Responsive applications for every platform Rapid Application Development Intro In today's world, markets change fast and companies need to be flexible to adapt to these changes. Also most companies find themselves in challenging environments due to fierce existing competitors and disrupting new start-ups. This requires an IT landscape that is able to quickly adapt, to support the organisation’s business, rather than the other way around, where the business needs to adapt to cope with the existing IT landscape. Developing transformative or disruptive applications at high speed to keep up with the changing markets, requires rapid experimentation, frequent iteration, and close collaboration between business and IT.
    [Show full text]