Hi Robyn, Thank you so much for the detailed explanation - it really helps clarify how you manage the lifecycle and statuses in practice. If possible, I'd ...

Hi Marina, great questions! Our requirements have statuses, from draft, to approved, and then implemented. Once a requirement or set of requirements go into production, ...

Hi Robyn, Thank you again - your answer really helped me understand your approach. If a requirement has been verified during the testing phase - do you consider ...

Hi Marina, A requirement is retired when it is no longer valid or used in the system. It might be a business rule that is no longer valid or a functional ...

Hi Robyn, Thank you very much for the information! I have a few follow-up questions: When do you decide on the retirement of a requirement? How ...

Hi Marina, the IIBA (International Institute of Business Analysis) states that requirements have a lifecycle and should be maintained and reused until they are retired. ...

Hi Daniel, Thank you for reinforcing my intuition, logic, knowledge, and experience - it's encouraging to hear this from someone with your perspective! What ...

Hi Marina. Perhaps the following will help you justify your intuition (which I think is correct!) No system is built once and never changes. When the system ...

Hi Gianluca, I understand we are not the only DNG Customer. The question is if it seems possible to find the entire project life using of the DOORS requirements ...

Hi Marina, there are several customer around the world using DOORS/DOORS Next, OSLC and other component of the Engineering Lifecycle Management platform connected ...