DSLCore
Menu

How DSLCore Works

DSLCore generates operational applications from an explicit structural definition.

Instead of building every screen and workflow separately, the operation is described in terms of entities, relationships, workflow states, rules, responsibilities, evidence and reporting requirements.

That model then drives the generated system.


The model is the common source

A DSLCore definition can generate database structure, validation rules, API behaviour, interfaces, navigation between related records, workflow states, reports, relationship diagrams and system documentation.

Because these outputs come from the same definition, they are less likely to drift apart.

Changes are made to the model and the system is regenerated.


Why this differs from custom development

Traditional custom development often locks operational meaning inside code, screens and individual developer decisions.

DSLCore keeps the structure visible, making it easier to review the model with operational users, identify exceptions, change workflows before a large implementation and retain documentation that reflects the system.


Why this differs from packaged software

Packaged software provides a predefined model. That can work well for common financial and transactional functions, but operational edge cases often fall outside it and return to spreadsheets.

DSLCore is intended for those operational areas and works alongside enterprise systems rather than competing with them.


From reference application to organisation-specific system

A reference application provides a working starting point. The main entities, relationships, workflows and controls are already visible.

select a reference application
→ review the current operation
→ tailor terminology and structure
→ confirm roles, rules and controls
→ regenerate the application
→ validate with users
→ pilot with real scenarios and data
→ implement

This reduces blank-page design work while recognising that operational systems must be validated against the organisation that will use them.


Start with a bounded area

DSLCore works best where spreadsheets perform important work, reporting is manual, workflows are understood but poorly documented, or current systems do not reflect actual operations.

Explore reference applications · Discuss an operational area