Annals of Computer Science and Information Systems, Volume 11

DOI: http://dx.doi.org/10.15439/2017F279

Citation: Proceedings of the 2017 Federated Conference on Computer Science and Information Systems, M. Ganzha, L. Maciaszek, M. Paprzycki (eds). ACSIS, Vol. 11, pages 999–1003 (2017)

Full text

Abstract. The research discusses the issue how to describe data quality and what should be taken into account when developing an universal data quality management solution. The proposed approach is to create quality specifications for each kind of data objects and to make them executable by using means of domain specific language (DSL). Therefore, a data quality specification of any information system can be treated as a combination of all specific data object quality specifications. The specification can be executed step-by-step according to business process descriptions, ensuring the gradual accumulation of data in the database and data quality checking according to the specific use case. The described approach can be applied: (1) to check the completeness, accuracy and consistency of accumulated data; (2) to support data migration in cases when software architecture and/or data models are changed; (3) to gather data from different data sources and to transfer them to data warehouse.

References

1. Veregin H. Data quality parameters. In P A Longley, M F Goodchild, D J Maguire, and D W Rhind (Eds.) New Developments in Geographical Information Systems: Principles, Techniques, Management and Applications, John Wiley & Sons, Inc. (2005), pp. 177-189
2. ISO 9001:2015. Quality management principles https://www.iso.org/standard/62085.html
3. Olson J.E. Data Quality. The Accuracy dimension. Morgan Kaufmann Publishers (2003), p. 294
4. Juran J.M., Gryna F.M. Juran’s quality control handbook, 4 th ed. New York: McGraw-Hill (1988)
5. Redman T.C. Data Quality. The Field Guide, Digital Press (2001), p. 74
6. Wang R.Y., Strong D.M. Beyond Accuracy: What Data Quality Means to Data Consumers, Jurnal of Management Information Systems, Springer, Vol.12., No.4 (1996), pp. 5-34.
7. OCL 2.0. Object Constraint LanguageTM, Version 2.0. Release date: May 2006. http://www.omg.org/spec/OCL/2.0/
8. http://www.omg.org/spec/OCL/2.4
9. https//www.codeproject.com/Articles/155829/SQL-Server-Integration-Services-SSIS-Part-Basics
10. Features Supported by the Editions of SQL Server 2014. msdn.microsoft.com. Microsoft Developer Network..
11. Sarjen, Microsoft Practices. What is SSIS? Its advantages and disadvantages. http://www.sarjen.com/ssis-advantages-disadvantages/
12. http://www.varam.gov.lv/eng/darbibas_veidi/e_gov/?doc=13052
13. https://www.ria.ee/en/administration-system-of-the-state-information-system.html
14. https://ivpk.lrv.lt/en/activities/state-registers-and-information-systems
15. J.Bicevskis, Z.Bicevska, Business Process Models and Information System Usability, Procedia Computer Science 77 (2015), 72 – 79.
16. J.Ceriņa - Bērziņa, J.Bičevskis, Ģ.Karnītis “Information systems development based on visual Domain Specific Language BiLingva”, In: 4th IFIP TC2 Central and East European Conference on Software Engineering Techniques (CEE-SET 2009), Krakow, Poland (2009)
17. Bicevska, Z, Bicevskis, J, Karnitis, G. Models of event driven systems. Communications in Computer and Information Science Volume 615, 2016, Pages 83-98