TOOLS Component and Object Technology Award

TOOLS Component and Object Technology Award

Post by TOOLS Conference » Sun, 18 Jul 1999 04:00:00

TOOLS Component and Object Technology Award

The TOOLS Components and Objects Prize will be awarded for the
first time on the occasion of TOOLS USA '99 (
in Santa Barbara, California, on August 2, 1999.

The TOOLS prize honors seminal contributions to the development
of object technology and component-based development. It will be
awarded annually and is intended to become the most important
award in the area of modern software technology. The prize
currently carries a $2,000 award contributed by Bertrand Meyer,
chairman of the TOOLS conference series.

The first TOOLS prize will be awarded to Professor David Parnas,
Director of the Software Engineering Programme at McMaster
University (Canada). Two of Parnas's pioneering articles published
in 1972, introduced the notion of "information hiding" which lies
at the basis of all modern approaches to software construction and
in particular component and object technology. His more than 200
articles have spanned many areas of software engineering and
provided contributions invaluable to anyone interested in reliable,
reusable and extendible programs and program families. His work
on such systems as the US Department of Defense's A7 project
and the Darlington Nuclear Generation Station in Canada has shown
unique insights into the application of systematic and formal
techniques to the development of safety-critical systems. Throughout
his career and publications, Dr. Parnas has provided leadership in
reconciling the theory of software engineering with the practice
of industrial software development.

Dr. Parnas has been Professor at the University of Victoria, the
Technische Hochschule Darmstadt, the University of North Carolina
at Chapel Hill, Carnegie Mellon University and the University of
Maryland. He received his B.S., M.S. and Ph.D. from Carnegie Mellon
University, and honorary doctorates from the ETH in Zurich and the
Catholic University of Louvain.

At TOOLS USA 1999, Dr. Parnas will be presenting a Keynote Lecture
on the theme "Tools for Component Documentation, Analysis and
Testing " and a Tutorial on the theme "Systematic Techniques for
Inspecting Critical Software", both on Monday, August 2. The TOOLS
prize will be awarded to him on the occasion of his keynote.

TOOLS ( is the major international practitioner-
oriented event in the field of object technology, component-based
development, and modern software technologies. Held regularly
since 1989, TOOLS (Technology of Object-Oriented Languages and
Systems) has regular sessions in the US, Europe, Australia and
China, with proceedings published by the IEEE Computer Society.
Past sessions have featured all the international leaders in the
field; TOOLS USA '99 is the most complete conference to date with
more than 60 invited lectures, tutorials and scientific contributions
by authors from more than 15 countries on all aspects of new
software technology.


1. Component/Object Technologies - Usability Issues

Hi all,
Has anyone thought about usability issues with component based technologies?
There seems to be a lot of talk these days of companies just building
components, and allowing users to simply put these together as they wish
into their own 'container' applications (such as Excel, Internet Explorer,
Visual Basic, etc).
While we see a number of advantages to this approach (it could let users
integrate different kinds of objects into their own custom applications), we
have also thought of some risks in terms of usability.
.People may not want to deal with objects. They may prefer to work with
pre-built applications.
.People might be happy to deal with components that are simple, but what
happens when they become complex and functionality-rich? We may be forcing
our users to become programmers, and they may not be interested in that -
they have other work to do!
.A lot of the UI decisions are in the container, in the way that we put
together the objects. If these objects are put together without much thought
for usability, the users' effectiveness might be compromised.
.It seems harder to implement validations and constraints with components. A
lot of usability issues happen in the relationships/links between objects.
.How are errors managed and reported? Components do not raise errors, but
pass an exception to the container. Is it fair to expect users to deal with
all these possible errors?

In general, we are concerned that the resulting applications would not be
well designed, but a confused, poorly integrated collection of objects.
Any thoughts on all this? Anyone know how people in general feel about using
components instead of actual applications? Any references?
Thank you for your thoughts.

2. CoCo 2 Memory Expansion

3. Changing models // How modify the painted objects on Components.

4. Is it me, or do Datasets suck? (kinda long)

5. Moving from Objects to Components

6. Sendmail and Request Systems

7. ObjectiveView Free Object and Component Technical Journal

8. Window Focus

9. CFP: USENIX Conference on Object-Oriented Technologies and Systems

10. 2nd Conference on Object-Oriented Technologies and Systems (COOTS):

11. Short Course - Software Engineering with Object Technology