Booking 2.0 Beta 2
Standard documentation
2.1 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 a concise, informal description of a feature or functionality written from an end user's or stakeholder 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 paragraph provides a few examples of user stories that DCSA has relied on to develop the standard for the Booking process. The supporting use cases are defined in the dedicated booking use cases page.2.2 User stories example
View examples of user stories that DCSA has relied on to develop the standard for the booking process. The supporting use cases are defined in the dedicated booking use cases page.
| User story | Action |
|---|---|
“As a shipper I want to update the booking request so that the type and number of containers gets changed to 5 x 40HC.“ | The shipper submits an updated booking request with Booking use case “UC3: Submit updated booking request”. |
“As a shipper I want the carrier to modify the confirmed booking so that the number of containers gets changed to 4 x 40HC.“ | The shipper submits a booking amendment request with Booking use case “UC7: Request amendment to confirmed booking”. |
“As a shipper I want to cancel the last amendment I requested to the confirmed booking.“ | The shipper cancels the last booking amendment request with Booking use case “UC9: Cancel amendment to confirmed booking”. |
“As a shipper I want the carrier to modify a draft Transport Document so that the Reefer drain holes get changed to closed.“ | The shipper cannot directly request an update of the draft Transport Document. Instead, the shipper requests a booking amendment with Booking use case “UC7: Request amendment to confirmed booking”. After approving the amendment with Booking use case “UC8: Process amendment to confirmed Booking”, the carrier publishes an updated draft Transport Document with eBL use case “UC6: Publish Draft Transport Document”. |
“As a shipper I want the carrier to modify a draft Transport Document so that the outer IMO packaging code of Dangerous Goods cargo gets changes to 3A1.“ | The shipper cannot directly request an update of the draft Transport Document. Instead, the shipper requests a booking amendment with Booking use case “UC7: Request amendment to confirmed booking”. After approving the amendment with Booking use case “UC8: Process amendment to confirmed Booking”, the carrier publishes an updated draft Transport Document with eBL use case “UC6: Publish Draft Transport Document”. |
“As a shipper I want the carrier to modify an issued Transport Document so that the Reefer O2 setpoint gets changed to 30%.“ | The shipper cannot directly request an update of the issued Transport Document. Instead, the shipper requests a booking amendment with Booking use case “UC7: Request amendment to confirmed booking”. After the carrier approves the amendment with Booking use case “UC8: Process amendment to confirmed Booking”, the shipper requests via the eBL platforms a surrender for amendment with eBL use case “UC9: Request surrender Transport Document (amendment)”. After approving the surrender request with eBL use case “UC10: Process Transport Document surrender request (amendment)”, the carrier voids the existing Transport Document and issues a new amended Transport Document with eBL use case “UC11: Void original Transport Document and issue amended Transport Document”. |
“As a shipper I want the carrier to modify an issued Transport Document so that the emergency contact phone number for Dangerous Goods gets changed to +1 23456789.“ | The shipper cannot directly request an update of the issued Transport Document. Instead, the shipper requests a booking amendment with Booking use case “UC7: Request amendment to confirmed booking”. After the carrier approves the amendment with Booking use case “UC8: Process amendment to confirmed Booking”, the shipper requests via the eBL platforms a surrender for amendment with eBL use case “UC9: Request surrender Transport Document (amendment)”. After approving the surrender request with eBL use case “UC10: Process Transport Document surrender request (amendment)”, the carrier voids the existing Transport Document and issues a new amended Transport Document with eBL use case “UC11: Void original Transport Document and issue amended Transport Document”. |
“As a carrier I want to confirm the Booking request based on the input received from the Shipper in the Booking request.“ | The carrier confirms the booking with Booking use case “UC5: Confirm booking request”. |
“As a carrier I want to confirm the Booking based on the input received from the Shipper in the Booking amendment.“ | The carrier confirms the booking amendment with Booking use case “UC8: Process amendment to confirmed Booking”. |
“As a carrier I want to update the confirmed booking with a new ETD (Expected Time of Departure).“ | The carrier re-confirms the booking with Booking use case “UC5: Confirm booking request”. |
“As a carrier I want to cancel the booking before it has been confirmed.“ | The carrier cancels the booking with Booking use case “UC4: Reject booking request”. |
“As a carrier I want to cancel the booking after it has been confirmed.“ | The carrier cancels the booking with Booking use case “UC10: Decline booking by carrier”. |