Versions Compared

Old Version 37

changes.mady.by.user Axel Magdelijns

Saved on

compared with

New Version 38

changes.mady.by.user Axel Magdelijns

Saved on

Key

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

...

FlowSpecifications


IDAP-UC08-AF01
NameDelete a message from the full message view
Description/
Actor(s)One healthcare professional
Requirements
  • Atleast one message in one of the message boxes.
TriggerA healthcare professional wants to delete a message.
Precondition(s)
  • The user is logged in.
  • The user wants to delete a message.
Flow
  1. See use case: login.
  2. The user wants to view the contents of one of his message boxes.
    The user will see a list with all of his message for the specific folder he/she requested.
    See use case: consultation for more information about the GetMessagesList method.
  3. The user selects one message to read. The message will be opened.
    See use case: read message for more information about the GetFullMessage method.
  4. The user moves this message to a different message box.
  5. The user gets automatically returned to the list view of the message box he/she was in.
    The list gets updated automatically.
Postcondition(s)
  • The message is no longer available in the message box it was consulted in.
  • The message is available in the message box it was moved to.
Test Data

GetMessagesList

GetFullMessage

DeleteMessage

Endpoint(s)


Exception flow

FlowSpecifications


IDAP-UC09-EF01
NameTry to delete a message with an invalid message id
Description/
Actor(s)One healthcare professional
Requirements
  • Atleast two message in one of the message boxes.
TriggerA healthcare professional wants to delete one or more messages.
Precondition(s)
  • The user is logged in.
  • The user wants to delete one or more messages.
Flow
  1. See use case: login.
  2. The user wants to view the contents of one of his message boxes.
    The user will see a list with all of his message for the specific folder he/she requested.
    See use case: consultation for more information about the GetMessagesList method.
  3. The user selects one or more messages. The user wants to delete this/these message(s).
  4. The user gets a confirmation screen. The user can chose to confirm (4a) or not (4b).
    1. The user confirms and the message(s) get(s) deleted.
      A request will be sent to delete the message(s). Afterwards,
      a request will be sent to update the message list.
    2. The message(s) remain(s) the same. Nothing happens.
Postcondition(s)

Path 4a:

  • The deleted message(s) is/are no longer available.

Path 4b:

  • The message(s) is/are still available. Nothing has changed.
Test Data

GetMessagesList

DeleteMessage

Endpoint(s)