COLLW | Page 17

TUTO R IALS Tuesday, June 9, 1:00pm–4:30pm (Half-day Afternoon) 3.75 PDUs Per Half-day Tutorial TM Innovation Thinking: Evolve and Expand Your Capabilities Jennifer Bonine, tap|QA, Inc. Innovation is a word frequently tossed around in organizations today. The standard cliché is “Do more with less.” People and teams want to be innovative but often struggle with how to define, prioritize, implement, and track their innovation efforts. Jennifer Bonine shares the Innovation Types model to give you new tools to evolve and expand your innovation capabilities. Find out if your innovation ideas and efforts match your team and company goals. Learn how to classify your innovation and improvement efforts as core (to the business) or context (essential but non-revenue generating). With this data, you can better decide how much of your effort should be spent on core versus context activities. Take away new tools for classifying innovation and mapping your activities and your team’s priorities to their importance and value. With Jennifer’s guidance you’ll evolve and expand your innovation capabilities on the spot. TN Testing the Data Warehouse: Big Data, Big Problems Geoff Horne, NZTester Magazine Data warehouses have become a popular mechanism for collecting, organizing, and making information readily available for strategic decision making. The ability to review historical trends and monitor near real-time operational data has become a key competitive advantage for many organizations. Yet the methods for assuring the quality of these valuable assets are quite different from those of transactional systems. Ensuring that the appropriate testing is performed is a major challenge for many enterprises. Geoff Horne has led a number of data warehouse testing projects in both the telecommunications and ERP sectors. Join Geoff as he shares his approaches and experiences, focusing on the key “uniques” of data warehouse testing including methods for assuring data completeness, monitoring data transformations, and measuring quality. He explores the opportunities for test automation as part of the data warehouse process, describing how you can harness automation to streamline and minimize overhead. TO Security Testing for Test Professionals Jeffery Payne, Coveros, Inc. Your organization is doing well with functional, usability, and performance testing. However, you know that software security is a key part of software assurance and compliance strategy for protecting applications and critical data. Left undiscovered, security-related defects can wreak havoc in a system when malicious invaders attack. If you don’t know where to start with security testing and don’t know what you are—or should be—looking for, this tutorial is for you. Jeffery Payne describes how to get started with security testing, introducing foundational security testing concepts and showing you how to apply those concepts with free and commercial tools and resources. Offering a practical risk-based approach, Jeffery discusses why security testing is important, how to use security risk information to improve your test strategy, and how to add security testing into your software development lifecycle. You don’t need a software security background to benefit from this important session. TP Principles and Practices of Lean Software Development Al Shalloway, Net Objectives Lean software development has often been described as “better, faster, cheaper” and focusing on “eliminating waste,” but those are misnomers. Going after speed improvement and waste elimination can actually reduce the benefits you might otherwise get from lean. Al Shalloway describes what lean software development really is and why you should be incorporating it into your development efforts— whether you use Scrum, kanban, or SAFe. Al explains the mindset, principles, and practices of lean. Its foundations are systems thinking, a relentless focus on time, and an understanding that complex systems require holistic solutions. Employing lean principles, you optimize the whole, eliminate delays, improve collaboration, deliver value quickly, create effective ecosystems for development, push decisions to the people doing the work, and build integrity in. Lean practices include small batches, cross-functional teams, implementing pull, and managing work in process. Al will describe how to use lean—no matter where you are in your development process. TQ Design Patterns Explained—from Analysis through Implementation Ken Pugh, Net Objectives Ken Pugh takes you beyond thinking of design patterns as “solutions to a problem in a context.” Patterns are really about handling variations in your problem domain while keeping code from becoming complex and difficult to maintain as the system evolves. Ken begins by describing the classic use of patterns. He shows how design patterns implement good coding practices and then explains key design patterns including Strategy, Bridge, Adapter, Façade, and Abstract Factory. In small group exercises, learn how to use patterns to create robust architectures that can readily adapt as new requirements arise. Lessons from these patterns are used to illustrate how to do domain analysis based on abstracting out commonalities in a problem domain and identifying particular variations that must be implemented. Leave with a working understanding of what design patterns are and a better way to build models of your application domains. bring your team Groups of 3+ save big! See page 42 for details T O R E G I S T E R C A L L 8 8 8 . 2 6 8 . 8 7 7 0 O R 9 0 4 . 2 7 8 . 0 5 2 4 O R V I S I T A D C - B S C - W E S T.T E C H W E L L . C O M 17