Information technology assignment 1 unit database design & development

Education INFORMATION TECHNOLOGY ASSIGNMENT 1 UNIT: DATABASE DESIGN & DEVELOPMENT STUDENT: PHAM PHU LOC CLASS: IT05102 STUDENT ID: BD00053 SUPERVISOR: VO DUC HOANG Da Nang, December

BTEC FPT INTERNATIONAL COLLEGE

Alliance with ago Education

INFORMATION TECHNOLOGY

ASSIGNMENT 1 UNIT: DATABASE DESIGN & DEVELOPMENT

STUDENT: PHAM PHU LOC CLASS: IT05102 STUDENT ID: BD00053 SUPERVISOR: VO DUC HOANG

Da Nang, December 2022

‘BTEC

Alliance with ago Education ‘BTEC

ASSIGNMENT 1 FRONT SHEET

Qualification BTEC Level 4 HND Diploma in Computing

Unit number and title Unit: Database Design & Development

Date received (1st Submission date 10/11/2021 ¬ 8/11/2021

submission) Date received (2nd Re-submission đate

submission) Student name Pham Phu Loc Student ID BD00053

Class IT105102 Assessor name Vo Duc Hoang

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:

Phu Loc

Grading grid:

SBTEC

Alliance with GGG Education ‘BTEC

Summative Feedbacks: Resubmission Feedbacks:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

Performed Student: Pham Phu Loc

TABLE OF CONTENT

II §N.4819616).40.161 2 si.àán19).0026n)nh)0) 1 1 REVIEWERS .V V Q2L 22 HH HT HH HH2 Hà nhi TABLEOECONTENI .ẶẶ.Q2L HH HH nhe LIST OF TABLES AND FIGURES

LIST OF ACRONYM .Ặ Q2Q22QQ 2H HH Hy INTRODUCTION —— ĂẰ.ĂẰ 2 2e CHAPTER 1: DESIGN DATABASE 2

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

1.1 Design a relational database system using appropriate design tools and techniques,

containing at least four _interrelated_tables, with clear siatements of user and system

is01111511911058 90007010707 2

1.1.1 The scenario of the chosen system -2:©2+2++2+v2++t2vEverxvrxvrrrrrrrrrrrrree 2L

1.1.2 System Requirement Specification (SRS) — _ ee

IS :0 8 o8.) 0n Á 1.1.4 Explanalon —_ 2 L2 22L 2 12L HH HH nh HH, Ấ II33⁄n1/65:00 6

CRITICAL EVALUATION NA s 6.6).I0 5061/60) 05 16

LIST OF TABLES AND FIGURES

Figure 1.1-1: FPT sChOOIÌ - ng ng HH HH HH TH Ho 1 9 1

In 72001030000 nà/, in Figure 1.1-3: Entity Relationship Diagram - ng HH HH HH

Figure 1.+4: Physical đesign ng HT HH TH HH HH TH 79

Table 1.1-1: Major ẽ E6 3 E026 4 IEIÔ0 i0 Ecvia.-oodddiiii5

EU 0 ái son cố ốc

EU ni

-LIST OF THE ACRONYM

CMS Content Management System

SRS System Requirement Specification

ERD Entity Relationship Diagram

RAM Random Access Memory

BTEC _ Business and Technology Education

Council

ERM _ Entity Relationship Diagram

IT Information Technology

:BTEC

INTRODUCTION First of all, I would like to thank my mentor Vo Duc Hoang for his consfant support in my

studies and research, for his patience, motivation, enthusiasm and rich knowledge Without your wonderful help, I would not have been able to achieve this

In addition to my mentor, I would like to thank my friends who have helped me improve

my knowledge of my subject And besides, I would like to thank the school for creating all conditions for me to have adequate facilities to help me complete my work

Last but not least, I would like to thank my family: my parents Pham Phu Loi and Phan Thi Thu They are always behind to care and help me have more motivation to complete the work well! The network plays a very important role in life

From there, we will test the results that we have done Finally, we will operate the system and maintain it It is also a process to build a complete Database Design & Development system Let's find out in this assignment!

1 Use an appropriate design tool to design a relational database system for a

substantial problem (LO1)

1.1 Design a relational database system using appropriate design tools and techniques, containing at least four interrelated tables, with clear statements of user and system

requirements (P1)

Performed Student: Pham Phu Loc

CHAPTER 1: DESIGN DATABASE

1 Use an appropriate design tool to design a relational database system

for a substantial problem (LO 1) 1.1 Design a relational database system using appropriate design tools and

techniques, containing at least four interrelated tables, with clear statements of user

and system requirements (P1)

1.1.1 Scenario of the chosen system

Figure 1.1-1: FPT school

- For a big IT consulting firm, you are a Database Developer The FPT University has approached the firm and is expanding due to the increase in the number of students FPT has difficulty interacting with university management at the moment

- It chose to build various academic systems that would make the institution simpler to

administer, such as: the online library, the student graduation system, the attendance system,

the CMS system

- You are responsible for selecting one of the systems for developing the FPT university database Your responsibilities are:

O Work with FPT to learn about existing system needs

oO Analysis needs and makes unambiguous user and system requirements statements

O Conceive a relational database system utilizing design tools and processes

oO Develop a completely working relation database system based on the system design

that exists

oO Test the system against needs of users and systems

Oo Produce user and technical documents

- Currently, FPT University has many discrete and inconsistent management systems such as: Online Library system, Student Grading System, Attendance System, CMS System, Scheduling

System, Enrolment Systems, and so on

- Thus, it is time for us to create a unified system to effectively capture and manage students in teaching and school management

