I recently conducted an IBM DOORS migration webinar (see replay below). A lot of great questions came up during the Q&A, so I thought I’d share the most common ones here and provide some added detail.
Why will Jama only allow me to import one module at a time? What if we have 100+ modules?
We debated a long time about the extent of the migration. We have experience with large migrations that attempt to migrate all the data from one system to another. In those large migrations there is inevitably a significant amount of effort and resources necessary to configure, map, test and run the migration. Even then, it’s never going to be 100% perfect, especially considering the tools are different. As I’ve always said, we are not out to replace DOORS by being like DOORS. Jama is designed to be different, more open, collaborative. Module-based migration enables teams to pick and choose as necessary the modules they want. With larger projects, if it’s necessary to still migrate hundreds of modules at once, it will still take less time to migrate than what would be involved in a full migration. Based on our calculations, 100 modules would take a couple of hours. Of course, the size of the modules matter and will have an impact on this time.
Why did you choose the HTML export method?
This too was heavily debated. We evaluated all the export options. The DOORS archive was proprietary, and both Microsoft Word and Excel were missing key information. The ReqIF was the closest option but is designed as an exchange and not really as a migration. Not that it would do well as a migration but it’s an incredibly complex XML file that, while widely promoted, has fallen short during implementation (based of the research we’ve done). We also looked at a direct connection for pulling data, but this proved to also be complicated and once again forced organizations to involve administrators or IT to set up and migrate instead of the self-service option. The HTML provided the best combination of data, format, and ease of use.
What is the largest set of data you’ve imported?
The import is built around the standard import that has worked for large Word and Excel documents. We tested using data sets with 400 requirements and 100 relationships. This size of data typically takes a couple of minutes. The relationships take the longest to import. It’s worth noting that the import process can run in the background.
Most of the other question were covered in the webinar recording. DOORS has been around for a long time and even though we worked closely with several key customers to build this migration, we look forward to working with more customers to learn and adapt. Thanks to everyone who attended the webinar. For those of you who missed the webinar, you can watch it here