[an error occurred while processing this directive] // preload images - you have to specify which images should be preloaded // and which Image-object on the wep-page they belong to (this is the first // argument). Change this part if you want to use different images (of course // you have to change the body part of the document as well) //main buttons preload("committee", "/images/buttons/toolbar/usa_99/image1/committee.gif", "/images/buttons/toolbar/usa_99/image2/committee.gif"); preload("exhibit", "/images/buttons/toolbar/usa_99/image1/exhibit.gif", "/images/buttons/toolbar/usa_99/image2/exhibit.gif"); preload("sponsors", "/images/buttons/toolbar/usa_99/image1/sponsors.gif", "/images/buttons/toolbar/usa_99/image2/sponsors.gif"); preload("venue", "/images/buttons/toolbar/usa_99/image1/venue.gif", "/images/buttons/toolbar/usa_99/image2/venue.gif"); preload("registration", "/images/buttons/toolbar/usa_99/image1/registration.gif", "/images/buttons/toolbar/usa_99/image2/registration.gif"); preload("tools26", "/images/buttons/toolbar/usa_99/image1/tools26.gif", "/images/buttons/toolbar/usa_99/image2/tools26.gif"); preload("contact", "/images/buttons/toolbar/usa_99/image1/contact.gif", "/images/buttons/toolbar/usa_99/image2/contact.gif"); preload("home", "/images/buttons/toolbar/usa_99/image1/home.gif", "/images/buttons/toolbar/usa_99/image2/home.gif"); preload("keynotes", "/images/buttons/toolbar/usa_99/image1/keynotes.gif", "/images/buttons/toolbar/usa_99/image2/keynotes.gif"); preload("program", "/images/buttons/toolbar/usa_99/image1/program.gif", "/images/buttons/toolbar/usa_99/image2/program.gif"); preload("intro", "/images/buttons/toolbar/usa_99/image1/intro.gif", "/images/buttons/toolbar/usa_99/image2/intro.gif"); preload("stot", "/images/buttons/toolbar/usa_99/image1/stot.gif", "/images/buttons/toolbar/usa_99/image2/stot.gif"); preload("dpaas", "/images/buttons/toolbar/usa_99/image1/dpaas.gif", "/images/buttons/toolbar/usa_99/image2/dpaas.gif"); preload("sbir", "/images/buttons/toolbar/usa_99/image1/sbir.gif", "/images/buttons/toolbar/usa_99/image2/sbir.gif"); preload("summit", "/images/buttons/toolbar/usa_99/image1/summit.gif", "/images/buttons/toolbar/usa_99/image2/summit.gif"); preload("golf", "/images/buttons/toolbar/usa_99/image1/golf.gif", "/images/buttons/toolbar/usa_99/image2/golf.gif"); preload("award", "/images/buttons/toolbar/usa_99/image1/award.gif", "/images/buttons/toolbar/usa_99/image2/award.gif"); // -->
TOOLS Conferences Home Page TOOLS USA '99
conference and program committee
keynotes
conference program
TOOLS Component and Object Technology Award
pre-conference session: intro to OT
symposium on teaching object technology
eiffel summit '99
SBIR
DPAAS
exhibit
sponsors
registration
Santa Barbara
Golf Tournament

contact us
TOOLS USA '98
  
TOOLS USA '99 - towards quality software, the way ahead

Eiffel Summit '99

Summit Chair: Roger Osmond, Amalasoft, USA
Bringing Eiffel into the Mainstream

Eiffel power

Topics, Ideas, Issues, Questions...

1. Suggested by Richard Bielak, CalFP Bank, USA:

How about arranging a discussion/panel on reorganization of NICE. I believe that NICE in its current shape is ineffective. My idea is to organize NICE along the lines of the IETF (http://www.ietf.org).

Main points:

1. Have NICE made up of two parts:
a. NICE Board which approves standards. Members are elected as today.
b. NICE Working groups that prepare standards. Membership should be completely open (just subscribe to a mailing list)

2. Standards process:

a. Working group forms.
b. WG produces an RFC (within a reasonable amount of time)
c. If possible, someone implements the code (to be open source)
d. Board approves the standard.

(i.e. "rough consensus and running code")

2. Suggested by Guido DeDene, Katholieke Universiteit Leuven, Belgium:

I can maybe contribute with my experience teaching to NON-computer-science students (which is still an overwhelming number of students exposed to software, in many cases still Pascal and Cobol!). I would like to make the case that Eiffel is indeed a good replacement for Pascal, and a better didactical choice than Java... It would also be good if at the summit we could come to some kind of "joint" WWW-site with teaching material, analogous to the shelf for software... It is my feeling that proper education is a long-term strategy for bringing Eiffel in the mainstream.

AGENDA

If you would like to actively contribute to the Eiffel Summit '99, please convey your ideas to the Chair:

Roger Osmond
Eiffel Summit '99 Chair
Amalasoft, USA
eiffel-summit@tools.com

Topics, ideas, issues, and questions that are suggested for discussion at the Eiffel Summit '99 will be added to this page.

Register online for the Eiffel Summit '99!

Back to main Eiffel Summit '99 page

Committee | Keynotes | Program | Award | Intro to OT | STOT | Golf
Exhibit | Sponsors | SBIR | DPAAS | Registration | Venue
TOOLS home | Contact TOOLS | TOOLS USA '98

Questions? Comments? Let us know!
Copyright 1994-1999 Interactive Software Engineering Inc. All rights reserved.
TOOLS is a trademark of Interactive Software Engineering
URL for this page: http://www.tools.com/tools/usa_1999/eiffel-summit99/topics.html