The Business Case for using CSLA

Question

I've been using CSLA in anger for some time on a long standing project. However I would like to use it on a new project and need to develop a sound business case in order to get buy-in from senior management.

Can anyone offer suggestions for this? So far I have:

1. It's quite widely adopted so it's easier to find experienced developers
2. There is good documentation out there in the form of Rocky's book plus community resources which means it's quicker (read cheaper) to get an answer when you have a problem.

Any other suggestions would be great.

Answer 1

• It has a story and examples for usage with a wide variety of client platforms. Thus you can say "we're going to do our first client as WinForms, but if we decide to do a Silverlight one, there's guidance, tools and libraries for it"
• It doesnt look like its going to die any time soon.

Answer 2

What are the alternatives? A different framework or no framework.

The case for frameworks in general is reasonably easily made - development and maintenance efficiencies.

This specific framework: maturity, breadth of adoption, availability of skills etc.