![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Experience with DOORS 7 Topic Summary: Created On: 17-Jul-2003 08:15 Status: Post and Reply |
Linear : Threading : Single : Branch |
|
![]() |
![]()
|
![]() Answer: Hello, We also use DOORS 7 SP1 build 70212 and DOORSnet 7.0. For DOORSnet we have a browse only license. However after the migration to DOORS 7 SP1, the anonymous login feature is no longer available to DOORSnet users due to a software glitch. We had been providing anonymous login for our users with DOORSnet 4 and 6. Telelogic support advised that "this problem with user 'anonymous' is a bug." The only work around is to log in with a user name and password in the way that the rest of the users do for DOORS! Regards, Mary | |
![]() |
|
Is there somebody out there working with DOORS 7 that can share experiences with us? How stable is 7 and how many bugs were discovered since migration from 5.2 or 6? Is it advisable/worth while to migrate to 7 when you are working under pressure to produce results? We need to migrate from 5.2 to at least 6: would you advise to go directly to 7?
I've seen the odes sung by users (e.g. Boeing), so spare me the marketing stuff. ------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
|
![]() |
|
Hello,
we are currently using DOORS 5.2 and made now some tests with DOORS 7.0. There are some good new feature (private views, OLE insertions in all text attributes, ...) and quite a lot of problems from DOORS 5.2 are fixed (advanced filters on columns,...). But we also noticed a problem that handicaps the work with DOORS 7.0. Often not the whole text of objects is visible. When viewing the object only the first rows are visible e.g. the first two rows are displayed, the rest is hidden. Sometimes not the whole text is visible although the cell is big enough. When double clicking in the cell, than the rest of the text is displayed. This behaviour is also shown, if the text is not very long (about three lines). There is no inidicator that not the whole text is shown. When douple clicking in the cell, then the rest text is shown either with a vertical scroll bar in the cell or the rest of the text is displayed overlapping to text of the next object. It is unclear, in which cases the text is truncated and in which not. I have also posted the problem in the forum "defect/issue tracking". Hanna Bock ext-hanna.bock@nokia.com Nokia Mobile Phones Ulm, Germany |
|
![]() |
|
![]() |
|
Hi -
I'm currently evaluating DOORS7 for my team and enjoy what I see so far. We migrated to 6 from 5.2 and are thinking of migrating to 7. When we migrated to 6 though, we suffered a performance hit with DOORS6 which I believe Telelogic recently admitted to us. From my tests so far, DOORS7 loads up modules about 20% faster, is more stable than 6 and 5.2, and has quicker compound filtering compared to 6. I haven't had the chance to play around with all the new features in 7 yet but my two cents are that these should of been all included in version 5.2. If you are thinking of upgrading from 5.2, then skip the pain and suffering and go to DOORS7 directly! Pete ------------------------- pete.kowalski(at)motorola.com Edited: 19-Aug-2003 at 19:07 by Pete Kowalski |
|
![]() |
|
![]() |
|
It is my understanding that if you are on DOORS 5.2 you MUST upgrade to DOORS 6.0 before upgrading to DOORS 7.0
|
|
![]() |
|
![]() |
|
Technically, you can't go from DOORS 5 to DOORS 7 in one step, but you could go from DOORS 5 to DOORS 6, and then immediately from DOORS 6 to DOORS 7 on the same day before users are allowed to log back in. I assume this is what Pete meant.
This thread details some issues on going from DOORS 5 to DOORS 6. You will need to run the "moduleMigrator" mentioned in the thread before going to DOORS 7. I recommend backing up the database filesystem, and converting the entire database at once. Archiving and restoring adds a whole set of problems that can be avoided. In the past, I have waited for the first service release to any major DOORS release before upgrading. ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
If you want to go from DOORS 5 to DOORS 7 you dont need to run the module migrator DXL.
You need to install one DOORS 6 "server install" on a machine and point to your DOORS 5 data. Login as Administrator and upgrade your data structure to DOORS 6 format You can then install DOORS 7 on your server and all of your client machines and do the quick data structure upgrade from DOORS 6 to DOORS 7 format by logging on as Administrator again This information is covered in a chapter in the "Installing and Setting up Guide" for DOORS 7. Michaels other advice about upgrading all of your data at once is the cleanest and simplest approach to take Mandy |
|
![]() |
|
![]() |
|
In attempting to go from 5.2 to 7, I ran into a big snag in the migration to V6. It just plain is not working. I followed the directions given, installing the DB server, then copying all my V5 data to the new location. Log in as the administrator, asks if you want to migrate, select the confirm, looks like it migrates (get the progress bar), appears to complete, the database views look correct. However, if I attempt to open any project or folder, I get an error message that states the item is not in the correct location. Have been working with tech support for 2 days, and have yet to resolve this issue. Presently attempting to convert to 6 via restore, but as was pointed out this is much less than ideal, not to mention very time consuming. Has anyone else seen or heard about this problem and does anyone have a solution.
TIA Frank |
|
![]() |
|
![]() |
|
Hi,
I'm currently creating an upgrade plan for an upgrade of an existing DOORS 5.2 DB to DOORS 7. What concerns me the most is Rich Text Format (RTF) related problems because I've experienced some interesting surprises in DOORS v6.0SR1 when it comes to RTF. It seems as though hidden RTF control information that was being supressed in DOORS v5.2 is now being processed in DOORS v6.0SR1 and of course v7.0 as well. So you somtimes end up with headings that have differant font's to those defiined under the Tools>Options>Display menu, paragraph's now appearing with hanging indents etc. The problem seems to be confined to content that originated from a MSWord to DOORS export - I suspect that during an export from MSWord, all of the RTF control word baggage is also exported and is now processed by v6.0SR1 and V7.0. Can anyone collaborate with this experience? In another thread, Michael Sutherland recommeded deleteing the Font Table attribute from each module to overcome some RTF problems - if Michael is reading or I invite a response from any others, are there any side-effects to deleting this font table, just exactly what does this Font table do? ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
Hi,
I have seen exactly the same problem going from 5.2 to 7.0 (via 6.1 SR1). Due to some past imports from Word, we had oddly placed underlines and boldings after migrating to 7.0. We ended up having to run the "remove all markup" utility in 5.2, then do the migration. Unfortunately, it removes ALL the markup, so if something was supposed to be underlined, it is no longer in 7.0. Fortunately, we didn't have much that needed to be fixed after that. Another related problem was that the default font does not map to the same font in 7.0 as it did in 5.2. Annoying. Alec |
|
![]() |
|
![]() |
|
Hi Paul,
My experience is that v6.0 and v7.0 of DOORS process the font information and bullet/indented paragraph information that is embedded in the RTF markup. Previous versions of DOORS ignored that markup. In general, we view it as an improvement to process that markup. If you want to remove the markup from objects, you can create a short DXL script that saves the text into an attribute without the markup, then save the text back into the object. The script should look something like this: Object o = current string s = o."Object Text" "" o."Object Text" = s This will also remove any graphics, bold, italics, etc. from the current object. As far as the font table goes, most of the time removing it will not cause any problems. We have found that the text sometimes appears as Greek text when we delete the font table. The rich text markup contains markup something like /f1 to designate Font #1, /f2 for Font #2, etc. All the font table does is tell DOORS which font is #1, and which is #2. If you don't have a font table, DOORS goes with the defaults (where one of the fonts is the greek character set). If you delete the font table and have greek text appear, you can run the script above to remove the markup specifying the greek font to get back to the DOORS default font. I hope this doesn't ramble on too long. Feel free to contact me if you want to converse more on this. Brian Azelborn |
|
![]() |
|
![]() |
|
Currently performing a trial upgrade from v5.2 to v6.0SR 1 to v7.0SR1 - has anyone else experienced a problem where view columns that have been set to Left & Right justified in v5.2 are appearing as left justified in v6.0SR1, even though the jutsification icon indicates that it should be Left & Right justification?? ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
We have migrated to DOORS 7.0 from 6.0 SP1.
Had some issues with setting up DOORSNet services due to some 6.0Sp1 services that were not removed by the 7.0 installer. Data migration went ok. Migration of our DXL scrips rised problems. We are using the dxlibf api and these scripts are not working anymore. Simple scripts worked ok. I haven't looked into the details yet. The product seems stable. We have performance problems with DOORSNet. Tried all known solutions without any convincing results. Annoying as DOORSNet is quite important to us. I have not yet installed 7.0 SP1 - but I haven't found anything on DOORSNet performance in the release notes. Regards Christian |
|
![]() |
|
![]() |
|
We have just upgraded to Doors 7, after extensive testing. Waited for the October Version of SP1 as it removed some of the print errors we were experiencing.
Upgrade went smoothly, and response has been positive so far. Appears to be more stable and slightly faster then Doors 6. We have a large amount of DXL and so far have had no issues. Overall we're really pleased with 7 SP1 (make sure that it's the version dated Oct 23rd not the first release.) Without a doubt worth the upgrade from 6 or moving straight to 7 from 5, you may notice some handling issues in DXL with richText, doors 6 added a new richTextWithOLE command - it's in the DXL reference manual. ------------------------- Graham Stradling, Alcatel-Lucent. |
|
![]() |
|
![]() |
|
Graham,
Our DOORs 7.0 SP1 is dated Oct 13, 2003. Are you saying that there is a newer SP1? Now, telelogic is releasing multiple SP1's with different dates!? |
|
![]() |
|
![]() |
|
There are 2 patches available for DOORS 7 SP1 - Patch 18059 and Patch 18449. Patch 18449 is a cumulative patch which includes the fixes done in patch 18059. Any mix of DOORS 7 SP1 clients, patched or unpatched can be run together with no problems although obviously we recommend that you upgrade to the latest patch when you can.
DOORS 7.0SP1 with no patches applied shows build no 70210 - this shows a date of 13th Oct. DOORS 7.0SP1 with patch 18059 applied shows build no 70212 DOORS 7.0SP1 with patch 18449 applied shows build no 70214. These patches are client only patches - there is no update required to the DDBS. The patches and associated readmes for the patches can be downloaded from the following location: http://support.telelogic.com/en/doors/download/patch/patch.cfm?vid=86 If you wish to receive information regarding release of patches then you should subscribe to DOORSNews@. All information regarding patches and full releases of DOORS/ERS is sent to users by this method. To subscribe goto the following location: http://support.telelogic.com/en/doors/mail/ Any further questions should be sent to your local customer support department. Mandy |
|
![]() |
|
![]() |
|
Douglas,
As Mandy notes above there have been several patches of Doors 7 SP1. Mandy recommends using the latest, I would go further and say that we found it essential as it cures some of the issues that we had noticed in the raw Doors 7 product. Mandy, Hows Tricks? long time since I've seen you. Graham ------------------------- Graham Stradling, Alcatel-Lucent. |
|
![]() |
|
![]() |
|
Hello,
We also use DOORS 7 SP1 build 70212 and DOORSnet 7.0. For DOORSnet we have a browse only license. However after the migration to DOORS 7 SP1, the anonymous login feature is no longer available to DOORSnet users due to a software glitch. We had been providing anonymous login for our users with DOORSnet 4 and 6. Telelogic support advised that "this problem with user 'anonymous' is a bug." The only work around is to log in with a user name and password in the way that the rest of the users do for DOORS! Regards, Mary |
|
![]() |
|
![]() |
|
As Mandy previously pointed out, the DOORS 7.x manual says: "You do not need to load and save your data as was necessary to complete the migration to DOORS 6.0 from DOORS 5.x. The migration to DOORS 7.0 SP1 from DOORS 6.0 SR1 completes the migration process."
Have anyone found this to be true, or not true? Has anyone NOT run the "moduleMigrator.dxl" after the v5.x to v6.x step? ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
Michael,
We did not run this script, but module opening times afterwards were terrible. (We passed from 5.2, via 6, directly to 7.0 SP1). Then I dived into the forum, and saw that there was an issue of initialising the modules by opening and saving. After doing this to all modules, the opening times were better compared to 5.2. Pieter ------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
|
![]() |
|
Pieter,
Opening and saving is all the "moduleMigrator.dxl" actually does. Based on your information, it seems that the modules still need to be opened and saved, but the step can be delayed until after the D6.x to D7.x conversion. ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
Telelogic DOORS
» Administration
»
Experience with DOORS 7
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.