Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!tandem!netcomsv!jls
From: jls@netcom.COM (Jim Showalter)
Newsgroups: comp.object
Subject: Re: Objects and Interactions: Separate Definitions
Message-ID: <1991Jun4.015958.6295@netcom.COM>
Date: 4 Jun 91 01:59:58 GMT
References: <3999@motcsd.csd.mot.com> <1991May21.064913.16149@netcom.COM> <1991May22.012821.12048@tkou02.enet.dec.com> <1991May22.183044.5634@Think.COM> <19807@crdgw1.crd.ge.com> <7051@stpstn.UUCP>
Distribution: comp
Organization: Netcom - Online Communication Services  UNIX System {408 241-9760 guest}
Lines: 14

>What should we call this higher-level construction? Why not 
>a card-level object, to suggest a new kind of object at a higher level
>of concretion.

I refer to the architectural-level chunks of a system as "subsystems",
to distinguish them from the smaller objects of which they are constructed.
(I think Grady calls these "class collections" in his newest book, but
this is too restrictive for my taste: subsystems are often more than mere
collections of related classes.)
-- 
**************** JIM SHOWALTER, jls@netcom.com, (408) 243-0630 ****************
*Proven solutions to software problems. Consulting and training on all aspects*
*of software development. Management/process/methodology. Architecture/design/*
*reuse. Quality/productivity. Risk reduction. EFFECTIVE OO usage. Ada/C++.    *