Skip to content
Source on GitHubVisitors

Functional decomposition graph

Aims to structure frontend application development by identifying and linking its UI elements, data elements, actions and functions.

Diagram · origin tag etalii/functional-decomposition-graph · Business process & workflow notation

Availability

Availability per host
HostStateHow to get it
StandalonePrototypeNot yet released
DesktopPrototypeNot yet released
IntelliJ PlatformNot plannedNot planned
Visual Studio CodeNot plannedNot planned
EclipseNot plannedNot planned
ThinkRailNot plannedNot planned
NotionNot plannedNot planned
ClaudeNot plannedNot planned

What it is for

Functional decomposition graph (UI elements, data elements, actions and functions linked parent to child, drawn as a superellipse, parallelogram, trapezoid and diode with bezier arrows; `.fdg`, ADP's own line-oriented schema); `functional-decomposition-graph`

Why a specialized view helps

Linking UI, data, actions and functions parent to child needs distinct shapes and strict rules; a dedicated tool enforces them so the decomposition stays traceable.

File formats

ExtensionFormatReadsWrites
.fdg.fdgYesYes

Screenshots

UI elements, actions, data elements and functions in their four shapes, linked parent to child by bezier arrows, with the two comment notes; Toolbox showing all five kinds. Nothing selected.

Standalone, at 3e2df46

What is visible: UI elements, actions, data elements and functions in their four shapes, linked parent to child by bezier arrows, with the two comment notes; Toolbox showing all five kinds. Nothing selected.

Why it matters: UI elements, actions, data elements and functions each keep their own shape and are linked parent to child, so a frontend's structure can be traced from what a user sees down to the functions behind it.

Licence: Apache-2.0

Background

  • A notation defined by the user of this repository, so ADP owns the schema and the etalii/ origin rather than a standards body's

Focus areas

Sources