Holarch

Training · Track 3. Behavior and Architecture

Track 3. Behavior and Architecture: exercise sheet

For engineers. One practice task and a few questions per chapter, to work through after each video. Print this page from your browser, or work on screen. The answer key starts on a new page at the end.

Before you start

Take first
Track 2. Requirements and Verification.
Plan
Free
Project
The Bike-Share Dock: each chapter has its starting file.

3.1 Functions and the FFBD

Watch chapter 3.1 (3:52)

Practice

On the CubeSat EO-1 demo project:

  1. Open your EO-1 demo project, or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering).
  2. In the Database, select F9 Transmit Payload Data. In its Trace section, click + beside decomposed by (tick Show all relations if it is not listed), choose New Action… and create Enable Transmitter, Send Data File, Confirm Receipt, Disable Transmitter and Report Pass Summary.
  3. Open Behavior → Functional Analysis, click Choose… beside Top-level function and pick F9 Transmit Payload Data. The Functions tab lists its five sub-functions.
  4. On Flow & FFBD, click Edit as Text…, type "Enable Transmitter" -> LOOP[return="next file"]("Send Data File" -> "Confirm Receipt") -> AND("Disable Transmitter" | "Report Pass Summary") and click Apply.
  5. Click Open FFBD and find the loop with its return arrow and the AND gate. Then choose F0 Perform EO-1 Mission as the top-level function again, open its FFBD and double-click F9 to open F9's own FFBD.
  6. For a checked walk-through, run tutorial 4 Functional Analysis (Help → Tutorials).

You're done when F9's FFBD shows Enable Transmitter, a loop of Send Data File and Confirm Receipt with the return arrow labeled next file, and an AND with two branches.

Questions

  1. Why does the Functional Analysis page need a top-level function?
  2. What is the difference between AND and OR in a flow?
  3. What happens to a function you leave out of the text flow?
  4. You change the flow on the Flow & FFBD tab. What happens to the FFBD?

3.2 Action Diagrams

Watch chapter 3.2 (2:55)

Practice

On the CubeSat EO-1 demo project:

  1. Open your EO-1 demo project, or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering).
  2. In the Database, select F10 Enter Safe Mode and choose Open in ▾ → Action Diagram.
  3. Drag Action from the Add panel onto the line and name it Detect Undervoltage. Then drag a Parallel onto the line after it, with Shed Payload Loads on one branch and Point Arrays to Sun on the other.
  4. Drag an Or onto the line after the Parallel and name it Battery recovered?. In the inspector, set the branch probabilities to 80 and 20, and put Resume Nominal Mode on the first branch and Keep Charging on the second.
  5. Drag Input/Output onto Detect Undervoltage and name it Undervoltage Flag. Drag the handle below the I/O onto Shed Payload Loads and choose Input (trigger).

You're done when F10's diagram shows the five steps, the parallel branches, the OR with Total 100%, and Undervoltage Flag passing from Detect Undervoltage to Shed Payload Loads.

Questions

  1. What does dropping an Action on the line add to the model?
  2. What is the difference between a triggering and an optional input?
  3. Why must an OR's branch probabilities add up to 100%?

3.3 Allocation

Watch chapter 3.3 (2:33)

Practice

On the CubeSat EO-1 demo project:

  1. Open your EO-1 demo project, or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering).
  2. Open Verification → Traceability Matrix. Click the Rows chip, set Rows from to Hierarchy under a root entity and choose OPS Run Nominal Imaging Pass as the root, then click Done.
  3. Click the Columns chip, set Columns from to All entities of a class with the class Asset, and set Relationship to performed by.
  4. Tick Gaps only. OPS.9 Hold Data Onboard remains, with the root OPS, which the system performs as a whole.
  5. Click the cell where OPS.9 Hold Data Onboard meets 1.4 C&DH, the part that holds payload data in storage. Then select OPS.9 in the Database and read performed by in its Trace section.
  6. For a checked walk-through, run tutorial 6 Physical Architecture and Allocation (Help → Tutorials).

You're done when Gaps only no longer lists OPS.9 and its Trace section shows performed by 1.4 C&DH.

Questions

  1. Why set Relationship to performed by instead of All allowed?
  2. Where is an allocation stored?
  3. Gaps only shows a row. Is that always an error?

3.4 Interfaces

Watch chapter 3.4 (2:31)

Practice

On the CubeSat EO-1 demo project:

  1. Open your EO-1 demo project, or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering).
  2. Open Interfaces → Interface Register and click the Proposed card. Click the row IF-14.1 Customer Portal.
  3. In the inspector, set Interface Status to Agreed, Owner to Ground Segment Lead and Medium to HTTPS. Keep its Capacity of 1000 Mbps.
  4. Open Interfaces → Items & I/O, select Image Product (the item the portal transfers), and set Data Rate to 50 and Data Rate Units to Mbps. Back in the register, point at the Capacity column of IF-14.1 and read the check. Click ICD on its row to export the interface control document.
  5. Select 1 EO-1 Spacecraft in the Database and choose Open in ▾ → I2 Diagram. Find the cell that holds IF-01 Payload Power Line.
  6. For a checked walk-through, run tutorial 7 Interfaces (Help → Tutorials).

You're done when IF-14.1 is Agreed with Owner and Medium set, its capacity check reads OK, and you have the ICD Word file.

Questions

  1. How does Holarch decide whether a conduit can carry its items?
  2. Why does the data rate belong on the item and not on the conduit?
  3. What does an interface status such as Proposed or Agreed tell a reader?
  4. What does a cell of the I² Diagram hold?

3.5 Simulation

Watch chapter 3.5 (2:39)

Practice

