DCSA Reference Documentation / Standards / Standard Releases / Arrival Notice / Arrival Notice v1.0.1

DCSA Interface Standard for Arrival Notice 1.0.1 - Use Cases

This page is republished as part of the complete documentation set for this version. No content changes were made compared to the 1.0.0 version.

Contents

Overview

In line with the techniques used in software development, DCSA has incorporated user stories and use cases into the standards development process to support the digitalization efforts of the shipping industry. Both user stories and use cases serve the purpose of capturing and documenting requirements, but they differ in granularity, level of detail, and the stages of the development process in which they are most prominently used. They are complementary (a user story may be supported by one or more use cases and vice versa) and can be used together to provide a comprehensive understanding of software requirements. In this section, we will focus on use cases.

Use cases

Use cases are typically descriptions of how a system will respond to a specific request or interact with a user and are a valuable technique for capturing and defining functional requirements in a way that is easily understandable by both technical and non-technical stakeholders. The use cases defined in this standard include the following components:

  1. Actors: Actors are external entities, which could be users or other systems, interacting with the software. They initiate the use case and are the ones for whom the system provides value.

  2. Description: A brief explanation that summarizes the purpose of the use case.

  3. Preconditions: Prerequisites that need to be fulfilled or tasks that must be finished prior to the execution of the use case.

  4. Postconditions: The state of the system after the successful completion of the use case.

  5. Flow: The primary steps of the use case, outlining the expected sequence of interactions between the actors and the system.

The following use cases have been defined by DCSA to support the Arrival Notice process.

UC1: Send Arrival Notice

Actors

Publisher to receiver.

Description

The publisher sends one or more Arrival Notices to inform the receiver that the shipment is approaching its destination.

Preconditions

  • The shipment is en route to the destination.

  • The Arrival Notice is scheduled to be sent based on timing or business rules.

  • Necessary shipment data and contact information is available and verified.

Postconditions

The Arrival Notice(s) are successfully delivered to the receiver.

Flow

  1. The publisher verifies that the shipment is in transit and that all required data is complete.

  2. The publisher retrieves the receiver’s contact details.

  3. The publisher sends one or several Arrival Notices to the receiver.

  4. The receiver successfully receives the Arrival Notice(s).

UC2: Update Arrival Notice

Actors

Publisher to receiver.

Description

The publisher updates an Arrival Notice(s) that has already been sent, due to updated or corrected shipment information.

Preconditions

  • An Arrival Notice has already been created and sent to the receiver.

  • The publisher identifies that some of the information is incorrect, missing, or has changed.

  • The updated information is available and validated.

Postconditions

  • The updated Arrival Notice(s) are successfully delivered to the receiver.

  • The latest and correct version of the Arrival Notice(s) are available to relevant parties.

Flow

  1. The publisher identifies that the information in the previously sent Arrival Notice(s) needs to be updated.

  2. The publisher collects and confirms the updated data.

  3. The updated Arrival Notice(s) are generated.

  4. The publisher sends the updated Arrival Notice(s) to the receiver.

  5. The receiver successfully receives the updated Arrival Notice(s).

UC3: Retrieve Arrival Notice

Actors

Receiver to publisher.

Description

A receiver submits a request to retrieve one or more Arrival Notices.

Preconditions

  • The receiver has not received the Arrival Notice or needs it resent.

Postconditions

There are two possible scenarios:

  • The request is approved and the Arrival Notice(s) are sent to the receiver.

  • The request is rejected due to authorization failure or data unavailability.

Flow

  1. The receiver submits a request for the Arrival Notice(s).

  2. The publisher checks if the receiver is authorized to receive the Arrival Notice. If not authorized, the request is rejected.

  3. If authorized, the publisher checks whether the Arrival Notice(s) are available. If not available, the request is rejected and the receiver is informed.

  4. If available, the publisher sends the Arrival Notice(s) to the receiver

UC4: Notify Arrival Notice availability

Actors

Publisher to receiver.

Description

The publisher sends a lightweight notification to inform the receiver that one or more Arrival Notices have been generated and are now available. The notification includes key arrival information to provide basic context.

Preconditions

  • The Arrival Notice(s) have been generated and are available in the publisher’s system.

  • The receiver is authorized to receive the Arrival Notice(s), and contact details are known and validated.

  • The receiver has implemented support for AN notifications.

Postconditions

  • The receiver is informed that the Arrival Notice(s) are available.

  • Basic arrival information is shared as part of the notification.

Flow

  1. The Arrival Notice(s) are created and available in the publisher’s system.

  2. The publisher verifies the receiver’s authorization and contact information.

  3. A lightweight notification is prepared, containing key details (e.g. transport document reference, ETA, POD).

  4. The publisher sends the notification to inform the receiver that the Arrival Notice(s) are ready.

  5. The receiver successfully receives the notification.