Database Dev Idea

Reasoning: Much of the simple work can be done by Gii We don't want to start the complex work until Gii has generated the simple stuff Gii works best when creating, not so well when modifying Therefore we should try to get the database tables stable before we start developing complex behaviour

Suggestion Iterative database development a. Database team develops a database b. Both 'View' teams try running the proposed DB through Gii automated procedures, poke around to see what they think needs changing c. They feedback to the database team d. If all teams are content, continue, otherwise goto a) When done, we should have a pretty good database (and a mostly functional site..?) (in the time while idle, database team makes their own improvements and view teams do planning to work out if they need any further features)