Database Design For Torrens We Help Inc.: Requirements And Implementation

Overview of the Organization

The database is the technology that stores the data into a database and provide the option of retrieving data from it later (Gouhar, 2017).  Database Management System is the application that handle the process of storing, manipulating and retrieval of data from the database. The Microsoft Access Database has been used for crating the database on the basis of the case study of Torrens We Help Inc.

The study is based on the implementation of the database in MS Access Application. The database is developed on the conditions and business case of TWHI. The report consist of the overview of TWHI. An ERD or Entity Relationship Diagram has been generated to provide an idea regarding the design of the database. The study also consists of the information regarding the IT controls needed for protecting the database.

1.1 The Overview of the Organization:

The case study is based on the organization named, TWHI or Torrens We Help Inc. The organization is an education institution which is not for profit private organization. The organization is well known for its initiation of providing online farming education around the world. Most numbers of TWHI students are from Vietnam, Papua New Guinea and Indonesia.

The organization is currently interested in working with the industries, communities and businesses as partners. The purpose of the partnership will be providing several learning opportunities and experiences so that the students can easily enjoy the learning process. The organization is widely reputed as the institution which provide higher education to the people who otherwise could not afford it. The government of Vietnam, Papua New Guinea and Indonesia provide the payment of many of the students who are citizens of respective countries.

TWHI is currently using a spread sheet software for recording and tracking its employee’s data. The organization’s HR or human resource department is currently having issues in accessing fresh academic and staff information.

1.2 Overview of the Project:

The project is based on the requirements of the information regarding the HR processes. The project is generally based on the database management system. The database will be developed based on the processes and constraints of business process of TWHI. There are two options for implementing the project. The organization can choose an in-house system that will be implemented in the organization computer server. Otherwise, it can be implemented in the cloud based system. In-house based Access database system will be best suited for the organization’s HR department.

2. Justification for the Use of Database:

The database is considered to be the most vital tool for storing and retrieving data. The database will be used for the following advantages it will deliver to Torrens We Help Inc.

1. Controlling data redundancy: The HR department uses different software for completing the processes, each of the software holds different files. This results into duplication of data. The database will allow the HR department to store all the data into one place (Souza et al., 2015). The modern database management systems implements various checks and configuration to prevent data duplication.
2. Data sharing: The database management system allows the authorized users to share data to other people in the organization. Torrens We Help Inc. must employ an administrator who will be responsible for managing the database system. The administrators provides rights to the users of the system such as allow access to whole database or a portion of the database (Elmasri & Navathe, 2016). The biggest advantage of the database is that it allows various users to access a specific data in the database simultaneously. Another big advantage is that different software programs can access the database. This not only saves the memory but also improves the organization reliability on the information.

• Data consistency: The database management system automatically implements the data consistency by aiding the data redundancy. Suppose, the set of information of an employee appear once in the whole database. The HR department want to update a specific information of an employee (Gubanov et al., 2016). In that case, the database will update the database immediately and the updated value will be available to all the software applications connected to the database. It is easy for the database system to enforce consistency if the database has already implemented controlled redundancy.

1. Data security: Security to the organization data is another reason behind the selection of implementing a database into the Torrens We Help Inc. environment. The database management system allows the users to create forms and reports in an easier and faster manner (Souza et al., 2015). A structured database has various configuration aspects that can prevent any unauthorized user to access unintended data. Suppose, the application HR department is using is hacked. No matter how the hackers try if they cannot breach the DBMS security checks, no data will be revealed to the hackers.
2. 3. Database Design:

The ERD showed in the figure 1, consist of four entities. All of the entities have primary keys. The teaching staff is also part of the employee that is why the teaching staff entity’s primary key is actually the foreign key of employee table. The subject a teacher teaches can be identified using the teacher subject entity. This entity has a composite primary key. The employee code refers to the primary key of teaching staff entity not the employee entity. If the employee is not a teaching staff then he or she cannot teach a subject. The subject entity has only two attributes, primary key which is subject code and subject name.

As one employee may or may not be one teacher, the relation between the employee and teaching staff is one to one multiplicity with 0 or one cardinality. One subject can be taught by many teachers but a teacher will teach only one subject, that is why the relation is one to many. One subject may be or may not be taught at the institution, but a subject which is currently taught to the students must be listed in the subject entity.

Table: Employee
Attribute	Data type	Constraints
employeeID	Number	Primary Key
Title	Short Text	None
firstName	Short Text	None
middleName	Short Text	None
lastName	Short Text	None
birthDate	Date/Time	None
Address	Short Text	None
phoneNumber	Number	None
mobileNumber	Number	None
dateHired	Date/Time	None
dateTerminated	Date/Time	None
TFN	Number	None
Department	Short Text	None
Location	Short Text	None

