Hi, |
Re: How to Copy Objects from One Module to Another? |
Re: How to Copy Objects from One Module to Another? SystemAdmin - Wed Sep 02 01:12:26 EDT 2009 |
Re: How to Copy Objects from One Module to Another? Doorsbert - Wed Sep 02 04:20:37 EDT 2009 Be aware that there is a bug in DOORS 9.1 where the Copy Objects tool does not copy Object Short Text. This issue is logged with DOORS Support for a future fix. Mark |
Re: How to Copy Objects from One Module to Another? mwilliamson - Wed Sep 02 11:51:24 EDT 2009 Can anyone suggest a solution and/or comment on the advantages/disadvantages of the above mentioned approach. |
Re: How to Copy Objects from One Module to Another? Karan_Cosmic - Mon Oct 05 12:12:39 EDT 2009 A lot depends on what tracebility links and link modules you are using with the requirements. On a recent project we did all the requirement capture work in small manageable modules and then used the Tools/Copy Objects function to create a single module incorporating all the objects from the surrogates. If it is purely a reporting issue, It is very easy with Rational Publishing Engine to report on requirements sourced from multiple modules. Hope this helps Mark |
Re: How to Copy Objects from One Module to Another? There are some technical reasons > While you can publish multiple docs as one like Mark says, it is obviously easier to just have to publish one module > As Mark says, links are also a consideration - linking between and into/outfrom 15 docs is a maintenance hassle. > You might also want to think about other maintenance aspects - if views, attributes etc are changing it becomes cumbersome to keep 15 docs in synch. > One thing that might drive splitting is the ability to partition out (e.g. for offline editing) - a single doc can only be taken by one user - but that mightn't be a consideration for you. > I'm not aware of sharing across multiple authors being a problem, but I'm not an expert there. However, more important might be the logical nature of the package of requirements, in terms of: 1. Version control - while 'baseline sets' allow the package of docs to be versioned together, if this is logically one thing that should always be versioned together then it may be more appropriate to treat as one. Sounds like this is how your sponsor looks at it. 2. Requirement integrity - splitting can more readily lead to duplication and conflicts across docs as each author tries to ensure their own spec is complete and makes sense. This can be further confused if the docs are moving separately through versions (as to which version of other specs a given one is up to date with). We found such problems and are now staying away from this for future projects. Kieran |
Re: How to Copy Objects from One Module to Another? |
Re: How to Copy Objects from One Module to Another? Hi All, I want to know that while copying the modules we can retain its Object ID's also. If yes then please guide. Thank :)
|
Re: How to Copy Objects from One Module to Another? AkkuKap - Mon Mar 07 00:38:39 EST 2016 Hi All, I want to know that while copying the modules we can retain its Object ID's also. If yes then please guide. Thank :)
If you are asking about the Copy objects function, the no, the copied objects in another module will have different Object Identifiers. But before copying objects you can create a new attribute and store the original Obj ID in that and then when copying remember to also copy the new attribute value to another module. If you are asking about copying whole modules, then yes, the Object Identifiers in the copy are the same as in the original. |
Re: How to Copy Objects from One Module to Another? PekkaMakinen - Mon Mar 07 03:27:46 EST 2016 If you are asking about the Copy objects function, the no, the copied objects in another module will have different Object Identifiers. But before copying objects you can create a new attribute and store the original Obj ID in that and then when copying remember to also copy the new attribute value to another module. If you are asking about copying whole modules, then yes, the Object Identifiers in the copy are the same as in the original. Yes m using Copy objects function... I have added a column (Absolute Number) and saved it as a view, and when trying to copy objects function there im not seeing Absolute Number Attribute type...Only Object Heading, short text, object text, paragraph style is there. Is there a way to add Absolute number or any column attrribute there??
|
Re: How to Copy Objects from One Module to Another? AkkuKap - Tue Mar 08 00:41:35 EST 2016 Yes m using Copy objects function... I have added a column (Absolute Number) and saved it as a view, and when trying to copy objects function there im not seeing Absolute Number Attribute type...Only Object Heading, short text, object text, paragraph style is there. Is there a way to add Absolute number or any column attrribute there??
You cannot copy Absolute Number, because it is a read-only attribute which DOORS manages. That is why you have to store the Object Identifier or Absolute Number to another attribute and copy that attribute to another module. DOORS has a tool to copy attribute values within module in Functions / Copy Attributes. So you can achieve what you need by: - Create a new Integer type attribute, e.g. OrigAbsNum or something - Use the Copy Attributes tool to copy Absolute Number values to OrigAbsNum (the attribute types have to be same, both are Integers) - Now you can use Copy Objects to copy objects to another module copying also the OrigAbsNum |
Re: How to Copy Objects from One Module to Another? PekkaMakinen - Tue Mar 08 01:03:28 EST 2016 You cannot copy Absolute Number, because it is a read-only attribute which DOORS manages. That is why you have to store the Object Identifier or Absolute Number to another attribute and copy that attribute to another module. DOORS has a tool to copy attribute values within module in Functions / Copy Attributes. So you can achieve what you need by: - Create a new Integer type attribute, e.g. OrigAbsNum or something - Use the Copy Attributes tool to copy Absolute Number values to OrigAbsNum (the attribute types have to be same, both are Integers) - Now you can use Copy Objects to copy objects to another module copying also the OrigAbsNum Thank you... Now I m able to copy object ID's but prefix is missing.
I m unable to copy object Identifier another attribute. No such attribute is shown in source attributes while copying attributes. |