用什麼軟體畫流程圖?
我用思維導圖比較多,mindmapper。但是有一個問題:思維導圖是很嚴格的從上到下的順序,你當然可以創造一個新topic,然後再把它跟原先的topic連起來,但那樣很難看。而visio我就覺得為什麼那麼小啊?畫兩下怎麼就沒地方了?mindmapper怎麼就沒這樣的問題,好像是無限大的那樣。
·······································這是擴張後的結果。我試探了一下,這樣的圖很難看。不知道應該怎麼調整。
可以試試ProcessOn.com, 一個專業在線畫流程圖的工具,使用ChromeFirefox瀏覽器,支持快捷鍵,非常方便。快捷鍵如下:Ctrl+A 全選,當移動整張圖時非常方便Ctrl+B 格式刷,選中圖形A,按Ctrl+B,選中圖形B,則對圖形A的設置會應用到圖形B上Ctrl+C 這兩個,不用說了Ctrl+V
1.我用思維導圖比較多,mindmapper。但是有一個問題:思維導圖是很嚴格的從上到下的順序,你當然可以創造一個新topic,然後再把它跟原先的
topic連起來,但那樣很難看。
思維導圖壓根就不適合畫流程,流程更多是動態分析,思維導圖是靜態分析;靜態分析中又包括兩種,一種是樹狀展開,一種是多維度分析,如常見的表格矩陣二維分析。思維導圖只適用於靜態分析中的圍繞一個中心點樹狀展開場景。
2. 而visio我就覺得為什麼那麼小啊?畫兩下怎麼就沒地方了?當前visio仍然是最好的畫流程的工具。裡面包括了三種常見的,一種是最基本簡單的流程圖,一種是支持階段和職能帶的流程圖,這種往往是用的最多的。還有基於EPC事件鏈的流程圖,往往在企業架構中的最底層流程會用到。
Office 環境下還是用 Visio 畫吧。
作為 LaTeX 黨,我都是用 TikZ 畫的。
TeXample 上的例子:
egin{tikzpicture}[node distance = 2cm, auto]
% Place nodes
ode [block] (init) {initialize model};
ode [cloud, left of=init] (expert) {expert};
ode [cloud, right of=init] (system) {system};
ode [block, below of=init] (identify) {identify candidate models};
ode [block, below of=identify] (evaluate) {evaluate candidate models};
ode [block, left of=evaluate, node distance=3cm] (update) {update model};
ode [decision, below of=evaluate] (decide) {is best candidate better?};
ode [block, below of=decide, node distance=3cm] (stop) {stop};
% Draw edges
path [line] (init) -- (identify);
path [line] (identify) -- (evaluate);
path [line] (evaluate) -- (decide);
path [line] (decide) -| node [near start] {yes} (update);
path [line] (update) |- (identify);
path [line] (decide) -- node {no}(stop);
path [line,dashed] (expert) -- (init);
path [line,dashed] (system) -- (init);
path [line,dashed] (system) |- (evaluate);
end{tikzpicture}
draw.io,網頁版跨平台無需安裝,功能強大超出想像,免費,數據保存在雲端。
visio的畫板可也以無限擴大,你超出了原來的範圍,它就自動擴展。
需要高大上的效果就花錢買個 OmniGraffle pro 吧
Omni系列都很良心。在我看來 沒有做不漂亮的工具 只有沒想清楚的糊塗腦子。說幾個用過的
- PowerPoint能滿足大部分需求了,節點能自動幫你連接,如果圖特別大,可以調整頁面大小的
下面說倆需要寫代碼的
2. plantuml 的activity圖,需要java
下面一個例子,如下代碼 保存成 sequenceDiagram.txt ,下載 plantuml.jar 放到你的目錄java -jar plantuml.jar sequenceDiagram.txt 可以用-T參數指定格式,比如svg啦@startuml
start
:ClickServlet.handleRequest();
:new page;
if (Page.onSecurityCheck) then (true)
:Page.onInit();
if (isForward?) then (no)
:Process controls;
if (continue processing?) then (no)
stop
endif
if (isPost?) then (yes)
:Page.onPost();
else (no)
:Page.onGet();
endif
:Page.onRender();
endif
else (false)
endif
if (do redirect?) then (yes)
:redirect process;
else
if (do forward?) then (yes)
:Forward request;
else (no)
:Render page template;
endif
endif
stop
@enduml
生成的是這樣的,樣式可以自己定義,顏色填充等。
"改變一下樣式
skinparam titleFontSize 25
skinparam titleFontStyle bold
skinparam activityFontColor white
skinparam activityBorderColor #0099CB
skinparam activityBackgroundColor #0099CB
skinparam activityFontSize 16
skinparam activityFontStyle plain
skinparam activityFontName Georgia
skinparam activityStartColor #00FF00
skinparam activityEndColor #FF0000
skinparam activityBarColor #0099CB
"#3AB871
skinparam activityArrowFontColor #000000
skinparam activityArrowFontSize 18
skinparam activityArrowColor #8699A3
skinparam activityArrowFontStyle bold
"skinparam activityArrowFontName
skinparam swimLaneBorderColor #0099CB
skinparam swimLaneBorderStype dashed
skinparam swimLaneTitleFontColor #0099CB
skinparam swimLaneTitleFontSize 40
skinparam swimLaneTitleFontStyle bold,italic
skinparam swimLaneTitleFontName Clibri
skinparam activityDiamondFontColor white
skinparam activityDiamondFontSize 16
優點:代簡單,帶邏輯,自動化,應用廣泛,適合特別複雜的圖。
流程圖僅是其中一個,其他的還有時序圖,UML,組件圖等,用例圖。具體看這裡 Open-source tool that uses simple textual descriptions to draw UML diagrams.缺點:可定製化差3. 大殺器,TikZ,功能強大,唯一限制的,只有你的想像力, 700頁以上的文檔。如果裝了TeXLive, 用texdoc tikz 命令能調出這個700頁的文檔官方的一個例子改的documentclass[x11names]{article}
usepackage{tikz}
usepackage{ctex}
usetikzlibrary{shapes,arrows,chains}
%%%&<
usepackage{verbatim}
usepackage[active,tightpage]{preview}
PreviewEnvironment{tikzpicture}
setlengthPreviewBorder{5mm}%
%%%&>
egin{comment}
uuuu
end{comment}
egin{document}
% =================================================
% Set up a few colours
colorlet{lcfree}{Green3}
colorlet{lcnorm}{Blue3}
colorlet{lccong}{Red3}
% -------------------------------------------------
% Set up a new layer for the debugging marks, and make sure it is on
% top
pgfdeclarelayer{marx}
pgfsetlayers{main,marx}
% A macro for marking coordinates (specific to the coordinate naming
% scheme used here). Swap the following 2 definitions to deactivate
% marks.
providecommand{cmark}[2][]{%
egin{pgfonlayer}{marx}
ode [nmark] at (c#2#1) {#2};
end{pgfonlayer}{marx}
}
providecommand{cmark}[2][]{
elax}
% -------------------------------------------------
% Start the picture
egin{tikzpicture}[%
&>=triangle 60, % Nice arrows; your taste may be different
start chain=going below, % General flow is top-to-bottom
node distance=9mm and 70mm, % Global setup of box spacing
every join/.style={norm}, % Default linetype for connecting boxes
]
% -------------------------------------------------
% A few box styles
% &
% positioning of nodes
ikzset{
base/.style={draw, on chain, on grid, align=center, minimum h=4ex},
proc/.style={base, rectangle, text w=8em},
test/.style={base, diamond, aspect=2, text w=4em},
term/.style={proc, rounded corners},
% coord node style is used for placing corners of connecting lines
coord/.style={coordinate, on chain, on grid, node distance=6mm and 25mm},
% nmark node style is used for coordinate debugging marks
nmark/.style={draw, red, circle, font={sffamilyfseries}},
% -------------------------------------------------
% Connector line styles for different parts of the diagram
norm/.style={-&>, draw, lcnorm},
free/.style={-&>, draw, lcfree},
cong/.style={-&>, draw, lccong},
it/.style={font={smallitshape}}
}
% ------上面的是設計,可以復用,下面開始畫圖-------------
% Start by placing the nodes
ode [proc, densely dotted, it] (p0) {New trigger message thread};
% Use join to connect a node to the previous one
ode [term, join] {Trigger scheduler};
ode [proc, join] (p1) {Get quota $k &> 1$ is p1};
ode [proc, join] {Open queue};
ode [proc, join] {Dispatch message};
ode [test, join] (t1) {Got msg? is t1};
% No join for exits from test nodes - connections have more complex
% requirements
% We continue until all the blocks are positioned
ode [proc, join] (p2) {$k mathbin{{-}{=}} 1$};
ode [proc, join] (p3) {Dispatch message};
ode [test, join] (t2) {Got msg?};
ode [test] (t3) {Capacity?};
ode [test] (t4) {$k mathbin{{-}{=}} 1$};
ode [proc] (x1) {I am x1};
ode [proc, join, fill=lcfree!30, left=of x1] (x2) {I am x2};
ode [proc, join, left=of t4] (x3) {I am x3};
ode [test, join, left=of t1] (x5) {I am x5};
ode [term, join, above=8em of x5, fill=lcfree!60] (x6) {有朋自遠方來 x6};
ode [nmark,blue, above=10em of x6] (x7) {咱是圓的};
draw [*-&>, cyan] (x6) -- (x7);
% We position the next block explicitly as the first block in the
% second column. The chain "comes along with us". The distance
% between columns has already been defined, so we don"t need to
% specify it.
ode [proc, fill=lcfree!25, right=of p1] (p4) {Reset congestion};
ode [proc, join=by free] {Set extsc{mq} wait flag};
ode [proc, join=by free] (p5) {Dispatch message};
ode [test, join=by free] (t5) {Got msg?};
ode [test] (t6) {Capacity?};
% Some more nodes specifically positioned (we could have avoided this,
% but try it and you"ll see the result is ugly).
ode [test] (t7) [right=of t2] {$k mathbin{{-}{=}} 1$};
ode [proc, fill=lccong!25, right=of t3] (p8) {Set congestion};
ode [proc, join=by cong, right=of t4] (p9) {Close queue p9};
ode [term, join] (p10) {Exit trigger message thread};
% -------------------------------------------------
% Now we place the coordinate nodes for the connectors with angles, or
% with annotations. We also mark them for debugging.
ode [coord, right=of t1] (c1) {}; cmark{1}
ode [coord, right=of t3] (c3) {}; cmark{3}
ode [coord, right=of t6] (c6) {}; cmark{6}
ode [coord, right=of t7] (c7) {}; cmark{7}
ode [coord, left=of t4] (c4) {}; cmark{4}
ode [coord, right=of t4] (c4r) {}; cmark[r]{4}
ode [coord, left=of t7] (c5) {}; cmark{5}
ode [coord, left=of x3] (c8) {}; cmark{8}
ode [coord, right=of x3] (c8r) {}; cmark[r]{8}
% -------------------------------------------------
% A couple of boxes have annotations
ode [above=0mm of p4, it] {(Queue was empty)};
ode [above=0mm of p8, it] {(Queue was not empty)};
ode [right=0mm of x3, it] {(I am above x3)};
% -------------------------------------------------
% All the other connections come out of tests and need annotating
% First, the straight north-south connections. In each case, we first
% draw a path with a (consistently positioned) annotation node, then
% we draw the arrow itself.
path (t1.south) to node [near start, xshift=1em] {$y$} (p2);
draw [*-&>,lcnorm] (t1.south) -- (p2);
% sanqiang drawing
path (x3.west) to node [near start, xshift=1em, yshift=4em] {$zhangsanqiang$} (x5);
draw [*-&>,lccong] (x3.west) -- (c8) |- (x5.west);
draw [o-&>,lcfree] (x5.east) -| (c8r);
%draw [o-&>,lcfree] (x5.east) -- (c8r);
% sanqiang
path (t2.south) to node [near start, xshift=1em] {$y$} (t3);
draw [*-&>,lcnorm] (t2.south) -- (t3);
path (t3.south) to node [near start, xshift=1em] {$y$} (t4);
draw [*-&>,lcnorm] (t3.south) -- (t4);
path (t5.south) to node [near start, xshift=1em] {$y$} (t6);
draw [*-&>,lcfree] (t5.south) -- (t6);
path (t6.south) to node [near start, xshift=1em] {$y$} (t7);
draw [*-&>,lcfree] (t6.south) -- (t7);
% -------------------------------------------------
% Now the straight east-west connections. To provide consistent
% positioning of the test exit annotations, we have positioned
% coordinates for the vertical part of the connectors. The annotation
% text is positioned on a path to the coordinate, and then the whole
% connector is drawn to its destination box.
path (t3.east) to node [near start, yshift=1em] {$n$} (c3);
draw [o-&>,lcnorm] (t3.east) -- (p8);
path (t4.east) to node [yshift=-1em] {$k leq 0$} (c4r);
draw [o-&>,lcnorm] (t4.east) -- (p9);
% -------------------------------------------------
% Finally, the twisty connectors. Again, we place the annotation
% first, then draw the connector
path (t1.east) to node [near start, yshift=1em] {$next$} (c1);
draw [o-&>,lcfree] (t1.east) -- (c1) |- (p4);
path (t2.east) -| node [very near start, yshift=1em] {$n$} (c1);
draw [o-&>,lcfree] (t2.east) -| (c1);
path (t4.west) to node [yshift=-1em] {$k&>0$} (c4);
draw [*-&>,lcnorm] (t4.west) -- (c4) |- (p3);
path (t5.east) -| node [very near start, yshift=1em] {$n$} (c6);
draw [o-&>,lcfree] (t5.east) -| (c6);
path (t6.east) to node [near start, yshift=1em] {$n$} (c6);
draw [o-&>,lcfree] (t6.east) -| (c7);
path (t7.east) to node [yshift=-1em] {$k leq 0$} (c7);
draw [o-&>,lcfree] (t7.east) -- (c7) |- (p9);
path (t7.west) to node [yshift=-1em] {$k&>0$} (c5);
draw [*-&>,lcfree] (t7.west) -- (c5) |- (p5);
% -------------------------------------------------
% A last flourish which breaks all the rules
draw [-&>,MediumPurple4, dotted, thick, shorten &>=1mm]
(p9.south) -- ++(5mm,-3mm) -- ++(27mm,0)
|- node [black, near end, yshift=0.75em, it]
{(When message + resources available)} (p0);
% Another freedom line
draw [-&>,red, thick, shorten &>=1mm]
(p10.west) -- ++(-6mm,+6mm) -- ++(-85mm,0)
|- node [blue, near end, yshift=0.75em, xshift=2em, it]
{(Matrix of ooxx)} (x6);
draw [*-&>,blue, thick, shorten &>= 1mm]
(x2.west) -- ++(-20mm, 0) -- ++(0, 10cm)
|- node [blue, near end, yshift=0.75em, xshift=-2em, it]
{(This is aonther way)} (x6);
% -------------------------------------------------
end{tikzpicture}
% =================================================
end{document}
出來是這樣的
在線自己修改 https://www.overleaf.com/6919604mwxmpscvzmgs#/23653229/
例子大集合 TikZ and PGF examples優點:靈活,隨心所欲,高質量,可以畫很複雜的圖缺點:起點高,入門難用什麼軟體畫流程圖?
如果只是畫很規範的流程而不是整理思路的話,還是用visio最好。他具有各種指向、連接以及豐富的模板、圖標等,這都有利於流程圖的順暢製作。當然,還有各種參考線、標尺的應用,讓你繪製更標準的圖,這些都是思維導圖軟體所沒有的。.visio為什麼那麼小?visio也是office系列,有office系列的一般特徵。這時候就可以拿word來看,word可以通過「頁面設置」,修改頁面屬性,橫版還是豎版,A3還是A4,都是可以設置的。visio也一樣,也可以設置自定義尺寸、比例,我就曾經直接把一個文件設置成80cm*120cm的,做完後直接發廠列印,出來效果沒有一點問題。說白了,就類似矢量圖一樣。所以,可以放心使用。ps:沒查資料,專業術語方面可能有問題,所言也純個人經驗。Gliffy | Online Diagram and Flowchart Software我之前也是在知乎被高票答案推銷了ProcessOn,直到見到同學用了 Gliffy 才發現之前用的不夠好用。而且 Gliffy 支持 GoogleDrive 的存儲。而且 Gliffy 支持不登陸就畫圖。而且一個邊長上有三個點可以連接。而且不止流程圖,連維恩圖(集合概念)都可以畫出來。而且有官方的微軟 Office 插件。
除了以上的答主介紹的軟體之外,答主自己還有一款流程圖製作軟體可以推薦一下。這款迅捷流程圖製作軟體中包含大量的流程圖素材,我們可以利用它來快速製作出業務流程圖、組織結構圖、數據流程圖、程序流程圖等多種流程圖。
看了上面一圈,發現沒人介紹這款,可能比較冷門吧,答主就以一個簡單的流程圖製作來簡單介紹一下如何進行操作吧。
首先在電腦上安裝並運行該軟體,然後在界面左上角上點擊「文件——新建」,新建一個流程圖編輯頁面。
這時候我們就可以在頁面上製作流程圖了,這裡我們在右側「工具箱」中,根據我們的需要選擇流程圖的製作素材。
將選擇的素材拉到編輯頁面上進行繪製,這裡我們可通過拖動圖形邊角來改變圖形大小或旋轉圖形。
如果我們需要在流程圖的圖形中添加文字的話,我們可以選中圖形中間位置,然後輸入需要的文字內容。
如果我們想要對圖形進行進一步的個性化編輯時,我們可以在選中圖形後,點擊右下角的「屬性」,然後對圖形或文字屬性進行編輯。
添加所需素材並根我們的思路成功繪製好流程圖後,點擊軟體菜單欄上的保存按鈕,即可對流程圖進行保存。
希望對題主有所幫助。
edrawmax更新一下:畫流程圖最重要的是反映你的思路,能夠讓別人一目了然的知道整個程序的過程。工具是用來幫助你實現表達你的思路的,只要你思路清晰,邏輯清楚,多畫幾張又有何妨?即使使用office內置的一些功能你也可以繪製出優秀的流程!
除了OmniGraffle,其他都可以忽略了。流程圖,草圖,低保真原型,OmniGraffle絕對是該領域的神器。
謝邀。
我用億圖,花了48塊錢買的正版註冊碼。(我雖然不是大牛,可也沒那麼笨在這種問題下暴露自己用盜版軟體哦~)簡單介紹一下這個軟體:1、國產2、界面設計逼格低3、專註畫圖,幾乎可以完全替代 visio + mindmanager4、不註冊也能用(只不過導出的圖會有水印)流程圖軟體匯總:
1.億圖(Edrae max7.9):強大的流程圖繪圖功能,附帶思維導圖插件。網路很多破解版,可以輸出為圖片格式,PDF,word的格式!2.百度在線思維導圖:需要註冊百度賬號。
3.現在國內和國外很多在線思維導圖製作網站,不用安裝最省事。搜索關鍵字:流程圖+在線
希望能夠通過互聯網關鍵詞搜索找到更多有用資源。Edraw
就這一個軟體,我用它完成了我大學所有要畫的流程圖,其他就再也沒有用過了。
逛評論吸取經驗我用 PowerPoint。
PowerPoint的優點:1、複雜的圖一般都可以分成幾塊。每塊流程一個頁面,存在一個文檔里,很方便。2、可以直接列印,可以直接做演示,巨方便。3、表格、文字、圖片、流程等等,都可以放在一個文檔里,很方便。補充:最近開始用自動生成流程圖的工具 GraphViz,超方便: Graphviz | Graphviz流程圖軟體我只支持國產的億圖因為:1,小而強悍2,界面已經很流暢漂亮,關鍵是他的圖庫很多3,Windows和Mac平台上都可以用
個人感覺edraw max億圖圖示好用一些,visio的模塊較少,達不到我想要的效果。你可以兩個軟體都試試,我當初就是都用用看。我用mac的時候edraw max也可以用.
Edraw
yed 大家可能沒多少人聽說過, java寫的,跨操作系統。
用了你就知道,從易用性、可實現的複雜性、效果的美觀性等方面秒殺visio、ppt、mind之類的。就為推薦個軟體,為了大家在工作中更方便點,我又是畫紅又是上傳的,容易么? :)
這個圖是沒使用任何3D效果的圖,我覺得用3D不值得,還得多使用些時間去修飾效果參數,沒啥必要。這個是邏輯圖,各種流程圖的框框yed也都有,它是混用的,你願意用哪個風格的框圖就用哪個,工具是散花的,沒什麼約束。推薦閱讀:
TAG:MicrosoftVisio | 流程圖 | Graphviz |