Logical Database Design for HR management System

Legitimate Database Design for HR the board System Errand 1.1 The foundation data of the association and activity that would bolster. In an association a HR division is liable for record every worker. Where the representatives have a recognizable proof number, work distinguishing proof code, email address, chief just as compensation. They additionally track those workers gain motivating force or commissions notwithstanding their compensation. In any case, the organization likewise tracks their job in the association. Each activity likewise recorded by the qualities. Besides, ever occupations have work title, distinguishing proof code, most extreme and least pay of the activity. There are not many representatives work for quite a while with the organization and they include held diverse division inside the organization. On the off chance that any representative leaves, at that point the activity ID number and division are recorded. The organization likewise track the area of its specializations and stockrooms. Each representative must allot with an office where divisions are distinguished by the exceptional recognizable proof number. Those offices are related with various areas. The organization need to store the area, for example, the state, city, postal code, road name just as region code. The organization additionally record the area name, money name and the locale. This database underpins a superior worker the executives plan just as their areas of expertise, area and related occupations. In any case, the organization would have a superior structure to store their classified data. This database will give a superior removed data to built up their deficiency. This proficient information structure permits them expands their capacity just as it avoid the repetition in information. Assignment 1.2 a reasonable database plan and rundown of big business rules Figure 1: EER-outline indicating all venture rules (Source: Created by creator) Task2.1: A Logical Database Design for HR the board System Figure 2: coherent database plan (Source: Created by creator) Task2.2: Create the tables utilizing Oracle DBMS - Table structure for COUNTRIES - DROP TABLE MYDB.COUNTRIES; Make TABLE MYDB.COUNTRIES ( country_id VARCHAR2(30 BYTE) NOT NULL , country_name VARCHAR2(30 BYTE) NULL , region_id VARCHAR2(30 BYTE) NULL ) LOGGING NOCOMPRESS NOCACHE ; - Table structure for DEPARTMENTS - DROP TABLE MYDB.DEPARTMENTS; Make TABLE MYDB.DEPARTMENTS ( department_id VARCHAR2(30 BYTE) NOT NULL , department_name VARCHAR2(30 BYTE) NULL , manager_id VARCHAR2(30 BYTE) NULL , location_id VARCHAR2(30 BYTE) NULL ) LOGGING NOCOMPRESS NOCACHE ; - Table structure for EMPLOYEES - DROP TABLE MYDB.EMPLOYEES; Make TABLE MYDB.EMPLOYEES ( employee_id VARCHAR2(30 BYTE) NOT NULL , first_name VARCHAR2(30 BYTE) NULL , last_name VARCHAR2(30 BYTE) NULL , email VARCHAR2(30 BYTE) NULL , phone_number NUMBER(12) NULL , hire_date DATE NULL , job_id VARCHAR2(30 BYTE) NULL , pay NUMBER(10,2) NULL , commission NUMBER(10,2) NULL , manager_id VARCHAR2(30 BYTE) NULL , department_id VARCHAR2(30 BYTE) NULL ) LOGGING NOCOMPRESS NOCACHE ; - Table structure for JOB_HISTORY - DROP TABLE MYDB.JOB_HISTORY; Make TABLE MYDB.JOB_HISTORY ( employee_id VARCHAR2(30 BYTE) NOT NULL , start_date DATE NULL , end_date DATE NULL , job_id VARCHAR2(30 BYTE) NULL , department_id VARCHAR2(30 BYTE) NOT NULL ) LOGGING NOCOMPRESS NOCACHE ; - Table structure for JOBS - DROP TABLE MYDB.JOBS; Make TABLE MYDB.JOBS ( job_id VARCHAR2(30 BYTE) NOT NULL , job_title VARCHAR2(30 BYTE) NULL , min_salary NUMBER(10,2) NULL , max_salary NUMBER(10,2) NULL ) LOGGING NOCOMPRESS NOCACHE ; - Table structure for LOCATIONS - DROP TABLE MYDB.LOCATIONS; Make TABLE MYDB.LOCATIONS ( location_id VARCHAR2(30 BYTE) NOT NULL , street_address VARCHAR2(30 BYTE) NULL , postal_code NUMBER(10) NULL , city VARCHAR2(30 BYTE) NULL , state VARCHAR2(30 BYTE) NULL , country_id VARCHAR2(30 BYTE) NULL ) LOGGING NOCOMPRESS NOCACHE ; - Table structure for REGIONS - DROP TABLE MYDB.REGIONS; Make TABLE MYDB.REGIONS ( region_id VARCHAR2(30 BYTE) NOT NULL , region_name VARCHAR2(30 BYTE) NULL ) LOGGING NOCOMPRESS NOCACHE ; Task2.3: Create the four most helpful lists - Records structure for table COUNTRIES - - Checks structure for table COUNTRIES - Modify TABLE MYDB.COUNTRIES ADD CHECK (country_id IS NOT NULL); - Essential Key structure for table COUNTRIES - Modify TABLE MYDB.COUNTRIES ADD PRIMARY KEY (country_id); - Records structure for table DEPARTMENTS - - Checks structure for table DEPARTMENTS - Modify TABLE MYDB.DEPARTMENTS ADD CHECK (department_id IS NOT NULL); - Essential Key structure for table DEPARTMENTS - Modify TABLE MYDB.DEPARTMENTS ADD PRIMARY KEY (department_id); - Records structure for table EMPLOYEES - - Checks structure for table EMPLOYEES - Modify TABLE MYDB.EMPLOYEES ADD CHECK (employee_id IS NOT NULL); - Essential Key structure for table EMPLOYEES - Modify TABLE MYDB.EMPLOYEES ADD PRIMARY KEY (employee_id); - Records structure for table JOB_HISTORY - - Checks structure for table JOB_HISTORY - Modify TABLE MYDB.JOB_HISTORY ADD CHECK (employee_id IS NOT NULL); Modify TABLE MYDB.JOB_HISTORY ADD CHECK (department_id IS NOT NULL); - Essential Key structure for table JOB_HISTORY - Modify TABLE MYDB.JOB_HISTORY ADD PRIMARY KEY (employee_id); - Records structure for table JOBS - - Checks structure for table JOBS - Modify TABLE MYDB.JOBS ADD CHECK (job_id IS NOT NULL); - Essential Key structure for table JOBS - Modify TABLE MYDB.JOBS ADD PRIMARY KEY (job_id); - Records structure for table LOCATIONS - - Checks structure for table LOCATIONS - Modify TABLE MYDB.LOCATIONS ADD CHECK (location_id IS NOT NULL); - Essential Key structure for table LOCATIONS - Modify TABLE MYDB.LOCATIONS ADD PRIMARY KEY (location_id); - Records structure for table REGIONS - - Checks structure for table REGIONS - Modify TABLE MYDB.REGIONS ADD CHECK (region_id IS NOT NULL); - Essential Key structure for table REGIONS - Modify TABLE MYDB.REGIONS ADD PRIMARY KEY (region_id); - Remote Key structure for table MYDB.COUNTRIES - Modify TABLE MYDB.COUNTRIES ADD FOREIGN KEY (region_id) REFERENCES MYDB.REGIONS (region_id) ON DELETE CASCADE; - Remote Key structure for table MYDB.DEPARTMENTS - Modify TABLE MYDB.DEPARTMENTS ADD FOREIGN KEY (location_id) REFERENCES MYDB.LOCATIONS (location_id) ON DELETE CASCADE; - Remote Key structure for table MYDB.EMPLOYEES - Modify TABLE MYDB.EMPLOYEES ADD FOREIGN KEY (job_id) REFERENCES MYDB.JOBS (job_id) ON DELETE CASCADE; Modify TABLE MYDB.EMPLOYEES ADD FOREIGN KEY (department_id) REFERENCES MYDB.DEPARTMENTS (department_id) ON DELETE CASCADE; - Remote Key structure for table MYDB.JOB_HISTORY - Modify TABLE MYDB.JOB_HISTORY ADD FOREIGN KEY (employee_id) REFERENCES MYDB.EMPLOYEES (employee_id) ON DELETE CASCADE; - Remote Key structure for table MYDB.LOCATIONS - Modify TABLE MYDB.LOCATIONS ADD FOREIGN KEY (country_id) REFERENCES MYDB.COUNTRIES (country_id) ON DELETE CASCADE; Task2.4: Data Population The underneath figures indicating all information in each table: Table nations: Table divisions: Table representatives: Table job_history: Table occupations: Table areas: Table locales: Task2.5: SQL Query composing Inquiry 1 SELECT MYDB.COUNTRIES.country_name FROM MYDB.COUNTRIES Inquiry 2 SELECT MYDB.REGIONS.region_name, MYDB.COUNTRIES.country_name FROM MYDB.COUNTRIES Internal JOIN MYDB.REGIONS ON MYDB.COUNTRIES.region_id = MYDB.REGIONS.region_id Inquiry 3 SELECT MYDB.JOB_HISTORY.start_date, MYDB.JOB_HISTORY.end_date, MYDB.EMPLOYEES.first_name, MYDB.EMPLOYEES.last_name, MYDB.EMPLOYEES.email FROM MYDB.EMPLOYEES FULL OUTER JOIN MYDB.JOB_HISTORY ON MYDB.JOB_HISTORY.employee_id = MYDB.EMPLOYEES.employee_id Inquiry 4 SELECT Count(MYDB.EMPLOYEES.employee_id) AS Number Of Employee FROM MYDB.EMPLOYEES Inquiry 5 SELECT MYDB.EMPLOYEES.first_name, MYDB.EMPLOYEES.last_name, MYDB.EMPLOYEES.email, MYDB.EMPLOYEES.phone_number, MYDB.EMPLOYEES.hire_date, MYDB.EMPLOYEES.salary, MYDB.EMPLOYEES.commission FROM MYDB.EMPLOYEES Request BY MYDB.EMPLOYEES.first_name ASC Inquiry 6 SELECT MYDB.EMPLOYEES.first_name, MYDB.EMPLOYEES.last_name, MYDB.EMPLOYEES.email, MYDB.EMPLOYEES.phone_number, MYDB.EMPLOYEES.hire_date, MYDB.EMPLOYEES.salary, MYDB.EMPLOYEES.commission FROM MYDB.EMPLOYEES WHERE MYDB.EMPLOYEES.email LIKE %gmail% Inquiry 7 SELECT MYDB.EMPLOYEES.first_name, MYDB.EMPLOYEES.last_name, MYDB.EMPLOYEES.email, MYDB.EMPLOYEES.phone_number FROM MYDB.EMPLOYEES Internal JOIN MYDB.JOB_HISTORY ON MYDB.JOB_HISTORY.employee_id = MYDB.EMPLOYEES.employee_id WHERE MYDB.JOB_HISTORY.employee_id IN (MYDB.EMPLOYEES.employee_id) Inquiry 8 MYDB.EMPLOYEES.email, MYDB.EMPLOYEES.phone_number, MYDB.EMPLOYEES.hire_date, MYDB.EMPLOYEES.job_id, MYDB.EMPLOYEES.salary, MYDB.EMPLOYEES.commission, MYDB.EMPLOYEES.manager_id, MYDB.EMPLOYEES.department_id, MYDB.EMPLOYEES.employee_id FROM MYDB.EMPLOYEES, (SELECT MYDB.JOB_HISTORY.employee_id fromã‚â MYDB.JOB_HISTORY) subquery1 WHERE subquery1.employee_id=MYDB.EMPLOYEES.employee_id Asabe, S.A., Oye, N.D. also, Goji, M., 2013. Emergency clinic persistent database the executives framework: A contextual analysis of general medical clinic north-bank makurdi-nigeria. Compusoft, 2(3), p.65. Coronel, C. also, Morris, S., 2016. Database frameworks: structure, usage, the board. Cengage Learning. Dorok, S., Breãÿ, S., Teubner, J. also, Saake, G., 2015. Adaptable Analysis of Plant Genomes in a Database Management System. In EDBT (pp. 509-512). Hussain, M., Pandey, A.C. also, Pachauri, S., 2013. Performanc Tuning of Database Management System by Fuzzy Controlled Architecture. Pragyaan: Journal of Information Technology, p.30. Jahn, M., Schill, E. what's more, Breunig, M., 2013. Towards a 4D database administration framework for geothermal ventures: a test

