Forum Replies Created
August 26, 2021 at 11:07 in reply to: Copying a requirement doesn’t update the requirement ID #2469
You’re right, it would be nice to ensure having a unique ID. As you’ve probably seen, at least the system marks the ID as a duplicate. Once you save, you should see an error marker in the side pane.
This feature request is on our backlist. I hope the error marker is a sufficient workaround until we get to it.
Best – Michael
This is not possible out of the box, unfortunately. However, the code for the ID Presentation is public and could be modified accordingly.
Here is a tutorial on how to do this: https://wiki.eclipse.org/RMF/Contributor_Guide/Presentations
Sorry, that’s not possible. You can do this with ReqMan, but from what I hear, it costs around EUR 25.000
Best – MichaelFebruary 18, 2021 at 11:14 in reply to: How do you hide SPEC-OBJECTs with ReqIF.ForeignDeleted set to true? #2399
Hi CR – This is possible, but would requiring some programming. As a workaround, you can easily set up a search filter. That would at least give you an outline where the deleted Objects are grayed out.
Here is the chapter in the user guide.
- This reply was modified 8 months, 1 week ago by Michael Jastram.
The free version of ReqIF Studio has a rich text editor that uses Java FX. This is only available if you get Oracle Java 8. Note that this is a very old version of Java.
The better option is to use the component “Extend”, which is €60/year:
Best – Michael
There are three primary use cases:
- Conducting ReqIF-based Reviews: If you receive ReqIF for review and similar activities, but don’t have a ReqIF-capable tool.
- Debugging ReqIF: Many ReqIF implementations are buggy and/or are interoperable, as only a subset of ReqIF is supported. Having a fully compliant editor can really help (compare this to using a simple XML editor)
- Basic RE: There are indeed some organizations that use ReqIF Studio for requirements engineering. This works for small specs and small teams
In short, it is not intended as a DOORS replacement, which also explains the significant price difference. 🙂
To be honest, the CSV importer was a simple prototype, and as you noticed, it’s violating the ReqIF spec by not setting the last change attribute. Sorry!
Also, you can’t edit the attribute, as it is updated automatically when you modify an item.
There are a few workarounds:
- If it’s a small number if items, then the attribute will be set when you edit them.
- You could also do a global search&replace on the raw XML
- You could simply ignore the messages. These warning won’t interfere with the operation of ReqIF Studio, and chances are low that this is a problem for any other ReqIF importer.
In the meantime, we logged this in our issue tracker.
I am still troubleshooting this. In the meantime, you could use Extend instead of the standard editor. As you can see from the above screenshot, when working on an embedded object, the dialog has a “open with default system viewer” link.
I’ll update this thread if I have news on the standard editor.
Okay, the screenshot clarifies it. Well, the icon you see in the rich text is hyperlinked. In other words, after importing the ReqIF in a different tool, the icon should be clickable, and clicking on it should open the embedded file.
What is the tool you are importing the ReqIF into? Is the icon clickable in that tool?
Embedded Objects are one of the most problematic aspects of ReqIF, unfortunately. Here are a few things that you can do:
- Try again with a file that does not have spaces in it. I doubt that’s the problem, but this is already one potential pitfall less.
- Open the .reqifz archive (it’s a zip file) and make sure the PNG is in there
I assume that you can re-open the ReqIF in ReqIF Studio, and it looks fine?
> But then, how to download / extract / identify a document that is encapsulated in a requirement, except opening the xml in a text editor?
You don’t need the RTF wrapper. You can simply add any file to a rich text field. ReqIF Studio will turn it into a hyperlink, and the file will be stored in the Project folder.
You can then open the file from ReqIF Studio with your System Viewer (e.g. Excel for an embedded spreadsheet).
Have a look at this screenshot from Extend:
I hope this helps!
First, I think that there are indeed better forums for this question than this one (see below): While ReqIF has traces (SpecRelations), ReqIF does not make any call on the semantics of the relationship. In other words, you can name relations whatever you like, and give it whatever meaning you like. As you noted correctly, this is quite different from modeling languages like SysML, which have a clearly defined semantics.
I remember the argument of refine vs. derive from over ten years ago! One can argue one way or another, and it’s certainly arguable whether the current definition is a good idea or not (there is no right or wrong, just better or worse).
Therefore, I am not even trying to answer your question. Instead, I would encourage you to engage with the OMG SysML Working Group:
If you are a member of INCOSE (or a local chapter thereof), then one of their working groups would also be a good place to discuss this.
Just to close the loop on this one, things are working again!
Cheers, -MichaelMarch 14, 2019 at 17:27 in reply to: How would you handle baselining of requirements in ReqIF environments? #2184
You are right, using a repository like GIT or SVN would be the way for baselining with ReqIF Studio. Remember, this is not a professional RE-Tool, it’s a ReqIF Editor.
Having said that, for a small number of requirements, using a repository actually works quite well. You can use Binom to compare different versions (or different Baselines with each other.