Restaurant / gen19

!new Restaurant('restaurant19')
!restaurant19.name := 'Nebula Nosh'

!new Owner('owner38')
!owner38.name := 'Orion Star'
!owner38.percentageShares := 60
!insert (restaurant19, owner38) into RestaurantOwner

!new Owner('owner39')
!owner39.name := 'Luna Eclipse'
!owner39.percentageShares := 40
!insert (restaurant19, owner39) into RestaurantOwner

!new Table('table54')
!table54.number := 54
!table54.description := 'Celestial Stand'
!table54.capacity := 4

!new Table('table55')
!table55.number := 55
!table55.description := 'Comets Belt'
!table55.capacity := 25

!new RegularCustomer('customer20')
!customer20.name := 'Stella Moonbeam'
!customer20.prefferedLanguage := #German

!new Waiter('waiter21')
!waiter21.name := 'Galaxy Swift'
!waiter21.dateOfBirth := Date('1989-05-05')
!waiter21.phoneNumber := '555-3421'
!waiter21.spokenLanguage := #English

!new HeadWaiter('headwaiter19')
!headwaiter19.name := 'Sol Celestia'
!headwaiter19.dateOfBirth := Date('1984-11-15')
!headwaiter19.phoneNumber := '555-6789'

!insert (headwaiter19, waiter21) into HeadWaiterWaiter

!new Individual('reservation35')
!reservation35.time := Time('20:15')
!reservation35.date := Date('2024-10-25')
!reservation35.numberPeople := 2
!reservation35.name := 'Stella Moonbeam'
!reservation35.phoneNumber := '555-9876'
!reservation35.number := 35
!reservation35.seating := #Inside
!reservation35.smoking := #NonSmoking
!insert (restaurant19, reservation35) into RestaurantReservation
!insert (reservation35, customer20) into ReservationCustomer
!insert (reservation35, waiter21) into ReservationWaiter
!insert (reservation35, table54) into ReservationTable

!new Banquet('reservation36')
!reservation36.time := Time('21:00')
!reservation36.date := Date('2023-12-31')
!reservation36.numberPeople := 50
!reservation36.name := 'Ecliptic Celebration'
!reservation36.phoneNumber := '555-5656'
!reservation36.number := 36
!reservation36.groupName := 'Lunar League'
!reservation36.paymentMethod := #Cash
!reservation36.busService := true
!insert (restaurant19, reservation36) into RestaurantReservation
!insert (reservation36, table55) into ReservationTable

!new Table('tableExtra13')
!tableExtra13.number := 56
!tableExtra13.description := 'Starlight Stage'
!tableExtra13.capacity := 30
!insert (reservation36, tableExtra13) into ReservationTable
!insert (reservation36, waiter21) into ReservationWaiter

!new BusDriver('busdriver13')
!busdriver13.name := 'Haley Nebula'
!busdriver13.dateOfBirth := Date('1965-09-09')
!busdriver13.phoneNumber := '555-4545'
!busdriver13.driverLicenseNr := 'DL789012'
!insert (reservation36, busdriver13) into BanquetBusDriver

!new ItemOrder('itemOrder19')
!itemOrder19.time := Time('20:45')
!insert (reservation35, itemOrder19) into ReservationItemOrdered

!new MenuItem('menuItem19')
!menuItem19.description := 'Cosmic Crepes'
!menuItem19.prepTime := 20.0
!menuItem19.classification := #Dessert
!insert (itemOrder19, menuItem19) into ItemOrderMenuItem

!new FoodItem('foodItem19')
!foodItem19.number := 119
!foodItem19.description := 'French Crepes'
!foodItem19.purchaseFlag := true
!foodItem19.unit := #Sheet
!insert (menuItem19, foodItem19) into MenuItemFoodItem

!new Allergen('allergen19')
!allergen19.type := #Gluten
!insert (foodItem19, allergen19) into FoodItemAllergen

!new Cook('cook19')
!cook19.name := 'Aurora Bright'
!cook19.dateOfBirth := Date('1993-03-03')
!cook19.phoneNumber := '555-1212'
!cook19.yearsOfExperience := 6

!new Chef('chef19')
!chef19.name := 'Meteor Flash'
!chef19.dateOfBirth := Date('1986-07-30')
!chef19.phoneNumber := '555-3434'
!insert (menuItem19, chef19) into MenuItemChef
!insert (chef19, cook19) into ChefCook

model Restaurant

dataType Date
operations
    Date (date : String)
end

dataType Time
operations
   Time (time : String)
end

enum SeatingPreference {
    Inside,
    Patio
}

enum SmokingPreference {
    Smoking,
    NonSmoking
}

enum PaymentMethod {
    Cash,
    CreditCard
}

