Business case

Last modified by Erik Bakker on 2023/05/01 10:46

With this exercise, we start our journey into the eMagiz platform. This exercise will explain the business case used throughout all exercises linked to this Crash Course. In the following exercises, we will guide you step by step through the platform so you can learn how to use it.
 
Should you have any questions, please contact academy@emagiz.com.

1. Prerequisites

2. Exercise

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.

2.1 Business Case

Read and understand the following business case

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.

  • OMS
    • Retrieve carrier information. This information is relevant to understand what color the truck is on which the order is placed.
    • Send order. Clients can directly submit orders to eMagiz Ltd. in a digital manner