VideoClub / gen4

Your task is to generate a complete and diverse instance, in plain English, for a given category and based on a provided conceptual model description. The instance must adhere to these requirements: - Be self-contained: Include all required attributes, relationships, and related entities in full detail. - Conform to the model: Fulfill the constraints, multiplicities, relationships, and attributes defined in the class diagram model. - Understand the context: Ensure that its attributes and relationships are relevant. - Avoid duplication of instances: Take into consideration those instances previously built to avoid redundancy. - Semantic diversity: From a semantic point of view, incorporate varied scenarios, including regional, linguistic, or cultural differences. - Structural diversity: Include instances with different numbers of elements, different numbers of relationships and complexity, and create varied examples by changing entity attributes.

You are tasked with creating instances of a conceptual model in the UML-based Specification Environment (USE). You will receive: 1. The UML class diagram that the instance follows. 2. A sample syntax of instances creation. 3. A description of the instance that needs to be created.  Your goal is to generate these instances based on the provided description, adhering strictly to these requirements: - The output must be in plain text, with no additional comments, descriptions, or explanations. - Ensure that the created instance adheres to the provided description. - Follow the syntax sample provided, without deviation. - Take into account previously created instances to avoid using duplicate naming.

<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>

For the same category and model description, generate another instance that is structurally and semantically different from the previous ones

Continue with the following description, creating the instance according to the syntax example and this specification: 
## VideoClub Unique Baseline Instance

### Clients
- **Client:**
  - **Client ID:** 4589
  - **Is Suspended:** True

### Rentals
- **Rental 1:**
  - **Date:** "2023-03-05"

- **Rental 2:**
  - **Date:** "2023-03-05"

- **Rental 3:**
  - **Date:** "2023-10-01"

### Cassettes
- **Movie Cassette 1:**
  - **Title:** "Historical Heist"
  - **Available Copies:** 6
  - **Genre:** Action

- **Movie Cassette 2:**
  - **Title:** "Laughing Stock"
  - **Available Copies:** 4
  - **Genre:** Comedy

- **Series Cassette:**
  - **Title:** "Mystery Unveiled Season 4"
  - **Available Copies:** 1
  - **Episode:** 7

### Actors
- **Actor 1:**
  - **Name:** "Isabella Nguyen"

- **Actor 2:**
  - **Name:** "Samuel Ling"

- **Actor 3:**
  - **Name:** "Fatima Al-Hassan"

### Relationships

#### ClientRental Association
- **Client 4589:**
  - **Rental Dates:**
    - "2023-03-05"
    - "2023-03-05"
    - "2023-10-01"

#### RentalCassette Association
- **Rental Date "2023-03-05" (First):**
  - **Cassette Title:**
    - "Historical Heist"

- **Rental Date "2023-03-05" (Second):**
  - **Cassette Title:**
    - "Laughing Stock"

- **Rental Date "2023-10-01":**
  - **Cassette Title:**
    - "Mystery Unveiled Season 4" (Episode 7)

#### CassetteActor Association
- **Movie Cassette "Historical Heist":**
  - **Actors:**
    - Isabella Nguyen
    - Samuel Ling

- **Movie Cassette "Laughing Stock":**
  - **Actors:**
    - Samuel Ling
    - Fatima Al-Hassan

- **Series Cassette "Mystery Unveiled Season 4" (Episode 7):**
  - **Actors:**
    - Fatima Al-Hassan
    - Isabella Nguyen

### Description
This instance exemplifies a client with ID 4589, who is currently suspended. Despite this, the client has made complex rental choices on several occasions, including two rentals on the same day, "2023-03-05", which illustrates a scenario where multiple items might be rented at the same time. The first rental involves "Historical Heist," an action-filled movie with 6 available copies, while the second rental from the same date includes "Laughing Stock," a comedy with 4 available copies, offering a mix of entertainment genres. 

