Dataset Viewer
Auto-converted to Parquet Duplicate
text
stringlengths
1
225
[
{
"Elem. name": "Control panel",
"description": "Provide interface to interact with the system",
"children": [],
"type": "Component",
"presntation": [
"System model"
],
"connected as target": [
{
"name": "Microcomputer",
"connection": "Visualize analysis result and receive control for subsystems"
}
],
"connected as source": [
{
"name": "Head of quality control",
"connection": "Provide quality grade for the batch"
}
]
},
{
"Elem. name": "Conveyor belt ",
"description": "Move fruits through the machine to collect images",
"children": [],
"type": "Component",
"presntation": [
"System model"
],
"connected as target": [
{
"name": "Quality control personel",
"connection": "loads proudcts"
}
],
"connected as source": [
{
"name": "Camera module",
"connection": "move fruits to the camera zone"
}
]
},
{
"Elem. name": "Camera module",
"description": "",
"children": [],
"type": "Component",
"presntation": [
"System model"
],
"connected as target": [
{
"name": "Conveyor belt ",
"connection": "move fruits to the camera zone"
},
{
"name": "Lighting module",
"connection": "Light"
}
],
"connected as source": [
{
"name": "Microcomputer",
"connection": "image"
}
]
},
{
"Elem. name": "Microcomputer",
"description": "Handle video. Send data and recieve the analysis from server. Visualize the results. Control hardware sub-systems",
"children": [],
"type": "Component",
"presntation": [
"System model"
],
"connected as target": [
{
"name": "Camera module",
"connection": "image"
},
{
"name": "Classification algorithm",
"connection": "Provide batch analytics"
},
{
"name": "Wifi",
"connection": "Provide internet acess"
}
],
"connected as source": [
{
"name": "Control panel",
"connection": "Visualize analysis result and recieve control for subsystems"
},
{
"name": "Detection algorithm",
"connection": "sends video taken"
}
]
End of preview. Expand in Data Studio

General

The dataset consists of the following items:

  1. dataset.csv: A tabular representation of the engineers involved in each case (aq, fp, in), providing an impact analysis of the proposed changes on the system. Each engineer change (EC) has a unique number (ec_number) and a corresponding description. The team member column specifies which team member proposed the component listed in the Component column, which would be included in the change. The team member labeled "combined" represents a set of components mentioned by all team members, without duplicates.

  2. aq.txt, in.txt, and fp.txt: Text files containing the system model descriptions for each case. These files were used as contextual input for the model.

Prompt

The prompt used to generate EC suggestions is the following:

## Role
You are the system engineer specializing in engineering change management.
## Context
{proj_description}
You have to assess the potential consequences of a change or modification to a system i.e. conduct an impact analysis. The team has built a model of the product they are developing, which is presented below:
"""
{model_data}
"""

The specific incoming change to be analyzed is: `{change_request}`.
## Instruction
Complete your task in phases. Finish each phase before proceeding to the next:
**Phase 1: Define your task**
Describe the given task briefly. Provide information about any constraints you have.
**Phase 2: Identify impact**
List all components that are directly influenced by the incoming change, along with your reasoning.
A component is considered **directly influenced (impacted)** by a change if: "It must undergo a modification as a first-order consequence of the proposed change, without requiring propagation through intermediary components (i.e., as a secondary or cascading effect)."
**Phase 3: Self-evaluation and verification**
Cross-check each pair: "Is this impact logically consistent with the model’s architecture?
Explain in 10 words or less."
**Phase 4: Final output**
Using the verified pairs, create the final output in the specific format described below. Use the reasoning text from the second phase.
"""
&&&
Component: <component_name>
Reasoning: <reasoning_text>
Component: <component_name>
Reasoning: <reasoning_text>
Component: <component_name>
Reasoning: <reasoning_text>
Component: <component_name>
Reasoning: <reasoning_text>
...
&&&
"""
## Constraints
Use exact component names from the model.
List only components in your analysis. Do NOT list sub-systems or systems.
**Definition:** A component is the smallest functional or structural unit of a system. It can be internal or external.
Downloads last month
27