DOORS Web Access or Desktop client?

we want to use DOORS on several clients at different places (no LAN conection).
But there is the stringent condition, that the clients have to comunicate with the database server only via internet. The second stringent condition is, that an installation of additional software (operating system and web browser, excluded) is not allowed.
Because of the above mentioned constraints, I think only "DOORS web access" is possible.

But what about the range of functions? Is there a difference in the range of funtions between "DOORS web access" and a client, installed on a computer (Fat client). If there are differences, it would be perfect if anybody can tell me these.
Best regard and thank you in advance
Peter
DC5G_Peter_Mutter - Thu Aug 18 11:52:54 EDT 2011

Re: DOORS Web Access or Desktop client?
SystemAdmin - Thu Aug 18 13:41:59 EDT 2011

Would Citrix client be included or not? DOORS on Citrix would then be one option.

With DWA you can:
  • create, modify and delete objects (dependig on your DWA license mode: review or edit)
  • modify attribute values
  • link objects
  • add discussions and comment on discussions
  • see views and baselines
  • search and filter
  • print
  • change your DOORS password (if allowed)

With DWA you can not:
  • create folders, modules, baselines or views
  • create attributes
  • manage users
  • manage linksets
  • export / import data
etc.

So, you would need at least one real DOORS client to do the administrative stuff.

Re: DOORS Web Access or Desktop client?
SystemAdmin - Mon Oct 17 10:15:01 EDT 2011

SystemAdmin - Thu Aug 18 13:41:59 EDT 2011
Would Citrix client be included or not? DOORS on Citrix would then be one option.

With DWA you can:

  • create, modify and delete objects (dependig on your DWA license mode: review or edit)
  • modify attribute values
  • link objects
  • add discussions and comment on discussions
  • see views and baselines
  • search and filter
  • print
  • change your DOORS password (if allowed)

With DWA you can not:
  • create folders, modules, baselines or views
  • create attributes
  • manage users
  • manage linksets
  • export / import data
etc.

So, you would need at least one real DOORS client to do the administrative stuff.

A couple of important notes of what one can NOT do with DWA:

1.) The built in DOORS CP System does NOT work with a DWA browser session\connection, the DOORS CP system MUST be used via the DOORS client.

2.) If your DOORS database is setup for the system username type of login design(vs. a Type in a Username & Type in a Password type database), then a DWA system will not work.

gsdguy...

ps. - if you have a "home-cooked" type of DOORS change system that does not function like the DOORS built in CP System which employs popup windows in the DOORS Client, then you may have a workaround. - eg. we have a proposed change column in a Module View that allows for this type of simplified change control vs. the full blown DOORS CP system with all of its pop up window magic.
And then a DOORS Admin\Project CP Manager process checklist which includes steps like lock out std users, baseline, run some DXL to push the changes into the Object Text, create a new blank proposed change column view at lates module revision level and continue with next round of proposed changes etc.
I suppose you could also employ the Discussions feature in a similar fashion since Discussions works with DWA.