-
Notifications
You must be signed in to change notification settings - Fork 26
I 30 Add the possibility for direct booking
Add support to book directly based on the detailed offer search criteria.
Comment ASC: Fundamental design decision whether we want to add that to the API natively or whether this can be implemented as a sort of filtering on offers requested via the existing API flow.
- Patrick Heuget (ETT)
For expert users such as rail agents
who have deep knowledge of the tariff systems and time tables
the possibility to specific the offer request directly
is an expert feature
that enables an efficient booking flow
unlike the current API specification
our solution reduces the call chain.
The measurable benefits that the business can anticipate if the epic hypothesis is proven to be correct.
More efficient booking flows for expert users.
The early measures that will help predict the business outcome hypothesis.
Feature is requested by expert user groups.
Nonfunctional requirements (NFRs) associated with the epic.
Define behavior in case the offer request doesn't fully match.
Making a booking based on a set of parameters by-passing the offer step. So
POST /bookings either takes an offer id or a set of parameters.
Other approach would be to calculate an offer based on these parameters, and if it's unique directly book it.
Would need some filters on the current API.
Next Step: Understand the relevant parameters and sufficient criteria for the booking.
OSDM Wiki