Developers

Generate database schemas, API specifications, and code scaffolds from conceptual models. Start with understanding, deliver working software.

What CaseTalk Generates

developer workflow

How developers typically use CaseTalk:

1. Get the Model
   Analyst/architect creates conceptual model
2. Generate Schema
   Export DDL for your target database
3. Generate Code
   Export classes/Structs for your language
4. Iterate
   Model changes? Regenerate artifacts

Technical articles

Understand the technical aspects:

• From Ambiguity to Precision

  The Journey from 'Customer → Order' to a Formal Semantic Layer Consider five ways to represent the same business reality: Customer → Order Customer has Order Customer buys Order The person places order . "The person or organisation, identified in our system as customer number 123, placed an order for our products or services identified by order number 20260991." The final expression isn't just "better documentation"—it's the foundation of a semantic layer : a formal, structured representation of business knowledge that sits between your SMEs' expertise and your data systems. This semantic layer is the result of applying FCO-IM (Fully Communication-Oriented Information Modeling), not just an improvement in notation.

• Python DataClass

  In response to Python's growing popularity among developers, CaseTalk extends its support to help developers align their work with business requirements. We've harnessed the power of Python's dataclasses to bridge this gap. However, dataclasses alone offer limited support for the rich conceptual information models in CaseTalk. To overcome this limitation, we've incorporated metadata support.

• Generated ERD, UML and Concept Map

  This short video demonstrates how CaseTalk automatically generates ERD, UML Class Diagram and simplified Concept Map.

• Reverse Engineering

  The reverse engineering creates an elementary CaseTalk model through a simple ADO connection. The tables, columns, key information, and relations are all created as facts and are made to be verbalized. This way, the database model can be validated as a conceptual model following the regular rules.

• Development with FCOIM and UML

  Software evolves rapidly, often outpacing changes in data structures. Over time, applications undergo transformations, upgrades, or migrations to new platforms. Effective software design plays a crucial role in managing the application life cycle. While widely used, the traditional UML design approach can sometimes be imprecise.

• Transformation of Models

  A conceptual information model of the business is a great asset, as well as a solid investment due to it being independent of technology. Since IT undergoes rapid changes, the only truly long-living asset is the information model.