Hi All.
I've used DOORS at my previous companies but always as an end-user. I'm in more of an administrator role (while still being an end-user) now and want to help direct our small company down the right path.
I'm looking for recommendations on naming conventions for public Views, Page Layouts and Reports. I'm going to be the one creating most of these initial ones so I'd like to do it right.
dwj - Fri Jun 11 19:21:13 EDT 2010 |
|
Re: Naming conventions: views, page layouts, reports
SystemAdmin - Sat Jun 12 13:24:25 EDT 2010
Hello;
One pattern that I suggest you to use is about name of objects.
"<<three caracters for project>> - <<three caracters for subjcet>>-<<sequential>>"
About Views name, I use "view" + Name of the view.
|
|
Re: Naming conventions: views, page layouts, reports
llandale - Thu Jun 17 13:45:03 EDT 2010
You should distinguish the 'official' views/layouts/reports from the ones users will create on the fly. Folks who create their own should prefix the name with their doors user name; and whatever policy you have for the 'official' ones should have a first word that could not be mistaken for a user name. If user names are always lower case, then the official ones could always start with an upper case letter.
|
|
Re: Naming conventions: views, page layouts, reports
SystemAdmin - Fri Jun 18 02:33:21 EDT 2010
I prefix all views that were created as part of a module template with a number so that they always appear at the top of the view list. I refer to these as template views. Deliberate gaps in the numbers allows more template views to be added later on. These template views have special access rights set so that they can only be modified by members of a special group - this stops users fiddling with these views and ensures consistency as they are often used to generate common reports.
All users are trained to prefix their public and private views with a two\three letter abrreviation of their name.
See attached screen grab for an example.
Paul Miller
Attachments
attachment_14478364_ModViewListExample.jpg
|
|
Re: Naming conventions: views, page layouts, reports
dwj - Fri Jun 18 13:55:30 EDT 2010 SystemAdmin - Fri Jun 18 02:33:21 EDT 2010
I prefix all views that were created as part of a module template with a number so that they always appear at the top of the view list. I refer to these as template views. Deliberate gaps in the numbers allows more template views to be added later on. These template views have special access rights set so that they can only be modified by members of a special group - this stops users fiddling with these views and ensures consistency as they are often used to generate common reports.
All users are trained to prefix their public and private views with a two\three letter abrreviation of their name.
See attached screen grab for an example.
Paul Miller
|
|
