Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Basic flow

FlowSpecifications


IDAP-UC04UC408-BF
NameSet an out-of-office with 1 substitute
Description/
Actor(s)

Two healthcare professionals:

  • One who will be OoO.
  • One who will be the substitute.
Requirements

/

TriggerA user wants to set an out-of-office.
Precondition(s)
  • The user is logged in.
  • The user wants to set an out-of-office.
Flow
  1. see Use case: login.
  2. When opening the OoO section, the application should automatically
    request a list of already inserted OoO periods.
  3. The inserted OoO period should be, for example,
    from the next monday until friday of the same week.
  4. Add the substitute (Example_Test_Actor). There are two ways to do this:
Postcondition(s)
  • The OoO is successfully added.
  • There is one more OoO period than there was before the insert.
Test Data

GetOoOList

InsertOoO

Endpoint(s)


Alternative flow 1

FlowSpecifications


IDAP-UC04UC408-AF01
NameSet an out-of-office with 2 or more substitutes
Description/
Actor(s)

Three or more healthcare professionals:

  • One who will be OoO.
  • Two or more who will be substitutes.
Requirements

/

TriggerA user wants to set an out-of-office.
Precondition(s)
  • The user is logged in.
  • The user wants to set an out-of-office.
Flow
  1. see Use case: login.
  2. When opening the OoO section, the application should automatically
    request a list of already inserted OoO periods.
  3. The inserted OoO period should be, for example,
    from the next monday until friday of the same week.
  4. Add the substitutes (Example_Test_Actor1) and (ExampleTest_Actor2).
    There are two ways to do this:
Postcondition(s)
  • The OoO is successfully added.
  • There is one more OoO period than there was before the insert.
Test Data

GetOoOList

InsertOoO

Endpoint(s)


Alternative flow 2

FlowSpecifications


IDAP-UC04UC408-AF02
NameDelete an out-of-office.
Description/
Actor(s)

One healthcare professional

Requirements

/

TriggerA user wants to delete an out-of-office.
Precondition(s)
  • The user is logged in.
  • The user has atleast one out-of-office period.
  • The user wants to delete an out-of-office.
Flow
  1. see Use case: login.
  2. When opening the OoO section, the application should automatically
    request a list of already inserted OoO periods.
Postcondition(s)
  • The OoO is successfully deleted.
  • There is one less OoO period than there was before the delete.
Test Data

GetOoOList

DeleteOoO

Endpoint(s)


Alternative flow 3

FlowSpecifications


IDAP-UC04UC408-AF02
NameUpdate an out-of-office.
Description/
Actor(s)

One healthcare professional

Requirements

/

TriggerA user wants to update an out-of-office.
Precondition(s)
  • The user is logged in.
  • The user has atleast one out-of-office period.
  • The user wants to update an out-of-office.
Flow
Postcondition(s)
  • The OoO is successfully updated.
Test Data

GetOoOList

InsertOoO

DeleteOoO

Endpoint(s)


...