enum ItemType {
    Apetizer,
    Main,
    Dessert,
    Beverage
}

enum UnitOfMeasure {
    Ounce,
    Sheet,
    Pound,
    Gram,
    Dozen
}

enum AllergenType {
    Lactose,
    Seafood,
    Nuts,
    Gluten
}

enum Diet {
    Vegetarian,
    Vegan,
    Kosher,
    Halal
}

enum Language {
    English,
    Spanish,
    German,
    Italian
}

class Restaurant
attributes
    name : String
end

abstract class Reservation
attributes
    time : Time
    date : Date
    numberPeople : Integer
    name : String
    phoneNumber : String
    number : Integer
end

class Individual < Reservation
attributes
    seating : SeatingPreference
    smoking : SmokingPreference
end

class Banquet < Reservation
attributes
    groupName : String
    paymentMethod : PaymentMethod
    busService : Boolean
end

class Table
attributes
	number : Integer
    description : String
    capacity : Integer
end

class ItemOrder
attributes
    time : Time
end

class MenuItem
attributes
    description : String
    prepTime : Real
    classification : ItemType
end

class FoodItem
attributes
    number : Integer
    description : String
    purchaseFlag : Boolean
    unit : UnitOfMeasure
end

class Allergen
attributes
    type : AllergenType
end

class Person
attributes
	name : String
end

class Owner < Person
attributes
	percentageShares : Integer
end

class RegularCustomer < Person
attributes
	prefferedLanguage : Language
end

class DietaryRequirement
attributes
	diet : Diet
end

class ReportedAllergy
attributes
	allergen : AllergenType
end

abstract class Worker < Person
attributes
	dateOfBirth : Date
    phoneNumber : String
end

class HeadWaiter < Worker
end

class Waiter < Worker
attributes
    spokenLanguage : Language
end

class Manager < Worker
end

class Cook < Worker
attributes
    yearsOfExperience : Integer
end

class Chef < Worker
end

class BusDriver < Worker
attributes
    driverLicenseNr : String
end


association RestaurantOwner between
    Restaurant [1..*]
    Owner [1..*]
end

association RestaurantReservation between
    Restaurant [0..1]
    Reservation [0..*]
end

association ReservationCustomer between
    Reservation [0..*]
    RegularCustomer [0..1]
end

association ReservationWaiter between
    Reservation [*]
    Waiter [1..*] role servedBy
 end

association BanquetBusDriver between
    Banquet [1]
    BusDriver [0..*]
end

association ReservationTable between
    Reservation [1]
    Table [1..*] role assignedTo
end

association ReservationItemOrdered between
    Reservation [1]
    ItemOrder [0..*]
end

association ItemOrderMenuItem between
    ItemOrder [*]
    MenuItem [1] role item
end

association MenuItemFoodItem between
    MenuItem [*] role isUtilized
    FoodItem [*] role utilizes
end

association FoodItemAllergen between
    FoodItem [*]
    Allergen [*] role contains
end

association MenuItemChef between
    MenuItem [*] role designs
    Chef [1] role designedBy
end

association ChefCook between
    Chef [1] role underSupervisionOf
    Cook [1..*] role supervises
end

association HeadWaiterWaiter between
    HeadWaiter [1]
    Waiter [1..*] role responsibleFor
end


constraints
context Table inv PositiveCapacity:
    self.capacity > 0

context Cook inv PositiveExperience:
    self.yearsOfExperience >= 0

context Restaurant inv TotalOwnerShares:
    self.owner -> collect(o | o.percentageShares) -> sum() = 100

context Reservation inv TablesCapacityGreaterThanPeople:
    self.assignedTo -> collect(t | t.capacity) -> sum() >= self.numberPeople

Given a conceptual model expressed in the UML-based Specification Environment (USE), your task is to generate valid and realistic instances that conform to the provided model. <requirements> - Instances must be syntactically correct according to the USE syntax_reference. - Avoid unnecessary comments and output the instance in plain text (i.e., not markdown). - Make sure instances fulfill all the model's constraints, and that multiplicities, relationships, and attributes are valid and realistic. - Provide multiple instances with diverse data values and structure. </requirements>  <syntax_reference> Here there is a snippet showing how to create objects and set values in the specific .soil language required: -- This is a comment example  -- Primitive data types:     -- Integer i.e. 1, 2, 3, etc.     -- Real i.e. 1.0, 21.89, 322.05556, etc.     -- Boolean i.e. true or false     -- String i.e. 'Hello World'  -- You can create instances with the following syntax: !new <instance type>('<instance name>') -- Example: !new Client('client1') !new Store('store4')  -- You can assign values to attributes for a created instance with the following syntax: !<instance name>.<attribute name> := <value> -- Example for different data types: !client1.clientId := 1 -- For Integer !client1.balance := 1123.45 -- For Real !client1.name := 'John' -- For Strings !store4.available := true -- For Boolean  -- You can create associations between instances with the following syntax: !insert (<instance name1>, <instance name2>) into <association name> -- Example: !insert (client1, store4) into ClientStore  -- Custom data types usage:     -- dataType Location     -- operations     --   Location(x : Real, y : Real)     --   some other operations     -- end -- You can create custom data types by calling the constructor directly; in this case, the constructor of Location requires two arguments: x and y of type Real. So it can be used as follows: !store4.location := Location(14.0, 289.0)  -- Enums usage:     -- enum Type { Clothes, Shoes } -- Can be used as follows: !store4.type := #Clothes </syntax_reference>

