System BuildAdvancedGeneralEngineeringManufacturing

System Database & Core Entities Planning Prompt

Derives core entities and relationships for a new system from its business processes.

Audience: IT, back-end engineers · Last updated 2026-07-17
Contents

Scenario

Derives core entities and relationships for a new system from its business processes.

Applicable Industry or Company Size

  • General
  • Engineering
  • Manufacturing

Preparation Before Use

  • A description of the business process.
  • Data export from an existing system (if any).

Variable Reference

VariableDescription
[Company Name]Your company's official name
[System Name]The system being planned
[Main Business Objects]e.g., customer, quote, project, part number

Full Prompt

Prompt
You are a senior database architect. Plan the core entities and relationships for a system.

[Background]
- Company: [Company Name]
- System: [System Name]
- Main Business Objects: [Main Business Objects]

[Output]
1. A list of entities, each with: fields, data type, required flag, default value, notes.
2. Primary keys and relationships (1:N / N:M).
3. Audit fields (created at, created by, updated at, updated by).
4. Soft-delete strategy.
5. Indexing recommendations.
6. 5 example common queries, confirming the data model supports them.
7. Classification of private / sensitive fields.

[Judgment Criteria] Do not over-normalize the design to the point queries become difficult; avoid over-denormalizing to the point consistency becomes risky.

[Handling uncertain information]
If any of the variables below have not been filled in or the information is insufficient, list the missing fields directly and ask the user — do not assume or fabricate data.

[Prohibited]
- Do not fabricate statistics, regulation numbers, certification names, or client case studies.
- When professional judgment is insufficient, explicitly mark "requires human confirmation" rather than inferring on your own.

[Final self-check]
After producing the output, list a self-check at the end covering: (1) whether any fabricated numbers, regulations, standards, or client names were used; (2) whether any unfilled but important variable was ignored; (3) whether assumptions are clearly labeled.

Usage Steps

  1. Fill in the variables.
  2. Draw the ERD using a diagramming tool (dbdiagram, Mermaid).
  3. Review with the back-end team.

Example

The core of a quoting system usually includes Customer, Quote, QuoteItem, and Product.

Common Mistakes

  • Putting all fields in one table.
  • Missing a soft-delete strategy, creating compliance risk.

Cautions

  • Personal-data fields need to consider encryption and access logging.
Last updated 2026-07-17

Need further customization to fit your company's process and industry?

AEGIS POWER INTEGRATIONS offers AI adoption, process assessment, and systems integration consulting to help you turn prompts into a stable, working internal process.