 |
Software Dimensions and The International Institute for Software Testing Present PSQT/PSTT 2001 North |
|
|
|
Tutorials:
Series W
|
You must specify which tutorial you wish to attend (W1 through W2) Tutorials marked with (CSTP) will count as one day of training towards the requirements for the Certified Software Testing Professional |
| W1 | Discovering REAL Requirements for Web and eBusiness Systems (Intermediate) (CSTP, #5) | Robin F. Goldsmith JD |
| W2 | A
Methodology for Software Test Automation (Intermediate) (CSTP, #6) |
Elfriede Dustin |
Or PSQT/PSTT Conference Sessions
| Keynote | Howard Rubin |
| How Do You Know When You Are Done Tesing? | Scott Jefferies |
| Topic to be Determined | Mark Blackburn |
| Common Mistakes in Software Testing | Dorothy Graham |
| Project Out of Control? 10 Easy Metrics You Can Begin Using Today | Judy Bamberger |
| 16 Track Presentations | |
| The Software Quality Summit |
Series M - Monday, October
8, 2001
Series T - Tuesday, October
9, 2001
Series H - Thursday,
October 11, 2001
Series F - Friday, October
12, 2001
W1: Discovering REAL Requirements for Web and eBusiness Systems (Intermediate) (CSTP, #5)
Robin F. Goldsmith JD
This tutorial counts as one day of training towards the Certified Software Test Professional requirements.
Web sites
seem simple. That’s a strength. It’s also a trap. Just ask the “dot.bombs” that failed in
droves. Many of them built seemingly fine Web sites that people either didn’t visit
or visited and left, never to return. Even
for conventional organizations, Web and eBusiness success depends mainly upon accurately
understanding business and user requirements as well as Web-specific technology
requirements that the Web site must satisfy. That’s
not simple; and the illusion of simplicity vastly increases the risks that the rush of
Internet time will cause requirements errors. This
interactive workshop helps systems professionals become aware of requirements issues and
techniques to quickly discover the REAL requirements that Web systems must meet to provide
value. The workshop will also address
issues related to system requirements for non-web systems.
Exercises with a real case assist learning.
Web and
eBusiness technology issues that must be addressed.
Using the
Problem Statement tool to discover the real business requirements.
Techniques for
gathering and analyzing data in order to understand what is required.
Formats for
documenting and communicating business and functional requirements.
Requirements,
design, and value
What it takes
for Web success
Where
eBusinesses have tended to fail
Content, form,
and stickiness
Illusion of
simplicity and Internet time
Business
requirements, what produces value
Functional
specifications, external view
Use cases, how
actors interact with system
Recognizing
common traps
Iterative
development models and myths
DISCOVERING
BUSINESS REQUIREMENTS
Do users really
not know what they want?
What they say is
not what they really need
Why we must be
detectives, not gatherers
Finding the
value, or it’s not a requirement
Where
requirements fit in the process
Understanding
the business needs/purposes
Problem
statement tool to get on track
Identifying the
“real” problem and causes
Guidelines for
avoiding wrong turns
Scaling to
frequent small Web changes
Aligning
strategy, management, operations
Maintaining
customer focus to avoid silos
Technology
requirements vs. design
Data gathering
strategies and techniques
Management/supervisor
vs. worker views
Questions to ask
Business rules,
structured English
E-R, data flow,
flow, organization diagrams
Data models,
process maps
Performance,
volume, frequency statistics
Sample forms,
reports, screens, menus
WEB TECHNOLOGY
REQUIREMENTS
Browser
compatibilities
Configuration
capacities
Factors
affecting download time
Content and
navigation
Coordination
with traditional media
Keeping data
fresh and up-to-date
Dynamic vs.
static pages
Links to other
sites
Interfaces with
middleware
Accessing legacy
systems and data
Security issues
Load and
performance
DOCUMENTING
REQUIREMENTS
Formats for
communicating requirements
IEEE standard
for software requirements
Use cases,
strengths and warnings
7 guidelines for
documenting requirements
Top-level
requirements and project scope
Iterating to
avoid analysis paralysis
Conceptual
system design solutions
Expanding to
detailed deliverables
W2: A Methodology for Software Test Automation
(Intermediate) (CSTP,
#6)
Elfriede Dustin
This tutorial counts as one day of training towards the Certified Software Test Professional requirements.
This tutorial outlines the Automated Test Life-cycle Methodology, a structured process for designing, developing, executing and managing testing that parallels the System Development Life-cycle. It is based on the book titled "Automated Software Testing" co-authored by the instructor and published by AWL, ISBN 0-201-43287-0.
Automated Testing Life-Cycle Methodology
How test teams introduce an automated software test tool on a new project is nearly as important as the selection of the most appropriate test tool for the project. A tool is only as good as the process being used to implement the tool.
Over the last several years test teams have largely implemented automated testing tools on projects, without having a process or strategy in place describing in detail the steps involved in using the test tool productively. This approach commonly results in the development of test scripts that are not reusable, meaning that the test script serves a single test string but cannot be applied to a subsequent release of the software application. In the case of incremental software builds and as a result of software changes, these test scripts need to be recreated repeatedly and must be adjusted multiple times to accommodate minor software changes. This approach increases the testing effort and brings subsequent schedule increases and cost overruns.
The fallout from a bad experience with a test tool on a project can have a ripple effect throughout an organization. The experience may tarnish the reputation of the test group. Confidence in the tool by product and project managers may have been shaken to the point where the test team may have difficulty obtaining approval for use of a test tool on future efforts. Likewise, when budget pressures materialize, planned expenditures for test tool licenses and related tool support may be scratched.
By developing and following a strategy for rolling out and implement an automated test tool as part of the Automated Testing Life-cycle methodology, the test team can avoid having to make major unplanned adjustments throughout the test process. The tutorial "Automated Software Testing" addresses these various issues and their solutions.
The ATLM describes how and where "Automated Software Testing" fits into the system development life-cycle.
This tutorial will cover the following topics:
Various companies throughout the world have adopted the ATLM and incorporated it into their project.
Learning Objective
Elfriede Dustin is a SQA Certified test engineer and has supported test efforts for a multitude of applications. She is frequently a speaker at various Quality Assurance and Software Test Conferences. Elfriede has a BS degree in Computer Science and has performed as a Computer Systems Analyst/Programmer developing software applications and utilities, process and data modeling using CASE tools, and system design simulation models.
In support of software test efforts, Elfriede has been responsible for implementing automated test, or has performed as the lead consultant guiding the implementation of automated software test. Elfriede has lead the successful rollout of automated testing tools at three companies, and has applied her rollout strategy on over nine different projects.
Elfriede Dustin is the lead author of the best-selling book "Automated Software Testing", published by Addison-Wesley Pub Co; ISBN: 0201432870, July 1999. The book has been getting excellent reviews throughout the testing community (see also www.amazon.com).
Top of Page Tutorials: Series W
