A Goal Based Methodology for Developing Domain-Specific Ontological Frameworks Faezeh Ensan, Weichang Du Faculty of Computer Science, University of New.

Slides:



Advertisements
Similar presentations
Designing Multimedia with Fuzzy Logic Enrique Diaz de Leon * Rene V. Mayorga ** Paul D. Guild *** * ITESM, Guadalajara Campus, Mexico ** Faculty of Engineering,
Advertisements

1 Enhancing Requirements Engineering by Quality Modelling: a structured Framework Paolo Donzelli Dept of Informatics Office of the Prime Minister Rome,
SOFTWARE ENGINEERING ONTOLOGY A DEVELOPMENT METHODOLOGY Projects: eLSE & SELBO Iveta Georgieva.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering Vahid Jalali Amirkabir university of technology, Department of computer.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
1 COST G9 - Work group 2 meeting Székesfehérvár, Hu Modeling real property transactions Radoš Šumrada Faculty of Civil and Geodetic.
Tips on Critiquing Articles The goal of the educational research is to observe phenomena in the field of education and attempt to explain why these phenomena.
Software engineering for supply chains:
COST G9 - Work group 2 Cadastral science meeting Aalborg, Dk Modeling methodology for real estate transactions Radoš Šumrada Faculty.
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
Software Requirements
CSCI928 Software Engineering Requirements & Specifications Modeling System Interactions Tri A. Kurniawan, M.Eng. Ph.D Candidate
Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering درس مهندسی نیازمندی ها استاد دکتر عبداله زاده دانشجو خیرالنسا مرچانت.
Requirements Engineering Processes
Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 5.
Overview of Software Requirements
1 CSC-3324: Chapter 4 Title: What is a requirement? Mandatory reading: Sommerville 6, 7 th ed., Chap.: 7.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Goal.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Towards.
Lecture Nine Database Planning, Design, and Administration
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Software Product Lines Krishna Anusha, Eturi. Introduction: A software product line is a set of software systems developed by a company that share a common.
Object-Oriented Analysis and Design
Issues in Teaching Software Engineering Virendra C. Bhavsar Professor and Director, Advanced Computational Research Laboratory Faculty of Computer Science.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Overview of the Database Development Process
Object Oriented Analysis By: Don Villanueva CS 524 Software Engineering I Fall I 2007 – Sheldon X. Liang, Ph. D.
CSI315 Web Applications and Technology Overview of Systems Development (342)
ITEC224 Database Programming
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Loc-based Variability for Mobile Information Systems Raian Ali, Fabiano Dalpiaz, Paolo Giorgini CAiSE’ June 2008.
Software Requirements Engineering CSE 305 Lecture-2.
1 Minggu 9, Pertemuan 17 Database Planning, Design, and Administration Matakuliah: T0206-Sistem Basisdata Tahun: 2005 Versi: 1.0/0.0.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Exploring the Intentional Dimension during Software (Architecture) Design adding the “why” and the “who/where” to the “what” and the “how” Daniel Gross.
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
Model-Driven Analysis Frameworks for Embedded Systems George Edwards USC Center for Systems and Software Engineering
Pallob Piriyasurawong Ph.D Assistant Professor Panita Wannapiroon Ph.D Assistant Professor Tanawat Jariyapoom Ph.D. Candidate Division of Information and.
Database Planning, Design, and Administration Transparencies
1 Workshop on Business-Driven Enterprise Application Design & Implementation Cristal City, Washington D.C., USA, July 21, 2008 How to Describe Workflow.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Raian Ali, Fabiano Dalpiaz, Paolo Giorgini Location-based Software Modeling and Analysis: Tropos-based Approach.
Knowledge Representation of Statistic Domain For CBR Application Supervisor : Dr. Aslina Saad Dr. Mashitoh Hashim PM Dr. Nor Hasbiah Ubaidullah.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
CIS 112 Exam Review. Exam Content 100 questions valued at 1 point each 100 questions valued at 1 point each 100 points total 100 points total 10 each.
Using Meta-Model-Driven Views to Address Scalability in i* Models Jane You Department of Computer Science University of Toronto.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
CSE 303 – Software Design and Architecture
Introduction The design, development and maintenance of concurrent software are difficult tasks. Truly effective support methodologies have yet to be developed.
1 Structuring Knowledge for a Security Trade-offs Knowledge Base Golnaz Elahi Department of Computer Science Eric Yu Faculty of Information Study University.
Prof. Hany H. Ammar, CSEE, WVU, and
CS223: Software Engineering Lecture 3: Software Develoment Processes.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Cmpe 589 Spring Fundamental Process and Process Management Concepts Process –the people, methods, and tools used to produce software products. –Improving.
Applying Adaptive Software Development (ASD) Agile Modeling on Predictive Data Mining Applications: ASD-DM Methodology M. Alnoukari 1 Z.Alzoabi 2 S.Hanna.
SECURE TROPOS Michalis Pavlidis 8 May Seminar Agenda  Secure Tropos  History and Foundation  Tropos  Basics  Secure Tropos  Concepts / Modelling.
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Independent Study of Ontologies
Blended Methodologies
Life Cycle Models PPT By :Dr. R. Mall.
Introduction to Software Engineering
Faezeh Ensan and Weichang Du
FInal Presentation : Object Oriented Software Engineeering
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
CSC 480 Software Engineering
Agent-oriented Software Engineering Methodologies
System Design and Acquisition
UML Design for an Automated Registration System
Presentation transcript:

