On 10/5/05, Brian Gorby <[EMAIL PROTECTED]> wrote: > Where is a good place to begin here? Should I start at the View and work > my way down, or first program the model and ORM service? Are there any > design tools that prove overly helpful in determining all of this?
Most agile development books (XP etc) would advice you to peek a small set of functionality and implement a vertical prototype. A vertical prototype is a prototype which represents all layers of your application (view, presentation logic, business logic, persistence). So take 2-5 use cases and programm them down, maybe even with different technologies (ibatis vs hibernate, struts vs. jsf, and so on, depending on how much time you have). Then you can decide how to work. To add a personal note, the above approach works perfectly for me, since i don't like the top-down or bottom-up approaches, but create a skeleton, test it, and then add muscles :-) regards Leon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
