From: jeremy gilbert (j.gilbert_at_shaw.ca)
Date: 2002-01-26 00:13:30
Hello all,
I'm another newbie here; I've been on the list for while trying to get a
feel for what's going on.
I will not be of any use for hardware design, but would love to help with
the software planning and design. I agree with what seems to be a general
consensus here, that we need to clarify an intial project statement for the
software team..... and I think John's question is the most important place
to start..
John Morrison wrote:
>A lot of discussion Has gone on about the insides of the software and some
>of the outsides.
>I thought it might be a good idea to step back and think about what each of
>us want the software to do.
>
>The QUESTION......
>
>If we had unlimited time and resources what would you want the software to
>do/have?
>(Short answers please)
>
> Multiple Interface capable
> 2 channel display
> Multi Channel display
> Platform independent (Windows/Linux/???)
> Easy to add modules to software
>
>
>When we get all the answers in I'll correlate and put up as a poll.
>We can then priorities them and get what "the group" wants done in the order
>we want. :-)
>
>Anyone have a better idea?
I would suggest, because it's what I was taught and what I'm familiar with,
that we use UML (or something like it) to guide the design of the
software. If we accept that, at least for starters (again, unless anyone
has a better idea), then the first thing we need to do is answer something
like the question John put forward, but from three different perspectives:
scope, objectives, and deliverables.
1. Scope: how extensive should the initial release of openEEG be? should
we initially aim for basically just a monitor & core libraries, or
something more interactive? how ambitious should we be with version 1.0?
2. Objectives: what are the non-material goals of this project? what will
it do for individuals? for society? in what way will it allow users to
grow, learn, develop? (this is in some ways the most important one)
3. Deliverables: what are the tangible expectations of the project? (eg.
the interface will look like this; it should be coded in Java, in C++ for
linux, windows, whatever...)
If we could get as much feedback as possible for these three little
questions, that would give a much firmer base from which to start planning
and developing the software, and a lot of the software discussion could
probably be moved off this list. Also, be sure to answer the questions
independently, ie. don't limit your answers to the second and third
question by your answer to the first.
Or perhaps John's approach is better, just having a sort of wish list and
then trying to prioritize. I just think that might become harder to
coordinate in the long run.
Please give us your (neuro) feedback. : )
-jeremy.
>John Morrison MailTo:jmorrison_at_ahc.net.au
>ICQ - 367473
>
>
>
>
>To unsubscribe from this group, send an email to:
>buildcheapeeg-unsubscribe_at_egroups.com
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
This archive was generated by hypermail 2.1.4 : 2002-07-27 12:28:37 BST