What is Divengine Studio

What is Divengine Studio?

Divengine Studio is a workspace for engineering knowledge. Think of it as the place where a software team writes down what it knows about the system it's building, and connects those pieces so they stay useful over time.

It's not a ticket tracker and it's not a wiki (even though you're reading one 😄). Tickets are great for "what do I do today?", wikis are great for "here's how things work". Studio answers a different set of questions:

• Why does this requirement exist, and where did it come from?
• If we change this business rule, what else is affected?
• Which tests prove that this use case works, and did they pass?
• Are we actually ready to move from Elaboration to Construction?
• What exactly did we agree on at the last release?

Who is it for?

You are…	Studio helps you…
A business or requirements analyst	Capture business actors, use cases, rules and requirements in a structured way, and see what's still unapproved.
An architect or designer	Keep diagrams and decisions next to the requirements they serve, with real links between them.
A project or process manager	Run a Development through phases, iterations and milestones, and get an honest readiness check before each milestone.
A tester or QA lead	Design test plans, run them, record evidence, report issues, and show which requirements are verified.
A team lead	Plan the work on boards, split it into subtasks, see what's blocked and what's overdue.
A developer	Find out what a feature is supposed to do, why, and how it will be tested, without digging through old chats.

The building blocks

mindmap
  root((Divengine<br/>Studio))
    Artifacts
      Requirements
      Use cases
      Business rules
      Decisions & risks
      Knowledge & standards
    Knowledge base
      Articles in a tree
      Links by code
      Mentioned in
    Diagrams
      BPMN processes
      UML diagrams
      Embedded in text
    Traceability
      Explicit links
      Typed relations
      Impact & coverage
    Unified Process
      Developments
      Phases & milestones
      Iterations & activities
      Change requests
      Baselines
      Readiness
    Project management
      Projects & subprojects
      Tasks & subtasks
      Kanban boards
      Comments
      Timesheets
    Test management
      Plans, suites, cases
      Runs & results
      Evidence
      QA issues
      Dashboard

Loading

• Artifacts are the units of knowledge: a requirement, a use case, a business rule, a decision, a risk. Each one has its own fields, its own lifecycle (draft → approved → baselined…) and a full revision history.
• Diagrams are first-class citizens, not pasted images. You draw BPMN and UML right in the browser, link diagram elements to artifacts, and embed diagrams inside any text.
• Traces are the glue. "This use case refines that requirement", "this test verifies that use case", "this change request impacts that rule". Every trace has a type, a direction and, if you want, a rationale.
• Developments organise the work using the Unified Process: four phases, each closed by a milestone, iterations inside them, activities, work products and change requests.
• Project management organises the day-to-day work: projects and subprojects, tasks and subtasks on Kanban boards, related tasks and comments.
• Test management turns quality into evidence: test plans, runs that freeze exactly what was tested, step-by-step results, attachments and QA issues.

A few principles we care about

Explicit beats clever. Studio never infers relationships for you. If a requirement isn't traced to anything, Studio tells you it's a gap instead of pretending it's covered.

History is sacred. Artifacts keep every revision. Baselines remember the exact revision of every record that was part of them. A completed test run is historical evidence and can't be quietly edited later.

Advice, not handcuffs. Readiness checks tell you what's missing before a milestone, but the decision to move on stays with the people running the project.

Your data, your server. Studio is a normal Drupal site. You can host it anywhere, back it up like any database, and extend it with the huge Drupal ecosystem.

What Studio is not (yet)

Honesty helps: Studio doesn't replace your issue tracker, your CI pipeline or your source code host. It sits next to them and keeps the knowledge that those tools are bad at keeping. The AI assistant connection is read-only on purpose.

Ready to try it? Head over to Installation.