Track 2. Requirements and Verification: 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 1. Getting Started, or tutorial 1 Getting Around in the app.
- Plan
- Free
- Project
- The Bike-Share Dock: each chapter has its starting file.
2.1 Writing Requirements and the Quality Check
Watch chapter 2.1 (3:37)
Practice
On the CubeSat EO-1 demo project:
- Open your EO-1 demo project (or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering)).
- Open Needs & Requirements → Documents → EO-1 System Requirements Specification. Select section 5 Communications, click + Child, name the requirement
Command Link Margin, and write a shall statement with a value (for example, at least 6 dB margin at 5 degrees elevation). - In the inspector, set Priority to High, Verification Method to Analysis and a Rationale, then click + Label and choose Performance Requirement.
- Open Needs & Requirements → Quality, choose Document: EO-1 System Requirements Specification in the scope bar and click Check Quality. Read the Suggestions for 2.5 Safe Mode Recovery.
- Rewrite 2.5 as one measurable statement (what triggers recovery, how fast, and to which mode), and click Check Quality again.
- Review your rewrite, then click the ✘ under Correct and Feasible on its row to mark them Yes.
You're done when 2.5 Safe Mode Recovery scores higher than before, its suggestions no longer name vague words, and Correct and Feasible show ✔.
Questions
- Why does a requirement joined by and score lower even when both halves are good?
- Why can the automatic check never mark Correct and Feasible?
- What makes a word such as quickly a problem in a requirement?
2.2 Tracing Needs to Requirements
Watch chapter 2.2 (2:07)
Practice
On the CubeSat EO-1 demo project:
- Open your EO-1 demo project (or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering)).
- In the Database, select 1.6.2 Off-Nadir Imaging. In Trace, on traced from (tick Show all relations if it is not listed), click + → Link existing…, tick N2 Twice-Weekly Revisit and click Link Selected.
- Open Verification → Traceability Matrix. Set Rows from the query
class:Requirement, Columns from the querynumber:N*, and choose the relationship traced from. - Click the empty cell of 1.5 Daily Collection Volume under N2 Twice-Weekly Revisit: the daily volume is what makes the revisit possible.
- Tick Gaps only. For 1.7 Mission Lifetime, add the missing need: create a Statement
Two Growing Seasonswith the next free N number (such asN4), then link it to 1.7 in the matrix. - For a checked walk-through, run tutorial 3 Trace Requirements (Help → Tutorials).
You're done when 1.5, 1.6.2 and 1.7 no longer appear with Gaps only ticked.
Questions
- What three questions does tracing needs to requirements answer?
- Gaps only shows a requirement with no source. Is the right fix always to link it to the nearest need?
- When is the Traceability Matrix better than the inspector for linking?
2.3 Open Items and Approvals
Watch chapter 2.3 (2:31)
Practice
On the CubeSat EO-1 demo project:
- Open your EO-1 demo project (or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering)).
- Select 1.5 Daily Collection Volume. In the inspector's Workflow group, set TBD/TBR to TBR, TBD Owner to
Payload Leadand a due date two weeks out. - Open Needs & Requirements → TBD/TBR. Find the overdue row (3.5 Battery Thermal Control), rewrite its statement with a final temperature range, and click Close on its row.
- Select 6.3 Telemetry Archive (still Draft) and set its Status to In Review in the inspector's Workflow group.
- Open Needs & Requirements → Approvals. Select 6.3 Telemetry Archive and click Approve in the review strip. If a dialog lists items under Needs re-review, look at them and click Approve to confirm.
- Select 5.3 Downlink Link Margin, click Reject…, give the reason that the link budget has not been rerun, and confirm.
You're done when the register lists 1.5 and no longer lists 3.5, and 6.3 shows Approved and 5.3 Rejected, each with your name and the time.
Questions
- What is the difference between TBD and TBR?
- Why write a best estimate into the statement instead of leaving the value blank?
- You edit the text of an Approved requirement. What happens to its status?
2.4 Baselines and Links to Review
Watch chapter 2.4 (2:40)
Practice
On the CubeSat EO-1 demo project:
- Open your EO-1 demo project (or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering)).
- Open EO-1 System Requirements Specification, click Version ▾ in the title block and choose Save Baseline…. Name it
PDR Baseline, fill in one approver row with your name and role, and click Create. - Change 3.3 Depth of Discharge from 30% to 25% in its description, and read the toast: the requirement is back In Review and its links need review.
- Open Needs & Requirements → Links to Review. On a row for 3.3, click Diff, then Mark Reviewed…, write what you checked and click Mark Reviewed.
- In the document, choose Version ▾ → Compare Versions… with From PDR Baseline and To Current version, and click Changes (Excel).
- Open Control & Reviews → Baselines & Versions and find PDR Baseline next to SRR Baseline. To freeze the whole model rather than one document, you would use + Save Baseline… in this page header.
You're done when the change report from PDR Baseline lists the 3.3 edit and the link you reviewed no longer appears on Links to Review.
Questions
- Why does changing a requirement mark the links that depend on it, not the requirement alone?
- What is the difference between a document baseline and a project baseline?
- When you mark a link reviewed, why write a note?
2.5 Verification and the Test Center
Watch chapter 2.5 (2:55)
Practice
On the CubeSat EO-1 demo project:
- Open your EO-1 demo project (or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering)).
- Open Verification → Test Center and scroll to Verification Coverage. On 4.4 Downlink Encryption, make sure I is on, choose Subsystem under Level…, and add success criteria with + Criteria.
- Click + New ▾ → Test Suite… in the page header, number it
TS-4, name itMission Analysesand click Create. On its card, click + Test Case, name itDaily Collection Volume Analysis, and click + in Verifies to pick 1.5 Daily Collection Volume (its method is Analysis and it has no test yet). - Type the Expected Result, then click + Steps, add two steps with an action and an expected result each, and click Apply.
- On the TS-4 card, choose ⋯ → Run Cycle…, record each step, describe the Actual Result and click ✔ Pass.
- For a checked walk-through, run tutorial 9 Verify the Requirements (Help → Tutorials).
You're done when Daily Collection Volume Analysis shows Passed with your name and date, and 1.5 leaves the Not verified list.
Questions
- Which method fits a requirement for a 730-day mission lifetime, and why?
- Why set success criteria before writing the test case?
- What does a passed test case change on the requirement it verifies?
2.6 RVTM and VCRM
Watch chapter 2.6 (2:29)
Practice
On the CubeSat EO-1 demo project:
- Open your EO-1 demo project (or create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering)).
- Open Verification → RVTM. Click the Failed card and note which requirements the failing tests TC-04 and TC-09 verify. Click the chip to clear the filter.
- Switch the table to VCRM and find the requirements with no X in any method column.
- Click Export ▾ → Excel (.xlsx) and open the file.
- Open EO-1 System Requirements Specification, select section 5 Communications and choose Write ▾ → Insert ▸ → Matrix…. Choose VCRM by Verification Level, keep the scope on this document, and click Insert.
- Choose Deliver ▾ → Traceability Matrix…, pick the RVTM, choose Matrix (Word) under Export as, set Model to SRR Baseline, and click Export.
You're done when the specification shows a live VCRM by level and you have a Word RVTM whose title names SRR Baseline.
Questions
- Which matrix answers how each requirement will be verified, and which answers whether it has been?
- Why insert the matrix as live content rather than paste a table into the specification?
- Why export a matrix from a baseline for a signed deliverable?
Answer key
2.1 Writing Requirements and the Quality Check
- It holds two requirements in one. They cannot be verified, traced or changed separately, so the check flags it as not singular.
- Whether a requirement states the right need and can be built takes engineering judgment. A person reviews it and marks those two criteria.
- It cannot be measured, so no test can show the requirement is met. Replace it with a value and a unit.
2.2 Tracing Needs to Requirements
- Why a requirement exists, whether every need is covered by a requirement, and which requirements change when a need changes.
- No. Either a need is missing and should be added, or the requirement is not needed and should be removed. A link made only to close the gap hides the question.
- When you make many links between two sets of items: you see the whole grid, create each link with one click and see the gaps at once.
2.3 Open Items and Approvals
- TBD means the value is still to be determined. TBR means there is a value, but it still has to be reviewed. Both need an owner and a due date.
- Design work can continue against the estimate, and the register makes sure someone settles it by the due date.
- It goes back to In Review, with the note that the text changed after approval, so the change is reviewed before the team builds to it.
2.4 Baselines and Links to Review
- The items at the other end, such as the function that satisfies it or the test that verifies it, were checked against the old text. Each link must be checked again to see whether it still holds.
- A document baseline freezes one document and its approvals (Version ▾ → Save Baseline…). A project baseline freezes every item and relationship (Baselines & Versions → + Save Baseline…).
- The note records what was checked and why the link still holds. It is added to the linked item's comments, so a reviewer can follow the decision later.
2.5 Verification and the Test Center
- Analysis: the lifetime cannot be measured before launch, so it is shown by calculation, such as a reliability estimate.
- They state the measurable outcome that shows the requirement is met, so the test is designed to that outcome rather than to whatever the test happens to measure.
- The requirement's verification status becomes verified, and it leaves the Not verified list in the coverage card and the RVTM.
2.6 RVTM and VCRM
- The VCRM shows the planned methods per requirement. The RVTM shows the methods, the tests that verify each requirement and their results.
- A live matrix is built from the model. When a method changes or a test passes, the matrix and every export of the document change with it.
- A signed document must show the model as it was agreed, not as it is today. A matrix from a baseline uses that baseline's items and relationships.
Published by Holarch