AddressBook / 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: 
## Instance: Continental Network Address Book

### Address Book
- **Name**: Continental Network Address Book

### Contacts

#### 1. Person Contact
- **Name**: Hiroshi Tanaka
- **Phone**: +81-90-5555-1234
- **Website**: www.hiroshitanaka.com
- **Email**: hiroshi.tanaka@businessmail.jp
- **Title**: Marketing Director

##### Notes for Hiroshi Tanaka
1. **Note**
   - **Author**: Hiroshi Tanaka
   - **Time**: "2023-02-20"
   - **Type**: EMAIL
   - **Comment**: Exchange ideas for the upcoming Tokyo Expo campaign.

##### Address for Hiroshi Tanaka
- **City**: Tokyo
- **House Number**: 88-03
- **Street**: Ginza District

##### Relationships for Hiroshi Tanaka
- **Relationship**
  - **Type**: BOSS
  - **Target**: Keiko Yamada

#### 2. Company Contact
- **Name**: Nordic Hardware Inc.
- **Phone**: +46-31-555-4432
- **Website**: www.nordichardware.se
- **Email**: contact@nordichardware.se
- **Industry**: Manufacturing

##### Notes for Nordic Hardware Inc.
- **Note**
  - **Author**: Erik Jonsson
  - **Time**: "2023-07-15"
  - **Type**: CALL
  - **Comment**: Discuss logistics for new product lines across Europe.

##### Address for Nordic Hardware Inc.
1. **Address**
   - **City**: Gothenburg
   - **House Number**: 110A
   - **Street**: Haga Nygata

2. **Address**
   - **City**: Stockholm
   - **House Number**: 42
   - **Street**: Drottninggatan

#### 3. Person Contact
- **Name**: Keiko Yamada
- **Phone**: +81-70-6655-9988
- **Website**: www.keikoyamada.net
- **Email**: keiko.yamada@creativeagency.jp
- **Title**: Junior Graphic Designer

##### Notes for Keiko Yamada
- **Note**
  - **Author**: Keiko Yamada
  - **Time**: "2023-04-12"
  - **Type**: MEETING
  - **Comment**: Brainstorming session for new ad visual concepts.

##### Address for Keiko Yamada
- **City**: Osaka
- **House Number**: 1204
- **Street**: Ebisubashi

##### Relationships for Keiko Yamada
- **Relationship**
  - **Type**: EMPLOYEE
  - **Target**: Hiroshi Tanaka

#### 4. Person Contact
- **Name**: Erik Jonsson
- **Phone**: +46-08-5556-7890
- **Website**: www.erikjonssonconsulting.se
- **Email**: erik.jonsson@consult.se 
- **Title**: Supply Chain Manager

##### Notes for Erik Jonsson
- **Note**
  - **Author**: Erik Jonsson
  - **Time**: "2023-10-23"
  - **Type**: CALL
  - **Comment**: Monthly call with international suppliers review.

##### Address for Erik Jonsson
- **City**: Malmö
- **House Number**: 74B
- **Street**: Lilla Fiskaregatan

##### Relationships for Erik Jonsson
1. **Relationship**
   - **Type**: SUBDIVISION
   - **Target**: Nordic Hardware Inc.

2. **Relationship**
   - **Type**: COWORKER
   - **Target**: Hiroshi Tanaka

### Relationships

- **Hiroshi Tanaka** leads **Keiko Yamada** as her **BOSS**.
- **Keiko Yamada** is an **EMPLOYEE** under **Hiroshi Tanaka**.
- **Erik Jonsson** manages a **SUBDIVISION**, which is **Nordic Hardware Inc.**.
- **Hiroshi Tanaka** and **Erik Jonsson** work together as **COWORKERS**.

This address book exemplifies varied geographic and industry-specific diversity, illustrating distinct cultural and corporate dynamics with unique sets of relationships and professional interactions related specifically to marketing, design, and manufacturing contexts.

The last output is partially incorrect: 
temp.soil> !HiroshiToKeikoBoss.type := #BOSS
temp.soil> !insert (HiroshiToKeikoBoss, KeikoYamada) into RelationshipToContact
<input>:1:0: Variable `KeikoYamada' in expression `KeikoYamada' is undefined.

Please provide the complete output corrected

<domain_model>
model AddressBook

enum NoteType {
    MEETING,
    CALL,
    EMAIL
}

enum RelationshipType {
    BOSS,
    EMPLOYEE,
    SUBDIVISION,
    COWORKER
}

dataType Date
operations
    Date(date : String)
end

class AddressBook
end

abstract class Contact
attributes
    name : String
    phone : String
    website : String
    email : String
end

class Note
attributes
    author : String
    time : Date
    type : NoteType
    comment : String
end

class Company < Contact
attributes
    industry : String
end

class Person < Contact
attributes
    title : String
end

class Address
attributes
    city : String
    houseNr : String
    street : String
end

class Relationship
attributes
    type : RelationshipType
end

composition AddressBookMadeOfContact between
    AddressBook[1]
    Contact[*]
end

composition ContactContainsNote between
    Contact[1]
    Note[*]
end

association RelationshipToContact between
    Relationship[*] role isRelated
    Contact[1] role target
end

composition ContactToRelationship between
    Contact[1]
    Relationship[*] role relates
end

composition ContactContainsAddress between
    Contact[1] role source
    Address[*] role address
end


constraints
context Contact inv DifferentSourceTarget:
    self.relates->forAll(r | r.target<>self)
</domain_model>

<object_model>
!new AddressBook('ContinentalNetworkAddressBook')

!new Person('HiroshiTanaka')
!HiroshiTanaka.name := 'Hiroshi Tanaka'
!HiroshiTanaka.phone := '+81-90-5555-1234'
!HiroshiTanaka.website := 'www.hiroshitanaka.com'
!HiroshiTanaka.email := 'hiroshi.tanaka@businessmail.jp'
!HiroshiTanaka.title := 'Marketing Director'

!new Address('HiroshiTanakaAddress')
!HiroshiTanakaAddress.city := 'Tokyo'
!HiroshiTanakaAddress.street := 'Ginza District'
!HiroshiTanakaAddress.houseNr := '88-03'
!insert (HiroshiTanaka, HiroshiTanakaAddress) into ContactContainsAddress

!new Note('HiroshiTanakaNote1')
!HiroshiTanakaNote1.author := 'Hiroshi Tanaka'
!HiroshiTanakaNote1.time := Date('2023-02-20')
!HiroshiTanakaNote1.type := #EMAIL
!HiroshiTanakaNote1.comment := 'Exchange ideas for the upcoming Tokyo Expo campaign.'
!insert (HiroshiTanaka, HiroshiTanakaNote1) into ContactContainsNote

!new Person('KeikoYamada')
!KeikoYamada.name := 'Keiko Yamada'
!KeikoYamada.phone := '+81-70-6655-9988'
!KeikoYamada.website := 'www.keikoyamada.net'
!KeikoYamada.email := 'keiko.yamada@creativeagency.jp'
!KeikoYamada.title := 'Junior Graphic Designer'

