Skip to end of metadata
Go to start of metadata

Method

These requirements have been gathered using the early steps of the methodology proposed by Graham Klyne in User requirements elicitation and analysis - proposal. The process makes use of the user roles identified in Users Roles in Astro and User Scenarios - User Perspective (2).

User Requirements

As a Creator of Research Objects ...

 

I want ...

so that ...

to create workflows

I can conduct an investigation [I can automate and streamline aspects of my investigation]

to collect data

I can conduct an investigation

to aggregate existing resources

there is a single access point to those resources [I can conveniently access related resources in a single operation; I can be sure that I have a matching collection of resources]

to describe the relationships between aggregated resources

the relationship is explicit [Other researchers can see how the resources fit together; to facilitate the automation of processing of aggreagted resources]

to be recognised as the creator of an RO

I get credit

As a Contributor to Research Objects ...

 

I want ...

so that ...

to provide a workflow

it can be incorporated or used in an investigation [Other researchers can review the processing performed; other researchers can repeat the processing performed]

to provide new or updated data/results

investigations are up to date

to modify contents

I can fix a known error with a workflow or investigation

to be credited for my contributions

I get credit and make tenure

As a Reader of Research Objects ...

 

I want ...

so that ...

to find relevant materials

I can understand the field

to browse an overview

I can determine whether there is something useful for me

to survey the field

to check whether something has been done before

to examine the relationships between resources

I can understand the relationships between resources

to access data

I can look at it [I can process it]

to access metadata

I can see where data/methods came from

to follow the steps taken

I can understand the investigative process or method

As a Reviewer/Evaluator of Research Objects ...

 

I want ...

so that ...

Rerun an investigation

I can validate that the results are as given

to examine the relationships between resources

I can validate those relationships

to access data

I can validate the data used

to follow the steps taken

I can validate the investigative process and identify any problems

to examine the resources

I can determine the source of those resources

As a Comparator of Research Objects ...

 

I want ...

so that ...

to compare an RO with others

I can determine whether the investigation is novel

to compare an RO with others

I can understand the differences between investigations

As a Re-User of Research Objects ...

I want ...

so that ...

to build a new workflow based on an existing one

I can do something new with less effort

to build a new workflow based on an existing one

I can use an existing, known, validated methodology

to run an existing workflow with new data

I can get new results [I can use existing understood procedures to get new results]

to use results from an existing investigation as input to a new one

I can build on existing results

to use data from an existing investigation as input to a new one

I can build on existing data

to see versions of a workflow

I can use the latest working version [I can better understand a workflow by understanding how it has evolved; I can see how the latest version of a workflow differs from an earlier version I may have used]

As a Publisher of Research Objects ...

 

I want ...

so that ...

to publish an RO

it is available for others to see or use

to provide references to ROs

they can be cited (leading to credit)

Technical Requirements

Creator of Research Objects ...

 

User Requirement

Technical Requirement

to create workflows

workflow system for creation. ROs support workflows as content

to collect data

ROs link and embed data

to aggregate existing resources

ROs provide aggregation

to describe the relationships between aggregated resources

Vocabularies for representing relationships. Aggregation structures support rich relationships

to be recognised as the creator of an RO

Author identification. Content annotation.

Contributor to Research Objects ...

 

User Requirement

Technical Requirement

to provide a workflow

Relating one workflow with another.

to provide new or updated data/results

Resources in an RO can be updated. Versioning of resources and RO as object.

to modify contents

Resources can be updated. Versioning of resources.

to be credited for my contributions

Author identification. Content annotation.

Reader of Research Objects ...

 

User Requirement

Technical Requirement

to find relevant materials

Searching/browsing of ROs. Tagging. Relations between ROs.

to browse an overview

Metadata for overview. Presentation of overview.

to survey the field

Grouping of ROs by field, "Most popular in field X"

to examine the relationships between resources

Browsing and following links between resources. Description of relationship.

to access data

Storage of data or link to data. Download or URL for data. Ability to request access.

to access metadata

Storage/retrieval of structured metadata. Representation of metadata.

to follow the steps taken

Overview of workflow/method. Replay workflow execution using provenance.

Reviewer/Evaluator of Research Objects ...

 

User Requirement

Technical Requirement

Rerun an investigation to validate

Workflow system. Provenance trace of original execution. Original inputs and required tools. Access to original services or copies of original return values.

to examine the relationships between resources

Browse annotations on how relationship was made (for instance "dataX producedBy runY of workflowZ using inputA")

to access data to validate

Verify data equality/similarity. Checksums, timestamps.

to follow the steps taken

Browse annotations on steps to validate scientific reasoning. Compare steps with known methodologies (abstract workflows)

to examine the resources and their source

Browse annotations of origin/source of data. Follow links to verify data equality/similarity/validity.

Comparator of Research Objects ...

 

User Requirement

Technical Requirement

to compare an RO with others to determine novelty

Find similar ROs. Find ROs using similar/same data/services/workflows. Find ROs based  on scientific field, keywords/tags, methodology. Compare workflow/methodology structure, in particular the abstract workflow.

to compare an RO with others to understand differences

Compare workflow structures. Compare individual data items in both ROs. Browse scientific reasoning of relationships between resources. Compare hypothesis.

Re-User of Research Objects ...

 

User Requirement

Technical Requirement

to build a new workflow based on an existing one to save time

Embed/link to existing workflows in ROs. Customize existing workflow, keeping link to original.

to build a new workflow based on an existing one to use existing methodology

Gather citations to existing RO. Notion of latest 'official' version. References to other's extensions/uses of chosen workflow.

to run an existing workflow with new data

Notion of service availability/compatibility.

to use results from an existing investigation as input to a new one

Linking/referencing of resource from one RO to another, including retrieval of data. Links to newer versions of data from later runs.

to use data from an existing investigation as input to a new one

Linking/referencing of resource, but also following its links back to origin/source

to see versions of a workflow

Notion of a 'version' (possibly non-linear). Forward-links to versions in other repositories/by other users.

Publisher of Research Objects ...

 

User Requirement

Technical Requirement

to publish an RO to make it available

Mechanism to ensure components of RO are accessible. Snapshot of RO and its resources. Including RO in publication.

to provide references to ROs

Identification of published RO. Citation mechanism.

Note that there are relationships between user roles here. For example, Reviewers are also Readers. Users may also move between roles. For example, a Reviewer/Evaluator may become a Contributor if the Reviewer has a proposed fix to a broken workflow.

  • No labels