FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W78114055> ?p ?o ?g. }

• W78114055 abstract "This document is the result of a process of web development to create a tool that will allow to Cracow University of Technology consult, create and manage timetables. The technologies chosen for this purpose are Apache Tomcat Server, My SQL Community Server, JDBC driver, JavaServlets and JSPs for the server side. The client part counts on Javascript, jQuery, AJAX and CSS technologies to perform the dynamism.The document will justify the choice of these technologies and will explain some development tools that help in the integration and development of all this elements:specifically, NetBeans IDE and MySQL workbench have been used as helpful tools.After explaining all the elements involved in the development of the web application, the architecture and the code developed are explained through UML diagrams. Someimplementation details related to security are also deeper explained through sequence diagrams.As the source code of the application is provided, an installation manual has been developed to run the project. In addition, as the platform is intended to be a beta that will be grown, some unimplemented ideas for future development are also exposed.Finally, some annexes with important files and scripts related to the initiation of the platform are attached.This project started through an existing tool that needed to be expanded. The main purpose of the project along its development has focused on setting the roots for a whole new platform that will replace the existing one.For this goal, it has been needed to make a deep inspection on the existing web technologies: a web server and a SQL database had to be chosen. Although the alternatives were a lot, Java technology for the server was finally selected because of the big community backwards, the easiness of modelling the language through UML diagrams and the fact of being free license software. Apache Tomcat is the open source server that can use Java Servlet and JSP technology.Related to the SQL database, MySQL Community Server is the most popular open-source SQL Server, with a big community after and quite a lot of tools to manage the server. JDBC is the driver needed to put in contact Java and MySQL.Once we chose the technologies that would be part of the platform, the development process started. After a detailed explanation of the development environment installation, we used UML use case diagrams to set the main tasks of the platform; UML class diagrams served to establish the existing relations between the classes generated; the architecture of the platform was represented through UML deployment diagrams; and Enhanced entity–relationship (EER) model were used to define the tables of the database and their relationships.Apart from the previous diagrams, some implementation issues were explained to make a better understanding of the developed code - UML sequence diagrams helped to explain this.Once the whole platform was properly defined and developed, the performance of the application has been shown: it has been proved that with the current state of the code, theplatform covers the use cases that were set as the main target. Nevertheless, some requisites needed for the proper working of the platform have been specified.As the project is aimed to be grown, some ideas that could not be added to this beta have been explained in order not to be missed for future development.Finally, some annexes containing important configuration issues for the platform have been added after proper explanation, as well as an installation guide that will let a new developer get the project ready.In addition to this document some other files related to the project are provided:- Javadoc. The Javadoc containing the information of every Java class created isnecessary for a better understanding of the source code.- database_model.mwb. This file contains the model of the database for MySQL Workbench. This model allows, among other things, generate the MySQL script for the creation of the tables.- ScheduleManager.war. The WAR file that will allow loading the developed application into Tomcat Server without using NetBeans.- ScheduleManager.zip. The source code exported from NetBeans project containing all Java packages, JSPs, Javascript files and CSS files that are part of the platform.- config.properties. The configuration file to properly get the names and credentials to use the database, also explained in Annex II. Example of config.properties file.- db_init_script.sql. The SQL query to initiate the database explained in Annex III. SQL statements for MySQL initialization.RESUMEN.Este proyecto tiene como punto de partida la necesidad de evolucion de una herramienta web existente. El proposito principal del proyecto durante su desarrollo se ha centrado en establecer las bases de una completamente nueva plataforma que reemplazara a la existente.Para lograr esto, ha sido necesario realizar una profunda inspeccion en las tecnologias web existentes: un servidor web y una base de datos SQL debian ser elegidos. Aunque existen muchas alternativas, la tecnologia Java ha resultado ser elegida debido a la gran comunidad dedesarrolladores que tiene detras, ademas de la facilidad que proporciona este lenguaje a la hora de modelarlo usando diagramas UML. Tampoco hay que olvidar que es una tecnologia de uso libre de licencia. Apache Tomcat es el servidor de codigo libre que permite emplear Java Servlets y JSPs para hacer uso de la tecnologia de Java. Respecto a la base de datos SQL, el servidor mas popular de codigo libre es MySQL, y cuenta tambien con una gran comunidad detras y buenas herramientas de modelado, creacion y gestion de la bases de datos. JDBC es el driver que va apermitir comunicar las aplicaciones Java con MySQL.Tras elegir las tecnologias que formarian parte de esta nueva plataforma, el proceso de desarrollo tiene comienzo. Tras una extensa explicacion de la instalacion del entorno de desarrollo, se han usado diagramas de caso de UML para establecer cuales son los objetivos principales de la plataforma; los diagramas de clases nos permiten realizar una organizacion del codigo java desarrollado de modo que sean facilmente entendibles las relaciones entre lasdiferentes clases. La arquitectura de la plataforma queda definida a traves de diagramas de despliegue. Por ultimo, diagramas EER van a definir las relaciones entre las tablas creadas en la base de datos.Aparte de estos diagramas, algunos detalles de implementacion se van a justificar para tener una mejor comprension del codigo desarrollado. Diagramas de secuencia ayudaran en estas explicaciones.Una vez que toda la plataforma haya quedad debidamente definida y desarrollada, se va a realizar una demostracion de la misma: se demostrara como los objetivos generales han sido alcanzados con el desarrollo actual del proyecto. No obstante, algunos requisitos han sido aclarados para que la plataforma trabaje adecuadamente.Como la intencion del proyecto es crecer (no es una version final), algunas ideas que se han podido llevar acabo han quedado descritas de manera que no se pierdan.Por ultimo, algunos anexos que contienen informacion importante acerca de la plataforma se han anadido tras la correspondiente explicacion de su utilidad, asi como una guia de instalacion que va a permitir a un nuevo desarrollador tener el proyecto preparado.Junto a este documento, ficheros conteniendo el proyecto desarrollado quedan adjuntos. Estos ficheros son:- Documentacion Javadoc. Contiene la informacion de las clases Java que han sido creadas.- database_model.mwb. Este fichero contiene el modelo de la base de datos para MySQL Workbench. Esto permite, entre otras cosas, generar el script de iniciacion de la base de datos para la creacion de las tablas.- ScheduleManager.war. El fichero WAR que permite desplegar la plataforma en un servidor Apache Tomcat.- ScheduleManager.zip. El codigo fuente exportado directamente del proyecto de Netbeans. Contiene todos los paquetes de Java generados, ficheros JSPs, Javascript yCSS que forman parte de la plataforma.- config.properties. Ejemplo del fichero de configuracion que permite obtener los nombres de la base de datos- db_init_script.sql. Las consultas SQL necesarias para la creacion de la base de datos." @default.
• W78114055 created "2016-06-24" @default.
• W78114055 creator A5008032138 @default.
• W78114055 date "2014-02-17" @default.
• W78114055 modified "2023-09-26" @default.
• W78114055 title "Advanced system of planning and organization of classes at the university" @default.
• W78114055 hasPublicationYear "2014" @default.
• W78114055 type Work @default.
• W78114055 sameAs 78114055 @default.
• W78114055 citedByCount "0" @default.
• W78114055 crossrefType "dissertation" @default.
• W78114055 hasAuthorship W78114055A5008032138 @default.
• W78114055 hasConcept C110354214 @default.
• W78114055 hasConcept C127413603 @default.
• W78114055 hasConceptScore W78114055C110354214 @default.
• W78114055 hasConceptScore W78114055C127413603 @default.
• W78114055 hasLocation W781140551 @default.
• W78114055 hasOpenAccess W78114055 @default.
• W78114055 hasPrimaryLocation W781140551 @default.
• W78114055 isParatext "false" @default.
• W78114055 isRetracted "false" @default.
• W78114055 magId "78114055" @default.
• W78114055 workType "dissertation" @default.