![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DOORS Wish List Topic Summary: Things that DOORS should JUST DO out of the box! Created On: 15-Jun-2007 09:57 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I'm sure this thread has been done before, but here we go, just in case the IBM boys want some food for thought.
------------------------- Andrew Tagg Thales Air Systems, Melbourne Australia. andrew.tagg@thalesatm.com |
|
![]() |
|
![]() |
|
My starter for 10: Cascading attributes/views: Set up an attribute/view definition for a folder, all modules in that folder inherit the attributes/views.
------------------------- Andrew Tagg Thales Air Systems, Melbourne Australia. andrew.tagg@thalesatm.com |
|
![]() |
|
![]() |
|
G'day mate, from Old South Wales. Good initiative! What I'd like to see from DOORS? To start, I'd like to be able to set up linksets in modules without having to have exclusive access. There are many other items I'd like to add to this, and will visit this thread daily if I can to soak up existing wish lists and respond to others. I'll be back - this is important. ------------------------- ----------------------- Matthew Thomas Panasonic Manufacturing UK Ltd Edited: 18-Jun-2007 at 13:44 by Matthew Thomas |
|
![]() |
|
![]() |
|
I think this notion would make sense if each module would 'inherit' the attr defs and types and could not modify them. Each folder could then have types and defs defined which applied to all modules in all sub-folders. If a folder defined a def or type that a parent folder also defined, then [1] the sub-folder takes precedence [2] You cannot do that; which means a folder cannot create a def-type if any sub-folder or any parent folder already has it defined.
There would need to be a mechanism for a folder to 'steal' a def-type from sub-folder. There remains the problem of changing the type of a attribute at the folder level. There remains the problem when a def is removed from a folder as this will cause all the data in all the modules to be lost. - Louie |
|
![]() |
|
![]() |
|
Shareable edit! In short, it should work...e.g. new objects inserted should be lockable by default.
------------------------- Pekka.Makinen@softqa.fi SoftQA Oy -http://www.softqa.fi/ Edited: 18-Jun-2007 at 19:28 by Pekka Mäkinen |
|
![]() |
|
![]() |
|
That would make, by default, every object its own section. In order to make any change you'd have to lock each object, then unlock and save it aftwards.
But you could change the meaning of 'shared' which means when you go to edit an object, you automatically read the object from the server and it remains locked for x minutes after you make a change to it (this lets you make several changes without having to wait for it to reload). You don't have to actually lock and unlock. There would be no 'shared sections'. - Louie |
|
![]() |
|
![]() |
|
Probably never happen, but I would like to see lockable sections and access permissions as completely separate things. It doesn't make sense (to the user) that an object with specific access permissions is lockable, but an object with inherited access permissions isn't.
------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Access rights for views.
Why can't the default access rights for a new view be 'inherit from parent' in all cases. The number of times users have created new views and everyone else finds they cannot change it since the full access rights are only assigned to the view creator. I know this only happens generally when creating a new view starting with the standard view but that's where most users start to create a new view. It's even more annoying if the user has left, requiring the assistance of the administrator. ------------------------- - Martin |
|
![]() |
|
![]() |
|
To be fair to Telelogic, what you describe is the way it used to be.
But customers complained that users were creating views and their view list was becoming cluttered with dozens of views they didn't want to see. Hence it was changed so that new views created from the standard view are created private by default. Views created from other views have, by default, the same permissions as the original view. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Hi,
When the DOORS Explorer folder and file type presentation was delivered in DOORS version 5, it was a big leap from previous versions ( I go back as far as version 3, and I know that there are some on this forum that go back to version 1). However, the folder file type view is no longer adequate. DOORS needs an interactive GUI that displays all modules and link relationships within a project as a logical type view. Creating all aspects of a project schema should be possible from such a view. It would be a bit like a MS PowerPoint presentation where you start with a blank sheet and then instantiate symbols which represent formal\descritive modules. Adding interconnecting lines between modules would represent independent linksets (no more link modules please!). Double clicking on symbols would allow you to fill out schema properties like views, attributes, access rights, triggers etc etc. Just like views in a module, each user should be able to have their own graphical view of the project and it's module structure as well as access to common views - access rights would determine what GUI elements they can modify. Users have had to resort to creating all manner of DXL scripts and frameworks to provide a more global view and management of a projects schema, but lets face it, whilst developing robust & resilient DXL might be a bit of fun (not always!) it is also a very costly overhead excercise that a project\company must pay for. Particularly when it has to be fully re-qualified at each major version release of DOORS. I thought that the DOORS XT product was going to be the new generation version of DOORS that would have such features out-of-the-box but I believe that this product is in some state of development suspension for some reason. ------------------------- 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 |
|
![]() |
|
![]() |
|
WISH: Being able to undo a "Setup Module for Shareable Edit" operation from the menu.
I asked about this, and the response is some DXL to reset the "Inherit from Parent (access rights)" option. WISH: shareable edit was not resting on the access rights in this way - use them for another purpose and it gets messy. ------------------------- ----------------------- Matthew Thomas Panasonic Manufacturing UK Ltd |
|
![]() |
|
![]() |
|
quote: True but it would be nice if there was such a command through DXL to create objects that are immediately shared. I have modules that are used to track things like pricing which don't have a lot of objects and all need to be shared. And I have to give our analysts admin level privileges so they can create objects and set them to share. If nothing else, that needs to be changed. You shouldn't need admin level privileges to set an object to share. ------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
Telelogic DOORS
» General Discussion
»
DOORS Wish List
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.