6 Detailed Use cases
6.1 Overview
Requirements gathering activities identified a range of user groups that will contribute to, operate, or consume Ecosystem Indicator Workflows (EIWs). The use cases below represent the most common and highest-priority applications identified through workshops, user stories, and stakeholder consultations. These use cases informed the prioritisation of workflow functionality and the staged development roadmap.
6.2 Use case descriptions
UC01 – Adapt an existing fit-for-purpose ecosystem-specific indicator to make it reproducible
| Attribute | Description |
|---|---|
| Primary User | Ecologist / Conservation Scientist (UG01) |
| Supporting Users | Research Software Engineer (UG07), Data Scientist (UG06) |
| Purpose | Adapt an ecosystem-specific indicator to make it reproducible |
| Trigger | Update existing ecosystem assessments, revisit research or monitoring questions. |
| Key requirements | AD01, AD02, AD05, RE01, RE02, RE04, VO01, VO02, DD02, DD03, DD04, DD06, DO04, AC01, AC03, VA02, VA03, VA04, VA05 |
Implementation steps
- Check existing scope of the workflow as per high-level requirements: ecosystem, purpose, diagnostic and variable selection.
- Check structure of the workflow as per high-level requirements: data preparation, calculation and validation/uncertainty assessment.
- Assess existing gaps in implementation of FAIR principles
- Edit/modify steps to close gaps in FAIR principles
- Review outputs and document all steps as per high-level requirements.
Outputs
- Indicator values
- Maps and visualisations
- Workflow documentation including validation and uncertainty reports
Impact
Enable reproducibility of existing ecosystem-specific indicators, increase consistency, transparency, and reproducibility across ecosystem assessments. This use case emerged as a high-priority scenario during workshop discussions around workflow adaptability.
UC02 – Develop a new fit-for-purpose ecosystem-specific indicator
| Attribute | Description |
|---|---|
| Primary User | Ecologist / Conservation Scientist (UG01, UG02) |
| Supporting Users | Research Software Engineer (UG07), Data Scientist (UG06) |
| Purpose | Develop an ecosystem indicator for a previously unassessed ecosystem type. |
| Trigger | A new ecosystem assessment, conservation program, or research project requires an indicator. |
Implementation steps
- Define the scope of the workflow as per high-level requirements: ecosystem, purpose, diagnostic and variable selection.
- Develop structure of the workflow as per high-level requirements: data preparation, calculation and validation/uncertainty assessment.
- Assess implementation of FAIR principles
- Review outputs and document all steps as per high-level requirements.
Outputs
- Indicator values
- Maps and visualisations
- Workflow documentation including validation and uncertainty reports
Impact
Reduces the effort required to develop new indicators while increasing consistency, transparency, and reproducibility across ecosystem assessments. This use case emerged as a high-priority scenario during workshop discussions around workflow adaptability.
UC03 – Adapt an existing reproducible fit-for-purpose indicator to a new ecosystem
| Attribute | Description |
|---|---|
| Primary User | Ecologist / Conservation Scientist (UG01, UG02) |
| Supporting Users | RSE (UG07), Data Scientist (UG06) |
| Purpose | Reuse an existing workflow for another ecosystem type or assessment purpose. |
Implementation steps
- Locate a suitable workflow in the workflow catalogue.
- Identify ecosystem-specific components.
- Replace ecosystem definitions, datasets and parameters.
- Re-run workflow using the new ecosystem context.
- Validate outputs.
Outputs
- Adapted workflow
- Updated metadata and documentation
- New indicator outputs
Impact
Reduces duplication of effort and accelerates ecosystem assessments. Workshop participants consistently identified workflow adaptability as one of the most important requirements for the EIW project.
UC04 – Adapt an existing reproducible ecosystem-specific indicator to a different purpose
| Attribute | Description |
|---|---|
| Primary User | Ecologist / Conservation Scientist (UG01, UG02) |
| Supporting Users | RSE (UG07), Data Scientist (UG06) |
| Purpose | Reuse an existing workflow for a different assessment or purpose. |
Implementation steps
- Locate a suitable workflow in the workflow catalogue.
- Identify components related to purpose of the indicator
- Replace parameters and adjust calculations for the intended purpose.
- Re-run workflow using the new analytical context and interpretation.
- Validate outputs.
Outputs
- Adapted workflow
- Updated metadata and documentation
- New indicator outputs
Impact
Reduces duplication of effort and accelerates ecosystem assessments. Workshop participants consistently identified workflow adaptability as one of the most important requirements for the EIW project.
UC05 – Publish and Maintain a Reproducible Workflow
| Attribute | Description |
|---|---|
| Primary User | Workflow authors (UG01, UG02, UG06, UG07) |
| Supporting Users | Platform Administrator (UG09) |
| Purpose | Publish a workflow that can be reused and maintained over time. |
Implementation steps
- Package workflow components.
- Define software dependencies.
- Configure reproducible environments.
- Register metadata and identifiers.
- Publish workflow documentation.
Outputs
- Workflow repository
- DOI and metadata records
- Documentation
- Containerised environment
Impact
Supports long-term maintenance and reuse while ensuring workflows remain reproducible as software and data sources evolve. Reproducibility and software versioning were identified as critical concerns during workshops.
UC06 – Integrate multiple indicator workflows in assessments or reports
| Attribute | Description |
|---|---|
| Primary User | Ecologist / Technical Analyst (UG01, UG02, UG03) |
| Supporting Users | RSE (UG07), Data Scientist (UG06) |
| Purpose | Reuse existing workflows and integrate them in a larger ecosystem assessment or report with a defined purpose, including one or multiple ecosystems. |
Implementation steps
- Locate suitable workflows in the workflow catalogue.
- Verify alignment with assessment or report purpose, adapt if necessary (see UC03, UC04)
- Combine outputs and document selection process
- Update report metadata including provenance information and references to input workflow (see UC05).
Outputs
- Assessment or report with embedded workflows (documented methods and/or outputs)
- Workflow citations
Impact
Reduces duplication of effort and accelerates ecosystem assessments. Workshop participants consistently identified workflow adaptability as one of the most important requirements for the EIW project.
UC07 – Discover and Reuse Existing Workflows
| Attribute | Description |
|---|---|
| Primary User | Researchers (UG01, UG02), Technical practicioner (UG03), Policy Analyst (UG04) Consultant (UG05) |
| Purpose | Find workflows relevant to a specific ecosystem, indicator, or assessment purpose. |
Implementation steps
- Search workflow catalogue.
- Filter by ecosystem type, indicator type, or assessment framework.
- Review documentation and examples.
- Execute or adapt workflow (see UC03 and UC04).
Outputs
- Reused workflows
- Adapted workflows
- Reproducible assessments
Impact
Reduces duplication of effort and encourages workflow standardisation across organisations and jurisdictions.
UC08 – Training and Skills Development
| Attribute | Description |
|---|---|
| Primary User | Student / Early-Career Researcher (UG02) |
| Supporting Users | Ecologists (UG01), Trainers (UG10) |
| Purpose | Build capability in reproducible ecosystem assessment workflows. |
Implementation steps
- Attend workshops or training events.
- Access worked examples.
- Run demonstration workflows.
- Modify workflows for new examples.
- Contribute improvements.
Outputs
- Trained users
- New contributors
- Community of practice
Impact
Expands the user base and supports long-term sustainability of the workflow ecosystem. Training and documentation were identified as high-priority requirements across all workshop participants.
UC09 – Apply an Existing Workflow to a Specific Assessment
| Attribute | Description |
|---|---|
| Primary User | Environmental Consultant / Assurance Practitioner (UG05) |
| Supporting Users | Environmental Manager / Technical Practitioner (UG03), Data Scientist (UG06) |
| Purpose | Run an existing, unmodified indicator workflow against a specific site, region, or portfolio to produce a result for an assessment, audit, ecosystem account, or nature-related disclosure. |
Implementation steps
- Select a workflow matching the ecosystem and assessment framework required.
- Confirm the workflow can run within the available data access and IT constraints.
- Assemble inputs and record data gaps, limitations, and known biases.
- Execute the workflow; where empirical validation data are unavailable, apply and document expert judgement.
- Put outputs through documented review before release.
Outputs
- Indicator result for the assessment
- Documented limitations statement
- Review and expert-judgement record
Impact
Covers routine application of existing workflows, which is expected to be the highest-volume activity across the user community. Distinguishes applied assessment from workflow development (UC01) and adaptation (UC02, UC03), and places a larger focus on documented limitations and expert review as standard requirements. This use case also brings the consulting and assurance community (UG05) into scope, reflecting the growth of ecosystem accounting and nature-related disclosure obligations.
6.3 Summary
Across the requirements gathering process, nine recurring use cases were identified. These can be grouped into four broad categories:
- Workflow development and adaptation (UC01, UC02, UC03, UC04)
- Workflow publication, discovery and integration (UC05, UC06, UC07)
- Capacity building and adoption (UC01, UC08)
- Assessment and reporting based on existing indicators (UC06, UC07, UC09)
These use cases form the basis for prioritising functionality and defining the first and second tranches of workflow development activities described in subsequent sections.