!new Address('KeikoYamadaAddress')
!KeikoYamadaAddress.city := 'Osaka'
!KeikoYamadaAddress.street := 'Ebisubashi'
!KeikoYamadaAddress.houseNr := '1204'
!insert (KeikoYamada, KeikoYamadaAddress) into ContactContainsAddress

!new Note('KeikoYamadaNote1')
!KeikoYamadaNote1.author := 'Keiko Yamada'
!KeikoYamadaNote1.time := Date('2023-04-12')
!KeikoYamadaNote1.type := #MEETING
!KeikoYamadaNote1.comment := 'Brainstorming session for new ad visual concepts.'
!insert (KeikoYamada, KeikoYamadaNote1) into ContactContainsNote

!new Relationship('HiroshiToKeikoBoss')
!HiroshiToKeikoBoss.type := #BOSS
!insert (HiroshiToKeikoBoss, KeikoYamada) into RelationshipToContact
!insert (HiroshiTanaka, HiroshiToKeikoBoss) into ContactToRelationship

!new Company('NordicHardwareInc')
!NordicHardwareInc.name := 'Nordic Hardware Inc.'
!NordicHardwareInc.phone := '+46-31-555-4432'
!NordicHardwareInc.website := 'www.nordichardware.se'
!NordicHardwareInc.email := 'contact@nordichardware.se'
!NordicHardwareInc.industry := 'Manufacturing'

!new Address('NordicHardwareAddress1')
!NordicHardwareAddress1.city := 'Gothenburg'
!NordicHardwareAddress1.street := 'Haga Nygata'
!NordicHardwareAddress1.houseNr := '110A'
!insert (NordicHardwareInc, NordicHardwareAddress1) into ContactContainsAddress

!new Address('NordicHardwareAddress2')
!NordicHardwareAddress2.city := 'Stockholm'
!NordicHardwareAddress2.street := 'Drottninggatan'
!NordicHardwareAddress2.houseNr := '42'
!insert (NordicHardwareInc, NordicHardwareAddress2) into ContactContainsAddress

!new Note('NordicHardwareNote1')
!NordicHardwareNote1.author := 'Erik Jonsson'
!NordicHardwareNote1.time := Date('2023-07-15')
!NordicHardwareNote1.type := #CALL
!NordicHardwareNote1.comment := 'Discuss logistics for new product lines across Europe.'
!insert (NordicHardwareInc, NordicHardwareNote1) into ContactContainsNote

!new Person('ErikJonsson')
!ErikJonsson.name := 'Erik Jonsson'
!ErikJonsson.phone := '+46-08-5556-7890'
!ErikJonsson.website := 'www.erikjonssonconsulting.se'
!ErikJonsson.email := 'erik.jonsson@consult.se'
!ErikJonsson.title := 'Supply Chain Manager'

!new Address('ErikJonssonAddress')
!ErikJonssonAddress.city := 'Malmö'
!ErikJonssonAddress.street := 'Lilla Fiskaregatan'
!ErikJonssonAddress.houseNr := '74B'
!insert (ErikJonsson, ErikJonssonAddress) into ContactContainsAddress

!new Note('ErikJonssonNote1')
!ErikJonssonNote1.author := 'Erik Jonsson'
!ErikJonssonNote1.time := Date('2023-10-23')
!ErikJonssonNote1.type := #CALL
!ErikJonssonNote1.comment := 'Monthly call with international suppliers review.'
!insert (ErikJonsson, ErikJonssonNote1) into ContactContainsNote

!new Relationship('KeikoToHiroshiEmployee')
!KeikoToHiroshiEmployee.type := #EMPLOYEE
!insert (KeikoToHiroshiEmployee, HiroshiTanaka) into RelationshipToContact
!insert (KeikoYamada, KeikoToHiroshiEmployee) into ContactToRelationship

!new Relationship('ErikToNordicSubdivision')
!ErikToNordicSubdivision.type := #SUBDIVISION
!insert (ErikToNordicSubdivision, NordicHardwareInc) into RelationshipToContact
!insert (ErikJonsson, ErikToNordicSubdivision) into ContactToRelationship

!new Relationship('ErikToHiroshiCoworker')
!ErikToHiroshiCoworker.type := #COWORKER
!insert (ErikToHiroshiCoworker, HiroshiTanaka) into RelationshipToContact
!insert (ErikJonsson, ErikToHiroshiCoworker) into ContactToRelationship

!insert (ContinentalNetworkAddressBook, HiroshiTanaka) into AddressBookMadeOfContact
!insert (ContinentalNetworkAddressBook, NordicHardwareInc) into AddressBookMadeOfContact
!insert (ContinentalNetworkAddressBook, KeikoYamada) into AddressBookMadeOfContact
!insert (ContinentalNetworkAddressBook, ErikJonsson) into AddressBookMadeOfContact
</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: "Startup Community Address Book"

### Address Book
- **AddressBook**: "Startup Community Address Book"
  - This address book is dedicated to connecting small startups and entrepreneurs within a local community.

### Contacts
- **Contact 1**: "Tech Hub"
  - **Type**: Company
  - **Attributes**:
    - Name: Tech Hub
    - Phone: +1-303-123-4567
    - Website: www.techhub.startup
    - Email: info@techhub.startup
    - Industry: Information Technology
  - **Addresses**: 
    - (Boundary case with no addresses)

- **Contact 2**: "Barbara Green"
  - **Type**: Person
  - **Attributes**:
    - Name: Barbara Green
    - Phone: +1-415-555-0111
    - Website: 
    - Email: barbara.green@innovators.com
    - Title: Founder
  - **Addresses**: 
    - Address 1:
      - City: San Francisco
      - HouseNr: 23
      - Street: Silicon Alley
    - Address 2:
      - City: Palo Alto
      - HouseNr: 456
      - Street: Innovation Drive
  - **Notes**: 
    - Note 1:
      - Author: Matthew Clark
      - Time: "2023-07-22"
      - Type: EMAIL
      - Comment: Discussed opportunities for co-working space collaboration.

- **Contact 3**: "Eco Ventures"
  - **Type**: Company
  - **Attributes**:
    - Name: Eco Ventures
    - Phone: +44-141-555-0199
    - Website: www.ecoventures.co.uk
    - Email: hello@ecoventures.co.uk
    - Industry: Environmental Services
  - **Addresses**: 
    - Address 1:
      - City: Glasgow
      - HouseNr: 9
      - Street: Greenway Boulevard
  - **Notes**: 
    - Note 1:
      - Author: Anna Davis
      - Time: "2023-09-05"
      - Type: CALL
      - Comment: Phone call to plan tree planting initiative.

### Relationships
- **Relationship 1**: Between "Tech Hub" and "Barbara Green"
  - **Type**: EMPLOYEE
  - Target: Barbara Green

- **Relationship 2**: Between "Barbara Green" and "Eco Ventures"
  - **Type**: COWORKER
  - Target: Eco Ventures

