About Requirements in Functional & Logical Design

Requirement Objects Definition

The following requirement objects are displayed in the tree (under the Requirement category) and in the work area:


Name	Definition	Available Commands (context menu)
Requirement category node	Structure node to organize the tree.	Insert… Insert New Specification Folder Insert New Requirement Specification Insert New Requirement Insert New Use Case Insert Existing Specification Folder Insert Existing Requirement Specification Insert Existing Requirement Insert Existing Use Case
Specification folder	A specification folder is a part of the requirement structure, to organize your requirement specifications in a specific folder. Note: Specification folders are not displayed in the requirement 2D graph.	Insert… Insert New Specification Folder Insert New Requirement Specification Insert Existing Specification Folder Insert Existing Requirement Specification Replace… Manage Latest Revisions Selection Mode… Select Children Select Others Select All Select Inversion Select Parent Select Siblings
Requirement specification	A requirement specification allows to enter basic details about the specification. An optional second step allows you to check in files (MS Word or another type) to the specification. This second step is performed through the same commands that are available for reference document.	Insert… Insert New Chapter Insert New Comment Insert New Requirement Insert Existing Chapter Insert Existing Comment Insert Existing Requirement Replace… Replace by Existing Component Replace by Existing Revision Replace by Latest Revision Replace by New Major Revision Manage Latest Revisions Selection Mode… Select Children Select Others Select All Select Inversion Select Parent Select Siblings
Chapter	Chapters contain requirements and comments.	Insert… Insert New Chapter Insert New Comment Insert New Requirement Insert Existing Chapter Insert Existing Comment Insert Existing Requirement Replace… Replace by Existing Component Replace by Existing Revision Replace by Latest Revision Replace by New Major Revision Manage Latest Revisions Selection Mode… Select Children Select Others Select All Select Inversion Select Parent Select Siblings
Comment	Comments provide additional information or commentary that is not part of a requirement.	Replace… Replace by Existing Component Replace by Existing Revision Replace by Latest Revision Replace by New Major Revision Manage Latest Revisions Selection Mode… Select Children Select Others Select All Select Inversion Select Parent Select Siblings Rich Content
Requirement	A requirement is intended to propose changes or additions to hardware or software products. Requirements are created by the Requirement Manager with input into a product's definition. Requirements are the initial point at which a request is analyzed.	Insert… Insert New Sub Requirement Insert New Downstream Requirement Insert New Parameter Insert Existing Sub Requirement Insert Existing Downstream Requirement Replace… Replace by Existing Component Replace by Existing Revision Replace by Latest Revision Replace by New Major Revision Manage Latest Revisions Selection Mode… Select Children Select Others Select All Select Inversion Select Parent Select Siblings Rich Content
Downstream requirement	A downstream requirement elaborates on some aspect of the original requirement. It provides new information. Note: In Functional & Logical Design, the downstream requirements are grouped in the tree under a Downstream Requirements folder, provided that the corresponding option is selected in Me > Preferences > App Preferences > 3D Modeling > Systems Architecture > Functional & Logical Design > . See Native Apps Preferences Guide: Tree.
Sub requirement	A sub requirement elaborates on some aspect of the original requirement. It does not provide any new information, just a clarification of the original information.
Requirement proxy	A requirement proxy is a subtype of requirement and corresponds to a requirement from an external system. Requirement proxies can be viewed in Functional & Logical Design and pointed to by implement links, but cannot be edited or expanded. Depending on the structure, requirement proxies appear as a downstream requirement proxy or a sub requirement proxy . Requirement proxies can be added to a requirement structure in Requirements Specification Editor and Requirements Structure Editor. In Functional & Logical Design, you can delete them from the structure and reorder them within the same parent. Note: You cannot import or export structures that contain a requirement proxy. For more information about requirement proxies, see Requirements Specification Editor User's Guide and Requirements Structure Editor User's Guide.	Reorder Delete
Requirement parameters	Note: In Functional & Logical Design, the requirement parameters are grouped in the tree under a Parameters folder, provided that the corresponding option is selected in Me > Preferences > App Preferences > 3D Modeling > Systems Architecture > Functional & Logical Design > Tree.	Delete Definition Open in New App
Extension	An extension defines an additional attribute for a requirement.

Edit and Review a Requirement

You can open a requirement for edition or review purposes.

To edit a requirement in a new web browser, select Explore in Web App from the context menu. A new window appears to let you edit the requirement in the Traceable Requirements Management app.
To edit a requirement in the same tab, select Embedded Web Browsing from the context menu. A Structure Display page appears. In this page, you can filter this view, edit the rich content of the requirement, etc. For more about the commands within the Structure Display, see the Traceable Requirements Management User's Guide.
To edit the rich content of a requirement or comment, select Rich Content from the context menu. See Editing Rich Content in Requirements and Comments.

Edit Parameters of a Requirement

From Functional & Logical Design, you can edit the parameters of a requirement.

See Editing Parameters of Requirements, Functions and Logical Components.

Locked/Unlocked

As many people can work on the same requirement structure within different apps (Traceable Requirements Management, Embedded Central, System Finder and Functional & Logical Design), we advise you to lock the objects before editing them.

Live Validation

You can perform a review on a requirement using the Live Validation app. See Working with Live Validation.

Import/Export a Requirement

From Functional & Logical Design, you can import or export a requirement from or to several formats, including 3D XML.

See 3DEXPERIENCE Native Apps: Importing and Exporting .