Later in the year, on "2023-10-01", the client selects "Mystery Unveiled Season 4" (Episode 7), a limited-copies series episode adding a sense of rarity and mystery. Actors Isabella Nguyen, Samuel Ling, and Fatima Al-Hassan interconnect through these cassettes, depicting a rich tapestry of talents ranging from action to comedic roles. The structurally complex instance demonstrates varied usage patterns, multiple rentals on the same day, and diverse actor engagements, maintaining all relationships and constraints outlined in the model.

<domain_model>
model VideoClub

dataType Date
operations
    Date(date : String)
end

enum Genre { 
    Action, 
    Comedy
}

class Client
attributes
    clientId : Integer
    isSuspended : Boolean
end

class Rental
attributes
    date : Date
end

class Cassette
attributes
    title : String
    availableCopies : Integer
end

class Movie < Cassette
attributes
    genre : Genre
end

class Series < Cassette
attributes
    episode : Integer
end

class Actor
attributes
    name : String
end

association ClientRental between
    Client [1] role assigned
    Rental [*] role gets
end

association RentalCassette between
    Rental [*] role borrowed
    Cassette [1..*] role borrows
end

association CassetteActor between
    Cassette [*] role actsIn
    Actor [1..*] role has
end

constraints
context Client inv positiveClientId:
    self.clientId > 0

context Cassette inv postiveAvailableCopies:
    self.availableCopies >= 0

context Series inv positiveEpisode:
    self.episode > 0
</domain_model>

<object_model>
!new Client('client16')
!client16.clientId := 4589
!client16.isSuspended := true

!new Rental('rental24')
!rental24.date := Date('2023-03-05')

!new Rental('rental25')
!rental25.date := Date('2023-03-05')

!new Rental('rental26')
!rental26.date := Date('2023-10-01')

!new Movie('movie20')
!movie20.title := 'Historical Heist'
!movie20.availableCopies := 6
!movie20.genre := #Action

!new Movie('movie21')
!movie21.title := 'Laughing Stock'
!movie21.availableCopies := 4
!movie21.genre := #Comedy

!new Series('series20')
!series20.title := 'Mystery Unveiled Season 4'
!series20.availableCopies := 1
!series20.episode := 7

!new Actor('actor37')
!actor37.name := 'Isabella Nguyen'

!new Actor('actor38')
!actor38.name := 'Samuel Ling'

!new Actor('actor39')
!actor39.name := 'Fatima Al-Hassan'

!insert (client16, rental24) into ClientRental
!insert (client16, rental25) into ClientRental
!insert (client16, rental26) into ClientRental

!insert (rental24, movie20) into RentalCassette
!insert (rental25, movie21) into RentalCassette
!insert (rental26, series20) into RentalCassette

!insert (movie20, actor37) into CassetteActor
!insert (movie20, actor38) into CassetteActor

!insert (movie21, actor38) into CassetteActor
!insert (movie21, actor39) into CassetteActor

!insert (series20, actor39) into CassetteActor
!insert (series20, actor37) into CassetteActor
</object_model>

Your task is to generate a complete and diverse instance, in plain English, for a given category and based on a provided conceptual model description. The instance must adhere to these requirements: - Be self-contained: Include all required attributes, relationships, and related entities in full detail. - Conform to the model: Fulfill the constraints, multiplicities, relationships, and attributes defined in the class diagram model. - Understand the context: Ensure that its attributes and relationships are relevant. - Avoid duplication of instances: Take into consideration those instances previously built to avoid redundancy. - Semantic diversity: From a semantic point of view, incorporate varied scenarios, including regional, linguistic, or cultural differences. - Structural diversity: Include instances with different numbers of elements, different numbers of relationships and complexity, and create varied examples by changing entity attributes.

You are tasked with creating instances of a conceptual model in the UML-based Specification Environment (USE). You will receive: 1. The UML class diagram that the instance follows. 2. A sample syntax of instances creation. 3. A description of the instance that needs to be created.  Your goal is to generate these instances based on the provided description, adhering strictly to these requirements: - The output must be in plain text, with no additional comments, descriptions, or explanations. - Ensure that the created instance adheres to the provided description. - Follow the syntax sample provided, without deviation. - Take into account previously created instances to avoid using duplicate naming.