### Boundary Considerations
- Minimalist structure with "Tech Hub" purposefully left without addresses to test the lower range of address multiplicity.
- Varied geographic and regional representation through San Francisco, Palo Alto, and Glasgow, showcasing different urban profiles.
- Business and environmental significance are combined through company specializations and relationship types.

<domain_model>
model AddressBook

enum NoteType {
    MEETING,
    CALL,
    EMAIL
}

enum RelationshipType {
    BOSS,
    EMPLOYEE,
    SUBDIVISION,
    COWORKER
}

dataType Date
operations
    Date(date : String)
end

class AddressBook
end

abstract class Contact
attributes
    name : String
    phone : String
    website : String
    email : String
end

class Note
attributes
    author : String
    time : Date
    type : NoteType
    comment : String
end

class Company < Contact
attributes
    industry : String
end

class Person < Contact
attributes
    title : String
end

class Address
attributes
    city : String
    houseNr : String
    street : String
end

class Relationship
attributes
    type : RelationshipType
end

composition AddressBookMadeOfContact between
    AddressBook[1]
    Contact[*]
end

composition ContactContainsNote between
    Contact[1]
    Note[*]
end

association RelationshipToContact between
    Relationship[*] role isRelated
    Contact[1] role target
end

composition ContactToRelationship between
    Contact[1]
    Relationship[*] role relates
end

composition ContactContainsAddress between
    Contact[1] role source
    Address[*] role address
end


constraints
context Contact inv DifferentSourceTarget:
    self.relates->forAll(r | r.target<>self)
</domain_model>

<object_model>
!new AddressBook('StartupCommunityAddressBook')

!new Company('TechHub')
!TechHub.name := 'Tech Hub'
!TechHub.phone := '+1-303-123-4567'
!TechHub.website := 'www.techhub.startup'
!TechHub.email := 'info@techhub.startup'
!TechHub.industry := 'Information Technology'

!new Person('BarbaraGreen')
!BarbaraGreen.name := 'Barbara Green'
!BarbaraGreen.phone := '+1-415-555-0111'
!BarbaraGreen.email := 'barbara.green@innovators.com'
!BarbaraGreen.title := 'Founder'

!new Address('BarbaraGreenAddress1')
!BarbaraGreenAddress1.city := 'San Francisco'
!BarbaraGreenAddress1.houseNr := '23'
!BarbaraGreenAddress1.street := 'Silicon Alley'
!insert (BarbaraGreen, BarbaraGreenAddress1) into ContactContainsAddress

!new Address('BarbaraGreenAddress2')
!BarbaraGreenAddress2.city := 'Palo Alto'
!BarbaraGreenAddress2.houseNr := '456'
!BarbaraGreenAddress2.street := 'Innovation Drive'
!insert (BarbaraGreen, BarbaraGreenAddress2) into ContactContainsAddress

!new Note('BarbaraGreenNote1')
!BarbaraGreenNote1.author := 'Matthew Clark'
!BarbaraGreenNote1.time := Date('2023-07-22')
!BarbaraGreenNote1.type := #EMAIL
!BarbaraGreenNote1.comment := 'Discussed opportunities for co-working space collaboration.'
!insert (BarbaraGreen, BarbaraGreenNote1) into ContactContainsNote

!new Company('EcoVentures')
!EcoVentures.name := 'Eco Ventures'
!EcoVentures.phone := '+44-141-555-0199'
!EcoVentures.website := 'www.ecoventures.co.uk'
!EcoVentures.email := 'hello@ecoventures.co.uk'
!EcoVentures.industry := 'Environmental Services'

!new Address('EcoVenturesAddress1')
!EcoVenturesAddress1.city := 'Glasgow'
!EcoVenturesAddress1.houseNr := '9'
!EcoVenturesAddress1.street := 'Greenway Boulevard'
!insert (EcoVentures, EcoVenturesAddress1) into ContactContainsAddress

!new Note('EcoVenturesNote1')
!EcoVenturesNote1.author := 'Anna Davis'
!EcoVenturesNote1.time := Date('2023-09-05')
!EcoVenturesNote1.type := #CALL
!EcoVenturesNote1.comment := 'Phone call to plan tree planting initiative.'
!insert (EcoVentures, EcoVenturesNote1) into ContactContainsNote

!new Relationship('TechHubToBarbaraEmployee')
!TechHubToBarbaraEmployee.type := #EMPLOYEE
!insert (TechHubToBarbaraEmployee, BarbaraGreen) into RelationshipToContact
!insert (TechHub, TechHubToBarbaraEmployee) into ContactToRelationship

!new Relationship('BarbaraToEcoCoworker')
!BarbaraToEcoCoworker.type := #COWORKER
!insert (BarbaraToEcoCoworker, EcoVentures) into RelationshipToContact
!insert (BarbaraGreen, BarbaraToEcoCoworker) into ContactToRelationship

!insert (StartupCommunityAddressBook, TechHub) into AddressBookMadeOfContact
!insert (StartupCommunityAddressBook, BarbaraGreen) into AddressBookMadeOfContact
!insert (StartupCommunityAddressBook, EcoVentures) into AddressBookMadeOfContact
</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: 
## Complex Address Book Instance

### Address Book: "Continental Network"

This address book, named "Continental Network," observes a wide-reaching collection of diverse, interconnected business and academic contacts across continents.

#### Contacts

1. **Contact 1 - Person**
   - **Name**: Dr. Ayesha Khan
   - **Phone**: +92 21 987 6543
   - **Website**: www.ayeshakresearch.org
   - **Email**: khan.ayesha@uni.edu
   - **Title**: Professor of Environmental Science

   - **Addresses**:
     - **1.1 Address**:
       - **City**: Karachi
       - **Street**: University Avenue
       - **House Number**: 12

   - **Notes**:
     - **1.1 Note**:
       - **Author**: Dr. Ayesha Khan
       - **Time**: "2023-06-01"
       - **Type**: EMAIL
       - **Comment**: "Follow-up email about the environmental research collaboration with EU partners."

     - **1.2 Note**:
       - **Author**: Dr. Ayesha Khan
       - **Time**: "2023-06-10"
       - **Type**: MEETING
       - **Comment**: "Attended the Global Climate Change Conference."

   - **Relationships**:
     - **1.1 Relationship** to Contact 2:
       - **Type**: COWORKER
     - **1.2 Relationship** to Contact 3:
       - **Type**: EMPLOYEE

2. **Contact 2 - Person**
   - **Name**: Prof. John Martinez
   - **Phone**: +34 91 555 6644
   - **Website**: www.innovateenergy.com
   - **Email**: martinez.j@energy-research.org
   - **Title**: Head of Research Department

   - **Addresses**:
     - **2.1 Address**:
       - **City**: Madrid
       - **Street**: Ciencia Street
       - **House Number**: 101

   - **Notes**:
     - **2.1 Note**:
       - **Author**: Prof. John Martinez
       - **Time**: "2023-06-15"
       - **Type**: CALL
       - **Comment**: "Discussed joint paper publication with Dr. Ayesha Khan."

   - **Relationships**:
     - **2.1 Relationship** to Contact 1:
       - **Type**: COWORKER
     - **2.2 Relationship** to Contact 4:
       - **Type**: BOSS

