PRISM

- framework for developing composite applications

*allows large or complex apps to be broken down into smaller,more
manageable pieces (modules)
- specific to wpf, silverlight, and windows phone 7 platforms
- relies heavily on design patterns to help promote loose coupling and
separation of concerns
*design patterns:
dependency injection (DI)
MVVM
Command Pattern
Inversion of Control Pattern (IoC)

USES OF PRISM
- changes made in every module won't affect the other modules (loosely
coupled)
- designed around architectural design patterns such as separation of
concerns and loose coupling

BENEFITS OF PRISM

- reuse of code
*build component on one framework like a WPF application and use the
same component on a silverlight application (cross-platforms)
- extensible
- flexible
- team development
*can be broken down into separate modules which for instance, like in
the ui part kay lahi nya lahi sad sa code;
- Quality
*improves quality which lets components to be fully tested
*allows separate teams to work on different pieces simultaneously