What are common requirement attributes? How can you specify what you need? And how can you best work with attributes?
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.
Work with requirements attributes in practice – test it out.
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).
The attributes you select depend on the following four factors:
How large is the project? What are the hidden risks?
Properties and regulations of the field of application
What are the reference models? Are there modelling instructions?
What are the business’s standards? What provisions does it have?
Frameworks and development process restrictions
Do you have to observe liability laws? Are there process standards?
Document information for requirements
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
Are you curious about working with requirement attributes and a tool?
All the features discussed here can be used with our application life cycle management solution objectiF RPM. Try out a project straight away with our free trial edition. And if you have any questions, just get in touch with us!
Here you will find an overview of our knowledge pages.
Do you already know our objectiF RPM whitepaper?
Let us show you more knowledge in our webinars.
Applying knowledge with the right tool: objectiF RPM.
Receive up-to-date knowledge directly in your inbox.
Find more interesting downloads here.
By clicking "Accept cookies" you agree to the use of functional and analytical cookies that allow us to better analyze our own website.
Essential cookies are absolutely necessary for the proper functioning of the website and to ensure basic functions and security features of the website. These cookies do not store any personal information.