Iterations and Iterations of reviews ..finally nice set of documentation came out!..
However I read this article today (sent to me by one of my colleagues ) it discuss why you should write a framework and why not.. Its quite interesting.. You can read the article here..
Why you should write frameworks
Why you shouldn’t write frameworkshttp://jeffreypalermo.com/blog/i-ll-get-to-your-application-in-a-minute-first-we-need-to-build-the-framework/
My personal opinion is that spending time and writing a framework is important,
If you are a multinational company (or a company with many IT departments who produce their own applications) and if you need every entity to develop applications on certain terms and standards So that the whole organization can have one standard by standardizing the framework to be used. It assures easy maintenance of each system as anybody who learn the framework can attend to the system and find issues fix etc. with lesser time.
Or if you are producing a product to the market and if you plan many sales of this product and if it needs many people to do the enhancements and maintenance work, its very important that you have a framework written for the project.
Further if you are a Software Development company who develop many applications concurrently also can be benefited out of a framework.
But as far as this second article is concerned I totally agree that you need not to write a framework for a specific application to be delivered to a customer unless its really a deliverable of the project. I think the problem is with the project manager of this project. ( Fire the PM !! :-))) )