<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>

For the same category and model description, generate another instance that is structurally and semantically different from the previous ones

Continue with the following description, creating the instance according to the syntax example and this specification: 
### Instance Description

#### Clients
- **Client4**: Named "Amina El-Tayeb", with a `clientId` of 500, illustrating mid-range typical user scenarios. Amina's `isSuspended` status is `false`, reflecting an engaged client actively participating in rentals without penalties.

#### Rentals
- **Rental6**: Dated "2024-04-15". This rental is characterized by involving a large batch of diverse cassettes, testing the upper limits of typical rental association multiplicities.
- **Rental7**: Dated "2024-04-25". A follow-up rental focusing on a unique series element, further pushing episodic engagement effects.

#### Cassettes
- **Movie4**: Titled "Desert Chronicles", classified under the `Action` genre, and with an `availableCopies` count of 2, balancing minimal inventory while sustaining client interest.
- **Movie5**: Titled "Comedy of Errors", in the `Comedy` genre, with `availableCopies` of 15 to simulate a high-demand comedy offering with sufficient stock prepared for increased engagements.
- **Series4**: Titled "Journey through Africa", involving an `episode` number of 10, indicating a mid-series depth exploring narrative progression, while having `availableCopies` of 0, capturing the intrigue surrounding popular yet temporarily unreachable series episodes.

#### Actors
- **Actor6**: Named "Kofi Agyeman", associated with both "Desert Chronicles" and "Journey through Africa", diversifying his roles between action and culturally-rich series narratives.
- **Actor7**: Named "Fatima Hassan", featuring in "Comedy of Errors", anchoring her talents within comedic story settings showing semantic breadth.

### Relationships and Structure
- Amina El-Tayeb's rental patterns reflect richly varied engagement across both diverse movie genres and multi-episodic series involvement, offering insights into processes where users balance these options extensively without overextending any relational bounds.

- Rental6 depicts a bundled engagement route where a mix of films captures Amina's simultaneous interest, testing the system's ability to manage cohesive media distribution and categorical rental diversity.

- Rental7 delves into singular episodic intrigue, utilizing a series-focused experience to stimulate further engagement beyond the typical movie-centric rental, challenging supply chains for popular content.

### Semantic Considerations
This scenario spans the expanse from high interest in captivating narratives to genre-specific engagements, with attention to the role of availability and popularity dynamics integral to the model. It exercises the balance of structured rental multiplicity and independence, enriching Amina's diverse cinematic journey through both expected and competitive media experiences. This iteration emphasizes aspects of renting dynamics, gratifying both genre depth and systemic handling of fluctuating inventory demands to increase operational versatility within the VideoClub's scope.

<domain_model>
model VideoClub

dataType Date
operations
    Date(date : String)
end

enum Genre { 
    Action, 
    Comedy
}

class Client
attributes
    clientId : Integer
    isSuspended : Boolean
end

class Rental
attributes
    date : Date
end

class Cassette
attributes
    title : String
    availableCopies : Integer
end

class Movie < Cassette
attributes
    genre : Genre
end

class Series < Cassette
attributes
    episode : Integer
end

class Actor
attributes
    name : String
end

association ClientRental between
    Client [1] role assigned
    Rental [*] role gets
end

association RentalCassette between
    Rental [*] role borrowed
    Cassette [1..*] role borrows
end

association CassetteActor between
    Cassette [*] role actsIn
    Actor [1..*] role has
end

constraints
context Client inv positiveClientId:
    self.clientId > 0

context Cassette inv postiveAvailableCopies:
    self.availableCopies >= 0

context Series inv positiveEpisode:
    self.episode > 0
</domain_model>

<object_model>
!new Client('client24')
!client24.clientId := 500
!client24.isSuspended := false

!new Rental('rental38')
!rental38.date := Date('2024-04-15')

!new Rental('rental39')
!rental39.date := Date('2024-04-25')

