OSATE always gives warnings for requirements that are already referencing another requirement

[Carlos Ramos]

I copied the ALISA example MIS-SSS.reqdoc 1:1 to my project. I then created some system requirements and had a reference like:

see requirement MIS_SSS.SYS_123

I get a warning that “System requirement should have a stakeholder goal or requirement reference.”

Also, in the MIS_SSS, all requirements have that warning. That is the source document though, so why should I see all the yellow warnings for something that is expected? Or am I not marking something right or missing some other syntax?

[Carlos Ramos]

I want to add to this after trying to do the same, but this time using goals like “see goal”. I copied the stakeholders file and the goals document. I tried a reference from the system requirements to the goal and the warnings are gone. The problem however is I don’t want to reference goals. I want to reference system requirements since I am working on a subsystem. I could act like our customer requirements are like goals but I’m not sure that is what is intended.

Do requirement to requirement references really cause warnings in OSATE? It seems that is a case.