SEVENTH FRAMEWORK PROGRAMME ICT PPP Future Internet · 2017. 4. 20. · UC-ENV1.4-sem-04-V01...

SEVENTH FRAMEWORK PROGRAMMEICT PPP

Future Internet

The Environmental Observation Web and its ServiceApplications within the Future Internet

FP7-284898

Collaborative project

Annex - ENVIROFI Use Case Requirements Report(WP1)

Creation date: 30/09/2011

The research leading to these results has received funding from the European Community’sSeventh Framework Programme (FP7/2007-2013) under grant agreement 284898

Annex - ENVIROFI UC Req. Report (WP1)

Table of Contents

1 Introduction 4

2 Use cases 112.1 WP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1.1 Login User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1.2 User Trust Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.1.3 Store data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1.4 Edit data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.1.5 Correct relations between concepts . . . . . . . . . . . . . . . . . . . . . . . . . 152.1.6 Access data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.1.7 Store information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.1.8 Edit information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.1.9 Access information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.1.10 Merge Concept List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.1.11 Merge Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.1.12 Extract Concept List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.1.13 Check occurrence record for plausibility . . . . . . . . . . . . . . . . . . . . . . . 252.1.14 Provide feedback on occurrences in area . . . . . . . . . . . . . . . . . . . . . . 262.1.15 Provide Identification Key Information . . . . . . . . . . . . . . . . . . . . . . . . 272.1.16 Provide feedback on dangerous occurrence . . . . . . . . . . . . . . . . . . . . . 282.1.17 Check Identifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.1.18 Generate Habitat Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.1.19 Generate Species Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.1.20 Provide identification for image . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.1.21 Provide identification for sound . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.1.22 Create Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.1.23 Modify Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.1.24 Delete Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.1.25 Access Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412.1.26 Provide Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422.1.27 Provide Occurrence - Teachers and pupils . . . . . . . . . . . . . . . . . . . . . . 432.1.28 Local Interesting Information - Teachers and pupils . . . . . . . . . . . . . . . . . 442.1.29 Provide Occurrence - Nature hobbyists & Advanced amateurs . . . . . . . . . . 482.1.30 Local Interesting Information - Nature hobbyists and Advanced amateurs . . . . 512.1.31 Fill Survey Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542.1.32 Provide Invasive Occurrence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.1.33 Create and maintain Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.1.34 Assess Background material - Researcher . . . . . . . . . . . . . . . . . . . . . 612.1.35 Get local and regional check lists - Researcher . . . . . . . . . . . . . . . . . . . 622.1.36 Provide Occurrence - Researcher . . . . . . . . . . . . . . . . . . . . . . . . . . 632.1.37 Validate Occurrence - Researcher . . . . . . . . . . . . . . . . . . . . . . . . . . 652.1.38 Register User on Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672.1.39 Discovery and View on Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682.1.40 Input Occurrences on Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712.1.41 Administrate “my” Occurrences on Portal . . . . . . . . . . . . . . . . . . . . . . 752.1.42 Provide Feedback on Occurrences on Portal . . . . . . . . . . . . . . . . . . . . 772.1.43 Provide Further Knowledge on Habitats and Species on Portal . . . . . . . . . . 792.1.44 Administrate Portal on Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812.1.45 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822.1.46 Upload Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832.1.47 Adjust Identifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862.1.48 Generate Distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

of 91Copyright © 2011 ENVIROFI Consortium


Index of tables

1 List of Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Summary of Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 UC-ENV1.1-auth-01-V01 – Login User . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 UC-ENV1.1-auth-02-V01 – User Trust Level . . . . . . . . . . . . . . . . . . . . . . . . . 135 UC-ENV1.2-data-01-V02 – Store data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 UC-ENV1.2-data-02-V02 – Edit data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 UC-ENV1.2-data-03-V01 – Correct relations between concepts . . . . . . . . . . . . . . 168 UC-ENV1.2-data-04-V01 – Access data . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 UC-ENV1.2-data-05-V01 – Store information . . . . . . . . . . . . . . . . . . . . . . . . 1810 UC-ENV1.2-data-06-V01 – Edit information . . . . . . . . . . . . . . . . . . . . . . . . . 1911 UC-ENV1.2-data-07-V01 – Access information . . . . . . . . . . . . . . . . . . . . . . . 2012 UC-ENV1.3-mrg-01-V01 – Merge Concept List . . . . . . . . . . . . . . . . . . . . . . . 2113 UC-ENV1.3-mrg-02-V01 – Merge Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2214 UC-ENV1.3-mrg-03-V01 – Extract Concept List . . . . . . . . . . . . . . . . . . . . . . . 2415 UC-ENV1.4-sem-01-V01 – Check occurrence record for plausibility . . . . . . . . . . . . 2616 UC-ENV1.4-sem-02-V01 – Provide feedback on occurrences in area . . . . . . . . . . . 2717 UC-ENV1.4-sem-03-V01 – Provide Identification Key Information . . . . . . . . . . . . . 2818 UC-ENV1.4-sem-04-V01 – Provide feedback on dangerous occurrence . . . . . . . . . 2919 UC-ENV1.4-sem-05-V01 – Check Identifications . . . . . . . . . . . . . . . . . . . . . . 3120 UC-ENV1.5-dst-01-V01 – Generate Habitat Distribution . . . . . . . . . . . . . . . . . . 3221 UC-ENV1.5-dst-02-V01 – Generate Species Distribution . . . . . . . . . . . . . . . . . . 3322 UC-ENV1.6-ident-01-V01 – Provide identification for image . . . . . . . . . . . . . . . . 3423 UC-ENV1.6-ident-02-V01 – Provide identification for sound . . . . . . . . . . . . . . . . 3724 UC-ENV1.7-chkl-01-V01 – Create Checklist . . . . . . . . . . . . . . . . . . . . . . . . . 3925 UC-ENV1.7-chkl-02-V01 – Modify Checklist . . . . . . . . . . . . . . . . . . . . . . . . . 4026 UC-ENV1.7-chkl-03-V01 – Delete Checklist . . . . . . . . . . . . . . . . . . . . . . . . . 4127 UC-ENV1.7-chkl-04-V01 – Access Checklist . . . . . . . . . . . . . . . . . . . . . . . . 4228 UC-ENV1.7-chkl-05-V01 – Provide Checklists . . . . . . . . . . . . . . . . . . . . . . . . 4329 UC-ENV1.A-mob-01-V01 – Provide Occurrence - Teachers and pupils . . . . . . . . . . 4430 UC-ENV1.A-mob-02-V01 – Local Interesting Information - Teachers and pupils . . . . . 4631 UC-ENV1.B-mob-01-V01 – Provide Occurrence - Nature hobbyists & Advanced amateurs 4932 UC-ENV1.B-mob-02-V01 – Local Interesting Information - Nature hobbyists and Ad-

vanced amateurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5233 UC-ENV1.B-mob-03-V01 – Fill Survey Checklist . . . . . . . . . . . . . . . . . . . . . . 5534 UC-ENV1.B-mob-05-V01 – Provide Invasive Occurrence . . . . . . . . . . . . . . . . . . 5735 UC-ENV1.B-prt-04-V01 – Create and maintain Checklist . . . . . . . . . . . . . . . . . . 5936 UC-ENV1.C-mob-01-V01 – Assess Background material - Researcher . . . . . . . . . . 6237 UC-ENV1.C-mob-02-V01 – Get local and regional check lists - Researcher . . . . . . . 6338 UC-ENV1.C-mob-03-V01 – Provide Occurrence - Researcher . . . . . . . . . . . . . . . 6539 UC-ENV1.C-mob-04-V01 – Validate Occurrence - Researcher . . . . . . . . . . . . . . 6740 UC-ENV1.D-prt-01-V01 – Register User on Portal . . . . . . . . . . . . . . . . . . . . . 6841 UC-ENV1.D-prt-02-V01 – Discovery and View on Portal . . . . . . . . . . . . . . . . . . 6942 UC-ENV1.D-prt-03-V01 – Input Occurrences on Portal . . . . . . . . . . . . . . . . . . . 7243 UC-ENV1.D-prt-04-V01 – Administrate “my” Occurrences on Portal . . . . . . . . . . . . 7644 UC-ENV1.D-prt-05-V01 – Provide Feedback on Occurrences on Portal . . . . . . . . . . 7845 UC-ENV1.D-prt-06-V01 – Provide Further Knowledge on Habitats and Species on Portal 8046 UC-ENV1.D-prt-07-V01 – Administrate Portal on Portal . . . . . . . . . . . . . . . . . . 8247 UC-ENV1.D-prt-08-V01 – Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8348 UC-ENV1.D-prt-09-V01 – Upload Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8449 UC-ENV1.D-prt-10-V01 – Adjust Identifications . . . . . . . . . . . . . . . . . . . . . . . 8750 UC-ENV1.D-prt-11-V01 – Generate Distributions . . . . . . . . . . . . . . . . . . . . . . 90



1 Introduction

According to the ENVIROFI methodology of how to analyze and document user requirements, thisreport comprises the collection of use cases that were edited and agreed within the member team ofthe ENVIROFI work package WP1.

WP1 focuses on the use of Future Internet technology for survey, analysis, quality assurance,persistence and dissemination of biodiversity data.

The report is automatically generated from the content of the ENVIROFI Use Case server acces-sible at http://envirofi.server.de.

The following tables provide a summary and overview description of the use cases as furtherdocumented in section 2.

Use Case Name

UC-ENV1.1-auth-01-V01 Login User

UC-ENV1.1-auth-02-V01 User Trust Level

UC-ENV1.2-data-01-V02 Store data

UC-ENV1.2-data-02-V02 Edit data

UC-ENV1.2-data-03-V01 Correct relations between concepts

UC-ENV1.2-data-04-V01 Access data

UC-ENV1.2-data-05-V01 Store information

UC-ENV1.2-data-06-V01 Edit information

UC-ENV1.2-data-07-V01 Access information

UC-ENV1.3-mrg-01-V01 Merge Concept List

UC-ENV1.3-mrg-02-V01 Merge Data

UC-ENV1.3-mrg-03-V01 Extract Concept List

UC-ENV1.4-sem-01-V01 Check occurrence record for plausibility

UC-ENV1.4-sem-02-V01 Provide feedback on occurrences in area

UC-ENV1.4-sem-03-V01 Provide Identification Key Information

UC-ENV1.4-sem-04-V01 Provide feedback on dangerous occurrence

UC-ENV1.4-sem-05-V01 Check Identifications

UC-ENV1.5-dst-01-V01 Generate Habitat Distribution

UC-ENV1.5-dst-02-V01 Generate Species Distribution

UC-ENV1.6-ident-01-V01 Provide identification for image

UC-ENV1.6-ident-02-V01 Provide identification for sound

UC-ENV1.7-chkl-01-V01 Create Checklist

UC-ENV1.7-chkl-02-V01 Modify Checklist

UC-ENV1.7-chkl-03-V01 Delete Checklist

UC-ENV1.7-chkl-04-V01 Access Checklist

cont...


http://envirofi.server.de


Use Case Name

UC-ENV1.7-chkl-05-V01 Provide Checklists