!new Movie('movie30')
!movie30.title := 'Desert Chronicles'
!movie30.availableCopies := 2
!movie30.genre := #Action

!new Movie('movie31')
!movie31.title := 'Comedy of Errors'
!movie31.availableCopies := 15
!movie31.genre := #Comedy

!new Series('series30')
!series30.title := 'Journey through Africa'
!series30.availableCopies := 0
!series30.episode := 10

!new Actor('actor59')
!actor59.name := 'Kofi Agyeman'

!new Actor('actor60')
!actor60.name := 'Fatima Hassan'

!insert (client24, rental38) into ClientRental
!insert (client24, rental39) into ClientRental

!insert (rental38, movie30) into RentalCassette
!insert (rental38, movie31) into RentalCassette

!insert (rental39, series30) into RentalCassette

!insert (movie30, actor59) into CassetteActor

!insert (movie31, actor60) into CassetteActor

!insert (series30, actor59) into CassetteActor
</object_model>

Your task is to generate a complete and diverse instance, in plain English, for a given category and based on a provided conceptual model description. The instance must adhere to these requirements: - Be self-contained: Include all required attributes, relationships, and related entities in full detail. - Conform to the model: Fulfill the constraints, multiplicities, relationships, and attributes defined in the class diagram model. - Understand the context: Ensure that its attributes and relationships are relevant. - Avoid duplication of instances: Take into consideration those instances previously built to avoid redundancy. - Semantic diversity: From a semantic point of view, incorporate varied scenarios, including regional, linguistic, or cultural differences. - Structural diversity: Include instances with different numbers of elements, different numbers of relationships and complexity, and create varied examples by changing entity attributes.

You are tasked with creating instances of a conceptual model in the UML-based Specification Environment (USE). You will receive: 1. The UML class diagram that the instance follows. 2. A sample syntax of instances creation. 3. A description of the instance that needs to be created.  Your goal is to generate these instances based on the provided description, adhering strictly to these requirements: - The output must be in plain text, with no additional comments, descriptions, or explanations. - Ensure that the created instance adheres to the provided description. - Follow the syntax sample provided, without deviation. - Take into account previously created instances to avoid using duplicate naming.

<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>

For the same category and model description, generate another instance that is structurally and semantically different from the previous ones

Continue with the following description, creating the instance according to the syntax example and this specification: 
## Unique Complex VideoClub Instance

### Entities

#### Clients
1. **Client:**
   - **clientId:** 701
   - **isSuspended:** False

2. **Client:**
   - **clientId:** 802
   - **isSuspended:** True

#### Rentals
1. **Rental:**
   - **date:** "2023-06-10"

2. **Rental:**
   - **date:** "2023-07-08"

3. **Rental:**
   - **date:** "2023-08-15"

4. **Rental:**
   - **date:** "2023-09-30"

#### Cassettes
1. **Movie:**
   - **title:** "Raging Rapids"
   - **availableCopies:** 4
   - **genre:** Action

2. **Movie:**
   - **title:** "Chuckle Island"
   - **availableCopies:** 0
   - **genre:** Comedy

3. **Series:**
   - **title:** "Ancient Treasures"
   - **availableCopies:** 5
   - **episode:** 12

4. **Series:**
   - **title:** "Galactic Stories"
   - **availableCopies:** 2
   - **episode:** 7

#### Actors
1. **Actor:**
   - **name:** "Miguel Flores"

2. **Actor:**
   - **name:** "Sophie Dubois"

3. **Actor:**
   - **name:** "Chen Wei"

4. **Actor:**
   - **name:** "Fatima Al-Shamari"

5. **Actor:**
   - **name:** "Alexios Papadopoulos"

### Relationships

#### ClientRental Association
- **Client 701** has the following rentals:
  - **Rental on 2023-06-10**
    - Involves:
      - **Raging Rapids**
      - **Ancient Treasures**

