Java Tutorial - Java Script :
Needs and Features Analysis
Before we examine the current field of application frameworks, you should ask yourself this question: What features would I like to have in an application development framework?
If you prefer, as we do, to use a framework that has already been developed, you probably want the following things:
· The framework should be mature and stable.
· The framework should have a large installed base of existing users to draw upon in order to staff our development needs.
· From a managerial and developers standpoint, we would like for the framework to be easy to grasp for new developers making the transition from other development groups. Easy to grasp translates into a reduced learning curve and keeping management happy by reducing startup costs.
· Good documentation and readily available example applications are a must.
· Preferably, the framework we use should be supported or maintaine by the technical mainstream.
· A record of changes in technical standards or direction for the framework should be maintained or updated by third parties and contributors in a timely fashion.
· The framework should be feature-rich, leaving our developers free to work on developing solutions for business requirements rather than spending time working on tool development.
· Although the framework should be feature rich, we do not want it to lock us in to core libraries. For example, we may have a corporate standard for logging tools. We do not want a logging tool forced upon us by a Web-application framework.
So, now that we know what we have to choose from and we know what we are interested in, let’s select the framework that is right for us.
