Scribd
Upload
33 views

DB Report Example

Uploaded by

6531501183
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
33 views

DB Report Example

Uploaded by

6531501183
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 21

Student Assistance Management System

A Project Report Presented By


Miss Sutita Jaisungnern ID.5731301074
Miss Apatsanan Sranoi ID.5731301081
Mr. Khun Nount ID.5731301088

In Partial Fulfillment
Of Requirements for the Course
1501208 Database Management System

SCHOOL OF INFORMATION TECHNOLOGY


MAE FAH LUANG UNIVERSITY
2021

©COPYRIGHT BY MAE FAH LUANG UNIVERSITY


1

1. Project Scope
1.1 Background and Problem Definition

Student assistance management program in school of information technology in each


semester, professors will announce the number of student to assist their work. The role of
staff is to provide information for the students and then the students can register which
subjects they want to work by writing in the paper. Therefore, they must come to the office to
apply an assistant job. After that the staffs transfer papers into client base (Microsoft Excels)
to manage schedules of students who registered. Finally, staffs will inform the result to the
students.
Thus, we found the problems if the staffs do not stay in the office. Furthermore, the
students cannot check schedules and register by themselves and check the number of
available seats. In addition, the document form can be mistaken or lost easily. So, it takes
times to check and edit. Therefore, we got an idea to create this application. It is a web-based
application to solve the problems and manage students’ information to support staff and
students for Student assistant program.

1.2 Objectives

1.2.1 To create a web-based application student assistance system to manage student


information.
1.2.2 To support staff working effectively.
1.2.3 To check status of seat.
1.3 Expected Result

1.3.1 Reduce paper and convenient to search and manage information.


1.3.2 To summarize the result of student registration in each subject into PDF file and can
print out.
1.3.3 Can access to the system anytime and anywhere using internet.

1.4Scope

Type of System: Web-Based Application


There are two user’s roles who will use this system as the following:

1.4.1 The 1st user, administration role


1) Login and Logout
2) Add (add staff, subject information, schedule, lab room, students)
3) Edit (edit staff, subject information, schedule, lab room, students)
4) Delete(delete staff, subject information, schedule, lab room, students)
5) Search (update staff, subject information, schedule, lab room, students)
6) View (information)

1.4.2 The 2nd user, student role


1) Register
2) Login and Logout
3) Choose (choose subjects and schedule for work)
4) Delete (delete booking)
5) Edit (edit booking and profile)
6) View booking and schedule (view information)
7) Print document (print the summary details)
2. Data Flow Diagram
2.1 Context level

Fig
ure 3.1: Context level
2.2 DFD Level 0

Figure 3.2: Level 0


2.3 DFD Level 1 of register

Figure 3.3: Level 1 of register


Level 1 of log in

Figure 3.4: Level 1 of log in


Level 1 of add new admin

Figure 3.5: Level 1 of add new admin


Level 1 of add course

Figure 3.6: Level 1 of add course


Level 1 of selection course

Figure 3.7: Level 1 of selection course


Level 1 of approve course request

Figure 3.8: Level 1 of approve course request


Level 1 of display summary report
Figure 3.9: Level 1 of display summary report
3. Entity Relationship Diagram

Figure 3.0: Entity Relationship Diagram

This is ERD of this system, it have five entities. They are student, admin, course, student
and admin, and hire job.
- Student entity has student ID, student first name, student last name, gender, address,
phone number, email, GPAX, GPA, advisor, username and password.
- Admin entity has admin ID, admin first name, admin last name, address, phone number
and email.
- Course entity has course ID, course name, section, date, time, total hour, room, amount of
student, teacher and major.
- Student and Admin entity have student ID and admin ID.
- Hire job entity has student ID, course ID, course name, major, requirement, approved and
empty.
Student entity has relationship one-to-many with Hire job entity.
Student entity has relationship one-to-many with Student and Admin entity.
Admin entity has relationship one-to-many with Student and Admin entity.
Admin entity has relationship one-to-many with Hire job entity.
Admin entity has relationship one-to-many with Course entity.
Hire job entity has relationship one-to-many with Course entity.
4. Data dictionary
5. SQL
This section is the illustration of SQL using in this project
5.1 Creating table structure
CREATE TABLE `audit` (
`AUDIT_ID` int(4) NOT NULL,
`CUSTOMER_ID` varchar(4) NOT NULL,
`LOG_DATE` date NOT NULL,
`USED` decimal(18,2) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

CREATE TABLE `country` (


`COUNTRY_CODE` varchar(2) NOT NULL,
`COUNTRY_NAME` varchar(50) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

CREATE TABLE `customer` (


`CUSTOMER_ID` varchar(4) NOT NULL,
`NAME` varchar(50) NOT NULL,
`EMAIL` varchar(50) NOT NULL,
`COUNTRY_CODE` varchar(2) NOT NULL,
`BUDGET` decimal(18,2) NOT NULL,
`USED` decimal(18,2) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

5.2 SQL for inputs


5.2.1 Register page
INSERT INTO USERS VALUES (‘001’,’John,’Smith’,’1998-10-15’,’123432’,’02’)
5.2.2 Login Page
SELECT * from USERS where user=’001’ and password=’123432’;
5.2.3 Buying ticket page
INSERT into TICKETS VALUES (‘002’,’001’,’2023-10-24’,’T1’,’J11’)

5.3 SQL for outputs


5.3.1 Profile display page
SELECT * from USERS u, PROVINCE p where u.pid=p.pid;
5.3.2 After logging-in page
SELECT * from USERS where user=’001’ and password=’123432’;
5.3.3 Display ticket
SELECT * from ticket where USERS =’001’;

You might also like