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: Total NOOB needs direction
Topic Summary:
Created On: 5-Jun-2006 19:00
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.
 5-Jun-2006 19:00
User is offline View Users Profile Print this message


Marlin Wegner

Posts: 20
Joined: 2-Jun-2006

Our Doors admin resigned recently and I have been thrust into the role.   I have no real DOORS experience and am looking for pointers on what others have found to be the best tutorials or documentation for coming up to speed in a big hurry.   I guess I am looking for docs discussing the user end as well as administration and learning DXL, though the DXL I have looked at thus far seems pretty straightforward.    My background is in software development and am an avid coder.  

Thanks in advance for any and all suggestions.

Report this to a Moderator Report this to a Moderator
 5-Jun-2006 19:37
User is offline View Users Profile Print this message


Hazel Woodcock

Posts: 78
Joined: 6-May-2005

The most efficient way would be to go on the two day DOORS course followed by the three day dxl course from Telelogic.
That will sort out the mechanics of the tool. Depending on your role, you may also want some requirements management training.

If you can't get time and funding for the courses, I think there is a tutorial book that comes with DOORS, so run through that, and then work on the principle that just about anything you can do in the tool can be done with dxl and you are basically manipulating a database. Previous coding experience, the help files and the forums should get you going.

Hazel
Report this to a Moderator Report this to a Moderator
 6-Jun-2006 13:33
User is offline View Users Profile Print this message


David Rose

Posts: 80
Joined: 10-Oct-2003

I am sympathetic because when I was handed DOORS, I didn't know what a requirement was and I thought DOORS was what I had come through on my way to my desk. What I did, and I encourage others in my organization to do is to make a copy of a working database, call it your sandbox(select the Project, Right click and select Properties), and break it. Fix what you broke then break something else. This is how I learned the basics, and my inhouse customers breaking things helped me learn the more advanced functions.

-------------------------
David A. Rose TSgt USAF
NCOIC System Administration
Report this to a Moderator Report this to a Moderator
 6-Jun-2006 23:14
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

DOORS Folks would be better off installing the server on their own client machine and restoring a project archive it, and using that as their sandbox. I'm sure I'm not the only one to think he was in the sandbox when he started throwing things.... If you needed some serious User and Group issues, you could archive the user database (via DXL: string archive(string fileName, bool span) and string restoreUserlist(string fileName)) and restore that on your private client. Then restore the project archives and you'll be all set ...err... Well, except that you'll need to know the live 'Administrators' password to get full control over your own sandbox.

- Louie

Edited: 6-Jun-2006 at 23:19 by Louie Landale
Report this to a Moderator Report this to a Moderator
 7-Jun-2006 19:37
User is offline View Users Profile Print this message


cliff Bly

Posts: 58
Joined: 11-Apr-2003

1. Louie's suggestion is great - a local database for a sandbox is the best thing to play with. Think of something to do and find out how to do it.
2. The other suggestions are great too -- take a few Telelogic courses. Originally I even had funding to hire the Telelogic consultant for a day. We used it to ask dumb questions. You pick up things that you would not normally find see in any manual.
3. If possible, I would ask the former doors admin where he/she put their documentation and dxl. And go thru that.

-------------------------
Cliff Bly
Report this to a Moderator Report this to a Moderator
 8-Jun-2006 09:06
User is offline View Users Profile Print this message


Robert Swan

Posts: 86
Joined: 14-Apr-2005

some pointers:- Yes using a local database is the safest approach to learning, especially if you're going to be learning admin tasks, or trying to develop database wide dxl, triggers etc. Under DOORS 5 there was a training database provided with the installation, I don't know if it's still available for DOORS 7/8, our IT can't seem to find it. Remember that DOORS is a tool to achieve what you want, so like all good tasks be clear on the objectives before you start. Don't be afraid to crib/copy/modify the code examples from the dxl guide and DOORS sample scripts. Otherwise all the standard coding 'good practice' comments apply, (comments, layout, naming).
Report this to a Moderator Report this to a Moderator
 8-Jun-2006 09:29
User is offline View Users Profile Print this message


Hazel Woodcock

Posts: 78
Joined: 6-May-2005

quote:

Originally posted by: cliff Bly
We used it to ask dumb questions.

I think refering to Telelogic consultants as 'it', and making them ask dumb questions is cruel. :-)
Report this to a Moderator Report this to a Moderator
 8-Jun-2006 10:34
User is offline View Users Profile Print this message


Hubertus Grobbel

Posts: 58
Joined: 3-May-2005

Hi Marlin,

Keep in mind also a sophisticated Cofigurationmanagement or at least a version control of your environment esp. the DXL scripts (r Word Templates) !

We are using very successfully subversion. Easy to handle (like cvs) and may use http-port 80 for the server. You can setup either a server or a local db on your desktop PC if you are the only one to connect at a time.

If you ever come to the point having done some changes and later on you detect that a feature is no longer working you are lost, because you cannot follow your changes comfortably. SVN or any other versioncontrol-tool offers of course a strong diff feature.

Then you are able not only to work with a sandbox DB, but also a sandbox of your DXL-scripts :-)

Regards
Hubertus
Report this to a Moderator Report this to a Moderator
 26-Jun-2006 11:33
User is offline View Users Profile Print this message


Graham Stradling

Posts: 67
Joined: 19-Sep-2002

As we serve DOORS through citrix, only our admins have a local sandbox as no one has direct access to the DOORS client, but we provide a sandbox db through citrix for everyone to play with and usually we use this for testing future versions of DOORS too.

For DXL to be honest the language is simple to pick up if you've used c, perl or something similar, where it falls down is in learning the bits where it doesn't quite do what you expect, or ways round some of the problems such as string handling leaking memory, also learning about some of the hidden but useful perms. The DXL forum here is pretty good for answers.

For DXL control we're slowly moving all ours into Visual Safe Store - if you have MSDN licences you should have access to this. For editing DXL our guys use either Ultra Edit or Crimson Editor - both are pretty strong - I tend to use Ultra Edit for PERL, HTML and CSS editing too....

-------------------------
Graham Stradling,

Alcatel-Lucent.

Edited: 26-Jun-2006 at 11:34 by Graham Stradling
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.