3. **Contact 3 - Company**
   - **Name**: Eco Research Institute
   - **Phone**: +61 7 3221 2345
   - **Website**: www.ecoresearch.org.au
   - **Email**: info@ecoresearch.org.au
   - **Industry**: Environmental Research

   - **Addresses**:
     - **3.1 Address**:
       - **City**: Brisbane
       - **Street**: Green Street
       - **House Number**: 55B

   - **Notes**:
     - **3.1 Note**:
       - **Author**: Eco Research Institute
       - **Time**: "2023-07-01"
       - **Type**: MEETING
       - **Comment**: "Organized meeting for the annual environmental awareness workshop."

   - **Relationships**:
     - **3.1 Relationship** to Contact 1:
       - **Type**: BOSS

4. **Contact 4 - Company**
   - **Name**: EnerTech Solutions Ltd.
   - **Phone**: +49 30 1234 567
   - **Website**: www.enertechsol.de
   - **Email**: contact@enertechsol.de
   - **Industry**: Renewable Energy

   - **Addresses**:
     - **4.1 Address**:
       - **City**: Berlin
       - **Street**: Solar Parkway
       - **House Number**: 200

   - **Notes**:
     - **4.1 Note**:
       - **Author**: EnerTech Solutions Ltd.
       - **Time**: "2023-08-10"
       - **Type**: EMAIL
       - **Comment**: "Sent an email confirming availability for upcoming renewable energy summit."

   - **Relationships**:
     - **4.1 Relationship** to Contact 2:
       - **Type**: EMPLOYEE

### Invariant Check
- **DifferentSourceTarget**: Ensured all relationship targets are distinct from their respective sources, affirming no self-reference violations.

This instance depicts a varied and complex network featuring both academic and corporate entities collaborating on global sustainability and research projects, emphasizing cross-continental linkages and diversity in both fields and geographic locations.

<domain_model>
model AddressBook

enum NoteType {
    MEETING,
    CALL,
    EMAIL
}

enum RelationshipType {
    BOSS,
    EMPLOYEE,
    SUBDIVISION,
    COWORKER
}

dataType Date
operations
    Date(date : String)
end

class AddressBook
end

abstract class Contact
attributes
    name : String
    phone : String
    website : String
    email : String
end

class Note
attributes
    author : String
    time : Date
    type : NoteType
    comment : String
end

class Company < Contact
attributes
    industry : String
end

class Person < Contact
attributes
    title : String
end

class Address
attributes
    city : String
    houseNr : String
    street : String
end

class Relationship
attributes
    type : RelationshipType
end

composition AddressBookMadeOfContact between
    AddressBook[1]
    Contact[*]
end

composition ContactContainsNote between
    Contact[1]
    Note[*]
end

association RelationshipToContact between
    Relationship[*] role isRelated
    Contact[1] role target
end

composition ContactToRelationship between
    Contact[1]
    Relationship[*] role relates
end

composition ContactContainsAddress between
    Contact[1] role source
    Address[*] role address
end


constraints
context Contact inv DifferentSourceTarget:
    self.relates->forAll(r | r.target<>self)
</domain_model>

<object_model>
!new AddressBook('ContinentalNetwork')

!new Person('DrAyeshaKhan')
!DrAyeshaKhan.name := 'Dr. Ayesha Khan'
!DrAyeshaKhan.phone := '+92 21 987 6543'
!DrAyeshaKhan.website := 'www.ayeshakresearch.org'
!DrAyeshaKhan.email := 'khan.ayesha@uni.edu'
!DrAyeshaKhan.title := 'Professor of Environmental Science'

!new Address('AyeshaKhanAddress')
!AyeshaKhanAddress.city := 'Karachi'
!AyeshaKhanAddress.street := 'University Avenue'
!AyeshaKhanAddress.houseNr := '12'
!insert (DrAyeshaKhan, AyeshaKhanAddress) into ContactContainsAddress

!new Note('AyeshaKhanNote1')
!AyeshaKhanNote1.author := 'Dr. Ayesha Khan'
!AyeshaKhanNote1.time := Date('2023-06-01')
!AyeshaKhanNote1.type := #EMAIL
!AyeshaKhanNote1.comment := 'Follow-up email about the environmental research collaboration with EU partners.'
!insert (DrAyeshaKhan, AyeshaKhanNote1) into ContactContainsNote

!new Note('AyeshaKhanNote2')
!AyeshaKhanNote2.author := 'Dr. Ayesha Khan'
!AyeshaKhanNote2.time := Date('2023-06-10')
!AyeshaKhanNote2.type := #MEETING
!AyeshaKhanNote2.comment := 'Attended the Global Climate Change Conference.'
!insert (DrAyeshaKhan, AyeshaKhanNote2) into ContactContainsNote

!new Person('ProfJohnMartinez')
!ProfJohnMartinez.name := 'Prof. John Martinez'
!ProfJohnMartinez.phone := '+34 91 555 6644'
!ProfJohnMartinez.website := 'www.innovateenergy.com'
!ProfJohnMartinez.email := 'martinez.j@energy-research.org'
!ProfJohnMartinez.title := 'Head of Research Department'

!new Address('JohnMartinezAddress')
!JohnMartinezAddress.city := 'Madrid'
!JohnMartinezAddress.street := 'Ciencia Street'
!JohnMartinezAddress.houseNr := '101'
!insert (ProfJohnMartinez, JohnMartinezAddress) into ContactContainsAddress

!new Note('JohnMartinezNote1')
!JohnMartinezNote1.author := 'Prof. John Martinez'
!JohnMartinezNote1.time := Date('2023-06-15')
!JohnMartinezNote1.type := #CALL
!JohnMartinezNote1.comment := 'Discussed joint paper publication with Dr. Ayesha Khan.'
!insert (ProfJohnMartinez, JohnMartinezNote1) into ContactContainsNote

!new Company('EcoResearchInstitute')
!EcoResearchInstitute.name := 'Eco Research Institute'
!EcoResearchInstitute.phone := '+61 7 3221 2345'
!EcoResearchInstitute.website := 'www.ecoresearch.org.au'
!EcoResearchInstitute.email := 'info@ecoresearch.org.au'
!EcoResearchInstitute.industry := 'Environmental Research'

!new Address('EcoResearchAddress')
!EcoResearchAddress.city := 'Brisbane'
!EcoResearchAddress.street := 'Green Street'
!EcoResearchAddress.houseNr := '55B'
!insert (EcoResearchInstitute, EcoResearchAddress) into ContactContainsAddress

!new Note('EcoResearchNote1')
!EcoResearchNote1.author := 'Eco Research Institute'
!EcoResearchNote1.time := Date('2023-07-01')
!EcoResearchNote1.type := #MEETING
!EcoResearchNote1.comment := 'Organized meeting for the annual environmental awareness workshop.'
!insert (EcoResearchInstitute, EcoResearchNote1) into ContactContainsNote

