Satisfy Requirement Matrix
Is every requirement designed for?
Blocks against requirements, with an arrow wherever a block satisfies a requirement.
An empty requirement column means nothing satisfies it. In the example, EV-5 Session Receipt.
Free tutorial · Requirements traceability · Cameo / CATIA Magic
A requirements traceability matrix shows which design elements satisfy each requirement and which test cases verify it. In Cameo, an empty column is a gap you can see. Double-click the empty cell to close it.
Worked example: the EV charging station from our allocation video
| EV-1Driver Auth. | EV-2Charge Power | EV-3Connector Interlock | EV-4Session Pricing | EV-5Session Receipt | |
|---|---|---|---|---|---|
| Card Reader«block» | ↗ | ||||
| Power Cabinet«block» | ↗ | ||||
| Charge Controller«block» | ↗ | ||||
| Cloud Backend«block» | ↗ | ||||
| Display«block» | no satisfy | ||||
| Authenticate Card Test«testCase» | ↗ | ||||
| Rated Power Test«testCase» | ↗ | ||||
| Session Price Test«testCase» | ↗ | ↗ | |||
| Connector Interlock Test«testCase» | no verify |
Three ways to see traceability
Cameo ships matrix templates for satisfy and verify. Each one finds one kind of gap. A Dependency Matrix with both criteria puts the whole picture on one screen.
Satisfy Requirement Matrix
Blocks against requirements, with an arrow wherever a block satisfies a requirement.
An empty requirement column means nothing satisfies it. In the example, EV-5 Session Receipt.
Verify Requirement Matrix
Test cases against requirements, with an arrow wherever a test case verifies a requirement.
An empty requirement column means nothing verifies it. In the example, EV-3 Connector Interlock.
Dependency Matrix
Blocks and test cases as rows, Satisfy and Verify as the dependency criteria. Color each criterion so the two kinds of arrow look different.
Every requirement column should end up with at least one black and one violet arrow.
Chapters
How to
The same steps as the video, on the EV charging station: five requirements, five blocks and four test cases.
Create the requirements in a Requirements package and give each one an id and its text: EV-1 Driver Authentication through EV-5 Session Receipt.
On a requirement diagram, draw a satisfy from each block to the requirement it satisfies. Card Reader satisfies Driver Authentication, and Power Cabinet satisfies Charge Power.
Create the test cases in a Verification package, then draw a verify from each test case to the requirement it verifies. One test case can verify more than one requirement: Session Price Test verifies two.
Use Cameo's Satisfy Requirement Matrix template. Blocks and requirements meet in a grid, with one cell for each pair.
Set the row element type, or the matrix shows no rows at all.A requirement with an empty column has nothing satisfying it. Double-click the empty cell where the right block meets it, and Cameo creates the satisfy relationship.
Test cases against requirements. An empty column is a requirement no test case verifies yet.
Make blocks and test cases the rows, and add Satisfy and Verify as the dependency criteria. Both draw the same arrow, so open Dependency Criteria, click the Style column for each criterion, and pick a color. We use black for Satisfy and violet for Verify.
More videos
Requirements · 9 minSysML requirement relationshipsTrace, deriveReqt, satisfy, verify, refine, copy and containment, and when to use each.
Allocation · 7 minAllocation with swimlanes and an allocation matrixThe EV charging model this example starts from: actions allocated to parts.
Traceability · 12 minTrace relationships across table columnsCreate and view trace relationships in a table and in a matrix.
Requirements · 9 minDropdowns and custom columns in requirementsAdd your own attributes and pick lists to a requirements table.
Requirements · 8 minLink requirement text to value propertiesKeep the numbers in a requirement's text tied to the model's values.
Requirements · 27 minRequirement with a textual constraintA subscriber question, answered step by step in Cameo.
Next steps
Training
$2,650Remote · $3,250 in person · 18 hours
Derive, satisfy, verify and refine relationships, checked in traceability matrices, on a full model you build in Cameo on our cloud VM. No license needed.
See 2027 datesConsulting
$0Your model, our engineers
Send us your model and we'll show you where its traceability has gaps: requirements nothing satisfies and requirements nothing verifies.
Book a free model reviewQuestions
A matrix view that shows requirements against the elements related to them. Cameo has Satisfy and Verify Requirement Matrix templates, and a general Dependency Matrix you can set up with any relationship types.
Satisfy goes from a design element, usually a block, to the requirement it meets. Verify goes from a test case to the requirement it proves. A requirement needs both to be fully traced.
Check the row element type. If it isn't set, the matrix shows no rows at all.
Both criteria draw the same arrow by default. Open Dependency Criteria, click the Style column for each criterion, and give it a color. We use black for Satisfy and violet for Verify.
Yes. Double-click an empty cell and Cameo creates the relationship. In a Dependency Matrix with several criteria, it asks which one to create.
Use a matrix to find gaps across many requirements at once. A relation map is better for following one element's relationships several levels deep.
Yes. Cameo Systems Modeler and CATIA Magic are the same software under different names, and the matrices work the same way.
CameoMagic is an independent company with no affiliation with, sponsorship by, or endorsement from Dassault Systèmes. CATIA and Cameo are trademarks of Dassault Systèmes or its subsidiaries.
Watch the video when it premieres on Oct 27, learn traceability hands-on in SysML Fundamentals, or have us review your model for free.
Prefer email? Write to consulting@cameomagic.com
Tell us about your model and we’ll follow up to set up your free 30-minute review.
No account yet?
Create an Account