Cyaneus

AWA is software development process for atomic web applications.

I intend to split it in 3 (three) main parts:

1. Design Instructions: rules for control as files as functions, classes and configuration variables. It's important because an atomic web application needs a special architecture.
2. Good practices set: good practices includes required, recommended and suggested. It's like eXtreme Programming. This part can be used too for development of non-atomic web applications.
3. Creation process: it's a software development process (steps) with one audacious proposal: to avoid graphic diagrams, prefering ASCII. Trying to capture the community development spirit, ASCII is a useful and needed decision: e-mails should be sent in ASCII, ASCII control file can easily be under a CVS or wiki. This will have cyclic steps like XP, but using todo list and feature list for control.

Lets go!