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 =======+
+======= August 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 Announcing C+- (Pronounced C More or Less), by John Favaro
o Mission Reliability Testing: A Testing Dream, by Larry Bernstein
o Remote Testing with TestWorks: A Disciplined Remote Testing
Approach vs. Rolling Betas
o Call For Papers: 2nd International B Conference, Montpellier,
France: 22-24 April 1998
o TestWorks Version Calibration, August 1997.
o Call for Papers: AQuIS, Venice, Italy: 31 March - 3 April 1998
o Nightmare of the Month Club: A Winner: "Features Not Required!",
by Link Hochnadle
o First European Conference on Achieving Software Product Quality:
Developing, Testing, Evaluating for 'Good Enough' Quality, Dublin,
Ireland: 15-16 September 1997
o ICSM'97, Bari, Italy: 29 September - 3 October 1997
o TTN SUBSCRIPTION INFORMATION
========================================================================
Announcing C+- (Pronounced: C More or Less)
Unlike C++, C+- is a subject-oriented language (SOL).
Contributed by J. Favero, INTECS, Italy
Each C+- class instance, known as a subject, holds hidden members, known
as prejudices, agendas or undeclared preferences, which are impervious
to outside messages, as well as public members, known as boasts or
claims. The following C operators are overridden as shown:
> better than
< worse than
>> way better than
<< forget it
! not on your life
== comparable, other things being equal
!== get a life, guy!
C+- is a strongly typed language, based on stereotyping and self-
righteous logic. The Boolean variables TRUE and FALSE (known as
constants in other, less realistic languages) are supplemented with
CREDIBLE and DUBIOUS, which are fuzzier than Zadeh's traditional fuzzy
categories. All Booleans can be declared with the modifiers strong and
weak. Weak implication is said to "preserve deniability" and was added
at the request of the DoD to ensure compatibility with future versions
of Ada. Well-formed falsehoods (WFFs) are assignment-compatible with all
Booleans. What-if and why-not interactions are aided by the special
conditional evenifnot X then Y.
C+- supports information hiding and, among friend classes only, rumor
sharing. Borrowing from the Eiffel lexicon, non-friend classes can be
killed by arranging contracts. Note that friendships are intransitive,
volatile and non-Abelian.
Operator precedence rules can be suspended with the directive #pragma
dwim, known as the "Do what I mean" pragma.
ANSIfication will be firmly resisted. C+-'s slogan is "Be Your Own
Standard."
========================================================================
Mission Reliability Testing: A Testing Dream
By
Larry Bernstein
Editors Note: Larry Bernstein, a frequent contributor to TTN-
Online, is President of the National Software Council
(http://www.CNSoftware.org).
When I was technical director for anti-missile systems tests I worried
about software reliability. Unit, block, system, scenario and stress
tests were done. But with congressional investigations overhanging two
successive failures, these conventional tests were not enough for me. I
insisted on repeatedly re-running the same simulated target and
intercept trajectories. Peers ridiculed me, they said, "the same
software that works for a given input will always work."
With a four-processor system and random noise generators perturbing the
simulated radar data there were slight timing differences in each run.
After 65 repeated mission simulations for the first mission we found
nothing but some marginal memory boards. To humor me and because the
computer hardware was being stressed these tests continued.
The payoff came after 105 mission reliability runs for the second
mission when to everyone's surprise and my glee an operating system
defect in tape handling aborted the mission simulation. Investigation
of this defect that it could have caused a real mission failure.
Mission reliability tests showed the importance of preventive testing
and led to the notions of preventive design. Software Rejuvenation
technology can be traced back to those early days of mission reliability
testing. My dream is that all software systems adopt this technology.
========================================================================
Remote Testing Technology with TestWorks:
A Disciplined Remote Testing Approach vs. Rolling Betas
INTRODUCTION
There has been a great deal of discussion in a range of technical and
trade journals about the increasing use of "rolling beta" tests. In a
rolling beta a company releases a product, typically downloadable off
their WebSite, Early adopters can get to try the product out under the
agreement that the product is, by definition, not a final release, and
that there which will likely be bugs and other design and implementation
problems. From time to time, upgrades to the trial product are put on
the WebSite and current users are invited to download that version --
replacing their current version with it. This continues until either
(1) the users get frustrated with it or (2) there is a stable enough
version available so that the [presumably then expanded] user community
will be happy with it.
Rolling betas can be effective for the software supplier and certainly
are way to get a LOT of feedback about a new release from a LOT of users
of a popular product. This has been the case for several versions of
Netscape Communications's Netscape SWeb Browser software, and in
particular with Communicator 4.n, which is currently in last stages of a
rolling beta release.
There is no quarrel here with the notion of using beta sites. Virtually
all software development activities now involve some form of early
full-scale testing of the completed product. But if a product does not
have the "pull" to help users over the hump, or if the corporate image
can't stand that kind of potential negative, then other methods have to
be found to do beta testing. In part this is the justification that
underlies the Remote Testing Technology that is being introduced in
stages in coming months as part of the TestWorks product line and
technology.
REMOTE TESTING OR JAVA APPLETS
TestWorks capabilities for Java include a preliminary form of remote
testing that can be demonstrated on the TestWorks website
(http://www.soft.com). A fully instrumented Java implementation of J-
Othello asks the player for an Email address and, using newly introduced
Proprietary TestWorks Remote Testing Technology, collects a complete
tracefile and records it to a file on the TestWorks website.
After the data is collected and a coverage report is generated, the
report is Emailed to the indicated Email address.
This data collection does not require an applet user's permission but
SR/TestWorks technologists are *strongly* recommending that users be
made aware -- as is done in the J-Othello demonstration -- that this
very detailed kind of data is being collected.
REMOTE TESTING WITH C/C++ APPLICATIONS
The remote testing paradigm is not constrained to work only for Java
applications or applets. The same kind of data collection for C/C++
applications can be done provided that a beta site has Email. A fully
instrumented C/C++ application carries with it a special version of the
TCAT/C-C++ runtime that Emails coverage results to a specified Email
address.
Such test tracefiles, being in fully reduced form, are relatively small
even for a large application. After collecting a number of tracefiles
from a number of users the coverage report begins to approximate an
"operational profile" -- like that needed for calculation of a true
software reliability figure.
For complete information about the new remote testing technologies and
their possible application to your testing situation, send an Email
request for the Remote Testing Technology white paper to sales@soft.com.
========================================================================
Announcement and First Call for Papers
The 2nd International B Conference
Montpellier, France
April 22-24 1998
URL: http://www-lsr.imag.fr/B98/
Organized by the B Conference Steering Committee (APCB)
Supported by the Z User Group (ZUG), the B User Group (BUG)
and
LIRM, University of Montpellier, France
Aims and Scope:
Following the success of the First B Conference which was held in Nantes
in November 1996, the users of B have expressed their interest in a
second conference. This conference aims to provide a forum for the
rapidly growing community working in specification and software
construction with the B method. The scope of the conference covers all
aspects related to the B technology. Topics of interest include (but are
not limited to):
- Industrial applications and case studies using B;
- Integration of the B method in the software development lifecycle
(technical as well as economical aspects);
- Software testing versus proof-oriented development;
- Theoretical issues about the proof process and proof validation;
- Support tools for the B method;
- B and other specification languages;
- Proposals for B extensions.
Important dates:
Deadline for paper submission: October 13, 1997
Notification of acceptance: December 17, 1997
Camera-ready version due: January 26, 1998
Conference dates: April 22-24, 1998
Submission:
Authors are invited to submit full papers for the conference.
Submissions must not exceed 15 pages in the LNCS format. The cover page
must clearly identify the author's name, address, phone, fax number and
electronic address and a 150 word abstract. Papers should be send by
electronic mail or by surface mail (5 hard copies) to the program chair:
Didier Bert E-mail: B98@imag.fr
LSR-IMAG, BP 72
38402 Saint-Martin-d'Heres CEDEX
France
Submitted papers must present original work and must not be
simultaneously under review for any other conference nor submitted to a
journal. They must be written in english. The organizers intend to
publish the proceedings in the Springer-Verlag collection of Lecture
Notes in Computer Science. Authors are invited to use the LaTeX LNCS
style from the beginning. Details about the right style for typing
papers are given below in the section "Instructions for the authors".
Program Committee:
Didier Bert, chair CNRS, LSR-IMAG, Grenoble, FR
Pierre Bieber ONERA-CERT, Toulouse, FR
Egon Boerger Univ. of Pisa, IT
Claude Boksenbaum Univ. of Montpellier, FR
Jonathan Bowen ZUG, Univ. of Reading, UK
Pierre Desforges RATP, Paris, FR
Ranan Fraer Intel, IL
Robert B. France Florida Atlantic Univ., FL, USA
Marc Frappier Univ. de Sherbrooke, CANADA
Philipp A. Heuberger TUCS, Abo Akademi Univ., Turku, FI
David Lightfoot Univ. of Oxford Brookes, UK
Fernando Mejia GEC-Alsthom, Paris, FR
Ken Robinson Univ. of South Wales, AUSTRALIA
Pierre-Yves Schobbens Univ. of Namur, BE
Educational issues session:
A session devoted to educational experience and issues is planned as
satellite meeting of the conference. To get more information, contact:
Steve E. Dunne: S.E.Dunne@tees.ac.uk
Henri Habrias: Henri.Habrias@irin.univ-nantes.fr
Location:
The conference will take place in Montpellier, a city in the south of
France, close to the Mediterranean Sea. It is organized by the LIRM, the
department of Computer Science of the University of Montpellier. Local
organization chair:
Claude Boksenbaum E-mail: boks@lirmm.fr
LIRMM
161, rue Ada
F-34392 Montpellier Cedex 5 FRANCE
Instructions for Authors: All the instructions to get LaTeX and TeX
styles of the llncs format can be found in the file "printing.txt" at
the ftp address (login name: anonymous):
ftp://ftp.imag.fr/pub/SCOP/Springer/
========================================================================
TestWorks Version Calibration: August 1997
Here is a short summary of the current release levels of all of the
products in the TestWorks line. If you're a TestWorks user on
maintenance you are entitled to free upgrades to these versions (check
your ".PRODUCED" file in $SR on UNIX for the exact versions you are
currently using).
UNIX Platforms (SPARC/SunOS, SPARC/Solaris, x86/Solaris, RS-6000/AIX,
SGI/IRIX, HP-9000/HPUX, x86/SCO-ODT, x86/UnixWare, DEC-Alpha/OSF-4):
Regression Bundle: Capbak/X Ver. 5.2, SMARTS Ver. 6.5, EXDIFF Ver.4.2,
CAPBAK/UNIX Ver.3.3.
Coverage Bundle: TCAT C-C++, Ver. 9.2, TCAT for Java, Ver. 1.1, TCAT
for Ada/F77, Ver. 8.2, S-TCAT for Ada/F77, Ver. 8.2,
TCAT-PATH (C, C++, F77, Ada), Ver. 8.2, T-SCOPE,
Ver. 3.1.
Advisor Bundle: METRIC (C, C++, F77, Ada), Ver. 1.3, STATIC (C) Ver.
1.2, TDGEN Ver. 3.4.
Windows Platforms (Windows 3.1n, Windows '95, Windows NT 3.n, Windows NT
4.n):
Regression Bundle: CAPBAK/MSW, Ver. 2.6 (Windows 3.n), CAPBAK/MSW, Ver.
3.1 (Windows '95/NT), SMARTS/MSW, Ver. 2.6.
Coverage Bundle: TCAT/C-C++, Ver. 1.5.
========================================================================
IEI - CNR and QUALITAL present
The Fourth International Conference on
"Achieving Quality in Software:
Software Quality in the Communication Society"
Venice, 31 March - 3 April 1998
THE CONFERENCE
To get the right information, wherever, whenever and just the way it is
needed for use: That is the essence of communication, which has never
played such a fundamental role in all aspects of human life as it does
today. It can hardly be said that software, with all its processes
involved, isn't responsible for achieving such goals.
Then, let us put the traditional issues of AQuIS this way: how can our
classic, multidimensional software quality models for processes and
products be generalized to include all the expected properties of the
components and systems involved in communication? Do they already
include everything is needed to cope with any new quality requirements?
The paroxistically increasing presence of multimedia multisite multiview
active objects of certain/uncertain behavior, swarming and lurking
throughout the Internet, perhaps escaping even their very creators,
might be nothing but slightly annoying noise with a few pleasant notes,
but could be a threat to incautious users as well. In any case, the
point deserves some attention, and this is a quality issue.
Likely, quality in software may always be improvable, but perhaps never
fully achievable, as quality notion evolves, and software appearance,
structure and behaviour evolve too, so the challenge remains. Stress on
components and processes for communication is not really new in the
Conference: Quality only makes sense if human beings are involved, and
so does the transfer of information, no matter of the starting and
ending points.
The Conference is aimed to assess, for the fourth time since 1991, what
has been done with the use of models, methods, techniques for quality
within the industrial world and what has been proposed, if anything has,
from the research area. Exploring the existence of the bridge between
the two sides and probing its validity has been AQuIS peculiarity since
then. Let's check if the bridge is still there and carries good news
both ways across.
Quality papers about status reports and trends, lessons learned, models
and methods for quality are strongly sought for. Submitted papers must
not have appeared on, or be under consideration by, other conferences
or journals.
Topics include but are not limited to:
* Quality models (formal/informal) for processes and products
* Process and product quality evaluation
* Quality of multimedia applications
* Quality of distributed applications
* Quality of www sites
* Role of standards
* Security issues
* Human factors
* Quality of user interfaces
* Project risk management
* Testing issues: target environments, distributed applications, reliability testing
* Experiences on technology transfer
INSTRUCTION FOR AUTHORS
Four copies (in English) of original work, limited to 12 pages (5000
words), must reach the Scientific Conference Secretariat before December
12, 1997. Papers must include a short abstract and a list of keywords,
the author's address, phone and fax number and E-mail address. All
papers received will be refereed by the International Program Committee
and each paper will be reviewed by at least three independent referees.
Final accepted papers will be published in the Conference Proceedings.
CONFERENCE ORGANIZATION
General Chair: Carlo Ghezzi, Politecnico Milan - I
Program Chair: Mario Fusani, IEI-CNR - I
Program Committee (provisional):
P.Ancilotti ITA B.Kraemer GER
M.Azuma JAP J.Leite BRA
A.Bertolino ITA M.Marre' ARG
S.Bologna ITA E.Miller USA
G.Bucci ITA D.Natale ITA
M.Bush USA B.Nuesibeh UK
A.Cimitile ITA K.Ochimizu JAP
A.Coletta ITA L.Osterweil USA
F.De Nazelle FRA E.Peciola ITA
G.Di Lucca ITA T.Rout AUS
A.Dorling SWE J.Sanders IRE
F.Fabbrini ITA Z.Shiyong CHI
I.Forgacs HUN J.Souquieres FRA
A.Fuggetta ITA T.Stalhane NOR
R.Glass USA L.Strigini UK
H.Hausen GER A.Wolf USA
P.Inverardi ITA K.Yasuda JAP
M.Jazayeri AUT
Organization Chair: Piero De Risi, QUALITAL - ITA
Organizing Committee:
Cristina Franceschi QUALITAL - ITA
Vinicio Lami IEI- CNR - ITA
Giacomo Petrini QUALITAL - ITA
Scientific Conference Secretariat:
Fabrizio Fabbrini
IEI-CNR
Via S. Maria, 46 Tel.: +39-50-593505
56126 Pisa, Italy Fax.: +39-50-554342
e-mail: f.fabbrini@iei.pi.cnr.it
IMPORTANT DATES
Papers due (four copies): December 12, 1997
Notification to authors: February 3, 1998
Camera ready copy: February 18, 1998
SELECTED PAPERS FROM THE AQuIS '98 PROCEEDINGS WILL BE PUBLISHED IN A
SPECIAL ISSUE OF THE "JOURNAL OF SYSTEMS AND SOFTWARE" (NORTH HOLLAND)
========================================================================
Nightmare of the Month Club: A WINNER!
$50 For This Contribution to Link Hochnadle
"Features Not Required!"
Our first beta release had shipped, and we started testing volume
database updates using a "home-grown" transaction generator. Small
samples worked great. The first big overnight test failed, causing
complete system failure and loss of all data. Consensus was - "the app"
works, we've been running it for months - ergo, something must be wrong
with the transaction generator.
Having written the transaction generator, I got the shaft. Second night
I stayed up with baby for several hours, finally stepped out for a
nature break - I was back in 5 minutes, but not soon enough. Another
total loss. Third night, my five-hour vigil was rewarded with the
cryptic message: "Debug Stack OverFlow," which flashed on-screen a
second before the crash. The transaction generator did not have any
debug stack. At the 800th transaction, the app had crashed the system.
A home-grown trace mechanism in the app had been pushing a record on the
"debug stack" for every transaction entered into the database. Due to
pervasive misuse of an exit macro, the stack almost never got popped,
eventually resulting in the overflow.
My revenge: coding a "stack abuse" dialog in the app, which popped up
whenever the "debug stack" should have been, but wasn't. It also
disabled the trace feature for the remainder of the run, but warned that
dire problems could be anticipated in the future if the error was not
immediately reported on the trouble hot line.
A month of merriment followed, as the testers reported stack-abuse bugs
by the score, at all hours of the day and/or night. I, on the other
hand, slept quite well for a change.
>:-)
========================================================================
First European Conference on
Achieving Software Product Quality
Developing, Testing, Evaluating for 'Good Enough' Quality
Dublin, IRELAND: 15-16 September 1997
FULL DETAILS: http://www.cse.dcu.ie/essiscope
Providing, over 2 days, 2 keynote addresses, 10 presentations, a number
of case studies, and 4 half-day tutorials with a selection across 2
parallel streams each day.
Presentations will address testing and evaluation, software development,
usability and standards and focus on improving and evaluating software
product quality. A number of short case studies will give practical
experiences.
Keynotes: Les Hatton, UK and Mary Corbett, Ireland
The event is to be held in Trinity College, Dublin, Ireland
For further information, please contact : Fiona Clince, Centre for
Software Engineering, DCU Campus, Dublin 9, IRELAND
Tel: +353 1 704 5750 Fax: + 353 1 704 5605 Email: admin@cse.dcu.ie Web
site: http://www.cse.dcu.ie/essiscope
About the Conference
This is the first conference on Product Quality to be held in Europe.
The event is split across two days. 15 Spetember is conference day.
Les Hatton will open the conference with a lively presentation entitled,
"Why do we keep making the same mistakes?"
The conference will then divide into two parallel strands, one dealing
with Testing and Evaluation, the other with aspects of Software
Development related to product quality.
Following lunch a number of short case studies will be presented on
evaluation and certification experiences and also the results of a
number of process improvement experiments (PIE) will be discussed. Then
once again the conference will divide into two parallel streams, one on
the User Perspective and one on Standards.
The conference will end with a second keynote speaker, Mary Corbett, who
will address many key aspects of designing for usability.
16 September is the tutorial day, there are 4 tutorials in total - 2 in
parallel, both in the morning and afternoon. The tutorials will cover
quality function development (QFD) to define requirements, structured
testing using TMAP, user oriented software product specification and
evaluation and Methods for specifying and evaluating usability as
quality in use.
Jackie Daly
Consultant, Centre for Software Engineering
Dublin City University Campus, Dublin 9, Ireland
email: jackie@cse.dcu.ie
Tel: +353-1-704-5612 Fax: +353-1-704-5605
Web: http://www.cse.dcu.ie
For MUCH MORE info, visit http://www.avnet.co.uk/SQM/
For LESS info, send email with "unsubscribe" in the body of the message
to sqm-request@avnet.co.uk
========================================================================
ICSM '97
International Conference on Software Maintenance 1997
Bari, Italy
September 29-30, October 1-3, 1997
Advance Program and Registration Information
Full program, in html and PostScript, with on-line registration:
http://www.cis.ohio-state.edu/~harrold/icsm97/
Contact: Nicholas Zvegintzov, Co-Publicity Chair
Software Management Network
141 Saint Marks Place, Suite 5F
Staten Island NY 10301 USA
telephone +1-718-816-5522, fax +1-718-816-9038
email 72050.570@compuserve.com
Sponsored by IEEE Computer Society, in cooperation with ACM, CRIM,
InfoCamere, Netsiel, O.Group, Software Maintenance News, Sogei, and
Telecom Italia
Historically, software maintenance practices have focused on the
development of tools and techniques for the maintenance of existing
systems. However, emerging technologies, such as the World Wide Web and
Java, frameworks, and software architectures, present both new problems
for maintainers and new opportunities for addressing maintenance
problems.
ICSM'97 will provide an international forum for researchers, developers,
and users interested in maintenance issues for both existing and
emerging software systems. Work on all aspects of software maintenance
is welcome. Of particular interest, however, is work that utilizes
emerging technologies, or that addresses the problems of maintaining
software that utilizes such technologies.
The theme of ICSM'97 is "Evolution of Legacy and Emerging Systems" and
includes tutorials, paper and panel presentations, an industry track,
and a tools fair.
Participants include practitioners and researchers from industry,
academia, and government.
Monday, September 29, 1997
Tutorial 1 (all day, 9-5:30):
Java and Security
Gary McGraw
Tutorial 2 (half day, 9-12:30):
Software Testability
Jeffrey Voas
Tutorial 3 (half day, 9-12:30):
Comprehension and Evolution of Legacy Software
Vaclav Rajlich
Tutorial 4 (half day, 2-5:30):
A Primer on Empirical Studies
Dewayne Perry, Adam Porter, Larry Votta
Tutorial 5 (half day, 2-5:30):
Using Program Decompositions in Software Maintenance
Keith Gallagher
Tuesday, September 30, 1997
Tutorial 6: (half day, 9-12:30)
Year 2000: Analyzing the Impacts and Managing the Effort
Shawn Bohner
Tutorial 7 (half day, 9-12:30):
Validating and Applying Reliability, Risk, and Test Metrics for
Measuring and Evaluating Maintenance Processes
Norman Schneidewind
Tutorial 8 (half day, 2-5:30):
Year 2000: Conversion, Testing, and Technology
Nicholas Zvegintzov
Tutorial 9 (half day, 2-5:30):
Software Maintenance: A Practical Approach
Thomas Pigoski
Wednesday, October 1, 1997
9:00 - 10:30 Session 1: Introduction and Keynote Address
Software Engineering Issues for Network Computing, Carlo Ghezzi,
Politecnico di Milano
11:00 - 12:30 Session 2a: Program Understanding
Chair: H. Muller (University of Victoria)
Reverse Architecting Approach for Complex Systems, R. Krikhaar
Hypothesis-Driven Understanding Processes During Corrective
Maintenance of Large Scale Software, A. Mayrhauser, A. Vans
Effects of Decomposition Techniques on Knowledge-Based Program
Understanding, S. Abd-El-Hafiz
Session 2b: Models
Chair: T. Khoshgoftaar (Florida Atlantic University)
Predicting Maintenance Effort with Function Points, F. Niessink, H. van Vliet
Modeling Software Maintenance Requests: A Case Study,
E. Burch, H. Kung
Measuring Abstractness for Reverse Engineering in a Reengineering
Tool, H. Yang, P. Luker, W. Chu
2:00 - 3:30 Session 3a: Program Understanding
Chair: V. Rajlich (Wayne State University)
Finding Components in a Hierarchy of Modules: A Step Towards
Architectural Understanding, J. Girard, R. Koschke
Program Understanding Using Program Slivers -- An Experience
Report, A. Gupta
Program Understanding and Maintenance With the CANTO Environment,
G. Antoniol, R. Fiutem, G. Lutteri, P. Tonella, S. Zanfei, E. Merlo
Session 3b: Models
Chair: L. Briand (Fraunhofer IESE)
A Model for Change Propagation Based on Graph Rewriting, V. Rajlich
Structural Information as a Quality Metric in Software Systems
Organization, G. Visaggio
Constructing Bayesian-network Models of Software Testing and
Maintenance Uncertainties, H. Ziv, D. Richardson
4:00 - 5:30 Session 4a: Panel - Software Maintenance Outsourcing
Chair: P. Gargiulo (NETSIEL)
A. Pizzarello (Peritus Software Services), D. Paschina (Alitalia
D.S.I), C. Pietrosanti (Aeroporti di Roma Software Center), S.
Bohner (META Group)
Session 4b: Object-Oriented Migration and Coexistence
Chair: G. Antoniol (IRST)
Effect of Object Orientation on Maintainability of Software, G. A.
Kiran, S. Haripriya, P. Jalote
Migrating Legacy Systems Towards Object-Oriented Platforms, A.
DeLucia, G.A. DiLucca, A.R. Fasolino, P. Guerra, S. Petruzzelli
An Experimental Comparison of the Maintainability of
Object-Oriented and Structured Design Documents, L. Briand, C.
Bunse, J. Daly, C. Differding
Thursday, October 2, 1997
9:00 - 10:30 Session 5a: Industry Track
Chair: T. Pigoski (TECHSOFT)
Non-Obvious Maintenance Measurement Pitfalls in Industry, H. Frank,
K. Schneider (DaimlerBenz)
An Integrated System for Software Assets Management and Information
Retrieval, C. Pietro, C. Giovanni, M. Antonio (I. T. Staff)
Beyond the XX Century: An Industrial Approach to Solve the Year
2000 Software Problem, R. Dabicco (Netsiel)
Identifying "Risk-to-Maintain" Software: An Experience Report, P.
Antonini (CRISALIDE Datitalia-Processing)
Metric Controls for C and C++ Languages, G. Albanese (CRIAI), L.
Giann (SOGEI)
Session 5b: Software Evolution
Chair: A. Cimitile (University of Naples)
Software Black Box Mechanism: A Pragmatic Method for Software Crash
Diagnosis and Usage Maintenance Testing, Z. He, G. Staples, M.
Ross, I. Court
MORALE: Mission Oriented Architectural Legacy Evolution, G. Abowd,
C. Ertmann-Christiansen, A. Goel, D. Jerding, M. McCracken, M.
Moore, J. W. Murdock, C. Potts, S. Rugaber, L. Wills
Software Evolution Observations Based on Product Release History,
H. Gall, M. Jazayeri, R. Klosch, G. Trausmuth
11:00 - 12:30 Session 6a: Panel - The Transition to Network
Computing
Chair: F. Castiglioni (Consorzio CORINTO)
M. Missikoff (CNR IASI), W. Pistarini (IBM Global Services), N.
Schneidewind (Naval Postgraduate School), H. Zampariolo (IBM)
Session 6b: Static and Dynamic Analysis
Chair: K. Gallagher (Loyola College, Maryland)
Identifying Modules via Concept Analysis, M. Siff, T. Reps
Dynamic Traceability Links Supported by a System Architecture
Description, E. Tryggeseth, O. Nytro
Intraprocedural Static Slicing of Binary Executables, C. Cifuentes
2:00 - 3:30 Session 7a: Software Evolution and the Year 2000
Problem
Chair: S. Bohner (META Group)
DLAs Year 2000 Conversion and Compliance Program: Managing a
Large-Scale Maintenance Initiative Across the Organization, S. Reed
Living with the 2-digit Year, Year 2000 Maintenance Using a
Procedural Solution, E. Lynd
When Counting Counts: Measuring the Maintenance Process (Invited
Presentation), S. Pfleeger
Session 7b: Process
Chair: M. Schrank (MITRE Corporation)
Characterizing the Requirements Change Process for a Large System,
K. El Emam, D. Hoeltje, N. Madhavji
CREP - Characterizing Reverse Engineering Process Component
Methodology, M. Tortorella, G. Visaggio
Measuring and Evaluating Maintenance Process Using Reliability,
Risk, and Test Metrics, N. Schneidewind
4:00 - 5:30 Session 8a: Software Evolution
Chair: K. Bennett (University of Durham)
Experimental Analysis of the Cognitive Processes of Program
Maintainers During Software Maintenance, K. Iio, T.Furuyama, Y.
Arai
Software Change Through Design Maintenance, I. Baxter, C. Pidgeon
Viewpoints as an Evolutionary Approach to Software System
Maintenance, P. Alencar, D. Cowan, C. Lucena, T. Nelson
Session 8b: Improved Maintainability
Chair: L. Mancini (O.Group)
Experiences Developing and Maintaining Software in a Multi-Platform
Environment, T. Pearse, P. Oman
Designing for Increased Software Maintainability, J. Han
A Formal Transformation and Refinement Method for Re-engineering
Concurrent Programs, E.J. Younger, K.H. Bennett, Z. Luo
Friday, October 3, 1997
9:00 - 10:30 Session 9: Joint ICSM/WESS Keynote Address
Analysis for Reuse and Maintenance: A Program for Experimentation,
Victor R. Basili, University of Maryland
11:00 - 12:30 Session 10a: Panel - The Impact of Distributed Object
Technology on Reengineering
Chair: S. Tilley (Software Engineering Institute)
H. Muller (University of Victoria), K. Wallnau (Software
Engineering Institute), H. Sneed (Software Engineering Services
GmbH), M. Olsem (Software Technology Support Center)
Session 10b: Static and Dynamic Analysis
Chair: L. White (Case Western Reserve University)
Low-Threat Security Patches and Tools, M. Bashar, G. Krishnan, M.
Kuhn, E. Spafford, S. S. Wagstaff, Jr.
Assessing the Benefits of Incorporating Function Clone Detection in
a Development Process, B. Lague, D. Proulx, E. Merlo, J. Mayrand,
J. Hudepohl
Investigating the Maintenance Implications of the Replication of
Code, E. Burd, M. Munro
10:45 - 6:30 1997 IEEE Workshop on Empirical Studies of Software
Maintenance (WESS'97)
(http://www.cs.umd.edu/~lanubile/wess97
ICSM '97 registrants please fax or mail this form with payment by September 5, 1997 to:
IEEE Computer Society
ICSM '97 Registration
1730 Massachusetts Ave., N.W.
Washington, D.C. 20036
Fax: +1-202-728-0884
Phone: +1-202-371-1013
========================================================================
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 ##