We bring to you the best practices, advances, interviews, product demos & details and more through this blog.Read on all the posts we have for you and let us know your comments and opinions.
Requirements Management Blog
Welcome to Requirements Management Blog!
A one stop blog for all you are looking about Requirements Definition and Management and IBM products for requirements management.
We bring to you the best practices, advances, interviews, product demos & details and more through this blog.Read on all the posts we have for you and let us know your comments and opinions.
We have been discussing about requirements management practices and solutions from IBM Rational for Requirements Definition and Management at Rational RDM Blog. We decided to move to our new own home here in developerworks and will continue our discussions going forward here.
Make sure you change your bookmarks and follow this blog to to keep abreast of requirements management principles, advances in the domain and solutions from IBM Rational. We hope to continue having a fruitful discussion here and create a mutual learning platform for all of us! We will continue to discuss the contemporary world of requirements management from both software and systems perspectives.
Continue reading the blog for more details and articles...If you have any suggestions for topics, provide your comments here.
VijaySankar 270000E5JQ Tags:  requirements_management traceability refresher requirements 4,514 Views
Does the above graph ring a bell?
Many articles, papers and books have talked about the impact of fixing a defect at later stages of development life cycle. Researches have also been proved that majority of the software defects found in a project are related to requirements and continues to be higher than that arising due to design or coding issues. According to studies conducted, approximately 60%-70% of IT project failures result from poor requirements gathering, analysis, and management*. The most successful products and applications have been built with a thorough understanding of what they are intended for. Understanding and managing requirements are by far the most important aspect in the development life cycle irrespective of which technology, development process, industry or purpose of the software or system under development. The beauty of an effective requirements management is that it provides complete insights into how the development of a system is progressing for every stakeholder in the team yet at a level of abstraction neutral to technology, platform or perspective. It thus becomes the corner stone of software or systems development!
In today’s world, developing smarter products at the lowest time to market has become a norm for success. Often the level of pressure that mounts to get started and come up with a prototype or the product itself is high and requirements are cornered with least importance. But if we check statistics, we can see many examples that have caused hefty prices and disasters due to hasty development or lack of thrust given to understand the real requirements. Read a compilation by Computer World UK here. These two videos from IBM and IAG Consulting respectively talks about why you should consider requirements seriously.
If you watched the above videos, it is clear that the process of how requirements, are managed and collaboration and communication between stakeholders are equally important for an effective requirements management. Also many mistakenly believe that requirements management is something that takes place during the definition stages of a project and is then complete. However the reality is that requirements exist in some form at virtually every stage of development.
The three main factors to be considered while defining the requirements management are
Stay tuned for more posts on requirements management, analysis and other topics...
Have some suggestions/opinions/comments/topics...send us!
* Source: The Meta Group market research firm, a division of Gartner, March 2003
AndyGurd 270001QKDH Tags:  rational ibm doors requirements-management innovate rational-doors 4,771 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!
VijaySankar 270000E5JQ Tags:  ibm requirements_management clm doors rational rrc agile innovate requisitepro alm requirements 5,307 Views
In the last post we focused on what you can expect from Requirements Management for Systems Engineering track at Innovate 2012. In this post we will explore what is there in Requirements definition and management for IT application development track at Innovate 2012.
We have 16 sessions lined up in this track with focusing on software delivery that revolve around eliciting, defining, elaborating, understanding, organizing, reviewing, communicating and tracking business, user, and software requirements. We have multiple customer sessions; however I am sure you will find the below sessions interesting
Like previous editions of Innovate, this year also we have keynotes where IBM shares its road map, strategies and vision for requirements definition and management tools. Also there will be immense number of opportunities to meet senior product management professionals and developers of IBM Rational's Requirements Management tools in sessions like 'Ask the Experts: IBM Rational Requirements Composer and IBM Rational RequisitePro', What's New with IBM® Rational® Requirements Composer? and other presentations.
Some of the other notable presentations focus on trending topics and best practices in the requirements management domain like conceptual frameworks for visual definition in requirements life cycle, Requirements Engineering Maturity Model (REMM) and many more. There are multiple workshops about defining and managing requirements with IBM Rational tools, IBM Collaborative Lifecycle Management, best practices in using Requirements Composer and Jazz primers. Don't forget to try out Open Labs and solutions peds at Innovate!
And finally we have a competition (Who Is the Best IBM Rational Composer User? ) in which Rational Requirements Composer experts put their skills to the test to compete in a variety of different tool challenges and prove who is the best requirements tool champion.In this special event, participants have a chance to compete with IBM experts and tool developers to prove their expertise by solving common and difficult requirements management problems!
Have you registered for Innovate 2012? Hurry Up!!! just 9 days left...http://www.ibm.com/innovate/
Don't miss this opportunity to meet 4000+ professionals, attend your preferred sessions from 27 tracks and 400+ presentations and try out next generation products.
See you at Innovate!
AndyGurd 270001QKDH Tags:  requirements-management innovate traceability rational-doors rational-requirements-com... rational ibm 4 Comments 9,461 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?
Requirements and Agile – Does it go hand in hand? An interview with Agile business analysis expert Mary Gorman
VijaySankar 270000E5JQ Tags:  guest interview requirements agile requirements-management 7,203 Views
There have been interesting thoughts on how requirements and should requirements be managed in agile projects. Some believe that requirements management is meaningless; some believe they are still a critical factor irrespective of the methodologies one follow. Here we bring to you an interview with Mary Gorman, an Agile Business Analysis Expert at EBG Consulting where she argues that business analysis is essential for agile success.
Mary Gorman, CBAP, CSM, is VP of quality and delivery at EBG Consulting, whose experts help deliver high-value products that delight customers. Mary works with global clients, speaks at industry conferences, and writes on requirements topics for the business analysis community. In addition to serving on the IIBA® Business Analysis Body of Knowledge® Committee for four years, Mary helped create the first certification exam for the Certified Business Analysis Professional™ (CBAP®).
We've heard comments like "you can throw away all that requirements and analysis stuff now we're going Agile." Have you come across this and what's your view?
It's a common misconception. In fact, requirements drive agile teams! At EBG Consulting we find when agile teams collaboratively analyze requirements, they can speed development and delivery of high value products. The ability to be focused, nimble and disciplined about your requirements is essential for successful agile delivery.
So how does business analysis change as you adopt Agile practices?
You plan and analyze regularly to support a steady flow of product delivery, a hallmark of successful agile teams. On agile projects, we plan to re-plan. A plan represents your allocation of requirements—really options for satisfying product needs—to delivery cycles. Rather than trying to acquire all the possible requirements upfront at the start and create one big plan, you plan continually, using feedback from prior deliveries to adjust your plan. This in turn means you are continually analyzing requirements to discover high value options for the next delivery. Planning and analysis are interdependent and synergistic. See this article for more details.
Agile analysis is done just-in-time—you want your requirements to be “fresh”. You adjust the precision and granularity of requirements taking a just-enough approach. You make use of good analysis tools and techniques. For example, you might sketch a context diagram to quickly visualize the interfaces needed for a release, a minimum marketable feature, a use case or a story. Or organically explore requirements using a data model or state diagram. For more ideas to tune analysis for agile, visit Agile Analysis Challenges
What about the role of the business analyst in Agile?
In our forthcoming book, my co-author, Ellen Gottesdiener (EBG’s founder and president), and I write about a product partnership that collaborates to discover and deliver valued products. The partners include diverse perspectives from the business, customer and technology communities. We have found this partnership is critical for agile product success. (The book’s title is Discover to Deliver: Agile Product Planning and Analysis. Read more about it here.
Often business analysts ask us where they ‘fit’ in this partnership. Our response is to ask, “What are your skills?” An agile team needs strong skills in analysis, modeling, elicitation, facilitation, risk analysis, prioritization, strategic thinking, verification and validation along with a sound understanding of the product’s domain. The person who possesses a combination of such skills will be a valuable and valued team member.
Who should attend the webcast on How Business Analysis is Essential to Agile Success and what will they gain from it?
The webinar’s content has broad applicability. It may benefit someone involved with planning, analysis, valuation, validation and verification; teams and organizations transitioning to agile; product champions and product owners who have the responsibility for making decisions about what product options to deliver, anyone on an agile team who recognizes that user stories, user story maps, personas are often not enough to communicate product needs. The webinar provides ideas for holistically exploring and evaluating product options within a framework the agile team can use to reach a shared understanding of high value product needs.
Mary will be joining with us on Wednesday, June 27, 2012 for a webinar where she will expand on the below discussions to build a case that business analysis is your key for
Register for the webinar here
A replay will also be posted in case you missed the webinar on Wednesday. We believe this interview gave an insight into why business analysis is critical to agile projects. For more interactive discussion join us in the webinar.
What you think about requirements in agile? What level of requirements management/analysis do you follow in your agile projects?
VijaySankar 270000E5JQ Tags:  announcements doors-next-generation requirements-management rrc doors requirements 5,357 Views
We had a series of announcements earlier this month during Innovate 2012. The major announcements pertaining to Requirements Management space were RRC 4.0, DOORS 9.4 and DOORS Next Generation Beta. This blog post aims to dive a little deeper into these and provide a few helpful links...so read on!
Introducing Rational Requirements Composer 4.0
Collaborative Lifecycle Management (CLM) 2012 was announced on June 12 at the jazz.net website and Rational Requirements Composer (RRC) 4.0 continues to be one of the major pillars. CLM 2012 aims to provide the best integration experience available today in the industry between requirements, source control and quality management. For a detailed post on CLM 12, see Robin Garside's post in jazz.net.
In order to better the existing requirements management solution, RRC 4.0 comes up with a whole new set of improvements and features. The new and improved capability in this release will help project teams realize project change impact with downstream visibility using graphical and suspect traceability across requirements, test, and development items. Information access can now be controlled at a granular level - giving you the peace of mind knowing the exact requirements information that need to be modified. Project template upload and download as well as Requirements Interchange Format (ReqIF) are now available to give administrators and team leads easier control for multiple project environments. Additionally, project teams have greater cross project visibility through project dashboards. Some other significant highlights of RRC 4.0 are:
Watch out for another blog post detailing these improvements in RRC 4.0 soon…
Introducing Rational DOORS 9.4
Systems space was equally active this month with lots of announcements from IBM Rational. With the help Open Services for Lifecycle Collaboration (OSLC), continued efforts have been put in unifying lifecycle disciplines across systems and software engineering. DOORS 9.4 and DOORS Web Access 1.5 are the latest offerings in Requirements Management for Systems space. DOORS 9.4 boasts of significant enhancements in server side and new integrations with Rational Quality Manager, Rational Software Architect Design Manager beta and DOORS Next Generation beta using OSLC.
Significant usability enhancements have been made for both rich and web clients. Customer templates designed using Rational Document Studio are now supported by DOORS 9.4. An additional bonanza of producing documentation from DOORS without the need for an additional license of Rational Publishing Engine is now possible. For a detailed account on the improvements in DOORS 9.4; visit the announcement letter here.
Download IBM Rational DOORS 9.4 here. Learn more about Rational DOORS here.
Stay tuned for a detailed post on What’s new in DOORS 9.4…..
DOORS Next Generation Beta
IBM DOORS Next Generation aims to be the next generation requirements management solution for complex software and systems engineering environments. Today, we are releasing latest version, Beta 3 of DOORS Next Generation and is available for download from jazz.net. DOORS Next Generation is built on the learnings of DOORS and extends the technologies of Rational Requirements Composer and DOORS 9. If you are considering how different DOORS Next Generation is from DOORS, read the article written by Richard Watson, Senior Product Manager for RM tools at IBM comparing the two products in jazz.net.
With this beta version, data import/export between DOORS Next Generation and DOORS 9.x projects are possible. Also bi-directional linking between the two products is supported. Development of DOORS Next Generation is kept transparent following the jazz vision and all developments can be tracked at Rational DOORS Next Generation section in jazz.net.
Our intended direction for developing DOORS family is to allow a smooth transition between DOORS and DOORS Next Generation. For each DOORS license entitlement that has active Subscription and Support, a customer will be able to use either DOORS V9 or next-generation capabilities. A commercial version of DOORS Next Generation is expected in the last quarter of this year.
Any queries? Feel free to contact us!!
VijaySankar 270000E5JQ Tags:  doors jazz.net rqm requirements-management requirements doors-rqm rational 2 Comments 12,382 Views
As we mentioned in an earlier blog post, DOORS 9.4 and DOORS Web Access (DWA) 1.5 were released during Innovate 2012.This blog post provides insight into what’s changed in this release of DOORS and some of the significant new features. I have also provided a few resources where you can learn more about this release.
DOORS –RQM Integration based on OSLC
The most significant changes in DOORS 9.4 are the improvements to OSLC based integrations. A new integration based on OSLC has been provided for Rational Quality Manager (RQM). Let's see how it is different from the existing (RQMI) integration based on a point-to-point solution. Provided below is a simplified representation of how RQMI works for the DOORS-RQM integration and contrasts it with the new OSLC based integration.
As you can clearly see, the integration has been made so simple in terms of software and storage, yet more powerful. The new integration provides a stable architecture for future enhancements and provides an automated migration. If we consider the installation and configuration aspects, the new integration no longer requires the server and java client components.
What does this mean to a typical DOORS user? - This enables real-time lifecycle traceability to RQM test cases. This can be achieved through either the hover over menu from DOORS that display RQM artifacts or directly from RQM
What does this mean to a typical RQM user? - The real-time integration enables the RQM user to review and edit the automatically created draft test cases (with the new requirement reconciliation wizard) based on new requirements, and trace them back to DOORS. Full test coverage when requirements are changing is enabled with features like
Another important improvement in this release is the enhanced traceability to meet regulatory requirements. This enables
Apart from this, integration to Design Manager RSA and Rhapsody beta based on OSLC is also available in DOORS 9.4. However Design Manager is still in beta and this integration will be available only during later part of this year. For more details, visit jazz.net. Also the data exchange mechanism has been upgraded to the latest version of OMG (Object Management Group) ReqIF (Requirements Interchange Format) from RIF. This helps in improved communication of requirements between organizations in a supply chain. Support for data exchange and linked data between DOORS 9.x and DOORS Next Generation is also included. Reporting across DOORS 9.x and DOORS Next Generation is also included.
There are going to be some changes in licensing when we consider using DOORS with Rational Publishing Engine (RPE). We have removed the requirement for a RPE license while using RPE custom templates from directly within DOORS. But you still need a license for creating new custom templates; however it is not required to drive the reports.
We will briefly look at the usability improvements that have gone into DOORS 9.4. Many of these usability improvements reduce the need of writing custom DXL scripts. In DOORS 9.4, we have provided a stronger support to define and manage how more than one user can work on a module simultaneously. It is controlled with a widget allowing you to set a sharing level for editing as shown below. The Views now support color coding and the user is allowed to control the background color of attributes. The views have been also extended to 128 columns.
Another small, yet significant usability improvement is the possibility to remove multiple views in a single selection. And finally DOORS now supports rich text exporting to Microsoft Excel.
What do you think about the improvements? If you have questions or comments please leave them here. If you need more information about the product, trials or resources, visit IBM Rational Requirements Management Web Page.
VijaySankar 270000E5JQ Tags:  rrc rational rational-requirements-com... requisitepro rrc40 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