New in Requirements Portal

Consolidated UI of the Importer

In this release, the Import Wizard used to import requirements to your projects has been updated to consolidate the user interface of the AI importer and the classic (formerly legacy) importer.

When accessing the Import Wizard, it will now suggest you uploading a file of a supported type (*.pdf, *.docx, *.xlsx, or *.csv).

Files in *.pdf and *.docx formats can only be imported using the AI importer. If you upload a *.xlsx or *.csv file, you can choose to use the classic importer by enabling the Classic Import (Non-AI) option.

The user interface of both AI and classic importers shares similar controls.

A number of improvements has been added to the AI importer: 

• Custom columns (including creating custom columns directly on the review page).

• The ability to remap fields.

• The ability to update existing requirements with the imported data.

For more information, refer to the Import Requirements page.

Engineering Assistant Improvements

The following improvements have been implemented to the Engineering Assistant functionality in this release:

• You can now copy your previously sent request or a response from the Engineering Assistant. Click the  button in under a request or response to copy its content to the clipboard.

  

• You can now scroll through previously sent prompts by using the Arrow Up and Arrow Down keys when the cursor is inside the text field in the Engineering Assistant pane.

For more information, refer to the Agentic Requirements Engineering page.

Support for the REST API

In this release, support for the REST API has been added to Requirements Portal. Using the REST API, you can get and modify data from Requirements Portal or even write data back into Requirements Portal and thus update information. Additionally, this gives you the possibility to connect/integrate with other applications.

For more information, refer to the Rest API and Python API Documentation page.

• The Engineering Assistant functionality has been updated with the ability to use Skills. A skill is a reusable instruction set that the Engineering Assistant can execute in to perform a specific task more consistently. A skill packages how a specific engineering task should be done – the intent, the boundaries, the inputs it needs, the steps to follow – so that the same outcome is produced consistently, regardless of who runs it or when and without each user having to explain the same instructions every time.

  A skill can be treated as:

  • A repeatable engineering workflow

  • An organizational standard made executable

  • A way to package expertise and make it reusable

  A set of available skills is managed using the AI Skills window accessed by clicking the  button at the top right of the Engineering Assistant pane. From this window, you can add new and change and delete existing skills.

  

  Skills can also be managed on the Settings – AI Skills page (accessed by clicking the  ​ icon at the top right, selecting Settings from the menu that appears, and then selecting AI Skills from list in the left-hand pane)

  Skills are invoked automatically by the AI which selects and applies them automatically based on your intent. You do not need to memorize commands or manually select skills. For example, when you send Rewrite these requirements using our company writing standard, the Engineering Assistant detects the intent (requirement standardization), identifies the skill whose short description best matches that request, executes the instructions defined in that skill, and returns the improved requirements.

  When the Engineering Assistant processes your request based on a skill, the used skill will be shown in the Check what I looked for collapsible region in the Engineering Assistant pane. Click the link to open the AI Skills window with the corresponding skill highlighted.

  

  For more information about the Engineering Assistant functionality, refer to the Agentic Requirements Engineering page.

• Highlight of changes suggested by the Engineering Assistant has been enhanced in this release. Now, all suggested changes are visible in the requirements table.

  • New requirements are highlighted in green, with the icon in the  icon in the Identifier column.

  • Changed requirements are highlighted in purple, with the  icon in the Identifier column. Actual changes are also highlighted in the table.

  • Requirements suggested for removal are highlighted in red, with the  icon in the Identifier column.

  

  

  

   

  For more information about the Engineering Assistant functionality, refer to the Agentic Requirements Engineering page.

• The Engineering Assistant functionality has been updated with the ability to show the current chat context. Click the  button at the bottom of the Engineering Assistant pane to display the Chat Context pop-up presenting the following information:

  • Project – shows the name of the current project and the name of the currently selected folder, specification, or section.

  • Filters – shows the number of filters currently applied to the table and the list of columns to which the filters are applied. 

  • Rows selected – shows the number of currently selected requirement rows.

  

   Click the  button to open the Chat Context pop-up. In this example, the Project region shows the name of the current project (Drone_Example_Project) and the name of the currently selected specification (Drone_Requirements).

  

  The Filters region shows the number of currently applied filters (2) and the list of columns to which the filters are applied (V&V Status and V&V Methods).

  

  The Filters region shows the number of the currently selected specifications (3).

   

