I'm evaluating OSEE as a possible replacement for a number of disparate
tools that my organisation uses. My personal background in requirements
management is primarily with IBM (Telelogic) DOORS.
I am stuggling with the apparent lack of documentation for OSEE Define.
How do I create relations between artifacts such as an element of design
being dependent on a requirement? I can see the ones from the example
suite in Sky Walker but can't work out how to create new ones.
Relations can be added / removed by double-clicking on any artifact,
selecting the "Relations" tab and dragging the related artifact into the
appropriate relation group.
Regarding the documentation issue. We are having some of the same
issues as some of the other Eclipse projects in trying to
create/maintain documentation in Eclipse Help, Eclipse Wiki and project
website becomes a daunting task. At EclipseCon this year, we ran across
a technology called wikitext where information maintained at eclipse
wiki can be automatically converted into the Eclipse Help system. The
Mylyn project created and uses wikitext for just this purpose.
We have had a number of discussions and have decided to move in this
direction. It will take some time to convert everything over, but it is
a priority to all of our users and developers.
Thanks Don. I appreciate the difficulty of keeping documentation on track
as we have a similar problem with some of our internal tools. The Wiki
approach sounds like a good way forward.
Relations can be added / removed by double-clicking on any artifact,
selecting the "Relations" tab and dragging the related artifact into the
appropriate relation group.
Regarding the documentation issue. We are having some of the same
issues as some of the other Eclipse projects in trying to
create/maintain documentation in Eclipse Help, Eclipse Wiki and project
website becomes a daunting task. At EclipseCon this year, we ran across
a technology called wikitext where information maintained at eclipse
wiki can be automatically converted into the Eclipse Help system. The
Mylyn project created and uses wikitext for just this purpose.
We have had a number of discussions and have decided to move in this
direction. It will take some time to convert everything over, but it is
a priority to all of our users and developers.
Thanks Don. I appreciate the difficulty of keeping documentation on track
as we have a similar problem with some of our internal tools. The Wiki
approach sounds like a good way forward.