1. When and Why to Use a Framework Simon Horwith CIO, AboutWeb

2. Objectives
The objective today is to describe what a framework is, and when/why they should be used
We will begin by examining how wikipedia answers these questions, then we will discuss how things work in reality

3. Topics What is a framework (wikipedia)?
Why to use a Framework (wikipedia)
Why NOT to use a Framework (wikipedia)
Who needs to pay attention?
What is a framework?
Confession
When to use a Framework
When not to use a Framework
Why to use a Framework?
Why NOT to use a Framework
Frameworks and You!

4. What is a Framework (wikipedia)?
In software development, a framework is a defined support structure in which another software project can be organized and developed
A framework may include support programs, code libraries, a scripting language, or other software to help develop and glue together the different components of a software project.

5. Why to use a Framework (wikipedia)
Frameworks are designed with the intent of facilitating software development, by allowing designers and programmers to spend more time on meeting software requirements rather than dealing with the more tedious low level details of providing a working system

6. Why NOT to use a framework (wikipedia)
There are common complaints that using frameworks adds to "code bloat", and that a preponderance of competing and complementary frameworks means that one trades time spent on rote programming and design for time spent on learning frameworks

7. Who needs to pay attention?
Executive Decision Makers
The decision to use or not to use a framework may effect all of the projects and developers in your organization
Team Leaders
Identifying how a framework will benefit your team and know how they will work within that framework
Developers
Know how to work within a framework and make yourself more marketable

8. What is a Framework? To add to the wikipedia definition:
Frameworks tend to offer centralized control to an application
Frameworks usually automate and/or obfuscate processes run on initialization and/or request

9. Frameworks and CMS’
Q: What is the difference between a Framework and a Content Management System?
A: A CMS is software designed to assist users in managing content
Versioning, authoring, uploading, workflow/approval
Fact:
A CMS usually complies with the definition of a framework, but many frameworks do not fall under the category of a content management system
Frameworks are for developers
CMS’ are for content authors/contributors

10. Confession My name is Simon, and I’ve used and even written frameworks
Despite being vocal about the problems with frameworks and being stereotyped as “Mr. Anti-Frameworks”, I also recognize their benefits
For every framework, there is a time and place when it makes sense to use

11. When to Use a Framework? Use a framework when:
the framework will assist in meeting software requirements without getting in the way
The developers on your team are all familiar with the framework or are confident they can get up to speed based on the framework documentation
The framework will make the running of a project better/easier (dividing tasks)
The framework offers some other benefit(s) that justify its use
Timeliness
Less experienced developers will build/maintain the code
Integration with other tools (wireframing, documentation, etc.)

12. When NOT to use a framework?
Do NOT use a framework when:
The learning curve will be too great
The framework is something that will or might get in the way of meeting business requirements
when using the framework isn’t the best way to achieve your results (i.e. you have a better option)
You can’t name several good reasons for using the framework

13. Why to use a framework
When used right, frameworks keep code consistent (location of files, comments, etc.)
When used right, frameworks can enforce good practices (separation of View and Model, etc.)
It can be much easier to manage the code with a team of developers
There are tools that offer value to some framework users
Centralized control can make coding or maintaining global logic easier

14. Why NOT to use a framework
A few reasons not to use a framework:
They are often not used properly thus negating benefits
Frameworks do sometimes get in your way
They can become a crutch
Sometimes the use of a framework is overkill

15. Frameworks and You!
There is nothing wrong with using a framework or learning one or more
Learn how to use them properly
Identify their strengths and weaknesses
Do not become dependant on them
If you build an app with a framework and don’t think you could build it without the framework, you should try doing so
On any project, ask yourself why you’re using a framework before you do

16. End Thank You for attending!
Feel free to send questions/comments to