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 =======+
+======= September 1997 =======+
+===================================================+
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 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 1997 by Software Research,
Inc.
========================================================================
INSIDE THIS ISSUE:
o Quality Week/Europe (QWE'97) Complete Technical Program Announced
o Improving the Attitude toward Testing: Shifting the Focus of
Testing, by Dr.San Murugesan
o ComputerWorld Special Report: Software Quality
o Sound Off: Should We Give Up On Quality Vendor-Supplied Software?
Yes!, by Steve Devinney
o TCAT C/C++ for UNIX Used in CS Testing Course
o Frequently Asked Questions (FAQs) About Testing
o Call For Papers: 20th International Conference on Software
Engineering (ICSE98)
o TTN SUBSCRIPTION INFORMATION
========================================================================
QWE'97 COMPLETE PROGRAM ANNOUNCED
1st Annual International Software Quality Week/Europe
4-7 November 1997
Sheraton Hotel, Brussels, Belgium
CONFERENCE THEME: Quality for the Millenium
http://www.soft.com/QualWeek/QWE97
Quality Week Europe is the first European edition of a series of
successful conferences held in San Francisco for the last decade.
Quality Week focuses 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 ADVISORY BOARD
QWE'97 papers are reviewed and selected by a distinguished International
Advisory Board.
Dr. Boris Beizer (Analysis, Inc.) USA
Prof. Fevzi Belli (University of Paderborn) GERMANY
Mr. Bill Bently (Bayer Corporation) USA
Dr. Gilles Bernot (Laboratoire d'Informatique) FRANCE
Dr. Antonia Bertolino (CNR-IEI) ITALY
Mr. Robert Binder (RBSC Corporation) USA
Dr. Juris Borzovs (Software House Riga) LATVIA
Ms. Rita M. Bral (Software Research, Inc.) USA
Mr. Gunther Chrobok-Diening (DLR - Oberpfaffenhofen) GERMANY
Ms. Ann Combelles (Objectif Technologies) FRANCE
Mr. Dirk Craeynest (OFFIS nv/sa) BELGIUM
Mr. Tom Drake (Booz Allen & Hamilton) USA
Mr. John Favaro (Intecs Sistemi S.p.A.) ITALY
Mr. Istvan Forgacs (Hungarian Academy of Sciences) HUNGARY
Prof. Mario Fusani (CNR-IEI) ITALY
Dr. Hans-Ludwig Hausen (GMD German National Research) GERMANY
Prof. William Howden (University of Cal. at San Diego) USA
Prof. Guenter Koch (Synlogic AG) SWITZERLAND
Dr. Peter Liggesmeyer (Siemens AG) GERMANY
Ms. Cecilie B. Loken (Ericsson AS) NORWAY
Dr. Edward F. Miller (Software Research, Inc.) USA
Dr. John D. Musa (Consultant) USA
Prof. Leon Osterweil (University of Massachusetts) USA
Dr. Thomas Ostrand (Siemens Corporate Research, Inc.) USA
Dr. Antonio Serra (QualityLab) ITALY
Mr. Otto Vinter (Brel & Kjaer) DENMARK
Prof. Pierre Wolper (University de Liege) BELGIUM
Dr. James C. Woodcock (Oxford University) ENGLAND
Prof. Dr. Jacques Vandenbulcke (SAI Studiecenter) BELGIUM
Mr. Erik P.W.M. VanVeenendaal (KEMA/Eindhoven Univ.) NETHERLANDS
MISSION AND GOAL
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.
The success of the Quality Week Conferences is due to its one main 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.
Over the past ten years, Quality Week has offered high caliber programs
that consistently draw the finest industry and academic speakers. Our
mission is to provide a quality educational conference without any
product marketing pitches.
QWE'97 OFFERS:
The QWE'97 program consists of four days of 1-day and 1/2-day tutorials,
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/Demo Presentations
* Vendor Show & Exhibits
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
software quality areas.
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,
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
T U T O R I A L S
Tuesday, 4 November 1997, 9:00 - 12:00 -- AM Tutorials
Dr. Boris Beizer (Independent Consultant) "An Overview of Testing (1A1)
(1A2)"
Mr. Hans-Ludwig Hausen (GMD Gesellschaft fur Mathematik und
Datenverarbeitung mbH) "Effective Metrication for Software Process
Assessment and Software Product Evaluation (1B1)"
Dr. Michael Haug "A Survey of EC-Sponsored Software Process Improvement
Efforts (1C1)"
Mr. Robert V. Binder (RBSC Corporation) "Modal Testing Strategies for
Object-Oriented Software (1D1) (1D2)"
Tuesday, 4 November 1997, 14:00 - 17:00 -- PM Tutorials
Dr. Boris Beizer (Independent Consultant) "An Overview of Testing (1A1)
(1A2)"
Mr. Tom Drake (Booz Allen & Hamilton) "Testing Software Based Systems:
People, Process & Technology (1B2)"
Dr. Giora Ben-Yaacov (Cadence Design Systems) "Effective Implementation
of ISO 9000 for Software (1C2)"
Mr. Robert V. Binder (RBSC Corporation) "Modal Testing Strategies for
Object-Oriented Software (1D1) (1D2)"
Wednesday, 5 November 1997, 9:00 - 12:00 -- AM Tutorials
Mr. Tom Gilb (Independent Consultant) "Requirements-Driven Test
Management (2A1) (2A2)"
Mr. Erik Van Veenendaal & Mr. Bart Broekman (KEMA/Eindhoven University
of Technology) "Structured Testing According to TMap (2B1)"
Mr. Robert V. Binder (RBSC Corporation) "Test Automation for Object-
Oriented Systems (2C1)"
Mr. Robert Poston (Aonix) "10X Testing: Automating Specification-Based
Testing (2D1) (2D2)"
Wednesday, 5 November 1997, 14:00 - 17:00 -- PM Tutorials
Mr. Tom Gilb (Independent Consultant) "Requirements-Driven Test
Management (2A1) (2A2)"
Mr. Nicholas Zvegintzov (Software Management Network) "Testing for Year
2000 (2B2)"
Mr. Erik Van Veenendaal & Jos Trienekens (KEMA/Eindhoven University of
Technology) "Practical User-Oriented Software Product Quality
Specification and Evaluation (2C2)"
Mr. Robert Poston (Aonix) "10X Testing: Automating Specification-Based
Testing (2D1) (2D2)"
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
T E C H N I C A L P R O G R A M
Thursday, 6 November 1997, 9:00 - 10:00 -- KEYNOTE SESSION #1
Mr. Tony Wasserman (Software Methods & Tools) "30 Years of Software
Engineering -- What Have We Learned? (1P)"
Thursday, 6 November 1997, 11:00 - 5:00 -- Parallel Technical Tracks
TECHNOLOGY TRACK...
Ms. Janet P. Oberti, et. al. (BEA Systems, Inc) "Testing an Object
Request Broker (ORB) Using Automation (2T)"
Dr. Agnes Arnould, Dr. Pascal Le Gall (Universite Paris-XI) "Some
Aspects of Test Data Selection from Formal Specifications (3T)"
Prof. Antonia Bertolino (IEI-CNR) "A General Path Generation Algorithm
for Coverage Testing (4T)"
Mr. T. Ashok, A. Balasubramaniam, K. Rangarajan (VeriFone India Pvt Ltd)
"Class Evolution and Equivalence Categories (5T)"
Dr. Denise Woit (Ryerson Polytechnic University) "Specifying Component
Interactions for Modular Reliability Estimation (6T)"
SOUTIONS TRACK...
Mr. Joseph R. Horgan, et. al. (Bell Communications Research) "Software
Fault Injection Testing on a Distributed System -- A Case Study (2S)"
Mr. Thierry Tacquet (Objectif Technologie) "Small Company Action
Training and Enabling (SCATE) (3S)"
Mr. Erik Van Veenendaal (KEMA/Eindhoven University of Technology)
"Practical Inspection Experiences at Philips (4S)"
Mr. Otto Vinter (Bruel & Kjaer) "How to Apply Static and Dynamic
Analysis in Practice (5S)"
Mr. Kyu-Ouk Lee (ETRI (Electronics & Telecommunications Research
Institute)) "Software Test Measurement and Reliability Prediction of a
Switching System (6S)"
MANAGEMENT TRACK...
Ms. Anne Mette Jonassen Hass & Mr. Jorn Johansen (DELTA, Software
Engineering) "BOOTSTRAP - The Real Way To SPI (2M)"
Mr. Morten Elvang-Goransson (SimCorp AS) "Devising a Specification
Process (by Turning Gilb Style Inspections Inside Out) (3M)"
Mr. Paolo Panaroni (Intecs Sistemi, S.p.A.) "Testing, But...The Other
Way Round: A Management Perspective (4M)"
Mr. Bruno Peeters (Gemeentekrediet van Belgie) "A COBOL Standards
Compliance Checker (5M)"
Mr. Tom Gilb (Independent Consultant) "Evolutionary Project Management
(6M)"
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Friday, 7 November 1997, 9:00 - 10:00 -- KEYNOTE SESSION #2
Dr. Boris Beizer (Independent Consultant) "The Future of Software
Quality (7P)"
Friday, 7 November 1997, 10:00 - 12:00 -- Parallel Technical Tracks
TECHNOLOGY TRACK...
Mr. Fraser Macdonald & Mr. James Miller (University of Strathclyde
Department of Computer Science) "ASSISTing with Software Inspection
(8T)"
Dr. Guido Dedene & Geert Poels (Department of Applied Economics)
"Assessing the Size and Complexity of Formally Specified Conceptual
Models (9T)"
Mr. Jean-Marie Condom & Khadir Ouriachi (Universite de Pau et des Pays
de l'ADOUR) "Meeting Quality Requirements in Robot-Based Manufacturing
Using Z (10T)"
Ms. Barbara Quaquarelli (Cad.Lab S.p.A) "Quality Improvement through
VErification PROcess (PROVE) (11T)"
Mr. Huey-Der Chu & Prof. John E. Dobson (University of Newcastle upon
Tyne) "An Integrated Test Environment for Distributed Applications
(12T)"
SOLUTIONS TRACK...
Mr. Bruno Peeters (Gemeentekrediet van Belgie) "Measurement of Software
Maintainability (8S)"
Karen Thelen, Gary Dehlin, Rosa Weber, (Honeywell Technology Center)
"Model-Based Requirements Definition and Verification Test Generation
for Cockpit Display Systems (9S)"
Mr. Sankar Chakrabarti & Mr. Harry Robinson (Hewlett Packard Company)
"Catching Bugs in the Web: Using the World Wide Web to Detect Software
Localization Defects (10S)"
Mr. Tony Templeton (IBM Canada Ltd.) "Rapid Testing Strategies (11S)"
Mr. Staale Amland (Avenir A.S.) "RAD Process Improvement by Testing
(12S)"
MANAGEMENT TRACK...
Mr. Marc Morel-Chevillet & Stephane Depres (Objectif Technologie) "AVAL
Objectives, Process and Results (8M)"
Mr. Bob Smith, Ms. Ana Andres, et. al. (European Software Institut)
"ISO-9000 Certification as a Business Driver: The SPICE Road (9M)"
Mr. Don O'Neill "Global Software Competitiveness Assessment Program
(10M)"
Mr. Stefan Biffl, Mr. G. Thomas (Technical University of Vienna) "How to
Apply Quality Assurance in Every Project: Guidance Towards Three Levels
of QA for Real Life (11M)"
Mr. Howard Chorney (Process Software Corporation) "A Practical Approach
to Using Software Metrics (12M)"
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
REGISTRATION INFORMATION
Complete registration with full information about the conference is
available on the WWW at
<http://www.soft.com/QualWeek/QWE97>
where you can register on-line.
We will be pleased to send you a QWE'97 registration package by E-mail,
postal mail or FAX on request. Send your E-mail requests to:
qw@soft.com
or FAX or phone your request to SR/Institute at the numbers below.
QWE'97: 4-7 November 1997, Brussels, Belgium EU
+-----------------------------------+----------------------------------+
| Quality Week Europe '97 | Phone: [+1] (415) 550-3020 |
| SR/Institute, Inc. | Toll Free: 1-800-942-SOFT |
| 901 Minnesota Street | FAX: [+1] (415) 550-3030 |
| San Francisco, CA 94107 USA USA | E-Mail: qw@soft.com |
| | WWW: http://www.soft.com |
+-----------------------------------+----------------------------------+
========================================================================
Improving the Attitude Toward Testing:
Shifting the Focus of Testing
by
Dr. San Murugesan
Faculty of Business and Technology
University of Western Sydney, Macarthur
email: s.murugesan@uws.edu.au
Editors Note: This article appeared in the August 1997 issue of
THE CUTTER EDGE, a free weekly email service for IT professionals
and is reprinted here with consent of the Managing Editor of the
American Programmer, Ms. Karen Pasley (kpasley@compuserve.com).
Most software testing efforts focus on detecting and correcting as many
errors as possible. The aim of testing has traditionally been to
eliminate or reduce (critical) errors -- a negative quality of software
-- and hence to minimize customer dissatisfaction arising from errors in
the software.
This approach, however, is not good enough -- the absence of the
negative does not make a positive. Besides minimizing defects, testing
should contribute to enhancing the positive qualities of the software
from the customers' (users') perspective. The focus of testing,
therefore, must shift toward maximizing customer satisfaction with the
software, rather than just minimizing errors in the software.
"Know the users and the application" is the first principle of software
development and testing. Testing has to concentrate on critical,
significant, high-value software components from the customers' and
application perspectives. It is also becoming increasingly important to
test the software according to its operational profile and usage
patterns. This requires a greater awareness of the application and
operations environment of the software and a better understanding of the
customers' requirements.
As described by Richard Zultner (in "TQM for Technical Teams,"
Communications of the ACM, Vol. 36 [October 1993], pp. 79-91),
customers' requirements can be grouped into three categories, each of
which has a different impact on customer satisfaction. These categories
are normal (or implied) requirements, expected requirements, and
exciting requirements.
NORMAL REQUIREMENTS
Software developers typically get these from the customer as formal
requirements of the software. These requirements satisfy (or dissatisfy)
customers in proportion to their presence (or absence) in the delivered
software.
EXPECTED REQUIREMENTS
Customers may not bother to mention these requirements until the
software fails to meet their expectations; they simply assume that the
software will meet these requirements. Such requirements include online
help, warnings, error messages, validation of input/output, built-in
safety features, and recovery from failures.
Fulfillment of these requirements meets customers' expectations, but it
does not normally enhance their satisfaction. Failing to meet these
requirements, on the other hand, is very dissatisfying to customers. So
while meeting the expected requirements goes unnoticed by most
customers, not meeting them will dissatisfy the customers.
EXCITING REQUIREMENTS
These requirements include features that are not anticipated by the
customers or that exceed their expectations. If delivered successfully,
such features can be highly satisfying. Of course, these desirable but
nonessential features can be difficult to identify and foresee. Their
presence greatly enhances customer satisfaction, but their absence does
not dissatisfy customers.
Besides detecting errors, the objectives of software testing are to
verify that software meets the customers' requirements and expectations,
and hence to enhance customer satisfaction. These goals require that
software be tested not only for normal requirements, but also for
expected and exciting requirements.
In addition, software should be tested for its robustness. Test cases
should also include invalid inputs to check the behavior of the software
under invalid or erroneous conditions.
For effective testing within schedule and resource constraints, testing
should focus on those areas of the software that are of great
significance to the customer. In many software projects, such a focus is
becoming more important than striving to attain "zero-defect" software.
Absolute correctness of software may not be mandatory in many
applications, as harmless or low-risk errors could be tolerated.
Further, it is very difficult to ensure absolute correctness of large,
complex software. Consequently, software testing is moving from a
product-driven (or engineering-driven) focus to a customer-driven focus.
========================================================================
ComputerWorld Special Report: Software Quality
18 August 1997 Issue of ComputerWorld
Rarely does one see such a straightforward survey of the software
quality area as that in the 18 August 1997 issue of ComputerWorld, which
contains a Special Report, written by Walter Crosby
(walter_crosby@cw.com), VP of Information Systems for Computerworld,
Inc. Crosby brings together a particularly interesting array of writers
and material that give a very good, hi-level introduction to software
quality questions.
Besides the hard copy version, most of the material is also available
online at:
http://www.computerworld.com/features/970818bfd_intropage.html
========================================================================
Sound Off: Should We Give Up On Quality
Vendor-Supplied Software? Yes!
By Steve Devinney (76435.44@compuserve.com)
This piece is part of the ComputerWorld set of papers (described
elsewhere in this issue of TTN-Online), and is reprinted here with
permission of the author.
Today, speed is everything. IS will gladly trade a few bugs for fast
releases
So the topic is quality. Let's review the IS track record.
According to a study by the Standish Group, 52% of all projects
undertaken by internal information systems organizations cost 189% of
their original estimates; projects completed have 42% of the originally
proposed features or functions; 81% of all projects are canceled before
completion; and only 16% of projects are completed on time and within
budget.
That isn't a difficult record for software vendors to beat. Vended
packages may be the only hope the U.S. has of maintaining a strong
position in today's competitive marketplace. (I'm not implying that all
IS departments are incapable of producing quality software, just
pointing out that IS faces problems that make vended packages even more
appealing.)
Why is vendor software more attractive in today's competitive
marketplace?
To begin with, quality isn't as bad as everybody says. Vendors subject
their products to beta testing. This gives hundreds, or even thousands,
of people the opportunity to identify defects and the vendor time to
remedy critical defects prior to a formal product introduction.
Corporate America can't subject homegrown applications to that level of
scrutiny.
Let's face it: Vendors focus primarily on the critical business
functions their products were designed to support. Hence, their
products' defects may be more a nuisance than a serious roadblock. That
isn't an excuse for poor interfaces or non-intuitive design, but at the
end of the day, the important thing is to get your job done.
Corporate America and corporate IS have come to expect and accept
defective products. "So we missed a deadline and our application is
defective. The users signed off and we still have a job. Life couldn't
get any better." Vendors bet their company on every introduction or
major enhancement. One catastrophic deployment may well be the last. How
long will a vendor stay in business if it only delivers 42% of the
promised functionality?
Is vendor software defect-free? Of course not. Why? Vendors are
especially sensitive to time-to-market demands. The competition is
plentiful, and new players join the game every day.
Look at the evolution of year 2000 technology solutions. Three years
ago, there were a few vendors that offered technology assistance. Today,
everybody who can spell year 2000 has some form of automated solution.
Speed of delivery is critical to vendors, and it may ultimately be the
deciding survival factor. Vendors can't simply focus on the current
market needs; they must stay abreast of new technologies and position
themselves to be the leaders of innovation.
Consumers have repeatedly demonstrated that speed of delivery and cost
are far more important than defect-free products. We continue to buy
their products, services and maintenance contracts. There was a period
when we expected vendor software to exceed the quality of the products
IS could produce. Now we tell vendors we will tolerate defects as long
as their software meets the critical needs of our core business
functions. In effect, we have lowered the product quality standards for
the vendor.
So whom do we blame for defective software? Vendors will react to the
demands and expectations of the consumer community, and will continue to
deliver defective products until we raise our quality expectations and
refuse to buy defective products. Today, you buy a product knowing it
has defects, but with some assurance that a fix is forthcoming via a
World Wide Web-enabled file transfer or a new release. You're happy.
The vendor's happy.
Of course, there are exceptions. Microsoft has such a stronghold on the
desktop market that it can force consumers to accept defective products.
Vendor software will always be an attractive solution for most
organizations. New and advanced technologies, the global marketplace,
and the dwindling availability of technical resources, will continue to
fuel the need. What you give up in quality you get back in convenience
and frequent releases.
Me, I'll take the a:install any day!
========================================================================
TCAT C-C++ for UNIX Used In CS Testing Course
Prof. Gail Murphy
(murphy@cs.ubc.ca)
University of British Columbia
Prof. Murphy will be using TCAT C/C++ Ver. 9.2 for SPARC and HP in her
course on software testing in the Computer Science department at the
University of British Columbia, Vancouver, B.C. CANADA.
The course in which TestWOrks will be used is a 3rd year (junior)
required Software Engineering class entitled "Software Engineering."
There are 180 students taking the class. The students are Computer
Science students, Computer Engineering students, and a smattering of
other science students and a few graduate students.
The software will be used as part of a lab on testing, providing the
students hands-on experience with automated testing. The course is a
survey course covering all the basic aspects of software engineering,
analysis, design, implementation, reuse, configuration management,
testing, etc. TestWorks licenses has been provided by SR gratis as part
of SR's Academic Discount Program.
========================================================================
Frequently Asked Questions about Testing
This is a pointer to the Frequently Asked Questions file for the
comp.software.testing newsgroup. Please read the guidelines in the FAQ
before posting to the newsgroup. You should be able to find the FAQ in
news.answers or comp.answers and also at:
<http://www.faqs.org/faqs/software-eng/testing-faq/>
For information about software engineering in general and the other
newsgroups that cover software engineering topics, see the introduction
to comp.software-eng at:
<http://www.faqs.org/faqs/software-eng/part0>
========================================================================
Call for Papers:
The 20th International Conference on Software Engineering (ICSE98)
THEME: FORGING NEW LINKS
Kyoto, JAPAN
19-25 April 1998
Sponsored by:
Science Council of Japan
Information Processing Society of Japan
Japan Society for Software Science and Technology
IEEE Computer Society,TCSE
ACM Special Interest Group on Software Engineering
Corporate Sponsors (Tentative)
Nippon Telegraph and Telephone Corporation
Nihon Keizai Shimbun, Inc.
For more information:
http://icse98.aist-nara.ac.jp/
e-mail:icse98-info@itc.aist-nara.ac.jp
The annual International Conference on Software Engineering (ICSE) is
the leading forum for the exchange of ideas on all aspects of software
engineering. ICSE98 invites you to submit work to share with the ICSE
community.
ICSE 98 encourages papers from the many perspectives that contribute to
the whole of Software Engineering. We particularly encourage papers
addressing topics wherein software engineering issues play a key role,
but where those topics have not been highlighted in previous ICSEs. We
encourage discussions of both the process and outcome of research
concerning design, engineering, development, installation, use, and
maintenance.
Different classes of contributions are sought, ranging from research
papers to lessons and status reports from software engineering
organizations. The ultimate goal is to build a rich and comprehensive
conference program that can fit the interests and needs of different
classes of attendees: professionals, researchers, managers, and
students.
Note: If you decide to submit, you should look into the ICSE98 Home Page
(http://icse98.aist-nara.ac.jp/) to get the necessary information for
submission.
========================================================================
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.
o Is there enough technical content?
o Are there too many or too few paper calls and conference
announcements?
o Is there not enough current-events information? Too much?
o 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 ##