Custom OSLC domain - is it possible?
Hello!
Accepted answer
DOORS Next Generation has integrations with CM, AM and QM tools that are fixed in the implementation. To integrate some other domain with DOORS Next, you need to specialize one of the domains already supported, and then can use the link types of that domain to link with requirements. Generally oslc_am:Resource is used for this, and that does limit the available link types for linking with requirements. Note that DOORS Next expect the AM tool to store these links.
Comments
Thank you very much! I think that we will go this way described by you in the direction of building AM-based type of adapter.
Thank you very much! I think that we will go this way described by you in the direction of building AM-based type of adapter.
You might want to have a look at the Eclipse Lyo project.
One other answer
Yes, that is all possible. I suggest the you explore the OSLC Developer Guide and in particular the Sample OSLC adapter for IoT platform which shows how to use eclipse/Lyo Designer to define a new domain model, create an implementation of a toolchain component, and integrate with ELM applications including DOORS Next.
Comments
Yes, we used the mentioned documents but they describe a process of integration with Jazz based on standard OSLC domains. We have already a working version of OSLC adapter that can be integrated with DNG artifacts using Validated By link. Do you mean that if we will re-design our Toolchain model describing the solution as we need, then DNG will automatically recognize new OSLC domain and suggest new link type instead of Validated By one?
Thanks!