You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+24-18
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,14 @@ A curated list of awesome diagramming tools available for software engineering t
4
4
5
5
6
6
### **When diagrams are useful?**
7
-
Diagrams are faster and compact way for knowledge transfer. It's much easier to convey system architechture with a diagram compared to writing an essay on it.
8
7
9
-
Diagrams are especially useful in providing high level overview of software design. Following are the most-widely used diagrams by engineering teams:
10
-
-**Sequence diagram** - to visualize interaction between different components in a sequential order
11
-
-**System architecture diagram** - to visualize system architecture
12
-
-**ER diagram** - to visualize data models
13
-
-**Gantt diagram** - used for project planning and timeline estimation
8
+
Diagrams are faster and compact way for knowledge transfer. It's much easier to communicate a system architecture with a diagram compared to writing an essay on it.
9
+
10
+
Following are the major categories diagrams used by most efficient software engineering teams (based on more than 30 interviews with engineers working in startups and big tech):
11
+
-**System Architecture Diagram** - to visualize high-level structure of a software system and interactions between difference components
12
+
-**Sequence Diagram** - to visualize data flow between different components in a sequential order
13
+
-**Database Schema Diagram** - to visualize data models and relations between entities (ER Diagrams)
14
+
-**Gantt Chart** - used for project planning and timeline estimation
14
15
15
16
16
17
### **Factors to consider before choosing the diagramming tool**
0 commit comments