!new Company('EnerTechSolutionsLtd')
!EnerTechSolutionsLtd.name := 'EnerTech Solutions Ltd.'
!EnerTechSolutionsLtd.phone := '+49 30 1234 567'
!EnerTechSolutionsLtd.website := 'www.enertechsol.de'
!EnerTechSolutionsLtd.email := 'contact@enertechsol.de'
!EnerTechSolutionsLtd.industry := 'Renewable Energy'

!new Address('EnerTechSolutionsAddress')
!EnerTechSolutionsAddress.city := 'Berlin'
!EnerTechSolutionsAddress.street := 'Solar Parkway'
!EnerTechSolutionsAddress.houseNr := '200'
!insert (EnerTechSolutionsLtd, EnerTechSolutionsAddress) into ContactContainsAddress

!new Note('EnerTechSolutionsNote1')
!EnerTechSolutionsNote1.author := 'EnerTech Solutions Ltd.'
!EnerTechSolutionsNote1.time := Date('2023-08-10')
!EnerTechSolutionsNote1.type := #EMAIL
!EnerTechSolutionsNote1.comment := 'Sent an email confirming availability for upcoming renewable energy summit.'
!insert (EnerTechSolutionsLtd, EnerTechSolutionsNote1) into ContactContainsNote

!new Relationship('AyeshaToJohnCoworker')
!AyeshaToJohnCoworker.type := #COWORKER
!insert (AyeshaToJohnCoworker, ProfJohnMartinez) into RelationshipToContact
!insert (DrAyeshaKhan, AyeshaToJohnCoworker) into ContactToRelationship

!new Relationship('AyeshaToEcoEmployee')
!AyeshaToEcoEmployee.type := #EMPLOYEE
!insert (AyeshaToEcoEmployee, EcoResearchInstitute) into RelationshipToContact
!insert (DrAyeshaKhan, AyeshaToEcoEmployee) into ContactToRelationship

!new Relationship('JohnToAyeshaCoworker')
!JohnToAyeshaCoworker.type := #COWORKER
!insert (JohnToAyeshaCoworker, DrAyeshaKhan) into RelationshipToContact
!insert (ProfJohnMartinez, JohnToAyeshaCoworker) into ContactToRelationship

!new Relationship('JohnToEnerTechBoss')
!JohnToEnerTechBoss.type := #BOSS
!insert (JohnToEnerTechBoss, EnerTechSolutionsLtd) into RelationshipToContact
!insert (ProfJohnMartinez, JohnToEnerTechBoss) into ContactToRelationship

!new Relationship('EcoToAyeshaBoss')
!EcoToAyeshaBoss.type := #BOSS
!insert (EcoToAyeshaBoss, DrAyeshaKhan) into RelationshipToContact
!insert (EcoResearchInstitute, EcoToAyeshaBoss) into ContactToRelationship

!new Relationship('EnerTechToJohnEmployee')
!EnerTechToJohnEmployee.type := #EMPLOYEE
!insert (EnerTechToJohnEmployee, ProfJohnMartinez) into RelationshipToContact
!insert (EnerTechSolutionsLtd, EnerTechToJohnEmployee) into ContactToRelationship

!insert (ContinentalNetwork, DrAyeshaKhan) into AddressBookMadeOfContact
!insert (ContinentalNetwork, ProfJohnMartinez) into AddressBookMadeOfContact
!insert (ContinentalNetwork, EcoResearchInstitute) into AddressBookMadeOfContact
!insert (ContinentalNetwork, EnerTechSolutionsLtd) into AddressBookMadeOfContact
</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: 
In this edge case instance, we explore a scenario where an address book contains intertwined relationships between an academic institution and its partners from various industries, showcasing complex, multifaceted networking with unique relationship dynamics and involvement in extensive note-taking.

### Address Book Instance
- **AddressBook: Global Networks Reference Book**

### Contacts
1. **Contact (Company)**
   - **Name**: Quantum Innovations Ltd.
   - **Phone**: +44-20-79301000
   - **Website**: www.quantuminnovations.co.uk
   - **Email**: contact@quantuminnovations.co.uk
   - **Industry**: Advanced Electronics
   - **Notes**:
     - **Note 1**:
       - **Author**: Helena Fox
       - **Time**: "2023-06-18T10:00:00"
       - **Type**: CALL
       - **Comment**: Discussed collaboration on the Higgs-Boson project.
   - **Address**:
     - **City**: London
     - **HouseNr**: 50
     - **Street**: Tech Park Avenue
   - **Relationships**:
     - **To**: Prof. Emily Zhang (Relation: SUBDIVISION)
     - **To**: Prof. Anton Ivanovich (Relation: BOSS)

2. **Contact (Person)**
   - **Name**: Prof. Emily Zhang
   - **Phone**: +86-10-22334455
   - **Website**: profzhangeducation.cn
   - **Email**: emily.zhang@edu.cn
   - **Title**: Director of International Studies
   - **Notes**:
     - **Note 1**:
       - **Author**: Prof. Emily Zhang
       - **Time**: "2023-09-12T12:30:00"
       - **Type**: EMAIL
       - **Comment**: Follow-up on the educational exchange program.
     - **Note 2**:
       - **Author**: Prof. Emily Zhang
       - **Time**: "2023-08-28T16:15:00"
       - **Type**: MEETING
       - **Comment**: Quarterly academic council meeting in Beijing.
   - **Address**:
     - **City**: Beijing
     - **HouseNr**: 88
     - **Street**: Knowledge Hub Road
   - **Relationships**:
     - **To**: Dr. Marcus James (Relation: COWORKER)
     - **To**: Quantum Innovations Ltd. (Relation: SUBDIVISION)

3. **Contact (Person)**
   - **Name**: Dr. Marcus James
   - **Phone**: +1-617-5557890
   - **Website**: www.marcusjamesconsulting.com
   - **Email**: marcus.james@consulting.com
   - **Title**: Senior Consultant
   - **Notes**:
     - **Note 1**:
       - **Author**: Dr. Marcus James
       - **Time**: "2023-05-05T10:45:00"
       - **Type**: CALL
       - **Comment**: Consulting session on green technology.
   - **Address**:
     - **City**: Boston
     - **HouseNr**: 101
     - **Street**: Innovation Row
   - **Relationships**:
     - **To**: Prof. Emily Zhang (Relation: COWORKER)
     - **To**: Quantum Innovations Ltd. (Relation: EMPLOYEE)

4. **Contact (Person)**
   - **Name**: Prof. Anton Ivanovich
   - **Phone**: +7-495-8889990
   - **Website**: anton-ivanovich-research.ru
   - **Email**: anton.ivanovich@research.gov.ru
   - **Title**: Head of Research
   - **Notes**:
     - **Note 1**:
       - **Author**: Prof. Anton Ivanovich
       - **Time**: "2023-04-22T09:30:00"
       - **Type**: MEETING
       - **Comment**: Innovation leaders summit in Moscow.
   - **Address**:
     - **City**: Moscow
     - **HouseNr**: 77
     - **Street**: Science Boulevard
   - **Relationships**:
     - **To**: Quantum Innovations Ltd. (Relation: BOSS)

