EDIT WP5 Internet Platform for Cybertaxonomy

1. EDIT WP5 Internet Platform for Cybertaxonomy Modelling for Revisionary Taxonomy Gubányi A.-Kiss, V.-Kilián, I. (Hungarian Natural History Museum) Meeting: KEW London, 21-Jan-07.

2. EDIT is a multidisciplinary/ interdisciplinary project • Synergic effects • Ecologists challenge/inspire informatic experts to find computerised solutions to new real-life problems • Informatic experts should challenge/inspire ecologists by opening up new technical possibilities to solve real life problems • new, unexpected results, breakthrough

3. Targets • 5.2.1 Modelling for Revisionary Taxonomy • Carry out an in-depth modelling effort of the revisionary work process. Initial interviews with Taxonomists across the EDIT partnership, and review of existing descriptions of process serve to identify prototype test agents (players contributing to the platform such as taxonomists, libraries and other intra- or extra-institutional resources) for interviews. Results of interviews are used in building Use Cases and Scenarios which are feed back to agents for evaluation. Finally, modelling using standard and advanced informatics techniques in workflow analysis and process modelling incorporating data flows and the knowledge of domain experts on the underlying business rules and local constraints. In the process, identify bottlenecks and suggest action for their removal to the network.

4. Work-process • Team: Gubányi, A biologist, Kiss V. biologist, Kilián I. informatic engineer • Steps: 1. Interviews with leading Hungarian taxonomists and biodiversity monitorists 2. Preparing questionnaire document 3. Business modelling • Results: (1. Use Cases) 2. Workflow models 3. Dataflow models • Tool: Enterprise Architect 6.5 from Geoffrey Sparx/Sparx Systems • Language: Unified Modelling Language (UML2) • Metodology: Rational Unified Process (RUP) + customizations

5. 1.Application data 2.Domain (software) model 3.Description of the modelling formalism (UML) 4.Description of the description of modelling tool Business Modelling and the 4 Layers of Metamodel stack • (Actual data of specimen collected) • Abstraction of data: classes, associations, taxonomical model • Metamodel of UML2, as a modeling tool • Metametamodel: The way of storing, managing, extending, modifying the metamodel

6. Use Cases • Precondition: creating a software to make certain tasks for certain people easier • Defining the circle of players contacting/using the new system (stakeholder-analysis) • Human players/users, organisations and automated systems • Defining a set of functions the new software should perform • Drawing the borders of the software. What should it do, and what not • Determining the most important relationships between functions • Connecting functions with players • Analysing and collecting requirements for functions

7. UML Metamodel/Profile for Cybertaxonomy • New stereotypes • generic metaclasses/concepts and/or relations • new graphic tools to be used • attributes/default values of new concepts • New generic metarelations (new relationships between new concepts) • New constraints for stereotypes • Model transformation rules • Codegeneration rules

9. UML Metamodel/Profile for Cybertaxonomy

10. Results/deliverables • Questionnaires (direct result of interviewing) • Metamodel: • EDITUML.XML an UML profile for EnterpriseArchitect • Modelling Guidelines.doc written description • Model (EDIT.EAP): • Stakeholder analysis • Domain model • Business process (workflow) model • Dataflow model

11. 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

12. 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

13. 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

14. 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

15. 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

16. Questionnary • Information reflecting the chosen workflow modelling scheme • Set of activites (not necessary sequential) • Steps of activities (sequential!) • Inputs of activities • Outputs of activities • Tools of activities • Materials of activities • Other information…

17. Structure of the model (EA Project Browser) • Domain model • Attribute value datatypes (without identity, eg. LengthDensityRange) • Domain objects (with identity, eg. <<chemical>> Acid) • Business Process Model • Business Context/Stakeholders (what actors/players we are talking about) • Business Workflows (dataflow and process flow analysis) • EDIT UML Technology (metamodel extensions in source/model form)

18. Business Context/Stakeholders

19. Business Processes: Modelling the diversity • Business Process • the root package contains concepts (activities, objects), that are common for each branch-science • Business Process/Algology • concepts specific to Algology as a branch-science • Business Process/Dipterology • Business Process/Entomolgy • Business Process/Malacology • Business Process/…

29. Status of work (20-Jan-07)

30. Thank you for your attention!