UC-ENV1.A-mob-01-V01 Provide Occurrence - Teachers and pupils

UC-ENV1.A-mob-02-V01 Local Interesting Information - Teachers and pupils

UC-ENV1.B-mob-01-V01 Provide Occurrence - Nature hobbyists & Advanced amateurs

UC-ENV1.B-mob-02-V01 Local Interesting Information - Nature hobbyists and Advancedamateurs

UC-ENV1.B-mob-03-V01 Fill Survey Checklist

UC-ENV1.B-mob-05-V01 Provide Invasive Occurrence

UC-ENV1.B-prt-04-V01 Create and maintain Checklist

UC-ENV1.C-mob-01-V01 Assess Background material - Researcher

UC-ENV1.C-mob-02-V01 Get local and regional check lists - Researcher

UC-ENV1.C-mob-03-V01 Provide Occurrence - Researcher

UC-ENV1.C-mob-04-V01 Validate Occurrence - Researcher

UC-ENV1.D-prt-01-V01 Register User on Portal

UC-ENV1.D-prt-02-V01 Discovery and View on Portal

UC-ENV1.D-prt-03-V01 Input Occurrences on Portal

UC-ENV1.D-prt-04-V01 Administrate “my” Occurrences on Portal

UC-ENV1.D-prt-05-V01 Provide Feedback on Occurrences on Portal

UC-ENV1.D-prt-06-V01 Provide Further Knowledge on Habitats and Species on Portal

UC-ENV1.D-prt-07-V01 Administrate Portal on Portal

UC-ENV1.D-prt-08-V01 Login

UC-ENV1.D-prt-09-V01 Upload Data

UC-ENV1.D-prt-10-V01 Adjust Identifications

UC-ENV1.D-prt-11-V01 Generate Distributions

Table 1: List of Use Cases

Use Case Description

UC-ENV1.1-auth-01-V01 The user starts the ENVIROFI biodiversity application. The useris uniquely identified for further processing steps

UC-ENV1.1-auth-02-V01 The users trust level is adjusted based on feedback provided. Ifthe users feedback correlates with that from trusted users thetrust level will rise; conversely if this is not so it will sink. Thesame holds true for identifications provided.

UC-ENV1.2-data-01-V02 Data can be entered from external sources

UC-ENV1.2-data-02-V02 Existing occurrence records can be edited by the user

cont...




UC-ENV1.2-data-03-V01 Manually correct relations between concepts in the ENVIROFIBiodiversity Ontology. In some cases, it may also be necessaryto introduce new relations

UC-ENV1.2-data-04-V01 the user can download biodiversity data via services for integra-tion into external applications

UC-ENV1.2-data-05-V01 Information can be entered from external sources

UC-ENV1.2-data-06-V01 Knowledge resources can be edited by the user

UC-ENV1.2-data-07-V01 the user can download biodiversity information via services forintegration into external applications

UC-ENV1.3-mrg-01-V01 In order to successfully merge data from different sources, wemust first merge and align the concepts used to describe thisdata. In this use case, based on various aspects of the 2 sources,we use semantic algorithms to align these concepts

UC-ENV1.3-mrg-02-V01 data resources from external sources will be merged into theENVIROFI Biodiversity Repository this merge will be performedbased on the concept lists corresponding to the data resource

UC-ENV1.3-mrg-03-V01 In order to merge data resources from external sources, one mustfirst align and merge the concepts defining this data. This taskis performed in UC UC-ENV1.3-data-02-V01 Merge DataIn orderto perform this task the relevant concepts must first be extractedfrom the external data resource. this UC provides the conceptsfrom within the external data resource

UC-ENV1.4-sem-01-V01 An occurrence record is checked against the knowledge con-tained in the ENVIROFI Biodiversity Ontology.The plausibility ofthis occurrence record is returned to the user

UC-ENV1.4-sem-02-V01 Based on the users current location, information is provided oninteresting biodiversity in the area.The nature of this informationwill vary across user groups

UC-ENV1.4-sem-03-V01 Provide the user with relevant information from an IdentificationKeyThis can serve both identification purposes as well as providea support when navigating to the proper habitat or species name

UC-ENV1.4-sem-04-V01 Based on the species identified, information is provided on pos-sible dangers ensuing from this species, i.e. poisonous mush-rooms, plants that can burn the skin.

UC-ENV1.4-sem-05-V01 Based on feedback from UC-ENV1.D-prt-05-V01 Provide Feed-back on Occurrence, occurrence records are adjusted. In mostcases, this only changes the identification, but could also pertainto the location of the occurrence.

cont...




UC-ENV1.5-dst-01-V01 Based on existing data habitat distribution information is calcu-lated and stored in the ENVIROFI Biodiversity Ontology

UC-ENV1.5-dst-02-V01 Based on existing species occurrence data together with variousbackground layers such as habitats and land cover, new speciesdistribution information is generated or existing species distribu-tion information is extended.

UC-ENV1.6-ident-01-V01 A user provides an image of an individual plant or animal (prob-ably only a leaf or wing)The system suggests possible identifica-tions based on pattern recognition algorithms

UC-ENV1.6-ident-02-V01 The user sees and hears a species that they can not directlyidentify. By provision of a short recording of the animals call, thesystem can suggest possible identifications

UC-ENV1.7-chkl-01-V01 In various scenarios, the user is provided with a checklist ofspecies or habitats to provide data on. Such checklists must becreated.

UC-ENV1.7-chkl-02-V01 In various scenarios, the user is provided with a checklist ofspecies or habitats to provide data on. Such checklists must bemodified and extended.

UC-ENV1.7-chkl-03-V01 In various scenarios, the user is provided with a checklist ofspecies or habitats to provide data on. Once they are no longerused, these checklists can also be deleted.

UC-ENV1.7-chkl-04-V01 In various scenarios, the user is provided with a checklist ofspecies or habitats to provide data on. The user must be ableto access the checklist on his survey device

UC-ENV1.7-chkl-05-V01 In various scenarios, the user is provided with a checklist ofspecies or habitats to provide data on. The user must be ableto select one or more checklists on his survey device

UC-ENV1.A-mob-01-V01 The user sees an interesting plant or animal they wish to pro-vide an occurrence record of. The species is photographed andidentified. After some QA steps assuring that the identification iscorrect, the occurrence record is uploaded

UC-ENV1.A-mob-02-V01 The user is out in the woods and wonders what could be of in-terest in this area. Based on the userâC™s location, the systemprovides information on interesting species or habitats known tobe in the users vicinity at this time of year.

UC-ENV1.B-mob-01-V01 The user sees an interesting plant or animal they wish to pro-vide an occurrence record of. The species is photographed andidentified. After some QA steps assuring that the identification iscorrect, the occurrence record is uploaded

cont...




UC-ENV1.B-mob-02-V01 The user is out in the woods and wonders what could be of in-terest in this area. Based on the userâC™s location, the systemprovides information on interesting species or habitats known tobe in the users vicinity at this time of year.

UC-ENV1.B-mob-03-V01 The survey participant is provided a list of species and habitattypes to find. Occurrence information on these species and habi-tat types is provided.

UC-ENV1.B-mob-05-V01 The survey participant is provided a list of invasive and allergenicspeciesto find. Occurrence information on these species is pro-vided.

UC-ENV1.B-prt-04-V01 In order to provide participants on a survey with checklists onwhich species and habitat types to identify and record, such alist must be created and maintained. The same holds true forinvasive or allergenic species.

UC-ENV1.C-mob-01-V01 The qualified user is provided with relevant background informa-tion. What information is provided will depend on the area ofinterest of the user, that can be based either on the current loca-tion of the mobile device or also on coordinates provided by theuser. A list of available topics will be provided to the user, whichcan then be viewed.

UC-ENV1.C-mob-02-V01 The qualified user is provided with relevant local and regionalcheck lists on species and habitats. What information is providedwill depend on the area of interest of the user, that can be basedeither on the current location of the mobile device or also on coor-dinates provided by the user. The user can then specify specificspecies or habitats, as well as data quality requirements; a cus-tomised checklist providing additional information on the entriesselected will be generated based on these requirements.

UC-ENV1.C-mob-03-V01 The user sees a species or habitat they wish to provide an oc-currence record of. The species or habitat is photographed andidentified. After some QA steps assuring that the identification iscorrect, the occurrence record is uploaded

UC-ENV1.C-mob-04-V01 The user sees a species or habitat occurrence record of. Thespecies or habitat they wish to comment on. Based on a regionand topic of interest, the user is provided with all correspondingoccurrence records available. The user can select an individualoccurrence record and both validate the existing information aswell as providing additional information to this record. This infor-mation can either be uploaded directly or stored for later uploadwhen connectivity is possible.

cont...




UC-ENV1.D-prt-01-V01 The user opens the ENVIROFI Biodiversity Portal. Creates a newuser and configures their profile. Registered users can modifytheir profile

UC-ENV1.D-prt-02-V01 The user opens the ENVIROFI Biodiversity Portal. The userspecifies the type of data they are interested in. This data isdisplayed to the user as maps as well as in tabular form as re-quested. In addition, further available knowledge on the habitatsand species can be requested.

UC-ENV1.D-prt-03-V01 The user opens the ENVIROFI Biodiversity Portal and logs in.The user provides occurrence data including images and loca-tional information. Once the occurrence data has been validatedit will be uploaded to the ENVIROFI Biodiversity Repository

UC-ENV1.D-prt-04-V01 The user can view, modify and share the occurrence data (includ-ing images and locational information) he/she provided . In addi-tion, it is possible to configure competitions within certain usageareas. This will allow users to compare the quality and quantityof occurrence records provided with other users.

UC-ENV1.D-prt-05-V01 The user opens the ENVIROFI Biodiversity Portal and logs in.The user browses through existing occurrence information andidentifies an error. The user provides what they consider to bethe proper information for the occurrence record. Based on theusers ranking, as well as inputs received from other users, thisinformation is then added to the occurrence record.

UC-ENV1.D-prt-06-V01 The user opens the ENVIROFI Biodiversity Portal and logs in.The user browses through existing species and habitat informa-tion and selects a habitat or species type to be annotated. Theuser provided further information for storage in the ENVIROFIBiodiversity Ontology.

UC-ENV1.D-prt-07-V01 The administrator logs on to the system. Once clearly identified,the administrator can configure new users as well as assigningranks to new and existing users. Competitions, based on check-lists and showing which participant has found the most speciesfrom the list, can be configured within the portal. Offensive datacan be blocked.

UC-ENV1.D-prt-08-V01 The user opens the ENVIROFI Biodiversity Portal. Registeredusers can log on to the system.

UC-ENV1.D-prt-09-V01 An external occurrence dataset is integrated into the system. Inorder to assure consistancy with existing data, a semantic mergeis performed

UC-ENV1.D-prt-10-V01 Users can provide feedback on the identification of occurrencerecords. This additional information must be integrated with theexisting identification, and based on the plausibility of the identi-fication as well as feedback a new identification provided.

cont...




UC-ENV1.D-prt-11-V01 New Habitat and Species distributions are calculated based onoccurrence data and background layers

Table 2: Summary of Use Cases



2 Use cases

2.1 WP1

2.1.1 Login User

