0% found this document useful (0 votes)
51 views

Assignment 1 Front Sheet

The document is an assignment front sheet for a database design project for a university attendance tracking system. It includes the student's name and ID, a scenario describing the need for an attendance tracking system, and the requirements for the design project, including producing logical and physical database designs with at least four related tables and specifying user and system requirements.
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
51 views

Assignment 1 Front Sheet

The document is an assignment front sheet for a database design project for a university attendance tracking system. It includes the student's name and ID, a scenario describing the need for an attendance tracking system, and the requirements for the design project, including producing logical and physical database designs with at least four related tables and specifying user and system requirements.
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 10

ASSIGNMENT 1 FRONT SHEET

Qualification BTEC Level 5 HND Diploma in Computing

Unit number and title Unit 04: Database Design & Development

Submission date July-22th-2021 Date Received 1st submission July-22th-2021

Re-submission Date Date Received 2nd submission

Student Name Dang Tan Tai Student ID BSAF200013

Class PBIT16101_CNTT1 Assessor name Lam Hong Thanh

Student declaration

I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand
that making a false declaration is a form of malpractice.

Student’s signature

Grading grid

P1 M1 D1
Learning Outcomes and Assessment Criteria

Pass Merit Distinction

LO1 Use an appropriate design tool to design a relational database system for a substantial problem

P1 Design a relational database system using appropriate M1 Produce a comprehensive design for a fully D1 Assess the effectiveness of
design tools and techniques, containing at least four functional system which includes interface and the design in relation to user
interrelated tables, with clear statements of user and output designs, data validations and data and system requirements.
system requirements.  normalisation.
❒ Summative Feedback: ❒ Resubmission Feedback:

Grade: Assessor Signature: Date:


Signature & Date:
I. Database Design

1. Scenario of the chosen system……………………………..……………………………..……………………………..……………………………..05

2. SRS (System Requirement Specification) ……………………………..……………………………..……………………………..………………05

3. Logical design (ERD) ……………………………..……………………………..……………………………..……………………………..………………05

4. Explanation……………………………..……………………………..……………………………..……………………………..…………………………….06
5. Physical design ……………………………..……………………………..……………………………..……………………………..……………………………07

REFERENCES……………………………..……………………………..……………………………..……………………………..……………………………..………11
I. Database Design
1. Scenario of the chosen system
Summary the requirement:
I am an employee as a Database Developer for a large IT consultancy company.
The partner of company is FPT University. Their problem is currently facing difficulties in dealing with
managing the University.
They are requirement us to manage the university easier including: Online Library System, Student Grading
System, Attendance System, CMS System, Scheduling System,.....
Project Manager has asked me to produce a report for the C.E.O of FPT, containing:
- Clear statements of user and system requirement. The system must have at least 2 user roles, including
business process and statistical reports for FPT university managers.
- The design of the relational database system and It needs to have 4 related tables

I have assigned to design the attendance system for FPT University. An attendance program can take
attendance of many students, classes, and times. Each student is identified by student card, name, identity
card, date of birth-year of birth,... For the convenience of managing and identifying students in the same class,
I will assign them a unique student code. Each student can study many different subjects, different time
periods. To be able to know if the current student is present in the classroom at that time, we will have 2
statuses for all students: Absent and Present.

2. SRS (System Requirement Specification )


The Database (DB) attendance system is built to serve the attendance needs, check the status of students,
control whether students are present in the classroom or not, check how many students are absent, how
many sessions are present and are you eligible to take the exam?
3. Logical Design
Table of Object and Properties:

Objects Properties
Students Name: Varchar
Student ID: INT
Room Room ID: INT
Class Name: Varchar
Time to learn:Date
Subjects SubjetID: INT
Subject Name: Varchar
Start Day: Date
End Day: Date
Attendances AttendanceID: INT
Status: Boolean
Date: Date
4. Explanation

The relationship between Subjects and attendances is 1-N because a subject can attendances for many time
The relationship between Students and attendances is 1-N because a student can attendances for many time
The relationship between Room and attendances is 1-N because a room can attendances for many student

5. Physical Design
Explanation for the keywords in the table will include: Data type of each variable, Foreign Key, Primary Key
The data type of each variable will include:
- VARCHAR(n): Custom length, n is the maximum length of 1 character that allocated memory
- INT: Integer type is a number without decimal places
- DATE: Date data type is taken from the data storage machine server's data (Auto Get Date)
- NOT NULL: By default, data types cannot be empty
- PK: stands for Primary Key of each table containing keys important of that table and above all P.K must not
be empty
- FK: Abbreviation for the keyword "Foreign Key" which is the linking keys table to table to be able to query
the data of the other table.
In order to be able to easily manage each student with different majors and subjects, different classrooms will
divide them into many different tables, which include 4 tables: Student, subject, classroom and attendance. To
easily manage each table and distinguish them from each other, we will use the ID keyword, which will be the
unique index and represent each table. Where ID will be the primary key of each table and other tables that
want to query the information of the other table must have a foreign key that is the primary key of other
tables. For example: Student table has StudentID as the primary key, then to the subject table, there will be a
foreign key StudentID to query personal information of students stored in that table.

StudentID is both a primary key and a foreign key, because in the attribute of a student other people can
distinguish many different students by ID and in the Student property, the name must always be present.

In the subject table, there will be a distinguishing id for each different subject, in which the SubjectID of each
subject will represent each student's subject and only one subject can register and StudentID will be a foreign
key to be able to retrieve information from Student table. One Subjects always have the properties like: Name
Subject, Day Start and End.

To be able to easily manage each student in a subject because 1 classroom of a subject can have many
students, so for easy management we can use the roomID of each classroom to represent each student. the
management of the students (StudentID) studying that subject (SubjectID) and in that classroom until the end

To be able to easily take attendance of the student status (StudentID) present in that classroom (RoomID) at
the time the subject (SubjectID) is started, we will use the attendance system in which the system will contain
all the students in which room the subject is at and at what time (date) and the status (status) of that student
is present or absent
REFERENCES

support.microsoft.com. n.d. Database design basics - Access. [ONLINE] Available at: https://support.microsoft.com/en-


us/office/database-design-basics-eb2159cf-1e30-401a-8084-bd4f9c9ca1f5. [Accessed 18 July 2021].

viblo.asia. n.d. Just a moment.... [ONLINE] Available at: https://viblo.asia/p/ly-thuyet-chung-ve-co-so-du-lieu-3P0lPqyv5ox.


[Accessed 25 August 2021].

Peterson , R., n.d. ER Diagram: Entity Relationship Diagram Model | DBMS Example. [online] Available at:
https://www.guru99.com/er-diagram-tutorial-dbms.html. [Accessed 25 August 2021].

You might also like