, - - harmoniqua most1 harmoniqua knowledge base and modelling guidelines presenter affiliation name...

<country>, <year> <presenter> - <workshop / course> - HarmoniQuA MoST

1

HarmoniQuA Knowledge Base and modelling guidelines

Presenter

affiliation name - country


2

Structure Introduction to the KB Previous initiatives Design criteria An ontological approach How the KB was produced The ontological structure of the KB Viewing the content of the KB How the KB is used in MoST Conclusions


3

Introduction to the KB

What is the KB? A collection of knowledge on modelling for various domains of water

management Structured according to an ontology (I.e. a sort of data model) Developed by decomposing the modelling process:

step - task – (activity + method)

What will it do? Provide guidance to

Various user types (manager, modeller, auditor, stakeholder, public)Various domainsVarious job complexities


4

Previous initiatives

Capability Maturity Model (Humphrey 1989, SE) Simulation Maturity Model

5 stages: (1) ad hoc, (2) repeatable, (3) defined, (4) managed, (5) optimised SMM was the starting point for:

Good Modelling Practice Handbook - Netherlands [Van Waveren et al., 2000, Scholten et al., 2001]

Other modelling guidelines in water management: Murray-Darling groundwater flow modelling,Australia [Middlemis, 2000] Bay-Delta modelling protocol for water and environmental modelling in

Californian [BDMF, 2000]


5

Design criteria (1)

Provide guidance during modelling that is dedicated to: Users (water manager, modeller, auditor, stakeholder, public) Domains (groundwater, precipitation-runoff, hydrodynamics,

flood forecasting, surface water quality, biota (ecology) and socio-economics);

Define the modelling process by decomposition into:1. Process into steps

2. Steps into tasks

3. Tasks into activities and activity related methods


6

Design criteria (2)

Other design criteriaEasy update via WEBEasy maintenanceFlexible structureAuthorisation management with

Knowledge administratorsKnowledge editorsRegistered users (can read and comment)

Operating system independentSoftware engineering criteria


7

An ontological approach (1)

Definition of an ontology Explicit specification of a conceptualisation (Gruber, 1993, 1995) Formal specification of a shared conceptualisation (Borst, 1997)

with conceptualisation = what can be represented, e.g. Concepts (i.e. entities, ideas, plans, etc.) Relations between the concepts


8


Why ontologies (Uschold et al., 1998)? Communication (exchange structured knowledge between

people and/or organisations), Interoperability (understanding knowledge between machines

and between men and machines) Systems engineering (software / KB systems: re-use of

knowledge and making knowledge explicit).


9


How to develop tools with ontologies:1. Develop an ontological structure (how the knowledge is

structured);2. Get the knowledge (knowledge acquisition);3. Put the knowledge in a Knowledge Base, which has the

previously defined ontological structure;4. Build software application(s) using the KB


10

How the KB was produced (1) First draft in a meeting with 5 persons with expertise in

modelling for water management knowledge engineering

The modelling process was decomposed in steps and subsequently the steps in tasks Produced structure diagrams of tasks in and between steps Produced empty spreadsheets for each task per domain (9x7) With for each task a spreadsheet, to be filled with

name task definition task explanation task [list of] activities with associated methods previous task next task other info (examples, relevant references and URLs, …)

3 types of tasks: normal, decision, review

Purpose and conditions

Conceptualisation

Model set-up

Calibration and validation

Prediction

Steps


11

The ontological structure of the KB


13

How the KB was produced (2) Implementing the KB

Experts from each domain filled in the content of the KB and contributed terms to the glossary. Expert contributions included:

Naming, defining and explaining each task Defining activities and associated methods for each task. Providing information on other aspects of each task

Subsequently all task spreadsheets were uploaded in the ontological KB

Improving the KB A web based tool for adding/editing KB by modelling experts has been produced The domain responsible persons edited and improved the KB The KB has been tested in 2 rounds:

round 1: 2004 round 2: 2005


14

Viewing the content of the KB

The KB can be viewed in 2 ways (first register as user):with Modelling Support Tool (MoST): easy browsing, flowchartswith the knowledge editor: long (printable) text:

First modelling step: mainly interaction between water manager and modeller

Next modelling steps: work of (teams of) modeller(s), reviewed by water manager and auditor


16

How the KB is used in MoST Toolbox to

use guidelines from KB Monitor modelling process Store monitored modelling

process in model journal Report from model journal Get advice from previous

model studies / model journals

Other web based tools for editing KB and glossary

Training material

Guiding

model journal 1Monitoring

Model archive

User

model journal 2Knowledge

Base

model journal 3

model journal 4

Advising

Reporting


17

ConclusionMoST = tool = KB + monitoring modelling

(see presentation: HarmoniQuA MoST)Too early for final conclusion on KB

Level of detail/granularity, complete, consistent?Agreement on knowledge on modelling?Does MoST meet the needs of its users?

Not easy to use? We developed training material:Students (demonstration, short, long)Professionals (demonstration, short, long)Web-based: presentations, hands-on experience, discussions, etc.)

, - - harmoniqua most1 harmoniqua knowledge base and modelling guidelines presenter affiliation name...

Documents

knowledge explicit

collection of knowledge

modelling process

harmoniqua most7

harmoniqua most8

harmoniqua most9

harmoniqua most10

environmental modelling