StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POModular Software Design
text
Body
copied!<p>I am trying to implement modular design in an asp.net project dividing the application into different modules like HR, Inventory Management System etc. Since I am trying to keep different modules independent of each other, I separated these modules in such a way that each module is a separate Visual studio solution having UI, BLL, DAL and even a separate database schema.</p> <p>Up till now I thought this as a common practice for developing Management systems and ERPs but I am searching the web for last three days but hardly found any help full stuff regarding developing modular applications. Most of what I found is mere theory explaining the concepts of cohesion and coupling but not real world scenarios. So I wonder</p> <ol> <li>Is it the right approach of separating modules?</li> <li>How the real world modular applications are developed?</li> <li>How should the different modules communicate with each other yet they stay independent of each other.</li> <li>I think there should be a core application which makes use of these modules, how should the core application communicate with these modules? </li> <li>There is some data, entities , objects which are common to each module, should I put them in the core modules in order for other modules to use them (I think this will make the modules coupled to core) or should every modules maintain its own copy of data + define those object, (which I think voilates DRY)</li> </ol> <p>Any thoughts, links are warmly welcome.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload