21.07.2015 Views

SOFTWARE TESTING ANALYSIS & REVIEW - SQE.com

SOFTWARE TESTING ANALYSIS & REVIEW - SQE.com

SOFTWARE TESTING ANALYSIS & REVIEW - SQE.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CONCURRENT SESSIONSWEDNESDAY, MAY 16, 3:00 p.m.W11TEST MANAGEMENTEmploy Tomorrow’s Customers to StaffYour Testing Team TodayAlex Dietz, Vital ImagesRegression testing of the Vital Images’ medical imaging software was acontinual challenge. Poor product testability, challenging automationimplementation, tester shortages, and low process discipline contributed to anenvironment in which regression testing was often <strong>com</strong>pleted after the Beta siterelease. Even then, testing was in<strong>com</strong>plete and failed to cover the growingproduct feature scope. Alex Dietz describes how, through a stroke ofinspiration, he created a new team just for regression testing. Rather thanturning to outsourcing, he hired future users of his product. Alex describes theunique labor pool he used to staff the team, the costs incurred, personnellevels, metrics, and the management approach he adopted while still meetingFDA requirements for class II medical devices. Although the model Alexdescribes was applied to medical imaging software, it is not specific to hisindustry—and could be used successfully in yours.• Benefits of employing users for regression testing• A <strong>com</strong>parison of costs for traditional outsourcing vs. user testing• Measurements and metrics to evaluate customers as testersW12TEST TECHNIQUESRisk-Based Testing: From Theory to PracticeSusan Herrick, EDS Global Quality AssuranceWith mounting pressure to deliver high-quality applications at breakneckspeed, the need for risk-based testing has increased dramatically. In fact, nowpractically everyone involved in testing claims to be doing risk-based testing.But are you really? Drawing on real-life examples, Susan Herrick guides youthrough a six-step, risk-based testing approach: ambiguity analysis to reducethe risk of misunderstood requirements; risk analysis to determine testing scopeand develop the “right” testing strategy; systematic test design to supportdevelopment and execution of the “right” tests; requirements traceability tomeasure and manage test coverage; test metrics collection and reporting toprovide information that supports corrective action; and testing closedown to<strong>com</strong>municate any remaining quality risks and support effective decision-makingregarding application readiness. Susan also describes where the risk-basedtesting process fits into the project life cycle, regardless of the developmentmethodology selected for the project.• A definition of risk-based testing• A proven six-step process for risk-based testing• How to introduce this risk-based testing approach into your organizationW13TEST AUTOMATIONBusiness Rules-Based Test AutomationHarish Krishnankutty, Infosys Technologies, Ltd.All business applications implement business rules. Unfortunately, the rules canbe very dynamic due to changes in requirements by external organizations andinternal forces. Wise application designers and developers do not imbed theimplementation of specific business rules within applications but define, store,and maintain them as data outside the applications that use them. Likewise,wise testers now use a similar approach called business rules-based testautomation in which automated test scripts are written against the businessrules rather than against the application. This process incorporates technical<strong>com</strong>ponents such as a robust testing keyword library, a business-friendly userinterface, and automated script generators to accelerate the test automationwork and cover more business scenarios than with the conventional approach.Harish Krishnankutty guides you through the underlying concepts of businessrules-based test automation, describes a roadmap for implementing it, anddiscusses the benefits of the adoption of this unique approach.• Identify business rules used within your organization• How to provide better test coverage at lower cost• Increase confidence in the reliability of your systemsW14SPECIAL TOPICSTesting the Heathrow Terminal 5 BaggageHandling System (Before It Is Built)Roger Derksen, Transfer Solutions BVLondon Heathrow Terminal 5 will open in March 2008. This new terminal willhandle 30 million passengers a year, and all of these passengers will expecttheir baggage to ac<strong>com</strong>pany them on their flights. To achieve this end, a newbaggage handling system is being built that will handle more than 100,000bags a day. The challenge of testing the integrated software is related not onlyto its size and <strong>com</strong>plexity but also to the limited time that will be available totest the software in its actual environment. Roger Derksen explains the vital roleof factory integration testing using models that emulate the full system. Rogerdiscusses the limitations of these techniques and explains what can—andcannot—be done in the factory environment and what issues still must beaddressed on site.• A testing strategy for use on very large, <strong>com</strong>plex systems• How to use models for testing when physical systems are unavailable• Advantages and disadvantages of these testing techniquesCONFERENCE BONUS!One-Year Subscription to Better Software Magazine!STAREAST 2007 conferenceattendees receive a one-yearsubscription (12 issues) toBetter Softwaremagazine—the onlymagazine deliveringrelevant, timelyinformation so you cantackle the challenges ofbuilding better qualitysoftware, regardless ofyour role in the software developmentlifecycle. www.BetterSoftware.<strong>com</strong>If you are a current subscriber, your subscription will beextended an additional twelve issues.16 CALL 888-268-8770 OR 904-278-0524 TO REGISTER • WWW.<strong>SQE</strong>.COM/SEREG

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!