Student Information System Entity Relationship Model

A database is a collection of information that is organized so that it can easily be accessed, managed, and updated. In one view, databases can be classified according to types of content: bibliographic, full-text, numeric, and images.

In computing, databases are sometimes classified according to their organizational approach.

The most prevalent approach is the relational database, a tabular database in which data is defined so that it can be reorganized and accessed in a number of different ways. A distributed database is one that can be dispersed or replicated among different points in a network. An object-oriented programming database is one that is congruent with the data defined in object classes and subclasses.

Computer databases typically contain aggregations of data records or files, such as sales transactions, product catalogs and inventories, and customer profiles. Typically, a database manager provides users the capabilities of controlling read/write access, specifying report generation, and analyzing usage. Databases and database managers are prevalent in large mainframe systems.

QUESTION 1

1. Create a database for a Student Information System. Your database should have the following components:

i) Tables

ii) Each and every table should have the Primary Key stated.

iii) The relationship between the tables

Answer question 1

Figure 1: table of student

Student index number

Student name

Age

Sex

IP 101551

YUKARI

IP 101552

ZAKA

IP 101553

ZAKURA

IP 101554

PAK HOE

IP 101555

CHIN KIT

IP 101556

MUN YEE

IP 101557

YEE YAN

IP 101558

BOON KIT

IP 101559

CHAN HOE

IP101560

YEE HOE

Leaturer id

leaturer

Age

Ic number

IP 101200

CHAN MUI KAH

123456781

IP 101201

CHIN KANG HANG

123456782

IP101202

KANG QING QING

123456783

IP101203

YANG CHIN KAH

123456784

IP101204

JEFF

123456785

IP101205

CHAN HOE

123456786

IP101206

KAH YAN

123456787

IP101207

KAH YEE

123456788

IP101208

YEE YAN

123456789

IP101209

TEE HOE

123456790

Figure 2:Table of leaturer

Campus ID

Campus

Office number

Since year

CA 1234

IPOH

+01234561

1987

CA 1235

KUALA LUMPUL

+01234562

1877

CA1236

JOHOR

+01234563

1992

CA1237

KUALA TERRENGANU

+01234564

1992

CA1238

SINGAPORE

+01234565

1993

CA1239

SELANGOR

+01234566

1994

CA1240

THAILAND

+01234567

1995

CA1241

ENGLAND

+01234568

1996

CA1242

INDONESIA

+01234569

1997

CA1243

KUANTAN

+01234561

1998

Figure 3: table of campus

Couse id

Couse

Semester payment

Full payment

AA101

DIT

1000

20000

AA102

CICT

1001

20001

AA103

DHO

1002

20002

AA104

CAT

1003

20003

AA105

DBM

1004

20004

AA106

CBM

1005

20005

AA107

CHO

1006

20006

AA108

DEE

1007

20007

AA109

DOT

1008

20008

AA110

COT

1009

20009

Figure 4:table of course

Primary key

A primary key uniquely defines a relationship within a database. In order for an attribute to be a good primary key it must not repeat. While natural attributes are sometimes good primary keys, Surrogate keys are often used instead. A surrogate key is an artificial attribute assigned to an object which uniquely identifies it (for instance, in a table of information about students at a school they might all be assigned a Student ID in order to differentiate them). The surrogate key has no intrinsic (inherent) meaning, but rather is useful through its ability to uniquely identify a tuple.

Another common occurrence, especially in regards to N:M cardinality is the composite key. A composite key is a key made up of two or more attributes within a table that (together) uniquely identify a record. (For example, in a database relating students, teachers, and classes. Classes could be uniquely identified by a composite key of their room number and time slot, since no other class could have that exact same combination of attributes. In fact, use of a composite key such as this can be a form of data verification, albeit a weak one.)

Foreign key

A foreign key is a field (or fields) that points to the primary key of another table. The purpose of the foreign key is to ensure referential integrity of the data. In other words, only values that are supposed to appear in the database are permitted.

For example, say we have two tables, a customer table that includes all customer data, and an ordestable that includes all customer orders. The constraint here is that all orders must be associated with a customer that is already in the customer table. In this case, we will place a foreign key on the orders table and have it relate to the primary key of the customer table. This way, we can ensure that all orders in the orders table are related to a customer in the customer table. In other words, the ordes table cannot contain information on a customer that is not in the customer table.

RELATIONSHIP DATABASE MANAGEMENT SYSTEM

Relational databases, as implemented in relational database management systems, have become a predominant choice for the storage of information in new databases used for financial records, manufacturing and logistical information, personnel data and much more. Relational databases have often replaced legacy hierarchical databases and network databases because they are easier to understand and use, even though they are much less efficient. As computer power has increased, the inefficiencies of relational databases, which made them impractical in earlier times, have been outweighed by their ease of use. However, relational databases have been challenged by Object Databases, which were introduced in an attempt to address the object-relational impedance mismatch in relational database, and XML databases.

QUESTION 2

2. Represent your database for the Student Information System Entity Relationship(ER) model and create the database in Microsoft Access.

ANSWER QUESTION 2

Question 2 I will show the student information relationship in Microsoft access.

Figure 1

FIGURE 1 is the student information in Microsoft access. There are student id, name, age and sex.

Figure 2

Figure 2 is step to set the primary key. First click the design and then click the primary key to set as the student primary key.

Figure 3

Figure 3 is the lecturer table. It have lecturer id, name, age, and ic. The most importand is the student id is same as student table.

Figure 4

Figure 4 is campus table, its have campus id, campus name, office num, since years.

Figure 5

Figure 5 is a campus table. Its show course id, campus id, semester payment and full payment.

Figure 6

Figure 6 is the relationship table like a student, leaturer, course and campus.

Figure 7

Figure 7 will show you all the table of leaturer, campus, student and course. After I will do the relationship between all of it.

figure 8

Figure 8 is all the relationship between the student table, lecturer table, course table and campus table.

Figure 9

Figure 9 is all the relationship of them after click student id, it will show all the leaturer id, campus id and course id. All of it I already done the database for the Student Information System Entity Relationship(ER) model.

CONCLUSION

After I doing this assignment, I have learned many about knowledge of database. Database is a structured collection of records or data that is stored in a computer system. In order for a database to be truly functional, it must not only store large amounts of records well, but be accessed easily. Another way new information and changes should also be fairly easy to input. In order to have a highly efficient database system, you need to incorporate a program that manages and information stored on the system.

In the question 2, I also learned about to use Microsoft access. It is very useful to me because I can use it on another way and I can stored my information with clearly and when I use it I can easy to find my information is already stored. Finally, I can use my knowledge to work when I working.

Order Now