Re: c.d.theory glossary -- definition of "class"

From: Dawn M. Wolthuis <dwolt_at_tincat-group.com>
Date: Thu, 24 Jun 2004 22:13:42 -0500
Message-ID: <cbg599$3n$1_at_news.netins.net>


"Mike Preece" <michael_at_preece.net> wrote in message news:1b0b566c.0406231701.48e822ad_at_posting.google.com...
> "Dawn M. Wolthuis" <dwolt_at_tincat-group.com> wrote in message
news:<cba23f$vsv$1_at_news.netins.net>...
> > Here is a definition I just read in
> > Systems Analysis & Design: An Object-Oriented Approach with UML by
Dennis,
> > Wixom, and Tegarden
> >
> > "A class is the template we use to define objects."
> >
> > This leaves the meatier definition to "objects" but at least it states
more
> > clearly what a class is.
> >
> > Additionally, what are the biggest issues with identifying a class as a
type
> > specification? Putting it together, I'd say:
> >
> > [Class]
> > Metadata that provides a template for software objects.
> > Object Type specification
> >
> > Then an objection might be -- "is it a template or a specification" and
I
> > think those are close enough that it is both. --dawn
>
> How closely does a dictionary item resemble a class? What is missing
> from a dictionary item that would be required in order for it to be
> called a class?

It fits with my def of class. In fact, I have written a Java class that exactly aligns with an item in an MV dictionary. Cheers --dawn Received on Fri Jun 25 2004 - 05:13:42 CEST

Original text of this message