VideoClub / gen2

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 Alternative Baseline Instance

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

### Rentals
- **Rental:**
  - **Date:** "2023-09-10"

### Cassettes
- **Movie Cassette:**
  - **Title:** "Galactic Warriors"
  - **Available Copies:** 7
  - **Genre:** Action

- **Series Cassette 1:**
  - **Title:** "Detective Chronicles Season 1"
  - **Available Copies:** 2
  - **Episode:** 1

- **Series Cassette 2:**
  - **Title:** "Detective Chronicles Season 1"
  - **Available Copies:** 2
  - **Episode:** 2

### Actors
- **Actor 1:**
  - **Name:** "Miguel Sanchez"

- **Actor 2:**
  - **Name:** "Yuki Nakamura"

- **Actor 3:**
  - **Name:** "Ethan Thompson"

### Relationships

#### ClientRental Association
- **Client 2047:**
  - **Rental Date:** "2023-09-10"

#### RentalCassette Association
- **Rental Date "2023-09-10":**
  - **Cassette Titles:**
    - "Galactic Warriors"
    - "Detective Chronicles Season 1" (Episode 1)
    - "Detective Chronicles Season 1" (Episode 2)

#### CassetteActor Association
- **Movie Cassette "Galactic Warriors":**
  - **Actors:**
    - Miguel Sanchez
    - Yuki Nakamura

- **Series Cassette "Detective Chronicles Season 1" (Episode 1 and 2):**
  - **Actors:**
    - Ethan Thompson
    - Yuki Nakamura

### Description
In this alternative instance, we have a different client who is currently suspended with a client ID of 2047, representing a realistic scenario where a client may not be able to rent further until resolved. This client has rented both a thrilling action movie "Galactic Warriors" and the first two episodes of a detective series titled "Detective Chronicles Season 1", all on the same date "2023-09-10". "Galactic Warriors" has 7 available copies, indicating a popular choice. The detective series copies are limited, with only 2 available per episode, highlighting its exclusivity or high demand. 

Miguel Sanchez and Yuki Nakamura star in the action movie, adding international diversity to the actor list. Ethan Thompson joins Yuki Nakamura for the series episodes, showcasing a varied cast. Every association between entities is coherent and adheres to the constraints defined, illustrating a different yet feasible scenario within the video rental framework.

<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('client7')
!client7.clientId := 2047
!client7.isSuspended := true

!new Rental('rental8')
!rental8.date := Date('2023-09-10')

!new Movie('movie9')
!movie9.title := 'Galactic Warriors'
!movie9.availableCopies := 7
!movie9.genre := #Action

!new Series('series7')
!series7.title := 'Detective Chronicles Season 1'
!series7.availableCopies := 2
!series7.episode := 1

!new Series('series8')
!series8.title := 'Detective Chronicles Season 1'
!series8.availableCopies := 2
!series8.episode := 2

!new Actor('actor16')
!actor16.name := 'Miguel Sanchez'

!new Actor('actor17')
!actor17.name := 'Yuki Nakamura'

!new Actor('actor18')
!actor18.name := 'Ethan Thompson'

!insert (client7, rental8) into ClientRental

!insert (rental8, movie9) into RentalCassette
!insert (rental8, series7) into RentalCassette
!insert (rental8, series8) into RentalCassette

!insert (movie9, actor16) into CassetteActor
!insert (movie9, actor17) into CassetteActor

!insert (series7, actor18) into CassetteActor
!insert (series7, actor17) into CassetteActor

!insert (series8, actor18) into CassetteActor
!insert (series8, actor17) 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
- **Client2**: Named "Carlos Hernández", with a `clientId` of 2147483647, representing a boundary condition at the upper limit for a typical 32-bit integer storing client IDs, and an `isSuspended` status of `true`. Carlos has a history of multiple rentals showcasing a scenario where a client engages with the service frequently but faces suspension.

