IT and software
Class diagram (order domain, UML)
A UML class diagram where inheritance, realisation, association and aggregation are told apart by line type and end symbol
This drawing comes from one YAML file. No shape was moved by hand.
Notes in the source (in Japanese)
属性と操作は描かない。コードに書いてあるものを図へ写すと、コードが変わった瞬間に図が嘘になる(PRD §1)。図は関係を描く。
クラスはすべて矩形。 実装が DB や外部サービスを使っていても、円柱や雲では描かない —— UML では形が別の意味を持つ(ノード・成果物)。技術は形ではなく technology(副題)で言う。
Source (YAML)
examples/gallery/46-クラス図.zumen.yaml
More in this field
An on-premise server layout rack by rack, with the redundant power feeds and network links drawn as separate paths
A cloud architecture showing the VPC and its subnets, and where the load balancer, application, database and object store sit
Where data goes from collection through transformation, storage and aggregation to display, and what kind of container holds it at each step
A network layout of the links and equipment between sites, with the address range carried by each segment
An order management ER diagram with primary and foreign keys, and the one-to-many relationships drawn as crow feet
A server room where racks face each other to make hot and cold aisles, with the clearance of each aisle written in
A UML state machine with transitions, the events and guards that fire them, and the pseudostates that begin and end it
A UML use case diagram with the actors, the use cases, and the include and extend relationships between them