information technology assignment 1 unit database design development

Use an appropriate design tool to design a relational database system for a substantial problemLO1...21.1 Design a relational database system using appropriate design tools and technique

BTEC FPT INTERNATIONAL COLLEGE

INFORMATION TECHNOLOGY

ASSIGNMENT 1

UNIT: DATABASE DESIGN & DEVELOPMENT

STUDENT: PHAM PHU LOC CLASS: IT05102

STUDENT ID: BD00053

SUPERVISOR: VO DUC HOANG

Da Nang, October 2022

ASSIGNMENT 1 FRONT SHEET

Unit number and title Unit: Database Design & Development

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

submission)

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:

❒Summative Feedbacks: ❒Resubmission Feedbacks:

Internal Verifier’s Comments:

Signature & Date:

TABLE OF CONTENT

INSTRUCTOR/ SUPERVISOR/ ASSESSOR .i

REVIEWERS iv

TABLE OF CONTENT ix

LIST OF TABLES AND FIGURES xi

LIST OF ACRONYM xii

INTRODUCTION 1

CHAPTER 1: DESIGN DATABASE 2

1 Use an appropriate design tool to design a relational database system for a substantial problem (LO1) 2

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) … 2 1.1.1The scenario of the chosen system 2

1.1.2System Requirement Specification (SRS) 3

1.1.3Logical design (ERD) 4

1.1.4Explanation 5

1.1.5Physical design 6

CRITICAL EVALUATION 15

CONCLUSION 16

LIST OF TABLES AND FIGURES

Figure 1.1-1: FPT school 2

Figure 1.1-2: Student Management System 3

Figure 1.1-3: Entity Relationship Diagram 4

Figure 1.4-4: Physical design 7

Figure 1.2-1: Login - Student Management System 7

Figure 1.2-2: Home - Student Management System 7

Figure 1.2-3: List - Student Management System 8

Figure 1.3-1: User and system requirements 14

Table 1.1-1: Major 5

Table 1.1-2: Course 5

Table 1.1-3: Student 5

Table 1.1-4: Study Program 5

Table 1.1-5: Student 5

Table 1.1-6: Result 6

Table 1.1-7: Lecturer 6

Table 1.1-8: Class 6

Table 1.2-1: Major Data 8

Table 1.2-2: Course Data 8

Table 1.2-3: Student Data 9

Table 1.2-4: Study Program Data 9

Table 1.2-5: Study Program Data 9

Table 1.2-6: Result Data 10

Table 1.2-7: Result Data 10

Table 1.2-8: Class Data 10

Table 1.2-9: Unnormalized Example 11

Table 1.2-10: First normal form (1NF) Example 12

Table 1.2-11: Second normal form (2NF) Example 12

Table 1.2-12: Second normal form (2NF) Example 13

Table 1.2-13: Third normal form (3NF) Example 13

Table 1.2-14: Third normal form (3NF) Example 14

LIST OF THE ACRONYM

INTRODUCTION

First of all, I would like to thank my mentor Vo Duc Hoang for his constant 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 Loc 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)

CHAPTER 1: DESIGN DATABASE

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)

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:

Work with FPT to learn about existing system needs

Analysis needs and makes unambiguous user and system requirements statements Conceive a relational database system utilizing design tools and processes Develop a completely working relation database system based on the system design

- 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 “Student 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)

- The creation of the FPT relationship database and division into clear and accurate tabulations can solve all of the difficulties listed above:

+ Major: Each Major has a major identity,

the main name, and the foundation year

+ Courses: every course has a course

management code, the year beginning, and the

year ending

+ Student: Every student has a student

identity and belongs to a certain class identity

(identified by ClassID)

+ Program: Each program has a managing

code and a name for the program

subject: Each subject has a management code

and belongs to a certain discipline (identified by

major) Figure 1.1-2: Student Management System

+ Subject: Each subject has a management code and belongs to a certain discipline

(identified by MajorID)

+Result: Each result of the exam records a student who took the test for a specific topic

during a certain test period (The student can take more than once a specific topic)

+ Lecturer: Each line in this table indicates a subject taught in a particular discipline within a

certain program In this program, that subject is specified with a specific number of theoretical and practical periods and equivalent to how many credits (The number of credits includes both theoretical and practical credits)

+ Class: A class that has a class code to manage, belongs to a certain industry and is open to

a certain course, in a certain program The ordinal numbers are numbered in ascending order for classes of the same course, major, and program

study programs, classes, lectures, Along with that is the data retrieval at the request of users

This system has high security to avoid data loss,

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

Nice and easy to use external interface

The system stores data history for users to easily check and review

- Non-functional requirements:

There are no problems and the system operates stably 24/7 and high performance For instance, re-response time is within 1-2 seconds as well as throughput The system also have a scalability

It also contains many data and is quite reliable

Stable resilience and maintenance and excellent interoperability

- System requirements:

The system runs on Windows 7, Windows 8, Windows 10, Windows 11 (Preferred Windows 10)

Processor: Processor clocked at 1 gigahertz (GHz) or higher, or SoC

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

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

Figure 1.1-3: Entity Relationship Diagram

For the system, Reasons ERD is suitable because:

- The relations of entities recorded in the database is shown in an Entity Relationship Diagram (ERD) An entity is an object, a data component in this context A collection of related entities is a set of entities They may have characteristics that identify their characteristics

- The ER diagram shows the logical structure of databases by defining the entities, their characteristics and displaying their relations

- Because the system requires a relational database to be designed The tables are tightly connected according to the ERD graph The system may simply and conveniently provide statistics

on student data, and topics Easily and scientifically import and export data, thus ERD is a good choice

an ERD diagram:

A smooth underline is the primary key

Foreign keys are not seamless, specified with underscores

Table 1.1-1: tblStudent

Field name Description Type Length

Table 1.1-2: tblCourse

Field Name Description Type Length

Table 1.1-3: tblStaf

Field Name Description Type Length

Table 1.1-4: tblStaf_Department

Field Name Description Type Length

Table 1.1-5: tblProject_Transaction

Field Name Description Type Length

Table 1.1-6: tblStudent_Registration

Field Name Description Type Length

Registration Date Date

Table 1.1-7: TblStudent_Reports

Field Name Description Type Length

transaction_reports

(FK)

Transaction Record Int 11

- Next, we need to define 1-n, 1-1, n-n relationships to be able to connect the tables together:

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

Each major will have many subjects such as Program, network, web, and database, this is a 1-n relationship

Each student will have many learning outcomes from many different subjects, this

is a 1-n relationship

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

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

Each course will have many different subjects for each course and each subject, this

is an n-n relationship

1.1.5 Physical design

- The materialization of a database in an actual system is a physics-based concept Although logical design may be done regardless of the ultimate data base platform, many physical database features are reliant on the details and semanticity of the DBMS target

+ Conversion of the logical design in table definitions: pre-deployment designs, table definitions, standardization, primary and external key relations, fundamental indexing

+ Physical data database design after deployment, frequently carried out by a

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

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

REFERENCES