#### Rentals
- **Rental2**: Dated "2024-01-15". This rental involves a complex scenario with several cassettes, emphasizing maximum multiplicity vertices.
- **Rental3**: Dated "2024-02-01". This rental is established just before the suspension date, determining a point of transition for the client’s rental history.

#### Cassettes
- **Movie2**: Titled "Epic Laughs", belonging to the `Comedy` genre, and with `availableCopies` set to 0, showing a boundary where a cassette exists in inventory but has no available copies for immediate rental.
- **Series2**: Titled "Daring Escapades", having an `episode` number of 50, tapping into the scenario where a series has a notably high episode count, and an `availableCopies` of 5, testing the system against a higher volume of stock.

#### Actors
- **Actor2**: Named "Sofia Martín", linked only to "Epic Laughs". This illustrates an actor participating solely in a specific genre, focusing on boundary conditions within a singular association context.
- **Actor3**: Named "Luis Rivera", associated with both "Epic Laughs" and "Daring Escapades", reflecting the boundary condition where an actor's work bridges multiple media types.

### Relationships and Structure
- Carlos Hernández, having two rentals before his suspension, demonstrates an exploration of the multifaceted rental lifecycle for a single client, with diversification in both timing and content consumption. 

- Rental2 highlights the maximal complexity of rental interplay, involving numerous cassette relations with distinctions among them, revealing the limits on handling extensive transactional entries.

- Rental3 marks a boundary in timing where a featured rental (Daring Escapades) might have been the tipping point before Carlos's suspension, indicating acute scenarios of client status changes and their conditions.

### Semantic Considerations
This instance elaborates a scenario where clients push the limits of rental engagements and interactions with various inventory statuses and episodes. It shows structural diversity in multiplicity and semantic variety through marked differences in client engagement, rental complexities, and cassette availability conditions, emphasizing the VideoClub system's elasticity in capturing abrupt and broad spectrums of functionality.

<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('client10')
!client10.clientId := 2147483647
!client10.isSuspended := true

!new Rental('rental13')
!rental13.date := Date('2024-01-15')

!new Rental('rental14')
!rental14.date := Date('2024-02-01')

!new Movie('movie12')
!movie12.title := 'Epic Laughs'
!movie12.availableCopies := 0
!movie12.genre := #Comedy

!new Series('series12')
!series12.title := 'Daring Escapades'
!series12.availableCopies := 5
!series12.episode := 50

!new Actor('actor23')
!actor23.name := 'Sofia Martín'

!new Actor('actor24')
!actor24.name := 'Luis Rivera'

!insert (client10, rental13) into ClientRental
!insert (client10, rental14) into ClientRental

!insert (rental13, movie12) into RentalCassette
!insert (rental13, series12) into RentalCassette

!insert (rental14, series12) into RentalCassette

!insert (movie12, actor23) into CassetteActor
!insert (movie12, actor24) into CassetteActor

!insert (series12, actor24) 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: 
## Another Complex VideoClub Instance

### Entities

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

2. **Client:**
   - **clientId:** 402
   - **isSuspended:** False

#### Rentals
1. **Rental:**
   - **date:** "2023-08-20"

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

3. **Rental:**
   - **date:** "2023-09-12"

4. **Rental:**
   - **date:** "2023-10-02"

#### Cassettes
1. **Movie:**
   - **title:** "Distant Thunder"
   - **availableCopies:** 10
   - **genre:** Action

2. **Movie:**
   - **title:** "Joyful Jingles"
   - **availableCopies:** 5
   - **genre:** Comedy

3. **Series:**
   - **title:** "Tales from the North"
   - **availableCopies:** 8
   - **episode:** 1

4. **Series:**
   - **title:** "Safari Adventure"
   - **availableCopies:** 3
   - **episode:** 5

5. **Series:**
   - **title:** "London Mysteries"
   - **availableCopies:** 6
   - **episode:** 2

#### Actors
1. **Actor:**
   - **name:** "Anna Kendrick"

2. **Actor:**
   - **name:** "Robert Liu"

