Single modules are easy and less prone to errors. Integration of related modules may be a much breath taking job. Every thing works fine when separate but on integration there are hundreds of things to take care of.
What is the basis of integration of integration?
: you need to find the exact star point for both the modules you are going to integrate so that some ids should be unique for entry point of one system to another.
why to integrate?
: single solution is emerging demand among customers basically for office automation systems. So that every thing is in one place and related to all other component and hence tracking process and resource becomes easier.
How much to integrate?
: extent of integration may depend on the requirement of the customer and decision of developer. But few things to be considered are
* system should not loose its dynamic nature.
* both system should be complete independently, although this could be alittle difficult to accomplish in few cases but the focus should be on making independent as much as possible.
What are Mostly demanded integrated solution?
: mostly
billing and account.
Inventort and tracking system.
MIS and website.
Production and inventort.
Attendance and payroll.
Erp are major market holders for integrated solutions around the globe.
Integration Mechanism:
There Could Be Many Integration Mechanism but I am Going to enlist few of my personally developed mechanism which are tested and are working for me and hope will hope to help others with some integrated MIS Development.
1. Using Union in View.
2. Using Bridge Table to and Integration Rule.
Using Union in View.
This is an easier mechanism but may not be useful in all cases.
In this mechanism the table structure should be similar or is made similar in view while Union.
There is not much overhead of changing reports from the data in this mechanism as the same view is used only the data it retrieves increases with the union of different tables.
useful in case of sales, purchase, journal, payment etc vouchers.
To break the Integration of this type of Integration, view needs to be changed.
May need extra effort for user level customization(To add or Integration feature by user).
When integrated using this mechanism no extra work for user i.e. if inventory vouchers are integrated to account using this method there is no need to regenerate the voucher in account module. the view automatically gets data from inventory module needed for account.
Note.: If Possible Use this method (Best for usability).
Using Bridge Table to and Integration Rule.
In this method we use bridge tables to get the equivalent data structure between tables different modules.
Then we write integration rule ie what to get from which column of what table for the voucher of account module from inventory module.
In this method different interface gets data from inventory module on the basis of integration rule using bridge tables and then user varifies the data and approves the voucher.
This case is needed where different independent bodies need to share there information to one another via application.
For example: Loan section and Account section of an organization are independent bodies then issue of loan should directly effect the account but should only using different voucher in account but what if all the data will be re posted manually by the user that will be a tidious joub in such case this kind on integration is very usefull as it will retrieve the data from other module as it is in the module it need to be integrated with and user will only have to approve the data.
What is the basis of integration of integration?
: you need to find the exact star point for both the modules you are going to integrate so that some ids should be unique for entry point of one system to another.
why to integrate?
: single solution is emerging demand among customers basically for office automation systems. So that every thing is in one place and related to all other component and hence tracking process and resource becomes easier.
How much to integrate?
: extent of integration may depend on the requirement of the customer and decision of developer. But few things to be considered are
* system should not loose its dynamic nature.
* both system should be complete independently, although this could be alittle difficult to accomplish in few cases but the focus should be on making independent as much as possible.
What are Mostly demanded integrated solution?
: mostly
billing and account.
Inventort and tracking system.
MIS and website.
Production and inventort.
Attendance and payroll.
Erp are major market holders for integrated solutions around the globe.
Integration Mechanism:
There Could Be Many Integration Mechanism but I am Going to enlist few of my personally developed mechanism which are tested and are working for me and hope will hope to help others with some integrated MIS Development.
1. Using Union in View.
2. Using Bridge Table to and Integration Rule.
Using Union in View.
This is an easier mechanism but may not be useful in all cases.
In this mechanism the table structure should be similar or is made similar in view while Union.
There is not much overhead of changing reports from the data in this mechanism as the same view is used only the data it retrieves increases with the union of different tables.
useful in case of sales, purchase, journal, payment etc vouchers.
To break the Integration of this type of Integration, view needs to be changed.
May need extra effort for user level customization(To add or Integration feature by user).
When integrated using this mechanism no extra work for user i.e. if inventory vouchers are integrated to account using this method there is no need to regenerate the voucher in account module. the view automatically gets data from inventory module needed for account.
Note.: If Possible Use this method (Best for usability).
Using Bridge Table to and Integration Rule.
In this method we use bridge tables to get the equivalent data structure between tables different modules.
Then we write integration rule ie what to get from which column of what table for the voucher of account module from inventory module.
In this method different interface gets data from inventory module on the basis of integration rule using bridge tables and then user varifies the data and approves the voucher.
This case is needed where different independent bodies need to share there information to one another via application.
For example: Loan section and Account section of an organization are independent bodies then issue of loan should directly effect the account but should only using different voucher in account but what if all the data will be re posted manually by the user that will be a tidious joub in such case this kind on integration is very usefull as it will retrieve the data from other module as it is in the module it need to be integrated with and user will only have to approve the data.