Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Talk:ALF/Requirements Management
Attributes and Requirements
From the description I take it that a Requirement Type pre- defines a particular set of attributes. Is that the case?
Qualitypark: Yes, that's true. One quality issue of requirements is their completeness. Thats why for every type of requirements a pre-defined set of attributes is given which have to be filled to proof the requirements completeness. Different requirement types may have different quality criteria and for that they have different attributes.
Change Proposals
Are change Proposals allowed on any version of the requirement or only the current version?
Qualitypark: The goal is to achieve a set of valid, non-conflicting requirements. Historical versions are stored for traceability reasons, but only the current version is valid. Any change proposal is a request to change the requirement within the actual environment of requirements. Practically there is no need to change a version that is already outdated.
Links and Impacts
From the description, an impact appears to be a link between two requirements that expresses some kind of releationship between the attributes of one requirement and the attributes of another requirement. The relationship between the attributes is unclear.
Is the link bi-directional? Can I see the link from the Target ore must I create a reverse link/impact?
Are impacts modeled between RequirementTypes or are they created dynamically on Requirement instances?
How are the attributes in an impact linked (eg one to one, one to many, many to many)
Can two requirement instances have muliple impacts btween each other or only one (in each direction)?