3. **Actor:**
   - **name:** "Eliott Gomez"

4. **Actor:**
   - **name:** "Jasmine Khan"

### Relationships

#### ClientRental Association
- **Client 301** has the following rentals:
  - **Rental on 2023-08-20**
    - Involves:
      - **Distant Thunder**
  - **Rental on 2023-09-12**
    - Involves:
      - **Tales from the North**
      - **Safari Adventure**

- **Client 402** has the following rentals:
  - **Rental on 2023-08-25**
    - Involves:
      - **Joyful Jingles**
      - **Safari Adventure**
  - **Rental on 2023-10-02**
    - Involves:
      - **London Mysteries**

#### RentalCassette Association
- **Rental on 2023-08-20** involves:
  - **Cassette:** Distant Thunder

- **Rental on 2023-08-25** involves:
  - **Cassette:** Joyful Jingles
  - **Cassette:** Safari Adventure

- **Rental on 2023-09-12** involves:
  - **Cassette:** Tales from the North
  - **Cassette:** Safari Adventure

- **Rental on 2023-10-02** involves:
  - **Cassette:** London Mysteries

#### CassetteActor Association
- **Distant Thunder** includes actors:
  - Anna Kendrick
  - Robert Liu

- **Joyful Jingles** includes actors:
  - Jasmine Khan
  - Eliott Gomez

- **Tales from the North** includes actors:
  - Anna Kendrick
  - Jasmine Khan

- **Safari Adventure** includes actors:
  - Robert Liu
  - Eliott Gomez

- **London Mysteries** includes actors:
  - Jasmine Khan
  - Anna Kendrick

This instance highlights different combinations of clients, cassettes, and their relationships, introducing new sets of actors and using varied geographic themes and cultural contexts in the titles of movies and series. The structural changes include variation in rental volumes and allocations, leading to a fresh interpretation of the VideoClub 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('client8')
!client8.clientId := 301
!client8.isSuspended := false

!new Client('client9')
!client9.clientId := 402
!client9.isSuspended := false

!new Rental('rental9')
!rental9.date := Date('2023-08-20')

!new Rental('rental10')
!rental10.date := Date('2023-08-25')

!new Rental('rental11')
!rental11.date := Date('2023-09-12')

!new Rental('rental12')
!rental12.date := Date('2023-10-02')

!new Movie('movie10')
!movie10.title := 'Distant Thunder'
!movie10.availableCopies := 10
!movie10.genre := #Action

!new Movie('movie11')
!movie11.title := 'Joyful Jingles'
!movie11.availableCopies := 5
!movie11.genre := #Comedy

!new Series('series9')
!series9.title := 'Tales from the North'
!series9.availableCopies := 8
!series9.episode := 1

!new Series('series10')
!series10.title := 'Safari Adventure'
!series10.availableCopies := 3
!series10.episode := 5

!new Series('series11')
!series11.title := 'London Mysteries'
!series11.availableCopies := 6
!series11.episode := 2

!new Actor('actor19')
!actor19.name := 'Anna Kendrick'

!new Actor('actor20')
!actor20.name := 'Robert Liu'

!new Actor('actor21')
!actor21.name := 'Eliott Gomez'

!new Actor('actor22')
!actor22.name := 'Jasmine Khan'

!insert (client8, rental9) into ClientRental
!insert (client8, rental11) into ClientRental

!insert (client9, rental10) into ClientRental
!insert (client9, rental12) into ClientRental

!insert (rental9, movie10) into RentalCassette
!insert (rental10, movie11) into RentalCassette
!insert (rental10, series10) into RentalCassette
!insert (rental11, series9) into RentalCassette
!insert (rental11, series10) into RentalCassette
!insert (rental12, series11) into RentalCassette

!insert (movie10, actor19) into CassetteActor
!insert (movie10, actor20) into CassetteActor

!insert (movie11, actor22) into CassetteActor
!insert (movie11, actor21) into CassetteActor

