NEW ARCHITECTURAL DESIGN OF AN ARCHAEOLOGICAL MANAGEMENT SYSTEM
NEW ARCHITECTURAL DESIGN OF AN ARCHAEOLOGICAL MANAGEMENT SYSTEM

Summary/Abstract: The purpose of this paper is to present the process of designing and developing a dynamic interface for an archaeological management system, with advanced possibilities of viewing, adding and modifying standardized sheets, created at a certain place, based on the coordinates extracted from the map. The main goal of the paper is to present the conception and implementing of the archeological management platform, along with the functionalities behind the composing elements and the classes which help in the process of data manipulation and database connections. This developing process also involved the integration of three modules. The developing process of these modules was based on the Three Layer Architecture and every one of the modules was designed separately. The database is the foundation of this project, because without it the main functionalities of this website wouldn't work. It was developed using the SQL scripting language with the help of the Microsoft SQL Server 2012 development kit. The initial design of its components was based on a standardized model of an analytical sheet of inventory, provided by the Architecture, Restoration and Archaeology Association. This analytical sheet is a standardized version which contains certain characteristic information associated with the archaeological site. The second module which help to the creation of this project is represented by the map, developed with the help of the Google Maps API. The technology provided by Google is highly complex, it offers us a lot of customizable functionalities, extensive documentation and the process of adding new functionalities is possible with the help of JavaScript in a relative simple way. The integration of the map within the interface it's possible with the help of a simple link-based reference, in order to get the needed data from the Google servers. Within this link, we have to summon a key, dynamically created in connection with our specified account. This is called an API key and its usage is that of counting the information traffic. If a certain traffic limit is reached or surpassed it is supposed that the application is not used in personal means and thus certain payroll may apply. In order to use the existing functions or overwrite them, we have to include another link referral to a JavaScript file, where some of the functionalities were already added by a teammate. The original contribution of the papers consists in its interdisciplinary nature, given the scope of platform developed, able to provide deepen related information, closely related to the archeology, history and cultural heritage study. The application is in its prototype version and has great potential as a major exploit in the future.

• Details
• Contents