As a Doctor
I want to be able to create an account
so that I can use the service with a secure access
Context
For convenience reasons Doctors are able to use our service through a web interface. This web interface only grants access to Doctors so that they can manage patient data. In order to do so they should be able to register and login.
In scope
Being able to register with email and password, first name, last name
Out of scope
Having any sort of validation on the fields (except for empty)
Having any sort of confirmation through email or what so ever of the doctor really being a doctor (e.g. Lebenslange Arztnummer)
Additional data that might be interesting to have from the doctor
doctor should be a role of a user (the other being a patient)
the data should only be transferred via HTTPS
Acceptance Criteria
AC1
GIVEN a doctor is not registered yet
WHEN they click on register, enter their email and password and click the register button
THEN they will be registered and can login and a confirmation screen appears (see attached sketches)
AC2
GIVEN a doctor is already registered with given email
WHEN they click on register, enter their email and password and click the register button
THEN they will be forwarded to the confirmation screen without anything happening in the backend (security reasons), it will look like they just registered, but they will not have actually registered a new user (see attached sketches)
AC3
GIVEN a doctor is not registered
WHEN they click on register, enter nothing in email and password and click the register button
THEN they will get an error message telling them they should at least enter the fields email and password (see attached sketches)
AC4
GIVEN a doctor is not registered
WHEN they fill out all the fields and are able to register and click on the register button
THEN all the filled out data will be sent to the backend via HTTPS (see browser if there is a certificate and https is enabled)
As a Doctor I want to be able to create an account so that I can use the service with a secure access
Context
For convenience reasons Doctors are able to use our service through a web interface. This web interface only grants access to Doctors so that they can manage patient data. In order to do so they should be able to register and login.
In scope
Out of scope
There will be follow up stories for this: https://github.com/diabetes-assistant/documentation/issues/13, https://github.com/diabetes-assistant/documentation/issues/15, https://github.com/diabetes-assistant/documentation/issues/12
Tech notes
Acceptance Criteria
AC1
GIVEN a doctor is not registered yet WHEN they click on register, enter their email and password and click the register button THEN they will be registered and can login and a confirmation screen appears (see attached sketches)
AC2
GIVEN a doctor is already registered with given email WHEN they click on register, enter their email and password and click the register button THEN they will be forwarded to the confirmation screen without anything happening in the backend (security reasons), it will look like they just registered, but they will not have actually registered a new user (see attached sketches)
AC3
GIVEN a doctor is not registered WHEN they click on register, enter nothing in email and password and click the register button THEN they will get an error message telling them they should at least enter the fields email and password (see attached sketches)
AC4
GIVEN a doctor is not registered WHEN they fill out all the fields and are able to register and click on the register button THEN all the filled out data will be sent to the backend via HTTPS (see browser if there is a certificate and https is enabled)
Sketches
Registration confirmation page
Registration with error message
Register form