What are your top 5 things to consider when building a framework?

Help me out with an experiment…

I’m finishing up the slides and content for my TechEd talk, and I want to do a little research based on the community. The subject of my talk is “Architecting your own enterprise framework”, and I’m curious to know what you consider when you’re doing this, and what you’d like to hear someone talk about. This is going to be used in the structure of my talk to make a point about how frameworks are built, so your answers are very important to me.

Please drop me a note at bbutton@agilestl.com with your answers!

I appreciate any help I get from this, and I hope to see many of you in Boston!

— bab

 

10 thoughts to “What are your top 5 things to consider when building a framework?”

  1. While putting these thoughts, I am assuming that this framework would be used by different application developement groups to develop and deploy applications.

    The top 5 things while building a enterprise application framework would be:

    1. Easy of Use (for the API)

    2. Extensibility

    3. Thorough Logging and Exception Handling

    4. Configuration capabilities

    5. Support for different types of applications.

    Once a version of such a framework is in production, then backward compatibility would also be a very important aspects.

    Regards

    Sameer

  2. Dont design a framework; harvest it from stuff that works, runs, and is considered good. If you dont have that stuff then guide the first few projects in what you think is the right direction and then harvest the successes into something that future projects can build upon.

  3. I agree to the fact that the first cut should basically make use of what is available and working, but selling it to others to write applications on top would require it to be rich in the kind of features it has to offer.

  4. I think that a framework should be based on simple rules.

    – Simple to use

    – Simple to explain

    – Simple to extend

    – Simple to deploy

    – Simple to evolve/migrate

    I think that Einstein was not wrong when said "Everything should be made as simple as possible, but not simpler".

  5. In addition to most of the things above, it’s got to be easy to use for the developers and it has to be more valuable than doing it thier way. If it’s not easy or better, they won’t use it.

  6. TechEd is still 2 weeks or more away! The slides are finished, but the presentation is still being crafted.

    I’m actually not sure if I’m allowed to post the slides or not 🙁 If I can, I will.

    bab

  7. In addition to most of the things above, it’s got to be easy to use for the developers and it has to be more valuable than doing it thier way. If it’s not easy or better, they won’t use it.

Leave a Reply to Dru Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.