Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Re-use of projects within hierarchy
Topic Summary: possible to have project visible in >1 other project?
Created On: 13-Nov-2006 14:23
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 13-Nov-2006 14:23
User is offline View Users Profile Print this message


Adrian Haw

Posts: 17
Joined: 25-Feb-2005

Is it possible to re-use a project (as a sub-project/re-usable component) within multiple other (eg: integration/system) projects? eg: Project C is a re-usable IP component Projects A & B are system projects which re-use Project C (which continues to be developed in various versions). Purpose us to maintain Project C in only 1 instance but re-use and make visible in other projects. I like to get the hierarchy, eg: System Projects Folder | ----- Proj A | | | ----- Proj C (read only for Proj A team) | ----- Proj B | ----- Proj C (read only for Proj B team) Re-usable IP Folder | ----- Proj C (read/write for Proj C team)
Report this to a Moderator Report this to a Moderator
 15-Nov-2006 11:24
User is offline View Users Profile Print this message


Robert Swan

Posts: 86
Joined: 14-Apr-2005

My short answer is yes-BUT its not straightforward. The major problem I had with trying to use a subproject was that tracing links across project boundaries wasn't simple. Although the dxl could be written to handle such cases, most existing code would need a rewrite, and we had a lot of that. The compromise was to only use DOORS project at the top level, and use folders for the subordinate levels, although they were named as Proj A etc.
Report this to a Moderator Report this to a Moderator
 23-Nov-2006 15:28
User is offline View Users Profile Print this message


Adrian Haw

Posts: 17
Joined: 25-Feb-2005

Hi Robert

Thanks for your answer. Can you elaborate on the issues you had with linking between projects and traceability?
Report this to a Moderator Report this to a Moderator
 24-Nov-2006 09:15
User is offline View Users Profile Print this message


Robert Swan

Posts: 86
Joined: 14-Apr-2005

It's been a while, so I can't remember all the references.
The net effect was that links across project boundaries resulted in the target module being reported as 'deleted'. I guess because DOORS only looks below the current project folder to match module id's.

It is possible to detect that situation and write the dxl to look in the next project up, but as I said. that would have meant rewriting a lot of existing DXL, some of which was in 3rd party tools, so we made the decision to not use multi projects.

Having a folder named as 'project 1z2z' was found quite adequate. 

Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.