DCSA Reference Documentation / Standards / Standard Releases / Arrival Notice / Arrival Notice v1.0.1
DCSA Interface Standard for Arrival Notice 1.0.1 - User Stories
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
- Introduction
- User Stories
- US1: “As a publisher, I want to send one or more Arrival Notices to a registered receiver.”
- US2: “As a publisher, I want to send updated versions of one or more Arrival Notices to a registered receiver.”
- US3: “As a receiver, I want to request the latest Arrival Notice(s) matching certain criteria.”
- US4: “As a receiver, I want to receive Arrival Notice(s) as soon as they become available.”
- US5: “As a publisher, I want to notify a registered receiver that one or more Arrival Notices are available, without sending the full structured content and visualization.”
Introduction
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 user stories.
User stories are typically concise, informal descriptions of a feature or functionality written from an end user’s or stakeholder’s perspective. They express the needs, goals, and expectations of users in a way that is easily understandable to ensure the delivered product meets the intended requirements. In standards development, this translates to creating testable acceptance criteria to validate that the standard is correctly implemented and achieves its intended purpose.
The next section outlines the Arrival Notice User Stories that DCSA used as the basis for developing the standard. The supporting use cases are defined in the dedicated Arrival Notice use cases section.
The standard specifies the interaction between two roles:
-
an arrival notice Publisher, typically an ocean carrier or a freight forwarder
-
an arrival notice Receiver, which can be a notify party, consignee, customs broker, etc.
User Stories
US1: “As a publisher, I want to send one or more Arrival Notices to a registered receiver.”
The publisher sends one or more Arrival Notices to a registered receiver with use case “UC1: Send Arrival Notice”.
US2: “As a publisher, I want to send updated versions of one or more Arrival Notices to a registered receiver.”
The publisher can send one or more updated Arrival Notices to a registered receiver with use case “UC2: Update Arrival Notice”.
US3: “As a receiver, I want to request the latest Arrival Notice(s) matching certain criteria.”
The registered receiver retrieves one or more Arrival Notices from the publisher using use case “UC3: Retrieve Arrival Notice”.
US4: “As a receiver, I want to receive Arrival Notice(s) as soon as they become available.”
The publisher sends one or more Arrival Notices to a registered receiver as soon as they are available, with use cases “UC1: Send Arrival Notice” & “UC2: Update Arrival Notice”.
US5: “As a publisher, I want to notify a registered receiver that one or more Arrival Notices are available, without sending the full structured content and visualization.”
The publisher sends a lightweight notification containing key attributes of one or more Arrival Notices, indicating that they are now available, with Arrival Notice use case “UC4: Notify Arrival Notice Availability.”