New Web Client Software Factory Modularity Bundle from patterns & practices
What is the concept (from CodePlex)?
Modularity is the separation of an application in independent and collaborative modules. You use modules to encapsulate a set of concerns of your application and independently develop and deploy them to your applications. These modules are developed and maintained by multiple teams.
A Web client application that uses the Composite pattern generally involves a shell module, which provides the overall user interface structure. A shell module typically registers user interface components shared by other modules, contains global pages and one or more ASP.NET master pages that module developers can use to create a consistent layout for pages.
Modules contain functionally discrete pieces, but they integrate with the user interface and communicate with each other. The shell module provides access to services required by other modules throughout the application. This means that the modules can use these capabilities instead of having to implement them themselves.
This approach provides a number of advantages in terms of a separation of roles between the developers of the modules and the solution designer/builder. Module developers are typically focused on implementing the business logic required to
provide specific business focused functionality (for example, providing access to the inventory, CRM, ERP, and HR systems). The solution designers are able to define a solution to a business problem at a level that is higher and more broadly focused (for example, providing a call center solution, a bank teller solution, or a document collaboration solution).
Get it here.
Modularity is the separation of an application in independent and collaborative modules. You use modules to encapsulate a set of concerns of your application and independently develop and deploy them to your applications. These modules are developed and maintained by multiple teams.
A Web client application that uses the Composite pattern generally involves a shell module, which provides the overall user interface structure. A shell module typically registers user interface components shared by other modules, contains global pages and one or more ASP.NET master pages that module developers can use to create a consistent layout for pages.
Modules contain functionally discrete pieces, but they integrate with the user interface and communicate with each other. The shell module provides access to services required by other modules throughout the application. This means that the modules can use these capabilities instead of having to implement them themselves.
This approach provides a number of advantages in terms of a separation of roles between the developers of the modules and the solution designer/builder. Module developers are typically focused on implementing the business logic required to
provide specific business focused functionality (for example, providing access to the inventory, CRM, ERP, and HR systems). The solution designers are able to define a solution to a business problem at a level that is higher and more broadly focused (for example, providing a call center solution, a bank teller solution, or a document collaboration solution).
Get it here.
posted by tadanderson at 1:55 PM
0 Comments:
Post a Comment
<< Home