Software engineering, explicit and traceable.
Divengine Studio is an open-source, self-hosted software engineering workspace that executes the Explicit Software Engineering Method (XSEM) across intent, models, specifications, decisions, validation, and traceability.
It is a parallel engineering system, not a coding environment. Engineering discipline is infrastructure enforced by automation, not ceremony, so rigor stays lightweight and executable. The engineering core keeps intent, models, decisions, activities, and outcomes explicit and traceable. It runs as server software alongside existing IDEs, repositories, CI pipelines, issue trackers, and infrastructure, integrating with them rather than replacing them. Open source and self-hosted by design; development is centered on GitHub.
What is Divengine Studio?
Canonical definition: Divengine Studio is an open-source, self-hosted software engineering workspace that executes the Explicit Software Engineering Method (XSEM), organizing intent, models, specifications, software engineering artifacts, analysis, generators, and documentation with explicit traceability alongside existing development workflows.
Methodology: The Explicit Software Engineering Method (XSEM) is authored and maintained independently by rafageist. Reference repository: github.com/rafageist/xsem.
Divengine Studio does not teach methodology; it executes it.
XSEM balances rigor through compensating variables, enabling flexibility without methodological anarchy.
What it is
- Self-hosted server software (local or remote), including containerized deployments such as Docker.
- Executes the Explicit Software Engineering Method (XSEM) as a machine-executable methodology with explicit software engineering artifacts: intent, models, specifications, decisions, trade-offs, and validation.
- Designed to integrate with existing tools through APIs and support federated collaboration between instances.
What it is not
- Not a SaaS, IDE, framework, or methodology-agnostic platform.
- Not a replacement for source control, CI/CD, issue trackers, or infrastructure tooling.
- Not a code editor or runtime environment.
It runs as server software (local or remote) in parallel with IDEs, repositories, CI pipelines, and infrastructure; it does not replace how developers write code.
It measures, tracks, and analyzes engineering work, detecting process failures and correlating them with technical outcomes.
Multiple instances can operate independently and collaborate through standard APIs in a federated, non-centralized model.
Divengine Studio is one tool within the broader Divengine Software Solutions ecosystem.
Engineering scope covered
Divengine Studio structures software engineering work through XSEM domains that cover the full lifecycle.
The engineering core keeps intent, models, decisions, activities, and outcomes connected as explicit engineering artifacts with traceability, while source control, CI/CD, and issue trackers remain external systems. The domains below show the full scope.
Requirements and intent
Designed to support user stories, goals, constraints, and business rules as explicit requirements.
Business process modeling (BPMN)
Business processes are represented as BPMN flows to make responsibilities and intent explicit.
Specification and formal reasoning
Formal specifications support reasoning and verification before implementation.
Architecture and design
UML classes, use cases, and architecture views represent system structure.
Planning and execution
Activities and tasks are represented through workflows, Kanban boards, and Gantt timelines.
Documentation and knowledge modeling
Decisions, rationale, and domain knowledge are captured as connected documentation.
Validation, simulation, and decision support
Validation and simulation connect to engineering artifacts to support engineering decisions.
Integration with external systems via APIs
External systems integrate through APIs while traceability stays intact.
Engineering artifacts, not just code
These visuals reference common engineering artifacts so scope is clear without implying full tooling.
Kanban board
Work stages represented as columns and tasks.
Gantt timeline
Timing and dependencies represented as schedules.
UML class diagram
Structure modeled as classes and relationships.
Use case diagram
Behavior modeled from the actor perspective.
BPMN process flow
Process logic modeled as events and tasks.
Why teams use Divengine Studio
Explicit, auditable engineering work. Making intent, models, and decisions explicit reduces rework and ambiguity.
Earlier modeling, specification, and validation can surface design errors sooner and reduce rework.
Traceability from intent to implementation keeps engineering activities auditable and measurable.
Analysis, documentation, and decision making are treated as first-class engineering work, not invisible effort.
This supports estimation and planning by making work visible.
Metrics are intended to be exposed through APIs for reporting and integration.
Aligned with industry standards
Divengine Studio aligns with recognized software engineering standards as guidance for structure, engineering artifacts, and traceability.
Reference points include ISO/IEC 12207 and ISO/IEC 15288 for lifecycle and process guidance, and ISO/IEC 25010 for quality characteristics.
The platform supports requirements, documentation, and traceability practices, and modeling and specification approaches such as UML, BPMN, SysML, and formal methods, including TLA+ where appropriate.
Organizations can map their own compliance requirements onto the platform. Audits and certification remain external.
Project lives on GitHub
This website presents the vision. The Divengine Studio project is developed in the open on GitHub, which hosts the source code, issues, discussions, roadmap, and releases.
These links point to project activity, not platform features or user workflows.
Engineering flow
Intent to validated outcomes
The XSEM flow moves from intent and requirements to models, planned work, and validation.
Intent emerges from real needs and is captured with requirements, rules, and constraints.
Models and specifications make structure and behavior explicit before execution.
Activities and validation stay linked to engineering artifacts so work remains traceable.
Open source and self-hosted
Divengine Studio is open source and self-hosted, designed to run as server software on your infrastructure (local or remote).
It runs alongside existing IDEs, repositories, CI/CD, issue trackers, and infrastructure; it does not replace them.
The API-first design allows multiple instances to interconnect through standard APIs, enabling federated collaboration without a central service.
Why self host?
Keep data in your environment, integrate with your stack, and control access.
Early Roadmap
Version 0.1 - Modeling Core + Platform Foundations
- Problem -> Need -> Intent -> Model.
- Modeling core.
- Specification -> Action generation.
- First orchestrations.
Version 0.2 - Specification -> Action Engine
- Deterministic generation, templates.
- Workflow engine.
- First orchestrations.
Version 0.3+ - Full Orchestration Layer
- Top down and bottom up synchronization.
- Guidance modules.
- Deep integration with source control, CI/CD, and issue trackers.
Get involved
Help shape the platform by contributing to the repositories.
- Contribute examples, models, teaching materials, plugins.
- Test workflows and propose ideas.
- Star the repositories on GitHub.
- Open issues and share ideas.
- Try the modeling approach in your projects.
Contact: contact@divengine.com