- **Client 802** has the following rentals:
  - **Rental on 2023-07-08**
    - Involves:
      - **Chuckle Island**
  - **Rental on 2023-08-15**
    - Involves:
      - **Galactic Stories**
  - **Rental on 2023-09-30**
    - Involves:
      - **Ancient Treasures**
      - **Raging Rapids**

#### RentalCassette Association
- **Rental on 2023-06-10** involves:
  - **Cassette:** Raging Rapids
  - **Cassette:** Ancient Treasures

- **Rental on 2023-07-08** involves:
  - **Cassette:** Chuckle Island

- **Rental on 2023-08-15** involves:
  - **Cassette:** Galactic Stories

- **Rental on 2023-09-30** involves:
  - **Cassette:** Ancient Treasures
  - **Cassette:** Raging Rapids

#### CassetteActor Association
- **Raging Rapids** includes actors:
  - Miguel Flores
  - Fatima Al-Shamari

- **Chuckle Island** includes actors:
  - Sophie Dubois
  - Alexios Papadopoulos

- **Ancient Treasures** includes actors:
  - Miguel Flores
  - Chen Wei
  - Fatima Al-Shamari

- **Galactic Stories** includes actors:
  - Sophie Dubois
  - Alexios Papadopoulos
  - Chen Wei

In this instance, we explore a new suspension status and manage rentals involving cassettes with temporarily depleted availability. The cultural diversity is reflected through actor nationalities and thematic content, with storylines spanning across space adventures, treasure hunts, and comedy on a fictional island. Actors are involved in multiple and geographically diverse projects, enhancing the semantic richness of the instance.

<domain_model>
model VideoClub

dataType Date
operations
    Date(date : String)
end

enum Genre { 
    Action, 
    Comedy
}

class Client
attributes
    clientId : Integer
    isSuspended : Boolean
end

class Rental
attributes
    date : Date
end

class Cassette
attributes
    title : String
    availableCopies : Integer
end

class Movie < Cassette
attributes
    genre : Genre
end

class Series < Cassette
attributes
    episode : Integer
end

class Actor
attributes
    name : String
end

association ClientRental between
    Client [1] role assigned
    Rental [*] role gets
end

association RentalCassette between
    Rental [*] role borrowed
    Cassette [1..*] role borrows
end

association CassetteActor between
    Cassette [*] role actsIn
    Actor [1..*] role has
end

constraints
context Client inv positiveClientId:
    self.clientId > 0

context Cassette inv postiveAvailableCopies:
    self.availableCopies >= 0

context Series inv positiveEpisode:
    self.episode > 0
</domain_model>

<object_model>
!new Client('client20')
!client20.clientId := 701
!client20.isSuspended := false

!new Client('client21')
!client21.clientId := 802
!client21.isSuspended := true

!new Rental('rental31')
!rental31.date := Date('2023-06-10')

!new Rental('rental32')
!rental32.date := Date('2023-07-08')

!new Rental('rental33')
!rental33.date := Date('2023-08-15')

!new Rental('rental34')
!rental34.date := Date('2023-09-30')

!new Movie('movie26')
!movie26.title := 'Raging Rapids'
!movie26.availableCopies := 4
!movie26.genre := #Action

!new Movie('movie27')
!movie27.title := 'Chuckle Island'
!movie27.availableCopies := 0
!movie27.genre := #Comedy

!new Series('series25')
!series25.title := 'Ancient Treasures'
!series25.availableCopies := 5
!series25.episode := 12

!new Series('series26')
!series26.title := 'Galactic Stories'
!series26.availableCopies := 2
!series26.episode := 7

!new Actor('actor48')
!actor48.name := 'Miguel Flores'

!new Actor('actor49')
!actor49.name := 'Sophie Dubois'

!new Actor('actor50')
!actor50.name := 'Chen Wei'

!new Actor('actor51')
!actor51.name := 'Fatima Al-Shamari'

!new Actor('actor52')
!actor52.name := 'Alexios Papadopoulos'

!insert (client20, rental31) into ClientRental

