What´s New in Visure Requirements
Visure Requirements 4.7 provides additional functionality, improved usability and security, modernized product backend for corporate deployments and new supported versions for Databases, Operating Systems and PluginSDK development environments.
Overview of enhancements
- Improved usability to ease end-user adoption
- Improved security for the deployment of Visure Requirements in critical environments
- Modernized product backend for corporate deployments
- New supported versions for Databases, Operating Systems and PluginSDK development environments
Visual Representation of the Edit Status of a Requirement
Users will now be able to quickly identify the status of a requirement through the new status icon. This new icon indicates whether the element is being edited by us i.e. checked out by us ( ), if the element is being edited by another user i.e. checked out by another user ( ), or if the element is not being edited by anybody i.e. checked in ( ).
Improved User Interface
The details tab has been redesigned to help users deal with a large number of attributes and large amounts of information at the same time:
Edit common attributes window
Performing bulk operations is key in the Requirements Management process.
The edit common attributes window has been improved to help users modify common attributes over a large group of items at the same time.
The versions tab now highlights the difference in the number of attributes in the different versions, helping users quickly spot all the differences between two versions of the same item.
New steps tab in Test Scenarios and Scenarios
Steps have now their own tab separate from the Details tab, providing users a cleaner environment to work with steps.
Visure Requirements’ terminology has been improved to provide a common understanding of the terms inside the tool and reflect the intended use of them.
|New Term||Former Term|
|Data Model||Block Diagram|
Only for instances of relations between items. Other relations still keep the same "Relationship"
|Traceability tree||Relationship by Motive|
- New Universally Unique Identifier for Requirements
With this new item attribute, users may globally identify a requirement throughout all projects, databases and applications, guaranteeing its uniqueness.
This attribute is specially useful when integrating Visure Requirements with other systems, and interfacing with other companies, making it possible to track the item back to its original location in Visure Requirements independent from its current location.
The new password policy for Visure Requirements users has been improved to match other User Management policies such as LDAP or Active Directory, and comply with the most stringent security audits.
This new password policy includes:
- Password construction guidelines, including minimum length, and whether mixed case, numerals and special characters are required.
- Validity period of the user’s password
- User blocking policies such as number of failed attempts and the amount of time a user is blocked
- The administrator of the Visure database (Admin) is able to configure for all the users of the Visure database:
The security policies can be enabled from the New Security tab in the Users folder of the Administration Center.
The new underlying Visure Requirements datalayer has been modernized to adapt to the changing market needs providing a more robust, web-enabled business layer. This new architecture provides a more reliable, scalable and performance environment for projects with a high volume of data, and highly distributed teams.. It also means that Visure Requirements 4.7 desktop and the upcoming Visure Requirements Web components will be able to work together with the same Visure Database, thereby providing a seamless transition between versions.
Visure Requirements now supports the following versions:
- Operating Systems: MS Windows Server 2012 R2
- Databases: SQL Server 2014, Oracle Database 12c
- Plugin SDK: Visual Studio 2013