Jesus santos capote/transactional systems/write sections and subsections

README.md

@@ -1 +1,86 @@
-# Latex template for students thesis of MatCom
+## Writting a Chapter
+### Chapter Structure
+Each chapter will be structured as follows:
+- An **introduction section** which should be concise and no longer than one page. This section must provide answers to the following questions:
+
+    - What topic are you going to discuss in the chapter? (Definitions)
+    - Why is it relevant to discuss that topic? (Context and real life applications)
+    - How is structured the current chapter? (Content of the rest of the sections)
+
+- **Content sections** in a logical order so each one refers to sections that the reader is already familiar with.
+
+To work in parallel in the same chapter we need to stablish some conventions. All the chapters of the thesis will be in the `document\MainMatter\` directory. I will use the chapter called *"Sistemas de Inteligencia de Negocios"* to illustrate how these conventions will work.
+
+- Each `chapter` will have his own directory with a descriptive name. In this case we will have the `document\MainMatter\BusinessIntelligence\` directory.
+- Each `chapter` directory will have the following files:
+
+    - A `.tex` main file with the same name as the directory. In this file we will write the introductory section of the chapter and include the files of the chapter's sections. This is how this file should look like:
+
+        ```LaTex
+        % Set the name of the chapter and its label
+        \chapter{Sistemas de Inteligencia de Negocios}\label{chapter:bi-systems}
+
+        % Write here the introductory section content
+
+        % These commands include the content of the sections files
+        \include*{MainMatter/BusinessIntelligence/TransactionalSystems}
+        \include*{MainMatter/BusinessIntelligence/AnalyticalSystems}
+        \include*{MainMatter/BusinessIntelligence/ETL}
+        ```
+
+    - A `.tex` file for each section, each one with a descriptive name and structured as follows:
+
+        ```LaTex
+         % Set the name of the section and its label
+        \section{Online Analytical Processing (OLAP)} \label{section:olap}
+
+        % Write here the introduction to the section
+
+        % Subsections for the contents
+        \subsection{Objetivos de los sistemas OLAP}
+            % Write here...
+        \subsection{Arquitectura de los sistemas OLAP}
+            % Write here...
+        \subsection{Almacenes de datos}
+            % Write here...
+        \subsection{Modelo Dimensional}
+            % Write here...
+        \subsection{Arquitectura de un almac\'en de datos}
+            % Write here...
+        \subsection{Herramientas OLAP}
+            % Write here...
+
+        ```
+
+    Having separate files for the sections of a chapter will allow us to work together in the same chapter but in different sections. This way we can avoid merge conflicts while working in parallel.
+
+    We include the chapters in the main thesis `.tex` file like this:
+
+    ```LaTex
+    \include{MainMatter/BusinessIntelligence/BusinessIntelligence}
+    \include{MainMatter/AutomaticETL/AutomaticETL}
+    \include{MainMatter/Proposal/Proposal}
+    \include{MainMatter/Implementation/Implementation}
+    ```
+
+    > The difference between `\include{file}` and `\include*{file}` is that the first one will create a new page for the content of the file.
+
+### Tracking progress
+
+For trackign the progress we will use GitHub issues. We will create an issue for each section of a chapter (including the introductory section). Each issue will contain a task list including all the subsections to complete the section.
+
+Each milestone of the project will be completing a chapter and each one will have a provisional deadline.
+
+### Writting a chapter
+
+To write a chapter we will create branches with the following naming convention:
+
+`<user>/<chapter>/<section>/<description>`
+
+For example:
+
+`vicmc99/BusinessIntelligence/TransactionalSystems/Add-Relational-Database-Subsection`
+
+In each pull request you will have to assign me as reviewer
+
+It should never happen to have two branches open on the same section of the same chapter at the same time. 

document/Bibliography.bib

@@ -0,0 +1,123 @@
+@misc{foote_brief_2018,
+	title = {A {Brief} {History} of the {Data} {Warehouse}},
+	url = {https://www.dataversity.net/brief-history-data-warehouse/},
+	abstract = {A Data Warehouse (DW) stores corporate information and data from operational systems and a wide range of other data resources. Data Warehouses are designed to support the decision-making process through data collection, consolidation, analytics, and research.},
+	language = {en-US},
+	urldate = {2023-03-10},
+	journal = {DATAVERSITY},
+	author = {Foote, Keith D.},
+	month = apr,
+	year = {2018},
+	keywords = {History},
+	file = {Snapshot:C\:\\Users\\Chuchi\\Zotero\\storage\\A36IKVEL\\brief-history-data-warehouse.html:text/html},
+}
+
+@misc{naeem_data_2020,
+	title = {Data {Warehouse} {Concepts}: {Kimball} vs. {Inmon} {Approach}},
+	shorttitle = {Data {Warehouse} {Concepts}},
+	url = {https://www.astera.com/type/blog/data-warehouse-concepts/},
+	abstract = {Inmon vs Kimball: Which data warehouse concept should you use to design a data warehouse. Find out in this blog.},
+	language = {en-US},
+	urldate = {2023-03-10},
+	journal = {Astera},
+	author = {Naeem, Tehreem},
+	month = feb,
+	year = {2020},
+	file = {Snapshot:C\:\\Users\\Chuchi\\Zotero\\storage\\DVQ44NVM\\data-warehouse-concepts.html:text/html},
+}
+
+@misc{noauthor_snowflake_2018,
+	title = {Snowflake {Schema} in {Data} {Warehouse} {Model}},
+	url = {https://www.geeksforgeeks.org/snowflake-schema-in-data-warehouse-model/},
+	abstract = {A Computer Science portal for geeks. It contains well written, well thought and well explained computer science and programming articles, quizzes and practice/competitive programming/company interview Questions.},
+	language = {en-us},
+	urldate = {2023-03-10},
+	journal = {GeeksforGeeks},
+	month = aug,
+	year = {2018},
+	note = {Section: DBMS},
+	file = {Snapshot:C\:\\Users\\Chuchi\\Zotero\\storage\\QXG6SE7S\\snowflake-schema-in-data-warehouse-model.html:text/html},
+}
+
+@misc{noauthor_kimball_nodate,
+	title = {Kimball vs. {Inmon} in {Data} {Warehouse} {Architecture}},
+	url = {https://www.zentut.com/data-warehouse/kimball-and-inmon-data-warehouse-architectures/},
+	abstract = {We will discuss about the Kimball vs. Inmon in data warehouse architecture and design approach. We also answer the question of how to choose Kimball or Inmon's architecture to build data warehouse.},
+	language = {en-US},
+	urldate = {2023-03-12},
+	journal = {zentut},
+	file = {Snapshot:C\:\\Users\\Chuchi\\Zotero\\storage\\VP7BZI6R\\kimball-and-inmon-data-warehouse-architectures.html:text/html},
+}
+
+@book{diaz2012introduccion,
+  title={Introducci{\'o}n al business intelligence},
+  author={D{\'\i}az, Josep Curto},
+  year={2012},
+  publisher={Editorial UOC}
+}
+
+@book{kimball2011data,
+  title={The data warehouse toolkit: the complete guide to dimensional modeling},
+  author={Kimball, Ralph and Ross, Margy},
+  year={2011},
+  publisher={John Wiley \& Sons},
+}
+
+@book{inmon2005building,
+  title={Building the data warehouse},
+  author={Inmon, William H},
+  year={2005},
+  publisher={John wiley \& sons}
+}
+
+@misc{oltpAzure,
+	title = {Online transaction processing ({OLTP}) - {Azure} {Architecture} {Center} {\textbar} {Microsoft} {Learn}},
+	url = {https://learn.microsoft.com/en-us/azure/architecture/data-guide/relational-data/online-transaction-processing},
+	urldate = {2023-08-08},
+	file = {Online transaction processing (OLTP) - Azure Architecture Center | Microsoft Learn:C\:\\Users\\Chuchi\\Zotero\\storage\\R94PD4QG\\online-transaction-processing.html:text/html},
+}
+
+@misc{oltpOracle,
+	title = {¿{Qué} es {OLTP}?},
+	url = {https://www.oracle.com/ar/database/what-is-oltp/},
+	abstract = {OLTP implica insertar, actualizar y/o suprimir pequeñas cantidades de datos en un almacén de datos para recopilar, gestionar y proteger transacciones.},
+	language = {es},
+	urldate = {2023-08-08},
+	keywords = {OLTP vs OLAP},
+	file = {Snapshot:C\:\\Users\\Chuchi\\Zotero\\storage\\UBC7LXYA\\what-is-oltp.html:text/html},
+}
+
+@book{garcia2008database,
+  title={Database systems: the complete book},
+  author={Garcia-Molina, Hector},
+  year={2008},
+  publisher={Pearson Education India}
+}
+
+@book{silberschatz2005database,
+  title={Database systems concepts},
+  author={Silberschatz, Abraham and Korth, Henry and Sudarshan, Shashank},
+  year={2005},
+  publisher={McGraw-Hill, Inc.}
+}
+
+@misc{helenclu_database_2023,
+	title = {Database normalization description - {Microsoft} 365 {Apps}},
+	url = {https://learn.microsoft.com/en-us/office/troubleshoot/access/database-normalization-description},
+	abstract = {Describe the method to normalize the database and gives several alternatives to normalize forms. You need to master the database principles to understand them or you can follow the steps listed in the article.},
+	language = {en-us},
+	urldate = {2023-08-18},
+	author = {helenclu},
+	month = jul,
+	year = {2023},
+	file = {Snapshot:C\:\\Users\\Chuchi\\Zotero\\storage\\WH495648\\database-normalization-description.html:text/html},
+}
+
+@misc{noauthor_what_nodate,
+	title = {What is a relational database?},
+	url = {https://www.oracle.com/database/what-is-a-relational-database/},
+	abstract = {Learn the definition of a relational database and how it can help your business.},
+	language = {en},
+	urldate = {2023-08-18},
+	file = {Snapshot:C\:\\Users\\Chuchi\\Zotero\\storage\\QEGMHW8Q\\what-is-a-relational-database.html:text/html},
+}

document/MainMatter/AutomaticETL/AutomaticETL.tex

@@ -0,0 +1 @@
+\chapter{Generaci\'on Autom\'atica de Procesos ETL}\label{chapter:auto-etl}