One belief I have about frameworks, is its usefulness outside of the Framework context.
When one reads about software frameworks as a software builder, one cant help but feel that Frameworks are probably not efficient or cost effective.
Frameworks seem to have a distinct usage and when you look at your project, a framework may seem like overkill.
I strongly feel that most projects have a strong case for at least a small framework, and in fact, your project will have major benefits.
The benefits of this simple approach means that if implemented correctly, even if the functionality is small, it offers a wide range of usefulness.
If certain implementation conditions are met and the concepts of a Framework applied, even at this simple level, you have a reason to know and understand what and how Frameworks can benefit your next project.
One could argue, that I am only pointing out one Design Pattern, but one could also say that a Framework need not be a complex beast underneath everything and in its early atomic level, it is just 1 or more Design Patterns.
This still means that if the conditions are right, it can be called a framework.
Understanding Frameworks and how they relate to everyday projects is tremendously important for making good agile software.
Previous Topic