On the CubeSat EO-1 demo project:

  1. Open your EO-1 demo project, or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering).
  2. In the Database, select OPS.11 Receive Downlink (9 minutes) and set its Duration to =triang.dist(8, 15, 9) Minutes, for passes that sometimes run long.
  3. Open Behavior → Simulator, choose OPS Run Nominal Imaging Pass as the Root Action, keep Discrete Event and press ⏩ Run to End. Read Total Time and the timeline.
  4. Switch to Monte Carlo and press ▶ Run Monte Carlo. On the Distribution tab, read the mean and the spread of the total time.
  5. Click Check Against Requirement…, keep Total time, set ≤ at most 100 Minutes, the requirement 6.5 Planning Cycle Time and Required probability (%) 95. Read P5 / P50 / P95, P(meet) and the Result.
  6. For a checked walk-through, run tutorial 8 Simulate the Functional Flow (Help → Tutorials).

You're done when the check shows P(meet) and a Pass or Fail result for 6.5 Planning Cycle Time at 95%.

Questions

  1. Why give a step a distribution instead of a fixed duration?
  2. What does one Discrete Event run tell you that Monte Carlo does not?
  3. Why check against the 95th percentile and not the mean?
  4. What does Record Result change in the model?

3.6 Budgets and TPMs

Watch chapter 3.6 (3:31)

Practice

On the CubeSat EO-1 demo project:

  1. Open your EO-1 demo project, or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering).
  2. Open Architecture → Budgets & TPMs. On the Budget tab, keep 1 EO-1 Spacecraft as the root and change Quantity to Power Draw.
  3. Find 1.1 Payload Camera (6.2 W, Estimated) and change its Basis to Measured. Read how its contingency and the spacecraft's margin change.
  4. In the Database, create a Measure with + New Item: ADCS Mass, number TPM-4. Set Units kg, Threshold Value 1.35 kg, Objective Value 1.2 kg and Improvement Direction Negative, add the label TPM, and link it to 1.2 ADCS with specified by.
  5. On the TPMs tab, select TPM-4 ADCS Mass. Type the ADCS mass from the Budget tab (Quantity Mass, CBE + contingency) as Current Estimate, click + Milestone to add CDR with a planned value of 1.3 kg, then click Take Snapshot.

You're done when TPM-4 ADCS Mass is listed with a status, a CDR milestone in its planned profile and a Snapshot point in its estimate history.

Questions

  1. Why does contingency depend on the basis of a value?
  2. How is margin worked out, and when does a line warn?
  3. What does a TPM add to a budget?
  4. What makes a Measure a TPM in Holarch?

Answer key

3.1 Functions and the FFBD

  1. The page works from one Action: its decomposed by children are the functions it lists, flows and draws. Choosing another top-level function, such as F9, shows that function's own breakdown.
  2. AND runs all its branches in parallel, and the flow continues when every branch has finished. OR takes exactly one of its branches.
  3. Holarch lists it as missing from the text and adds it after the last element of the flow, so no function is lost.
  4. It redraws. The FFBD, the function tree and the functions table all read the same model, so there is nothing to update by hand.

3.2 Action Diagrams

  1. A new Action, decomposed under the function the diagram belongs to, at that place in its flow. It appears in the Database and on every view that shows it.
  2. A step with a triggering input does not start until that item arrives. An optional input is received but does not hold the step back.
  3. The Simulator picks a branch by its probability. If the numbers don't total 100%, the inspector warns you. If the probabilities are unknown, choose None: the Simulator then asks during the run, and Monte Carlo uses equal probabilities.

3.3 Allocation

  1. With one type chosen, a click on an empty cell creates exactly that relationship. With all allowed types, Holarch has to ask which one you mean when several apply.
  2. On the items, as performed by on the Action and performs on the Asset. The matrix is only a view of those links, so any other view, such as the item's Trace section, shows the same allocation.
  3. No. A top-level operation or function may be done by the system as a whole, so it needs no single performer. Each remaining step usually needs one.

3.4 Interfaces

  1. It adds the Data Rate (or Size) of every item the conduit transfers, converts each to the conduit's units and compares the total with Capacity. The result is OK, Over capacity, Unit mismatch or No capacity.
  2. The rate describes what is carried, and the same item can travel over several conduits. Each conduit's check sums the items it carries against its own capacity.
  3. How far the teams on both ends have got: Draft and Proposed are written down but not yet accepted by both sides, Agreed means both accept it, and Baselined is the final stage. The register's cards count each status.
  4. The conduits between the two child assets of its row and column: the row is the origin end and the column the other end.

3.5 Simulation

  1. Real durations vary. A distribution is sampled on every execution, so Monte Carlo shows the spread of the total time, not one number.
  2. It plays a single run on a timeline, so you can see the order of the steps, the parallel branches and which branch a decision took. Monte Carlo repeats the run many times for statistics.
  3. Half the runs take longer than the mean. A limit that must hold in 95 runs out of 100 is judged by the time those 95 stay under, which P(meet) and P95 report.
  4. It sets the Measure's Projected Value (or Value) to the mean and sets a Test Case that verifies the requirement to Passed or Failed. You review the changes first, and they apply as one undo step.

3.6 Budgets and TPMs

  1. An estimate is less certain than a calculation, and a calculation less than a measurement. Contingency by basis (15, 10 and 3% in the demo) carries more allowance where the number is less certain.
  2. Margin is the allocation minus the current best estimate plus contingency. A line shows ▲ Low when the margin is below the required margin and ✕ Over when it exceeds its allocation.
  3. A budget shows today's roll-up. A TPM tracks one critical number over the life of the project against a planned profile, a threshold and an objective, so a trend toward a breach shows before reviews.
  4. The TPM label. Measures with it are listed on the TPMs tab, together with requirements that have a Threshold Value.

Published by Holarch