> as a single item rather than decomposing it into pieces yet. We should
> work forward
> from that point. I'm sure this sounds pedantic, but it works in Research
> and
> development based companies that develop similarly multi-disciplinary
> products.
I agree with this statement. I think that we should first figure out
what exactly what we want this thing to do (design specification) and
then we can deal with the breaking down of the project into different
chunks.
>
> Firstly we need to determine what we expect to achieve as a finished
> product
> and then decompose each part. The danger I see with this mailing list is
Yes, excactly.
> that it
> could become anarchic, with everyone talking about any element of the
> project
> without and formal agenda.
Right, we should definately see if we can try to set up some sort of
timeline and adgenda and try to make dealines as to when we will make
decisions on certian components of the project.
> > If we take it a stage
at a time, discussing each element to a > satisfactory
> conclusion (reviewing later as other elements are implemented) we should
> be
> able to achieve the goal.
Right. I'm sure none of us on the list want to discuss this thing
endlessly. I hope that everyone wants results, or at least the majority
do. I know there are some on the list that just want to be spectators,
that's fine.
>
> I'm willing to donate web space for the specifications, drawings, FAQ
> etc as
> we progress.
Thank you for your offer.
Anyone out there want to start telling us what they are looking for in a
finished project?
Ray