Teaching and Education Philosophy :: Teaching Education Philosophy

Instructing and Education Philosophy My way of thinking is that a teacher is the most important asset our nation has. Of the considerable number of occupations or vocations in this world none of them would be conceivable without instructors. There are two central matters to my way of thinking, why educators are significant and what teachers' identity is. Ideally perusing my way of thinking will give you a superior comprehension of the significance of teachers in this world. Instructors are significant in our general public since we need them to give our childhood the information and social encounters they should improve their future and the eventual fate of the whole planet. As an instructor I would like to be capable impact numerous lives and help understudies comprehend what training can accomplish for them and their future. I can review just a single educator from secondary school who really discussed school and what we would need to improve arranged for school. Dr. Lawrence was my eleventh grade science educator. He had been a school educator at George Mason University for around 30 years before he chose to instruct at my school. He brought a school like climate into our study hall, which helped us, get ready for the manner in which things would be in school. This is only a little case of what instructors are for, to teach understudies on something beyond books or scholastics however on life. Educators are something beyond individuals who transfer d ata about a specific subject. What teachers' identity is, they are anybody and everybody. Instructors are grandmas, fathers, siblings, and sisters. For anything to be educated it must be instructed. I recall commonly my mother and father sitting me down to discuss a few circumstances that may occur and disclosing to me approaches to manage them. Homeroom educators particularly in the early years are the individuals that those understudies will see most over the span of the day and will learn <a href=http://www.