### Edge Case Details
- **Multiple countries**: Illustrates international collaboration spanning the UK, China, the US, and Russia with diverse cultural connections.
- **Complex Relationships**: Prof. Anton Ivanovich acts as a BOSS both directly and indirectly influencing relationships via Quantum Innovations Ltd.
- **Rich Activity**: Multiple notes are associated with individual activities reflecting a busy network of communications and initiatives.
- **Involvement of an Educational Role**: Prof. Emily Zhang reflects an uncommon scenario of academic involvement in commercial and scientific entities.

The last output is partially incorrect: 
temp.soil> !QuantumToAntonBoss.type := #BOSS
temp.soil> !insert (QuantumToAntonBoss, ProfAntonIvanovich) into RelationshipToContact
<input>:1:0: Variable `ProfAntonIvanovich' in expression `ProfAntonIvanovich' is undefined.

temp.soil> !EmilyToMarcusCoworker.type := #COWORKER
temp.soil> !insert (EmilyToMarcusCoworker, DrMarcusJames) into RelationshipToContact
<input>:1:0: Variable `DrMarcusJames' in expression `DrMarcusJames' is undefined.

Please provide the complete output corrected

<domain_model>
model AddressBook

enum NoteType {
    MEETING,
    CALL,
    EMAIL
}

enum RelationshipType {
    BOSS,
    EMPLOYEE,
    SUBDIVISION,
    COWORKER
}

dataType Date
operations
    Date(date : String)
end

class AddressBook
end

abstract class Contact
attributes
    name : String
    phone : String
    website : String
    email : String
end

class Note
attributes
    author : String
    time : Date
    type : NoteType
    comment : String
end

class Company < Contact
attributes
    industry : String
end

class Person < Contact
attributes
    title : String
end

class Address
attributes
    city : String
    houseNr : String
    street : String
end

class Relationship
attributes
    type : RelationshipType
end

composition AddressBookMadeOfContact between
    AddressBook[1]
    Contact[*]
end

composition ContactContainsNote between
    Contact[1]
    Note[*]
end

association RelationshipToContact between
    Relationship[*] role isRelated
    Contact[1] role target
end

composition ContactToRelationship between
    Contact[1]
    Relationship[*] role relates
end

composition ContactContainsAddress between
    Contact[1] role source
    Address[*] role address
end


constraints
context Contact inv DifferentSourceTarget:
    self.relates->forAll(r | r.target<>self)
</domain_model>

<object_model>
!new AddressBook('GlobalNetworksReferenceBook')

!new Company('QuantumInnovationsLtd')
!QuantumInnovationsLtd.name := 'Quantum Innovations Ltd.'
!QuantumInnovationsLtd.phone := '+44-20-79301000'
!QuantumInnovationsLtd.website := 'www.quantuminnovations.co.uk'
!QuantumInnovationsLtd.email := 'contact@quantuminnovations.co.uk'
!QuantumInnovationsLtd.industry := 'Advanced Electronics'

!new Address('QuantumInnovationsAddress')
!QuantumInnovationsAddress.city := 'London'
!QuantumInnovationsAddress.street := 'Tech Park Avenue'
!QuantumInnovationsAddress.houseNr := '50'
!insert (QuantumInnovationsLtd, QuantumInnovationsAddress) into ContactContainsAddress

!new Note('QuantumInnovationsNote1')
!QuantumInnovationsNote1.author := 'Helena Fox'
!QuantumInnovationsNote1.time := Date('2023-06-18T10:00:00')
!QuantumInnovationsNote1.type := #CALL
!QuantumInnovationsNote1.comment := 'Discussed collaboration on the Higgs-Boson project.'
!insert (QuantumInnovationsLtd, QuantumInnovationsNote1) into ContactContainsNote

!new Person('ProfEmilyZhang')
!ProfEmilyZhang.name := 'Prof. Emily Zhang'
!ProfEmilyZhang.phone := '+86-10-22334455'
!ProfEmilyZhang.website := 'profzhangeducation.cn'
!ProfEmilyZhang.email := 'emily.zhang@edu.cn'
!ProfEmilyZhang.title := 'Director of International Studies'

!new Address('EmilyZhangAddress')
!EmilyZhangAddress.city := 'Beijing'
!EmilyZhangAddress.street := 'Knowledge Hub Road'
!EmilyZhangAddress.houseNr := '88'
!insert (ProfEmilyZhang, EmilyZhangAddress) into ContactContainsAddress

!new Note('EmilyZhangNote1')
!EmilyZhangNote1.author := 'Prof. Emily Zhang'
!EmilyZhangNote1.time := Date('2023-09-12T12:30:00')
!EmilyZhangNote1.type := #EMAIL
!EmilyZhangNote1.comment := 'Follow-up on the educational exchange program.'
!insert (ProfEmilyZhang, EmilyZhangNote1) into ContactContainsNote

!new Note('EmilyZhangNote2')
!EmilyZhangNote2.author := 'Prof. Emily Zhang'
!EmilyZhangNote2.time := Date('2023-08-28T16:15:00')
!EmilyZhangNote2.type := #MEETING
!EmilyZhangNote2.comment := 'Quarterly academic council meeting in Beijing.'
!insert (ProfEmilyZhang, EmilyZhangNote2) into ContactContainsNote

!new Person('DrMarcusJames')
!DrMarcusJames.name := 'Dr. Marcus James'
!DrMarcusJames.phone := '+1-617-5557890'
!DrMarcusJames.website := 'www.marcusjamesconsulting.com'
!DrMarcusJames.email := 'marcus.james@consulting.com'
!DrMarcusJames.title := 'Senior Consultant'

!new Address('MarcusJamesAddress')
!MarcusJamesAddress.city := 'Boston'
!MarcusJamesAddress.street := 'Innovation Row'
!MarcusJamesAddress.houseNr := '101'
!insert (DrMarcusJames, MarcusJamesAddress) into ContactContainsAddress

!new Note('MarcusJamesNote1')
!MarcusJamesNote1.author := 'Dr. Marcus James'
!MarcusJamesNote1.time := Date('2023-05-05T10:45:00')
!MarcusJamesNote1.type := #CALL
!MarcusJamesNote1.comment := 'Consulting session on green technology.'
!insert (DrMarcusJames, MarcusJamesNote1) into ContactContainsNote

!new Person('ProfAntonIvanovich')
!ProfAntonIvanovich.name := 'Prof. Anton Ivanovich'
!ProfAntonIvanovich.phone := '+7-495-8889990'
!ProfAntonIvanovich.website := 'anton-ivanovich-research.ru'
!ProfAntonIvanovich.email := 'anton.ivanovich@research.gov.ru'
!ProfAntonIvanovich.title := 'Head of Research'

