[Project_owners] How do you design your projects?
Biju G C
bijumaillist at yahoo.com
Tue Nov 4 22:48:13 EST 2003
Unlike vbrowse most projects at mozdev are amateur in nature.
Even my http://quickmanager.mozdev.org/ started by
by combining http://quicktools.mozdev.org/ with
Still it have all the steps of software engineering
* gather requirements,
* plan their feature set,
* plan their UI or API or schema design,
* usability studies
But may not be a systematic way.
1. It start with "usability studies"
Many times I get Idea from mozillazine
2. "gather requirements" its starts in step 1
and its a ongoing process.
3. "plan their UI" from step 1 & 2
4. "plan their API or schema design"
did it before coding and is a ongoing process.
5. standards, which I define, then violate, fix,
redefine, again violate
"if you do these things collaboratively"
the biggest collaboration at mozdev I saw is on
database at mozdev.org maillist
you can join it and see how they do
database at mozdev.org is driving
PS: Word "amateur" orginated from Latin "amator" meaning lover.
ie, one who engages in a pursuit, study, science, or sport
because he loves it rather than the money it generates
--- David Pautler <vbrowse at yahoo.com> wrote:
> I'm the owner of the vbrowse project, and I'm
> interested in how other project owners gather
> requirements, plan their feature set, plan their UI or
> API or schema design, and do usability studies.
> I'm especially interested if you do these things
> collaboratively, because I'd like to design a tool to
> support that kind of use.
> If you collaborate on UML diagrams or have a shared
> coding journal, I'd like to hear about what tools you
> currently use to support those, too.
> Please write to me directly at vbrowse at yahoo.com
Want to chat instantly with your online friends? Get the FREE Yahoo!
More information about the Project_owners