MBSE with GENESYS Oct 2023

Rename Requirements

Number Original Name

New Name

Auto ‐ naming by the parser gives us a starting point, but we want to adjust the names for clarity

R.1.1 Provide Continuous Real ‐ time Support To

Continuous Support

R.1.2 Be Unavailable No More Than Availability R.2.1 Accept Information Requests from Certified Accept Requests from Certified Customers R.2.2 Retain An Inventory Of Previously Retain Inventory and Provide Products R.2.3 Control Multiple Image Collectors And Control Multiple Collectors and Collector Types R.2.4 Be Staffed At A Maximum Maximum Staff R.2.5 Provide Feedback On The Customer’s Provide Feedback R.2.6 Provide A Means Of Prioritizing Prioritize Requests R.2.7 Monitor And Assess Its Own Monitor and Assess Performance

Rename entities one of three ways: ribbon bar command, right ‐ click and select from context menu, or edit Name on the property sheet

143

Identifying Composite Requirements Our objective is single, verifiable Requirements . We can identify those Requirements that must be refined further. Requirements R.2.2, R.2.3, and R.2.7 contain multiple requirement statements meaning they are “composite” 1. Change the Facilities to Essentials

2. Select the Requirements class 3. Control ‐ click on the indicated Requirements

4. Right ‐ click and select Set Attribute 5. Select “Type” from the attribute drop ‐ down to set the type attribute 6. Select “Composite” from the Value drop ‐ down 7. Click OK

The Set Attribute command can set an attribute from anywhere (without opening the property sheet) and can be used to set the same value for multiple entities at once

144

MBSE with GENESYS