![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DOORS Partitions Topic Summary: Created On: 15-Jul-2008 16:04 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Other then what the DOORS Help has on Partitions, do anyone know of any specific problem areas, issues to be cautious of or any lessons learned that would preclude a program from using partitions ?
We need to have a way to allow different databases to edit the same module while maintaining CM control of the baseline. It seems to be coming down to Partitions, Archive/Restore or a control external to DOORS and then input back into DOORS. Thanks Bill LM IS&GS Sunnyvale, CA |
|
![]() |
|
![]() |
|
Bill Bauerly
I understand what you mean by "other then what the DOORS Help has on Partition". The DOORS partitioning function dates back to version 4 or v5. It has a legacy of bad feelings; thoughts of overhead to set-up, loss of performance, and the unknown about its daily maintenance for unexpected errors. First Quarter 2008, I spent a few weeks researching its v8.1 functionality between two mock databases. On a simple scale, set-up appeared easily, albeit very detailed. The Help does not volunteer all the details. So I suggest you experiment with it. There are good undocumented features embedded in Partitioning set-up and Synchronizing functions. Between a co-operative of DOORS-experienced engineers, none of us actually had first-hand experience with Partitioning, nor any current performance facts. Very Respectfully, Richard Robledo Bell Helicopter - Textron Incorporated Texas |
|
![]() |
|
![]() |
|
I've used Archive and Restore for this, and in versions later than DOORS 7.1, it seems that Archive and Restore strips all of the access from the module in the .dma. This makes it much more useful.
I think Archive and Restore could work for you, and be easier to maintain if you are only doing a few modules. You just need to script or set access rights manually when you get the module back into your database. ------------------------- Kevin Murphy http://www.baselinesinc.com |
|
![]() |
|
![]() |
|
Hi Kevin,
Can you provide more details how this is done? We have this problem of partitioning a module for more than one person to work on. Do you mean that a module is archived and restored as a separate module for another user to work on simultaneously? And later on, we incorporate the changes in the original module? - Krishna |
|
![]() |
|
![]() |
|
Krishna,
I think you have the wrong idea. When you pass modules back and forth in this manner, then only one database can write to it. Otherwise you can't reconcile the changes. Thus, if I send you a module, then on my end I have to make it read-only. You send it back, I delete my read-only one and restore yours. You make yours read-only at that point. That's really the only way to do it on a module-by-module basis. Also you'll need to record then restore links and keep them synchronized between databases. Getting this set up is a lot of work, but once you have the process going it works pretty smoothly. Partitioning is similar, except that it can be more than one module and you don't have to wrestle with links. ------------------------- Kevin Murphy http://www.baselinesinc.com |
|
![]() |
Telelogic DOORS
» Administration
»
DOORS Partitions
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.