|
|
Seminar: Testing Object Oriented Software in real life
|
|
From: David Grietens [SMTP:david@highq.be]
Sent: zondag 2 mei 1999 12:55
To: MEMBERS@BSUG.ORG
Subject: [BSUG] Seminar: Testing Object Oriented Software in real life
Dear BSUG member,
We (BSUG) are very proud to announce our first one day seminar. This
seminar, that is organised in cooperation with the technological institute
(TI-KVIV), will focus on testing object oriented software. Speakers from
the US, Switserland, Holland and Belgium will present their experience
with the subject of OO testing.
We are especially very proud to have Kent Beck among our speakers. Kent
Beck is one of the most experienced Smalltalkers in the world and on top
of that he is a very talented speaker
So, be sure not to miss this unique event.
David Grietens
Chairman BSUG
info@bsug.org
--------------------------------------------------------------------------
---------------------------------------------------------------------
One day seminar + exhibition
Testing Object Oriented Software in real life
Tuesday 1 June 1999
Leuven, Belgium
--------------------------------------------------------------------------
---------------------------------------------------------------------
Organisation
--------------------
Technologisch Instituut, Section on Software Metrics & Software Testing
and BSUG (The Belgian Smalltalk User Group)
Abstract
-------------
Testing will never prove that a software system will never fail, one can
only show that it contains faults [Ivar Jacobson; Object Oriented Software
Engineering 1992]
Starting from this perspective, it is clear why most projects try to
minimise testing activity. More and better testing will result in more
errors, which means more work to fix them. This explains why the only good
approach to testing is a disciplined and structured approach. Planning for
testing activities before a project starts is more an exception than a
rule in software development projects. This hasn't changed very much with
the introduction of object oriented development techniques. Nevertheless,
object oriented methods offer new opportunities to testing, but also new
problem issues that need special attention. This makes testing object
oriented software similar but different to testing a classical developed
system.
This seminar will explain the specific issues related to testing object
oriented software in order to attain the expected quality level. The
cooperation between BSUG vzw and KVIV vzw resulted in this exceptional
event that brings together speakers experienced in both software testing
and object oriented software engineering. They will present new insights
and solutions to the testing aspect of the object oriented software
development process in different problem domains.
David Grietens
Chairman BSUG vzw
e-mail: info@bsug.org
Bruno Peeters
Chairman of the Section on Software
Metrics & Software Testing
BSUG
---------
The Belgian Smalltalk User Group vzw (BSUG) is a non profit organisation
that serves the interests of people involved in Smalltalk based
development and/or the commercialisation of Smalltalk related products.
BSUG has been active since 1992. Its main goals are to generate interest
in Smalltalk, create a synergy between all its members, increase the
overall technological capacity of everyone involved in Smalltalk based
development, help Smalltalk grow within Belgium and advocate the
technology. BSUG tries to realize these goals by communicating Smalltalk
related news, providing a networking environment among smaltalkers,
exposing Smalltalk success stories worldwide, maintaining a web site
(http://www.bsug.org) and communication media, activating technical and
commercial studies and organizing regular meetings, lectures, courses and
seminars that will show technical ideas, experience and commercial
products.
Venue
---------
Congress Centre Brabanthal
Research Zone Haasrode
Brabantlaan 1
3001 LEUVEN
Tel: +32 (0)16.38.30.11
Audience
--------------
OO software developers, technical managers, project managers
All people involved in classic testing wanting to learn about the
specifics of OO testing
Schedule
--------------
8:30 9:00 onthaal
9:00 9:05 opening (David Grietens, Chairman BSUG vzw)
9:05 10:05 Van Veenendael (Improve Quality Services)
10:05 10:50 Freddy Potargent (IMEC)
10:50 11:20 Coffee - Exhibition
11:20 12:45 Michael Silverstein (Silvermark, Inc)
12:45 14:00 Lunch - Exhibition
14:00 14:45 Koen Vranken (Euroclear)
14:45 15:30 Sam Michiels (KULeuven)
15:30 16:00 Coffee - exhibition
16:00 17:30 Kent Beck (Daedolos)
17:30 17:45 Closing
Programme
-------------------
OO and black box testing
Erik Van Veenendaal
Improve Quality Services
Speaker
------------
Drs. Erik P.W.M. van Veenendaal CISA has been working for many years as a
practitioner and manager within the area of software quality including
quality management, project control, EDP-auditing and software testing. He
specializes in software testing and is the author of "Structured testing;
an introduction to TMap" and "Software quality from a business
perspective". He is a regular speaker both at national and international
testing conferences and a leading international trainer in the field. Erik
van Veenendaal is the founder and managing director of Improve Quality
Services, a company that provides services in the area of quality
management and testing. , Erik is also involved in lecturing and research
activities on a part-time basis at the Eindhoven University of Technology,
Faculty of Technology Management. Furthermore, he is on the Dutch
standards institute committee for software quality.
Abstract
------------
Object orientation is by definition a system development approach. A black
box system or acceptance test engineer is focused towards the
functionality and externally visible characteristics of an information
system. In principle he doesn't need any knowledge of the system's
implementation. However, does this principle also apply to testing an
information system that has been developed using an OO approach ? If not,
what are the consequences, e.g. which techniques should be used, which
quality characteristics are important to test, etc. ?
This presentation will try to answer to questions raised above, mainly
based on a practical example regarding black box testing of an OO
information system. The example concerns Oce Technologies B.V. (The
Netherlands) where currently a Product Data Management System (PDMS) is
being implemented. The PDMS is a OO package developed in C++.
System verification in an
Object-Oriented hardware design flow
Freddy Potargent
IMEC, div. INVOMEC
Speaker
------------
Freddy Potargent graduated in 1987 as an Industrial Engineer in
electronics. He started his career as a developer of Compact Disc
servosystems at Philips Hasselt. There he advanced to system developer,
involved in both hardware and software design. In 1993 he moved to APEX as
chief engineer of development, responsible for the design of professional
studio and broadcast audio equipment. Since May 1998 he is employed at
IMEC performing research on design methodologies for embedded systems
using object-oriented technology
Abstract
------------
The complexity and heterogeneity of todays systems, integrated on a chip,
has led to the use of Object Oriented methodologies for hardware designs.
This introduces the unique requirements of hardware testing and
verification issues to the OO world. We at IMEC use an in-house developed
C++ environment, called Ocapi, that supports OO modeling and
design of complex chips in a seamless way from algorithmic specification
to implementation. The specific requirements of hardware validation and
the integrated support in the OO environment will be presented. The
effectiveness of the validation strategies is illustrated by several
industrial-strength designs.
Testing Smalltalk Applications
Michael Silverstein
SilverMark, Inc.
Speaker
------------
Michael Silverstein is lead architect and a cofounder of SilverMark, Inc.,
a leading provider of automated testing tools for Smalltalk. He has been
developing software for 18 years, with the last seven using Smalltalk.
Prior to SilverMark, Michael developed a wide variety of applications at
IBM and was a member of the VisualAge for Smalltalk team.
Abstract
------------
One of the attractions of Smalltalk's highly interactive development
environment is the ability to execute code piecemeal as you develop it.
This technique certainly speeds the process of assembling code into
working units but it should not be taken as a substitute for formal
testing.
In this session we will present technical strategies for formalized
testing of Smalltalk applications. We will focus on practical techniques
for leveraging Smalltalk's unique strengths, determining where to
concentrate testing energies, model vs. view testing, selecting test
objects, designing reusable, scalable and maintainable automated tests,
testing in teams,
development practices that promote testability, and tools.
The NEXT project
Koen Vrancken, Xavier Van Dessel
Euroclear
Speaker:
-------------
Xavier Van Dessel has worked since 1993 at Euroclear. He started at
Operations and was involved in NEXT as Project Leader, before moving to
Software Engineering, where he took responsibility over the Configuration
Management group. Currently he is working as independent contractor with
Flux Consultancy.
Koen Vranken has worked since 1993 at Euroclear. He started within
Applications Development, before moving to the Software Engineering group
for which he is
currently responsible. This group concentrates on Architecture,
Configuration Management, Methodology, SLA, Tool Support and Application
DBA.
Abstract
-------------
The Euroclear System is the world's largest clearance and settlement
system for internationally traded securities.The core Euroclear business
is to settle securities transactions on behalf of its participants
(broker/dealers, commercial and central banks, investment managers,
custodians, and supranationals from more than 80 countries). Over 100,000
different securities from over 30 markets are accepted for settlement
through the Euroclear System.
Three years ago, Euroclear started a major re-engineering project (NEXT),
in order to move its core system from a overnight batch towards a 24 hour
real-time system. An OO methodology was set in place and a custom made OO
framework encapsulates the COBOL/CICS/DB2 environment running on an IBM
mainframe. 400 man-years, with peaks of up to 200 people involved in the
development process, and no less than 8,000 scenarios make the NEXT
project undoubtably one of the biggest OO projects in the world ever
perfomed.
This presentation will focus on the methodological and technical aspects
of the different tests done. Furthermore it will stress the importance of
integration with configuration and environment management to ensure code
consistency (through controlled delivery mechanisms and impact analysis)
and availability.
Testing concurrent system software
Sam Michiels
KULeuven, Dept. Computer Science
Speaker
------------
Sam got his degree in Informatics in 1996 at the University of Leuven
(KUL). Since then, he has been a research assistant at that same
university for the DistriNet Research group, a group that studies
distributed systems and computer networks. The general aim of this
research group is to build distributed object support platforms for
advanced applications, using state of the art software technology.
Abstract
------------
The traditional and outdated view on system software development has been
based on the dream of full reuse: system software has been defined as a
large reusable entity that an application developer has to accept and live
with. DistiNet's policy is to develop open systems with generic parts
which are shared by many applications, as well as customized parts that
are specialized for particular application areas, for individual
applications and even for particular executions of applications.
In developing an advanced communication architecture, testing is a
critical success factor. Different components can be differentiated, like
the communication platform (API and proxy layer), the invocation system
(Object Request Broker), a customized protocol stack, etc.
Each of these components is subject for black-, white- and gray-box
testing. To identfify, document and test different paths of execution and
external circumstances, we make use of test cases.
One of the components, the protocol stack, is a highly concurrent
subsystem. This reflects in specific testing strategies. Moreover
concurrency should be considered during design, so that concurrency
failures (e.g. deadlock) are avoided in the first place, instead of to be
solved.
Confidence
Kent Beck
Daedalos
Speaker
------------
Kent Beck has been writing Smalltalk for 14 years. In that time he has
been involved in developing the widely used and copied frameworks HotDraw
and SUnit, and in pioneering the software engineering ideas CRC cards,
software patterns, and now Extreme Programming. He is currently employed
as a consultant with Daedalos Consulting, and living in Zurich,
Switzerland. He is the author of more than 50 technical articles, The
Smalltalk Best Practice Patterns, Kent Beck's Guide to Better Smalltalk (a
compilation), a contributing author to Martin Fowler's book Refactoring,
and author of the coming Extreme Programming: Embracing Change.
Abstract
------------
The primary goal of writing automated tests is to earn and maintain
confidence in the behavior of your system. This talk will demonstrate how
to use the SUnit framework to make writing automated tests part of your
daily routine, and discuss how to exploit the power you gain from writing
automated tests.
---------------------------------
General information
---------------------------------
Registrations
--------------------
Preferably before May 25, 1999 by returning the enclosed registration form
to Technologisch Instituut vzw
Further details about participation to the exhibition can be asked at the
secretariate mentioned below
Registration fee
-------------------------
15.000 BEF (+21% VAT)
12.500 BEF (+21% VAT) for members TI-KVIV and/or BSUG
10.000 BEF (+21% VAT) for members academics / civil servants
900 BEF (+21% VAT) for students (excl lunch)
The registration includes the texts of the lectures, lunch and coffee.
Payments are to be made on receipt of the invoice. Cancellation is
possible until 1 week before the date of the seminar in which case 25% of
the registration fee will be charged. In case of cancellation during that
week the full amount is due. Replacement of the person registered is
possible
Secretariate
--------------------
Technologisch Instituut vzw
Ingenieurshuis - KVIV
MR L. Baele, project co ordinator
Desguinlei 214
2018 Antwerpen 1
Tel: 03/216.09.96
Fax: 03/216.06.89
e-mail: luc.baele@ti.kviv.be
website http://www.ti.kviv.be
© 1998-1999 BSUG vzw.
|