Login User

Use Case ID UC-ENV1.1-auth-01-V01

Use Case Name Login User

Revision and Reference V01; http://envirofi.server.de/servlet/is/4104/

Reference http://envirofi.server.de/servlet/is/4104/

Use Case Diagram

Status Planned

Priority of accomplishment Must have

Goal Identify the user

Summary The user starts the ENVIROFI biodiversity application. The useris uniquely identified for further processing steps

Category User Registration

Actor All

Primary Actor (initiates) All

Stakeholder

Requested InformationResources

Type: list of registered users

Preconditions The user is registered with the ENVIROFI Biodiversity System

Triggers The user starts the mobile app or logs in to the web portal.

Main success scenario 1. The user is successfully identified and can proceed with furtherparts of the scenario.

Extensions 1. The same user registration should also be available from boththe mobile devices as well as the web portal (Scenario D)

Alternative paths

Post conditions

Non-functional requirements

Validation statement All further steps taken by this user can be clearly correlated withthis user

Notes

Author and date KS_UBA, 2011-07-19

Refines UseCase System uniquely identifies users

cont...


http://envirofi.server.de/servlet/is/4104/


Login User

Included in UseCase Register User on PortalAdministrate Portal on PortalLogin

Table 3: UC-ENV1.1-auth-01-V01 – Login User

2.1.2 User Trust Level

User Trust Level

Use Case ID UC-ENV1.1-auth-02-V01

Use Case Name User Trust Level



Use Case Diagram

Status Planned


Goal Adjust the users trust level based on feedback provided

Summary The users trust level is adjusted based on feedback provided. Ifthe users feedback correlates with that from trusted users thetrust level will rise; conversely if this is not so it will sink. Thesame holds true for identifications provided.


Actor All


Stakeholder



Preconditions The user is registered with the ENVIROFI Biodiversity System

Triggers An action that influences the trust level is started

Main success scenario The users trust level is adjusted based on feedback provided. Ifthe users feedback correlates with that from trusted users thetrust level will rise; conversely if this is not so it will sink. If theidentifications provided by a user are overruled by experts, theusers trust level will sink, if it is confirmed by experts, the trustlevel will rise.

cont...




User Trust Level

Extensions

Alternative paths

Post conditions The users trust level has been adjusted based on feedback pro-vided.


Validation statement The users trust level corresponds to the quality of the identifica-tions provided.

Notes


Included in UseCase Check Identifications

Table 4: UC-ENV1.1-auth-02-V01 – User Trust Level

2.1.3 Store data

Store data

Use Case ID UC-ENV1.2-data-01-V02

Use Case Name Store data



Use Case Diagram

Status Planned


Goal Upload of data from external sources

Summary Data can be entered from external sources

Category

Actor All


Stakeholder


ENVIROFI Biodiversity Repository

Preconditions User is logged in UC-ENV1.1-auth-01-V01

Triggers User wishes to upload an occurrence or has selected bulk dataupload

Main success scenario Data successfully stored in the ENVIROFI Biodiversity Reposi-tory

cont...




Store data

Extensions Various types of data entry:• Upload data from mobile devices• Manually enter new data and information• Bulk upload data from existing sources (various formats)• Upload data from field-computers and mobile devices for

cases where this was not possible from the field

Alternative paths

Post conditions new data in the ENVIROFI Biodiversity Repository


Validation statement

Notes


Refines UseCase User provides new observation(s) to the system

Included in UseCase Provide Occurrence - Nature hobbyists & Advanced amateursInput Occurrences on PortalUpload Data

Table 5: UC-ENV1.2-data-01-V02 – Store data

2.1.4 Edit data

Edit data


Use Case Name Edit data



Use Case Diagram

Status Planned


Goal Edit data in the ENVIROFI Biodiversity Repository

Summary Existing occurrence records can be edited by the user

Category

Actor All

Primary Actor (initiates)

Stakeholder


ENVIROFI Biodiversity Repository

cont...




Edit data

Preconditions User is logged in UC-ENV1.1-auth-01-V01, data available UC-ENV1.2-data-01-V01

Triggers Edit functionality required from diverse user interaction use cases

Main success scenario The user has successfully modified and stored an existing datarecord

Extensions We may wish to provide more complex options to high end userswhile letting simpler users only edit basic fields

Alternative paths

Post conditions A modified record is stored in the ENVIROFI Biodiversity Repos-itory



Notes


Refines UseCase User alters existing observation(s)

Included in UseCase Administrate Portal on PortalAdministrate “my” Occurrences on PortalCheck IdentificationsUpload DataAdjust Identifications

Table 6: UC-ENV1.2-data-02-V02 – Edit data

2.1.5 Correct relations between concepts

Correct relations between concepts


Use Case Name Correct relations between concepts



Use Case Diagram

Status Planned


Goal Manually correct relations between concepts

Summary Manually correct relations between concepts in the ENVIROFIBiodiversity Ontology. In some cases, it may also be necessaryto introduce new relations

cont...




Correct relations between concepts

Category Data Input

Actor All


Stakeholder


ENVIROFI Biodiversity Ontology

Preconditions User is logged in UC-ENV1.1-auth-01-V01, information availableUC-ENV1.2-data-05-V01

Triggers requirement to edit relations from one of the scenarios

Main success scenario relations within the ENVIROFI Biodiversity Ontology are success-fully modified

Extensions create new relations in the ENVIROFI Biodiversity Ontology

Alternative paths

Post conditions A modified information record is available in the ENVIROFI Bio-diversity Ontology



Notes


Included in UseCase Edit information

Table 7: UC-ENV1.2-data-03-V01 – Correct relations between concepts

2.1.6 Access data

Access data


Use Case Name Access data



Use Case Diagram

Status Planned


Goal Provide access to ENVIROFI Biodiversity data

Summary the user can download biodiversity data via services for integra-tion into external applications

Category Data Input

cont...




Access data

Actor All


Stakeholder


ENVIROFI Biodiversity Repository for information on species

Preconditions User is logged in UC-ENV1.1-auth-01-V01; data available UC-ENV1.2-data-01-V01

Triggers user selects download data in the portal, or from a different UC

Main success scenario The user has received the required data resources via services.For the provision of data we foresee the use of SOS

Extensions It is possible to filter the data based on various criteria, i.e.species, location, time occurrence was provided.The data orig-inator is informed that their data has been accessed

Alternative paths

Post conditions The user has received all required data



Notes


Refines UseCase User downloads observations set from the portalUser accesses the existing observations

Included in UseCase Discovery and View on Portal

Table 8: UC-ENV1.2-data-04-V01 – Access data

2.1.7 Store information

Store information


Use Case Name Store information



Use Case Diagram

Status Planned


Goal Upload of information from external sources

Summary Information can be entered from external sources

cont...




Store information

Category

Actor All


Stakeholder




Triggers User wishes to upload an information related to habitats orspecies

Main success scenario Data successfully stored in the ENVIROFI Biodiversity Ontology

Extensions Various types of information entry:• Upload information from mobile devices• Manually enter new information• Upload information from existing sources (various formats)

Alternative paths

Post conditions new information in the ENVIROFI Biodiversity Ontology



Notes


Included in UseCase Generate Distributions

Table 9: UC-ENV1.2-data-05-V01 – Store information

2.1.8 Edit information

Edit information


Use Case Name Edit information



Use Case Diagram

Status Planned


Goal Edit information in the ENVIROFI Biodiversity Ontology

Summary Knowledge resources can be edited by the user

Category

cont...




Edit information

Actor All


Stakeholder




Triggers Edit functionality required from diverse user interaction use cases

Main success scenario The user has successfully modified and stored an existing knowl-edge record

Extensions various extensions will be required depending on the type of in-formation to be edited

Alternative paths

Post conditions A modified record is stored in the ENVIROFI Biodiversity Ontol-ogy



Notes


Includes UseCase Correct relations between concepts

Included in UseCase Administrate Portal on PortalProvide Feedback on Occurrences on PortalProvide Further Knowledge on Habitats and Species on PortalUpload Data

Table 10: UC-ENV1.2-data-06-V01 – Edit information

2.1.9 Access information

Access information


Use Case Name Access information



Use Case Diagram

Status Planned


Goal Provide access to ENVIROFI Biodiversity information

Summary the user can download biodiversity information via services forintegration into external applications

cont...




Access information

Category Data Input

Actor All


Stakeholder




Triggers user selects download information in the portal, or from a differentUC

Main success scenario The user has received the required information resources via ser-vices. For the provision of information we foresee the use of RDFencoding

Extensions It is possible to filter the information based on various criteria, i.e.type of information (relation), related to species.The informationoriginator is informed that their information has been accessed

Alternative paths

Post conditions The user has received all required information



Notes


Included in UseCase Local Interesting Information - Nature hobbyists and AdvancedamateursCreate and maintain ChecklistUpload DataGenerate Distributions

Table 11: UC-ENV1.2-data-07-V01 – Access information

2.1.10 Merge Concept List

Merge Concept List

Use Case ID UC-ENV1.3-mrg-01-V01

Use Case Name Merge Concept List



Use Case Diagram

Status Planned


cont...




Merge Concept List

Goal Merge concept lists

Summary In order to successfully merge data from different sources, wemust first merge and align the concepts used to describe thisdata. In this use case, based on various aspects of the 2 sources,we use semantic algorithms to align these concepts

Category

Actor Administrator


Stakeholder


ENVIROFI Biodiversity Ontology for quality assurance and provi-sion of knowledge on identification object

Preconditions User is logged in UC-ENV1.1-auth-01-V01, has proper rights,new concept list uploaded

Triggers concept merge triggered from portal

Main success scenario Concept lists have been successfully merged according to thefollowing methods:

• String Comparison• Phonetic comparison• Comparison of related concepts• Eliminate homonyms• Manual interference

Extensions

Alternative paths

Post conditions concept list successfully merged and harmonized with ENVIROFIBiodiversity Ontology



Notes


Included in UseCase Upload Data

Table 12: UC-ENV1.3-mrg-01-V01 – Merge Concept List

2.1.11 Merge Data

Merge Data


Use Case Name Merge Data



cont...




Merge Data

Use Case Diagram

Status Planned


Goal merge data from external sources to ENVIROFI BiodiversityRepository

Summary data resources from external sources will be merged into theENVIROFI Biodiversity Repository this merge will be performedbased on the concept lists corresponding to the data resource

Category Data Input

Actor Administrator


Stakeholder


ENVIROFI Biodiversity Ontology for quality assurance and provi-sion of knowledge on identification objectENVIROFI BiodiversityRepository for information on species sighted in the users vicinity

Preconditions User is logged in UC-ENV1.1-auth-01-V01, has proper rights,new data resource uploaded

Triggers user triggers data merge on portal

Main success scenario Data from an external resource has been successfully mergedinto the ENVIROFI Biodiversity Repository

• Alignment via concept mapping available in the ENVIROFIBiodiversity Ontology

• Alignment via additional information contained within thedata (i.e. species traits)

Extensions

Alternative paths

Post conditions External data successfully aligned and merged with ENVIROFIBiodiversity Repository



Notes



Table 13: UC-ENV1.3-mrg-02-V01 – Merge Data

