Home | About QAI | QAI Home Page | Federated Chapters
QuEST Chicago

Conference Home Page

QUEST Magazine

Full-Day Tutorials: Tuesday, April 29th


System Testing with an Attitude: An Approach that Nurtures Front-Loaded Quality
Nathan Petschenik, STS Consulting

Achieving success in system testing depends on technical excellence, it's true, but technical expertise alone is simply not enough.  To effectively prevent defects from reaching users, you need to approach the testing process with an attitude, an attitude that is about far more than just finding problems.  System test teams must nurture front-loaded quality - quality designed in and built in, not tested in later.  To accomplish this, system testers must exercise an influence on the project and project team's behavior that will prevent defects from ever reaching system test in the first place. This highly interactive tutorial will teach both the technical skills you need for a successful system test and will provide participants with concrete techniques that they can and must use to change attitudes.  You will learn to inspire project team behavior in a way that significantly impacts the quality of the software that reaches the system test team.

  • Learn the elements of a comprehensive system testing methodology
  • Practice architecting and designing system tests
  • Understand Data collection and usage for technical excellence and front loaded quality

About the instructor ...
As Chief Consultant for STS, Nathan Petschenik's career includes significant leadership experience in all phases of system development and testing.  He is an expert in Independent Verification and Validation (IV&V) methodologies and his paper, "Practical Priorities in System Testing," is considered to be a milestone in the science of software testing.  Prior to STS Consulting, Nathan held senior positions at Bell Labs, Bellcore, and Telcordia.  He is the author of System Testing with an Attitude.


 Back to top


Proactive Testing: Putting Agile Test-Driven Development on Steroids
Robin F. Goldsmith, JD, Go Pro Management, Inc.

Traditional testing is reactive; struggling uphill after all the possible errors have been made.  Agile test-driven development writes tests prior to coding, continually reviews code through pair programming, and emphasizes  frequent "acceptance" (integration) testing of small code implementations, all of which help produce cleaner program code quicker.   As much of an improvement as this is, Agile test-driven development could do even better by also applying concepts and techniques of the powerful Proactive Testing process.  Proactive Testing identifies numerous test conditions that traditional and test-driven approaches ordinarily overlook, including up to two-thirds of showstoppers and smaller issues that cause much of the extensive rework which terms like "refactoring" tend to obscure.  Following the CAT-Scan Approach, this interactive workshop describes a Proactive Testing model and outlines methods that enable Agile, and other, development methodologies to deliver far better systems even quicker and cheaper, while also helping overcome traditional user, manager, and developer resistance to testing.  Exercises will be included to enhance the learning process.

  • Understand the advantages and limitations of Agile
  • Learn the basics of Proactive Testing
  • Reveal ordinarily-overlooked test conditions

About the instructor...
Robin F. Goldsmith, JD has been President of Go Pro Management, Inc., consultancy since 1982.  He works directly with and trains business and systems professionals in requirements, quality and testing, metrics, ROI, software acquisition, and project and process management.  Previously he has been a developer, systems programmer/DBA/QA, and project leader with the City of Cleveland, leading financial institutions, and a "Big 4" consulting firm.  Member of the IEEE Software Test Documentation Std. 829 Revision Committee and formerly International Vice President of the Association for Systems Management and Executive Editor of the Journal of Systems Management, Robin is the author of the Proactive Testing methodology and the recent Artech House book, Discovering REAL Business Requirements for Software Project Success

Back to top 


Making Test Automation Live Up to Its Promises - SOLD OUT!
Bob Crews, Checkpoint Technologies, Inc.

Decrease testing time!  Increase requirements coverage!  Improve your QA process!  These are but a few of the promises of test automation.  So why are so many organizations struggling, and often failing, in their efforts to implement an effective automation process?  When trying to determine whether or not to automate why is the test case analyzed and the test requirements ignored?  Why do organizations base their automated processes on manual tests?  This one-day, highly-interactive tutorial will present "tried and true" implementation strategies covering both methodologies and technical tips and techniques (regardless of the automation solution you are using).   You will learn an approach utilizing Requirements Based Testing and Risk Based Analysis which will significantly increase your effectiveness in implementing test automation.  This tutorial will present code design examples designed to decrease automated test development cycles and increase the value of test automation engineers.

  • Understand the anatomies of a "test case" and "test requirement" and their influence on automation.
  • Discuss the benefits of using Requirements Based Testing and Risk Based Analysis approaches in developing an automation strategy
  • Discover code design specifications for highly-efficient and effective automated processes