<role>
You are an expert software and system modeler. You are able to assess the semantic quality of object models that have been created to conform to a domain model. The models are defined in USE (UML-based Specification Environment) and OCL (Object Constraint Language).

Your primary capability is "Semantic Reality Checking". You do not just check for syntactic correctness; you check for real-world plausibility and logical consistency within a given domain.
</role>

<context>
The user will provide two types of content:
1. **Domain Model (.use)**: A class diagram definition including classes, attributes, enums, relationships, multiplicities and roles.
2. **Object Model (.soil)**: An object model. This object model can be seen as a script composed of instructions for the creation of objects, relationships and setting attribute values (snapshot).

Your goal is to act as a judge to determine if the object model represents a **REALISTIC** scenario based on the domain model and common sense real-world logic.
</context>

<definitions>
- **Realistic**: The object model is syntactically correct AND semantically plausible (e.g., A 'Person' has an age between 0 and 120; a 'Car' has a positive price).
- **Unrealistic**: The object model contains contradictions, impossible physical values, or nonsensical relationships (e.g., A 'Person' is their own father; a 'Product' has a negative weight).
- **Doubtful**: You cannot determine whether the object model is realistic or not.
</definitions>

<instructions>
Follow this thinking process strictly before generating the final output:

1. **Analyze the Domain (.use)**: Understand the classes and what they represent in the real world.
2. **Analyze the Instances (.soil)**: Map the created objects to their classes. Look at the specific values assigned to attributes and the relationships created between objects.
3. **Evaluate Semantics**:
    - Apply "Common Sense Knowledge" to the attribute values.
    - Check cardinality and relationship logic beyond simple OCL constraints.
    - Identify any outliers or logical fallacies.
4. **Determine Verdict**: Select one of the defined labels (Realistic/Unrealistic/Doubtful).
</instructions>

<constraints>
- **Tone**: Objective, Analytical, Technical.
- **Verbosity**: Low. Be direct.
- **Reasoning**: The "Why" section must be concise and specific, citing variable names, objects, or relationships when possible.
- Do not output the internal thinking process. Only output the final formatted result.
</constraints>

<output_format>
Structure your response exactly as follows:

**Response**: [Realistic | Unrealistic | Doubtful]
**Why**: [Concise explanation of your reasoning. If Unrealistic, specify the exact objects, values or relationships that break realism.]
</output_format>

<examples>
Example 1:
Input:

<domain_model>
class Person
attributes
    age: Integer
end
class Pet
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Pet [*] role pets
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 250
!new Pet('pet1')
!pet1.name := 'Luna'
… 1.000 more pets creation …
!pet1000.name := 'Max'
!insert (p1, pet1) into Ownership
…1.000 more pets associated with p1 …
!insert (p1, pet1000) into Ownership
</object_model>

Output:

**Response**: Unrealistic
**Why**: The object 'p1' of class 'Person' has an age of 250, which exceeds the biologically plausible lifespan of a human. Although it is not plausible that 1 same person owns 1.000 pets.


Example 2:
Input:

<domain_model>
class Car
attributes
    brand: String
end
class Person
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Car [*] role cars
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 19
!new Car('c1')
!c1.brand := 'Toyota'
!insert (p1, c1) into Ownership
</object_model>

Output:

**Response**: Realistic
**Why**: The object 'c1' has a valid, recognized real-world car brand assigned, and its plausible that a teenager has only one car.


Example 3:
Input:

<domain_model>
class Component
attributes
    setting_val: Integer
    config_mode: String
end
</domain_model>
<object_model>
!new Component('c1')
!c1.setting_val := 8080
!c1.config_mode := 'Legacy'
</object_model>

Output:

**Response**: Doubtful
**Why**: The class 'Component' and attribute 'setting_val' are generic and lack specific real-world semantic context. Without knowing what specific physical or software system this represents, it is impossible to determine if '8080' is a realistic value or an outlier.

</examples>