Suitcase domain model

[mihh-don]

Create ER diagram for the Suitcase domain:

• Abstract Entity (general entity): ID, version, created by, created on, changed by, changed on
• User: username, password, creation date, email
• Baggage Item: object name, category, type, description, dimensions, weight, color, (default) priority
• Baggage Container (is a Baggage Item): capacity, set of items
  • a suitcase is also a baggage container
• Composite Baggage Item (is a Baggage Item): multiple items tightly connected together to be considered as one (e.g. socks covering and protecting mugs)
  • splitting and merging items should be possible
  • consider making these objects immutable (like Strings)
• User <-> Baggage Item relationship: set of all baggage items, users they belong to (m to n)
• Transport Carrier: name, mean of transport, set of baggage policies (1 to n)
• Travel Details: season, start date, end date, duration (derived), last notification date, purpose, list of transport carriers
• Transport Carrier <-> Travel Details:
  • many to many relationship
  • Travel Class has to be added for each Transport Carrier: Economy, Business, First etc.
  • sequence of Transport Carriers to be added, to keep them in order
• Baggage policies: transport carrier, not allowed items, item restrictions, allowed item types, allowed count
• Travel Baggage Item: references the Baggage Item (many to one) and the current travel plan (many to one), priority
  • it is a many to many relationship between Travel Plan and Baggage Item
  • priority has to be added as it might be different than the default one
  • container type should be specified, for the items used as Baggage Containers during this Travel Plan: hand baggage, checked baggage, cabin baggage
• Travel Plan: Travel details, Travel Baggage Items, notification flag
• User will have a set of Travel Plans (1 to n)

[mihh-don]

More about Baggage Items:

• types: Liquid, Aerosol, Gas, Gel, Powder, Solid
• categories: shoes, underwear, toiletries & medicine, jewelry, clothes, hats, scarfs, accessories, documents, notebooks, pens, bags, electronics, electronic accessories, personal electronic devices (laptops, tablets etc.), keys & other house tools, general food, baby food, edible oils (olive oil, rapeseed oil etc.), medicine, alcoholic drinks, non alcoholic drinks, dishes, cutlery, toys & games, books & magazines, packaging material, vehicles (bikes, scooters etc), battery operated vehicles (hover-boards, segways, e-bikes, e-scooters etc.), wheelchairs, medical devices, sporting equipment (not included in clothes and accessories), pets, plants, musical instruments, firearms and ammunition, gases, explosives, flammable substances, oxidizers, corrosives, chemical substances, toxic substances, cigarettes, e-cigarettes, other
• object name: bike, toothbrush, knife, mug, popcorn etc
• priority: need, want, not required, not applicable
• color:
  • combination: mono, duo, multi
  • primary color (used in all 3 combinations)
  • secondary color (not required for mono)

[mihh-don]

More about Travel Plan:

• Travel Details:
  • season: summer, winter, spring, autumn
  • start and end date will determine the duration of the trip
  • end date can be left blank (e.g. for relocation) -> duration will be indeterminate
  • purpose: study, business, leisure, relocation
  • means of transport: airplane, helicopter, train, ship, boat, car, bus, truck, motorcycle, bicycle, other
  • there can be more means of transport for the same journey
  • one transport mode can be used for multiple travel details
  • many to many relationship
• notification date: date set when the user was notified about the upcoming trip (3 days before)
  • can be extended later

[mihh-don]

All the 'reusable' Entities should be stored as Master Data inside the domain model. The user can make a request to add new values, in case something is missing. Duplicates or incorrect values should be avoided. These Entities include:

• Baggage Item
• Transport Carrier
• Baggage Policies

[mihh-don]

More about Baggage Policies:

• many to one relationship to Transport Carrier
• some policies refer generally to types or categories of items, therefore the Baggage Policies can be sub-classed by: Baggage Item Policy, Baggage Type Policy, Baggage Category Policy
• Baggage Container Type where this policy applies (e.g. hand baggage, checked baggage)
• allowance: unrestricted, not allowed, limited amount, limited quantity, limited weight, extra fee, securely wrapped
• allowed amount (within the whole Baggage Container)
• allowed quantity dimensions (within the whole Baggage Container)
• allowed weight (usually applies to the Baggage Container)
• name
• observations
• sequence, sometimes the order of policies for a certain Transport Carrier can be important (e.g. first checked bag included in price, second bag at extra fee)
• Travel Class: Economy, Business, First etc.

[mihh-don]

It would be good to keep the Master Data separate from the rest of the Entities in the Domain Model. These Entities can be grouped inside a Catalog. The m-to-n relationships will be then broken into 1-to-n relationships, with just a reference to the Master Entity from the Catalog.

[mihh-don]

ER Diagram