DB markup language

Hi Freddy,

I’m quite certain that most capabilities noted in DBML can find its way to the model in the Thinkwise platform. Table partials have always lingered on the backlog since the inception of the Thinkwise Platform but have been pushed to the background due to dynamic modeling. We could take a look at that again at one point.

What would be the use case to use this markup language instead of simply modeling the entities directly using the Software Factory?

Hi ​@Anne Buit . Thanks for the reply.

Use Cases for DBML in (or alongside) Thinkwise Projects

1. Collaborative conceptual data modeling with clients or prospects
   Define data structures together in a readable, text-based format without requiring access to the Software Factory.
2. Kickstarting greenfield projects without an existing database or Upcycler
   Quickly define models externally, then import or convert them as needed.
3. Pre-sales and demo support
   Rapidly build and visualize domain models to showcase understanding of the client’s business process.
4. Auto-generated data model documentation
   Export structured, visual documentation of the model for clients, auditors, or internal use.
5. Use as a prototype or wireframe before formal modeling
   Serves as an intermediate step to validate data structures before building in Thinkwise.
6. Support for DevOps and version control
   Store DBML files in Git with full collaboration via branches and pull requests.
7. Hybrid development scenarios
   Use DBML as the source for database models that are partly implemented in Thinkwise and partly elsewhere.
8. Standardization in tenders or multi-vendor environments
   Neutral format to align data models across vendors or contractors without tool lock-in.
9. Training and onboarding of new team members
   Easy-to-read and -write model format for junior developers or business analysts learning data modeling.
10. Legacy system migration preparation
    Start with DBML based on interviews or reverse engineering before formalizing models in Thinkwise.

Why Use DBML Instead of Modeling Directly in Thinkwise?

DBML is simpler, text-based, version-controlled, and tool-agnostic. It enables fast and low-barrier collaboration with non-technical stakeholders, allowing you to draft, review, and document data models before committing to full implementation in the Thinkwise Software Factory. This makes it ideal for co-creation, workshops, pre-sales, and agile project starts where flexibility and clarity are more important than immediate technical detail. It’s not a replacement for the SF—it’s a complementary way to bridge the gap between business understanding and system design.

Definitely interesting to have a closer look at and consider to support it in combination with a DB modeler in the Universal-based SF ​@Anne Buit. Some of the Business Analysts at Wagenborg used this too in the past!

​@Suleyman is this still being used at Wagenborg?

​@Arie V  We still use DB Diagram for setting up the first ‘concept-model’ when starting with new features / processes, since it is much easier for business analysts to use this tool, to create a datamodel + visualize it to have discussions with developers first. Before actually spending time in SF. 

But after a good model has been created in SF, we proceed to maintain the datamodel via SF. 

But the idea to simply draw up something in DB Diagram + import it to SF for quick demo purposes is great. It also enables us to quickly detect some ‘gaps’ in the process or identify inaccurate relations / tables in the datamodel.

Have a nice week guys!