IBM just released the latest version of their Collaborative Lifecycle Management (CLM) suite, which includes DOORS Next Generation (DNG), Rational Team Concert (RTC) and Rational Quality Manager (RQM). This is a huge update and I think it lays the foundation for the future direction of the tool.
CLM 6.0 was marked by configuration management (CM) appearing for DNG and RQM, however there were limitations on opting-in to CM. Many of those limitations are now removed, and instead of focusing solely on CM, the developers of all the applications were able to focus on adding new features and refining existing ones.
I’m not kidding when I say the changelist is huge, so grab yourself some coffee and dig in for all of these new features, which are available right now from Jazz.net! Here are some of the new features and changes I find most notable.
DOORS Next Generation
- Link Validity – Instead of just monitoring for suspect links, users can be more active and tell the tool whether links are valid. I’m still wrapping my head around this concept and how it will be used, but I do think the theory behind it is sound. If users can mark a link as not valid before having a change process to review and remove it, then it could make it easier for owners on the other end of the link to understand that there are issues before they arrive.
- Link By Attribute – Makes it easy to create bulk links! I believe there will still be confusion due to the linking to a module/base artifact differences but people like me will know how to train the end users.
- Link Constraints – Makes it so that artifacts of one type can only link to certain other artifacts. This is another great thing to have and brings DNG further ahead of DOORS 9. The theory behind OSLC and Jazz is that you can link to anything at anytime, but this violates a core principle of requirements management. I’m glad the DNG team put the user experience ahead of the theoretical foundations of their toolset.
- Round Trip CSV – Another finally! We’ve been wanting this since 2012! I also like how it’s just integrated with the import requirement screen. Very nice, though as always there are limitations. A quick one I saw was the inability to change an artifact’s type via CSV. Makes sense on one level, but on another level, I can change an artifact’s type via the DNG GUI. But that’s just a nit-pick. This one change will make automations much easier to implement, and unlike DOORS 9, you can even delete requirements via CSV!
- Tie changes to RTC work items – The hooks to allowing DNG to completely manage change from RTC are finally here. Can’t wait to try this out! This will make it so that all changes to production requirements must go through a work item. The DOORS 9 to RTC integration has had this for a while and it’s great that DNG is now getting it too.
- Dashboard Widgets Are Now CM Aware – Better late than never. This is one of the reasons I advised my clients to hold off on implementing CM in their DNG 6.0 environments.
- Improved resolutions of CM delivery conflicts of Modules (Module Merge) – Yet another vital improvement.
- Version-aware Jazz Reporting Service – Again, the ability to report on DNG streams is a requirement, and another reason I suggestion people hold off before. Now I don’t have as much of a reason.
- Filter by Artifact ID! – I’ve needed this for so long.
- DOORS 9 to DNG Migration Package – It’s easier to get data from DOORS 9 to DNG, and this is great for testing all of the improvements made in DNG. There are still limitations in artifact mapping from DOORS 9 to DNG that people migrating ought to be aware of. Still, it’s nice to see significant improvement in this area as pure ReqIF alone had could have its own issues.
- Right-click for the action (pencil) Menu – You can hide the pencil column and do right-click only if you want, or you can have both. A much needed UX enhancement.
See more information about what’s new in DOORS Next Generation 6.0.1.
Rational Quality Manager
- Reconcile Requirements Progress Indicator – Now when users go to reconcile their requirements from DNG, they can see a progress bar. Great for large sets of requirements in test plans.
- Improved pasting of images in manual test scripts – This leads to better tool usability and better exports from RPE.
- Editable Environments in TCERs – Execution Records can now have their environments changed. I can’t think of a great use case for this but I’m sure it’s there because someone asked.
- Ability to specify that TCERs can’t be run in certain cases – can’t be run without being attached to a test plan, iteration, or environment. This is great for managers who want to enact good processes without having to control everything in the tool themselves.
- Some awesome new dashboard widgets – These are great!
- Link Validity is implemented in RQM as well!
- New artifacts available in Jazz Reporting Service – You can now report on Test Environment, Test Data, and Keywords. You can also see the category hierarchy in JRS.
- Table view filtering improvements – Really too many to list. One of my favorites is “show me which test cases don’t have test scripts”.
- RQM can import requirements from DNG Project Areas with CM enabled – Again, this is absolutely necessary before any companies that use both RQM and DNG can opt-in to CM.
See more information about what’s new in Rational Quality Manager 6.0.1.
Rational Team Concert
- My Stuff Menu Item – See all of your work items across all projects with a single click.
- Query by typing commands – These images do a good job of explaining:
I really like the -> notation for “Parent link”
- Bulk editing of Work Item fields in Quick Planner, My Stuff screens
- CM Linking from Work Items Is Now Available
- Local changes preserved when reloading an out of sync project – Anything that lets me preserve changes if I click the wrong thing is always fine with me!
- Online code review – I really like this one!
- New methods to set direction of flow targets – Users can do this from RTC, VS, and the command-line. In the GUIs, its done via the “Change Flow…” button. In the command line it’s done via the set flowtarget command.
- Restrict flows to components in a stream – Admins can set rules that component X must be delivered to by stream Y and only stream Y. Very useful!
- Custom attributes on more artifact types – file versions, baselines, snapshots, streams, and now components allow for custom attributes.
- Lots of git integration improvements
- Improved Jenkins plugin and authentication
- Build reports GUI improvements all over the place
- RTC 6.0.1 supports Microsoft Visual Studio 2015
- Delete multiple remote workspaces at once
- Pattern-based component search
- Work Item Auto Subscribe for Commenters
See more information about what’s new in Rational Team Concert 6.0.1.
Jazz Reporting Service
- Improved Add Calculated Column Dialog Boxes
- Time range support with drill-down when counting artifacts
- Dynamic filtering is made more prominent in the GUI
- Custom Graph Colors – FINALLY!
- Historical Trend Reporting for the Data Warehouse
- Set a goal line
See more information about what’s new in the Jazz Report Builder (JRS), Data Collection Component (DCC), and Lifecycle Query Editor (LQE) applications.
- Online migration from one Jazz Server to Another – May make it easier to set up sandbox servers? I need to dive into this one.
- WebSphere Liberty replaces Apache Tomcat – I’m really not sure what to think about this one. The good news is that Tomcat is still supported and can still be used.
- Team Concert now supports integrated Windows Authentication
IBM DOORS Next Generation, Rational Quality Manager, and Rational Team Concert 5.0.2 were just released.
You can read the release notes on Jazz.net. Notable in DNG are greatly enhanced file management and much needed updates to managing views.
The Jazz Reporting Service is also promoted to more of a public view, and my guess is that in 6.0 it will be fully baked in. It looks very promising.
One of the coolest pieces of DOORS-related tech I saw at Innovate 2014 was Author XG by GEBS. GEBS developed the early versions of Rational Publishing Engine and really know their stuff when it comes to Document Generation and Reporting via DOORS. Author XG is basically RPE for non-technical people. Awesome stuff.
Learn About Document Generation
If you want to see Author XG and even learn more about RPE, GEBS is hosting a few FREE webinars over the coming months.
The first Webinar is Tuesday July 29th 2014
9:00 AM NA Eastern Time (UTC – 4)
9:00 AM NA Pacific Time (UTC – 7)
Do you want to know more about document generation? Are you curious to learn how automated publishing might benefit your organization? Then why not join us for our introductory tour of document generation technologies and discover the tools, methods and solutions that can enhance both your bottom line and delivery capability. (Note – this introductory webinar is industry/tool agnostic, and not specific to IBM Rational Publishing Engine).
The webinar will last approximately 1 hour with a question and answer session. Registration and attendance is free.
Presenter: Alex Feseto of GEBS
Learn about using IBM Rational Publishing Engine and other tools
This is the first webinar in an enlightenment series on document generation, below you can find the schedule for the next episodes:
Tuesday August 12th – Getting Started With Rational Publishing Engine – Register now
Thursday September 4th – Introducing Author XG: the future of document generation
September TBA – Introducing Reporting Central: the modular CMS for RPE and Author XG
October TBA – Advanced hints, tips & tricks for RPE and friends
October TBA – End to end document generation with RPE, Author XG, Reporting Central and Web Publisher
October TBA – Generating documents across the SDLC
Anyone who has downloaded the milestone release of Rational Requirements Composer 5.0 may have noticed that in the help documentation, Rational Requirements Composer does not have its own help section. DOORS Next Generation, however, does.
When version 5.0 of the Jazz suite gets released in June, RRC will be no more. The name of Jazz’s requirements management tool will henceforth be Rational DOORS Next Generation.
I suspected this change coming for a while. As RRC gained modules, most places I’ve seen latched onto modules, even if they had never used DOORS 9. Having DOORS and RDNG still presents the “which tool should I use” problem to IBM, but at least IBM has narrowed the list down from three tools to two tools.
With the upcoming Requirements Configuration Management capabilities in RDNG (open beta starting around June and final release coming in Q4), I expect RDNG’s marketshare to grow exponentially, especially since existing DOORS 9 users can leverage their licenses for RDNG.
In the meantime, I can now speak about RDNG to everyone we do business, and that will lead to less confusion to my customers and even within IBM. June 1 can’t get here soon enough.
From now until the end of 2013, registering on IBM’s JazzHub allows free hosting of source code for public and private projects.
This was just announced so I haven’t been able to dive in head first on this, but JazzHub seems to be an implementation of Rational Team Concert in the cloud that has been set up to import code from github, who also allows free project hosting for open source projects.
There is a small catch here. Your private projects are hosted at no cost to you until January 2015, where fees start to apply. At that time you can either migrate your projects elsewhere, convert them to open source, or decide to pay.
While we here at Baselines Incorporated have always been experts in requirements management, we learned Rational Team Concert when we saw that Jazz was the future platform for the Rational DOORS brand. While Rational Requirements Composer/DOORS Next Generation are not currently at feature parity with DOORS Classic, going towards Jazz allows for a much better backend architecture than the current DOORS Classic settings, which will eventually allow for things like true version control of requirements! (This will be the killer feature that solidifies DOORS Next Gen’s place in the market as the new requirements leader. You heard it here first.)
Git/Github is great for version control. Aside from a bit of a learning curve because of a new paradigm of source code control, I don’t personally have many complaints about it. It’s easy to use when you know how to use it. The simultaneous problem and benefit with git in my opinion is that other than the command line, there’s no standard client to use.
RTC allows use of a command line, explorer shell extensions in Windows, Visual Studio, and Eclipse. Eclipse has a fully configured RTC download and RTC is a plug-in on the Visual Studio side. There are git plugins for Eclipse too (I’m not sure about VS). But RTC was built with Eclipse in mind and so there is just one RTC plug-in for Eclipse.
In any case, if you’ve been wanting to try out RTC for some application ideas you’ve had, there’s really not a lot of reason not to try JazzHub right now.
Feel free to contact us for more information regarding DOORS, DOORS Next Generation, Rational Team Concert and Rational Quality Manager.
I wonder if my last post had anything to do with this.
What a horrible title for this technote. The “Table” caption comes in as a HEADING, not a caption. And this problem only exists in exports from DOORS that were brought in from MS Word and that is also not mentioned. The word DOORS isn’t even in the title, which tells me that most RPE customers are using DOORS.
While the information in the technote is valuable, I still can find no actual reason any long time user of DOORS would want invisible table headers to have a heading of “Table” on tables exported to DOORS from Word documents. Unless every DOORS table will always have this heading regardless of where it is created, this “feature” needs to be removed in the next release.
Friday was not a fun day for me. I had to troubleshoot a bizarre issue with Rational Publishing Engine. Anyone who has worked with RPE knows that while it’s a very good tool, troubleshooting document errors is a long process that can absolutely test every ounce of patience you have.
The issue in this particular case was that in certain modules, an extra heading would be added to a table. This did not happen in every module, which seems to point to not being an issue with the RPE template (a .dta file) but rather with the data of the table itself. The problem was that the tables appeared to be identical!
Reproducing The Problem
I’ve been able to replicate the problem in Word 2010, DOORS 126.96.36.199 and DOORS 9.4, and RPE 188.8.131.52. Here’s what to do.
Create a new Word Document. Put a table in it. Here’s what I did. You can click the number next to each photo for a fullsize view.
Export from Word to DOORS
Okay, everything so far looks good. Let’s export with RPE. I’m going to use the doorsData.dta file that comes with RPE just for demonstration purposes.
Let’s do an export and look at our output.
The red arrow shows an erroneous heading! What’s going on here? I didn’t put that there. Those italicized Table captions comes after each table, and that’s controlled by the .dta file.
Troubleshooting The Problem
I could write lots of paragraphs here boring you with everything I tried. I’ll tell you this to speed things up: I tried multiple .dta files and multiple DOORS modules and the results appeared consistent between modules. What I mean is, one module would consistently output table headings and one module would consistently not output table headings, regardless of the .dta file used to export. Strange indeed. I’d look at random table cells in each table and they all looked identical.
I know what might work! Inserting a DOORS Table into a module that was behaving like this. So that’s next.
Now we export again and check the results.
Ok, so it’s not a module-by-module basis, it’s a table-by-table basis on which this error occurs! I’m stumped. The only thing I know for sure here is that it is not a .dta problem. It appears that tables captured from Word documents behave this way, while tables created in DOORS don’t.
I talk this problem over with a colleague and she tells me that there are other modules that are exhibiting this behavior. She did a little research and ultimately determined the problem.
DOORS Tables (Suck)
If you are a religious person, and you use DOORS, you must believe that DOORS Tables are a tool of the devil. When I train people in DOORS, I explain that having tables in modules is not just a DOORS issue, it’s a requirements management issue. Tables can make it easy to digest information, but they can also obscufate requirements. Is each cell a requirement? Each row? A combination of rows? The entire table? Since the purpose of requirements management is to make requirements clearer, tables go against the very nature of effective requirements.
Over a decade ago, Telelogic had a problem. DOORS did not support tables. Their clients were demanding table support, so some designer came up with the idea to “hack” DOORS objects and make tables consist of these hacked DOORS objects. Each DOORS table has an “invisible” table header object, and each row has an invisible row object. Why did I put the first “invisible” in quotes? Well, because you actually can see these invisible DOORS table header objects, under the correct circumstances. How?
Click View->Show->Table Cells. It’ll likely be checked when you see it in the menu. Clicking it will uncheck this option.
Ok, now that you’ve done that, you’ll see objects that appear to have a Heading of > > Table. Like so:
So now that we can see these table headers, I can now get to the properties of the invisible table headers. TBLISSUE-6 represents the table where the problem is showing up. I right-click the object and choose Properties and am presented with this!
This table header object has an Object Heading of Table! Where did it come from? The Microsoft Word export process now sets the Object Heading of each invisible DOORS Table Header object as “Table”, thus putting a bug into every single RPE template that deals with DOORS data!
The only way I can think of to fix this, for sure, 100% of the time, without affecting data in any of your modules is to remove this Object Heading from each DOORS table exported from Word. What a pain! But let’s do that and see what happens.
I wasted almost an entire work day trying to troubleshoot and solve this issue. I’m not very happy about this, and am posting here in order to help others who may encounter the same issue. This fix was not at all obvious and even the problem occurs sporadically.
I read the release notes for each DOORS release I implement and I either completely missed this change to DOORS or more likely, this change was not documented. It’s also angering, because as a user, if I want to put Object Headings on my invisible Table Headers then I will do so. Also, the latest RPE sample files do not reflect this change, as demonstrated, so in my opinion, the DOORS developers introduced a bug into RPE!
Even more frustrating is that I’ve entered PMRs and RFEs for DOORS behavior that I believe are outright bugs and they get ignored outright or I have to justify changing them because of how much they cost my clients. Yet stuff like this happens with no warning and my clients eat the cost of me and others trying to figure out what’s happened here.
Friday I announced on this site that Baselines Incorporated is now an authorized reseller of IBM Rational Software. I stated that I would ensure that the content of this site along with my opinions would not be affected by us selling IBM Rational DOORS and Rational Publishing Engine and the like. The bad news is that this bug exists at all, but the good news, for me anyway, is that I got to prove that I am a man of my word.
I sincerely hope this article helps people save some time in the future and that IBM fixes this issue in a soon-to-be-released future release. In the mean time, a PMR/SR has been entered and I am engaging my IBM representatives about this horrible change.
I’m excited to announce that Baselines Incorporated now has the ability to sell IBM Rational software, including IBM Rational DOORS, IBM Rational Team Concert, IBM Rational Rhapsody, and IBM Rational Publishing Engine, IBM Rational Quality Manager, to name a few. This has been a few months in the making and I want to thank everyone involved for helping to make this happen.
I will still give my same opinions and thoughts on where IBM should go with their software and hopefully my status as a business partner and reseller will go towards my thoughts being heard and implemented.
This change won’t affect the content of this site. The exciting part is that if Baselines has an existing relationship with your company, then this is an extra service we can offer, as you can purchase IBM Rational DOORS from us. We can generate quotes and there are different payment and financing options that can be chosen as well.
Baselines Incorporated, The Requirements Management Experts, are experts in IBM Rational DOORS, DOORS DXL scripting, Rational Publishing Engine and Rational Team Concert. We make it our business to understand our clients’ requirements management, change management process and workflow, and validation and verification needs and fulfill their expectations. If it involves requirements, it involves our knowledge.
If you have any questions about any of our services, don’t hesitate to contact us!
I received the following email from Nancy Rundlet at IBM.
IBM is now offering both Rhapsody Enlightenment and DOORS Enlightenment every Friday, alternating between the two products. NOTICE that there are 3 new DOORS Enlightenment topics that have been added in November and December as well as links to the recordings for the events that have recently been delivered. Please scan the list below for those topics of interest and when you click on the link, you will see an abstract for each of the topics.
Please spread the word to others who may be interested.
Rhapsody Enlightenment Series
6/22 12-1 ET Validating the consistency & completeness of your requirements with modeling Manohar Rao https://www2.gotomeeting.com/register/785884730
7/13 12-1 ET Reverse Engineering existing code into Rhapsody Chris Carson https://www2.gotomeeting.com/register/890348450
7/27 12-1 ET Systems Engineering: Importing Requirements from DOORS to Rhapsody Justin Dyer https://www2.gotomeeting.com/register/933085170
8/10 12-1 ET Safety Critical Software Development with Rhapsody Bruce Douglass https://www2.gotomeeting.com/register/208807610
8/24 12-1 ET Systems Engineering: Trade Study Analysis Gavin Arthurs https://www2.gotomeeting.com/register/575771018
9/14 12-1 ET DDS Software Development with Rhapsody Dan Poirot https://www2.gotomeeting.com/register/289500490
9/28 12-1 ET Systems Engineering: Automating Harmony SE Processes with the SE Toolkit Andy Lapping https://www2.gotomeeting.com/register/653823042
10/12 12-1 ET How to Organize Your Model for Teaming, Reuse, Configuration Management Ed Mayer https://www2.gotomeeting.com/register/724120402
10/26 12-1 ET Systems Engineering: Creating Combined Simulations with Rhapsody and The Mathworks Simulink Ron Felice https://www2.gotomeeting.com/register/812217530
11/9 12-1 ET Test Driven Development with Rhapsody TestConductor Jeff Cohen https://www2.gotomeeting.com/register/801734122
12/14 12-1 ET Systems Engineering: Creating Interface Specifications with DOORS and Rhapsody Ed Mayer https://www2.gotomeeting.com/register/974353882
DOORS Enlightenment Series
Webcast series 1st Friday (Introductory) and 3rd (Advanced) each month 12:00 Noon ET for approximately 1 hour
6/29/12 DOORS Next Generation Update (every 2 – 3 months) Richard Watson https://www2.gotomeeting.com/register/348355346
7/6/12 Importing with ease Jim Marsh https://www2.gotomeeting.com/register/423068266
7/20/12 Common Metrics Collection in DOORS George Siampos https://www2.gotomeeting.com/register/996061362
8/3/12 Extending DOORS with DOORS Web Access Jim Hays https://www2.gotomeeting.com/register/856848242
8/17/12 Optimizing the Performance of DOORS Web Access Jim Marsh https://www2.gotomeeting.com/register/838124410
9/7/12 DOORS and Testing — The options available Jim Hays https://www2.gotomeeting.com/register/123105626
9/21/12 Requirements Management and Product Line Engineering Michelle Specht https://www2.gotomeeting.com/register/305250674
10/5/12 Collaborating with DOORS Discussions Melissa Robinson https://www2.gotomeeting.com/register/890606066
10/19/12 Extending DOORS – Introduction to DXL (DOORS eXtension Language) Don Cunningham https://www2.gotomeeting.com/register/370491698
11/2/12 Basic Tips and Tricks of Using DOORS Rick Learn https://www2.gotomeeting.com/register/240379874
11/16/12 Managing Change Proposals in DOORS Steve Grossman https://www2.gotomeeting.com/register/211722578
11/30/12 The Latest Update on DOORS Next Generation Richard Watson https://www2.gotomeeting.com/register/609802306
12/7/12 Extending DOORS to Model Based Systems Engineering Barclay Brown https://www2.gotomeeting.com/register/139105194
I’m just going to list the scripts and their functionality.
Rules have changed this year: Scripts can be up to 2000 lines long.
Export Heirarchy to HTML
Apparently based on the included DOORS HTML Exporter. Lets you selected which modules to export (including linked modules).
It’s a standard exporter but no Stylesheet information is used to make the HTML pop. I actually started work on something similar a few years ago, but felt that RPE made it obsolete.
Advanced Table Properties
Very impressive. Amazingly impressive. Can merge cells, easily set border option. Can select diagonally. Can Merge Right and Merge Left. Can split cells. Insert Row button. Incert Column button (left and right. Can remove rich text, show/hide link arrow, jump tables.
If he adds sort capabilities, which is not trivial, DOORS tables just may be usable. No table split capability either, which is fine.
I hope the author submits this to our DXL Repository (hint, hint).
Folder Hierarchy Picklist Wrapper (my name for it)
Helps to run DXL on multiple modules easily. Can choose a folder and then it’ll pick up all modules in a folder, even allowing to optionally match a search term (e.g., “Software”) and then runs any DXL you want across modules in the database.
A customer wanted to view baselines by “1”, not “1.0”. And search by milestone description (which is a pre-defined list).
The script will search out baselines matching criteria that has been input. Can also create a baseline with this tool. Also allows signatures. With the signature, it will allow a role selection, and also a label (Rejected/Accepted). If Rejected, a comment is required.
DOORS to RTC Bridge
Author did not give his name, but he sounded Scottish
Open-source VB.Net project. ALlows requirements in DOORS to be linked to work items in RTC using OSLC.
- Uses Madgex OAuth Library
- Requires MS .NET Framework 4
- There are instructions.
This is not a DXL script.
There is a girl snoring.
ANd the winner is…
Advanced Table Properties
My Suggestions for Next Year
OK, everyone. THe first rule of making a presentation is to introduce yourself. This is a huge pet peeve of mine, because even though I think everyone should know exactly who I am, the fact is they don’t. So I tell them who I am when I get in front of them. Simple.
Next year apparently is not going to be DXL specific. It’s going to be general DOORS scripting, so OSLC, VB, and other languages will be allowed.
This year, allowing 2000 lines, a revelation occurred: Why haven’t they done this before? It was absolutely stupid to limit the competition to 75 lines. Talk about limiting potential! I say lift the limit completely! Imagine some of the scripts that would be out there today if they didn’t have this absolutely ridiculous limitation. You could have had multiple competitions, one with the 75-line limit, and another without.
And on the same note, give better prizes. An Amazon gift certificate is nice, but make it like $500 or $1000. Or free admission next year (which I think is what they used to give) or something.
Also, send out notification. Apparently the DXL competition notification went out really late this year. That was acknowledged. But here I am, running a Web site that has a DXL Repository and I did not get any such notification at all.
Looking forward to what next year will bring.