ITEC601 Enterprise Systems Integration

Customer Database

Integration technique

The integration of the data would be done for the Housing Office and Centrelink so that the data of the customers and the properties owned by them can be linked properly so that efficient queries and results can be fetched from the system. In addition to this, the integration would enable them to provide a uniform response for the multiple queries which have been sent to the system. Major emphasis has to be put on the program-centric data system that would be developed for the organization. This would help the policy makers in simplifying the queries that are to be made in the system do that their purpose is served efficiently. An application based system is to be used for the development to the system which would help them in obtaining. Hence a Need based Data Integration is to be adopted by the organization, which would benefit the organization to a great extent and this would help them in achieving a proper integration.

Tiered EAI system

Queries decomposition and replies re-composition

For the explanation of the query getting decomposed and the replies to the query getting decomposed and the replies to be re-composed for the staffs. The case of an applicant wanting to check the eligibility of her housing subsidy. The applicant wants to check the type of housing support that they can apply for and desired area for which the rents are available. The integrated system would provide the applicant the option to input their queries and the system would process the query. For example, the query provided below is considered for discussion:

SELECT eligibility FROM Property

INNER JOIN Housing_Policies ON Property.PropertyID = Housing_policies.PropertyID

INNER JOIN Owner ON Owner.OwnerID = Housing_Polcies.OwnerID

WHERE eligibility = “elegible”;

For the retrieval of the data is done by sub dividing the query into the projection into two groups. The data is selected from the projection of the two tables Housing_Policies and Property and also the projection of Owner and Housing_Policies. In addition to this, the data from the projections are to be joined using the two projections and the data are fetched and re-complied using the Join operations. The join operation would be providing a large set of data for the query hence a selection is to be done for the data which is eligible for the applicant. The complete organized data is then displayed in front of the query maker very efficiently.

Assumptions

For the system some assumptions have been made in development of the schemas. Here it has been assumed that the owners and the customers are different entities. However, for the example that has been stated in this, report that the applicant can be considered and assumed both as an owner and a customer. In addition, to this the owners and the customers can be included in the applicant category. In addition to this, it has been assumed that there has been an eligibility field.

Bibliography

Bi, Z., Da Xu, L. and Wang, C., 2014. Internet of things for enterprise systems of modern manufacturing. IEEE Transactions on industrial informatics, 10(2), pp.1537-1546.

Colombi, J.M., Kretser, M.P., Ogden, J. and Hartman, P., 2016. Enterprise Systems Integration using Collapsing Design Structure Matrices. CrossTalk, p.33.

He, W. and Da Xu, L., 2014. Integration of distributed enterprise applications: A survey. IEEE Transactions on Industrial Informatics, 10(1), pp.35-42.

Javidroozi, V., Shah, H., Amini, A. and Cole, A., 2014. Smart city as an integrated enterprise: a business process centric framework addressing challenges in systems integration. In Proceedings of 3rd International Conference on Smart Systems, Devices and Technologies, Paris (pp. 55-59)