!insert (client21, rental32) into ClientRental
!insert (client21, rental33) into ClientRental
!insert (client21, rental34) into ClientRental

!insert (rental31, movie26) into RentalCassette
!insert (rental31, series25) into RentalCassette

!insert (rental32, movie27) into RentalCassette

!insert (rental33, series26) into RentalCassette

!insert (rental34, series25) into RentalCassette
!insert (rental34, movie26) into RentalCassette

!insert (movie26, actor48) into CassetteActor
!insert (movie26, actor51) into CassetteActor

!insert (movie27, actor49) into CassetteActor
!insert (movie27, actor52) into CassetteActor

!insert (series25, actor48) into CassetteActor
!insert (series25, actor50) into CassetteActor
!insert (series25, actor51) into CassetteActor

!insert (series26, actor49) into CassetteActor
!insert (series26, actor52) into CassetteActor
!insert (series26, actor50) into CassetteActor
</object_model>

Your task is to generate a complete and diverse instance, in plain English, for a given category and based on a provided conceptual model description. The instance must adhere to these requirements: - Be self-contained: Include all required attributes, relationships, and related entities in full detail. - Conform to the model: Fulfill the constraints, multiplicities, relationships, and attributes defined in the class diagram model. - Understand the context: Ensure that its attributes and relationships are relevant. - Avoid duplication of instances: Take into consideration those instances previously built to avoid redundancy. - Semantic diversity: From a semantic point of view, incorporate varied scenarios, including regional, linguistic, or cultural differences. - Structural diversity: Include instances with different numbers of elements, different numbers of relationships and complexity, and create varied examples by changing entity attributes.

You are tasked with creating instances of a conceptual model in the UML-based Specification Environment (USE). You will receive: 1. The UML class diagram that the instance follows. 2. A sample syntax of instances creation. 3. A description of the instance that needs to be created.  Your goal is to generate these instances based on the provided description, adhering strictly to these requirements: - The output must be in plain text, with no additional comments, descriptions, or explanations. - Ensure that the created instance adheres to the provided description. - Follow the syntax sample provided, without deviation. - Take into account previously created instances to avoid using duplicate naming.

<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>

For the same category and model description, generate another instance that is structurally and semantically different from the previous ones

Continue with the following description, creating the instance according to the syntax example and this specification: 
### Edge Case Instance: The Single Actor, Multiple Genres Phenomenon

#### Date Instance
- **Date:** "2023-12-05"

#### Client Class
1. **Name:** Zhen Wei
   - **clientId:** 999
   - **isSuspended:** False
   - **Rentals:**

#### Rental Class
1. **Rental Date:** "2023-12-05"
   - **Associated Client:** Zhen Wei
   - **Cassettes Involved:**
     - "Echoes of the Ancients"
     - "Last Laugh Chronicles"

#### Cassette and Derived Classes

1. **Movie:**
   - **Title:** "Echoes of the Ancients"
   - **availableCopies:** 2
   - **genre:** Action
   - **Associated Actors:** 
     - Amir Khan

2. **Movie:**
   - **Title:** "Last Laugh Chronicles"
   - **availableCopies:** 10
   - **genre:** Comedy
   - **Associated Actors:** 
     - Amir Khan
     - Sofia Lopez

#### Actor Class

1. **Actor Name:** Amir Khan
   - **Associated Cassettes:** 
     - "Echoes of the Ancients"
     - "Last Laugh Chronicles"

2. **Actor Name:** Sofia Lopez
   - **Associated Cassettes:**
     - "Last Laugh Chronicles"

#### Description:

In this "Single Actor, Multiple Genres Phenomenon," Zhen Wei engages with a unique collection bridging both the fierce action in "Echoes of the Ancients" and the humor capture in "Last Laugh Chronicles." This example highlights Amir Khan, a rare actor depicting versatility by featuring prominently as the sole common actor across distinct genres, embodying both intense action and light-hearted comedic roles.

