Versions Compared

Old Version 34

changes.mady.by.user Axel Magdelijns

Saved on

compared with

New Version 35

changes.mady.by.user Axel Magdelijns

Saved on

Key

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

...

FlowSpecifications


IDAP-UC04-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.
Test Data
Endpoint(s)


Alternative flow 1

FlowSpecifications

Image Added


IDAP-UC04-AF01
NameSet an out-of-office with
1 substitute
2 or more substitutes
Description/
Actor(s)
Two

Three or more healthcare professionals:

  • One who will be OoO.
One
  • Two or more who will be
the substitute
  • 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
substitute
  1. substitutes (Example_Test
_Actor
  1. _Actor1) and (ExampleTest_Actor2).
    There are two ways to do this:
    • Add the NISS number of the
substitute
Postcondition(s)
  • The OoO is successfully added.
Test Data
Endpoint(s)