Better Software Conference & Expo 2008 brochure

cOncuRRenT cLasses ThuRsdaY, june 12, :00 T15 ManaGinG proJeCts anD teaMs T19 soa Maximizing ROi on new Technology acquisition Chris Ronak, Divestco, Inc. IT departments and software technologists must invariably navigate many challenges when planning to acquire new tools, invest in new technology, fund new technology projects, and introduce process changes. How do you get the most out of these investments without upsetting existing missioncritical processes or projects? Subsequently, how do you rapidly turn your new technology into a successful release that augments your product suite? Chris Ronak shares his experiences and offers his recommendations on how to best integrate newly acquired technology into mainstream development processes and projects. A strategic acquisition must provide missing functionality that enhances your existing product suite or technical framework—and it must be implemented without hindering or stopping progress on other business-critical projects. Join Chris to explore ways to build an extensible core technology framework that allows you to successfully integrate new technology and innovative practices into your existing development organization. The challenges of sOa security Jimmy Xu, CGI, Inc. Service Oriented Architecture (SOA) has many security challenges. To address these challenges, it is not enough to set up a secure operational infrastructure. SOA security must be implemented in all key areas of software development— architecture, design, platform, governance, requirements, development, and testing. Jimmy Xu discusses today’s SOA security challenges and explains why it is important to address these challenges inside software development. He presents the latest security practices: standards compliance; review of architectural blueprints and SOA platforms; secure SDLC process; threat modeling; secure coding; and security testing. This session not only prepares you to delve into the details of SOA security methodology, process, and techniques but also gives you the background information you need to plan and scope security assurance activities in your SOA development projects. T20 seCUrity T16 personal DeVelopMent fuzzing: new Tests for Robustness and security Ari Takanen, Codenomicon Traditional security measures are doomed to fail because they are focused only on defending against known attacks—and studies show that more than 80 percent of software will likely crash when extensive negative testing is employed. Fuzzing is a new, proactive technique for discovering security vulnerabilities and robustness issues in software. Although fuzz testing is most often based on some form of syntax checking, random input testing also can be appropriate. Fuzzing is valuable during development when application testers use the technique to surface issues and in production when security testers use it for audits. Any type of system can be fuzz tested—from enterprise solutions to consumer products such as mobile phones and set-top TV cable boxes. Ari Takanen discusses the origins of fuzzing, explains the different technologies used by fuzzers, and identifies current fuzzing tools, their uses and limitations. Ari describes various metrics related to fuzzing that allow you to measure effectiveness and compare the efficiency of various tools. an alternative to consensus: accelerating effective decisions Michele Sliger, Sliger Consulting Software development teams don’t always need, want, or have time to make decisions via group consensus. And project leaders often already feel overburdened with the multiple decisions they have to make on their own. But there is a middle path—an alternative to consensus—in which shared responsibility for decision-making provides for input from many and one voice to represent the team and make the final choice. In this decision-making process, a team member volunteers to be the decision-maker on a particular issue with only one mandatory rule—seek guidance. The greater the impact the decision will have on the organization, the wider the quest for advice must be—all the way to the board of directors, if appropriate. Join Michele Sliger to learn how this approach to decision-making might be right for your organization. T17 aGile DeVelopMent T21 speCial topiCs Test-driven analysis: focus on the user, not the code Ken Pugh, Net Objectives Test-driven analysis (TDA) focuses on the system at the user interface level. By concentrating on scenarios from the users’ point of view, TDA examines the inputs and outputs of a system and how the state of that system changes as a result of actions performed on the system. Further, TDA concentrates on creating tests that help developers and business analysts understand the problem domain and the system requirements. Ken Pugh explores how tests created during TDA efforts relate to user acceptance tests and how the TDA tests can propagate to those created in a test-driven development framework. Together with Ken, you’ll create analysis tests for a sample system and differentiate between various types of tests—acceptance, analysis, and design. This class is about the process of inquiry we need during analysis to answer the question “I know you’re ready for testing, but what are you testing for?” scenario-Based architecture Reviews: a Quality process Kevin Bodie, Pitney Bowes Quality attributes—performance, scalability, availability, maintainability, etc.—are often referred to as the non-functional requirements. Unfortunately, these critical factors often are specified through vague platitudes rather than explicit statements. Participatory, scenario-based architecture reviews are essential to determine if the architecture meets the system’s quality attributes as well as the functional requirements. Scenario-based architecture reviews rigorously examine the characteristics of the system to determine strengths, limitations, operating bounds, and overall requirements satisfaction. Results include the impact on and risk of architectural choices for the system. Kevin Bodie details the architecture review planning process, illustrates its execution, and shows you the results with specific deliverables—the Architecture Readout Presentation and Executive Architecture Readout. Kevin presents real-world examples of these deliverables and offers you a review process model to implement in your organization. T18 MetriCs You just don’t understand Me: interdisciplinary awareness to the Rescue Mike Tholfsen, Microsoft Different disciplines and departments in an organization still have the same goals, but often misunderstand one another. We have all heard someone say about another group, “Those people are clueless.” The irony is that “those people” are saying the same thing back under their breath. Within the software disciplines, poor understanding, lack of communication, and unfortunate stereotyping are often commonplace. Presenting a new concept and team exercise called Interdisciplinary Awareness, Mike Tholfsen helps us focus on the importance of team dynamics in building good software. With case studies from both Microsoft Office and Windows teams, Mike shows how they built stronger trust within and between teams. Incorporate this exercise in your group and discover how interdisciplinary awareness can lead to greater understanding and appreciation, a stronger sense of team, and a higher degree of trust. To regisTer call 888-268-8770 or 904-278-0524 or visiT www.sqe.com/bscereg 2 http://www.sqe.com/bscereg

Table of Contents Feed for the Digital Edition of Better Software Conference & Expo 2008 brochure

Better Software Conference & Expo Brochure Contents Conference At-A-Glance Special Events Conference Speakers 49 In-Depth Pre-Conference Tutorials 4 Keynote Presentations 42 Concurrent Classes Event Location and Las Vegas Highlights What Our Delegates are Saying Sponsors and Exhibitors Registration Information

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.