Essayer
Exportez un vrai modèle, tout de suite
Deux modèles prêts à l'emploi et 9 formats d'export. 8 d'entre eux produisent un vrai fichier dans ce navigateur, sans compte ni installation - et chacun annonce ce qu'il abandonne avant de s'exécuter.
A UML class model: an Order composed of Payments, with Card and BankTransfer specialising Payment.
Les deux diagrammes sont des vues sur un modèle, pas des dessins. C'est cette séparation qui permet aux exports de porter du sens plutôt que des formes.
Choisir un format
Ce que cet export abandonne
Lossless. This is the model itself, not a translation of it.
Aperçu
{
"id": "uml-payments",
"name": "Payments",
"notation": "uml",
"summary": "A UML class model: an Order composed of Payments, with Card and BankTransfer specialising Payment.",
"elements": [
{
"id": "order",
"name": "Order",
"kind": "class",
"attributes": [
{
"name": "id",
"type": "UUID",
"visibility": "private"
},
{
"name": "placedAt",
"type": "Instant",
"visibility": "private"
}
],
"operations": [
{
"name": "total",
"returns": "Money",
"visibility": "public"
}
]
},
{
"id": "payment",
"name": "Payment",
"kind": "class",
"attributes": [
{
"name": "amount",
"type": "Money",
"visibility": "private"
},
{
"name": "status",
"type": "Status",
"visibility": "private"
}
],
"operations": [
{
"name": "authorize",
"returns": "AuthResult",
"visibility": "public"
},
{
"name": "refund",
"parameters": [
{
"name": "amount",
"type": "Money"
}
],
"visibility": "public"
}
]
},
{
"id": "card",
"name": "Card",
"kind": "class",
"attributes": [
{
"name": "last4",
"type": "String",
"visibility": "private"
}
]
},
{
"id": "transfer",
"name": "BankTransfer",
"kind": "class",
"attributes": [
{
"name": "iban",
"type": "String",
"visibility": "private"
}
]
}
],
"relationships": [
{
"id": "order-payment",
"from": "order",
"to": "payment",
"kind": "composition",
"sourceMultiplicity": "1",
"targetMultiplicity": "1..*"
},
{
"id": "card-payment",
"from": "card",
"to": "payment",
"kind": "generalization"
},
{
"id": "transfer-payment",
"from": "transfer",
"to": "payment",
"kind": "generalization"
}
],
"view": {
"width": 940,
"height": 340
},
"layout": {
"order": {
"x": 40,
"y": 118,
"w": 230,
"h": 108
},
"payment": {
"x": 370,
"y": 96,
"w": 250,
"h": 152
},
"card": {
"x": 720,
"y": 40,
"w": 190,
"h": 66
},
"transfer": {
"x": 720,
"y": 238,
"w": 190,
"h": 66
}
}
}
Pourquoi deux formats manquent
Le PDF est produit côté serveur en encapsulant le SVG, et un .qea est une base SQLite portant le schéma de référentiel d'Enterprise Architect - écrit en copiant un référentiel de départ produit par EA lui-même. Un navigateur ne peut fabriquer ni l'un ni l'autre, donc nous ne les simulons pas ici.