how could remove coupling between subsystems? RRS feed

  • Question

  • in our company we have a framework application that contain basic information and configuration data .other project of company work along this framework and use its data.for example access data,user information,menus or toolbar configurations,user Customisation,etc.

    our problem is when something change in framework project for example a "Stored Procedure" that return access information for a user,all the "subsystem applications" that use framework have to change.or if I don't want to change the SP and write a knew one,my framework will become large and I couldn't manage SP and finally bugs.what is your idea?

    how could remove this type of dependency between "subsystem applications" and framework? or how to manage them witch dont need to change all of "subsystem applications" for a change in framework? thanks.


    Monday, October 29, 2012 5:55 AM

All replies

  • I think you're talking about Coupling rather than Cohesion? It's a big topic and should start with your design to help lower coupling. You could look at tools such as ORMs that help with the specific issues there but really you want to take a serious look at the design.


    For me I like to go the SOA route but I think that will just confuse things but if you have a change look for Domain Driven Design, Greg Young, Udi Dahan, etc.


    • Proposed as answer by Amac01 Monday, October 29, 2012 6:52 PM
    Monday, October 29, 2012 11:24 AM