!new Address('AntonIvanovichAddress')
!AntonIvanovichAddress.city := 'Moscow'
!AntonIvanovichAddress.street := 'Science Boulevard'
!AntonIvanovichAddress.houseNr := '77'
!insert (ProfAntonIvanovich, AntonIvanovichAddress) into ContactContainsAddress

!new Note('AntonIvanovichNote1')
!AntonIvanovichNote1.author := 'Prof. Anton Ivanovich'
!AntonIvanovichNote1.time := Date('2023-04-22T09:30:00')
!AntonIvanovichNote1.type := #MEETING
!AntonIvanovichNote1.comment := 'Innovation leaders summit in Moscow.'
!insert (ProfAntonIvanovich, AntonIvanovichNote1) into ContactContainsNote

!new Relationship('QuantumToEmilySubdivision')
!QuantumToEmilySubdivision.type := #SUBDIVISION
!insert (QuantumToEmilySubdivision, ProfEmilyZhang) into RelationshipToContact
!insert (QuantumInnovationsLtd, QuantumToEmilySubdivision) into ContactToRelationship

!new Relationship('QuantumToAntonBoss')
!QuantumToAntonBoss.type := #BOSS
!insert (QuantumToAntonBoss, ProfAntonIvanovich) into RelationshipToContact
!insert (QuantumInnovationsLtd, QuantumToAntonBoss) into ContactToRelationship

!new Relationship('EmilyToMarcusCoworker')
!EmilyToMarcusCoworker.type := #COWORKER
!insert (EmilyToMarcusCoworker, DrMarcusJames) into RelationshipToContact
!insert (ProfEmilyZhang, EmilyToMarcusCoworker) into ContactToRelationship

!new Relationship('MarcusToEmilyCoworker')
!MarcusToEmilyCoworker.type := #COWORKER
!insert (MarcusToEmilyCoworker, ProfEmilyZhang) into RelationshipToContact
!insert (DrMarcusJames, MarcusToEmilyCoworker) into ContactToRelationship

!new Relationship('MarcusToQuantumEmployee')
!MarcusToQuantumEmployee.type := #EMPLOYEE
!insert (MarcusToQuantumEmployee, QuantumInnovationsLtd) into RelationshipToContact
!insert (DrMarcusJames, MarcusToQuantumEmployee) into ContactToRelationship

!insert (GlobalNetworksReferenceBook, QuantumInnovationsLtd) into AddressBookMadeOfContact
!insert (GlobalNetworksReferenceBook, ProfEmilyZhang) into AddressBookMadeOfContact
!insert (GlobalNetworksReferenceBook, DrMarcusJames) into AddressBookMadeOfContact
!insert (GlobalNetworksReferenceBook, ProfAntonIvanovich) into AddressBookMadeOfContact
</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: 
## Overconstraint Detection Instance

### Scenario Overview
This instance focuses on a complex network within an international non-profit organization and its branches, revealing potential overconstraints in the "ContactContainsNote" and hierarchical relationships among branches.

### Instance Description

1. **AddressBook**
   - **Primary Address Book**: This address book holds contacts related to the non-profit scenario.

2. **Contacts**
   - **Organization (WorldAid International)**:
     - **Industry**: Non-profit Humanitarian Aid
     - **Phone**: +1-888-555-1234
     - **Website**: www.worldaid.org
     - **Email**: contact@worldaid.org
     - **Addresses**:
       - **Address 1**: 
         - City: New York
         - HouseNr: 870
         - Street: Liberty Avenue
     - **Relationships**: 
       - **Branch Asia**: Subdivision (TARGET: Branch Asia)
       - **Branch Europe**: Boss (TARGET: Branch Europe)

   - **Branch Asia (WorldAid Asia Pacific)**:
     - **Industry**: Non-profit Regional Branch
     - **Phone**: +61-2-5550-9876
     - **Website**: asia.worldaid.org
     - **Email**: admin@asia.worldaid.org
     - **Addresses**:
       - **Address 1**:
         - City: Sydney
         - HouseNr: 101
         - Street: Ocean Avenue
     - **Relationships**:
       - **Local NGO A**: Partner (TARGET: Local NGO A)

   - **Branch Europe (WorldAid Europe)**:
     - **Industry**: Non-profit Regional Branch
     - **Phone**: +49-30-5551-2345
     - **Website**: europe.worldaid.org
     - **Email**: europe@worldaid.org
     - **Addresses**:
       - **Address 1**:
         - City: Berlin
         - HouseNr: 75
         - Street: Wilhelmstrasse
     - **Relationships**:
       - **Branch Asia**: COWORKER (TARGET: Branch Asia)
       - **Local NGO B**: Partner (TARGET: Local NGO B)

   - **Local NGO A (Helping Hands Asia)**:
     - **Industry**: Local NGO
     - **Phone**: +91-40-5552-6789
     - **Website**: helpinghands.org
     - **Email**: info@helpinghands.org
     - **Addresses**:
       - **Address 1**:
         - City: Mumbai
         - HouseNr: 50
         - Street: Unity Road

   - **Local NGO B (Care & Share Europe)**:
     - **Industry**: Local NGO
     - **Phone**: +34-914-555722
     - **Website**: careandshare.org
     - **Email**: contact@careandshare.org
     - **Addresses**:
       - **Address 1**:
         - City: Madrid
         - HouseNr: 190
         - Street: Gran Via

3. **Notes**
   - **Note for WorldAid Asia Pacific**:
     - **Author**: John D., Head of Operations
     - **Time**: 2023-08-01
     - **Type**: CALL
     - **Comment**: Coordination for the upcoming regional conference.
   - **Note for WorldAid International**: (Exists but should not be due to constraint)
     - **Author**: Maria L., Executive Director
     - **Time**: 2023-08-10
     - **Type**: EMAIL
     - **Comment**: Review quarterly performance reports.

### Overconstraint Analysis

- **Violation**: The model constraint "ContactContainsNote" dictates that a Contact must have exactly one relationship, but this instance shows an issue: both WorldAid International and WorldAid Asia Pacific have notes but differing relationships and roles. Moreover, hierarchical issues arise as WorldAid International treats Branch Europe as a "Boss," which conflicts with anticipated non-profit structures where branches aren't typical bosses.

- **Insight**: This scenario highlights a potential overconstraint on semantic roles and relationships. In non-profit structures, the distinction between leading branches and partners needs clearer modeling, possibly introducing more nuanced relationship types. Moreover, allowance for dynamic and multi-noted interactions would better reflect such organizations' operational realities, where varying note types across contacts are common.

<domain_model>
model AddressBook

enum NoteType {
    MEETING,
    CALL,
    EMAIL
}

enum RelationshipType {
    BOSS,
    EMPLOYEE,
    SUBDIVISION,
    COWORKER
}

dataType Date
operations
    Date(date : String)
end

class AddressBook
end

abstract class Contact
attributes
    name : String
    phone : String
    website : String
    email : String
end

class Note
attributes
    author : String
    time : Date
    type : NoteType
    comment : String
end

class Company < Contact
attributes
    industry : String
