 |
Software Dimensions and The International Institute for Software Testing Present PSQT/PSTT 2001 North |
|
|
|
Tutorials:
Series F
|
| F1 | Risk-Based
Testing (Intermediate) (CSTP, Elective) |
Robin F. Goldsmith JD |
| F2 | Writing Testable Requirements (Basic) (CSTP, #5) |
Dr. Magdy Hanna |
| F3 | Writing
Test Plans
(Intermediate) (CSTP, #3) |
Leslie Segal |
| F4 | Test Design Based on Use Cases (Intermediate) (CSTP, #5) |
Patrick Johnson |
| F5 | Principles of Software Test Automation (Basic)(CSTP, #6) | Jamie Mitchell |
| F6 | Effective
Test Management (Intermediate)(CSTP, #3&4) |
Denis Meredith |
Series M - Monday, October
8, 2001
Series T - Tuesday, October
9, 2001
Series W - Wednesday,
October 10, 2001
Series H - Thursday,
October 11, 2001
F1: Risk-Based Testing (Intermediate) (CSTP, Elective)
Robin F. Goldsmith JD
Testing is our primary means of
reducing risks related to systems and software. By
identifying and prioritizing risks, we can make sure that limited time and resources are
used to test the most important things. After
examining the elements of risk and classical means for dealing with it, attendees will
review three separate approaches for identifying risks:
the traditional project management perspective, conventional testing which is
reactive to development, and Proactive TestingÔ that drives development. Exercises
enhance learning by allowing participants to practice applying practical techniques to
realistic examples.
Participants will learn:
Risks that
project management tend to focus on.
Reactive risk
prioritization approaches commonly practiced in the testing community.
Proactive
TestingÔ methods to identify commonly overlooked major risks.
Scaling the
risk analysis to the size of problem at hand.
NATURE AND
IMPORTANCE OF RISK
Murphy’s
Law; O’Brien’s Law
Relation of risk
to software and testing
Elements of risk
Business impacts
from systems and projects
Direct and
indirect forms of injury
Management and
technical risks
Window of market
opportunity
Effects of
delivering poor quality
Software factors
that increase likelihood
Classical
risk-reduction techniques
Risk-based
testing strategy
Traditional
checklists for project managers
Late, over
budget, poor quality
Lack of
management support
Shifting
priorities
Organizational/strategic
change
Demand fails to
materialize or is too great
Staffing
difficulties and interruptions
Vendor
nonperformance
Relying on new
technologies
Overtaken by
competitors’ innovations
Poor reviews
Fraud, security
breaks, and sabotage
Software
risks--or just poor management
Changing
requirements and scope creep
Poor estimates
CONVENTIONAL
TESTING APPROACHES
Evaluating risks
of the intended tests
Why this
approach is reactive
Strengths and
weaknesses
Difficulties
communicating importance
Translating into
business outcomes
PROACTIVE
RISK-BASED TESTING
Advantages of
being truly proactive
Prioritization
demands knowing the choices
Proactive
TestingÔ Life Cycle
Structured model
of test planning
Multiple levels
of risk analysis
Project-level
proactive risk analysis
Involving all
the stakeholders
Identifying
overlooked project-specific risks
Prioritizing and
clustering
Defining tests
that reduce the key risks
Letting testing
drive development
Gaining user,
manager, developer support
Identifying and
analyzing lower-level risks
Differentiating
user and technical views
Checklists to
detect common risks
Risk analysis in
test designs and test cases
Deciding which
tests to emphasize
Risks of not
testing some things
Metrics to
monitor effectiveness
Improving over
time
Top of Page Tutorials: Series F
F2: Writing Testable Requirements (Basic) (CSTP, #5)
Dr. Magdy Hanna
This tutorial counts as one day of training towards the Certified Software Test Professional requirements.
This one-day course is essential for test and quality professionals, requirement engineers, business and system analysts and everyone who is involved in writing, validating and testing requirements. It covers details on how to document different types of requirements in a form that is testable. The course adopts a model-driven requirement process. It is based on the instructor’s philosophy of using models to assure completeness, correctness, testability, and precession of requirements. The course will also discuss the elements of requirement management process.
- Learn how models can tremendously improve the testability of requirements
- Learn how to identify test scenarios for model-based requirements
- Learn the elements of a requirement management process and learn how to build your own process
Types of requirements
Requirement traceability
Functional Vs quality requirements
Documenting quality requirements
Assessing the quality of software requirements
Forms of requirements
2. The
Requirement Management Process
3. Models for
Exploring and Refining Requirements
Data models
Process models
Use Cases
State Models
Dr. Magdy Hanna, is a recognized educator, speaker and consultant in several related areas of software engineering. Dr. Hanna, who is the president of Software Dimensions Consulting and Training, brings over twenty years of experience with building and maintaining software systems. As an assistant professor at the University of St. Thomas, he teaches graduate courses on several software engineering topics. He developed new approaches and methods in software development including the Unified Data Model (UDM), the Data-Driven Object Model (DOM), and the Software Quality Engineering Methodology (SQEngineer). Dr. Hanna holds a Ph.D. and a Master in Computer and Information Sciences from the University of Minnesota. The methodology was developed by Dr. Magdy Hanna and is used for several small to medium size projects.
Top of Page Tutorials: Series F
F3: Writing Test Plans (Intermediate)(CSTP, #3)
Leslie Segal
This tutorial counts as one day of training towards the Certified Software Test Professional requirements.
This tutorial
provides an introduction to writing test plans. Test
plans are the roadmap for testing. Without
good test plans, what’s been tested or not tested may be unknown, how to repeat a
test may be difficult to determine, expected results may be ambiguous or undefined, and
estimating risk can be hampered.
With this tutorial, you
will learn what constitutes a good test plan. We’ll
discuss industry standards for writing test plans as well as establishing company
standards. The various test plan types will
be introduced. We also discuss what to do
when time is short. Estimation techniques
will be covered just in case your manager wants to know how long it will take to write the
test plan. You’ll also get some practice
writing test plans.
Leslie Segal has published several articles on various test tools and has been a speaker at many testing conferences. She has also developed and taught several testing methodology and automation classes based upon her practical experience.
Top of Page Tutorials: Series F
F4: Test Design Based on Use Cases (Intermediate)(CSTP, #5)
Patrick Johnson
The seminar was designed to give testers a solid foundation in today’s technology like use cases and helps them understand how to perform test case design based on use cases. It begins with an overview of the concepts of use cases and different types of testing required for today’s applications. The seminar also shows how a use case is converted to other artifacts that are important for test design. The primary content of the course includes detailed instruction and hands-on exercises in converting use case models to test case models. Patrick Johnson has experiences ranging from modeling and analysis, requirements gathering to software quality automation, which enables him to provide expertise in each phase of the development and testing lifecycles… a unique skill set not common to the industry. Patrick was awarded the Quality Award by Shell’s management group in recognition for his innovative concepts and procedures that directly affected QUALITY.Top of Page Tutorials: Series F
Tutorial #F5 (Friday 8:30 - 4:30 p.m.)
F5: Principles of Software Test Automation (Basic)(CSTP, #6)
Jamie Mitchell
This tutorial counts as one day of training towards the Certified Software Test Professional requirements.
Abstract functionality
Jamie L. Mitchell is highly skilled with the implementation of software test automation tools from the major vendors and developed a supporting infrastructure to significantly increase the flexibilty, ease of use and efficiency of the tools. Jamie was awarded the Master of Computer Science Degree from Lehigh University, is a QAI Certified Software Test Engineer, an instructor and board member for IIST, and a contributing editor for the Journal of Software Testing Professionals.Tutorial #F6 (Friday 8:30 - 4:30 p.m.)
F6: Effective Test Management (Intermediate) (CSTP, 3&4)
Denis Meredith
This tutorial counts as one day of training towards the Certified Software Test Professional requirements.
This one-day tutorial will
provide a foundation for people who manage software development test efforts. It will describe a standards-based testing process
that can be applied to any software development life-cycle.
The steps required for preparing to test, executing tests, and evaluating
the results of testing will be discussed in detail. Finally,
some simple steps to follow to get started applying the principles covered in the tutorial
will be provided.
Outline
I.
Introduction
-
Definitions
-
Experiences
II.
The
Testing Process
-
Standards-Based
-
Levels of Testing
-
Test Products
-
Risk Management
III.
Test Preparation
-
Test Planning
-
Test Scheduling
-
Resource
Requirements
IV.
Test Execution
-
Test environment
-
Test Supports
-
Test Scripts
V.
Test
Evaluation
-
Defect Tracking
-
Test Reporting
-
Process Measurements
VI.
Conclusion
-
Summary
-
Action Plan
- Why management of testing is important
- How to develop test plans and test cases that support meeting customer needs
- How to prepare for test execution
- How to evaluate the results of testing and the test process
- How to work and communicate effectively within the organization
- How to use testing to manage quality risk
About the
Instructor:
Denis Meredith is an independent
consultant, concentrating in the areas of Software Testing and Quality Assurance; Tools
Selection and Implementation; and Project Selection, Scheduling, and Management. He has often been asked to speak on these and
other software engineering topics for various groups such as the DPMA, QAI, ACM, ASM,
CIPS, STSC, and EDPAA chapters and conferences. Mr.
Meredith has conducted testing, project management, metrics, and estimation seminars
throughout the United States, Canada, Mexico, Europe, and Australia.
Denis has served in several different organizations since entering the software
field in 1969. He has performed a variety of
work, beginning as a programmer and moving through a number of assignments of increasing
responsibility, including managing teams of developers, all development, managing an
organization’s data center, and information systems manager. Denis was employed by a software vendor and
functioned as product manager, product support manager, and finally as regional general
manager.
Mr. Meredith has been a member of IEEE Unit Test Standard, Life Cycle Process Standard, Software Productivity Metrics Standard, and CASE Tool Evaluation and Selection Standard working groups. He holds CCP, CSTE, and CQA certificates. Denis has had articles published in Data Management, Systems Development, System Builder ,and Software Quality Professional magazines and has written articles for Auerbach’s Data Processing Management series.
Top of Page Tutorials: Series F