- Therefore, we have proposed to build a “Library Management System” - a large system with a large source of data so that FPT University can thoroughly solve these difficult problems 1.1.2 System Requirement Specification (SRS)

- Creating an FPT relational database and dividing it into clear and precise tables will solve all the above difficulties:

+ Books: The publisher lends books, types of books, and students borrow them

+ Publisher: each publisher has publisher name, publisher code, address

+ Type of book: Each type of book has a type name and type code

+ Borrow: Borrowed days, Borrowed date, Return date

+ Student: Each student has a student code, student's first and last name, and class Results: Each test result is recorded by a student who borrowed and returned it on time, on time

inn

rmsabart.net

Figure 1.1-2 SRS

- Functional requirements:

O The system has the following main functions: Manage students to borrow books quickly, simply but with high efficiency

O_ This system has high security to avoid data loss

O Correct transaction actions are stored and the system records modifications and cancellations

O Beautiful external interface, easy to use

O_ Data history storage system for users to easily check and review

- Non-functional requirements:

Oo There are no problems and the system operates stably 24/7 and high

performance

O _sCFor instance, re-response time is within 1-2 seconds as well as throughput

Os The system also have a scalability

O Stable resilience and maintenance and excellent interoperability

- System requirements:

OThe system runs on Windows 8, Windows 10, Windows 11 (Preferred Windows 10)

O _—s~ Processor: Processor clocked at 1 gigahertz (GHz) or higher, or SoC

O RAM: 1 gigabyte (GB) for 32 bits or 2 GB for 64 bit OS

O Hard disk space: 16 GB for 32-bit OS or 20 GB for 64-bit OS

1.13 Logical design (ERD)

Figure 1.1-3: Library management chart

ype rare)

type code

et type of book

.s tưng

Ss

^>~

<Ctetonang >> ally Ju

(as) ao (eum > days j

po

i

publisher f

ee )——] publisher borrow student

nar class À

ẹ address ie student is first

year ot

\ ublication

CO title » Csx c

Explanation

O For the system, Reasons ERD is suitable because:

- An ERD diagram represents the logical structure of the database by identifying entities,

characteristics and relationships

- This is because the system requires the development of a relational database ERD

diagrams used to link closed boards Statistics and data on student data

and books can be stored easily and quickly by the system ERD is a wonderful thing

chosen because it allows you to import and export data in a convenient and scientific way

O Explain ERD:

Firstly, we need to identify the primary and secondary keys of each table while designing an ERD diagram:

O Asmooth underline is the primary key

Os Foreign keys are not seamless, specified with underscores

Column Name

Type code (PK)

Type name

Column Name

Publisher code (PK)

Publication name

Address

Column Name

Book ID (PK)

Quantity

Title

Year of publication

Column Name

Student ID (PK)

Class

Student is first and last name

Column Name

Borrowed days (PK)

Borrowed date

Return date

Table 1.1-1: type of book Data type number string

Table 1.1-2: Publisher

Data type number string string

Table 1.1-3: Book

Data type number string string datetime Table 1.1-4: Student Data type number string string Table 1.1-5: Borrow Data type string datetime datetime

Length

50

Length

50

50

Length

50

50

Length

50

50

Length 50

together:

O Ina class that will have many different courses and different majors, this is a 1-n relationship

O Each major will have many subjects such as Program, network, web, and

database, this is a 1-n relationship

O Each student will have many learning outcomes from many different subjects, this is a 1-n relationship

O Each lecturer can only teach one subject and a certain course, this is a 1-to-

1 relationship

O Each major will have a specific program of study for that discipline, this is a 1- to-1 relationship

O Each course will have many different subjects for each course and each subject, this is an n-n relationship

1.1.5 Physical design

- Database materialization is a physical concept While the logical design may be independent of the final database platform, many physical database

features are dependent on the details and semantics of the DBMS target

O Implementing logical design in table definitions: pre-deployment design,

Os table definition, standardization, primary and foreign key relationships, and basic

Ol indexing

O Designing the physical data database after deployment Often performed by Othe database manager

% Typecode

Typename

Yearofpublication

Publishercode

Typecode

student

® Studentid

Class firstandlastname

Dihlich

r

® Publishercode Publicationname Address

Figure 1.4-4: Physical design

CRITICAL EVALUATION

After completing this assignment with my own efforts and with the help of my mentor During the learning process, he was very dedicated to teaching and always answered my questions With the knowledge that I have learned, I have presented very fully the questions that Assignment raised in brief, with clear and specific images Moreover, I am confident that I can self- study and can make the Database Design & Development process for business

In addition, I have mastered the basics of Database Design & Development, so I can

definitely create a large Database Design & Development to help many people connect with

each other and make life better!

CONCLUSION

After completing this report, I have understood and grasped the principles, analysis and specification of a Database Design & Development system and their operation Moreover, with Microsoft SQL Management System software, I can use it to design, and code a complete database

to be able to develop a website or application

I am now confident that I can select the necessary devices and build the development and database management workflows that are right for me

Database Design & Development is really great! Thanks to it, I understand how the devices around us work This is very interesting and wonderful Thankyou my mentor!

REFERENCES

[1] Fred R McFadden 01 January 1991, Database management

https://dl.acm.org/doi/abs/10.5555/102701 _

[2] docs.microsoft.com (2021) Aggregate Functions (Transact-SQL) [Online] Available at:

server-ver15 [Accessed 20 November 2021]

[3] Publication History, 01 January 2007, Relational database: a practical foundation for productivity

https://dl.acm.org/doi/abs/10.1145/1283920.1283937