What are common requirement attributes? How can you specify what you need? And how can you best work with attributes?
1
2
Specific information can be determined for each requirement. Structured logging of this information is a tried and tested method for ensuring that this information is documented consistently and changes to it can be traced at any time. The IREB tasks are a useful point of reference when working with requirement attributes. These will be summarized below.
How do you specify attributes?
A variety of attributes can be used for requirements. You can create templates to define which ones you need. A template could be a table structure, for example, in which you list attribute types with a short description. Make sure that the attributes can be differentiated between according to attribute type: for example, different information has to be documented for functional requirements than for non-functional.
A more visually appealing alternative is defining attributes with class diagrams. Then the requirement is simply a class that you can specify the desired properties for. The advantage of this method is that you can model relationships to other elements straight away, for example, the relationship between requirement and risk (by the way, you can also specify attributes for risks and other entities like use cases, test cases or change requests).
In practice, requirements or information for different attributes are normally documented with one tool: MS Excel. There, you can create a table and define individual columns as requirement attributes. But requirements engineering comes to its limits pretty quickly with this tool: references to other elements like templates for requirements have to be maintained manually, for example, as soon as a new folder structure is created or a file moved. That’s a lot of work in large and complex projects that sometimes have thousands of requirements.
It is more efficient to work with a special requirements engineering tool where it’s easier to create attributes for requirements of different types (functional vs. non-functional, etc.) and later fill them in with information. At the same time, such a tool ensures traceability of requirements and can, for example, quickly list changes of attribute information between different versions of a requirement. Here, you can see a comparison:
A comparison of two versions of a requirement
In such a requirements engineering tool, you often use forms that provide the definied attributes to capture requirements. They are similar to views on the requirements that only display specific attributes, for example. You can even create relationships to other project results such as goals or test cases in these forms:
View on a requirement through forms
The biggest advantage of attributes: Simple evaluation
Once the requirements information is recorded with structure via attributes, you can specifically access them according to your needs. A simple example: Display all the requirements with their derived test cases if available and only with the ID, name and state of these elements. This way, you can keep an overview, despite large projects and increased complexity.
A list with requirements and linked test cases
Overview of our Knowledge Base
Applying knowledge with the right tool: objectiF RPM
Find more interesting downloads here
This site uses cookies to constantly improve your experience with our website. You can find more information about their use in our Privacy Policy.
By clicking "Accept cookies" you agree to our privacy terms and the use of functional and analytical cookies that allow us to better analyze our own website.
Essential cookies are mandatory and do not store personal data.
You can deselect cookies for Performance, Analysis, Advertisement and Others here, even if the use of these cookies is only for statistical purposes.
Necessary cookies are absolutely necessary for the website to function properly and to ensure basic functions and security features of the website. These cookies do not store any personal information. By clicking "Save & Accept" you agree to our Privacy Policy.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Cookie
Duration
Description
_gat
1 minute
This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites.
_p_hfp_client_id
past
Elfsight sets this cookie to implement social platforms on the website and enables the social platforms to track the users by assigning them a specific ID.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
CONSENT
2 years
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
_ga
2 years
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_ga_YTLFCXYZSV
2 years
This cookie is installed by Google Analytics.
_gid
1 day
Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
VISITOR_INFO1_LIVE
5 months 27 days
A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSC
session
YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devices
never
YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextId
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requests
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
