DEP — DEVlink Engineering PlatformUser Guide
ChargeLink docs ↗
Developed byDEVlink

Requirements to Model

This workspace takes you from written requirements to an editable DEP model, with the requirements kept next to the model as a versioned baseline. You can compose behaviour from rules and equations without AI. You can also ask the optional DEP Engineering CoPilot to propose a model. Open it with System → Requirements to model.

Requirements to model: the requirements browser on the left, the three-step model workflow on the right.
Requirements to model: the requirements browser on the left, the three-step model workflow on the right.

The three steps

  1. Define modelImport requirements or describe the problem, then choose how to build the model.
  2. Review proposalInspect the proposed blocks, parameters and requirement links, and correct them.
  3. Verify & useRun numerical verification against expected values, then save the model and prepare it for the System.

Step 1: get requirements in

OptionUse it when
Import a document → Import requirements…You have Excel, CSV, ReqIF or requirements JSON. Choose the worksheet and map the ID and description columns. Problems are reported as DEP-REQ-IMPORT, and your current baseline is not replaced.
Describe the problemYou want to type the requirements yourself.
Try VCU exampleYou want to see the workflow with a ready-made baseline: VCU torque demand with two requirements.
The VCU example: VCU-001 “Every 10 ms, requested torque shall equal normalized accelerator demand multiplied by 200 Nm” and VCU-002 “Requested torque shall be limited to the range 0 to 200 Nm”.
The VCU example: VCU-001 “Every 10 ms, requested torque shall equal normalized accelerator demand multiplied by 200 Nm” and VCU-002 “Requested torque shall be limited to the range 0 to 200 Nm”.

In the browser, find a requirement and select it, then use Edit selected requirement or Remove selected requirement. Select Save draft to keep your work. Resume saved draft continues later. Saved revisions and saved models are listed under the browser.

Step 1b: choose how to build the model

  • Describe or import: start from your requirements (above).
  • Rules and equations: Compose supported behavior locally. The guided rule builder needs no AI connection. You build the model from supported rule and equation forms, each linked to a requirement.
  • 12-cell battery plant: Review per-cell physical parameters for a battery plant template.

Optional: the AI CoPilot

If you have set up an AI connection (AI Connections), choose a CoPilot task:

  • Suggest a physical specification: proposes parameters for RC, thermal, rotational or 12-cell battery behaviour for you to review before building.
  • Generate a control model: proposes a control model from the requirements.
  • Improve requirement wording: suggests clearer wording. Accept it with Apply this wording.
  1. Choose the Saved AI connection. Manage in Settings opens the connection settings.
  2. Read Review data to be sent.
  3. Tick I approve sending this baseline to the displayed destination. Nothing is sent before you approve.
  4. Start the task, for example Propose engineering equation.

Proposals are checked structurally and against behaviour acceptance before anything is created (DEP-AI-PROPOSAL, DEP-MODEL-BEHAVIOR).

Step 2 and 3: review, verify, use

  1. Review the proposal: each block and parameter shows the requirement it implements.
  2. Enter test inputs and independent expected values, then run numerical verification. If it cannot complete, DEP reports DEP-MODEL-VERIFY and records no report.
  3. Save the model. It opens in Model Designer for further editing. Then use Check model → Prepare for System → Verify in System.

A generated model that passes its checks is not proof of physical accuracy. Review the requirements and use expected results that come from an independent source.

HomeTop