Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Assignment Database

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 23

ASSIGNMENT 1 FRONT SHEET

Qualification TEC Level 5 HND Diploma in Computing

Unit number and title Unit 04: Database Design & Development

Submission date Date Received 1st submission

Re-submission Date Date Received 2nd submission

Student Name NGUYEN VAN MANH Student ID BHAF200079

Class PBTIT17101 Assessor name DINH THI MINH NGUYET

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
❒ Summative Feedback: ❒ Resubmission Feedback:

Grade: Assessor Signature: Date:


Signature & Date:
Table of Contents:
Database Design & Development
I. Database Design (D1)
1. Scenario of the chosen system

2. SRS (System Requirement Specification)

3. Logical Design (ERD)

4. Explanation

5. Physical Design

II. Data Validation and Normalization (M1)


1. User interfaces of your system

2. Data Validation (included in physical design)

3. Normalization
III. Design Evaluation (D1)
IV. References
I. Database Design (P1)
- A database is an organized collection of structured information, or data, typically stored electronically in a
computer system. A database is usually controlled by a database management system (DBMS). Together, the
data and the DBMS, along with the applications that are associated with them, are referred to as a database
system, often shortened to just database.

- Data within the most common types of databases in operation today is typically modeled in rows and columns
in a series of tables to make processing and data querying efficient. The data can then be easily accessed,
managed, modified, updated, controlled, and organized. Most databases use structured query language (SQL) for
writing and querying data. (What is a database?, 2021)

1. Scenario of the chosen system


- In this assignment, I will work as a data developer for a large IT company and was selected to build a student
grading system database for FPT. I will analyze requirements, design database systems, develop a fully functional
relational database system based on an existing system design, test and create technical documents according to
user requirements.

2. SRS (System requirement Specification)


- In this assignment, I received a request from FPT about build a student grading system. It allows storing and
retrieving student information.

- For each student, you need to manage the following information: Student code, Full name, gender, date of birth,
place of birth, address, ID number or citizenship, class.
- A place to store and retrieve information about courses. It include course code, course name, course description,
start-date and end-date.

 The course code is unique, consisting of 7 characters both letters and numbers.

 Each subject can have 1-3 teachers participating in teaching and a teacher can teach many different subjects.

 Course names cannot be duplicated.

- Student transcripts and for each course, student have 4 types of marks.

 Attendence only counts the test conditions, not the final score.

 Midterm exam score and end-of-term exam score where the final score is calculated as 60 percent of the end-
of-term plus 40 percent of the midterm score.

3. Logical Design (ERD)


- ERD stands for Entity Relation Diagram.

- An entity relationship diagram (ERD), also known as an entity relationship model, is a graphical representation
that depicts relationships among people, objects, places, concepts or events within an information technology (IT)
system. (What is Entity Relationship Diagram (ERD)? - Definition from WhatIs.com, 2021)

- My ERD includes 7 entity: Class, Student, StudentAccount, Grading, Course, Teacher and TeacherCourse.
Picture of my ERD about Student Grading System

4. Explanation
- Entity: An entity is an object that exists. It doesn't have to do anything; it just has to exist. In database
administration, an entity can be a single thing, person, place, or object. Data can be stored about such entities.
(2021)

- Attribute: An attribute is a characteristic. In a database management system (DBMS), an attribute refers to a


database component, such as a table. It also may refer to a database field. Attributes describe the instances in the
column of a database. (What is an Attribute in Database Systems? - Definition from Techopedia, 2021)

- Relationship: A relationship, in the context of databases, is a situation that exists between two relational
database tables when one table has a foreign key that references the primary key of the other table. Relationships
allow relational databases to split and store data in different tables, while linking disparate data items. (What is a
Relationship? - Definition from Techopedia, 2021).

- In my ERD have 7 entity includes: Class, Student, StudentAccount, Grading, Course, Teacher and
TeacherCourse. And each entity has its own attributes.

- Entity Class includes 2 attributes are ClassID and ClassName where ClassID is primary key.