2.1.12 Extract Concept List

Extract Concept List


cont...




Use Case Name Extract Concept List



Use Case Diagram

Status Planned


Goal The relevant concepts for merge are extracted from an occur-rence data resource

Summary In order to merge data resources from external sources, one mustfirst align and merge the concepts defining this data. This taskis performed in UC UC-ENV1.3-data-02-V01 Merge DataIn orderto perform this task the relevant concepts must first be extractedfrom the external data resource. this UC provides the conceptsfrom within the external data resource

Category Data Input

Actor Scientific Admin


Stakeholder



Preconditions User is logged in UC-ENV1.1-auth-01-V01, has proper rights,new data resource uploaded

Triggers user triggers extract concept list on portal

Main success scenario In order to merge data resources from external sources, one mustfirst identify, align and merge the concepts defining this data. Inorder to perform this task the relevant concepts must first be ex-tracted from the external data resource. this UC provides theconcepts from within the external data resource. In most cases,the concepts to be merged will be the species names. however,this also applies to other standardized attributes of the occur-rence records.

Extensions

Alternative paths

Post conditions A concept list as used in defining the external data resource isavailable for further processing



Notes

cont...







Table 14: UC-ENV1.3-mrg-03-V01 – Extract Concept List



2.1.13 Check occurrence record for plausibility

Check occurrence record for plausibility

Use Case ID UC-ENV1.4-sem-01-V01

Use Case Name Check occurrence record for plausibility



Use Case Diagram

Status Planned


Goal Check the plausibility of a reported species or habitat occurrencerecord

Summary An occurrence record is checked against the knowledge con-tained in the ENVIROFI Biodiversity Ontology.The plausibility ofthis occurrence record is returned to the user

Category Semantics

Actor All


Stakeholder



Preconditions User is logged in UC-ENV1.1-auth-01-V01, has provided an oc-currence record UC-ENV1.2-data-01-V01

Triggers user selects validate record

Main success scenario the occurrence record provided by the user is validated againstthe ENVIROFI Biodiversity Ontology by the following criteria:

• Spatial probability (i.e. Does this species fit into this biogeo-graphical region? Does it occur within the know distributionarea?)

• Temporal probability (i.e. Can it be observed at this time ofthe year?)

• Comparison with common mis-identifications (i.e. Provideuser with image of other types often confused with typeidentified - does the leaf of this species look like this?)

• Food Webs for related occurrences• Relationships between species and the habitats and

biotopes they occur in• Names and synonyms in other taxonomies (for merging

from other sources)• Identification Key information (A step-by-step list of ques-

tions allowing the user to identify the species)

The plausibility of the occurrence is returned to the user andstored with the occurrence record.

Extensions

cont...




Check occurrence record for plausibility

Alternative paths

Post conditions The plausibility of the occurrence record is known



Notes


Refines UseCase Service performs algebraic and logical operation on observationsUser alters existing observation(s)System assesses the quality of observations

Included in UseCase Provide Occurrence - Nature hobbyists & Advanced amateurs

Table 15: UC-ENV1.4-sem-01-V01 – Check occurrence record for plausibility

2.1.14 Provide feedback on occurrences in area

Provide feedback on occurrences in area


Use Case Name Provide feedback on occurrences in area



Use Case Diagram

Status Planned


Goal Provide user information on other interesting biodiversity in thevicinity

Summary Based on the users current location, information is provided oninteresting biodiversity in the area.The nature of this informationwill vary across user groups

Category Semantics

Actor All


Stakeholder



Preconditions User is logged in UC-ENV1.1-auth-01-V01, location is known

Triggers User selects additional information

cont...




Provide feedback on occurrences in area

Main success scenario Based on the users current location and request, relevant infor-mation pertaining to that area is providedThe type of informationoffered will vary with the users level of knowledge:

• Basic users such as school classes receive basic informa-tion on common biodiversity

• Semi-advanced users such as Nature hobbyists receive in-formation on biodiversity related to their field of interest

• Professional users can access additional background lay-ers such as watersheds and landcover data

Extensions In some cases the user may wish to perform this query for adifferent area than their current location. Examples of this areresearchers who will not have reception in the field, or hobbyistspreparing for their next weekend hike.

Alternative paths

Post conditions


Validation statement The user has received relevant additional information for the lo-cation selected

Notes


Refines UseCase Service performs algebraic and logical operation on observationsUser alters existing observation(s)

Included in UseCase Local Interesting Information - Nature hobbyists and Advancedamateurs

Table 16: UC-ENV1.4-sem-02-V01 – Provide feedback on occurrences in area

2.1.15 Provide Identification Key Information

Provide Identification Key Information


Use Case Name Provide Identification Key Information



Use Case Diagram

Status Planned


Goal Provide Identification Key Information

Summary Provide the user with relevant information from an IdentificationKeyThis can serve both identification purposes as well as providea support when navigating to the proper habitat or species name

cont...




Provide Identification Key Information

Category Semantics

Actor All


Stakeholder




Triggers user selects functionality utilizing identification key

Main success scenario Using the support of the information contained in the identifica-tion key, the user has successfully identified the species or habitatof interest.

Extensions In order to ease navigation within species taxonomies, especiallyon mobile devices with small displays, simple identification keyscan be used to help the user find the appropriate species

Alternative paths

Post conditions User has successfully found the species they were looking forbased on various characteristica



Notes Short note to Identification Keys: These are traditionally booksthat allow a user to successively home in on the species of inter-est through a series of successively refined questions on charac-teristica of the species that ultimately lead to the correct identifi-cation.Can be seen as a binary question tree.



Table 17: UC-ENV1.4-sem-03-V01 – Provide Identification Key Information

2.1.16 Provide feedback on dangerous occurrence

Provide feedback on dangerous occurrence


Use Case Name Provide feedback on dangerous occurrence



Use Case Diagram

Status Planned


cont...




Provide feedback on dangerous occurrence

Goal Provide user information with feedback on possible danger of thespecies identified

Summary Based on the species identified, information is provided on pos-sible dangers ensuing from this species, i.e. poisonous mush-rooms, plants that can burn the skin.

Category Semantics

Actor All


Stakeholder


ENVIROFI Biodiversity Ontology for information on identificationobject

Preconditions User is logged in UC-ENV1.1-auth-01-V01, location is known

Triggers User selects additional information

Main success scenario Based on the species identified, information is provided on pos-sible dangers ensuing from this species is provided to the user.This can be the fact that a plant is poisonous, allergenic, or insome other manner dangerous.

Extensions In some cases the user may wish to perform this query for aspecies without providing an occurrence record. Examples ofthis are researchers who will not have reception in the field, orhobbyists preparing for their next weekend hike.

Alternative paths

Post conditions


Validation statement The user has received relevant additional information for thespeciesselected

Notes


Refines UseCase Service performs algebraic and logical operation on observations


Table 18: UC-ENV1.4-sem-04-V01 – Provide feedback on dangerous occurrence

2.1.17 Check Identifications

Check Identifications


Use Case Name Check Identifications


cont...





Use Case Diagram

Status Planned


Goal Adjust occurrence records based on feedback from UC-ENV1.D-prt-05-V01 Provide Feedback on Occurrence

Summary Based on feedback from UC-ENV1.D-prt-05-V01 Provide Feed-back on Occurrence, occurrence records are adjusted. In mostcases, this only changes the identification, but could also pertainto the location of the occurrence.

Category Semantics

Actor All


Stakeholder


ENVIROFI Biodiversity Ontology for feedback on identificationobjectENVIROFI Biodiversity Repository List of registered userswith user profiles for user trust identification

Preconditions User is logged in UC-ENV1.1-auth-01-V01,

Triggers Adjust identifications selected

Main success scenario Based on feedback from UC-ENV1.D-prt-05-V01 Provide Feed-back on Occurrence, occurrence records are adjusted. In mostcases, this only changes the identification, but could also pertainto the location of the occurrence. The users trust level is integralin deciding which identification is most trustworthy. If a highlytrusted user provides feedback on an identification this is morelikely to be used than feedback from a user with a low trust level.The same holds true for the data provider, records from a dataprovider with a high trust level are unlikely to be adjusted, thosefrom a data provider with a low trust level are more likely to beadjusted.The user can also select which adjustments are to beperformed

cont...





Extensions An adjustment interval can be set. Then the system will automat-ically perform adjustments at this interval.

Alternative paths

Post conditions Occurrence records within the ENVIROFI Biodiversity Ontologyare adjusted based on feedback from UC-ENV1.D-prt-05-V01Provide Feedback on Occurrence,


Validation statement The user has received relevant additional information for thespeciesselected

Notes


Includes UseCase User Trust LevelEdit data


Included in UseCase Adjust Identifications

Table 19: UC-ENV1.4-sem-05-V01 – Check Identifications

2.1.18 Generate Habitat Distribution

Generate Habitat Distribution

Use Case ID UC-ENV1.5-dst-01-V01

Use Case Name Generate Habitat Distribution



Use Case Diagram

Status Planned


Goal Generate Habitat Distribution

Summary Based on existing data habitat distribution information is calcu-lated and stored in the ENVIROFI Biodiversity Ontology

Category Fusion

Actor Administrator


Stakeholder


ENVIROFI Biodiversity Ontology ENVIROFI Biodiversity Reposi-tory

cont...




Generate Habitat Distribution

Preconditions User is logged in UC-ENV1.1-auth-01-V01, has proper rights,habitat occurrence data is available

Triggers user selects generate habitat distribution

Main success scenario Based on habitat occurrence data available in the ENVIROFI Bio-diversity Repository (both points and polygons) as well as avail-able background data that has been imported to the Repository(i.e. Ortho-Images, Landcover), a new habitat distribution is gen-erated and stored in the ENVIROFI Biodiversity Ontology

Extensions

Alternative paths

Post conditions


Validation statement New habitat distribution information is available in the ENVIROFIBiodiversity Ontology

Notes




Table 20: UC-ENV1.5-dst-01-V01 – Generate Habitat Distribution

2.1.19 Generate Species Distribution

Generate Species Distribution

Use Case ID UC-ENV1.5-dst-02-V01

Use Case Name Generate Species Distribution



Use Case Diagram

Status Planned


Goal Create new species distribution information

Summary Based on existing species occurrence data together with variousbackground layers such as habitats and land cover, new speciesdistribution information is generated or existing species distribu-tion information is extended.

cont...




Generate Species Distribution

Category Fusion

Actor Administrator


Stakeholder


ENVIROFI Biodiversity Ontology ENVIROFI Biodiversity Reposi-tory

Preconditions User is logged in UC-ENV1.1-auth-01-V01, has proper rights,species occurrence data is available

Triggers user selects generate species distribution

Main success scenario The user selects the species to generate the distribution informa-tion forThe user selects the area the distribution information isto be generated forThe user selects the appropriate backgroundlayers such as habitats distribution or land cover to be used ingenerationThe system generates a new species distribution forthe selected species and stores it in the ENVIROFI BiodiversityOntology

Extensions The user may wish to adjust the results of the distribution gener-ation based on expert knowledge

Alternative paths

Post conditions


