Shopping cart functionality - Versionsgeschichte

Althoffm: Question/Remark regarding Use Case

2017-01-06T09:16:07Z

Question/Remark regarding Use Case

Holtermp am 14. Dezember 2016 um 07:45 Uhr

2016-12-14T07:45:37Z

Holtermp am 24. November 2016 um 13:15 Uhr

2016-11-24T13:15:29Z

Holtermp am 23. November 2016 um 17:59 Uhr

2016-11-23T17:59:00Z

Holtermp am 23. November 2016 um 17:49 Uhr

2016-11-23T17:49:22Z

Holtermp am 23. November 2016 um 17:48 Uhr

2016-11-23T17:48:12Z

Holtermp: Die Seite wurde neu angelegt: „ Kategorie:UseCases == Use Case: ''Shopping cart functionality'' == '''Module:''' Handling: Booking administration == Description == We would like to h…“

2016-11-23T17:47:06Z

Die Seite wurde neu angelegt: „ Kategorie:UseCases == Use Case: ''Shopping cart functionality'' == '''Module:''' Handling: Booking administration == Description == We would like to h…“

Neue Seite

[[Kategorie:UseCases]]

== Use Case: ''Shopping cart functionality'' ==

'''Module:''' Handling: Booking administration

== Description ==

We would like to have a shopping cart functionality like in an online shop. From a customer's point of view the the typical workflow would be:

* While not customer satisfied:
** Search for products (not necessarily part of this interface)
** if customer likes search result:
*** add search result to shopping cart.
* then checkout:
** book all items in shopping cart.

The shopping cart functionality should be optional. Implementations of the STRING-Interface are '''not required''' to implmement it.

== Request Data ==
Changes:

* Add a <code>BookingMode</code> to <code>StringBookRequest</code>,<code>Component</code> and <code>ComponentVariant</code> with the values
** <code>BOOK</code>: Perform an actual Book (turn the shopping cart into a booking).
** <code>QUOTE</code>: Just add the <code>Object</code>(s) in the request to the an existing or new shopping Cart
** ...other modes like optionBooking,...

* Add an element <code>BookingRef</code> to <code>StringBookRequest</code>
** This can be used to refer to an existing shopping cart or booking

== Response Data ==
* Add an element <code>BookingStatus</code> to <code>StringBookResponse</code>,<code>Component</code> and <code>ComponentVariant</code> with the values
** <code>OK</code>: Object has been sucessfully booked
** <code>QUOTED</code>: Object was just added to
** ...other status like optionBooking, cancelled...
'''Check whether we generalize and reuse the attribute ObjectsVariants/ObjectVariant/Room#Status for that purpose '''

* Add a Element <code>AvailabilityStatus</code> to <code>Component</code> and <code>ComponentVariant</code> with the values
** <code>OK</code>: Object is available
** <code>ON_REQUEST</code>: Object availability can not be confirmed yet

* Add an element <code>BookingRef</code> to <code>StringBookResponse</code>
** This can be used to refer to this shopping cart or booking in the next workflow step

== Simplified example workflow ==

'''Watch for the new elements :-)'''

<syntaxhighlight lang="XML">

<StringBookRequest>
<BookingMode>QUOTE</BookingMode>
<Accommodation TourOperatorCode="DER" TravelType="TOUR">
<Objects>
<Object ID="01" ProductCode="LUM12345">
<Stay Nights="14" Start="2017-10-22"/>
</Object>
</Objects>
<ObjectsVariants>
<ObjectVariant ID="01" ObjectIDRef="01">
<Room OpCode="DZ" PassengerIdList="01 02" />
</ObjectVariant>
</ObjectsVariants>
</Accommodation>
</StringBookRequest>


<StringBookResponse Success="true" >
<BookingRef>1234567890</BookingRef>
<BookingStatus>QUOTED</BookingStatus>
<Accommodation TourOperatorCode="DER" TravelType="TOUR">
<Objects>
<Object PackageIndicator="false" ID="01" ProductCode="LUM12345">
<BookingStatus>QUOTED</BookingStatus>
</Object>
</Objects>
<ObjectsVariants>
<ObjectVariant ID="01" ObjectIDRef="01">
<Room OpCode="DZ" PassengerIdList="01 02" Status="QUOTED">
<BookingInfos>
<Price Amount="999.00" Fares="666.66" Taxes="333.33"/>
</BookingInfos>
</Room>
</ObjectVariant>
</ObjectsVariants>
</Accommodation>
</StringBookResponse>



<StringBookRequest>
<BookingRef>1234567890</BookingRef>
<BookingMode>QUOTE</BookingMode>
<Accommodation TourOperatorCode="DER" TravelType="TOUR">
<Objects>
<Object ID="01" ProductCode="SPK54321">
<Stay Nights="14" Start="2017-11-12"/>
</Object>
</Objects>
<ObjectsVariants>
<ObjectVariant ID="01" ObjectIDRef="01">
<Room OpCode="JS" PassengerIdList="01 02" />
</ObjectVariant>
</ObjectsVariants>
</Accommodation>
</StringBookRequest>


