The Tools | Project Options | General Features 1 tab as below:
The following values can be set:
•SysML data Project
This option decides whether to handle requirements as SysML Data Project.
•Count and save requirement status when closing project
This option determines whether RaQuest counts and saves the status information in the project while the project is closing.
•Enable to delete items
This option decides whether the delete function is available or not. If the check is on, items can be deleted. If the check is off, items cannot be deleted.
oEnable to delete requirements
This option decides whether the delete requirement function is available or not. If the check is off, relationships between requirements, empty packages, members, and divisions can be deleted, but not requirements and their packages.
oConfirm when deleting
This option decides whether to show a confirmation dialog when deleting items.
oMove to Trash package
This option decides whether to move deleted requirements or packages to the "Trash" package in order to allow them to be undeleted later. (The items in the "Trash" package are not permanently deleted, so you can restore them as needed.)
▪Show Trash package
This option decides whether to show the "Trash" package in the tree view.
•Create a relationship when generating a child requirement
This option decides whether to create a relationship automatically when a new requirement is created under the parent requirement. If the check is on, RaQuest automatically creates a relationship between the parent and the child. (The relation defined is such that the child requirement depends on the parent requirement.)
oSpecify the type of relationship
This option decides whether to specify the type of relationship when created. You can select from Dependency (default)/Aggregation/Nesting.
oCreate relationship when moving requirement
This option decides whether to create a relationship automatically when a requirement is moved under another requirement. If the check is on, RaQuest automatically creates a relationship between the parent and the child.
▪Delete relationship when moving requirement
This option decides whether to delete the relationship automatically when a child requirement is moved from its parent requirement. If the check is on, RaQuest automatically deletes the relationship between the parent and the child.
•Change to the specified Requirement Category of the destination package when moving requirement
This option decides whether to change to the specified requirement category of the destination package when moving requirement
•Use Divisions as Member
In some property dialogs, there are dropdown lists of members. If this check is on, divisions are also displayed on these dropdown lists.
•Turn off "Review Required" flag when the Source Requirements List for Review is empty
This option decides whether to clear the "Review Required" flag automatically when the "Source Requirements List for Review" is empty.
•Display Attribute by list form on this project
This option decides whether to display requirement's properties in two tabs style which includes the Description tab and the Attribute tab, despite the option setting of Local Options | View | Display Attribute by List Form
•Save ID in front of requirement summary
This option decides whether to save the string including requirement's summary and its ID in front as a name of EA element. So that the requirement ID can be seen in Enterprise Architect.
•Add PackageID instead of automatic ID prefix
This option decides whether to add Package ID instead of adding automatic ID prefix and save it as a name of EA element when "Save ID in front of requirement summary" is checked.
•Sort RequirementID as numerical value
This option decides whether to sort Requirement ID as numerical value instated of string value.
•Use stereotype on relationship with UML Item
This option decides whether to add stereotype to relationship when it is associated to UML Item at UML Items tab of requirement property.
•Save a relationship map as requirement's child diagram.
This option decides whether to save a relationship map as requirement's child diagram. With editing the document template in EA, it is possible to bind the requirement with its relationship map when outputting the RTF document files.
•Use extended format in requirement's detail
This option decides whether to use the extended format like setting the fonts, inserting table and others in requirement's detail.
Caution: The save location of the detail is changed at an EA element.