![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DOORS Implementation Team - How Necessary is DXL Knowledge? Topic Summary: Created On: 6-Mar-2006 20:27 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We are in the pilot mode of a DOORS implementation. For those of you who are further along in your implementation, how necessary is it to have a permanent member of the team with knowledge of DXL and how strong should that knowledge be? Ours is a small implementation, and we plan to have the system as vanilla as possible.
Thanks for your insight, |
|
![]() |
|
![]() |
|
In my experience you do not usually need DXL scripts or experience in implementing DOORS.
With a good knowledge of attributes, views and tracebility you can build up your own DOORS implementation. If after that you really have some specific needs for customization, some consultant can build up the needed scripts for you on a case-by-case basis. Note also that DOORS is supplied out-of-the-box with a pleanty of example DXL scripts, most of which are quite useful. Shame, that they are not documented anywhere, e.g. the contents of DXL Library. ------------------------- Pekka.Makinen@softqa.fi SoftQA Oy -http://www.softqa.fi/ |
|
![]() |
|
![]() |
|
If you have a defined business process for requirements management, and want to map DOORS to it then some DXL may be useful. As stated above a good consultant should be able to provide what you need if you define your process.
DXL is quite easy to pick up if you are used to 'c' or similar languages, provided you don't want to get into the clever bits, (triggers, graphics, other tool interfacing).
As people get used to DOORS you will probably find the first need is for some layout dxl, and then for some simple utilities. In my case these were things like counting visible objects, clearing all entries of an attribute, finding specific text strings and enboldening them. You will only identify these as you use the tool. Like any software the biggest challenge is to make them maintenance free.
In short I agree you don't have to have it, but it can make life easier.
|
|
![]() |
|
![]() |
|
You can certainly get going and be usefull without any DXL scripting. Folks can manage their requirements without scripts. But the more complicated your requirements and demands on DOORS the more you will need scripting. For example there is no mechanism to report "the number of requirements" other than via DXL (Ok, there is if you want to do a bunch of manual filtering and jot down results on paper). As your policies mature, such as "Requirements must be justified by parent requirements" so will your needs for DXL scripting, in this case following links and insuring that requirements are properly connected ..err.. appear to be properly connected. As folks get into it they will start asking for then demanding utilities that make their work easier; such as some script that presents their requirements alongside all their children so they can do their peer reviews.
So I'd stay step off the cliff and let realities and demands dictate what kind of DXL support you provide over time. As for learning it ... take the course then start modifying existing DXL. If you get stuck you can always post here as there are plenty of ego-maniacs (like myself) who want to show-off with their clever and "elegant" DXL solutions. Solutions to real and imagined needs... but I degress ... ![]() - Louie |
|
![]() |
|
![]() |
|
While you don't have to have the expertise, I think the reality can be seen here in these forums look at the number of threads in each area and the DXL one wins by a long stroke (1000+ threads versus 300+ for general discussion). You will end up in the scenario where there are things that are just much more easily done by dxl.
Louie's suggested course of action is a good call - it's how a lot of people start - take the courses, play with it and ask others for help when you get stuck, in the long run you'll find all sorts of useful bits and pieces that you can do more efficiently. ------------------------- Graham Stradling, Alcatel-Lucent. |
|
![]() |
|
![]() |
|
Look at DOORS as this: it is a shrink wrap product.
It doesn't come with some friendly user features that it should so thus you must use DXL to extend the functionality. Anyone developer who has a C or C++ background should be able to pick up DXL with patience, practice and good anger-management skills. ------------------------- pete.kowalski(at)motorola.com |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.