• The Engineering Assistant functionality has been updated with the ability to perform a search in a specific folder.

  

This release includes bug fixes to enhance the overall functionality and user experience.

• The Engineering Assistant functionality has been extended with the ability to modify, create, or delete requirements. Now, you can submit requests such as:

  • Generate requirements for a lightweight drone power supply that takes a 6S LiPo input, provides regulated 5 V / 5 A and 12 V / 3 A outputs, and weighs under 150 g. It should handle vibration and -10°C to +50°C operation, with protection for short circuit, reverse polarity, overtemperature, and low battery.

  • Change the required maximum operating temperature for all parts to 60°C.

  • Can you identify all requirements that affect the sizing of the power system and ensure they are verifiable?

  • In the new design, I've replaced the camera with an IR sensor. Remove all requirements that were related to the camera.

  When you submit a request to the Engineering Assistant to create a new or change or delete an existing requirement, suggested changes will be shown in a dedicated tile within the Engineering Assistant pane where you can review them (by expanding the Changes summary collapsible region) and then either apply or discard the changes.

  

  Also, the requirement(s) related to the latest query are now highlighted in the requirements table, and the number of related requirements is shown in the project tree next to the corresponding specifications, sections, and folders.

  

  For more information about the Engineering Assistant functionality, refer to the Agentic Requirements Engineering page.

• The ability to delete a requirements project has been added. In Requirements Portal's Home page, click a project's  control and select the Remove command of the menu that appears to remove that project. Before the deletion is complete, you will be asked to confirm.

  

  • The deletion is permanent, i.e., a removed requirements project cannot be restored.

  • Removal is only possible if you are the owner of the project or a Workspace Administrator.

  • If the project to be removed has external dependencies (i.e., references being used in other projects), they will be listed so you can remove them manually before proceeding ().

  For more information about working with projects, refer to the Project Module page.

In this release, support for commenting within your requirement projects has been added to Requirements Portal. A comment is a user-added note that is assigned to a specific requirement and may be replied to by other users. Comments promote collaboration between users without altering the shared data itself, because comments are stored by the Workspace independently of that data. You can mention one or more people or groups in the comment. A comment can also be assigned to a Workspace member.

Comments are posted, replied to, and managed directly within the requirements table using a contextual commenting window. Comments are also presented on the Comments and Tasks pane, which is presented on the right-hand side and provides more of an overview/navigational instrument, rather than the operational interface. Use the  control at the top right to toggle the display of the Comments and Tasks pane.

For more information, refer to the Commenting page.

AI agents provide substantial advantages for engineering tasks like requirements capturing by significantly enhancing efficiency and automating complex, repetitive workflows. In Requirements Portal, the Engineering Assistant functionality is now available. It leverages AI technologies to provide you with fast, automated review tool for your requirements that allows you to ask questions about requirements in your current project in free-form, natural language and get quick answers without manually filtering or searching through the requirements, for example:

• How many requirements are not verified?

• Are there any engineering gaps in these requirements?

• Show me all requirements about the power supply.

• Which requirements need to be taken into account for PCB design?

• Do any requirements conflict with each other?

• Give me an overview of all battery-related requirements.

For more information, refer to the Agentic Requirements Engineering page.

This release includes bug fixes to enhance the overall functionality and user experience.

This release includes bug fixes to enhance the overall functionality and user experience.

Requirements Verification Improvements

• For requirements that have no assigned V&V activities, you now have the ability to manually define their V&V status. Double-click the requirement's V&V Status cell and select either Verified or Not Verified from the menu that appears.

  

  The V&V status of requirements that have linked V&V activities is set based on the status of these activities.

  Additionally, V&V rules no longer affect the V&V Status of requirements.

  For more information about requirements verification, refer to the Flow 4: Manual and Rules Verification Flow page.