Validation statement A new or extended species distribution record is available fromthe ENVIROFI Biodiversity Ontology

Notes




Table 21: UC-ENV1.5-dst-02-V01 – Generate Species Distribution

2.1.20 Provide identification for image

Provide identification for image

Use Case ID UC-ENV1.6-ident-01-V01

Use Case Name Provide identification for image



Use Case Diagram

Status Planned

cont...




Provide identification for image


Goal Identify an image provided by a user

Summary A user provides an image of an individual plant or animal (prob-ably only a leaf or wing)The system suggests possible identifica-tions based on pattern recognition algorithms

Category Fusion

Actor All


Stakeholder


Preconditions User is logged in UC-ENV1.1-auth-01-V01, has provided an oc-currence image

Triggers user selects identify image

Main success scenario A user provides an image of an individual plant or animal (prob-ably only a leaf or wing)The system suggests possible identifica-tions based on pattern recognition algorithmsThe user can usethis identification for the reporting of the occurrence record

Extensions

Alternative paths

Post conditions


Validation statement The user has received information on what species the image isof

Notes


Refines UseCase User alters existing observation(s)System identifies the observed phenomena / environmental state


Table 22: UC-ENV1.6-ident-01-V01 – Provide identification for image



Figure 1: Use case UC-ENV1.6-ident-01-V01 Provide identification for image



2.1.21 Provide identification for sound

Provide identification for sound

Use Case ID UC-ENV1.6-ident-02-V01

Use Case Name Provide identification for sound



Use Case Diagram

Status Planned


Goal Provide identification for sound

Summary The user sees and hears a species that they can not directlyidentify. By provision of a short recording of the animals call, thesystem can suggest possible identifications

Category Fusion

Actor All


Stakeholder



Preconditions User is logged in UC-ENV1.1-auth-01-V01, has provided an oc-currence sound

Triggers user selects identify sound

Main success scenario The user has provided a sample of the animals call to the ENVI-ROFI SystemThe system compares this sound with the calls ofanimals stored in the ENVIROFI Biodiversity Ontology The sys-tem suggests possible identifications to the userThe user selectsthe appropriate identification for the occurrence record

Extensions

Alternative paths

Post conditions


Validation statement The user has received identification information based on thesound information provided

Notes


Refines UseCase User alters existing observation(s)System identifies the observed phenomena / environmental state

cont...




Provide identification for sound


Table 23: UC-ENV1.6-ident-02-V01 – Provide identification for sound

Figure 2: Use case UC-ENV1.6-ident-02-V01 Provide identification for sound



2.1.22 Create Checklist

Create Checklist

Use Case ID UC-ENV1.7-chkl-01-V01

Use Case Name Create Checklist



Use Case Diagram

Status Planned


Goal Create a species checklist

Summary In various scenarios, the user is provided with a checklist ofspecies or habitats to provide data on. Such checklists must becreated.

Category Data Input

Actor


Stakeholder


ENVIROFI Biodiversity Checklists ENVIROFI Biodiversity Ontol-ogy


Triggers The create checklist functionality triggered

Main success scenario A new checklist has been created and filled with species or habi-tats from the ENVIROFI Biodiversity OntologyIt should be possi-ble to create logical groupings between entries within this list foreasier navigation.Once the list has been completed, this list canbe assigned to various participant groups.

Extensions

Alternative paths

Post conditions A checklist is available within the ENVIROFI Biodiversity Check-lists



Notes

Author and date KS 2011-09-20

Included in UseCase Create and maintain Checklist

cont...




Create Checklist

Table 24: UC-ENV1.7-chkl-01-V01 – Create Checklist

2.1.23 Modify Checklist

Modify Checklist


Use Case Name Modify Checklist



Use Case Diagram

Status Planned


Goal An existing species checklist is modified

Summary In various scenarios, the user is provided with a checklist ofspecies or habitats to provide data on. Such checklists must bemodified and extended.

Category Data Input

Actor


Stakeholder


ENVIROFI Biodiversity Checklists ENVIROFI Biodiversity Ontol-ogy


Triggers The modify checklist functionality triggered

Main success scenario An existing checklist has been modified.

Extensions

Alternative paths

Post conditions A modified checklist is available within the ENVIROFI BiodiversityChecklists



Notes


Included in UseCase Create and maintain Checklist

cont...




Modify Checklist

Table 25: UC-ENV1.7-chkl-02-V01 – Modify Checklist

2.1.24 Delete Checklist

Delete Checklist


Use Case Name Delete Checklist



Use Case Diagram

Status Planned


Goal An existing species checklist is deleted

Summary In various scenarios, the user is provided with a checklist ofspecies or habitats to provide data on. Once they are no longerused, these checklists can also be deleted.

Category Data Input

Actor


Stakeholder


ENVIROFI Biodiversity Checklists


Triggers The delete checklist functionality triggered

Main success scenario An existing checklist has been deleted.care must be taken thatthis checklist is not currently in use by any user groups.

Extensions

Alternative paths

Post conditions The checklist is no longer available within the ENVIROFI Biodi-versity Checklists



Notes


Included in UseCase Create and maintain ChecklistAdministrate Portal on Portal

cont...




Delete Checklist

Table 26: UC-ENV1.7-chkl-03-V01 – Delete Checklist

2.1.25 Access Checklist

Access Checklist


Use Case Name Access Checklist



Use Case Diagram

Status Planned


Goal Access a species checklist

Summary In various scenarios, the user is provided with a checklist ofspecies or habitats to provide data on. The user must be ableto access the checklist on his survey device

Category Data Input

Actor


Stakeholder




Triggers The access checklist functionality triggered

Main success scenario The user is provided with a checklist on their survey device. De-pending on the groups and activities the user is registered fordifferent checklists will be made available; the user can selectone or several for current use.Information for all the species orhabitat types listed will be provided to the user, optionally thiscan be downloaded to mobile survey devices for use in areaswhere there is no receptionThe list of species or habitat typesis integrated into the user interface for easy identification of theoccurrences to be reported.

cont...




Access Checklist

Extensions

Alternative paths

Post conditions A checklistfrom the ENVIROFI Biodiversity Checklists is madeavailable to the user on their survey device



Notes


Included in UseCase Fill Survey ChecklistProvide Invasive Occurrence

Table 27: UC-ENV1.7-chkl-04-V01 – Access Checklist

2.1.26 Provide Checklists

Provide Checklists


Use Case Name Provide Checklists



Use Case Diagram

Status Planned


Goal Provide a list of all checklists available to the user

Summary In various scenarios, the user is provided with a checklist ofspecies or habitats to provide data on. The user must be ableto select one or more checklists on his survey device

Category Data Input

Actor


Stakeholder




Triggers The provide checklists functionality triggered

Main success scenario The user is provided with an overview of the checklists availableto them. Depending on the groups and activities the user is regis-tered for different checklists will be made available; the user canselect one or several for current use.

cont...




Provide Checklists

Extensions

Alternative paths

Post conditions The user can select a checklistfrom the ENVIROFI BiodiversityChecklists for use



Notes



Table 28: UC-ENV1.7-chkl-05-V01 – Provide Checklists

2.1.27 Provide Occurrence - Teachers and pupils

Provide Occurrence - Teachers and pupils

Use Case ID UC-ENV1.A-mob-01-V01

Use Case Name Provide Occurrence - Teachers and pupils



Use Case Diagram

Status Planned


Goal Provide Occurrence Record from Mobile Device

Summary The user sees an interesting plant or animal they wish to pro-vide an occurrence record of. The species is photographed andidentified. After some QA steps assuring that the identification iscorrect, the occurrence record is uploaded

Category Data Input

Actor Teachers and pupils


Stakeholder


ENVIROFI Biodiversity Ontology for quality assurance and provi-sion of knowledge on identification objectENVIROFI BiodiversityRepository for storing the species occurrence record


Triggers The user selects “provide occurrence” on mobile app.

cont...




Provide Occurrence - Teachers and pupils

Main success scenario 1. The user has successfully photographed the species or habitatto be provided2. The location of the user has been determinedbased on the location of their mobile device.3. The user has suc-cessfully identified the species or habitat to be provided a. If theuser requires support in the identification process, informationfrom an identification key is provided. The user is led throughthis information on a step by step basis. - UC-ENV1.4-sem-03-V01 b. For selected species, automatic identification based onan image of a single leaf or insect wing will be possible. Thisimage must be provided in addition to the image of the entire in-dividual. Feedback on likely species will be returned based onpattern recognition as well as other background information suchas habitats. - UC-ENV1.6-fus-01-V01 & UC-ENV1.6-fus-02-V01c. If the quality assurance routines in ENVIROFI find the oc-currence record not plausible, feedback is given to the user andthe identification is adjusted accordingly. - UC-ENV1.4-sem-01-V014. If the species being reported is known to be poisonousor otherwise dangerous, the user is given a warning message -UC-ENV1.4-sem-02-V015. The occurrence record is uploaded tothe ENVIROFI biodiversity repository for further processing anddissemination. - UC-ENV1.2-data-01-V01

Extensions 1. The same identification and upload functionality will also beavailable from the web portal (Scenario D)

Alternative paths

Post conditions A new occurrence record is available in the ENVIROFI biodiver-sity repository


Validation statement A new occurrence record is available in the ENVIROFI biodiver-sity repository and can be clearly correlated with this user

Notes

Author and date KS-UBA, 2011-07-20

Maps to Requirement Determine feature of interest

Refines UseCase Support user-specific application behaviourUser provides new observation(s) to the system

Table 29: UC-ENV1.A-mob-01-V01 – Provide Occurrence - Teachers and pupils

2.1.28 Local Interesting Information - Teachers and pupils

Local Interesting Information - Teachers and pupils

Use Case ID UC-ENV1.A-mob-02-V01

Use Case Name Local Interesting Information - Teachers and pupils



cont...





Use Case Diagram

Status Planned


Goal Provide information on interesting species in the users area

Summary The user is out in the woods and wonders what could be of in-terest in this area. Based on the userâC™s location, the systemprovides information on interesting species or habitats known tobe in the users vicinity at this time of year.

Category Information Provision

Actor Teachers and pupils

Primary Actor (initiates) Teachers and pupils

Stakeholder



Preconditions The user has installed app on mobile device successfully and isa registered user.

Triggers The user selects “Provide local information” on mobile app.

Main success scenario • The user’s location is clearly identified based on the loca-tion of their mobile device

• Information on interesting species that are known to be inthe vicinity of the user is provided including images UC-ENV1.4-sem-02-V01

Extensions 1. Based on the user’s profile, this information can be tailoredto areas of interest specific to the user. I.e. a birdwatcher canconfigure their profile to restrict the information received to birds.

Alternative paths -

Post conditions The user has a better understanding of the biodiversity of thearea he is in.



Notes There are no special notes.Internal remark: UC-ENV1.A-mob-02-V01.doc



Refines UseCase Service performs algebraic and logical operation on observationsSupport user-specific application behaviourSystem presents user with information on his/her surroundingsUser accesses the existing observations

cont...




Table 30: UC-ENV1.A-mob-02-V01 – Local Interesting Information - Teachers and pupils



2.1.29 Provide Occurrence - Nature hobbyists & Advanced amateurs

