🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: ab.software.developers
Article #630

OOPSLA Workshop - Design for Maintenance

#630
From: Pete McBreen, McBreen.Consulting
Date: Wed, 15 Sep 1999 00:00
54 lines
2728 bytes
The deadline for submitting position papers has been extended to 30th
September to allow for wider participation in the workshop, hope you
can make it to OOPSLA 99 in Denver.

Pete, Jens and Russell

Call for Participation.

Workshop #8, "Design for Maintenance" is an exploration of what it
takes
to make a system maintainable. What can we do to increase the
economic
life of a system without making the development of the system
impossible?

The aim of this workshop is to capture the practical and pragmatic
techniques that have proved to work in delivering maintainable
systems.
To participate in this workshop visit
http://www.cadvision.com/roshi/DesignForMaintenance.html

The organizers of this workshop are Pete McBreen, Jens Coldewey and
Russel Bryant. See
http://www.acm.org/sigs/sigplan/oopsla/oopsla99/2_ap/workshops/ws8.ht
ml
for the initial workshop announcement.

"We often claim that Object Technology makes systems more
maintainable,
but what does that really mean? What is it about objects that makes
it
easy to maintain a system? Identifying maintenance as a design
priority
is especially important with the moves to create a "standard"
development process for object technology, since all too often the
developers in the field forget to report back on what actually works.
As
an example think about the number of project teams who are always
having
to apologize for not having enough documentation. Who gets to define
enough? Is a track record of 4 years of increasing sales an indicator
that the team has enough documentation, or a sign that they are soon
going to fail unless they stop and document what they have got? The
concept behind design for maintenance has analogues in other
engineering
fields such as "Design for Manufacture". The workshop will seek to
identify other priorities for OO development such as "design for
testability" and the effects that these priorities would have on the
economics of the delivered system. "

-----
Pete McBreen, McBreen.Consulting , Calgary, AB
email: petemcbreen@acm.org    http://www.cadvision.com/roshi
Using Creativity and Objects for Process Improvement
Technical Details
Message-ID: <37e0754b@news.cadvision.com>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10f2ee,662035e938939e3d,start
X-Google-Attributes: gid10f2ee,public
From: "Pete McBreen, McBreen.Consulting" <mcbreenp@cadvision.com>
Subject: OOPSLA Workshop - Design for Maintenance
Date: 1999/09/15
Message-ID: <37e0754b@news.cadvision.com>
X-Deja-AN: 525723090
X-Original-NNTP-Posting-Host: 204.50.1.43
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Trace: 15 Sep 1999 22:42:51 -0700, 209.91.71.220
Organization: McBreen.Consulting
Newsgroups: ab.software.developers