After listening to Clark Valberg at the last NY CFUG, I got all jazzed up about Interface Driven Architecture. I feel that it is definitely the way to go when it comes to successful project life cycles. Of course, right now this is all theory for me as my company's current development model is the more archaic, "develop now, show the client later" mentality.
In order to even approach management with this suggested shift in thinking, I am going to have to prove to them that this is a worthy strategy. I am using a small project called Team Nylon as my proof of concept. Team Nylon is a very small task-management system. More or less, it's a glorified To-Do list that has a sense of clients and teams. It's small, but I think it will be a useful enough application to prove that this is a valid approach to development.
The first stage of my prototyping was purely graphical. No ColdFusion or code of any sort is used during this phase. I used Adobe Fireworks to create slides of what I thought the application should look like. The following slides took me about 3 hours to create. Keep in mind - and this is really the whole point - that NO ColdFusion code has been written at this stage. The idea is that I can get the clients (my management) involved in the process sooner rather than later and with minimal wasted development effort.
These are the slides that they have signed off on for further prototyping: