Glossary
Access partition - (User Management) |
Grouping elements of Visure Requirements. The elements are structured in this way in order that different users may have different access permissions to different groups of elements.
|
| Active baseline - | Baseline that is selected by the user in Visure Requirements client. If the active baseline is different from the current baseline, no data can be modified.
|
| Admin - | User created by default in all the projects. Has administrator privileges.
|
| Attribute - | The attributes of items are characteristics associated with specification elements, so each one of the items acquires those characteristics, and their value may be specified separately for each individual item. The scope of the attribute determines the set of items for which the attribute will take values.
|
| Attribute Type - | Category of an attribute of elements or a specification property.
|
| Author - | User of the project who is responsible for creation of an element.
|
| Baseline - | Set of all elements of a project, where each of them appears in a specific version. All links between elements also belong to the baseline.
|
| Criteria - | The requirements are filtered based on selection criteria that match the different types of elements of the project and its values: author, date of creation, concept, etc.
|
| Current Baseline - | Baseline containing the most updated version of the Project elements. It is the default active baseline, that is, the one selected by default when a project is open.
|
| Database - | Information storage system for one or several projects.
|
| Date - | Information associated with the elements, that shows the date on which they were created or modified.
|
| Element - | Any of the concepts managed within Visure Requirements, such as items, specifications, attributes, etc.
|
| Field - | Contains a specific, indivisible part of the information of an element.
|
| Filter - | Specifies the set of selection criteria to filter all the elements to be viewed. For example, a filter may be applied to view only the requirements input by a specific author or associated with a specific value of an attribute. |
 |
| Inheritance - | Type of association that indicates a hierarchy between specifications in which one of them inherits the structure and/or behavior of the other.
|
| Item - | Project element. In the application context, it usually refers to a requirement, but it can also refer to a test case, a defect, a risk...…
|
| Documents - | This is a group of items of the same type, with some common characteristics.
|
| Login - | Username formed by a chain with a maximum of 32 characters.
|
| Permission - | Rights assigned to a user of a project to be able to read, create or modify elements.
|
| Project - | Basic working unit of Visure Requirements.
|
| Scope - | Set of elements for which an element attribute takes individual values. It can be all elements of a given type (requirements, test scenarios, etc.) or one or several specifications (for example, user requirements, performance tests, services of subsystem 1, etc.).
|
| Tree - | Structure displaying the elements of a model in hierarchical format.
|
| User - | Each one of the persons with permission to work on a data base with Visure Requirements projects.
|
| View - | Screen that shows a part of the information on a project. The project is comprised of several views that may be shown simultaneously and remain synchronized between each other, so if one element appears in several views, if it is modified in one of them it is updated in the others.
|
| Window - | See View. |