Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UC Proposal: Acquiring Consent for web surveys #21

Open
crtahlin opened this issue Jul 21, 2019 · 0 comments
Open

UC Proposal: Acquiring Consent for web surveys #21

crtahlin opened this issue Jul 21, 2019 · 0 comments
Labels
use-case-proposal Incoming use cases prior - copy into a file once accepted

Comments

@crtahlin
Copy link

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Use Case Name
(A short name)

Acquiring Consent for web surveys

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Scope:
(The name of the system or business area or business function operated)

Software system for doing web surveys (questionnaires).

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Context:
(Text about the goal in its operational context)

Surveying software needs to have proper consent from the person answering the questionnaire (taking into account the questions and the purpose of processing).

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Primary Actor:
(The primary actor name or role)

Respondent (person being asked the questions)

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Stakeholders & Interests
(List of all the stakeholders and their interests in the system operation. Stakeholders include actors that interact with the system and others who do not interact with the system.)

Respondent - will answer questions (tied to his person as PII)
Surveyor - gathers data from the respondent

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Minimal Guarantees
(An optional section listing the minimal guarantees)

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Success Guarantees
(An optional section listing the success guarantees)

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Preconditions:
(What must be true before this use case can be triggered)

Respondent must receive an invitation to the web survey.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Triggers
(What causes the main scenario to start)

Respondent accepts the invitation to the web survey and opens the web survey.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Main Success Scenario:
(A brief list of what the actors do which results in the goal being successfully achieved.)

  1. Respondent starts with the web survey.
  2. Respondent is identified and system checks if appropriate consent (receipt) already exists (based on the type of survey and processing).
  3. If not, the Respondent is shown what he would need to consent to, to go through with the survey
  4. Respondent gives his consent and a consent receipt is offered for download (and also saved by the surveying system)
  5. Respondent continues with answering the questions

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Secondary Success Scenario:
(A second brief list of what the actors do when things don't go down the main path - includes alternative paths and major failure conditions.)

2.1 If appropriate consent (receipt exists), the Respondent continues with the survey.
AND
4.1 Respondent does not give his consent and the surveying finishes.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++

@crtahlin crtahlin added the use-case-proposal Incoming use cases prior - copy into a file once accepted label Jul 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
use-case-proposal Incoming use cases prior - copy into a file once accepted
Projects
None yet
Development

No branches or pull requests

1 participant