Skip to main content

Task

Being a framework based on a "low code" approach, you might be tempted to start working with the ADITO Designer right away. However, this is not recommended, as it can lead to an incomplete or suboptimal project structure.

Therefore, your first task is to take a white sheet of paper (or a suitable digital tool) and design an Entity structure on the basis of the requirements given in chapter "Introduction". Collect a list of all data you want to manage via ADITO, and then structure it carefully into logical units with all required features.

Solution

CAR:

  • Car ID (autogenerated)
  • Manufacturer (mandatory)
  • Type (mandatory)
  • Color
  • Date of Manufacture
  • Picture
  • Price
  • Currency
  • License plate number
  • Mileage (calculated from previous car reservation)
  • Value (calculated from price, mileage, and damages)
  • Availability ("available"/"lent", dependent on car reservation)
  • Damages (calculated from reservations - simply concat single damages)

CAR DRIVER:

  • Car driver ID (autogenerated)
  • Contact ID (related to xRM Entity "Person_entity", mandatory)
  • Age (calculated from date of birth, via Contact ID)
  • Number of driving license (mandatory)
  • issue date of driving license (mandatory)
  • Driving experience (calculated from issue date)
  • Sum of parking ticket fines (calculated from car reservations)
  • Sum of speeding fines (calculated from car reservations)

CAR RESERVATION:

  • Car reservation ID (autogenerated)
  • Car driver ID (mandatory; related to business object "Car driver")
  • Car ID (mandatory; related to business object "Car")
  • Start date (mandatory)
  • End date (mandatory)
  • Mileage at start (calculated from car reservation)
  • Mileage at return
  • Damage
  • Parking ticket fine
  • Speeding fine
  • Currency