Module 3 Project
robertdjamerson
Projectfiles.zipDatagathering/Data dictionary.pdf
Datagathering/Data Gathering Document.edited.docx
DATA GATHERING DOCUMENT 8
Data Gathering Document
Student Name
Institutional Affiliations
Importance of the Report
The sample report is an illustration of the proposed database systems for Greta's Gym. It is an illustration of how the data will be stored in the database. It also represents the processes of storing data and how the database will communicate and the operations which will be carried in the database and by the gym's processes and functions. The necessary information contained in the report will also indicate the importance of mapping information, data and entity relationship as it controls the relationship among the entities of the database. It is also important to use the report as a foundation to help, organize and increase information processing between one platform and the front end of the database.
The Logical View of the Database
The Entity Relationship Diagram
Data Dictionary
The data dictionary offers the necessary explanation of the entities, their attributes, data types and character lengths. As indicated by the ERD diagram above, the data dictionary includes all the necessary facts to understand the information and data types of the database.
a) Class Entity
b) Customer Entity
c) Equipment Entity
d) Room Entity
e) Staff Entity
References
Hay, D. C. (2013). Data model patterns: conventions of thought. Pearson Education.
Umanath, N. S., & Scamell, R. W. (2014). Data modeling and database design. Nelson Education.
image3.png
image4.png
image5.png
image6.png
image7.png
image1.emf
Microsoft_Visio_Drawing1.vsdx
customer Customer Registration Customer Details Customer Updates customer data Membership Updates Customer data Retrieval of information Data retrieval Rooms Details Customer Details Staff Details Customer details Equipment Customer details Rooms awarded a certain Instructor Rooms have certain equipment Classes Offered Room Details Room Equipments Customer Class Details Borrowed and Assigned Equipments
image2.png
Datagathering/gym.sql
-- phpMyAdmin SQL Dump -- version 4.7.0 -- https://www.phpmyadmin.net/ -- -- Host: 127.0.0.1 -- Generation Time: Nov 14, 2017 at 10:58 AM -- Server version: 10.1.26-MariaDB -- PHP Version: 7.1.8 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; SET AUTOCOMMIT = 0; START TRANSACTION; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- -- Database: `gym` -- -- -------------------------------------------------------- -- -- Table structure for table `class` -- CREATE TABLE `class` ( `Class_ID` varchar(20) NOT NULL, `Class Name` varchar(20) NOT NULL, `Room_ID` varchar(20) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `customer` -- CREATE TABLE `customer` ( `Customer_ID` varchar(20) NOT NULL, `First_Name` varchar(20) NOT NULL, `Last_Name` varchar(20) NOT NULL, `Address` varchar(20) NOT NULL, `Class_ID` varchar(20) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `equipment` -- CREATE TABLE `equipment` ( `Equipment_ID` varchar(20) NOT NULL, `Name` varchar(20) NOT NULL, `Customer_ID` varchar(50) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `rooms` -- CREATE TABLE `rooms` ( `Room_ID` varchar(10) NOT NULL, `Classes Offered` varchar(20) NOT NULL, `Staff_ID` varchar(20) NOT NULL, `Class_ID` varchar(20) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `staff` -- CREATE TABLE `staff` ( `Staff_ID` varchar(20) NOT NULL, `First_Name` varchar(20) NOT NULL, `Last_Name` varchar(20) NOT NULL, `Address` varchar(20) NOT NULL, `Room_ID` varchar(20) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- Indexes for dumped tables -- -- -- Indexes for table `class` -- ALTER TABLE `class` ADD PRIMARY KEY (`Class_ID`), ADD UNIQUE KEY `Staff_ID` (`Room_ID`); -- -- Indexes for table `customer` -- ALTER TABLE `customer` ADD PRIMARY KEY (`Customer_ID`), ADD UNIQUE KEY `Class_ID` (`Class_ID`); -- -- Indexes for table `equipment` -- ALTER TABLE `equipment` ADD PRIMARY KEY (`Equipment_ID`), ADD UNIQUE KEY `Customer_ID` (`Customer_ID`); -- -- Indexes for table `rooms` -- ALTER TABLE `rooms` ADD PRIMARY KEY (`Room_ID`), ADD UNIQUE KEY `Staff_ID` (`Staff_ID`), ADD UNIQUE KEY `Class_ID` (`Class_ID`); -- -- Indexes for table `staff` -- ALTER TABLE `staff` ADD PRIMARY KEY (`Staff_ID`), ADD UNIQUE KEY `Room_ID` (`Room_ID`); -- -- Constraints for dumped tables -- -- -- Constraints for table `customer` -- ALTER TABLE `customer` ADD CONSTRAINT `customer_ibfk_1` FOREIGN KEY (`Class_ID`) REFERENCES `class` (`Class_ID`); -- -- Constraints for table `equipment` -- ALTER TABLE `equipment` ADD CONSTRAINT `equipment_ibfk_1` FOREIGN KEY (`Customer_ID`) REFERENCES `customer` (`Customer_ID`); -- -- Constraints for table `rooms` -- ALTER TABLE `rooms` ADD CONSTRAINT `rooms_ibfk_1` FOREIGN KEY (`Staff_ID`) REFERENCES `staff` (`Staff_ID`), ADD CONSTRAINT `rooms_ibfk_2` FOREIGN KEY (`Class_ID`) REFERENCES `class` (`Class_ID`); COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
Datagathering/ProjectOverviewDocument.doc
PROJECT OVERVIEW DOCUMENT 4
Project Overview Document
Student Name
Institutional Affiliations
Functional Requirements
Considering the needs of the project, it is important to develop a system which meets the needs and demands of the Greta's Gym and team processes. The aim of the database system is to develop a system which helps to accommodate and increase the necessary communication between the gym processes and team. The gym database should be able to hold new information such as gym memberships and members. This will help in processing payrolls and holding classes. There is also the need for developing a system with the help of implementing the necessary resources to meet and improve different operations between the gym processes. The database should also be able to contain information such as on manager and class sessions offered by the database. This will increase and improve the control, security and accessibility of information and details, the gym team should also consider developing the gym database with registration details and viewing the already registered members. This will help in allocation of gym rooms to host different activities and sessions. The aim of this is to improve the relocation and management of the gym services with focus on operations and implementation of the necessary operations.
Database System
The database system to apply in developing the gym database is a relational database system. A relational database will offer the easier way of coordinating the necessary services of the database. This will help in improving the value, resources and how to effectively increase the services of the database and gym processes. For instance, the database main entities include: Classes, Rooms, instructors and Staff, customers, and equipment. To develop such a database takes into consideration the relationship between the classes offered, where allocated and how is the instructor under supervision from gym staff. The database system in a relational architecture will be able to help the gym team to control information, access information based on the need to know basis and fully integrate the consumer information into the database of the Greta Gym. Also of importance is sorting and linking information from one database to another table. It improves information readability, retrieval and updating of data. This system will the gym to maintain, store, retrieve and update data since it is easy to use and apply. It does not require a skilled and trained user to run the system since it applies the constraints and rules of a database schemas.
Database System Logical View: Current and Future Processes
References
Elmasri, R. (2008). Fundamentals Of Database Systems. Pearson Education India.
Holtzblatt, K., & Beyer, H. R. (1995). Requirements Gathering: The Human Factor. Communications Of The ACM, 38(5), 31-32.
Kuhn, K. (2000). Problems and Benefits of Requirements Gathering With Focus Groups: A Case Study. International Journal of Human-Computer Interaction, 12(3-4), 309-325.
customer Customer Registration Customer Details Customer Updates customer data Membership Updates Customer data Retrieval of information Data retrieval Rooms Details Customer Details Staff Details Customer details Equipment Customer details Rooms awarded a certain Instructor Rooms have certain equipment Classes Offered Room Details Room Equipments Customer Class Details Borrowed and Assigned Equipments
