Frameworks and Libraries


Here are my two cents on frameworks and libraries :


If you are software architect or developer for a medium or large enterprise or Business application I suggest that you consider creating an application framework or class library even if its only thin layer that can be leveraged for building the next generation of the application since change control becomes rigid once an application is deployed and having a suitable control point via these frameworks and libraries gives architects and developers the flexibility to mold the application as per ones needs.

Here are some potential areas for creating a framework of reusable business objects :


a) Application settings. 
Storing and retrieving settings local or in a distributed environment. Can be Registry or config or database. This will allow you to switch the data store to anything you want in the future without causing a major rewrite or redesign.


b) UI class framework for standardization of look and feel.
In case of web app this can be a Page base class for your ASP.NET pages or if you are a old style thick client it can be standard UI controls, Framewindow clases, dialog classes and special purpose menus and controls. Classes here can also provide base classes for all your controls, error windows, icons, cursors, system tray handlers and events controls.


d) Integration or InterOp classes for interfacing with legacy classes or third party code


e) Service layer frameworks for defining application tiers and service boundaries. This may useful for defining process boundaries.
f) Help system frameworks.


g) Data Access layer. Wrappers to wrap your ADO.NET calls, or OLE-DB


h) Error handling and Exception handling. 
Define standards and methodology of how error codes are defined and who is responsible for processing them and how they are displayed.


i) Cookie cutter classes for code-generation or repetitive code.


j) Abstract classes for plugin or adapter architecture. 
- Adapter classes to support multiple  vendor interfaces.
- Mulitplexing, multicasting and pubsub scenarios.  One source and multiple consumers scenarios.
 eg mulitcasting Streaming, File downloading,broadcast, event propagation, announcements, alerts etc 
- Multi protocols support scenarios- Say if you have one protocol in first release but want to support multiple protocols in future releases you have to provide a template class that each of them can be derived from.