![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Partitioning and using Change proposals Topic Summary: Created On: 8-Mar-2006 19:17 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I am running DOORS 8.0. I am trying to partition a module, bring it into the away database, and write change proposals against it, approve/apply them, then bring the updated module back to the Home database. I am trying to keep the history of the changes with the module, i.e. where you could normally follow a changed object to the change prop module and see why it was changed, etc...
Here are my questions: 1) Is it possible to keep the history without someone keeping the change proposal module? 2) Or, do I need to partition the change prop module/and link module for the change proposal module so that the change data (i.e. reason for change) is in the HOME database when the CP module is re-joined (if that's possible). I'm thinking the CP system won't work this way...I imagine it will generate it's own CP module in the AWAY database, so it won't jive with the partitioned one... Not to mention the CP links module would be locked in the home database until it is rejoined...Thus not permitting others to write CP's against other modules. Any suggestions? Thanks. Patrick Edited: 8-Mar-2006 at 20:08 by Patrick Whalen |
|
![]() |
|
![]() |
|
A long time ago - DOORS 5 I think - I tried using partitions and CPS. It was a bad move, warnings of database corruption, much heartache and a very patient help desk. There was a warning somewhere in the back of the manual that these should not be used together. I have not tried since, but I would recommend checking with support that this is not a problem now. I think it might be.
Try on a standalone database if you can. Hazel |
|
![]() |
|
![]() |
|
Hazel,
Thanks for the info. What was your solution? Did you just partition the modules and then lose the reason for change, etc, when you rejoined the HOME database? Patrick |
|
![]() |
|
![]() |
|
If I was provided a partition and I wanted to implement a CPS for one or more modules of the partition:
1. I would create a copy of the modules with objects linking to the original objects in the partitioned modules. 2. Run the CPS on the module copies. This allows me to configure the module copies with extra attributes, etc that I needed and I could configure the CPS for my system and users. 3. When it is time to return the partition, update the partitioned modules with the contents of the copies. Provide any needed documentation or copies of my CPS to the originator. Having a CPS on my database implies that I have complete adminstrative control. If a CPS is partitioned, you lose that control because of the controls and locks put onto the partition. ------------------------- Cliff Bly |
|
![]() |
|
![]() |
|
I abandoned the CPS and captured my reasons for change in attributes. This can be made to work for light weight process, and a heavy weight process probably wants something more flexible than the CPS anyway.
Hazel |
|
![]() |
Telelogic DOORS
» General Discussion
»
Partitioning and using Change proposals
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.