The initial setup is not very simple. 

The initial setup was difficult. My organization did the deployment. Online licensing includes a lot of processes that I am not aware of. Once the organization installed the solution, I requested an additional license. It is difficult to use the tool. The solution is deployed on my laptop. I have an internal link to access the product and GUI.

I haven't participated in the installation phase.

I don't know because our IT department sets up the program.

The setup was not easy.

The initial setup is simple and takes only half an hour to complete. For deployment, you need to click, provide some inputs, and execute fairly simple actions.

I rate the initial setup a seven to eight out of ten, where one is difficult and ten is easy.

You can create a whole server inside the project. It's easy to set up. 

I wasn't directly involved with the deployment and do not know how long it takes. 

It was quite complicated, luckily for me I learned from the best and was able to continue to network and continue learning from the brightest minds in the industry. Combining this with my own experiences and the many clients I have worked with have equated to superb amount of real like challenged faced and overcome.

The initial setup was straightforward.

We have our computer management who instructed me to download IBM Rational DOORS.

It was simple to download and get started.

Setting up DOORS is easy, and I can handle it by myself. The initial installation takes around an hour, but the total deployment depends on your environment. However, you can handle it with a remote install, and installing the client itself takes only a few minutes. 

We use predefined templates, so the setup for us was more or less straightforward.

It was straightforward as it came pre-installed on my company machine.

My initial setup and integration were more complex than I was expecting.

DOORS is a proprietary database, and it is a simple install of a server and a client, and you are off and running. Very straightforward in the Rich Client environment. It only begins to get complex if you begin setting up integrations using the IBM CLM environment.

I wasn't involved in that.

We worked together with one of our dealers in order to handle the initial implementation. We were handling a complex environment in order to fit our requirements. Due to our needs, the implementation and initial setup was more complex than straightforward.

Deployment took us a couple of months, including having time to review everything.

We have our own internal team that handles ongoing maintenance.

Rational DOORS provides no guidance on best-practices for the product, or advice in requirements management using the product. So an initial setup is best done by someone with a deep understanding of both requirements management and the tool.

The initial setup was straightforward, thanks to the robust help files that IBM has maintained as a library that is accessible both inside the tool (Help button) and via the internet (on the IBM site). Aside from that, technical support was available as needed - even to the extent that phone support can be provided.

The initial setup is easy. The deployment usually takes a couple of weeks.  

In the deployment process, there are between three to seven people involved depending on the project.  

It is not simple to answer how many people are involved in the maintenance because we have decided to divide the way we look at supporting clients and products into different levels. Our support services have three levels now because all these different levels need different information about the tool in-depth to be able to use it properly for their purposes. If we do not provide them the information about the tool in-depth, we would not be providing proper support. In general, we have about six people providing the maintenance services.  

The setup is very simple. It licenses, and runs the two executables, server and clent, and you are done.

Initial setup of the software is straight forward. Just follow the steps described in the IBM site. The complexity starts on the use case of the business that wants to employ DOORS. Different businesses have different use cases and different users have different needs. At that point an expert is needed to design the Database and the relationships in that way that can be maintainable for the future and provide an ease of use. DXL tools and customisations always add an extra level of complexity.

It's simple to setup the complete environment. Linking with external applications is also friendly. We are using Rational Directory Server for our user management and Rational Change for change management, so the integration configuration was somewhat easy without much trouble.

In most cases with clients, initial set-up involved importing a document corpus into Rational DOORS, then verifying that it was imported successfully. Regardless of the format of the original documents, I have not had trouble configuring documents then importing them into Rational DOORS, which supports imports of CSV, ReqIF, rich and plain text, FrameMaker files, and several others. Rational DOORS 9.6 also supports importing documents/spreadsheets to update current data.

Installation is straightforward. Project start-up can take some time if an organization or project does not have an institutionalized process around which they have tailored DOORS usage. Also, if tailoring requires DXL scripting, the organization or project must have the expertise available. Many projects/organizations stay away from customization for that reason. Using Rational DOORS integrations with other tools can add another layer of complexity.

The initial setup is straightforward.

From my point of view, I didn't do the initial setup. However, from the moment I started using it, I found it to be straightforward. 

I'm not sure how long deployment takes.

It installed really well, and it has a straightforward license key operation.

The initial setup was straightforward.

I did not manage the setup of the program, but I believe it is quite straightforward.

With a qualified DOORS Deployment Professional, the initial setup is relatively straightforward. They should be able to design and build a schema to support your process. templates can be created to make project setup relatively straightforward.

I managed to install it without any serious or issues, so it was quite okay. I had a lot of exceptions at different moments, but I managed to find solutions on the web. 

The initial setup was complex.

It depends on the organizations size and needs.

The initial setup is complex, although it is linked to the complexity of the project.

If you have something very simple then the setup will be straightforward but if you have something complex then it will be more difficult. For example, if you are designing a launcher to send satellites into space then you want to have enough information about it before you start the system. These systems are very expensive to develop, so you want to demonstrate that it will be of good quality and be able to handle the operations required to achieve the goals of the project.

It takes between one week and one month to deploy, depending on the requirements.

The initial setup was easy. It's easy to provide access to users.

It was very straightforward.