Team 3 - Use cases - Homework 10 - Global use case view review

[bourdelin]

We need a global presentation of the use cases.
Please find a schematic presentation based on the (Einar) hypothesis :

• linked to the use cases in a temporal presentation flow
• this flow describes when booking is needed and multiple DISTRIBUTORS. Most cases are simpler, but also covered, like only one DISTRIBUTOR and also not always need for reservation / booking.
• some concepts used are not yet in Transmodel, but described in the CoRoM part of the EA file. There will be a need for changes in Transmodel, like the TRAVEL PACAGE and TRAVEL GUARANTEE and properly more also.
• need changes in the profile (EPIP): use of BOOKING ARRANGEMENT (where and when booking is needed)

Link in SharePoint : EUDIT Purhcase Flow_version1

[OlivierBigex]

an easy first comment: in the retailer line, replace "retaler" by "retailer"
Same in "assumption", replace "reitailer" by "retailer"

[OlivierBigex]

As discussed: add a disclaimer telling that the flow describes a linear generic BUC, but there could be interruptions, go backs, errors, iterations... Most of them are described inside each BUC.

[OlivierBigex]

Transmodel terminology:

Still not confortable with transmodel objects mapping:

1. Distributors provide offers = a description of the mobility service (eligible product = SOP) + a price = CPP ?
2. as described in BUC, the retailer aggregates offers. If this aggregation is called a Travel Package (from Corom), is it clear that this object is not the same objet than the one on distributor side, which is also an aggregation of fare owners offers ?
3. as described in BUC, indeed the retailer aggregates offers, but what we call a "travel basket" can gather different independent offers as well. Thus this step is rather a management of travel basket with travel basket elements.

[OlivierBigex]

booking step:

• "start (pre)booking" or "finalize purchase" rather than "start reservation" because "reservation" is often bound to a resource allocation. If "reservation" is kept, a definition shall explain what is behind. Same at the end: it is rather a booking confirmation than a reservation confirmation.
• as comment in BUC B and C, the prebooking can start each time an offer is put in the retailer's basket, in order to secure dynamic prices and seat allocation. Thus I would put "start prebooking" under the diamond with a condition " if the offer needs to be frozen on distributor side" (or something like that).
• the timout will go back on basket management

[OlivierBigex]

Update the fulfilment step with the content of BUC E. In particular their could be an interaction with the distributors to get fulfilments and possibly fulfilment media.

[OlivierBigex]

payment (BUC D): as discussed, add an interaction with the distributor in case of payment with voucher provided by the distributor.