|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The Belgian Smalltalk User Group is 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 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Programme | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
9:05 - 10:05 OO and Black Box TestingErik van Veenendaal (Improve Quality Services)SpeakerDrs. 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.AbstractObject 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++.10:05 - 10:50 System Verification in an Object-Oriented Hardware Design FlowFreddy Potargent (IMEC, div. INVOMEC)SpeakerFreddy 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 technologyAbstractThe 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.11:20 - 12:45 Testing Smalltalk ApplicationsMichael Silverstein (SilverMark, Inc.)SpeakerMichael 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.AbstractOne 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. 14:00 - 14:45 The NEXT ProjectKoen Vrancken and Xavier Van Dessel (Euroclear)SpeakersXavier 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. AbstractThe 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. 14:45 - 15:30 Testing Concurrent System SoftwareSam Michiels (KULeuven)SpeakerSam 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.AbstractThe 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. 16:00 - 17:30 ConfidenceKent Beck (Daedalos)SpeakerKent 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.AbstractThe 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. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Registrations | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Preferably before May 25, 1999 by returning the registration form
to Technologisch Instituut vzw
Further details about participation to the exhibition can be asked at the
secretariate mentioned below
Registration Fee
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 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driving Instructions | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Evaluation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Our first paid event has turned into a success. Although we had expected more people
interested into the subject of testing object-oriented software, the evaluation forms
proved that those who didn't come made the wrong decision. Testing Object-Oriented
Software in Real Life turned out to be a conference with a high added value to its
attendees, which is exactly our major concern.
74% of the attendees evaluated the conference overall as "good" (possible answers were very good, good, average, weak, poor). 4% even thought the conference was "very good". Especially the talks of Kent Beck (95% good to very good) and Mark Foulkrod (91% good to very good) were very much appreciated by the public. The venue was appreciated by 90% of the attendees and lunch must have been really good since all attendees (100%) said it was good to very good. You can expect more BSUG conferences like these in the future, so make sure to stay tuned and check out our website regularly.
Chairman BSUG vzw |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||