Employee
employeeID	Title	firstName	middleName	lastName	birthDate	Address	phoneNumber	mobileNumber	dateHired	dateTerminated	TFN	Department	Location
1	A	Jack		Moa	7/10/1991	Main Street	12345678	12345678	3/10/2017		1	A	Main Campus
2	B	Johny	Roger	Federer	4/20/1989	Camac Street	234567	765432	5/23/2016	6/5/2018	2	B	Main Campus
3	A	Mia		Sanders	6/20/1992	Amaharst Street	98765	123456	5/23/2016		3	A	Main Campus
4	C	John		Wick	11/9/1991	Main Street	345678	765432	5/10/2016		4	F	Second Campus
5	C	Sunny		Hodge	12/29/1986	Nelson Street	123456	654322	3/10/2017	6/5/2018	5	A	Second Campus
6	B	Luka		Modrich	10/15/1992	Camac Street	987653	1234567	3/10/2017		6	E	Main Campus
7	D	Maddy	Simpsons	Jonathna	11/9/1991	Amaharst Street	234567	76543	5/17/2018		7	F	Second Campus
8	B	Emily		Mandy	12/29/1996	Nelson Street	7654321	12345678	5/17/2018		8	E	Main Campus
9	A	Rick		Morty	11/1/1991	Camac Street	982345	654234567	1/27/2018	1/7/2018	9	A	Main Campus
10	E	Christopher		Nolan	6/16/1992	Main Street	54313456	4566711	5/23/2016		10	E	Main Campus
11	asd						0	0			0

Table: Subject
Attribute	Data type	Constraints
subjectCode	Number	Primary Key
subjectName	Short Text	None

Subject
subjectCode	subjectName
1	Maths
2	Physics
3	Chemistry
4	Geography
5	History
6	English
7	French
8	Polytical Science
9	Applied Mathematics
10	Biology

Table: teacherSubject
Attribute	Data type	Constraints
subjectCode	Number	Primary Key, Foreign Key
employeeID	Number	Primary Key, Foreign Key

teacherSubject
subjectCode	employeeID
1	10
2	4
5	2
10	1

Table: teachingStaff
Attribute	Data type	Constraints
employeeID	Number	Primary Key, Foreign Key
campusLocation	Short text	None
contactDetails	Short text	None
empStatus	Short text	None

teachingStaff
employeeID	campusLocation	contactDetails	empStatus
1	Main Campus	Father-1234567	full-time
2	Second Campus	Mother-98765432	part-time
4	Main Campus	Wife-123456	sessional
10	Main Campus	Husband-8765432	full-time

4. IT controls:

Access Control: Access controls is considered to be basic functionality a database management system must include (Yunus et al., 2017). The purpose of the access control is to protect the data stored within the database from falling in the hands of unauthorized users.

Concurrency Control: Refers to the class of controls used in database management systems (DBMS) to ensure that transactions are processed in an atomic, consistent, isolated and durable manner (ACID) (Arasu et al., 2016).  This implies that only serial and recoverable schedules are permitted, and that committed transactions are not discarded when undoing aborted transactions.

5. Conclusion:

From the above study, it can be concluded that the database is a crucial element of any business in order to make the business process more convenient. The database is not designed to hold the static data like goods or staff, but it can hold more dynamic data like process status and outcome. The database will allow the HR department of Torrens We Help Inc. to access all the information of the employees.

Achpal, A., Kumar, V. B., & Mahesh, K. (2016). Modeling Ontology Semantic Constraints in Relational Database Management System. In Proceedings of the International MultiConference of Engineers and Computer Scientists (Vol. 1).

Arasu, A., Babcock, B., Babu, S., Cieslewicz, J., Datar, M., Ito, K., … & Widom, J. (2016). Stream: The stanford data stream management system. In Data Stream Management (pp. 317-336). Springer, Berlin, Heidelberg.

Elmasri, R., & Navathe, S. (2016). Fundamentals of database systems. London: Pearson.

Gouhar, A. (2017). Database Management System. International Journal of Engineering Science, 11766.

Gubanov, M., Jermaine, C., Gao, Z., & Luo, S. (2016). Hybrid: A large-scale linear-relational database management system. In MIT Annual DB Conference.

Souza, R., Silva, V., Oliveira, D., Valduriez, P., Lima, A. A., & Mattoso, M. (2015). Parallel execution of workflows driven by a distributed database management system. In ACM/IEEE Conference on Supercomputing, Poster.

Yunus, M. A. M., Krishnan, S. K. G., Nawi, N. M., & Surin, E. S. M. (2017). Study on Database Management System Security Issues. JOIV: International Journal on Informatics Visualization, 1(4-2), 192-194.