About the instructor...
Bob Crews, President of Checkpoint Technologies, is a consultant and trainer with over eighteen years of IT experience including full life-cycle development involving development, requirements management, and testing.  He has consulted and trained for over 160 different organizations in areas such as effectively using automated testing solutions, implementing automated frameworks, and developing practices which ensure the maximum return-on-investment with automated solutions.  Bob has presented at numerous conferences and user groups throughout the world including QAI, EuroStar (Copenhagen), and LatinStar (Mexico City).  Bob was selected as one of the top five speakers at the QAI Annual Software Testing Conference in 2004.

Back to top


Scenario Based Requirements Management
Marcia Stinson, Quality Lifecycle Solutions

In this tutorial, Marcia will discuss the requirements management process and the role that scenarios play in that process.  All phases of requirements development from user requirements to detailed requirements will be covered.  In particular, Marcia will discuss how scenarios ensure that requirements are robust and document errors and exceptions that might occur.  Scenarios also ensure that relationships between requirements are considered and they provide a jumpstart to the next phase of requirements development.  Scenarios often become the basis for testing at all levels and assist in ensuring that traceability exists between requirements and between requirements and tests.  Finally, scenarios document how external requirements (i.e. business rules, regulations) affect the end user.  Several examples of scenario development will be presented and the relationship of scenarios to requirements and to test plans will be illustrated.  We will discuss how this process results in requirements that are at the appropriate level of detail which in turn produces clear test plans to support the requirements.  During the tutorial, you will participate in set of exercises designed to reinforce the concepts being taught.  You will take a real life example and develop scenarios at the user level, system level, and finally the detailed design level.  You will also develop test plans for each of these levels from the scenarios.  Finally, you will learn how the use of scenarios leads to a concrete set of development tasks that can be placed into a development schedule that is directly tied to requirements.  Be a hero to your customer and learn how to use scenarios to manage requirements.

  • Learn how scenario based requirements support the requirements process at all levels
  • Understand the relationship between requirements, scenarios, and test plans
  • Practice the development of scenarios and the resulting test plans

About the instructor...
Marcia Stinson is an experienced system and software development engineer, well versed in managing and leading teams involved in large complex projects.  She has a proven track record of developing and delivering process and software tool related training.  Marcia served as Director/Vice President of Professional Services at Telelogic prior to joining the other partners at QLS.  She was instrumental in organizing and streamlining the organization into a vital revenue producer.  Since joining QLS, Marcia has been the driving force behind the creation of a requirements management methodology process and training.


Back to top


Software Verification and Validation for Practitioners and Managers
Steven Rakitin, Software Quality Consulting, Inc.

Applying proven software verification and validation techniques improves quality and helps to meet aggressive time to market goals.  From firsthand experience in working with over 100 companies in several industries, Steve has found that basic software verification and validation activities are not well understood and are not applied consistently. He often sees wide variances in overall effectiveness among those organizations that have Software QA and Testing groups. Based on his book, Software Verification and Validation for Practitioners and Managers, Steve will present a basic set of software verification and validation (V&V) activities and provide a foundation in the skills needed to be effective in delivering high quality software in a timely manner. Software verification techniques including Peer Reviews, Unit Testing, and Integration Testing will be discussed. You will also learn about alternative techniques for expressing requirements in a manner that improves testability. Consideration of software validation and testing principles along with effective ways to plan, document, and execute the testing process will be included in the presentation.  Interactive exercises will be used to illustrate key activities.

  • Review basic Verification and Validation principles, activities, and techniques.
  • Learn new requirement techniques to improve testability.
  • Participate in V&V learning activities.

About the instructor...
Steve Rakitin has over 30 years experience as a software engineer and quality manager.  He has written extensively on the subject of software quality and has authored a book entitled Software Verification & Validation for Practitioners and Managers.  Steve helped to write the first IEEE Software Engineering Standard for Software Quality Assurance Plans and is currently a member of the IEEE Standard 1012 (Software Verification & Validation) Working Group.  He has earned certifications from the American Society for Quality (ASQ) as a Software Quality Engineer (CSQE) and Quality Auditor (CQA).  Steve is a member of the IEEE Computer Society, the ASQ Software Division, and is on the Editorial Review Board for the ASQ Journal Software Quality Professional.  As President of Software Quality Consulting, Inc., he works with clients who are interested in improving the predictability of their development processes and the quality of their products.

Back to top

Events: Managers' Workshop | Tutorials: Monday | Tutorials: Tuesday | Certification Courses & Exams | Exhibitor EXPO | Book Store & Signing Networking Events

Quality Engineered Software & Testing (QUEST) Conference - Copyright © 2008