課程章節
培訓 · 第 3 單元:行為與架構 · 第 3.1 章,共 6 章
3.1 功能與 FFBD 3:52
為功能指定最上層功能,然後以文字撰寫其流程並取得 FFBD。
展示 Holarch 1.27。
您將學到
- 在功能分析頁面上選擇最上層功能
- 以 decomposed by 關係將功能分解為子功能
- 以箭頭、AND 與 LOOP 將功能流程寫成文字
- 閱讀 Holarch 根據流程繪製的 FFBD,並開啟子功能自己的 FFBD
在功能分析頁面上將 Bike-Share Dock 的功能組織在最上層功能之下,新增一項功能,以箭頭、AND 與 LOOP 將功能流程寫成一行文字,並讓 Holarch 據此繪製功能流程方塊圖(FFBD)。
練習
在 Holarch 中於 CubeSat EO-1 示範專案上親自操作。
- 開啟您的 EO-1 示範專案,或建立它:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程)。
- 在資料庫中選取 F9 Transmit Payload Data。在其追溯區段中,按一下 decomposed by 旁的 +(若未列出,請勾選顯示所有關係),選擇新增 Action…,並建立
Enable Transmitter、Send Data File、Confirm Receipt、Disable Transmitter與Report Pass Summary。 - 開啟行為 → 功能分析,按一下最上層功能旁的選擇…,並挑選 F9 Transmit Payload Data。功能分頁會列出其五個子功能。
- 在流程與 FFBD 上,按一下以文字編輯…,輸入
"Enable Transmitter" -> LOOP[return="next file"]("Send Data File" -> "Confirm Receipt") -> AND("Disable Transmitter" | "Report Pass Summary"),然後按一下套用。 - 按一下開啟 FFBD,找到帶有返回箭頭的迴圈與 AND 閘。接著再次選擇 F0 Perform EO-1 Mission 作為最上層功能,開啟其 FFBD,並按兩下 F9 以開啟 F9 自己的 FFBD。
- 若要進行有檢查的逐步練習,請執行教學課程 4 Functional Analysis(說明 → 教學課程)。
當 F9 的 FFBD 顯示 Enable Transmitter、一個由 Send Data File 與 Confirm Receipt 構成且返回箭頭標示為 next file 的迴圈,以及一個有兩個分支的 AND 時,即完成。
自我檢查
- 為什麼功能分析頁面需要最上層功能?
- 流程中的 AND 與 OR 有什麼不同?
- 您在文字流程中遺漏的功能會怎樣?
- 您在「流程與 FFBD」分頁上變更了流程。FFBD 會怎樣?
顯示答案
為什麼功能分析頁面需要最上層功能?
此頁面以一個 Action 為基礎運作:其 decomposed by 子項目就是它所列出、排定流程並繪製的功能。選擇另一個最上層功能(例如 F9),會顯示該功能自己的分解。
流程中的 AND 與 OR 有什麼不同?
AND 會平行執行其所有分支,並在每個分支都完成後才繼續流程。OR 則恰好選擇其中一個分支。
您在文字流程中遺漏的功能會怎樣?
Holarch 會將其列為文字中遺漏的功能,並加在流程最後一個元素之後,因此不會遺失任何功能。
您在「流程與 FFBD」分頁上變更了流程。FFBD 會怎樣?
它會重新繪製。FFBD、功能樹與功能表格都讀取同一個模型,因此沒有任何內容需要手動更新。
延伸閱讀
文字稿
顯示文字稿 (旁白與畫面內容)
Introduction
Welcome to Behavior and Architecture. This track models what the Bike-Share Dock does, what it is made of, how its parts connect, and whether the design adds up.
This first chapter is about functions, and the order they run in.
Functions and their flow
A function is something the system must do, named with a verb: rent a bike, take a payment. A functional flow block diagram, the F F B D, shows the order the functions run in, which ones run at the same time, and which ones repeat.
On screen: Card: functions and the FFBD.
A top-level function
Open Behavior, then Functional Analysis. The page works from one top-level function, and the dock has none yet. The four functions from Getting Started stand on their own.
On screen: Behavior → Functional Analysis: no top-level function.
Click Choose, then Create New. The top-level function is the whole job of the system: Operate the Bike-Share Dock, numbered F zero.
On screen: Choose… → Create New… → F.0 Operate the Bike-Share Dock.
Now put the four functions under it. Open the Database, select Operate the Bike-Share Dock, and in its Trace section, link Rent a Bike, Return a Bike, Charge Bikes and Take Payment under decomposed by.
On screen: Database → F.0 → decomposed by → F.1–F.4.
One function is missing: the dock reports its status, the free bays and the charge levels, to the back office. Create a new Action, F five, Report Dock Status.
On screen: New Entity: Action F.5 Report Dock Status.
Place it in the hierarchy from the other side: show all relations in its Trace section, and under decomposes, link it to Operate the Bike-Share Dock.
On screen: F.5 → decomposes → F.0.
Back in Functional Analysis, the Functions tab lists all five under the top-level function.
On screen: Functional Analysis → Functions.
The flow as text
Open Flow and FFBD. Until someone writes the flow, it simply lists the functions in number order, which says nothing about how they work together.
On screen: Flow & FFBD tab.
Choose Edit as Text. A flow is written like a sentence: function numbers joined by arrows, in the order they run. A rider pays, takes the bike, and later returns it: F four, arrow, F one, arrow, F two.
On screen: Edit as Text → F.4 -> F.1 -> F.2.
After a return, two things happen at the same time: the bike charges, and the dock reports its status. AND opens parallel branches, separated by a bar. Both start together, and the flow goes on when both are done.
On screen: -> AND(F.3 | F.5).
The whole cycle repeats for the next rider. LOOP repeats what is inside its brackets, and return names the arrow that goes back. Wrap the flow in a loop.
On screen: LOOP[return="next rider"]( … ).
The FFBD
The preview below draws the diagram as you type. Apply it.
On screen: Preview → Apply.
Holarch draws the F F B D from that one line: a numbered box for each function, a circle where the AND branches open and close, and the loop with the return arrow labeled next rider.
On screen: The FFBD.
The diagram, the hierarchy and the functions table all read the same model. Change the flow, and the diagram follows.
On screen: The FFBD.
Recap
Let's recap. You created a top-level function, placed the dock's functions under it, wrote their flow as text with arrows, AND and LOOP, and got the F F B D drawn from it.
Next, you take one function apart, step by step, on an action diagram.