Taking Control of your Requirements with DOORS Next Generation

1,333 views

Published on

Poor requirements management is the single biggest reason for project failure, and the cost of correcting mistakes increases dramatically the later we spot them. Complex products and projects demand a tool which can support design integrity, demonstrate regulatory compliance, and provide a single point of access for all requirements information to allow efficient communication of changes to everybody concerned. Furthermore the option to integrate with selected change, configuration and test management tooling to help facilitate end to end traceability.

See how IBM Rational DOORS Next Generation facilitates this by:

Enabling true collaboration within and between teams

Empowering users to adhere to governance through traceability, as well as showing the full scope of the impact of change

Ultimately making your data work for you, instead of the other way around

Allowing greater reporting capabilities in real time to take control of requirements and get a greater insight for impact analysis on changes to requirements

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,333
On SlideShare
0
From Embeds
0
Number of Embeds
236
Actions
Shares
0
Downloads
64
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Taking Control of your Requirements with DOORS Next Generation

  1. 1. Taking control of your requirements with DOORS Next Generation Matt Mendell, Product Specialist, IBM UK Internet of Things Team
  2. 2. Agenda  Challenges in developing and delivery of complex systems and products  How IBM Rational Requirements Management and other solutions can help  Key capabilities and benefits of IBM Rational DOORS Next Generation  Product Demonstration  Questions
  3. 3. Poor requirements management has a significant impact on your business 20 200 RelativeCosttoRepair Acceptance Test Unit TestCodingDesignAnalysis 0 Maintenance 1-2 10 5 50 Errors detected late in the Maintenance phase can cost up to 200 times more than detected early in Requirement Analysis phase1 Stage in which Requirements Error Is Discovered More than 40% of development budget can be consumed by poor requirements2 Sources: 1) Leffingwell & Widrig, “Managing Software Requirements,” Addison Wesley, 1999 2) IAG Consulting, “Business Analysis Benchmark”, 2008 “Our research indicates 80-plus percent of development failures result directly from poor requirements gathering, management, and analysis.” IDC, November 2007
  4. 4. 7 key fundamentals of Requirements Management Granularity Hierarchy & TraceabilityAttributes Collaboration Audit Trail Reporting
  5. 5. Information Traceability – ‘Chaos to Order’
  6. 6. DOORS Next Generation is part of a wider family
  7. 7. Demonstration
  8. 8. Exporting the data Linking for traceability Review & editing Importing the data1 3 2 4 5 Analysing the data
  9. 9. Exporting the data Linking for traceability Review & editing Importing the data1 3 2 4 5 Analysing the data Single source of truth Simplified version control Keeping track of requirement decomposition Satisfying regulators easily Evaluating impact of change
  10. 10. 7 key fundamentals of Requirements Management Granularity Hierarchy & TraceabilityAttributes Collaboration Audit Trail Reporting
  11. 11. References
  12. 12. Increased time to market and customer satisfaction. Reduced the time taken to detect the causes of bugs by 99%. Reduced system design time by more than 70%. Accelerated the time to market and the rate of innovation.
  13. 13. A major US health insurance company Saving at least SEK2 million (USD304,000) annually on each major project. Minimized exposure to potential delays and remedial work Reduced project defect rate by more than 10%
  14. 14. Thank You
  15. 15. Questions
  16. 16. Appendix: DOORS vs. DOORS Next Generation
  17. 17. DOORS DOORS Next Generation Client Thick client Jazz in browser Requirements Objects (tied to module) Artifacts (can be reused throughout database) Attributes Defined within each module Same for each object Defined across database User-defined artifact types Integration Point-to-point solutions Replicated data Synchronisation Seamless data and process integration Traceability across tools Jazz platform 3rd party integration via OSLC Views Local to module Can be global to project, or personal to user Links Static links Static traceability columns Mouse-over panels Dynamic traceability columns Dashboard Welcome screen Dashboard, real-time reporting of live information
  18. 18. Appendix: Integrations
  19. 19. Available adapters  CLM – Atlassian JIRA – Git – HP ALM  Rational Team Concert – PTC Windchill Further information: https://jazz.net/products/#adapters
  20. 20. Appendix: References
  21. 21. References  Leffingwell & Widrig, “Managing Software Requirements,” Addison Wesley, 1999  IAG Consulting, “Business Analysis Benchmark”, 2008

×