Provide Occurrence - Nature hobbyists & Advanced ama-teurs

Use Case ID UC-ENV1.B-mob-01-V01

Use Case Name Provide Occurrence - Nature hobbyists & Advanced amateurs



Use Case Diagram

Status Planned


Goal Provide Occurrence Record

Summary The user sees an interesting plant or animal they wish to pro-vide an occurrence record of. The species is photographed andidentified. After some QA steps assuring that the identification iscorrect, the occurrence record is uploaded

Category Data Input

Actor Nature hobbyists & Advanced amateurs

Primary Actor (initiates) Nature hobbyists & Advanced amateurs

Stakeholder



Preconditions The user has installed app on mobile device successfully and isa registered user. UC-ENV1.1-auth-01

Triggers The user selects “provide occurrence” on mobile app.

Main success scenario 1. The user has successfully photographed the species or habitatto be provided2. The location of the user has been determinedbased on the location of their mobile device.3. The user has suc-cessfully identified the species or habitat to be provideda. If theuser requires support in the identification process, informationfrom an identification key is provided. The user is led throughthis information on a step by step basis. see UC-ENV1.4-sem-03-V01b. For selected species, automatic identification basedon an image of a single leaf or insect wing will be possible. Thisimage must be provided in addition to the image of the entire indi-vidual. Feedback on likely species will be returned based on pat-tern recognition as well as other background information such ashabitats. see UC-ENV1.6-fus-01-V01, UC-ENV1.6-fus-02-V01c.If the quality assurance routines in ENVIROFI find the occurrencerecord not plausible, feedback is given to the user and the iden-tification is adjusted accordingly. see UC-ENV1.4-sem-01-V014.If the species being reported is known to be poisonous or other-wise dangerous, the user is given a warning message. see UC-ENV1.4-sem-02-V015. The occurrence record is uploaded to theENVIROFI biodiversity repository for further processing and dis-semination. If this is not possible due to connectivity problems,the occurrence record will be stored for later provision. see UC-ENV1.2-data-01-V01

Extensions 1. The same identification and upload functionality will also beavailable from the web portal (Scenario D)2. Occurrence recordthat could not be provided from the field due to connectivity prob-lems and have been stored on the mobile device can be providedat a later time.

cont...




Provide Occurrence - Nature hobbyists & Advanced ama-teurs

Alternative paths




Notes


Includes UseCase Check occurrence record for plausibilityProvide Identification Key InformationProvide identification for imageProvide identification for soundStore dataProvide feedback on dangerous occurrence




Table 31: UC-ENV1.B-mob-01-V01 – Provide Occurrence - Nature hobbyists & Advanced amateurs



.png

Figure 3: Use case UC-ENV1.B-mob-01-V01 Provide Occurrence - Nature hobbyists & Advancedamateurs



2.1.30 Local Interesting Information - Nature hobbyists and Advanced amateurs

Local Interesting Information - Nature hobbyists and Ad-vanced amateurs


Use Case Name Local Interesting Information - Nature hobbyists and Advancedamateurs



Use Case Diagram

Status Planned



Summary The user is out in the woods and wonders what could be of in-terest in this area. Based on the userâC™s location, the systemprovides information on interesting species or habitats known tobe in the users vicinity at this time of year.

Category Data Input

Actor Nature hobbyists and Advanced amateurs

Primary Actor (initiates) Nature hobbyists and Advanced amateurs

Stakeholder




Triggers The user selects “Provide local information” on mobile app.

Main success scenario 1. The user’s location is clearly identified based on the locationof their mobile device2. Information on interesting species thatare known to be in the vicinity of the user is provided includingimages. see UC-ENV1.4-sem-02-V01

Extensions 1. Based on the user’s profile, this information can be tailoredto areas of interest specific to the user. I.e. a birdwatcher canconfigure their profile to restrict the information received to birds.

Alternative paths -

Post conditions The user has a better understanding of the biodiversity of thearea he is in.

cont...




Local Interesting Information - Nature hobbyists and Ad-vanced amateurs



Notes While this use case is very similar to UC-ENV1.A-mob-03-V01,the level of complexity of information provided to the user will bequite different depending on the user group. While the informa-tion provided in scenario A will be tailored to the limited under-standing of school classes, in scenario B we assume more edu-cated users, that can be provided with more detailed information


Includes UseCase Provide feedback on occurrences in areaAccess information

Maps to Requirement Determine feature of interestIntegrate Web map servicesEnable map selectionProvide component for occurrence accessEnable security and rights managementAssure sufficiently short response timeOptimise battery lifeSupport integration of meta-informationSupport information modellingProvide location informationProvide topic informationSupport different data typesPublish interfacesProvide User Interface with Location selection.Enable user management

Refines UseCase Service performs algebraic and logical operation on observationsSupport user-specific application behaviourSystem presents user with information on his/her surroundingsUser accesses the existing observations

Table 32: UC-ENV1.B-mob-02-V01 – Local Interesting Information - Nature hobbyists and Advancedamateurs



Figure 4: Use case UC-ENV1.B-mob-02-V01 Local Interesting Information - Nature hobbyists andAdvanced amateurs



2.1.31 Fill Survey Checklist

Fill Survey Checklist


Use Case Name Fill Survey Checklist



Use Case Diagram

Status Planned


Goal The user provides occurrence data based on a checklist

Summary The survey participant is provided a list of species and habitattypes to find. Occurrence information on these species and habi-tat types is provided.

Category Data Input

Actor NatureHobbyist


Stakeholder NatureGuide




Triggers The user initiates the survey functionality

Main success scenario In biodiversity surveys, the participants are usually given a listof species to locate and provide information on. This list is pro-vided to the user on the mobile device. When the user locates aspecies or habitat type on the list, the current location as well asan image of the occurrence is provided, as well as an indication ofwhich species or habitat type from the survey list has been iden-tified.The data provision process continues as described in theincluded use case UC-ENV1.B-mob-01-V01 Provide Occurrence

Extensions

Alternative paths

Post conditions A completed survey list is available within the ENVIROFI Biodi-versity Repository



Notes

cont...




Fill Survey Checklist


Includes UseCase Provide Occurrence - Nature hobbyists & Advanced amateursAccess ChecklistProvide Checklists

Table 33: UC-ENV1.B-mob-03-V01 – Fill Survey Checklist

Figure 5: Use case UC-ENV1.B-mob-03-V01 Fill Survey Checklist



2.1.32 Provide Invasive Occurrence

Provide Invasive Occurrence


Use Case Name Provide Invasive Occurrence



Use Case Diagram

Status Planned


Goal The user provides occurrence data on invasive and allergenicspecies based on a checklist

Summary The survey participant is provided a list of invasive and allergenicspeciesto find. Occurrence information on these species is pro-vided.

Category Data Input

Actor NatureHobbyist


Stakeholder NatureGuide




Triggers The user initiates the survey functionality

Main success scenario In order to track invasive and allergenic species, checklist can bea valuable support as many of these species, especially new in-vasives, are not commonly known. By providing information onthese species to the user on their mobile device, it is easier forthe user to identify them.When the user locates a species on thelist, the current location as well as an image of the occurrenceis provided, as well as an indication of which species from thechecklist has been identified.The data provision process contin-ues as described in the included use case UC-ENV1.B-mob-01-V01 Provide Occurrence

cont...




Provide Invasive Occurrence

Extensions

Alternative paths

Post conditions Information on allergenic and invasive species from the checklistis available within the ENVIROFI Biodiversity Repository



Notes


Includes UseCase Provide Occurrence - Nature hobbyists & Advanced amateursAccess ChecklistProvide Checklists

Table 34: UC-ENV1.B-mob-05-V01 – Provide Invasive Occurrence

Figure 6: Use case UC-ENV1.B-mob-05-V01 Provide Invasive Occurrence



2.1.33 Create and maintain Checklist

Create and maintain Checklist

Use Case ID UC-ENV1.B-prt-04-V01

Use Case Name Create and maintain Checklist



Use Case Diagram

Status Planned


Goal A checklist is created for use in a survey

Summary In order to provide participants on a survey with checklists onwhich species and habitat types to identify and record, such alist must be created and maintained. The same holds true forinvasive or allergenic species.

Category Data Input

Actor NatureGuide


Stakeholder


ENVIROFI Biodiversity ChecklistsENVIROFI Biodiversity Ontol-ogy


Triggers The user initiates the create checklist functionality

Main success scenario In biodiversity surveys, the participants are usually given a listof species and habitat types to locate and provide informationon. This list must first be created by a survey advisor or natureguide. The nature guide can select various species and habi-tat types from the species and habitat lists contained within theENVIROFI Biodiversity Ontology. It should be possible to createlogical groupings between entries within this list for easier naviga-tion.Once the list has been completed, this list can be assignedto various participant groups.

Extensions In addition to the creation of lists, it must be possible to copy,update and delete existing lists.

Alternative paths

Post conditions A survey list is available within the ENVIROFI Biodiversity Check-lists


cont...




Create and maintain Checklist


Notes


Includes UseCase Delete ChecklistCreate ChecklistModify ChecklistAccess information

Table 35: UC-ENV1.B-prt-04-V01 – Create and maintain Checklist



Figure 7: Use case UC-ENV1.B-prt-04-V01 Create and maintain Checklist



2.1.34 Assess Background material - Researcher

Assess Background material - Researcher

Use Case ID UC-ENV1.C-mob-01-V01

Use Case Name Assess Background material - Researcher



Use Case Diagram

Status Planned


Goal Provide the qualified user with relevant background information.

Summary The qualified user is provided with relevant background informa-tion. What information is provided will depend on the area ofinterest of the user, that can be based either on the current loca-tion of the mobile device or also on coordinates provided by theuser. A list of available topics will be provided to the user, whichcan then be viewed.


Actor Researcher

Primary Actor (initiates) Researcher

Stakeholder



Preconditions The user has installed app on mobile device and is successfullyregistered.

Triggers The user selects “Assess Background material” on mobile app.

Main success scenario 1. The user has selected a region of interest. There are 2 op-tions for the provision of this locational informationa. Region ofinterest based on current locationb. Region of interest extendedby input of coordinates2. The user is provided with a list of avail-able background material (“topics”) for the specified area of inter-est UC-ENV1.4-sem-02-V01 3. The user has selected a specifictopic area from the available background information4. The userhas viewed information on the available background informationfrom the selected topic area. Depending on the type of infor-mation selected, this information will be presented to the user indifferent forms: UC-ENV1.2-data-04-V01a. For spatial informa-tion such as the coverage of a specific habitat, this informationwill be provided to the user in the form of mapsb. For non-spatialinformation, a more tabular or tree form or representation will beused (i.e. for species lists)

cont...




Assess Background material - Researcher

Extensions

Alternative paths

Post conditions


Validation statement The user has obtained the required information

Notes



Refines UseCase Support user-specific application behaviour

Table 36: UC-ENV1.C-mob-01-V01 – Assess Background material - Researcher

2.1.35 Get local and regional check lists - Researcher

Get local and regional check lists - Researcher


Use Case Name Get local and regional check lists - Researcher



Use Case Diagram

