danno
Uploaded by
12 SLIDES
265 VIEWS
120LIKES

Proposal for Workflow Management Software in Cybertaxonomy

DESCRIPTION

This proposal outlines a comprehensive workflow management software aimed at enhancing cybertaxonomy processes. It emphasizes key aspects of workflow modeling, including basic concepts, relationships, and incremental evolution. The software supports both client-server and standalone solutions, facilitating efficient information gathering, task assignment, and decision-making. It employs various technological integrations—such as GPS and cameras—while providing options for workflow customization. This approach is designed to streamline tasks in the field and enhance data management for natural history collections.

1 / 12

Download Presentation

Proposal for Workflow Management Software in 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 Proposal for a Workflow Management Software Gubányi A.-Kiss, V.-Kilián, I. (Hungarian Natural History Museum) Meeting: HNHM Budapest, 7-May-07.

  2. Workflow modelling • The basic concepts and relationships to be modelled • Incremental evolution with other concepts • Inferred relationships: eg. sequence of activities can be inferred from dataflow model. • Other business rules/constraints

  3. Workflow modelling • The basic concepts and relationships to be modelled • Incremental evolution with other concepts • Inferred relationships: eg. sequence of activities can be inferred from dataflow model. • Other business rules/constraints

  4. Workflow modelling • The basic concepts and relationships to be modelled • Incremental evolution with other concepts • Inferred relationships: eg. sequence of activities can be inferred from dataflow model. • Other business rules/constraints

  5. Workflow modelling • The basic concepts and relationships to be modelled • Incremental evolution with other concepts • Inferred relationships: eg. sequence of activities can be inferred from dataflow model. • Other business rules/constraints

  6. Workflow modelling scheme • The basic concepts and relationships to be modelled • Incremental evolution with other concepts • Inferred relationships: eg. sequence of activities can be inferred from dataflow model. • Other business rules/constraints

  7. Basic Workflow Modelling • Human Actors • tasks are passed to them electronically) • Activities • information gathering • decisions • wrappers for System Actors • System Actors • Embedded software (word processors, RDBMS) • Attached hardware (GPS, Camera, etc.)

  8. Workflow Management Software in a Nutshell I. • Client-Server solution • Server side • maintains the workflow • appoints new workers • Client side • Feeding information by forms • Wrappers for common software • Downloading information from external devices directly (camera, GPS) • Downloading information from Web-based electronic services (databases)

  9. Workflow Management Software in a Nutshell II. • Standalone solution for field work • Standalone solution running on a single (on a small network of laptops) • Reduced functionality • No Internet access • No huge database access • Export-import/download-upload functionality • Exporting the working environment to a laptop before field work • Importing the working environment to a laptop afterwards

  10. Workflow Management Software in a Nutshell III. • Proposal for implementation • Server-based Java programming (Java Server Pages • Thin-Fat client: functionality is embedded in client side only when it is delivered by external software • Description of workflows • Alternatives for workflows depending on discipline • Compiled vs. interpreted solution • Compiled: workflows are hard-coded • Interpreted: metamodel is hard-coded (customizable!) • Language of workflow description • UML Activity diagrams? • Business Process Engineering Language BPEL • UML Software Process Engineering Model SPEM

  11. Workflow Management Software in a Nutshell IV. • Interpreted workflow description (proposal) • Metamodel is hard coded • Workflow customization/editing facilities are to be programmed (new Use Case!!!)

  12. Thank you for your attention!

More Related