Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Re-using SPEC-OBJECT in SPEC-HIERARCHY #2541
    Sebastian
    Participant

    Thank you so much. Ok, this is bad…

    Sebastian
    Participant

    Aha, now I have found this information right here on this page:

    ReqIF Under the Hood


    which explains: “This ID must be different for every file! In other words, even if just one requirement has changed, a new ID must be used.”

    Reading the spec once again, I see that REQIF-HEADER is not an “Identifiable” with respect to section 10.2

    This means to me, I can use the IDENTIFIER of the REQIF-HEADER to distinguish between my subsequent exports. I also found out, that ReqIF-Studio does not alter it during export, so this seems appropriate for my purpose.

    in reply to: Which kind of identifier to use for which purpos #2497
    Sebastian
    Participant

    Hello Michael,

    ah, now I am getting close. So the IDENTIFIER attribute of a SPEC-OBJECT should never change, while the requirement develops over several roundtrips – OK.
    The foreignid should be human readable and therefore also cannot be the place for my “real” id. And the ALTERNATIVE-ID is not meant for this also – and shouldn’t be changed.

    But if I have no possibility to transport the real id through the roundtrip iteration, then I would need to store a mapping between the IDENTIFIER (which stays the same through the whole conversation) and the real id for each outgoing Customer Request.

    Wouldn’t it be much better, if I could transport the real id through the reqIF roundtrip?

    Thanks for you reply btw 🙂

Viewing 3 posts - 1 through 3 (of 3 total)