1 / 15

EDIT WP5 Internet Platform for Cybertaxonomy

This presentation discusses the challenges and benefits of modelling taxonomical and inventorying activities in a unified way. It explores the multi-level approach, disciplinary dimension, and bottleneck analysis, and proposes a model-view approach for unifying modelling efforts.

Télécharger la présentation

EDIT WP5 Internet Platform for Cybertaxonomy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. EDIT WP5 Internet Platform for Cybertaxonomy Modelling for Inventory/Unification of modelling efforts Gubányi A.-Kiss, V.-Kilián, I. (Hungarian Natural History Museum) Meeting: HNHM Budapest, 7-May-07.

  2. Workflow Modelling • Challenges: • Modelling the Taxonomical/Inventorying activities in a unified way • Multi level approach – from the simplest to the most detailed abstraction/granularity • Disciplinary Dimension - Modelling the work of several experts by keeping the overlapping activities commonly defined • Bottleneck analysis: what CAN be and what SHOULD be supported in an electronical/computerized way

  3. Workflow Modelling • Targets: • Unified models for dataflow and control flow matters • Activity diagrams with control flow links • Object tags with control flow links

  4. Semantics of Activity Diagrams • Activities, links, conditions and tokens • Firing of an activity - if each incoming links deliver a token • Scheduling of outgoing tokens is unspecified • A composite activity is finished when each incoming activity is finished • Fork and Join nodes can be described by the means above • Decision and merge nodes can be described by the means above • Receive signal nodes: triggers • Object and activity nodes can be mixed

  5. Coping with diversity • Business Process (root package) + subpackages for certain disciplines • the root package contains concepts (activities, objects), that are common (inherited) for each branch-science • common visibility rule for structured and OO programming • subpackages contain concepts that are specific to the discipline • Problems: • when to be regarded specific? (The name should be different or the realization?) • an activity step is missing at a specific discipline • links (control/object flows) are represented in EA differently from classes

  6. Multiple level of abstraction • Compound activities, embedded structures • Model-view approach – a single, unified model in the background, with different projections/views

  7. Unification of modelling efforts • Common agreements (as described before) • Agreement on Package Structure. (Proposal disciplines-subdisciplines) • Agreement on Modelling Common Activities

  8. Abstract process

  9. General Process

  10. Inventory Process - Preparation

  11. Inventory Process - Preparation

  12. Decorated Workflow - Preparation

  13. Decorated Workflow - Identification

  14. Results Algology(Dr. Buczkó K.) Bryophytology Colepterology Dipterology(Dr. Földváry M.) Lepidopterology Entomology(Dr. Merkl O.) Malacology(Dr. Fehér Z.) Bryology (Dr. Papp B) Lichenology (Dr. Lőkös L) Experience shows: . Disciplines have only in occasional case anything specific . Disciplines mostly only bypass certain steps . Disciplines are to 90-95% same

  15. Thank you for your attention!

More Related