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 digitalisation 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 some examples of user stories that DCSA has relied on to develop the standard for the Bill of Lading. This list is not exhaustive and serves only to illustrate the concept. The supporting use cases are defined in the dedicated Bill of Lading use cases section.

Explore chapters

Introduction

Use cases

State Transition Diagram