• When adding an applicable block to a requirement which V&V Status was manually set to Verified, you will now get a warning that the requirement was already verified. Use the warning window to choose either to keep the V&V status of the requirement or reset the status (set it to Not Verified) while adding the block.

  

  For more information about available requirement fields, refer to the Requirement Fields page.

• When you copy requirements using the Custom Copy method and some of the requirement being copied have assigned V&V activities, a warning is now shown next to the V&V Status field of the Reuse Requirements window at the Select Fields to Copy & Synchronize stage. 

  

  In the example shown below, several requirements were selected, and some of them have V&V activities assigned.

  

  When copying these requirements using Custom Copy, a warning will be shown next to the V&V Status field. 

   

  If all requirements being copied have assigned V&V activities, it will be not possible to select the V&V Status field as a field to be copied.

  For more information about the Custom Copy feature, refer to the Reuse Requirements page.

Requirements Creation Improvements

• The Create Requirement window has been improved to provide a more straightforward process of creating a requirement. When the window is initially accessed, it is presented in a simple form, with the Identifier and Text fields only. Click the  button at the bottom of the window to access other fields, such as Specification, Section, etc.

  

  The Create Requirement window in its simple form.

  

  The Create Requirement window in its advanced form.

   

• ValiAssistant now suggests improvements to the requirement text entered in the Text field of the Create Requirement window while you type the text (the process starts when you stop typing for three seconds). Alternatively, click the  button at the top right of the field to start the process manually.

  

• When you manually create a requirement and select to check it for possible valis (by enabling the Parametrize values option in the Create Requirement window), the process of valifying the requirement is now performed in the background. After clicking the  button in the Create Requirement window, the requirement is now created immediately, without showing further windows related to the valifying process. Once the requirement is valified, you can click the  button in the pop-up that appear at the bottom right of the page for details about the valifying process.

  

  After creating a requirement with the Parametrize values option enabled, it appears in the list immediately, and a pop-up notifying about the valifying process appears at the bottom right of the page.

  

  Once the process if finished, another pop-up appears, from which you can access the Calculation Details window.

   

For more information about creating requirements, refer to the Creating Requirements page.

Other Improvements

• In the Select Requirements window used to assign requirements to a block (accessed by clicking the  button in the Requirements view of a block in the Blocks module), you now have the ability to select columns to be displayed in the window (Columns) and the ability to filter the content of the window based on requirements' Identifier, Text, and Specification.

  

  For more information about the Blocks module, refer to the Blocks Module page.

• To provide consistency with entities related to Verification & Validation, the Methods field has been renamed to V&V Methods in all places of Requirements Portal. Some examples of these places are shown below.

  

  The V&V Methods column in a specification table in the Requirements module

  

  The V&V Methods column in a specification's Parents view in the Requirements module

  

  The V&V Methods column in the list of activities in the Verification & Validation module

   

  For more information about the Verification & Validation Module, refer to the Verification & Validation Module page.

This release includes bug fixes to enhance the overall functionality and user experience.

• A new Home page has been introduced in Requirements Portal in this release. The page provides access to existing projects, which target requirements management, and also provides the ability to create a new project.

  

  The Home page opens when accessing Requirements Portal using the nine-dot menu at the top right of the Workspace's browser-based interface.

  For more information, refer to the Project Module page.

• When creating a new requirement while the Requirements entry is selected in the project tree (i.e., no specific specification is currently selected), a default specification (the first specification in alphabetical order) is now selected in the Specification field of the Create new requirement window.

  

  If the project has a single specification, it will be selected.

  If the project has no specification, an attempt to create a requirement will open the Create Specification window using which you can create a specification first.

  

  For more information about creating requirements, refer to the Creating Requirements page.

