Commercial Schedules 1.0
Standard documentation
Following the user stories that have been defined by 永利皇宫app下载注册’s members regarding information exchange for commercial schedules, one use case has been identified per topic within commercial schedules.All use cases mentioned in this Interface Standard are covered by the 永利皇宫app下载注册 OpenAPI specification for Commercial Schedules in dedicated endpoints that can be implemented independently.
Explore 永利皇宫app下载注册 OpenAPI specification for Commercial Schedules3.1 Point to point routing
# | Use case name | [Actor] to [Actor] |
|---|---|---|
1 | Request point-to-point routing | Customer to carrier |
3.2 Port Schedule
# | Use case name | [Actor] to [Actor] |
|---|---|---|
1 | Request port schedule | Customer to carrier |
3.3 Vessel Schedule
# | Use case name | [Actor] to [Actor] |
|---|---|---|
1 | Request vessel schedule | Customer to carrier |
Each of the three use cases has a definition and, for simplification of this document, all are supported by the same UML use case diagram. Further, a UML sequence diagram depicts the activity flow of the three use cases. Request parameters and outputs are provided in a data overview table for each use case. The listed attributes are part of the 永利皇宫app下载注册 information model.