Path: news.easynews.com!core-easynews!newsfeed1.easynews.com!easynews.com!easynews!cyclone1.gnilink.net!spamkiller2.gnilink.net!gnilink.net!nwrdny03.gnilink.net.POSTED!32f31ba7!not-for-mail
From: "Alan" <not.me@uhuh.rcn.com>
Newsgroups: comp.databases.theory
References: <40c30358$0$568$e4fe514c@news.xs4all.nl> <E_Dwc.8882$9g6.4288@nwrdny03.gnilink.net> <40c32cad$0$33919$e4fe514c@news.xs4all.nl> <c9vhg4$bsg$1@news.netins.net> <N1Iwc.11118$QT3.4141@nwrdny01.gnilink.net> <c9vijk$6gc$1@news.netins.net>
Subject: Re: cdt
Lines: 57
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <5qIwc.10392$9g6.6043@nwrdny03.gnilink.net>
Date: Sun, 06 Jun 2004 17:23:13 GMT
NNTP-Posting-Host: 141.158.4.151
X-Complaints-To: abuse@verizon.net
X-Trace: nwrdny03.gnilink.net 1086542593 141.158.4.151 (Sun, 06 Jun 2004 13:23:13 EDT)
NNTP-Posting-Date: Sun, 06 Jun 2004 13:23:13 EDT
Xref: core-easynews comp.databases.theory:35740
X-Received-Date: Sun, 06 Jun 2004 10:22:32 MST (news.easynews.com)


"Dawn M. Wolthuis" <dwolt@tincat-group.com> wrote in message
news:c9vijk$6gc$1@news.netins.net...
> "Alan" <not.me@uhuh.rcn.com> wrote in message
> news:N1Iwc.11118$QT3.4141@nwrdny01.gnilink.net...
> >
> > "Dawn M. Wolthuis" <dwolt@tincat-group.com> wrote in message
> > news:c9vhg4$bsg$1@news.netins.net...
> > > "mAsterdam" <mAsterdam@vrijdag.org> wrote in message
> > > news:40c32cad$0$33919$e4fe514c@news.xs4all.nl...
> > > > Here are some proposed changes to the glossary from recent
> > > > discussions.
> > > >
> > > > Please take only one or two items at a time for easy
> > > > harvesting :-)
> > > <snip>
> > > ADDITIONS (comments welcome)
> > >
> > > > [change management]
> > > > The organization of data within a database can and will
> > > > change with circumstances. A DBMS should provide
> > > > facilities for changing the underlying structure
> > > > without affecting what is already stored.
> > > > For example, you can add a column to a table without losing
> > > > what is already there.
> > >
> > > I'll start with this one.  There are several similar terms:
> > maintainability,
> > > agility, flexibility, adaptive that are all more obvious choices for
> > talking
> > > about the data organization with repect to changes.  I have always
used
> > the
> > > term "Change Management" to be a process employed by people.  Is this
> > really
> > > an industry-accepted use of the phrase?  --dawn
> > >
> > >
> >
> > I would say this it is an industry-accepted phrase. There are "change
> > management" tools, for example. We have a "change management" process at
> > work (not that anyone actually pays any attention to it, but I
digress...)
>
> Yes, there are change management tools and change management processes,
but
> this definition suggests that the organization of the data is called
"change
> management".  --dawn
>
>

I see what you mean. It is really because the title of the definition is
"change management". It should be something like, "change management needs
in an RDBMS" or such.