sss ssss rrrrrrrrrrr
ssss ss rrrr rrrr
sssss s rrrr rrrr
ssssss rrrr rrrr
ssssssss rrrr rrrr
ssssss rrrrrrrrr
s ssssss rrrr rrrr
ss sssss rrrr rrrr
sss sssss rrrr rrrr
s sssssss rrrrr rrrrr
+===================================================+
+======= Testing Techniques Newsletter (TTN) =======+
+======= ON-LINE EDITION =======+
+======= April 1999 =======+
+===================================================+
TESTING TECHNIQUES NEWSLETTER (TTN), Online Edition, is E-mailed monthly
to support the Software Research, Inc. (SR)/TestWorks user community and
to provide information of general use to the worldwide software quality
and testing community.
Permission to copy and/or re-distribute is granted, and secondary
circulation is encouraged by recipients of TTN-Online provided that the
entire document/file is kept intact and this complete copyright notice
appears with it in all copies. (c) Copyright 2003 by Software Research,
Inc.
========================================================================
INSIDE THE APRIL 1999 ISSUE:
o QW'99 Update: Sponsors, Exhibit Vendors
o New Report Available: Improvements to the Trace Assertion Method,
submitted by Doris Burns
o TestWorks Corner: Hot Items for TestWorks Users
o QW'99 Conference Tour -- Technical Tracks
o Year 2000 Problem: Probability of Occurrence
o Testing Techniques Newsletter, Online Edition: A Review by Danny
Faught
o The Art of Training Testers, by Romilla Karunakaran
o Proposal for Quality Grades For Software Component Source Code
Packages, by Frank Ackerman
o Parnas and Brooks to Speak At Mills Memorial Colloquium
o On the Naming Of Ships and Computers
o TTN SUBMITTAL, SUBSCRIPTION INFORMATION
========================================================================
QW99 Update: Sponsors, Exhibit Vendors
As our Quality Week and Quality Week/Europe conferences continue to grow
we're pleased to point out some facts and events.
o The ACM has once again recognized the QW'99 and QWE'99 Conferences as
having attained "In cooperation with..." status via the SigSOFT
group.
o Software Development Magazine has been designated as the official
QW'99 Media Sponsor.
Non-commercial sponsors previously announced include:
o Bay Area Quality Assurance Association (BAQA)
o CNSS (Center for National Software Studies, previously the National
Software Council)
o NASA's Software Assurance Technology Center (STAC)
Commercial sponsors previously announced include (in alphabetic order):
o Capital One
o Interim Technology
o Rational Software Corporation
o Software Research, Inc.
o Testmasters, Inc.
Lastly, here is a current list of the companies (in alphabetic order)
whose products and services will be on display at the 2-day QW'99 Tools
and Services Exhibition:
AutoTester; AZOR, Inc.; Capital One Services; Cisco Systems, Inc.;
Computer Associates International; Compuware; CS VERILOG; Cyrano, Inc.;
Data Dimensions; ErgoLight; Hall Kinion; Information Balance, Inc.;
Interim Technology; Intrinsa; KeyLabs; McCabe & Associates; Microsoft;
Performance Research, s.r.l. (ITALY); Q-Labs, Inc.; Quantitative
Software Management, Inc.; Software Emancipation Technology; Rational
Software; Soffront Software; Software Development Technologies; Software
SETT Corporation; Software Quality Engineering; Software Research, Inc.;
Sunpower Computing; Technology Search International, Inc.; Teradyne
Software & Systems Test; Testmasters, Inc.; The International Institute
for Software Testing.
========================================================================
Availability of New Report, by Doris Burns
Below is an abstract from a recently completed report by
McMaster University's Software Engineering Group. If you
are interested in receiving this report, please e-mail your
request to me. My email address is:
burns@raid.cas.mcmaster.ca.
Improvements to the Trace Assertion Method
for Software Engineering
Andrew C.P. Dookhan
CRL Report 372
March 1999
ABSTRACT: Many formal methods have been suggested for documenting
software work assignments, some are discussed in [19]. This thesis
presents a new version of Trace Assertion Method [1,10]. We refer to
this new version as ITAM. TAM originated in 1977, [1,2]. Although TAM is
sound, TAM specifications seem inappropriately complex. The complexity
of a specification is not proportional to the complexity of the concepts
being described. In this thesis we reintroduce TAM to document software
work assignments, (i.e. module interface specifications). This thesis
suggests improvements to TAM (ITAM) for programmers and specification
writers. In doing this we :- (a) allow specification method writers to
represent the state of an object, using sets. (b) view the collection of
objects implemented by one module, as a single object (refer to as a
primary object,) which may be composed of other objects. (c) presents
objects' state representation semantics and a syntax that is more in
tune with programmers' perceptions. (d) provide a tool that checks the
syntax describing the canonical representation of an object's state. (e)
provide commonly used predefined auxiliary functions to reduce redundant
mathematical notation. (f) provide predefined auxiliary functions to be
used when it is necessary to "check type" and "check availability" of an
object, before performing operations on an object. (g) provide a method
of abbreviating, long and duplicate, mathematical expressions. (h) use
tables which can be easily checked for completeness and consistency,
when we describe state changes of a module's objects, caused by
invocations of that module's programs, (operation tables). (i) show that
it is possible for ITAM to document polymorphic and non-deterministic
module specifications. (j) provide a common compact and systematic
document format for ITAM's module interface specifications.
In this paper we present a new symbolic approach to hybrid systems.
Hybrid systems are systems containing both, continuous and discrete
changing quantities. We model hybrid systems using hybrid automata:
Hybrid automata extend the classical notion of finite state machines by
combining differential equations to model the dynamic behavior of
systems with a finite control. In contrast to other approaches we
consider a hybrid automata as a generalization of differential equations
and develop the notion of a symbolic "closed form" solution of a hybrid
automata. A closed form solution is an expression which gives the value
of the quantities in question as a function of design parameters and
time. These solutions allow us to perform the verification of design
properties. We were able to detect design constrains on control systems
that other methods fail to detect. This paper gives the basic
definitions, algorithms, and an example to demonstrate the advantage of
the proposed approach.
========================================================================
TestWorks Corner: Hot Items for TestWorks Users
Here are several items that will be of interest to current and
prospective TestWorks users:
o The mid-April builds of our new CAPBAK/Web capture replay system are
now available for download. This is a beta release and users are
encouraged to forward comments. Go to:
<http://www.soft.com/Products/Downloads>.
o The latest SGI/IRIX builds of TestWorks are downloadable from the
WebSite. Now all of the Windows products and nearly all of the UNIX
products can be downloaded direct.
o LINUX support is beginning to be planned. We ask all users or
potential users who may want TestWorks available on the LINUX
platform to Email us at to indicate how soon the
need might be.
o If you want to be added to the regular TestWorks Software
Installation List (SIL) mailing please make the request to
. This monthly mailing has a wealth of current
pointers and other details about the TestWorks solution.
Complete information about TestWorks can be obtained by Emailing
.
========================================================================
QW'99 Conference Tour -- Technical Tracks
Last month we highlighted the Tutorials, Keynotes, QuickStarts and the
new BOFSs. This month, just a few short weeks before the QW'99 event,
we focus on the main technical tracks of the QW'99 Conference.
T E C H N O L O G Y T R A C K
Innovative software tools are always of interest, and we have in QW'99
four papers that point out some very good concepts: * Dr. Selim Aissi
and Ms. Wendi Hummel (Applied Dynamics International) "Automating Syntax
Testing: The Case of a Real-Time Simulation Tool (2T1)", * Mr. Kenneth
Nagin & Dr. Alan Hartman (IBM Research Laboratory in Haifa) "TCBeans
Software Test Tool Kit (2T2)", * Mr. Steven Toeppe & Mr. Scott Ranville
(Ford Motor Company) "An Automated Inspection Tool For A Graphical
Specification and Programming Language (8T1)", and, * Mr. John Kent
(CISS Ltd.) "Advanced Automated Testing Architectures (8T2)".
Tools are meant to be applied, and these two papers deal with automated
testing of high assurance systems: * Mr. Brian Miller (Teradyne)
"Automated Test Generation for Computer Telephony Systems (3T1)", and, *
Dr. Bettina Buth, Prof. Dr. Jan Peleska & Dr. Hui Shi (FB3 Informatik)
"Combining Methods for the Analysis of a Fault-Tolerant System (3T2)".
Systems, once built, sometimes continue to change, and it's important to
assure quality through maintenance testing, as these two papers point
out: * Mr. Ira D. Baxter, Mr. Andrew Yahin, Mr. Srinivas Nedunuri, and
Mr. Leonardo Moura (Semantic Designs) "Lowering Maintenance Costs by
Code Clone Removal (4T1)", and, * Mr. Christopher Agruss (Autodesk,
Inc.) "Automating Software Installation Testing (4T2)".
Embedded systems present particular problems, and we have two papers
that deal specifically with Windows CE issues: * Mr. Patrick Copeland
(Microsoft) "Approaches to Testing Componentization in the Windows CE
Operating System (7T1)", and, * Mr. Sergio Cherskov (Microsoft) "Testing
Windows CE 3.0 Real-Time Kernel (7T2)".
Web testing is a hot topic (see the sessions on E-Commerce below) and we
have four papers (two in Technology and two in Applications) that face
the question of testing WebSites: * Ms. Fan Yang, Mr. Trung Nguyen &
Mr. Anant Adiga (Sequent Computer Systems, Inc.) "A Web-based System
Testing Repository Model (6T1)", * Ms. Frances I. Medina (AT&T
Operational Technology Center) "Test Automation of a GUI WEB Based
Application: An Experience Developing Reusable Automated Testing (6T2)",
* Mr. Leon Slota (Neoglyphics Media Corporation) "Developing Load and
Performance Requirements for Web Sites (7A1)", and, * Mr. Sam
Guckenheimer (Rational Software Corporation) "Effective Testing for
Java-Based Web Software (7A2)".
While still a relatively new technology, data flow approaches deserve
serious consideration, to wit: * Mr. Bor-Yuan Tsai, Dr. Simon Stobart,
Mr. Norman Parrington & Dr. Ian Mitchell (University of Sunderland) "A
State-Based Testing Approach Providing Data Flow Coverage in Object-
Oriented Class Testing (9T1)", and, * Ms. Martina Marre, Ms. Monica
Bobrowski & Dr. Daniel Yankelevich (Universidad de Buenos Aires) "A
Software Engineering View of Data Quality (QWE'98 Best Paper) (9T2)".
A P P L I C A T I O N S T R A C K
Fault density methods promise clarity and accurate emphasis, as these
two papers describe: * Mr. Graham Thompson (InCert Software)
"Minimizing Testing While Maximizing Failure Detection (2A1)", and, *
Dr. Frank Ackerman & Ms. Cherie McKinney (Institute for Zero Defect
Software) "Measuring Fault Density in the Real World (2A2)".
Technology injection in critical complex systems always has been
difficult, but these six papers (two from the Tools and Solutions Track)
address this critical area from varying perspectives: * Mr. Ron Silacci
(Lucent Technologies, Inc.) "A Testers' Top 10 List (3A1)", * Mr.
Lorenzo Lattanzi & Mr. Mario Musmeci (Alenia Aerospazio) "Safety
Critical S/W Development for a Satellite Based Navigation System (8A1)",
* Mr. Rob Oshana (Raytheon Systems Company) "An Automated Testing
Environment to support Operational Profiles of Software Intensive
Systems (3S1)", * Ms. Lisa Boden & Mr. Jon Hagar (Lockheed Martin
Astronautics Company) "How to Build a 20 Year Successful Independent
Verification and Validation (IV&V) Program for the Next Millennium
(3A2)", * Mr. David Carman (Bellcore) "Event-Based Test Generation for
Distributed Systems (3S2)", and, * Mr. Matias Vierimaa, Ms. Minna
Makarainen & Mr. Atte Kinnula (VTT Electronics) "Improving DSP Software
Engineering Processes from the Testing Viewpoint (8A2)".
eCommerce draws continued attention, and some of the practicalities are
addressed in these two papers: * Dr. Steven Rabin (Interworld
Corporation) "eCommerce Performance Benchmarking -- Methodology and
Criteria (4A1)", and, * Mr. Federico Pacquing, Jr. (Techwave Inc.)
"Usability Testing in eCommerce Applications (4A2)".
OO methods and model-based testing are important applications areas, as
illustrated in these four papers: * Ms. Mei-Hwa Chen and Mr. Ming-Hung
H. Kao (SUNY Albany) "Investigating Test Effectiveness on Object-
Oriented Software -- A Case Study (6A1)", * Mr. Glen Xia (Deloitte
Consulting) "An Industrial Case Study of Quantitative Management for
Object Oriented Software Testing (6A2)", * Mr. Jon Hagar (Lockheed
Martin Astronautics Company) "Industrial Experiences in Establishing
Laboratories and Software Models to Effectively Execute Software Test
(9A1)", and, * Ms. Johanna Rothman (Rothman Consulting Group, Inc.)
"Using Quality to Drive Product Development Processes (9A2)".
T O O L S & S O L U T I O N S T R A C K
The tools and solutions track tries to focus attention to cases where
specific kinds of tools are put to effective use. Both generally, and
specifically to client/server applications, we have these four papers:
* Mr. Alan Ark and Sarah Ackroyd (Thomson Financial Services) "Euro: An
Automated Solution to Currency Conversion (2S2)", * Mr. Douglas Hoffman
(Software Quality Methods, LLC) "Test Automation Architectures; Planning
for Test Automation (2S1)", * Dr. Heesun Park (SAS Institute Inc.)
"Optimum Level of Test Automation for Client/Server Software (4S1)",
and, * Dr. Huey-Der Joseph Chu (National Defense Management College)
"Automating Client/Server Testing in the Real World (4S2)".
Requirements based testing -- always an important technology area -- is
addressed with these four papers: * Mr. Hanania T. Salzer (RTS Software
Ltd.) "ATRs (Atomic Requirements) Used Throughout Development Lifecycle
(6S1)", * Mr. Larry Apfelbaum and Mr. Steve Meyer (Teradyne, AT&T) "Use
Cases are Not Requirements (6S2)", Requirements II... * Mr. Mark
Charles (Vector Research, Inc.) "Testing a System With Dynamic
Requirements (8S1)", and, * Mr. Yuri Chernak (Valley Forge Consulting,
Inc.) "In-Process Validation and Improvement of Test-Case Effectiveness
(8S2)".
Real-world testing continues to grow in importance, as indicated in
these selections: * Mr. Jim Williams (CableData, Inc.) "Testing for Y2K
Compliance: A Case Study (7S1)", * Mr. E.L. (Ed) Safford III (Lockheed
Martin Tactical Aircraft System) "Development of an Integrated Real-Time
Avionics Software Testbed (9S2)", * Mr. Alain Kerbrat & Mr. Iulian Ober
(Verilog) "Automated Test Generation from SDL/UML Specifications (9S1)",
and, * Mr. Gunther Chrobok-Diening, Dr. Andreas Ulrich & Mr. Peter
Zimmerer (Siemens AG) "Test Architectures for Testing Distributed
Systems (7S2)".
M A N A G E M E N T T R A C K
Careers and the software quality culture must go hand in hand for things
really to work well: These four papers address differing aspects of
this important topic: * Mr. Tom Wissink (Lockheed Martin Mission
Systems) "Test Engineering -- A "Value Add" Career Path (9M1)", * Mr.
Roger M. Records (Boeing Commercial Airplanes) "Deploying SQA in Very
Small Projects (2M1)", * Mr. Mike Ross (Quantitative Software
Management, Inc.) "Size Does Matter: Continuous Size Estimating and
Tracking (2M2)", and, * Mr. Keith Stobie (BEA Systems, Inc.) "Creating a
Testing Culture (9M2)".
Software process issues are key to success in building CMM and similar
organizations, as pointed out by these papers: * Mr. Herb Krasner
(Krasner Consulting) "Using the Cost of Quality Approach for Software
(4M1)", * Mr. Michael Deck (Cleanroom Software Engineering, Inc.)
"Process Diversity: How I Stopped Worrying and Learned to Love Chaos
(4M2)", * Mr. Philip Lones (Lucent Technologies) "Revolutionary? A
Development Method That Works (7M1)", and, * Mr. Nick Borelli (Microsoft
Corporation) "Seizing Control of the Development Lifecycle (7M2)". At
the same time, it is good to focus specifically on CMM specifics, as is
done here with: * Mr. John N. Romanak (Bellcore) "Life as a CMM Level 5
Test Organization (3M1)", and, * Dr. Ilene Burnstein, Ms. Ariya Homyen,
Dr. Taratip Suwannasart, Mr. Robert Grom & Mr. Gary Saxena (Illinois
Institute of Technology) "Using the Testing Maturity Model (TMM) to
Assess and Improve Your Software Testing Process (3M2)".
Risk management is a management approach that is growing in importance,
and these two talks are not to be missed: * Mr. Stale Amland (Avenir
(UK) Ltd.) "Risk Based Testing and Metrics (6M1)", and, the ever popular
and dynamic * Mr. Tom Gilb (Result Planning Limited) "Risk Management
Technology: A Toolkit for Identifying, Documenting, Analyzing and Coping
with Project Risks (6M2)".
Finally, we have to learn from our experience, as illustrated in these
two talks: * Mr. James Bindas (Intel Corporation) "Tactical Improvement
Projects: Real-Life Lessons in Leading Change (8M1)", and, * Mr. Scott
Young "Them and Us: Communication between Development and Test (8M2)".
Complete information about QW'99 including online registration is
available from the Conference WebSite:
<http://www.soft.com/QualWeek/QW99>
or by Email to .
========================================================================
Year 2000 Problem: Probability of Occurrence
A recent Technical Report undertaken by the Software Productivity
Research Company, Burlington, Massachusetts, sought to assess the
probability of certain future outcomes, directly attributable to Y2K.
Year 2000 Problem Probability
Bad credit reports due to Year 2000 errors 70%
Cancellation of Year 2000 liability insurance 60%
Loss of local electric power (>1 day) 55%
Litigation against corporate officers 55%
Loss of regional electric power (>1 day) 40%
Loss of international telephone services 35%
Errors in 2000 tax reporting (1099 forms) 35%
Errors with social security payments 35%
Errors in first January paycheck 30%
Errors or delays in tax refunds 30%
Delays or cancellations of airline flights 25%
Loss of local telephone services 20%
Errors with motor vehicle records 20%
Manufacturing shutdowns (>1 day) 20%
Errors in bank account balances 15%
Corporate bankruptcy due to Year 2000 5%
Death or injury due to Year 2000 1%
========================================================================
Testing Techniques Newsletter, Online Edition: A Review
by
Danny Faught
<http://www.soft.com/News/TTN-Online> for back issues and email
subscription information.
TTN Online from Software Research, Inc. is the best that I've seen in
the category of what I call "commercial newsletters". Companies create
newsletters as marketing tools, but some are better than others at
providing useful general information relating to their field of
interest. I've let my name drop off of several other software vendor's
mailing lists, and when they realize I'm not sending any revenue in
their direction, they're happy to see me go. But I've been a TTN Online
subscriber for several years running.
You certainly get more than you pay for - the subscription is free, at
least in monetary terms. You agree to tolerate the announcements
related to the company's product offerings and the conferences sponsored
by SR/Institute. Maybe, just maybe, you even agree to read some of it.
Then in what's left you often find some good stuff relating to software
quality from some very reputable sources in the industry. Be aware,
though, that SR will use its TTN Online subscriber list to send
additional advertisements to you. In the spirit of the junk fax law,
after all, subscribers do have a prior business relationship with them.
But such ads only come infrequently, and not even at a volume that I've
bothered to catch them with my mail filter. For what I get from the
newsletter, I consider it well worth the costs.
The content of the newsletter includes random conference and seminar
announcements, humor, news from the Center for National Software Studies
and other industry news, and technical articles on software process,
quality assurance, and testing. I particularly remember a detailed
analysis of the Pentium FDIV bug by Boris Beizer that showed why it was
a software problem and why it should have been avoided.
TTN Online is now only available in electronic (ASCII) form.
Editor's Note: You can see this item as posted on this website:
<http://www.geraldmweinberg.com>.
========================================================================
The Art of Training Testers
by
Romilla Karunakaran
QA Consultant
bala450@worldnet.att.net
ABSTRACT: Few universities offer courses on software
testing and most courses available today tend to strum on
testing practices which are not in tune with the reality of
the software development world. Most software testers have
to acquire the skills while on the job and condense together
what seems to be the rightful art towards effective software
testing. Training people who are fresh to the software
testing field can be a challenge especially when the testing
manager has to ensure that the training is mutually
beneficial to the company as well and does not affect the
delivery of the current testing at hand.
It is a difficult and challenging process for anyone seeking to perfect
the art of software testing. Most experienced testers have acquired
their relevant expertise through years of experience working on software
development projects and familiarizing with the software development
process lifecycle. These testers might have frequently been witnesses to
a long and drawn-out process trying to implement strategies and test
plans in a world where the quality assurance process has often been
thought of as a side platter, more often a whiner. Throughout my career
as a software tester and consultant, I have seen software testing and
software testers viewed mostly as bystanders with no specific role or
responsibility to play in the development process other than to report.
The development team often does the follow-up with scant regard for the
need to include the opinions of the software tester who will too often
be able to offer quality and valuable insights towards the on-time
release of a bug-free product.
Software testing is an important component and function of the quality
assurance process. The implementation of a good testing process comes
with the institution of good project planning practices. This is very
much needed in large and complex projects especially client/server
projects where a series of skill sets in effective time management,
people management and client support are often required. In addition to
this, the versatile tester also meets deadlines; documents, reports and
manages the defects; and possesses excellent technical and testing
skills.
While some companies tend to take a subliminal approach towards
investing in training of software testers, there are many companies
today which do take a serious approach on the training of their software
testing personnel. These companies set up their own quality assurance
departments, and stipulate guidelines and standards on the
implementation of the quality assurance process during product
development. The proper institution of an effective testing process
within an organization however rests on the responsibility of top
management to acknowledge the need and importance of effective software
testing and the need to develop software that is testable.
The Issue with Novices
The recent demand for software testers have seen a flurry of individuals
moving into the software testing field. Many of these "testers" have had
no prior experience with the intricacies and demand in software testing,
and no conceptual background on testing methodologies. These testers
adopt the approach that what is required is a simple process of punching
the keyboard and reporting as many defects as they can find in the
application.
In reality, software testing is not that simple a process. What most of
these untrained testers fail to do is to be able to categorize the
nature of these defects appropriately and sieve out only defects that
are most important and critical. They frequently write poor reports with
little or no indication on how the defects were arrived at. Their verbal
and communications skills are also virtually nil. Thus it comes as no
surprise when the frustrated developer complains about reports which do
not tell him much about resolving the defects reported. Most of these
testers can gain the relevant experience in time but will not be
familiar to new testing challenges that may occur in changing
environments. They tend to perceive and adopt skills that are relevant
to their current environment and are not adaptable to the needs and
demands stemming from other environments.
This can present a problem as testers who are not growing to new
challenges are often not comfortable with the fast-changing demands of
the software development world. These people are most often slow in
responding to the new risks presented in software testing and tend to
fall out of line.
Getting the Right People for the Job
It can be a challenging task to identify the right people for the
position of software tester. Even grooming an experienced tester for a
new kind of testing position can be a difficult task especially when
this person feels he/she has acquired the relevant expertise need for
the testing field. Over the years, I have seen people from all walks of
life seeking to enter the software testing profession, a number with no
prior software testing experience. However, there are a few basic rules
that a software testing recruiter can adhere to when recruiting the
right person for the job.
Sometimes, the best testers can be the people who have no testing
experience before but who have a solid foundation in management and are
creative enough to find ways to solve problems. Those who are drawn into
this profession from a genuine motive, take easily to the testing field.
New comers to the software testing profession are receptive to the
various testing methodologies although they may have trouble absorbing
information that is on a higher level. Nevertheless, those new comers
who are self-motivated and study the intricacies of the discipline with
open arms often turn out to be the most resilient testers.
Incidentally, those who computer science backgrounds are usually
difficult to train as these people have already gotten used to a
preconceived notion on what is entailed in the software testing field.
The candidate with a computer science background is most often drawn
towards using this field as background knowledge in software testing. I
have noted automation testing specialists with programming background,
who program testing scripts using the SQA automation tool when these
scripts have already been defined by the robot. The continuous obsession
in "programming" test scripts designed by the SQA robot only defeats the
true purpose of testing with an automation tool.
The Training Program
It is important that organizations providing software testing services
internally or externally, identify and institute a comprehensive
training program for its testers. By mapping out a common body of
knowledge such as the one used by the Quality Assurance Institute (QAI)
of Florida, the organization should be able to determine the focal
points needed for training its new and existing testers. This should be
useful as it can also define the career path of the testers within the
organization as well. There should also be a grouping of the testers to
specific categories so that the required training programs can be
suitably identified for each of the individuals concerned. The grouping
of testers could be as follows:
1. Possesses no knowledge or experience in software testing
2. Possesses knowledge but no experience in software testing
3. Able to execute tasks but lacks quality and depth in performance
4. Able to execute tasks with efficiency; Possesses quality and depth in
performance
5. Is a Genius (Very efficient and is able to perform in a variety of
difficult situations)
It can be a difficult task defining the types of training programs that
would successfully groom testers. However, the basis for success is
first developing a valuable training program that defines what
objectives are sought by the testing organization and the type of skills
required to achieve these given set of objectives.
Software Testing is an art. There is always a conflict about the theory
and practice in the area of software testing and most often, testers
learn the hard way when it comes to perfecting the tools of the trade.
These testers not only gain familiarity in the areas assigned to them
but they also acquire confidence in their abilities. Those who undergo
training the difficult way often benefit by developing an eye for
solving problems as they come. These testers are also self-motivated,
disciplined, and take control and responsibility over the tasks assigned
to them.
Those who enter the field with no knowledge or prior experience in
software testing should be carefully guided and trained through a
mentor. This could be an effective way for the mentor to monitor the
work of the junior testers assigned to her/him. The student can then be
skillfully guided on the important aspects of testing in the field, what
techniques to employ and when. The mentor should however be familiar
with the testing techniques, both theory and practice, before
undertaking the task of training and guiding junior testers.
Organizations that recognize the important of software testing in the
software development process should also ensure that testers receive
sufficient amount of training based on their skill sets. Training can be
undertaken within the premises of the organization or otherwise.
However, there should not be an over-reliance on commercially available
training programs that continually strum on over-analytical testing
methods which do not meet well on the practical side of the testing
field. Moreover, these training programs are spaced mostly over a two or
three-day period, making it difficult for the tester to actually acquire
any useful techniques. However, sending testers for group meetings and
conferences can be an added advantage as it allows for an exchange of
ideas and practical techniques on testing. This could turn out more
beneficial than a theory-oriented class that emphasizes a series of
concepts and no means to solve the typical problems at hand in an actual
testing environment.
The responsible tester will however engage in his/her own self-study
programs, gleaning all relevant information from books and journals.
Reading will help supplement the testers' own body of knowledge and it
is up to the individual to self-educate on the noteworthy areas raised
if any. Few books truly provide specific test cases which hinge on the
practical side of software testing and there are those which imply the
most perfect way of software testing without actually defining the ropes
for moving forth given an environment facing a lack of resources. A
process of self-education is noteworthy but few testers unfortunately
find the time or the opportunity to keep up on reading materials.
Peer reviews and inspections are however an excellent means of training
software testers as it ensures that testers commit more quality in the
testing work. Testers would naturally place more care and quality in
their work if they know that their work is going to be examined by
higher authorities. There should be a review of test cases and test
plans so that there will be communication to the testers in terms of
what should or should not be spelt out in their testing efforts. It also
gives them some direction and path in their testing efforts.
Organizations should conduct regular reviews and inspections as these
can highlight and resolve the issues and problems presented to both the
testing and development teams. On a broader scale, peer reviews and
inspections are time-consuming but they are productive and ensure that
the organization is establishing and maintaining a certain standard and
compliance in its software process.
Training Means Perfection
Developing a suitable training program for the testing team is a
challenge, as it requires the organization to identify the key areas in
need of attention. However, an organization that has been successful in
implementing testing standards will be graced with a testing team that
is capable of undertaking difficult and varied tasks assigned to them
and adapting their skills appropriately when the situation calls for it.
Testers who are organized and systematic tend to be flexible in adapting
their test plan and testing efforts in response to the variable changes
typical of a software development environment.
A well-trained tester has a knack for undertaking the demands of the
project at hand and the ability to rely on concrete evidence rather than
mere hearsay. Successful testers not only possess excellent
communication skills, but are also keen to experiment and are uncanny in
noting defects relevant to the testing effort at hand. The quality and
success of a testing project depends very much on the dynamism and
ability of its testing team. By identifying the key problem areas of the
team and supplementing this with a training schedule, the successful
testing manager will be able to develop and nurture the required testing
skills and subsequently, contribute to the demands of a somewhat chaotic
and dynamic software development environment.
========================================================================
Proposal for Quality Grades For Software Component Source Code Packages
submitted by
Frank Ackerman (fackerman@aol.com)
An IEEE/CS study group has been working for some time now on a proposal
for an international standard for quality grades for software component
source code packages. To support their efforts the IEEE Computer
Society has established a web site at:
<http://hopper.computer.org/qgscscp.nsf>
Check it out! Participation in this effort is open to all interested
parties.
========================================================================
Parnas and Brooks to Speak At Mills Memorial Colloquium
The Mills Memorial Colloquium is an affiliated meeting as part of ICSE
1999, May 18, 1999, Los Angeles, CA.
The ICSE-affiliated colloquium "Science and Engineering for Software
Development" has been organized in honor of Dr. Harlan D. Mills (1919-
1996) and as a recognition of his enduring legacy to the theory and
practice of software engineering. This year's event will feature keynote
addresses by David Parnas and Fred Brooks. The colloquium will take
place in Los Angeles on May 18, 1999, the day before the opening of the
23rd International Conference on Software Engineering.
The program includes invited presentations, refereed papers, and a panel
session. The invited speakers, in addition to Professors Brooks and
Parnas, include Jesse Poore and Carmen Trammell. The panel session, to
be chaired by Professor Victor Basili, will feature Terry Baker, Susan
L. Gerhart, and Al Hevner. The first annual "Harlan D. Mills Practical
Visionary Prize" award will be presented. This award is given to an
individual who has demonstrated a long-standing and meaningful
contribution to both the theory and practice of the information
sciences.
Details at: <http://www.isr.wvu.edu/mills/>
Register at: <http://sunset.usc.edu/r1/icse99>
========================================================================
On the Naming Of Ships and Computers
As you're aware, ships have long been characterized as being female
(e.g., "Steady as she goes" or "She's listing to starboard, Captain!").
Recently, a group of computer scientists (all males) announced that
computers should also be referred to as being female. Their reasons for
drawing this conclusion are:
1. No one but the Creator understands their internal logic.
2. The native language they use to communicate with other computers is
incomprehensible to Everyone else.
3. The message "Bad command or file name" is about as informative as,
"If you don't know why I'm mad at you, then I'm certainly not going
to tell you
4. Even your smallest mistakes are stored in long-term memory for later
retrieval.
5. As soon as you make a commitment to one, you find yourself spending
half your paycheck on accessories for it.
However, another group of computer scientists (all female) think that
computers should be referred to as if they were male. Their reasons
follow:
1. They have a lot of data, but are still clueless.
2. They are supposed to help you solve problems, but half the time they
ARE the problem.
3. As soon as you commit to one you realize that, if you had waited a
little longer, you could have obtained a better model.
4. In order to get their attention, you have to turn them on.
5. Big power surges knock them out for the rest of the night.
Editors note: Does anyone remember how to spell androgynous?
========================================================================
------------>>> TTN SUBMITTAL POLICY <<<------------
========================================================================
The TTN Online Edition is E-mailed around the 15th of each month to
subscribers worldwide. To have your event listed in an upcoming issue
E-mail a complete description and full details of your Call for Papers
or Call for Participation to "ttn@soft.com".
TTN On-Line's submittal policy is as follows:
o Submission deadlines indicated in "Calls for Papers" should provide at
least a 1-month lead time from the TTN On-Line issue date. For
example, submission deadlines for "Calls for Papers" in the January
issue of TTN On-Line would be for February and beyond.
o Length of submitted non-calendar items should not exceed 350 lines
(about four pages). Longer articles are OK and may be serialized.
o Length of submitted calendar items should not exceed 60 lines (one
page).
o Publication of submitted items is determined by Software Research,
Inc. and may be edited for style and content as necessary.
DISCLAIMER: Articles and items are the opinions of their authors or
submitters; TTN-Online disclaims any responsibility for their content.
TRADEMARKS: STW, TestWorks, CAPBAK, SMARTS, EXDIFF, Xdemo, Xvirtual,
Xflight, STW/Regression, STW/Coverage, STW/Advisor, TCAT, TCAT-PATH, T-
SCOPE and the SR logo are trademarks or registered trademarks of
Software Research, Inc. All other systems are either trademarks or
registered trademarks of their respective companies.
========================================================================
----------------->>> TTN SUBSCRIPTION INFORMATION <<<-----------------
========================================================================
To SUBSCRIBE to TTN-Online, to CANCEL a current subscription, to CHANGE
an address (a CANCEL and a SUBSCRIBE combined) or to submit or propose
an article, use the convenient Subscribe/Unsubscribe facility at
<http://www.soft.com/News/TTN-Online>. Or, send E-mail to
"ttn@soft.com" as follows:
TO SUBSCRIBE: Include in the body the phrase "subscribe {your-E-
mail-address}".
TO UNSUBSCRIBE: Include in the body the phrase "unsubscribe {your-E-
mail-address}".
QUALITY TECHNIQUES NEWSLETTER
Software Research, Inc.
1663 Mission Street, Suite 400
San Francisco, CA 94103 USA
Phone: +1 (415) 861-2800
Toll Free: +1 (800) 942-SOFT (USA Only)
Fax: +1 (415) 861-9801
Email: qtn@soft.com
Web: <http://www.soft.com/News/QTN-Online>
## End ##