Requirements Management Blog
AndyGurd 270001QKDH Tags:  requirements-management innovate traceability rational-doors rational-requirements-com... rational ibm 4 Comments 9,462 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:  requirements-management rtc doors-next-generation rational-doors rational-requirements-com... agile doors-ng doors rational rational-requisite-pro rational-team-concert reqpro jazz.net jazz requirements-traceability collaboration traceability requisitepro 17,890 Views
On Thursday 14 March I presented on an IBM sponsored Dr Dobbs webcast on the topic of ‘3 Reasons to Throw Away Your Requirements Documents’. If you didn’t catch the webcast, you can view it on-demand and download the slides. If you did attend I hope you enjoyed it and in this blog post I want to answer some of the questions that I didn't get time to cover in the webcast, so scroll down to see if I've covered your question here. But first, for those of you who didn't make it, here's a quick recap of points I made during the webcast:
Ok now onto some of the questions that were submitted but I didn’t time to answer during the webcast. I’ve divided them into sections based on the type of question so you can easily scan down to topics you’re interested in:
Alternative approaches to managing requirements
Q. What's the advantage of a requirements management tool if I could link my change management tickets to fine grained requirements (use cases, storyboards) that are maintained on a wiki or other collaboration tool (e.g. Sharepoint or IBM Connections)? It would seem that the work items would give you the needed traceability and metrics?
A. While you might be able to create the level of traceability you require, how would you report on it? Would you have to build bespoke views and reports? And would the use of a wiki for ‘fine grained requirements’ provide you with a view of requirements in context with one another as opposed to individual wiki pages? Where would you document additional properties of requirements? Could you easily reuse requirements across projects? A requirements management tool like IBM Rational DOORS Next Generation provides built-in traceability views and reports, enables to you to structure requirements in context with another in document-like views, provides user-defined properties for recording additional information and facilitates reuse of requirements.
Requirements Management and Agile Development
Q. We are mostly using water fall model, but looking into checking if Agile works for our customers. I am very interested in the role of a Requirements Analyst in the Agile world. In our world, the analyst is a facilitator of requirements gathering and not a SME on the business application we are gathering requirements for.
A. That facilitation role and the analysis skills of the Requirements or Business Analyst are still essential in Agile development. A common mistake when moving to moving to more agile approaches is appointing a ‘Product Owner’, who is a subject matter expert in the business domain you are building an application or product for, and expecting them to write the requirements or ‘user stories’. While they are experts in the business and you need that expertise on hand for Agile to work, they are not usually skilled in getting to the root goals or needs of the business problems you’re looking to address with the product or application. Without the skills of the Requirements or Business Analyst, it’s all too easy for the user stories to become about automating the way things are done today rather than addressing the real business issues in an optimal way. You can read more about the role of the analyst in Agile development in an interview with Mary Gorman of EBG Consulting.
Q. How does the IBM requirements toolset compare to more "agile" focused toolsets like Atlassian, Rally, etc.?
A. IBM is very committed to supporting agile development, particularly when agile is scaled to large, distributed development teams. At the heart of our agile development capabilities is Rational Team Concert which supports agile planning, task management and change management. As stated in the webcast though, we’ve found in our own continuous delivery process and heard from clients, that a place is needed to capture more details of requirements and their associated properties, in context with one another, together with supporting artifacts like storyboards, workflow scenarios and use cases. The integration of Rational Team Concert with Rational DOORS Next Generation provides those additional capabilities while preserving traceability to user stories and epics managed in the product backlog.
IBM Requirements Management solutions
Q. It seems this discussion is on Rational DOORS. Is Rational Requisite Pro still offered? If so then how do these two products compare?
A. IBM continues to support, maintain and respond to enhancement requests for Requisite Pro, but our future direction for requirements management for IT application development lies with Rational Requirements Composer and we provide migration support and a trade-up program. Please contact your IBM representative for more details. If you are using Requisite Pro for requirements management for complex products or embedded systems development, then you might also want to look at whether Rational DOORS or Rational DOORS Next Generation is the right move forward for your organization. But don’t worry we’re not forcing you to migrate today.
Q. You've mentioned DOORS Next Generation in your presentation, what is that? Does it replace DOORS?
A. IBM Rational DOORS Next Generation is a requirements management application on a collaborative lifecycle management platform for systems and software engineering that provides requirements collaboration, planning, reuse and lifecycle traceability. DOORS Next Generation (DOORS NG) was introduced in 2012 to take advantage of the common, collaborative ‘Jazz’ platform shared by Rational Team Concert, Rational Quality Manager, Rational Design Manager and Rational Requirements Composer; and to extend the requirements management capabilities in Requirements Composer to meet the needs of product & systems development organizations developing complex and/or embedded systems. DOORS NG will enable IBM to introduce new capabilities, faster, that would have been more difficult to deliver with existing DOORS product. However DOORS NG does not replace DOORS today. We have a very large install base of DOORS users working on programs that can last tens of years, and we will continue to support, maintain and enhance the DOORS 9.x series to meet the needs of those users. We encourage existing DOORS users to take a look at DOORS NG, to try it out on pilot projects and use the interoperability capabilities to exchange and/or link data with DOORS 9.x. Existing DOORS customers with active support & subscription are entitled to use DOORS NG without requiring an additional purchase – you can use your existing DOORS license entitlements to use with either DOORS or DOORS NG or a combination of the two. But we are not telling existing DOORS users to migrate live projects to DOORS NG today. DOORS NG in it’s early releases is attractive to organizations who don’t currently use a requirements management tool and are looking for a web based solution that also offers common platform integration with change management, agile planning, test management and design management capabilities. You can download a trial and follow development plans for DOORS NG on Jazz.net.
Q. How does Rational DOORS Next Generation compare to Rational Requirements Composer?
A. DOORS Next Generation is based on Rational Requirements Composer but extended to meet the requirements management needs of product & systems development organizations developing complex and/or embedded systems. In the first releases of DOORS NG, the web client is identical to Requirements Composer, but DOORS NG also features a rich client which is designed for usability of editing large requirements specifications. The strategy for the two products is that while Requirements Composer will be focused on the needs of business analysis and IT application development teams, DOORS NG will be focused on the needs of systems engineers and product & systems development teams.
I’d like to wrap up this post by thanking all of you who attended the webcast, participated in the polls, asked some great questions and completed the survey feedback. If you missed it, you can catch a replay or download the slides. I’d welcome any additional comments or questions here.
VijaySankar 270000E5JQ Tags:  requirements-management rational rational-requirements-com... rational-doors 5,797 Views
As another year comes to an end, we wish you all a happy and prosperous new year!
2012 was an eventful year with major releases for both Requirements Composer and DOORS. We announced the next generation requirements management solution for complex & embedded systems from IBM - Rational DOORS Next Generation in November.
We moved to deverloperWorks platform for our blog. We believe our readers found this blog useful. Please share with us your comments and suggestions for the blog content and also any specific topics in requirements management that you want us to focus on in 2013....
Last but not least, as we mentioned in the last post, call for speakers in now open for Innovate 2013 - The IBM Technical Summit. Submit your abstracts before January 14 2013 to stand a chance of presenting in a conference with 4000+ footfalls and a free conference pass!
Happy New Year!
VijaySankar 270000E5JQ Tags:  innovate2013 rational-requirements-com... jazz requirements-management requirements innovate rational track-chair rational-doors jazz.net 11,766 Views
Innovate 2013 – The IBM Technical Summit is here. The 2013 event promises to be even more exciting with top-notch keynotes, over 450 breakout sessions, labs, certifications and our biggest exhibit hall ever. As in previous events, Requirements Management is one of the key areas of interest at Innovate which attracts speakers and attendees from across the globe representing a wide range of industries. In 2012, we had two tracks for Requirements Management with sixteen sessions each with one track focusing on IT and another focusing on Systems Engineering. We had 14 real life case studies, 2 panel discussions and 4 instructor led sessions.
Managing requirements has always been a cornerstone in both software and systems development. The importance of the discipline continues to grow and is expected to take a leading role in the coming years. This is an opportunity to showcase your thoughts on the discipline, and how requirements management tools like DOORS or Requirements Composer can aid in managing effectively the requirements for project successes. Here are some of the topics from last year and an expected list of topics
Some session topics from Innovate 2012
Explore new areas - Free conference pass opening up the doors to 450+ sessions, labs and demo booths
Network with experts and peers - Over 4000 professionals expected to attend the event
Sharpen your technical know-how - Learn from product and domain experts and from IBM core developers
Submit your papers before January 21, 2013 and stand a chance to present at Innovate 2013!. For more details, visit http://www-01.ibm.com/software/rational/innovate/tracks/. Here is a blog post for some submission guidelines
VijaySankar 270000E5JQ Tags:  rrc rational rational-requirements-com... rrc40 requisitepro clm clm2012 requirements-management requirements 6,422 Views
A lot have been talked about CLM 2012 and Rational Requirements Composer 4.0 since their release in June 2012. RRC 4.0 is now available for download from jazz.net.I am sure, most of you have already downloaded and started playing around with it.In this post, I will try to briefly touch base on the enhancements we made in RRC 4.0 and also provide resource links to download, demos and other tutorials.
Essentially the improvements in RRC 4.0 have been around
Combined Definition and Management - A clear and centralized requirements management eliminate redundancy and enable real time development.In RRC 4.0 we have moved the sketching, diagramming capabilities to the Web client to allow creation of rich text, diagrams, visual use cases, storyboards, and rich text based requirements.
Life cycle Solutions & Collaboration - Improved Word/Excel migration and improved collaboration capabilities
Improved Planning & Visibility - Enhanced visibility using traceability across requirements, test and development.Visual and textual scenarios are now supported.Through the customized dashboard users will be able to know what is under work and can quickly navigate to information that is being traced, discussed, or under work at the present time. Data can also be organized in dynamic analysis views to help answer project questions and reports. For RRC 4.0 you can now use the RTC planning capabilities to help priorities requirements before they are defined. This capability allows requirements to be directly aligned with priority and planning.
Support for ReqPro data migration has been improved significantly. Stay tuned for another post on this topic. Meanwhile I encourage you to watch some videos that explains this in detail. The major improvement in RRC 4.0 is with respect to the improvements we have made in traceability. We have further expanded both requirements and life cycle traceability capabilities. A graphical traceability analysis and usage tool has been included in the latest version that enables you to graphically analyze the requirements in detail with enhanced filtering options.Suspect link analysis has also been improved significantly. A suspicion profile can be set and it allows to select the requirement types that you want to assess.This enables to take care of false positives, and discover changes across trace links among requirements and other life cycle elements. Watch the demos provided below to see how this works.
Some other feature level enhancements in RRC 4.0 are
Requirements Composer on jazz.net
Requirements Composer Forum
Rational Requirements Composer Download
A Preview of Links Explorer
A Preview of Suspect Analysis