Status Planned


Goal Provide the qualified user with relevant local and regional checklists on species and habitats.

Summary The qualified user is provided with relevant local and regionalcheck lists on species and habitats. What information is providedwill depend on the area of interest of the user, that can be basedeither on the current location of the mobile device or also on coor-dinates provided by the user. The user can then specify specificspecies or habitats, as well as data quality requirements; a cus-tomised checklist providing additional information on the entriesselected will be generated based on these requirements.


Actor Researcher


Stakeholder



cont...




Get local and regional check lists - Researcher

Preconditions The user has installed app on mobile device and is successfullyregistered.

Triggers The user selects “Get Checklists” on mobile app.

Main success scenario 1. The user has selected a region of interest. There are 2 optionsfor the provision of this locational informationa. Region of inter-est based on current locationb. Region of interest extended byinput of coordinates2. The user is provided with a list of availablelists of species and habitats for the specified area of interest3.The user has selected a specific species and/or habitats fromthe available background information4. The user has specifiedthe required level of data quality for their purpose5. A customchecklist is generated for the user. It is possible to store thischecklist for future use.6. The user has access to the customchecklist. If additional information on a species or habitat is avail-able (i.e. traits, description, threat status, protection status, etc.),this information can also be accessed - UC-ENV1.2-data-04-V01

Extensions 1. Sharing custom checklists with other users.

Alternative paths

Post conditions


Validation statement The user has obtained the required information

Notes



Refines UseCase Support user-specific application behaviourUser accesses the existing observations

Table 37: UC-ENV1.C-mob-02-V01 – Get local and regional check lists - Researcher

2.1.36 Provide Occurrence - Researcher

Provide Occurrence - Researcher


Use Case Name Provide Occurrence - Researcher



Use Case Diagram

Status Planned



cont...





Summary The user sees a species or habitat they wish to provide an oc-currence record of. The species or habitat is photographed andidentified. After some QA steps assuring that the identification iscorrect, the occurrence record is uploaded

Category Data Input

Actor Researcher


Stakeholder



Preconditions The user has installed app on mobile device successfully and isa registered user.

Triggers The user selects “Provide occurrence” on mobile app.

Main success scenario 1. The user has successfully photographed the species or habitatto be provided2. The location of the user has been determinedbased on the location of their mobile device.3. The user has suc-cessfully identified the species or habitat to be provideda. If theuser requires support in the identification process, informationfrom an identification key is provided. The user is led through thisinformation on a step by step basis. - UC-ENV1.4-sem-03-V01b.For selected species, automatic identification based on an imageof a single leaf or insect wing will be possible. This image must beprovided in addition to the image of the entire individual. Feed-back on likely species will be returned based on pattern recog-nition as well as other background information such as habitats.UC-ENV1.6-fus-01-V01 & UC-ENV1.6-fus-02-V01c. If the qualityassurance routines in ENVIROFI find the occurrence record notplausible, feedback is given to the user and the identification isadjusted accordingly. - UC-ENV1.4-sem-01-V014. The user hasprovided additional information on the occurrence.5. The occur-rence record is uploaded to the ENVIROFI biodiversity repositoryfor further processing and dissemination. If this is not possibledue to connectivity problems, the occurrence record will be storedfor later provision. UC-ENV1.2-data-01-V01

cont...




Extensions 1. The same identification and upload functionality will also beavailable from the web portal (Scenario D)2. Occurrence recordthat could not be provided from the field due to connectivity prob-lems and have been stored on the mobile device can be providedat a later time. UC-ENV1.2-data-01-V01

Alternative paths




Notes There are no special notes.




Table 38: UC-ENV1.C-mob-03-V01 – Provide Occurrence - Researcher

2.1.37 Validate Occurrence - Researcher

Validate Occurrence - Researcher


Use Case Name Validate Occurrence - Researcher



Use Case Diagram

Status Planned


Goal Validate Occurrence Record

Summary The user sees a species or habitat occurrence record of. Thespecies or habitat they wish to comment on. Based on a regionand topic of interest, the user is provided with all correspondingoccurrence records available. The user can select an individualoccurrence record and both validate the existing information aswell as providing additional information to this record. This infor-mation can either be uploaded directly or stored for later uploadwhen connectivity is possible.

cont...





Category Data Validation

Actor Researcher


Stakeholder




Triggers The user selects “Validate occurrence” on mobile app.

Main success scenario 1. The location of the user has been determined based on thelocation of their mobile device.2. The user has successfully se-lected the topic areas (Species or habitats) of interest3. The userhas been provided with all available occurrence records corre-sponding to the selection criteria provided4. The user has pro-vided validation information and/or additional information on theoccurrence record. This can include information on other inter-esting occurrences in the area.5. The validated and extended oc-currence record is uploaded to the ENVIROFI biodiversity repos-itory for further processing and dissemination. If this is not pos-sible due to connectivity problems, the occurrence record will bestored for later provision. If additional knowledge is provided, thisis uploaded to the ENVIROFI Biodiversity Ontology

Extensions 1. The same identification and upload functionality will also beavailable from the web portal (Scenario D)2. Occurrence vali-dation records that could not be provided from the field due toconnectivity problems and have been stored on the mobile de-vice can be provided at a later time.

Alternative paths

Post conditions A validated or extended occurrence record is available in the EN-VIROFI biodiversity repository


Validation statement A validated or extended occurrence record is available in the EN-VIROFI biodiversity repository and can be clearly correlated withthis user

Notes



Refines UseCase Support user-specific application behaviourUser alters existing observation(s)

cont...




Table 39: UC-ENV1.C-mob-04-V01 – Validate Occurrence - Researcher

2.1.38 Register User on Portal

Register User on Portal

Use Case ID UC-ENV1.D-prt-01-V01

Use Case Name Register User on Portal



Use Case Diagram

Status Planned


Goal Register a new user on the portal and configure their profile.

Summary The user opens the ENVIROFI Biodiversity Portal. Creates a newuser and configures their profile. Registered users can modifytheir profile


Actor All


Stakeholder



Preconditions

Triggers The user opens the ENVIROFI Biodiversity Portal and selects“Register user”

Main success scenario 1. A new user is registered2. A user has configured their profile

Extensions 1. An existing user has modified their profile

Alternative paths

Post conditions



Notes


Includes UseCase Login User

cont...




Register User on Portal

Table 40: UC-ENV1.D-prt-01-V01 – Register User on Portal

2.1.39 Discovery and View on Portal

Discovery and View on Portal


Use Case Name Discovery and View on Portal



Use Case Diagram

Status Planned


Goal Show data and information available in ENVIROFI BiodiversityPortal to users.

Summary The user opens the ENVIROFI Biodiversity Portal. The userspecifies the type of data they are interested in. This data isdisplayed to the user as maps as well as in tabular form as re-quested. In addition, further available knowledge on the habitatsand species can be requested.


Actor All


Stakeholder



Preconditions none

Triggers The user opens the ENVIROFI Biodiversity Portal

Main success scenario 1. The user can search for data a. By species or species group b.By location c. By data provider2. The user can view occurrencedata in the following forms: a. Tabular form b. Map3. The usercan view further species information

Extensions

Alternative paths

Post conditions


cont...




Discovery and View on Portal


Notes


Includes UseCase Access data

Refines UseCase User accesses the existing observationsUser interactively explores the existing observations

Table 41: UC-ENV1.D-prt-02-V01 – Discovery and View on Portal



Figure 8: Use case UC-ENV1.D-prt-02-V01 Discovery and View on Portal



2.1.40 Input Occurrences on Portal

Input Occurrences on Portal


Use Case Name Input Occurrences on Portal



Use Case Diagram

Status Planned


Goal Allow a user to provide biodiversity occurrence records via theportal

Summary The user opens the ENVIROFI Biodiversity Portal and logs in.The user provides occurrence data including images and loca-tional information. Once the occurrence data has been validatedit will be uploaded to the ENVIROFI Biodiversity Repository

Category Data Input

Actor All


Stakeholder



Preconditions The user has been successfully logged on to the system - UC-ENV1.1-auth-01-V01

Triggers The user opens the ENVIROFI Biodiversity Portal and selects“Input Occurrences”

Main success scenario 1. The user provides an image of the occurrence to be provided2.The user provides identification information on the occurrence tobe provided3. The user provides geospatial information on theoccurrence to be provided. Depending on the type of occurrencebeing provided, this information can take the following forms: a.Points for the location of an individual b. Polygons for the locationand extent of a habitat or a population4. The occurrence recordprovided is validated against the information in the ENVIROFIBiodiversity Ontology a. If there are doubts as to the validity ofthe occurrence record being provided, these are returned to theuser with a request for revision of the information to be provided5.The occurrence record is uploaded to the ENVIROFI biodiversityrepository for further processing and dissemination.

cont...




Input Occurrences on Portal

Extensions

Alternative paths




Notes


Includes UseCase Store data

Refines UseCase User provides new observation(s) to the system

Table 42: UC-ENV1.D-prt-03-V01 – Input Occurrences on Portal



Figure 9: Use case UC-ENV1.D-prt-03-V01 Input Occurrences on Portal



2.1.41 Administrate “my” Occurrences on Portal

Administrate “my” Occurrences on Portal


Use Case Name Administrate “my” Occurrences on Portal



Use Case Diagram

Status Planned


Goal Allow a user to administrate biodiversity occurrence records pro-vided by them via the portal

Summary The user can view, modify and share the occurrence data (includ-ing images and locational information) he/she provided . In addi-tion, it is possible to configure competitions within certain usageareas. This will allow users to compare the quality and quantityof occurrence records provided with other users.


Actor All


Stakeholder


ENVIROFI Biodiversity Ontology for quality assurance and provi-sion of knowledge on identification object ENVIROFI BiodiversityRepository for information on species sighted in the users vicinity


Triggers The user opens the ENVIROFI Biodiversity Portal and selects“Administrate My Occurrences”

Main success scenario • The user opens the ENVIROFI Biodiversity Portal and logsin.

• The user can filter and view all occurrence records theyhave provided in the following forms: a. Maps (includingvarious available background layers such as habitats) b. Ta-bles (displaying all information provided together with thespecies occurrence)

• The user can select an individual occurrence record formodification. The user can then perform the following modi-fications: - UC-ENV1.2-data-02-V01 a. Modify identificationb. Modify location c. Modify Image d. Make occurrencerecord openly available

• In addition to making an occurrence record openly avail-able, it is also possible to only expose the record to selectedfriends also registered on the portal. - UC-ENV1.2-data-02-V01 4.

• If a user is taking part in a competition on the ENVIROFIportal, it is possible to see the users ranking amongst allparticipating users.

Extensions

cont... of 91Copyright © 2011 ENVIROFI Consortium



Administrate “my” Occurrences on Portal

Alternative paths

Post conditions A modified occurrence record is available in the ENVIROFI biodi-versity repository


Validation statement A modified occurrence record is available in the ENVIROFI biodi-versity repository

Notes (Denis) The “competition” part in summary appears to be from adirrerent use case. Don’t see how it fits here.


Includes UseCase Edit data

Maps to Requirement Visualize observations on interactive mapVisualize observationsVisualize observations in interactive tables


