Successfully reported this slideshow.

Blueprint Requirements Center 2010

4,686 views

Published on

Blueprint requirements Center 2010. An impressive requirements workbench.

Published in: Technology, Business

Blueprint Requirements Center 2010

  1. 1. Blueprint Requirements Center 2010 Terry Pritchard, Regional Director, Canada terry.pritchard@blueprintsys.com ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary 416 568 0075
  2. 2. VALUE OF REQUIREMENTS Requirements define success in all application projects Effort New Application Application Application Modernization Consolidation Minor Minor Release Release Project Lifecycle ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary 2
  3. 3. ROLE OF THE REQUIREMENTS AUTHOR • Author requirements documentation for Software projects • Validate requirements with stakeholders • Communicate requirements to developers, testers, and project managers Effort New Application Application Application Modernization Consolidation Minor Minor Release Release Project Lifecycle ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary 3
  4. 4. AUTHORING CHALLENGE: SILO’D TOOLS Textual User Interface Use Cases Glossaries Business Lists Mockups Flows Process Requirements Documents • Business • Performance Requirements Requirements • Functional • Glossary of Terms Requirements • Risk and Constraints • Security • Specifications Requirements • Traceability Matrix Problems:  Promotes inconsistencies and hides errors  Lost context and lack of traceability  Template focus vs. content quality and completeness  Difficult collaboration via document reviews  Managing change impossible ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary
  5. 5. FALSE VALIDATION AND REVIEW Textual Lists User Interface Mockups Use Cases Flows Glossaries Business Process ? ? ? ? ? Requirements Documents • Business • Performance Requirements Requirements • Functional • Glossary of Terms Requirements • Risk and Constraints • Security • Specifications Requirements • Traceability Matrix Problems:  Ambiguous, missing, conflicted requirements  Difficult to read and understand  Stakeholders are busy and don’t thoroughly read  False validation and premature requirements signoff ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary
  6. 6. FALSE VALIDATION = POOR OUTCOMES 40% of project budgets are wasted due to rework from poor requirements(1) The problem is multiplied with distributed teams, outsourcing, and integrated CIO/PMO application modernization projects. Revision Revision Rework Rework MULTIPLE Rework Revision VERSIONS OF THE TRUTH Business Business Reqs Design Dev QA UAT Needs Application Revision Rework Rework Rework Revision Rework Rework Effort Problems: REWORK REWORK  Costly change and project rework REWORK Application  Cycle time increases New Application Modernization Application Minor Consolidation Minor Release  Projects over budget Release Project Lifecycle  Inability to meet business needs 1 – voke, IDC, IAG, Gartner 6 ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary
  7. 7. BLUEPRINT INTRODUCTION Blueprint provides the industry’s most complete requirements workbench that empower all organizations to author, validate, and communicate high-quality requirements. Blueprint Process Blueprint Impact: Author  Improve business and IT alignment Iterative And Communicate  Reduce cycle time and project rework Additive Validate  Lower delivery costs ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary
  8. 8. BLUEPRINT REQUIREMENTS CENTER 2010 Requirements Workbench Author Collaborate Multi-Aspect Rich Text Requirements Actors Import/Export Simulation Process Traceability Comments Test Generation Requirements Mgmt Use Cases Glossaries Track Changes Integration Test Management User Interface Data and Rules Document Generation Integration Blueprint Resource Center Self-Training Videos Best Practices Knowledge Base Industry Resources Discussion Forum Blueprint Team Repository Version Control Security Notifications 8 ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary
  9. 9. THE BLUEPRINT DIFFERENCE A SINGLE VERSION OF THE TRUTH 1 Author Requirements Lists UI Mockup Business Process Use Case Editor Editor Glossaries Data and Rules Diagrams Editor Editor • Full Traceability Blueprint • Impact Analysis Integrated • Track Changes Model 2 Validate 3 Communicate Requirements Document, Specify Simulation Generate Test Scenarios • Simulate All Requirements (UI, process, data) • Auto-generate Microsoft Office Documents • Capture Feedback into System • Generate 100% of Functional Test Scenarios • Track and Incorporate Changes • Integrated with ALM Solutions for Req Mgmt ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary
  10. 10. SUMMARY: REQUIREMENTS THAT WORK Challenge Summary: What Blueprint Does. Multiple Requirements Documents  Single Version of the Truth Confusion and Misunderstanding  Multi Aspect Simulation Changes are lost between Documents  Track Changes Quality Assurance is not aligned  Generate Test Scenarios Developers use ALM Tools  ALM Integrations Effort New Application Application Application Modernization Consolidation Minor Minor Release Release Project Lifecycle ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary 10
  11. 11. BLUEPRINT EMPOWERS ALL ORGANIZATIONS Centralized Department BENEFIT Competitive Advantage Project Based BENEFIT Team Productivity • IT Organizations standardize on Blueprint and deliver all BENEFIT • Departments standardize on requirements definition Individual Productivity Blueprint. through a center of excellence. • Software projects are • All department requirements authored, validated, and are visualized through • All business/IT requirements Ad-hoc communicated through simulation. are visualized through Blueprint simulation. • Department benefits from • MS Word, Excel, • Project requirements are PowerPoint, Visio visualized through simulation standards, requirements reuse, and expertise ROI • Company wide standards. leveraged efficiency. • Project test scenarios are used • 1st Generation RM by QA, requirements tools used documents are generated. • GUI Prototype tools may be used. ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary
  12. 12. CASE STUDIES Challenge The scale and complexity of IT projects increased dramatically due to business expansion, and paper-based requirements were resulting is increased rework, waste. Business Value Requirements authors centralized and empowered to deliver a competitive advantage. All requirements (including use cases, UI Watch Video: mockups, lists) are visualized to ensure understanding. Result: Agile http://blueprintsys.com/customers.php requirements, faster cycle-time, less rework. Challenge Under pressure to standardize requirements practices for upcoming application modernization projects, Merck was looking to create central system-of-record for all requirements assets. Business Value Merck now has standard processes for Six Sigma certification and all requirements are defined within Blueprint Requirements Center. Merck uses the Blueprint + HP Integration to ensure IT and QA teams test the right functionality: Result: Standardized requirements to reduce error and control costs, tight integration with existing ALM process and solutions. Challenge Requirements error, ambiguity, and inconsistency were resulting in rising costs of IT projects and delaying delivery of systems critical to cruise line operations. Business Value After an exhaustive search of all requirements definition options, Carnival selected Blueprint to define, simulate, and communicate all requirements Result: Better requirements with more stakeholder Watch Video: http://blueprintsys.com/customers.php involvement -- and the most successful IT project in history. ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary
  13. 13. CUSTOMER SUCCESS
  14. 14. MORE INFORMATION Online Customer Demonstration Testimonials Visit the Blueprint Demonstration center to watch on- Learn from Blueprint customers on the process on how demand video presentations on the product. Blueprint they selected Blueprint Requirements Center, the ROI, and product specialist will provide an overview of the solution. how they are using to lower costs and improve alignment. http://www.blueprintsys.com http://www.blueprintsys.com/Customers.php Blueprint HP Quality Center Whitepapers Interoperability Download free whitepapers on requirements definition for Learn about how Blueprint and HP Software provide seem- distributed teams, outsourcing, application modernization, less integration and interoperability. Watch videos on how building a center-of-excellence, the rework tax, and more. the solutions work together. http://www.blueprintsys.com/whitepapers.php http://www.blueprintsys.com/hpqualitycenter Solution Visit Video Overviews Requirements.net Watch short videos on how Blueprint is used to define Blueprint is a founding member of the industry’s largest requirements for agile, application modernization, consortium dedicated to requirements process outsourced teams, and distributed organizations improvement. Download Podcasts, whitepapers, more. http://www.blueprintsys.com/solutions.php http://requirements.net ⓒ 2010 Blueprint Software Systems Inc. - Confidential & Proprietary

×