Changes for page Business case

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.etorken

Content

...	...	@@ -10,18 +10,20 @@
10	10
11	11	== 2. Exercise ==
12	12
13		-To kickstart your journey into the eMagiz platform, we have selected a set of exercises linked to the Crash Course API Gateway course that will guide you through the platform, from an API perspective, in building and validating your first integration. To start things off, we will introduce the business case in this exercise that will be used to model out the correct solution in eMagiz.
	13	+To kickstart your journey into the eMagiz platform, we have selected a set of exercises linked to the Crash Course Platform course that will guide you through the platform in building and validating your first integration. To start things off, we will introduce the business case in this exercise that will be used to model out the correct solution in eMagiz.
14	14
15	15	=== 2.1 Business Case ===
16	16
17	17	**Read and understand the following business case**
18	18
19		-As Dream Inc., we supply custom-made dream events for our customer base. Our customers enter orders (i.e., bookings) into our "state of the art" website. From then on, we need to communicate directly with our backend systems and provide information to the customer who entered the booking. On top of that, we have additional functionality to enhance the experience. This extra functionality allows us to report specific information to the client before the dream events truck shows up at the event location. To make this happen, we need to communicate to our own Order Management System that handles the orders (i.e., bookings) and stores metadata information on what truck is going to which event. The external company that supplies the people for the "dream event" must also retrieve the carrier information to be in time for the "dream event" at the correct location. See below for specifications.
20		-
	19	+As eMagiz Ltd. we want to directly receive & send information from/to an internal system responsible for the primary process. It concerns the OMS (Order Management system) that handles the Orders that are incoming from clients. eMagiz Ltd. has decide to expose API operation to their clients so that the message traffic is standardized and less manual intervention is required for the backoffice. See below for specifications.
	20	+
21	21	* OMS
22		- ** Retrieve carrier information. This information is relevant to understand what color the truck is on which the order is placed.
	22	+ ** Retrieve carrier information. This information is relevant to understand what color the truck is where the order is placed on.
23	23	** Send order. Clients can directly submit orders to eMagiz Ltd. in a digital manner
24	24
	25	+eMagiz Ltd. has two large clients that would start to use these operations. ACME requires the ability to submit orders, retrieve invoices and carriers. Street Smart requires access to all operations. Both clients can work with API keys for authentication purposes.
25	25
	27	+
26	26	)))((({{toc/}}))){{/container}}
27	27	{{/container}}