!insert (series9, actor19) into CassetteActor
!insert (series9, actor22) into CassetteActor

!insert (series10, actor20) into CassetteActor
!insert (series10, actor21) into CassetteActor

!insert (series11, actor22) into CassetteActor
!insert (series11, actor19) 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 Rare Multi-Episode Marathon Scenario

#### Date Instance
- **Date:** "2023-10-20"

#### Client Class
1. **Name:** Hiroshi Nakamura
   - **clientId:** 1  (Using the smallest possible valid positive integer)
   - **isSuspended:** True
   - **Rentals:**

#### Rental Class
1. **Rental Date:** "2023-10-20"
   - **Associated Client:** Hiroshi Nakamura
   - **Cassettes Involved:**
     - "The Everlasting Gag"
     - "Epic Sword Chronicles"

#### Cassette and Derived Classes

1. **Movie:**
   - **Title:** "The Everlasting Gag"
   - **availableCopies:** 10
   - **genre:** Comedy
   - **Associated Actors:** 
     - Farah El Bastawy
     - John McEdge

2. **Series:**
   - **Title:** "Epic Sword Chronicles"
   - **availableCopies:** 50  (Indicating moderate availability, typical for popular series)
   - **episode:** 1  (The very first episode, implying the start of a series marathon)
   - **Associated Actors:**
     - Mei Lin
     - Rajiv Banerjee

3. **Series:**
   - **Title:** "Epic Sword Chronicles: The Saga Continues"
   - **availableCopies:** 2  (Rare, suggesting limited release or high demand for sequels)
   - **episode:** 65535  (A maximum allowable number for series episode to show extreme longevity)
   - **Associated Actors:**
     - Mei Lin
     - Rajiv Banerjee

#### Actor Class

1. **Actor Name:** Farah El Bastawy
   - **Associated Cassettes:** 
     - "The Everlasting Gag"

2. **Actor Name:** John McEdge
   - **Associated Cassettes:**
     - "The Everlasting Gag"

3. **Actor Name:** Mei Lin
   - **Associated Cassettes:**
     - "Epic Sword Chronicles"
     - "Epic Sword Chronicles: The Saga Continues"
   
4. **Actor Name:** Rajiv Banerjee
   - **Associated Cassettes:**
     - "Epic Sword Chronicles"
     - "Epic Sword Chronicles: The Saga Continues"

#### Description:

In this "Rare Multi-Episode Marathon Scenario," the instance explores the unusual combination of a client with the smallest possible `clientId` who is also suspended, creating a logical oddity since they still have rentals associated. Perhaps, they had a rental scheduled before suspension that is yet to be canceled.

"The Everlasting Gag," a comedy with moderate availability, contrasts with the extremely long-running series "Epic Sword Chronicles," of which the first episode and a near-capacity episode (65535) are rented together, creating a dichotomy between series beginnings and extensive progress.

The actors bring a global dimension with Farah El Bastawy and John McEdge in comedy, while Mei Lin and Rajiv Banerjee bridge narrative across multiple points in a long-spanning series, speaking to universal appeal and versatility across different film types. This setup provides a snapshot of diverse cultural casting and storyline longevity in the film industry.

<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('client13')
!client13.clientId := 1
!client13.isSuspended := true

!new Rental('rental18')
!rental18.date := Date('2023-10-20')

!new Movie('movie17')
!movie17.title := 'The Everlasting Gag'
!movie17.availableCopies := 10
!movie17.genre := #Comedy

!new Series('series15')
!series15.title := 'Epic Sword Chronicles'
!series15.availableCopies := 50
!series15.episode := 1

!new Series('series16')
!series16.title := 'Epic Sword Chronicles: The Saga Continues'
!series16.availableCopies := 2
!series16.episode := 65535

!new Actor('actor29')
!actor29.name := 'Farah El Bastawy'

!new Actor('actor30')
!actor30.name := 'John McEdge'