- Student entity includes 8 attributes are StdID, StdName, StdGender, StdDoB, StdPob, StdAddress, StdPassport
and ClassID where StdID is primary key and ClassID is foreign key of Class entity.
- StudentAccount entity includes 3 attributes are UsernameST, SAPassword, StdID where UsernameST is primary
key and StdID is foreign key of Student entity.

- Teacher entity includes 8 attributes are TeacherID, NameTeacher, DoB, PoB, Gender, RecruimentDay,
UsernameTA, TAPassword where TeacherID is primary key.
- Course entity includes 5 attributes are CourseID, CourseName, Description, StartDate and EndDate. CourseID is
primary key.

- TeacherCourse entity includes 2 attributes are TeacherID and CourseID. Both of these attributes are primary
keys. TeacherID foreign key of Teacher entity and CourseID foreign key of Course entity.
- Grading entity includes 5 attributes are CourseID, StdID, Attendence, MidTerm and EndTerm. CourseID and
StdID are primary key, CourseID foreign key of Course entity and StdID foreign key of Student entity.

5. Physical Design
a) Definition
- Physical database design is the process of transforming a data model into the physical data structure of a
particular database management system.

- Physical database design translates the logical data model into a set of SQL statements that define the database.
For relational database systems, it is relatively easy to translate from a logical data model into a physical database.

b) The attention while doing physical design


- 11 important database designing rules which I follow:

Rule 1: What is the nature of the application (OLTP or OLAP)?

Rule 2: Break your data in to logical pieces, make life simpler.

Rule 3: Do not get overdosed with rule 2.

Rule 4: Treat duplicate non-uniform data as your biggest enemy.

Rule 5: Watch for data separated by separators.

Rule 6: Watch for partial dependencies.

Rule 7: Choose derived columns preciously.

Rule 8: Do not be hard on avoiding redundancy, if performance is the key.

Rule 9: Multidimensional data is a different beast altogether.

Rule 10: Centralize name value table design.

Rule 11: For unlimited hierarchical data self-reference PK and FK.


(koirala, 2021)

c) Create database by SQL Server


- Create Student Grading System database

- Create Class database

And add database


- Create Student database

And add database


- Create StudentAccount database
And add data

- Create Teacher database


And add database

- Create Course database


And add database

- Create TeacherCourse database


And add database

- Create Grading database


And add database
II. Data Validation and Normalization (M1)
1. User interfaces of your system

2. Data Validation

3. Normalization

III. Design Evaluation (D1)


IV. References
 Techdocs.broadcom.com. 2021. Introduction to Logical Design. [online] Available at:
<https://techdocs.broadcom.com/us/en/ca-mainframe-software/database-management/ca-idms/19-
0/administrating/administrating-database-design/introduction-to-logical-design.html> [Accessed 20 June 2021].

 Oracle.com. 2021. What is a database?. [online] Available at: <https://www.oracle.com/database/what-is-database/>


[Accessed 21 June 2021].

 SearchDataManagement. 2021. What is Entity Relationship Diagram (ERD)? - Definition from WhatIs.com. [online]
Available at: <https://searchdatamanagement.techtarget.com/definition/entity-relationship-diagram-ERD> [Accessed 22
June 2021].

 Study.com. 2021. [online] Available at: <https://study.com/academy/lesson/what-is-an-entity-in-a-database.html>


[Accessed 22 June 2021].
 Techopedia.com. 2021. What is an Attribute in Database Systems? - Definition from Techopedia. [online] Available at:
<https://www.techopedia.com/definition/1164/attribute-database-systems#:~:text=In%20general%2C%20an
%20attribute%20is,the%20column%20of%20a%20database.> [Accessed 22 June 2021].

 Techopedia.com. 2021. What is a Relationship? - Definition from Techopedia. [online] Available at:
<https://www.techopedia.com/definition/24438/relationship-databases#:~:text=A%20relationship%2C%20in%20the
%20context,while%20linking%20disparate%20data%20items.> [Accessed 22 June 2021].

 Koirala, S., 2021. 11 important database designing rules which I follow. [online] Codeproject.com. Available at:
<https://www.codeproject.com/Articles/359654/11-important-database-designing-rules-which-I-fo-2> [Accessed 22
June 2021].

You might also like