This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Let's say I have two modules in DOORS Next. System Spec and Software Spec. Software links to System via Satisfies / Satisfied By. Link Validity is turned on.
The way it works out of the box is that if two artifacts in each of those modules are linked to each other, and that link is set to be valid, if the content of either of the artifacts changes, the link validity is set to unknown.
The way it *should* work according to Systems Engineering V principles is that only a change to the System Requirement should set the content back to unknown. If the software requirement changes it should still be a valid link.
This has implications linking from ETM to DN as well. The link from requirement to test case, if set to valid, should only be set back to unknown if the requirement artifact changes. If the test artifact changes, no one cares, and it's a bunch of busy work to set it back.
Idea priority | Low |
Needed By | Yesterday (Let's go already!) |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.1?topic=applications-link-validity
The link validity indicates whether the meaning of a link is satisfied by the content of the two artifacts that are connected by the link.
The validity summary shows you at a glance the status of all the links to relevant artifacts so you know which downstream artifacts you must examine to verify intended meaning of a link.
Tests are downstream of requirements, models, and designs.
Requirements are considered symmetric to each other.