Requirements Management Blog
AndyGurd 270001QKDH Tags:  requirements-management innovate traceability rational-doors rational-requirements-com... rational ibm 4 Comments 9,276 Views
I'm writing from Innovate 2012 in Orlando, Florida where thousands are attending sessions and sharing thoughts about software development and systems engineering. One topic that keeps coming up is that of traceability. On Sunday at VoiCE (Voice of the Customer Event), we had some great discussions with clients in the industrial sector building complex and embedded systems such as planes, cars and medical devices about traceability scenarios they have. There was a lively discussion around how much traceability is enough. One client, who is working in aerospace, needs to comply with DO-178B, and requires traceability all the way from a high level customer requirement through to individual lines of code. Others asked 'do you really need that fine grained traceability?' and 'won't that be very difficult to manage?' Another described that they have 26 teams and 16 applications to manage, and in the past had many (I think I heard 50!) locations where requirements were stored, usually in spreadsheets, making traceability very difficult. Now with the 'right schema' in place and using IBM Rational Requirements Composer, they have a solution that makes traceability much easier, and an environment that is manageable for the long term as it scales. Having the right schema - the information model of artifacts and what relationships they have was stressed as a vital ingredient in any recipe for successful traceability.
In a breakout session yesterday, data was shared that on a deep space exploration mission project, there are over 80,000 items in the requirements database (IBM Rational DOORS) and over 40,000 links - mind blowing complexity of data and relationships, and that's on one of many projects they have running today.
The right culture, process and tools for your application/system/product/service, organization and industry are necessary to prevent traceability across not only requirements, but into designs, work items, tests and so on, spiraling into an uncontrollable, unusable spaghetti of artifacts and links.
So for you and your projects, how much traceability is enough, how are you managing it and what would you like to see in the future to make the creation, maintenance and most importantly utilization of traceability easier to do and more effective?
AndyGurd 270001QKDH Tags:  rational ibm doors requirements-management innovate rational-doors 4,604 Views
At Innovate 2012 in Orlando, June 3-7 there will be two requirements management (RM) tracks – one focused on RM for IT application development, and product-wise primarily on RequisitePro and Rational Requirements Composer; and another focused on RM for systems engineering (SE), and product-wise on DOORS. This blog post is focused on the RM for SE track but look out for another on the IT focused track.
I think you’ll find that the RM for SE track has some really strong content this year. Out of 16 sessions, 10 will feature customer speakers, including:
You’ll also be able to meet product management and senior development staff and ask them questions in our ‘Ask The Experts (for DOORS version 7.x, 8.x and 9.x users)’, and you’ll hear about IBM’s strategy and roadmap in ‘What's Now and Next in Requirements Management for Systems Engineering’, including the latest release and plans for the DOORS 9.x series.
If you’ve been following our RM developments recently you’ll be aware of the DOORS Next Generation project on Jazz.net and you’ll hear about that during the Now and Next session, and if you want to dive deeper into what’s planned be sure to go to the session ‘Deep Dive Investigation and Feedback about IBM Rational DOORS Next-Generation Beta’ and visit the DOORS Next Generation demo pedestal in the Innovation Lab area of the Solution Center.
And if you’ve ever attended before, you’ll know that a popular feature is the DOORS DXL Script Exchange competition, where you can demonstrate your prowess in DXL and win a small prize. For more details about this year’s competition (with a twist!) please email email@example.com. Scripts are due on or before May 25th.
On top of all this fantastic content (and this is just for one track – there are over 400 sessions across the whole conference!), Innovate is a great opportunity to network with other systems engineers and software developers, share war stories, tips and tricks and maybe a drink or two.
To find out more about Innovate 2012 and to register go to ibm.com/innovate.
We hope to see you there!