This instance explores the uncommonly encountered scenario where one actor dominates multiple genres, providing diverse audience engagement. Zhen Wei's rental mix displays a blend of rich narratives, uncommon in traditional collections, yet illustrating evolving cinematic universes with actors seamlessly transitioning between genre boundaries without losing character depth or filmic quality. This reveals the industry's openness to varied actor roles across contrasting storylines, highlighting Amir Khan's diversified filmography alongside Sofia Lopez’s comedic talent.

<domain_model>
model VideoClub

dataType Date
operations
    Date(date : String)
end

enum Genre { 
    Action, 
    Comedy
}

class Client
attributes
    clientId : Integer
    isSuspended : Boolean
end

class Rental
attributes
    date : Date
end

class Cassette
attributes
    title : String
    availableCopies : Integer
end

class Movie < Cassette
attributes
    genre : Genre
end

class Series < Cassette
attributes
    episode : Integer
end

class Actor
attributes
    name : String
end

association ClientRental between
    Client [1] role assigned
    Rental [*] role gets
end

association RentalCassette between
    Rental [*] role borrowed
    Cassette [1..*] role borrows
end

association CassetteActor between
    Cassette [*] role actsIn
    Actor [1..*] role has
end

constraints
context Client inv positiveClientId:
    self.clientId > 0

context Cassette inv postiveAvailableCopies:
    self.availableCopies >= 0

context Series inv positiveEpisode:
    self.episode > 0
</domain_model>

<object_model>
!new Client('client25')
!client25.clientId := 999
!client25.isSuspended := false

!new Rental('rental40')
!rental40.date := Date('2023-12-05')

!new Movie('movie32')
!movie32.title := 'Echoes of the Ancients'
!movie32.availableCopies := 2
!movie32.genre := #Action

!new Movie('movie33')
!movie33.title := 'Last Laugh Chronicles'
!movie33.availableCopies := 10
!movie33.genre := #Comedy

!new Actor('actor61')
!actor61.name := 'Amir Khan'

!new Actor('actor62')
!actor62.name := 'Sofia Lopez'

!insert (client25, rental40) into ClientRental

!insert (rental40, movie32) into RentalCassette
!insert (rental40, movie33) into RentalCassette

!insert (movie32, actor61) into CassetteActor

!insert (movie33, actor61) into CassetteActor
!insert (movie33, actor62) into CassetteActor
</object_model>

Your task is to generate a complete and diverse instance, in plain English, for a given category and based on a provided conceptual model description. The instance must adhere to these requirements: - Be self-contained: Include all required attributes, relationships, and related entities in full detail. - Conform to the model: Fulfill the constraints, multiplicities, relationships, and attributes defined in the class diagram model. - Understand the context: Ensure that its attributes and relationships are relevant. - Avoid duplication of instances: Take into consideration those instances previously built to avoid redundancy. - Semantic diversity: From a semantic point of view, incorporate varied scenarios, including regional, linguistic, or cultural differences. - Structural diversity: Include instances with different numbers of elements, different numbers of relationships and complexity, and create varied examples by changing entity attributes.

You are tasked with creating instances of a conceptual model in the UML-based Specification Environment (USE). You will receive: 1. The UML class diagram that the instance follows. 2. A sample syntax of instances creation. 3. A description of the instance that needs to be created.  Your goal is to generate these instances based on the provided description, adhering strictly to these requirements: - The output must be in plain text, with no additional comments, descriptions, or explanations. - Ensure that the created instance adheres to the provided description. - Follow the syntax sample provided, without deviation. - Take into account previously created instances to avoid using duplicate naming.

<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>

For the same category and model description, generate another instance that is structurally and semantically different from the previous ones

Continue with the following description, creating the instance according to the syntax example and this specification: 
**Overconstrained Scenario: Community-Driven Film Restoration Event**

In this scenario, we examine a grassroots effort in South America aimed at restoring and showcasing classic films within the local community. These initiatives often function outside the traditional rental paradigms, revealing potential rigidity in the VideoClub model.

**Entities:**

1. **Client:**
   - `clientId`: 300
   - `isSuspended`: False

