Home > Archive > Software Engineering > February 2006 > literature on project organization
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
literature on project organization
|
|
| leisner@rochester.rr.com 2006-02-14, 7:01 pm |
| Are there any literature/studies on project organization/directory
structure and the
costs associated with it?
I.e. -- file sizes, directory sizes, -- why have a tree structure
rather than a flat structure...
I have a lot of "opinions" from viewing lots of projects, lots of other
people also have
their own "opinions" -- anything better than sticking a finger in the
air to test the wind?
marty
| |
| Peter Dembinski 2006-02-16, 7:58 am |
| leisner@rochester.rr.com writes:
> Are there any literature/studies on project organization/directory
> structure and the costs associated with it?
Oh, sure there are.
> I.e. -- file sizes, directory sizes, -- why have a tree structure
> rather than a flat structure...
AFAIK Sun has published some blueprints about project directory tree
structure. And you could check out maven -- they have their own way
of structurizing software artifacts too.
> I have a lot of "opinions" from viewing lots of projects, lots of
> other people also have their own "opinions" -- anything better than
> sticking a finger in the air to test the wind?
IIRC the more proper term is 'factorization'. That is: distribution
of responsibilities between objects and classes. The file structure
of the project should express the project's metamodel factorization.
--
http://www.peter.dembinski.prv.pl
|
|
|
|
|