• It is now possible to export a table in the Statuses and Procedures views of a run in the Verification & Validation module. Use the Export sub-menu of the view's right-click menu to export the table to a file of the *.csv, *.xlsx, or *.xml format.

  

  

   

  For more information about the Verification & Validation module, refer to the Verification & Validation Module page.

• In the V. matrix view of requirements, the activity creation action is now available in the  button menu. The requirement import action has been removed from the menu.

  

• If Requirements Portal is not activated yet for a Workspace, it is now possible to start the activation process from the Requirements pane when viewing a design project in the Web Viewer.

  

  For more information about working with requirements in the context of a design project, refer to the Working with Requirements page.

• Performance of the AI importer has been improved for long (more than three pages) documents by parallelizing extraction of sections.

  For more information about the AI importer, refer to the Import Requirements page.

• Fixed an issue when formatted text (that uses bullet points, italics, etc.) in custom columns was displayed incorrectly in exported documents.

  For more information, refer to the Document Export Custom Templates page.

• In order to consolidate the user interface of Requirements Portal with other elements of Altium Platform, a number of UI changes have been implemented in this release:

  • Breadcrumbs are now available at the top left of the page, under the name of the Workspace.

    

  • In the Table view of requirements, the menu of requirement actions is now available by clicking the  button in a dedicated column ().

    

  • A new Info pane has been implemented for specification sections.  The pane substitutes a separate Section info view and therefore, allows displaying and modifying specification section details without leaving the currently selected view (such as Table or Doc). When a specification section is selected in the Requirements Module, click the  button at the top right of the page to access the pane.

    

• The AI importer has been enhanced in this release.

  • The importer now recognizes the content between the document title and the first heading as a requirement.

  • The owner of imported requirements is now assigned not only based on the user's first and last name, but also the email. 

  For more information about the AI importer, refer to the Import Requirements page.

• A new Info pane has been implemented for specifications. The pane substitutes a separate Spec. info view and therefore, allows displaying and modifying specification details without leaving the currently selected view (such as Table or Doc). When a specification is selected in the Requirements Module, click the  button at the top right of the page to access the pane.

  

  For more information about specifications, refer to the Create Specifications page.

• The AI importer has been enhanced in this release:

  • The AI extractor has been improved to better handle bullet points and line breaks.

  • The title of the file being imported is no longer present in a section or subsection in the hierarchical structure of requirements.   

  For more information about the AI importer, refer to the Import Requirements page.

In this release, the process for creating and importing requirements has been updated. To perform either of these actions, navigate to the Requirements Module, click the  button, and then select either Create Requirement or Import Requirements from the menu that appears.

For more information, refer to the Creating Requirements and Import Requirements pages.

This release includes bug fixes to enhance the overall functionality and user experience.

Requirements engineering often begins with drafting of stakeholder requirements in documents like PDFs and Excel spreadsheets where data is not well structured. Extracting requirement data manually from these unstructured documents might be labor-intensive and error-prone, and in order to expedite the process of capturing requirements in Requirements Portal, you can leverage AI capabilities to import requirements from unstructured PDF, Excel, Word, and CSV files using a new AI-assisted Importer.

For more information, refer to the Import Requirements page.

This release includes bug fixes to enhance the overall functionality and user experience.

This release includes bug fixes to enhance the overall functionality and user experience.

In order to align the UI of Requirements Portal with other parts of the Workspace's browser-based interface, the following changes have been implemented:

• A new left-hand pane has been introduced. The pane allows access to different modules of the Requirements Portal and corresponding elements (specifications, V&V activities, blocks, etc.) of the currently selected project.

  

  

  

   

• A new top bar has been introduced. From the  icon menu of the top bar, you can access Requirements Portal's Settings, the File Management view, Documentation, Help resources, and the Trash Bin.

  

• The display of controls used to switch between different views in modules has been updated.

  

  

   

This release includes bug fixes to enhance the overall functionality and user experience.

When creating a new folder for specifications in the Requirements Module, the folder now appears in the tree at the left-hand side immediately after creation, without the need for refreshing the page.

For more information about folders, refer to the Grouping Requirements page.