A Goal Based Methodology for Developing Domain-Specific Ontological Frameworks Faezeh Ensan, Weichang Du Faculty of Computer Science, University of New Brunswick, Fredericton, Canada Introduction The field of ontology engineering has witnessed a wide range of algorithms, tools, methodologies and ontological frameworks for developing and maintaining different types of ontologies. By ontological frameworks we mean those proposals that specify particular phases and also provide implemented components for developing ontologies. Our objective in this research is to define some methods, guidelines and criteria for creating ontological frameworks. This proposed high-level scheme assists ontology engineers to specify the goal of an ontological framework and its capabilities, the domain knowledge it intends to exploit, and also to indicate its dependency to a specific domain. A Methodology For Creating Ontological Frameworks With the purpose of specifying and tracking the ‘intentions’ and ‘goals’ of an ontological framework during the analysis and design phases, we utilize the i* model. i* is a conceptual framework for modeling processes and indicating the dependencies among several agents of a software system for specifying the goals to be achieved and the tasks to be performed. Our methodology consists of four major phases. In the first phase, we specify specific actors, and their distinct soft goals. Later in the second phase we introduce the popular hard- goals that can realize the specified abstract softgoals. We then analyze the goals and tasks of the ontological framework and propose a set of related domain specific constrains in the analysis phase. Finally, in the implementation phase, we suggest the employment of the business process definition and also UML activity diagrams for modeling an ontological framework. Phase 2: Specifying The Goals That Contribute to The High- Level Softgoals Phase 3: Analyzing and Decomposing Goals and Tasks Phase 4: Specifying Business Processes A Case Study As a case study, we consider creating an ontological framework for tourism attractions of Canada. We employed this example to explain the features of the proposed methodology. Phase 1: Specifying Actors and their High-Level Softgoals We define five types of actors for a typical ontological framework: the customer or stakeholder that supports and owns the project, the ontology engineer who is familiar with the ontology technologies and tools, the domain expert, the end-user who benefits from the ontology which is developed by the framework and finally the framework itself which should be created using the high-level methodology. Fig 1. The Actors of an Ontological Framework and Their High-level Softgoals. Fig 2. The goals that contribute to the high level soft- goals. Fig 3. The SR model for the ‘provide a good ontology’ softgoal Fig 4. The activity diagram for the ‘Find recall of concept extraction algorithms’ business process Reference 1.Yu, E. S.-K, Modeling strategic relationships for process reengineering. PhD thesis, Toronto, Ont., Canada. 2.Ensan, F. and Du, W. Towards domain-centric ontology development and maintenance frameworks. In Proceedings of the Nineteenth International Conference on Software Engineering & Knowledge Engineering (SEKE’2007).