Table 43: UC-ENV1.D-prt-04-V01 – Administrate “my” Occurrences on Portal

Figure 10: Use case UC-ENV1.D-prt-04-V01 Administrate “my” Occurrences on Portal



2.1.42 Provide Feedback on Occurrences on Portal

Provide Feedback on Occurrences on Portal


Use Case Name Provide Feedback on Occurrences on Portal



Use Case Diagram

Status Planned


Goal Allow a user to provide feedback on occurrence records availablewithin ENVIROFI

Summary The user opens the ENVIROFI Biodiversity Portal and logs in.The user browses through existing occurrence information andidentifies an error. The user provides what they consider to bethe proper information for the occurrence record. Based on theusers ranking, as well as inputs received from other users, thisinformation is then added to the occurrence record.


Actor All


Stakeholder


List of registered users with user profilesENVIROFI BiodiversityOntology for quality assurance and provision of knowledge onidentification objectENVIROFI Biodiversity Repository for infor-mation on species sighted in the users vicinity

Preconditions The user logged UC-ENV1.1-auth-01-V01; The user is viewing -UC-ENV1.D-prt-02-V01

Triggers The user opens the ENVIROFI Biodiversity Portal and selects“Provide Feedback on Occurrences”

Main success scenario 1. The user selects a specific occurrence record and providesalternative entries for: a. Identification b. Location c. Image d.Additional information provided2. If a user finds a questionableoccurrence record, but does not know the correct information tobe provided, the user can just mark the record as questionable.3.If the user finds an offensive occurrence record (IâC™m sureweâC™ll soon have occurrence of pretty naked girls), the recordcan be immediately blocked.

cont...




Provide Feedback on Occurrences on Portal

Extensions

Alternative paths

Post conditions A modified occurrence record is available in the ENVIROFI biodi-versity repository


Validation statement A modified occurrence record is available in the ENVIROFI biodi-versity repository

Notes


Includes UseCase Edit information


Table 44: UC-ENV1.D-prt-05-V01 – Provide Feedback on Occurrences on Portal

Figure 11: Use case UC-ENV1.D-prt-05-V01 Provide Feedback on Occurrences on Portal



2.1.43 Provide Further Knowledge on Habitats and Species on Portal

Provide Further Knowledge on Habitats and Species on Por-tal


Use Case Name Provide Further Knowledge on Habitats and Species on Portal



Use Case Diagram

Status Planned


Goal Allow a user to provide further knowledge on habitats andspecies

Summary The user opens the ENVIROFI Biodiversity Portal and logs in.The user browses through existing species and habitat informa-tion and selects a habitat or species type to be annotated. Theuser provided further information for storage in the ENVIROFIBiodiversity Ontology.

Category Data Input

Actor All


Stakeholder


List of registered users with user profilesENVIROFI BiodiversityOntology for quality assurance and provision of knowledge onidentification object


Triggers The user opens the ENVIROFI Biodiversity Portal and selects“Provide Knowledge on Habitats and Speci

Main success scenario 1. The user browses through the available knowledge resourceson habitats and species 2. The user selects a specific habitat orspecies they wish to provide information on 3. The user selectsthe type of information they wish to provide. This can be one ofthe following: a. Common names b. Common mis-identificationc. Species Traits d. Phenology e. Associations between speciesf. Medical usages g. Recipes4. The user provides the relevantinformation5. The information provided is stored in the ENVIROFIBiodiversity Ontology

cont...




Provide Further Knowledge on Habitats and Species on Por-tal

Extensions 1. The knowledge record provided also stores the users ranking.This will determine to what extent this piece of knowledge will befurther utilized within ENVIROFI

Alternative paths

Post conditions An extended knowledge record is available in the ENVIROFI Bio-diversity Ontology


Validation statement An extended knowledge record is available in the ENVIROFI Bio-diversity Ontology

Notes


Includes UseCase Edit information


Table 45: UC-ENV1.D-prt-06-V01 – Provide Further Knowledge on Habitats and Species on Portal

Figure 12: Use case UC-ENV1.D-prt-06-V01 Provide Further Knowledge on Habitats and Species onPortal



2.1.44 Administrate Portal on Portal

Administrate Portal on Portal


Use Case Name Administrate Portal on Portal



Use Case Diagram

Status Planned


Goal Allow an administrator to configure users as well as certain portalfunctionality

Summary The administrator logs on to the system. Once clearly identified,the administrator can configure new users as well as assigningranks to new and existing users. Competitions, based on check-lists and showing which participant has found the most speciesfrom the list, can be configured within the portal. Offensive datacan be blocked.


Actor Administrators

Primary Actor (initiates) Administrators

Stakeholder


• List of registered users with user profiles• ENVIROFI Biodiversity Ontology for quality assurance and

provision of knowledge on identification object.

Preconditions The user has been successfully logged on to the system anddetermined to have administration rights

Triggers The user opens the ENVIROFI Biodiversity Portal and selectsAdministrate Portal

Main success scenario • The user can configure new users. - UC-ENV1.1-auth-01-V01

• The user can change the rank of new and existing users-UC-ENV1.1-auth-01-V01

• The user can block records that are deemed offensive - UC-ENV1.2-data-02-V01 & UC-ENV1.2-data-06-V01

• The user can delete checklists no longer in use - UC-ENV1.7-checklist-03-V01

• The user can create checklists and configure them for vari-ous groups to use in surveys or competitions

cont...




Administrate Portal on Portal

Extensions

Alternative paths

Post conditions An extended knowledge record is available in the ENVIROFI Bio-diversity Ontology



Notes


Includes UseCase Login UserDelete ChecklistEdit dataEdit information

Maps to Requirement Manage trust levels for users

Refines UseCase Administrate Portal

Table 46: UC-ENV1.D-prt-07-V01 – Administrate Portal on Portal

2.1.45 Login

Login


Use Case Name Login



Use Case Diagram

Status Planned


Goal Login an existing user in the system

Summary The user opens the ENVIROFI Biodiversity Portal. Registeredusers can log on to the system.


Actor All


Stakeholder



cont...




Login

Preconditions

Triggers The user opens the ENVIROFI Biodiversity Portal and selects“Login”

Main success scenario The user is logged on to the ENVIROFI Biodiversity Portal.Based on their user configuration and rights, they will be providedwith different views within the portal.

Extensions

Alternative paths

Post conditions


Validation statement The user is identified within the system

Notes


Includes UseCase Login User

Table 47: UC-ENV1.D-prt-08-V01 – Login

2.1.46 Upload Data

Upload Data


Use Case Name Upload Data



Use Case Diagram

Status Planned


Goal Upload and Merge external occurrence data

Summary An external occurrence dataset is integrated into the system. Inorder to assure consistancy with existing data, a semantic mergeis performed

Category Data Input



Stakeholder


ENVIROFI Biodiversity RepositoryENVIROFI Biodiversity Ontol-ogy

cont...




Upload Data

Preconditions The user logged UC-ENV1.1-auth-01-V01

Triggers The user initiates Upload Occurrence

Main success scenario An external occurrence dataset is integrated into the system. Inorder to assure consistancy with existing data, a semantic mergeis performed. The following steps are performed:Extract conceptlist from external occurrence datasetNew concept list is mergedwith existing species concepts, the following mechanisms areused:

• String Comparison• Phonetic Comparison• Comparison of related concepts• Elimination of Homonyms• Manual correction

Data is aligned with the ENVIROFI concepts. The old identifica-tion of the occurrence record must be stored in addition to thealigned name.

Extensions

Alternative paths

Post conditions New occurrence records from an external source are availablefrom within the ENVIROFI Biodiversity Repository. These recordsare aligned with the concepts within the ENVIROFI BiodiversityOntology.


Validation statement There is no unaligned occurrence data available within the ENVI-ROFI Biodiversity Repository

Notes

Author and date kschleidt

Includes UseCase Store dataMerge Concept ListMerge DataEdit dataAccess informationEdit informationExtract Concept List

Table 48: UC-ENV1.D-prt-09-V01 – Upload Data



Figure 13: Use case UC-ENV1.D-prt-09-V01 Upload Data



2.1.47 Adjust Identifications

Adjust Identifications


Use Case Name Adjust Identifications



Use Case Diagram

Status Planned


Goal Adjust occurrence identifications based on user feedback

Summary Users can provide feedback on the identification of occurrencerecords. This additional information must be integrated with theexisting identification, and based on the plausibility of the identi-fication as well as feedback a new identification provided.

Category data input



Stakeholder


ENVIROFI Biodiversity Repository ENVIROFI Biodiversity Ontol-ogy


Triggers The user has initiated adjust identifications

Main success scenario The records within the ENVIROFI Biodiversity Repository arechecked for alternative identification records provided within UC-ENV1.D-prt-05-V01 Provide Feedback on Occurrences on Portaland stored within the ENVIROFI Biodiversity Ontology.Based onthe trust levels assigned to both the data provider as well as theusers providing feedback on the occurrence record, a new iden-tification may be provided and stored with the record within theENVIROFI Biodiversity Repository

Extensions The user is given the possibility to view the proposed adjustmentsbefore they are stored in the ENVIROFI Biodiversity RepositoryThe user can also activate automatic adjustment to be performedat regular intervals. In this extension it is not possible to first viewthe adjustments.

cont...




Adjust Identifications

Alternative paths

Post conditions The occurrence records within the ENVIROFI Biodiversity Repos-itory have been reidentified based on user feedback



Notes


Includes UseCase Check IdentificationsEdit data

Table 49: UC-ENV1.D-prt-10-V01 – Adjust Identifications



Adjust Identifications.png

Figure 14: Use case UC-ENV1.D-prt-10-V01 Adjust Identifications



2.1.48 Generate Distributions

Generate Distributions


Use Case Name Generate Distributions



Use Case Diagram

Status Planned


Goal Calculate new Habitat and Species distributions

Summary New Habitat and Species distributions are calculated based onoccurrence data and background layers

Category semantics



Stakeholder


ENVIROFI Biodiversity Repository ENVIROFI Biodiversity Ontol-ogy


Triggers The user has initiated generate distributions

Main success scenario New Habitat and Species distributions are calculated based onoccurrence data and background layersThe user can select thehabitats or species these distributions are to be generated forBe-fore storing the new distributions, the user can manually checkthem for plausibility.The new distributions are stored in the ENVI-ROFI Biodiversity Ontology

Extensions

Alternative paths

Post conditions Adjusted Habitat and Species Distributions are available fromwithin the ENVIROFI Biodiversity Ontology



Notes


Includes UseCase Store informationAccess informationGenerate Habitat DistributionGenerate Species Distribution

cont...




Generate Distributions

Table 50: UC-ENV1.D-prt-11-V01 – Generate Distributions



Figure 15: Use case UC-ENV1.D-prt-11-V01 Generate Distributions


SEVENTH FRAMEWORK PROGRAMME ICT PPP Future Internet · 2017. 4. 20. · UC-ENV1.4-sem-04-V01...

Documents

Transcript of SEVENTH FRAMEWORK PROGRAMME ICT PPP Future Internet · 2017. 4. 20. · UC-ENV1.4-sem-04-V01...