!new Actor('actor31')
!actor31.name := 'Mei Lin'

!new Actor('actor32')
!actor32.name := 'Rajiv Banerjee'

!insert (client13, rental18) into ClientRental

!insert (rental18, movie17) into RentalCassette
!insert (rental18, series15) into RentalCassette
!insert (rental18, series16) into RentalCassette

!insert (movie17, actor29) into CassetteActor
!insert (movie17, actor30) into CassetteActor

!insert (series15, actor31) into CassetteActor
!insert (series15, actor32) into CassetteActor

!insert (series16, actor31) into CassetteActor
!insert (series16, actor32) 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: Regional Documentary Archive Special Viewing**

In this instance, we explore a culturally rich and non-commercial scenario involving documentary films from indigenous cultures in Australia, which are often showcased as part of community awareness events, revealing potentially overstated restrictions in the VideoClub model.

**Entities:**

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

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

3. **Movies:**
   - Title: "Voices of the Outback"
     - `availableCopies`: 0
     - `genre`: "Action" (used metaphorically to represent active lifestyle)
   - Title: "Dreamtime Legends"
     - `availableCopies`: 0
     - `genre`: "Comedy" (a light-hearted take on cultural narratives)

4. **Series:**
   - Title: "Walkabout Chronicles"
     - `availableCopies`: 0
     - `episode`: 1

5. **Actors:**
   - Name: "N/A" (Non-traditional documentary style with no professional actors)

**Situation Overview:**

- **ClientRental Association:**
  - **Client (1):** Includes the client with `clientId` 87 attending as a viewer.
  - **Rental (0):** Intriguingly, this client does not rent but rather participates in in-house viewings. Realistically plausible in events but breaches model assumptions regarding always present rentals per client.

- **RentalCassette Association:**
  - **Rental (0):** No physical cassettes are rented or exchanged, as viewings happen within a community space.
  - **Cassette (0):** The concept of in-house viewings with zero physical cassettes circulating challenges the assumption that a rental must involve at least one cassette, aligning with community-hosted, archive-protection policies.

- **CassetteActor Association:**
  - **Movie and Series without Actors:** Highlight indigenous storytelling modes where community leaders and historical footage fill narrative roles without professional actors involved, contesting the enforced mapping of actors to cassettes.

**Model Violation Highlights:**

- **Non-Rental Viewings:** Events permitting on-site screenings without physical cassette checkouts expose the limits of `Cassette [1..*]` under strict outdoor protocols.
- **Community Participants Without Rentals:** Genuine scenarios where clients participate in screenings without renting burden the model's assumption on mandatory rentals.
- **Actor-Free Content:** Reflects models of non-commercial storytelling unbound by traditional actor roles, illuminating rigidity in `Actor [1..*]`.

This instance illustrates the necessity for flexibility within a video club system, especially in representing cultural experiences and archival showcases that diverge from the commercial video rental norm, testifying to broader inclusion in multimedia enterprise planning beyond existing restrictions.

<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('client11')
!client11.clientId := 87
!client11.isSuspended := false

!new Rental('rental15')
!rental15.date := Date('2023-10-15')

!new Movie('movie13')
!movie13.title := 'Voices of the Outback'
!movie13.availableCopies := 0
!movie13.genre := #Action

!new Movie('movie14')
!movie14.title := 'Dreamtime Legends'
!movie14.availableCopies := 0
!movie14.genre := #Comedy

!new Series('series13')
!series13.title := 'Walkabout Chronicles'
!series13.availableCopies := 0
!series13.episode := 1

!new Actor('actor25')
!actor25.name := 'N/A'

!insert (client11, rental15) into ClientRental

!insert (rental15, movie13) into RentalCassette
!insert (rental15, movie14) into RentalCassette
!insert (rental15, series13) into RentalCassette

!insert (movie13, actor25) into CassetteActor
!insert (movie14, actor25) into CassetteActor
!insert (series13, actor25) into CassetteActor
</object_model>