# Describe apps in UML

**URL:** <https://community.fibery.io/t/describe-apps-in-uml/1631>\
**Category:** Ideas & Features\
**Created:** [May 14, 2021, 6:05pm UTC](https://community.fibery.io/t/describe-apps-in-uml/1631 "2021-05-14T18:05:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jean1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jean1/32/1669_2.png) [@jean1](https://community.fibery.io/u/jean1)\
**Post date:** [May 14, 2021, 6:05pm UTC](https://community.fibery.io/t/describe-apps-in-uml/1631/1 "2021-05-14T18:05:43Z")

</div>

I was thinking more about this topic, particularly when it got into association classes:

> [@Relationship properties](https://community.fibery.io/t/relationship-properties/887):
>
> This might be a big ask, but would it be possible to add properties to relationships as well as entities (like is possible with a graph database)? I realise that the more sophisticated you make the underlying platform, the greater the risk of users being scared away by the complexity, but for me, it would put you into a whole different league. It could be a feature that can be enabled but is disabled by default so as to not scare non-techies…

An app already looks like a UML diagram ([PlantUML source](https://www.planttext.com/?text=PL9RRW8n3FptAQpzHDehLBJG1qA8rS85Gd0XRLvD72fKzUvDifHssuyyFB5dx56caKNWP3G0AzQ4CsUyisGvOliJu5o9Gn06ZcfFICRp6GsP7OKuG585gGd02_ag3eJDUjdZDkH8sKE37x3UlP1aTIASj2qsIpfZJp5fRk3pLraNt3v9nfMmEJPPkXHBBMAyFZOe8dO1ke1jUuEpSr7EWSl43oGu1O8ALgbEiJoED3P2KyHPlohKjrAwb0TismdUbWPL7cs4hhrtsIAR7qRup5aMak5oZXX6UZrnSD4FuySYEa86GqgbixXWCcD7DkwPtqKWdDE9jFD_FDcICDMGBMoh7PaXYC85rrjrPiCkdA7kLV7UAmbbgz5TEa1UDJDREr2DshnW_-tiIPE8tuFL-v0Phk6tmk-oHyLFQJSKUHVLjR6x86oM60uitdH9wzpCMwAOlykVz4MCYIvkhEgNX0hXZoR0bEm-V_8l)).

Here’s _My Apps_:

 ![plantuml](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2714dcea2a4bb347f3cc2abccaee9c07172b843d.png)

Here’s the _GitHub_ app ([PlantUML source](https://www.planttext.com/?text=fLNBRgCm5Dtp5LQwwLJgebiMLO7GITIyb1AfMyVS9bO1CxR9A1hDlu-nIN0S4fL9Di7dFdpEiRcy28cvhFBCyxOq1GHvAVSeXtmDN1Y8K4uoy3oIOI7G4aecg6HyZ_vuIFtkPZW7vACa_aWqy9FAKRL64rfyANWodhrfU0Y2S5fAoWe5ByVHw5YnAbCi8KM1L95XaCGQNN2wKx22eb4SlONp3mr773gINwiiGowJHIMsPvbtka7DOcYwjv4fI-ad9UVHlmVr8SS5sVPKlk1C0gavErBUHu5TVXEpXJ9W2Ryg4BBlmN3yAVLJY0KS9DR5nk-CYJCJhSFKwodm3U1rPaecZ7n1QhJJ4Z9Q07gNM5P2OqlOKVYjUX0g3WtCBlfn13WzOp6hwXjvvRPqNmlDomLhAd2xusCXAkZfzGIhuubJQfYU-jjfxA9QPxIvnQwtbcS1aNG7EgZinQAfRfLs-kSOrouFces7hXF_RTsHzFqF1GLHCfxFKBXAalcijNMgPqzVNzc65jzG5-UOPhSSVSDky310Zu_wptxnVAGKq4sXJgL9V51Pfnd4CF8yQvBMMUR6k-XfRRr2pLAWLyvoDrzVoZvD4cPd3vvgNSze9HHt_-XUkFSykqaZlT6eZjAe1k5cMQrzCrvQnCrjNddV7W0NSwnHTNLFtUlodgs2IcuPlohIZAtwi-XcATCw33FpuR9LRVnfS4Ra6BIudnHqRFW2HLf_oVy1)) (not super rigorous):

 ![github](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/43d25a40556f065fb8e08a7a8190f34611da1fb5.png)

It would be pretty cool if Fibery could import and export PlantUML diagrams 😁

This is just a thought experiment really. Lots to think about.  
A complex app with many fields and relations would be super easy to bootstrap as a PlantUML file.  
I actually did something like this using the [Orchard XML import format](https://docs.orchardcore.net/projects/O1/en/latest/Documentation/Import-Export/): quick & dirty YAML file, transform to XML, import, try it out, iterate. UML would be much nicer.

---

<div class="post-metadata">

**Author:** ![MaxL](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/maxl/32/6137_2.png) [@MaxL](https://community.fibery.io/u/MaxL)\
**Post date:** [October 12, 2023, 9:41am UTC](https://community.fibery.io/t/describe-apps-in-uml/1631/2 "2023-10-12T09:41:39Z")

</div>

Would be really cool if at least the whiteboard would support all UML forms.
