This morning at work we discussed and sketched a class diagram and an entity diagram on the whiteboard. With hibernate we tend to think just on the class diagram, but some of us still need to think in tables.
After we started implementing it, we remembered that the information would have to be remoted across to the client. We would also need to create the admin interface to manage this and some db script to provision default values.
We used the eraser on the whiteboard and decided that we would implement those collections as hard coded enumerations and let our code generator handle the conversion from Java to ActionScript.
We will only have one early adopter client for the next few months and there were no real requirements to make this easily configurable yet.
A comment from a colleague of mine:
- In uni I would never have imagined that I would have a nice class diagram and entity diagram defined and that then I would want to dumb it down to an hard coded enumeration!
Hard coded values are not bad: hard coded unorganised values are bad.
Also if we had used word or visio to create the diagrams we would have felt that we needed to implement it the way it was first drawn. Whiteboards rule!
BTW all the logic and most of the complex UI has been successfully pair programmed today based on the specs that we had discussed yesterday with the client. Agile methodologies rule!