2. **Rental:**
   - `date`: "2023-08-10"

3. **Movies:**
   - Title: "The Andes Echo"
     - `availableCopies`: 0
     - `genre`: "Action" (depicting traditional celebrations and narratives)

4. **Series:**
   - Title: "Savannah Chronicles"
     - `availableCopies`: 2
     - `episode`: 5

5. **Actors:**
   - Name: "Luis Miranda" (involved in community-led projects)
   - Name: "Gabriela Sánchez" (unlinked, portraying flexibility in participation)

**Situation Overview:**

- **ClientRental Association:**
  - **Client (1):** The client with `clientId` 300 is part of the event's volunteer team, who do not engage in traditional rentals but facilitate community sessions, presenting a valid social participation angle not covered by existing rental-oriented constraints.

- **RentalCassette Association:**
  - **Rental (0):** Rentals are not transactional but are part of a curated exhibition series throughout the region, catering to local access only and not aligning with the traditional model assumption.
  - **Cassette (0):** Showcases involve digital versions effectively screened at events with no rental circulation, bypassing `Cassette [1..*]`, under accepted fair use for educational and restoration purposes.

- **CassetteActor Association:**
  - **Community Engagement with No Consistent Actor Line-up:** Historic restoration often includes narratives without formal actors, showcasing traditional storytelling, challenging actor link mandates.
  - **Selected Actor For Restoration Projects Only:** Featuring Luis Miranda only, reflecting non-standardized roles in restoration initiatives, illuminating flexibility outside commercial constraints.

**Model Violation Highlights:**

- **No Rentals for Volunteers:** Engages volunteers' participation in non-remunerative or rental-based involvement, challenging the structured client to rental mapping.
- **Digital-Only Exhibitions:** Expresses flexibility towards format variations, advocating for non-rentable intangible screenings, defying `Rental [1..*]`.
- **Actor Non-Engagement in Certain Screenings:** Clarifying local non-commercial storytelling's place in the community viewership approach, contesting always-linked actor roles.

This instance emphasizes the diversity and adaptability required in multimedia systems that engage local communities through non-traditional and non-commercial pathways, identifying potential oversights in the rigidity of the initial model.

<domain_model>
model VideoClub

dataType Date
operations
    Date(date : String)
end

enum Genre { 
    Action, 
    Comedy
}

class Client
attributes
    clientId : Integer
    isSuspended : Boolean
end

class Rental
attributes
    date : Date
end

class Cassette
attributes
    title : String
    availableCopies : Integer
end

class Movie < Cassette
attributes
    genre : Genre
end

class Series < Cassette
attributes
    episode : Integer
end

class Actor
attributes
    name : String
end

association ClientRental between
    Client [1] role assigned
    Rental [*] role gets
end

association RentalCassette between
    Rental [*] role borrowed
    Cassette [1..*] role borrows
end

association CassetteActor between
    Cassette [*] role actsIn
    Actor [1..*] role has
end

constraints
context Client inv positiveClientId:
    self.clientId > 0

context Cassette inv postiveAvailableCopies:
    self.availableCopies >= 0

context Series inv positiveEpisode:
    self.episode > 0
</domain_model>

<object_model>
!new Client('client23')
!client23.clientId := 300
!client23.isSuspended := false

!new Rental('rental37')
!rental37.date := Date('2023-08-10')

!new Movie('movie29')
!movie29.title := 'The Andes Echo'
!movie29.availableCopies := 0
!movie29.genre := #Action

!new Series('series29')
!series29.title := 'Savannah Chronicles'
!series29.availableCopies := 2
!series29.episode := 5

!new Actor('actor57')
!actor57.name := 'Luis Miranda'

!new Actor('actor58')
!actor58.name := 'Gabriela Sánchez'

!insert (client23, rental37) into ClientRental

!insert (rental37, movie29) into RentalCassette
!insert (rental37, series29) into RentalCassette

!insert (movie29, actor57) into CassetteActor
!insert (series29, actor57) into CassetteActor
</object_model>