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 =======+
+======= June 1997 =======+
+===================================================+
TESTING TECHNIQUES NEWSLETTER (TTN), On-Line Edition, is E-mailed
monthly to support the Software Research, Inc. (SR) user community and
provide information of general use to the worldwide software testing
community.
(c) Copyright 1997 by Software Research, Inc. Permission to copy and/or
re-distribute is granted to recipients of the TTN On-Line Edition
provided that the entire document/file is kept intact and this copyright
notice appears with it.
========================================================================
INSIDE THIS ISSUE:
o My Worst Testing Nightmare ... by Gebhard Dunst
o Your Worst Testing Nightmare: The Contest!
o Call for Participation: Quality Week Europe (QWE'97)
[4-7 November 1997]
o Trustworthy Software (As Discussed At Quality Week '97), by Larry
Bernstein
o Software Research Announces Comprehensive Cooperative Marketing
Agreement with AONIX
o SEI Softwre Technology Reference Guide
o Call for Participation: Foundations of Component-Based Systems [26
September 1997]
o Conference: Second BCS-FACS Northern Formal Methods Workshop [14-
15 July 1997]
o Evaluating TTN-Online
o TTN-Online -- Mailing List Policy Statement
o TTN SUBSCRIPTION INFORMATION
========================================================================
My Worst Testing Nightmare...
Submitted by:
Gebhard Dunst
Test Engineer
Porsche Informatik, Austria
I once discovered a bug in our large windows NT application. The bug was
in a new version and it caused it to crash every ten to twenty minutes
or so. As the senior tester, I informed the project manager about it,
but he denied the problem, saying that nothing critical had been changed
for the version and that the crashes had to be due to my system
settings.
The "buggy" version went out to the customer and the next day we played
havoc: The application crashed every two minutes. We recalled the
application and set the customer back to the previous version. Knowing
about the bug, I spent two days in trying to replicate it: it appeared
over and over again, but I couldn't say exactly when. Needless to say,
that this made it impossible to fix the bug. I seemed to get fewer
crashes with different system configurations and this led us to a bitter
task:
We set up exactly the same configuration as the customer had on my
client PC: including "ini" files, the clients 200 MB original database
and anything else. I started to test the different configurations,
checked every change in every "ini" file from this version to the last.
I set up different databases and spent hours of testing. Sometimes the
app crashed immediately, sometimes I could work for about an hour
without failure.
I got to replicate the error and -- you guess it -- it was all too
simple. It surfaced when closing several windows with the ESC key. The
bug fix included moving one line of code to a different location...
I guess that looking for such a mysterious bug is a highlight in testing
rather than a nightmare. Never have I seen half the development team
surrounding my pc, watching in interest and discussing what was
happening.
Editors Note: $50 to Mr. Dunst for this nightmare!
========================================================================
YOUR WORST TESTING NIGHTMARE: THE CONTEST!
We know there must be a million nightmarish stories about "what happened
to me when I tried to test..." out there. And we think a lot of you
would find comfort in comparing your own nightmare with those others
write about. Or, putting it another way, misery loves company!
Here is the contest in a nutshell: Submit a short writeup (try to keep
in to fewer than 250 words) of your worst software testing nightmare.
We'll pick one or more nightmare stories per month and publish them in
TTN-Online.
The Prize: You get the comfort of sleeping better knowing you have kept
someone else up worrying about YOUR nightmare. And, we will send a
check for $50 to the nightmare voted by our staff the worst one we
received (well, we mean the best, i.e. the most worst, well, you
know...) every month. You can't win the $50 unless you enter! So, get
it off your chest and share your Testing Nightmare with the community!
========================================================================
C A L L F O R P A R T I C I P A T I O N
1st Annual International Software Quality Week/Europe
4-7 November 1997
Sheraton Hotel, Brussels, Belgium
CONFERENCE THEME: Quality for the Millenium
Quality Week Europe is the first European edition of a continuing series
of conferences focusing on advances in software test technology, quality
control, risk management, software safety, and test automation.
Software analysis methodologies, supported by advanced automated
software test methods, promise major advances in system quality and
reliability, assuring continued competitiveness. QWE'97 papers are
reviewed and selected by a distinguished International Advisory Board.
The mission of the QWE'97 Conference is to increase awareness of the
importance of Software Quality and the methods used to achieve it. It
seeks to promote Software Quality by providing technological education
and opportunities for information exchange within the software
community.
QWE'97 OFFERS:
The QWE'97 program consists of four days of mini-tutorials, panels,
technical papers and workshops that focus on software test automation
and new technology. QWE'97 provides the Software Testing and QA/QC
community with:
* Quality Assurance and Test involvement in the development process
* Exchange of experience-based information among technologists
* State-of-the-art information on software quality test methods
* Analysis of effectiveness through case studies
* Vendor Technical Presentations
* Vendor Show & Exhibits
IMPORTANT DATES:
Abstracts and Proposals Due: 30 July 1997
Notification of Participation: 29 August 1997
Camera Ready Materials Due: 19 September 1997
FINAL PAPER LENGTH: 10 - 20 pages, including Slides / View Graphs
We are soliciting 45- and 90- minute presentations or participation in
panel discussions on any area of testing and automation, including:
New and Novel Test Methods
Automated Inspection
CASE/CAST Technology
Client-Server Computing
Cost / Schedule Estimation
CMM
Data Flow Testing
Defect Tracking / Monitoring
Function Point Testing
GUI Test Technology
Integrated Environments
ISO-9000
Load Generation & Analysis
Multi-Threaded Systems
Object Oriented Testing
Process Assessment / Improvement
Productivity and Quality Issues
Re-Use
Real-World Experience
Real-Time Software
Reliability Studies
Risk Management
Software Metrics in Test Planning
Test Automation
Test Data Generation
Test Documentation Standards
Test Management Automation
Test Planning Methods
Test Policies and Standards
SUBMISSION INFORMATION:
Abstracts should be 2 - 4 pages long, with enough detail to give
reviewers an understanding of the final paper, including a rough outline
of its contents. Indicate if the most likely audience is technical,
managerial, or application- oriented.
In addition, please include:
* A cover page with the paper title, complete mailing and e-mail
address(es), and telephone and FAX number(s) of each author.
* A list of keywords / phrases describing the paper.
* A brief biographical sketch of each author.
Send abstracts to:
Ms. Rita Bral
Software Research Institute
901 Minnesota Street
San Francisco, CA 94107 USA USA.
Or fill out a SPEAKER DATA SHEET on the Web at:
http://www.soft.com/QualWeek/speakers.html
For information on the conference, E-mail your request to qw@soft.com or
phone SR/Institute at [+1] (415) 550-3020, or FAX SR/Institute at [+1]
(415) 550-3030.
CONFERENCE THEME
The QWE'97 theme, Quality for the Millenium, will focus attention not
only on the year 2000 problem, but also on such important changes as the
Internet, Electronic Commerce, Client/Server and OO testing, and related
quality areas.
CONFERENCE STRUCTURE
QWE'97 features two pre-conference tutorial days and a complete two-day
general conference with keynote sessions, mini-tutorials, and regular
technical paper tracks. There are special debates, a vendors'
presentation track, and a vendor exhibit featuring top suppliers of
Computer Aided Software Test (CAST) products.
QWE'97 speakers will include industry experts, academics and experienced
practitioners in QA/QC/Testing to provide the methodologies and advanced
automated software test methods that promise major advances in system
quality and reliability.
QWE'97 has one goal: To create an ongoing, publicly accessible platform
where researchers and Quality Assurance and Software Test Professionals,
as well as users at every level, can communicate and exchange experience
and technology.
TWO-DAY VENDOR EXHIBIT
Products and services that support software test methodologies and
techniques will be displayed November 6 and 7 in the conference hotel.
This year's vendor showcase brings you the latest technology and tools.
You'll have the opportunity to:
* Visit exhibitors representing today's most advanced solutions for
your software process needs. You can do all your product
investigation at one time.
* Heighten your industry knowledge. Learn how you can effectively
implement the proven techniques immediately.
* Gain a competitive edge. You can see live demonstrations of the
products that will dominate the decade!
* Vendor Presentation Track: Listen to selected vendors present their
solutions.
* Some past QW exhibitors have included: AZOR, Inc., B-Tree, Bender
and Associates, CenterLine Software, Direct Technology, Eastern
Systems, International Software Automation, KPMG Peat Marwick,
Mercury Interactive, Microsoft, Odyssey Research Associates,
Performance Awareness, Performance Software, Qualit, Quality Checked
Software, Reliable Software Technologies, Segue Software, Software
Quality Engineering, Software Research, Vermont Creative Software,
and John Wiley & Sons,
FOR EXHIBIT REGISTRATION AND INFORMATION, PLEASE CONTACT:
Margaret Kenny at [+1] (415) 550-3020.
========================================================================
Trustworthy Software as Discussed at Quality Week '97
by
Larry Bernstein
lbernstein@worldnet.att.net
President of National Software Council: http://www.CNSoftware.org
Associates and Friends of the National Software Council, here are some
notes from a recent conference I think you will find interesting and
useful.
The Tenth International Software Quality Week Conference and Vendor
Exhibition was held in San Francisco from May 26 to May 30, 1997. It
was a gala affair and dealt with issues facing today's software
developers and testers in a meaningful way. The conference papers were
well presented, the proceedings are quite good and there was energy not
felt at too many recent conferences.
A Birds-of-the-feather session addressed "Trustworthy Software" and here
are some findings:
1. People could not agree on what 'Trustworthy" meant; yet there was
a consensus of 125 people that something was needed. The notion that
the customer or supplier could declare a system "Trustworthy" if they
followed some defined process was agreed to.
2. Dick Hamlet of Portland State University made the point that
software "best practices are often not known and when they are they
are not practiced."
3. He pointed out that the best processes deal with investment in
tooling and technology before setting up administrative processes to
encourage people to work harder.
4. (Lori Clarke pointed out that "process without underlying
technology is bureaucracy," at a UMASS conference last year.)
5. Avoiding Data Corruption is fundamental to trustworthy software.
6. The software industry needs to agree on business practices for:
a. Recalls
b. "Stop Ship" orders
c. Defining boundary conditions
d. Specifying behavior at the boundary conditions.
e. Conformance to standards
f. Defining software life expectancy.
7. A consensus was reached on a set of ethics for internal and
external software suppliers for trustworthy systems:
a. A software architect would be named and sign off that the
software product was fit for use.
b. A software project manager would be named and sign off that the
software was fit for use. The architect and the project manager
could be the same person.
c. Fitness for use means that:
1. the software works,
2. it solves the problem,
3. a formal documented process was used in its development,
4. the software is not harmful and
5. risks are documented and managed.
8. It was suggested that the Food and Drug Administration procedure
for assuring the safety of software become an industry wide standard.
9. It surprised me that no mention was made of IEEE, ACM or other
professional society efforts to establish a set of ethics was
mentioned.
========================================================================
Software Research Announces
Comprehensive Cooperative Marketing Agreement with Aonix.
San Francisco, CA, May 16, 1997 -- Aonix and Software Research, Inc.
(SR) have announced a comprehensive sales and marketing agreement which
offers the first end-to-end solution of Automated Software Testing Tools
available in one package today. Through the integration of their
complementary tools, the two companies provide a process for reducing
the error-prone nature of testing -- an area where software developers
spend most of their time. In the past test cases were generated by
hand. The Aonix test tool generates test cases automatically at ten
times the rate of manual methods. The Aonix automatic test case
generation coupled with Software Research/TestWorks for automatic test
execution will dramatically improve productivity of software testing by
decreasing test schedules. The two tools together will also increase
quality of software testing through increased test coverage.
The agreement between the two companies includes exclusive use by Aonix
of Software Research's TestWorks suite in all Aonix sales/installations,
special emphasis by Aonix and Software Research/TestWorks on sales of
the 10X program, and sharing of sales distribution and leads by both
organizations.
The 10X program offering, which includes five days of comprehensive
training on Requirements Modeling and Specification Based Testing works
in the following way: Starting with Aonix' Software through Pictures
StP/OMT product with the Use Case Editor, the user records requirements
and uses "T" the Aonix test case generation tool for generating test
cases. Then the users runs Software Research's TestWorks Regression
suite for automated test execution, validation and test management of
the generated test cases. Once it has been determined that the test
cases demonstrate the requirements, Software Research's SR/TestWorks
Coverage tool evaluates the quality and completeness of the test cases
by indicating how much of the source code has been exercised at the
branch, call-pair and path or path class level. All information is
easily accessible through visual reports.
SR/TestWorks Tool Suite
The SR/TestWorks tool suite offers a family of integrated testing and QA
products for test data generation, regression testing, capture and
playback, test execution and evaluation. SR/TestWorks also provides
software test management and reporting, code comprehension, coverage
analysis, metrics and maintenance in some of the most-commonly used
languages such as Java, C, C++, Ada and Fortran F77. TestWorks is
available for the major UNIX platforms, Windows 95, Windows NT and DOS.
Its open architecture allows for testing of enterprise-wide applications
in both embedded or client/server systems and GUI desktop or Web
applications.
The Aonix Tool Suite
The Aonix tool suite includes: Software through Pictures Object Modeling
Technique (StP/OMT), a robust multi-user analysis and design environment
with a shared repository that supports development teams through the
full life cycle of object-oriented application development; the Use Case
Editor which performs high level analysis with usage models to identify
requirements; and the "T" Test Case Generator which automatically
builds test cases to test the validity of those requirements.
Dr. Edward Miller, President of SR said, "The reasons to thoroughly test
software are even more true than they have been historically, and the
opportunity now exists to assure quality from the very beginning of the
software life cycle, when the chance to prevent defects has the highest
payoff, to the end of the development cycle, where very often the most
critical defects that affect product quality are often found."
"The agreement we've signed is historic because it provides a true end-
to-end solution to the software development process that is affordable,
efficient, effective and more comprehensive than any other available
solution."
"The Aonix and SR suite of tools is the most complete set of testing
tools on the market providing and end-to-end testing solution to the
user with tools for creating test-ready specifications and models, tools
for generating test cases and scripts, tools for managing large sets of
test cases and scripts, tools for executing test scripts, and tools for
evaluating test coverage," says Bob Poston - Director of Testing Tools &
Practices for Aonix and author of the book "Automating Specification-
Based Software Testing"
About Software Research, Inc.
Software Research was the pioneer in software testing and quality
assurance and remains at the forefront of innovative testing
technologies. Founded in 1977 as a consulting and service organization,
Software Research, Inc. is the world leader in this field, providing the
broadest suite of integrated software testing tools on the market:
TestWorks. Product details are available directly by phone: (415) 957-
1441, fax: (415) 550-3030) and e-mail: info@soft.com. The SR web site
is http://www.soft.com.
About Aonix
Aonix, with headquarters in San Francisco, is a $75 million company in
the OO tools market and one of the top 50 software companies in the
world. The firm was formed in November 1996 with the merging of two
market leaders: Interactive Development Environments, Inc. (IDE), a
veteran player in the modeling, analysis and design tools market, and
Thompson Software Products, a diversified tools company whose products
and extensive service portfolio span the implementation and deployment
phases of high-end software development. Aonix currently has over 80
sales people and 80 consultants worldwide, serving Thomson's 20,000
installations and half a million users, and IDE's 18,000 users
worldwide. The merger positions Aonix to offer a new end-to-end OO
development platform for even greater penetration into both the
commercial and technical markets, and to increase its presence in the
development and deployment tools market. Aonix details can be found on
the Internet at: http://www.aonix.com.
For Additional Information:
Ms. Rita Bral
Software Research, Inc.
VP/Corporate Communication
901 Minnesota Street
San Francisco, CA 94107 USA
[+1] (415) 550-3020
bral@soft.com
http://www.soft.com
Mr. Anthony Simpson
Director, Corporate Marketing
Aonix
595 Market Street
San Francisco, CA 94105
[+1] (415) 543-0900
tsimpson@aonix.com
http://www.aonix.com
========================================================================
SEI Software Technology Reference Guide
The Software Engineering Institute has produced a Software Technology
Reference Guide to industry best practices. This project is directed by
John Foreman of the SEI and is intended to be kept current with semi-
annual updates.
The Software Technology Reference Guide can be found at
http://www.sei.cmu.edu/technology/str.
The SEI has selected Don O'Neill to produce and maintain the section on
Software Inspections. Simply search on inspections.
Please contact O'Neill (ONeillDon@aol.com) with any questions and
interest in Software Inspections training.
========================================================================
Call for Papers: Foundations of Component-Based Systems
September 26, 1997
Zurich, Switzerland
Affiliated with:
European Software Engineering Conference -- ESEC 97
together with
Fifth ACM SIGSOFT Symposium on the
Foundations of Software Engineering FSE 97
Program Committee
Gary T. Leavens, Iowa State University, USA
Robyn Lutz, Iowa State University and NASA Jet Propulsion Laboratory, USA
Helen Gill, Defense Advanced Research Projects Agency, USA
Oscar Nierstrasz, University of Berne, Switzerland
Murali Sitaraman, West Virginia University, USA
Bruce W. Weide, The Ohio State University, USA
Description
The objective of this workshop is to explore how formal (mathematical)
techniques can be or should be used to establish a suitable foundation
for component-based software engineering. We would like to bring
together:
* researchers and practitioners in component-based software engineering
who are interested in better theoretical foundations, and
* researchers and practitioners in formal methods who are interested in
bridging the gap between principles and practice
The idea would be to help make research in both areas more productive.
For example, researchers in formal methods have only recently begun to
study:
* object-oriented design, specification, verification, and
* architectural issues for component-based systems,
but other issues are also important in the practice of component-based
systems, such as:
* parameterization and inheritance,
* performance (time and space),
* reuse,
* software composition,
* reducing evolution and maintenance costs.
The participants will brainstorm about these and related problems to
understand both the problems and how formal techniques may be useful in
the solving them. The main expected result of the meeting will be:
* an outline of collaborative research topics
* a list of areas for further exploration.
Details may vary with the background and interest of the participants.
Submissions
Invitation to the workshop will be based on accepted position papers. An
ideal position paper would identify new research topics, areas, or
problems related to component-based software engineering. Position
papers should address the following questions.
* What is the problem (or topic or area) that is being described?
* What is the significance of the problem for component-based software
engineering?
* What theoretical or practical insights might help to solve this
problem?
* What related work is there about the problem and the theoretical
approach? How does it compare?
Position papers must follow the format given in the file
http://www.cs.wvu.edu/~resolve/FoCBS/FoCBS.tex
Submissions are due by July 15, 1997 and must not exceed 10 pages. Four
hard copies must be sent to:
Gary T. Leavens
Department of Computer Science
Iowa State University
226 Atanasoff Hall
Ames, Iowa 50011-1040 USA
Tel: (515) 294-1580
Fax: (515) 294-0258
leavens@cs.iastate.edu
See http://www.cs.wvu.edu/~resolve/FoCBS/ for more details.
========================================================================
Second BCS-FACS Northern Formal Methods Workshop
Call for Participation
Craiglands Hotel
ILKLEY, UK, 14-15 July 1997
The aim of the BCS-FACS Northern Formal Methods Workshop is to foster
research and collaboration in formal methods by bringing leading figures
and young researchers together in a friendly and informal atmosphere,
in which participants can exchange and contribute novel ideas and
innovative developments.
Following the success of the inaugural workshop, the meeting will be
held again at the Craiglands, a delightful Victorian country hotel on
the edge of Ilkley Moor.
The Workshop will consist of invited talks by three leading figures in
the use and application of formal methods, a strong program of
contributed papers, and a discussion session.
Web Address:
http://www.comp.brad.ac.uk/research/nfmw/index.html
Preliminary Programm (Authors and Titles) Include:
Invited Talk by R. Milner, University of Cambridge
"Relaxing Property Preservation in the Refinement of Concurrent
Systems." by M. Siegel, Weizmann Institute of Science, Israel
Invited Talk by D.A. Duce, Rutherford Appleton Laboratory, Didcot, UK
"Modelling Program Compilation in the Refinement Calculus" by C.J.
Fidge, SVRC, The University of Queensland, Australia
"Towards Rigorous Analysis of Fusion Models: The MIRG Experiences," by
R.B. France, J.-M. Bruel, C. Raghavan, Florida Atlantic University, USA
Using LOTOS for the Evaluation of Design Options in the PREMO
Standard," by G.P. Faconti and M. Massink, CNR-Instituto CNUCE, Pisa,
Italy
"Coupling Schemas: Data Refinement and View(point) Composition," by E.
Boiten, J. Derrick, H. Bowman and M. Steen, University of Kent,
Canterbury
"Algebraic Advances for Aspects of the WWW," by A. Hughes and A.
Donnelly, Trinity College, Dublin, Ireland
"A Rigorous Approach to the Production of Formal Specifications from
CASE Repositories," by B. Ryan, Leeds Metropolitan University
"The Geometry of Distributions in Formal Methods" by M. Mac an
Airchinnigh, Trinity College, Dublin, Ireland
Invited Talk by P. Gorm Larsen, IFAD, Denmark
"A Tool for Logic Program Refinement," R. Colvin, I. Hayes, R. Nickson
and P. Strooper, SVRC, The University of Queensland, Australia
"Formalizing Correlate - From Practice to Pi," by B. Robben, F.
Piessens, W. Joosen, K.U. Leuven, Belgium
"On Formal Semantics of Statecharts," by E. Mikk, Y. Lakhnech, C.
Petersohn and M. Siegel, Christian-Albrechts-Universitat zu Kiel,
Germany, and Weizmann Institute of Science, Israel
"Communication Traces in the Verification of Distributed Programs," by
N. Soundarajan, The Ohio State University, Columbus, USA.
"Using Graphical Icons to Build Z Specifications," by C.N. Yap and M.
Holcombe, Department of Computer Science, University of Sheffield
"Analysis of Abstract Syntax Trees of Z Specifications," by L. Mikusiak
and V. Vojtek, Intergraph SR, Bratislava, Slovak Republic, Slovak
Technical University, Bratislava, Slovak Republic.
"The Real Numbers in Z," by W.R. de Oliveira and R.S.M. de Barros,
Universidade Federal de Pernambuco, Brazil
"Object-oriented Operations Have Two Parts," by A. Griffiths, The
University of Queensland, Australia
"Formalizing the Unified Modeling Language," A.S. Evans, T. Clark, L.
Lai and T. Bryant, University of Bradford, and Leeds Metropolitan
University
It is expected that the proceedings will be published by Springer-
Verlag.
Program Review Committee
J. Armstrong (York) J. Fitzgerald (Newcastle)
H. Barringer (Manchester) J. Hammond (Praxis)
G. Birtwistle (Leeds) J.L. Jacob (York)
A. Bryant (LMU) S. King (York)
A. Butterfield (Trinity, Dublin) K.Lano (Imperial)
D.A. Carrington (Qld) L.M. Lai (Brad)
D.J. Duke (York) M. Mac an Airchinnigh (Trinity,Dublin)
R.W. Duke (Qld) P. Mukherjee (Leeds)
A.S. Evans (Brad) L.T Semmens (LMU)
G. Faconti (CNUCE,Pisa) I.S.Torsun (Brad)
Organizing Committee
A.S. Evans D.J. Duke
Department of Computing Department of Computer Science
University of Bradford University of York
West Yorkshire Heslington, York
BD7 1DP YO1 5DD
U.K. U.K.
a.s.evans@comp.brad.ac.uk duke@minster.york.ac.uk
Registration Information
Charlotte Johnson,
BCS-FACS Northern Formal Methods Workshop.
Department of Computing,
University of Bradford,
West Yorkshire,
BD7 1DP,
UK.
C.J.Johnson@comp.brad.ac.uk
tel: +44 (0)1274 383921
fax: +44 (0)1274 383920
========================================================================
EVALUATING TTN-ONLINE: GIVE US YOUR COMMENTS
TTN-Online is free and aims to be of service to the larger software
quality and testing community. To better our efforts we need YOUR
FEEDBACK!
Please take a minute and E-mail us your thoughts about TTN-Online?
Is there enough technical content?
Are there too many or too few paper calls and conference announcements?
Is there not enough current-events information? Too much?
What changes to TTN-Online would you like to see?
We thrive on feedback and appreciate any comments you have. Simply
address your remarks by E-mail to "ttn@soft.com".
========================================================================
TTN-Online -- Mailing List Policy Statement
Some subscribers have asked us to prepare a short statement outlining
our policy on use of E-mail addresses of TTN-Online subscribers. This
issue, and several other related issues about TTN-Online, are available
in our "Mailing List Policy" statement. For a copy, send E-mail to
ttn@soft.com and include the word "policy" in the body of the E-mail.
========================================================================
------------>>> 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 and 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, send E-mail to "ttn@soft.com".
TO SUBSCRIBE: Include in the body of your letter the phrase "subscribe
".
TO UNSUBSCRIBE: Include in the body of your letter the phrase
"unsubscribe ".
TESTING TECHNIQUES NEWSLETTER
Software Research, Inc.
901 Minnesota Street
San Francisco, CA 94107 USA
Phone: +1 (415) 550-3020
Toll Free: +1 (800) 942-SOFT (USA Only)
FAX: +1 (415) 550-3030
E-mail: ttn@soft.com
WWW URL: http://www.soft.com
## End ##