RE: Need Development Guidelines To Organize Classes into Packages

[angus.berry@elken.com]

Lee,

Scope is a factor to consider when designing Packages.

I hope this isn't too vague of a response, but if you were at Dave Thomas's
presentation to AJUG, he pointed out that you can achieve what Microsofties
would call 'Friend' scope.


> -----Original Message-----
> From: Lee Chalupa [mailto:lchalupa@seelink.org]
> Sent: Monday, November 03, 2003 10:08 PM
> To: Ajug Members
> Subject: Need Development Guidelines To Organize Classes into Packages
>
>
> Hello:
>
> I am looking for some guidelines to help me organize a new application's
> classes into packages.
>
> Is there a quantity of classes per package that tends to be
> easier to work
> with?  What number of classes per package is definitely too few?  What is
> definitely too many? Why might this be a problem?
>
> Should you consider some kind of fan-out ratio when you are
> organizing the
> package hierarchy?
>
> How would you go about evaluating the quality of a packaging
> scheme for an
> application?  What does goodness look like? For example, high cohesion
> inside packages, low coupling between packages, intuitive package
> names, a
> consistent range of quantity of classes in each package of the
> application.
>
> Does anyone have any references for these kind of development issues?
>
> Thanks
>
> Lee
>
>
>
> --
> Lee Chalupa
> Something Else Enterprises, Inc.
> lchalupa@seelink.org
> 770 381 2377
>
>