end

class Person < Contact
attributes
    title : String
end

class Address
attributes
    city : String
    houseNr : String
    street : String
end

class Relationship
attributes
    type : RelationshipType
end

composition AddressBookMadeOfContact between
    AddressBook[1]
    Contact[*]
end

composition ContactContainsNote between
    Contact[1]
    Note[*]
end

association RelationshipToContact between
    Relationship[*] role isRelated
    Contact[1] role target
end

composition ContactToRelationship between
    Contact[1]
    Relationship[*] role relates
end

composition ContactContainsAddress between
    Contact[1] role source
    Address[*] role address
end


constraints
context Contact inv DifferentSourceTarget:
    self.relates->forAll(r | r.target<>self)
</domain_model>

<object_model>
!new AddressBook('PrimaryAddressBook')

!new Company('WorldAidInternational')
!WorldAidInternational.name := 'WorldAid International'
!WorldAidInternational.phone := '+1-888-555-1234'
!WorldAidInternational.website := 'www.worldaid.org'
!WorldAidInternational.email := 'contact@worldaid.org'
!WorldAidInternational.industry := 'Non-profit Humanitarian Aid'

!new Address('WorldAidInternationalAddress1')
!WorldAidInternationalAddress1.city := 'New York'
!WorldAidInternationalAddress1.houseNr := '870'
!WorldAidInternationalAddress1.street := 'Liberty Avenue'
!insert (WorldAidInternational, WorldAidInternationalAddress1) into ContactContainsAddress

!new Company('WorldAidAsiaPacific')
!WorldAidAsiaPacific.name := 'WorldAid Asia Pacific'
!WorldAidAsiaPacific.phone := '+61-2-5550-9876'
!WorldAidAsiaPacific.website := 'asia.worldaid.org'
!WorldAidAsiaPacific.email := 'admin@asia.worldaid.org'
!WorldAidAsiaPacific.industry := 'Non-profit Regional Branch'

!new Address('WorldAidAsiaPacificAddress1')
!WorldAidAsiaPacificAddress1.city := 'Sydney'
!WorldAidAsiaPacificAddress1.houseNr := '101'
!WorldAidAsiaPacificAddress1.street := 'Ocean Avenue'
!insert (WorldAidAsiaPacific, WorldAidAsiaPacificAddress1) into ContactContainsAddress

!new Company('WorldAidEurope')
!WorldAidEurope.name := 'WorldAid Europe'
!WorldAidEurope.phone := '+49-30-5551-2345'
!WorldAidEurope.website := 'europe.worldaid.org'
!WorldAidEurope.email := 'europe@worldaid.org'
!WorldAidEurope.industry := 'Non-profit Regional Branch'

!new Address('WorldAidEuropeAddress1')
!WorldAidEuropeAddress1.city := 'Berlin'
!WorldAidEuropeAddress1.houseNr := '75'
!WorldAidEuropeAddress1.street := 'Wilhelmstrasse'
!insert (WorldAidEurope, WorldAidEuropeAddress1) into ContactContainsAddress

!new Company('HelpingHandsAsia')
!HelpingHandsAsia.name := 'Helping Hands Asia'
!HelpingHandsAsia.phone := '+91-40-5552-6789'
!HelpingHandsAsia.website := 'helpinghands.org'
!HelpingHandsAsia.email := 'info@helpinghands.org'
!HelpingHandsAsia.industry := 'Local NGO'

!new Address('HelpingHandsAsiaAddress1')
!HelpingHandsAsiaAddress1.city := 'Mumbai'
!HelpingHandsAsiaAddress1.houseNr := '50'
!HelpingHandsAsiaAddress1.street := 'Unity Road'
!insert (HelpingHandsAsia, HelpingHandsAsiaAddress1) into ContactContainsAddress

!new Company('CareAndShareEurope')
!CareAndShareEurope.name := 'Care & Share Europe'
!CareAndShareEurope.phone := '+34-914-555722'
!CareAndShareEurope.website := 'careandshare.org'
!CareAndShareEurope.email := 'contact@careandshare.org'
!CareAndShareEurope.industry := 'Local NGO'

!new Address('CareAndShareEuropeAddress1')
!CareAndShareEuropeAddress1.city := 'Madrid'
!CareAndShareEuropeAddress1.houseNr := '190'
!CareAndShareEuropeAddress1.street := 'Gran Via'
!insert (CareAndShareEurope, CareAndShareEuropeAddress1) into ContactContainsAddress

!new Note('WorldAidAsiaPacificNote1')
!WorldAidAsiaPacificNote1.author := 'John D., Head of Operations'
!WorldAidAsiaPacificNote1.time := Date('2023-08-01')
!WorldAidAsiaPacificNote1.type := #CALL
!WorldAidAsiaPacificNote1.comment := 'Coordination for the upcoming regional conference.'
!insert (WorldAidAsiaPacific, WorldAidAsiaPacificNote1) into ContactContainsNote

!new Relationship('WorldAidToAsiaSubdivision')
!WorldAidToAsiaSubdivision.type := #SUBDIVISION
!insert (WorldAidToAsiaSubdivision, WorldAidAsiaPacific) into RelationshipToContact
!insert (WorldAidInternational, WorldAidToAsiaSubdivision) into ContactToRelationship

!new Relationship('WorldAidToEuropeBoss')
!WorldAidToEuropeBoss.type := #BOSS
!insert (WorldAidToEuropeBoss, WorldAidEurope) into RelationshipToContact
!insert (WorldAidInternational, WorldAidToEuropeBoss) into ContactToRelationship

!new Relationship('AsiaToHelpingHandsPartner')
!AsiaToHelpingHandsPartner.type := #COWORKER
!insert (AsiaToHelpingHandsPartner, HelpingHandsAsia) into RelationshipToContact
!insert (WorldAidAsiaPacific, AsiaToHelpingHandsPartner) into ContactToRelationship

!new Relationship('EuropeToAsiaCoworker')
!EuropeToAsiaCoworker.type := #COWORKER
!insert (EuropeToAsiaCoworker, WorldAidAsiaPacific) into RelationshipToContact
!insert (WorldAidEurope, EuropeToAsiaCoworker) into ContactToRelationship

!new Relationship('EuropeToCareAndSharePartner')
!EuropeToCareAndSharePartner.type := #COWORKER
!insert (EuropeToCareAndSharePartner, CareAndShareEurope) into RelationshipToContact
!insert (WorldAidEurope, EuropeToCareAndSharePartner) into ContactToRelationship

!insert (PrimaryAddressBook, WorldAidInternational) into AddressBookMadeOfContact
!insert (PrimaryAddressBook, WorldAidAsiaPacific) into AddressBookMadeOfContact
!insert (PrimaryAddressBook, WorldAidEurope) into AddressBookMadeOfContact
!insert (PrimaryAddressBook, HelpingHandsAsia) into AddressBookMadeOfContact
!insert (PrimaryAddressBook, CareAndShareEurope) into AddressBookMadeOfContact
</object_model>