<StringBookResponse Success="true" >
<BookingRef>1234567890</BookingRef>
<BookingStatus>QUOTED</BookingStatus>
<Accommodation TourOperatorCode="DER" TravelType="TOUR">
<Objects>
<Object PackageIndicator="false" ID="01" ProductCode="LUM12345">
<BookingStatus>QUOTED</BookingStatus>
</Object>
<Object PackageIndicator="false" ID="02" ProductCode="SPK54321">
<BookingStatus>QUOTED</BookingStatus>
</Object>
</Objects>
<ObjectsVariants>
<ObjectVariant ID="01" ObjectIDRef="01">
<Room OpCode="DZ" PassengerIdList="01 02" Status="QUOTED">
<BookingInfos>
<Price Amount="999.00" Fares="666.66" Taxes="333.33"/>
</BookingInfos>
</Room>
</ObjectVariant>
<ObjectVariant ID="02" ObjectIDRef="02">
<Room OpCode="JS" PassengerIdList="01 02" Status="QUOTED">
<BookingInfos>
<Price Amount="300.00" Fares="200.00" Taxes="100.00"/>
</BookingInfos>
</Room>
</ObjectVariant>
</ObjectsVariants>
</Accommodation>
</StringBookResponse>




<StringBookRequest>
<BookingRef>1234567890</BookingRef>
<BookingMode>BOOK</BookingMode>
</StringBookRequest>


<StringBookResponse Success="true" >
<BookingRef>1234567890</BookingRef>
<BookingStatus>OK</OK>
<Accommodation TourOperatorCode="DER" TravelType="TOUR">
<Objects>
<Object PackageIndicator="false" ID="01" ProductCode="LUM12345">
<BookingStatus>OK</BookingStatus>
</Object>
<Object PackageIndicator="false" ID="02" ProductCode="SPK54321">
<BookingStatus>OK</BookingStatus>
</Object>
</Objects>
<ObjectsVariants>
<ObjectVariant ID="01" ObjectIDRef="01">
<Room OpCode="DZ" PassengerIdList="01 02" Status="OK">
<BookingInfos>
<Price Amount="999.00" Fares="666.66" Taxes="333.33"/>
</BookingInfos>
</Room>
</ObjectVariant>
<ObjectVariant ID="02" ObjectIDRef="02">
<Room OpCode="JS" PassengerIdList="01 02" Status="OK">
<BookingInfos>
<Price Amount="300.00" Fares="200.00" Taxes="100.00"/>
</BookingInfos>
</Room>
</ObjectVariant>
</ObjectsVariants>
</Accommodation>
</StringBookResponse>

</syntaxhighlight>

← Nächstältere Version		Version vom 6. Januar 2017, 09:16 Uhr
Zeile 9:		Zeile 9:

	We would like to have a shopping cart functionality like in an online shop. From a customer's point of view the the typical workflow would be:		We would like to have a shopping cart functionality like in an online shop. From a customer's point of view the the typical workflow would be:
		+
		+	''Question/Remark: The project is about the definition of an interface - shopping carts can either be a function of the front end or the inventory system of the tour operator. The interface itself does not provide an own shopping cart. Pls check the use case.''

	* While the customer wants to keep on shopping:		* While the customer wants to keep on shopping:

@@ Zeile 18: / Zeile 18: @@
 ** Book all items in shopping cart.
 The shopping cart functionality should be optional. Implementations of the STRING-Interface are '''not required''' to implement it.
 == Request Data ==

@@ Zeile 12: / Zeile 12: @@
 * While the customer wants to keep on shopping:
 ** (1) Search for products (not necessarily part of this interface)
-** If the customer likes a asearch result:
+** If the customer decides to pick a search result:
 *** Customer adds search result to shopping cart.
-*** If the customer keeps on shopping goto (1) otherwise goto (2)
+*** If the customer continues shopping goto (1) otherwise goto (2)
 * (2) Checkout:
 ** Book all items in shopping cart.
-The shopping cart functionality should be optional. Implementations of the STRING-Interface are '''not required''' to implmement it.
+The shopping cart functionality should be optional. Implementations of the STRING-Interface are '''not required''' to implement it.
 == Request Data ==

@@ Zeile 10: / Zeile 10: @@
 We would like to have a shopping cart functionality like in an online shop. From a customer's point of view the the typical workflow would be:
-* While not customer satisfied:
+* While the customer wants to keep on shopping:
-** Search for products (not necessarily part of this interface)
+** (1) Search for products (not necessarily part of this interface)
-** if customer likes search result:
+** If the customer likes a asearch result:
-*** add search result to shopping cart.
+*** Customer adds search result to shopping cart.
-* then checkout:
+*** If the customer keeps on shopping goto (1) otherwise goto (2)
-** book all items in shopping cart.
+* (2) Checkout:
 The shopping cart functionality should be optional. Implementations of the STRING-Interface are '''not required''' to implmement it.

@@ Zeile 35: / Zeile 35: @@
 ** <code>QUOTED</code>: Object was just added to
 ** ...other status like optionBooking, cancelled...
-'''Check whether we generalize and reuse the attribute ObjectsVariants/ObjectVariant/Room#Status for that purpose '''
+'''Check whether we can generalize and reuse the attribute <code>ObjectsVariants/ObjectVariant/Room#Status</code> for that purpose '''
 * Add a Element <code>AvailabilityStatus</code> to <code>Component</code> and <code>ComponentVariant</code> with the values

@@ Zeile 141: / Zeile 141: @@
 <!-- STEP 3 Check out: Book all items in the cart -->
-<!--if objects are omitted alle items are booked with the given booking mode -->
+<!--if objects are omitted all items int the cart are booked with the given booking mode -->
 <StringBookRequest>