+ All Categories
Home > Documents > FACULTY : INFORMATICS AND COMPUTING...buku teks (SPBT). Kemudian, kakitangan sekolah SPBT mesti...

FACULTY : INFORMATICS AND COMPUTING...buku teks (SPBT). Kemudian, kakitangan sekolah SPBT mesti...

Date post: 28-Jan-2021
Category:
Upload: others
View: 5 times
Download: 0 times
Share this document with a friend
52
FACULTY : INFORMATICS AND COMPUTING CODE/COURSE NAME : CSF 35104/FINAL YEAR PROJECT I PROGRAM : BACHELOR OF COMPUTER SCIENCE SOFTWARE DEVELOPMENT SEMESTER / SESISION : 5 (2018/2019) NAME : NUR FARAH AZLIN BINTI TUSRI MATRIC NO : BTAL 16044773 SUPERVISOR’S NAME : DR WAN SURYANI BINTI WAN AWANG PROJECT TITLE : TEXTBOOK LOAN (SPBT) MANAGEMENT SYSTEM
Transcript
  • FACULTY : INFORMATICS AND COMPUTING

    CODE/COURSE NAME : CSF 35104/FINAL YEAR PROJECT I

    PROGRAM : BACHELOR OF COMPUTER SCIENCE SOFTWARE

    DEVELOPMENT

    SEMESTER / SESISION : 5 (2018/2019)

    NAME : NUR FARAH AZLIN BINTI TUSRI

    MATRIC NO : BTAL 16044773

    SUPERVISOR’S NAME : DR WAN SURYANI BINTI WAN AWANG

    PROJECT TITLE : TEXTBOOK LOAN (SPBT) MANAGEMENT SYSTEM

  • ABSTRACT

    This study was conducted at Sekolah Menengah Kebangsaan (SMK) Tembila, Besut,

    Terangganu. This study aims to identify the problem when the textbook loan at the school is

    still using manually. It becomes harder and takes time for the SPBT staff to key-in the data of

    the students that borrows the textbooks (SPBT). Then, the staff SPBT school must check the

    quantity of textbooks whether adequate or not. Sometimes the textbooks are damage or

    missing then the textbook supervisor cannot know who was student that borrows. However,

    this system can help staff SPBT to record all the students and textbook information without

    using manually. It can reduce their burden to check the quantity of textbook if it still

    available, damage or missing. It can create a systematic and efficient SPBT management

    based on ICT and establish a system that can assist in the monitoring and coordination of

    SPBT management. In realizing this solution, intelligent support system will be proposed by

    the student.

  • ABSTRAK

    Kajian ini dijalankan di Sekolah Menengah Kebangsaan (SMK) Tembila, Besut,

    Terengganu. Kajian ini bertujuan untuk mengenalpasti masalah ketika pinjaman buku

    pelajaran di sekolah masih menggunakan secara manual. Ia menjadi lebih sukar dan

    memerlukan masa untuk kakitangan SPBT memasukkan data-data pelajar yang meminjam

    buku teks (SPBT). Kemudian, kakitangan sekolah SPBT mesti memeriksa kuantiti buku teks

    sama ada mencukupi atau tidak. Kebiasaannya buku teks rosak atau hilang maka penyelia

    buku teks tidak dapat mengetahui siapa pelajar yang meminjam. Walau bagaimanapun,

    sistem ini dapat membantu kakitangan SPBT untuk menyimpan semua maklumat pelajar dan

    buku teks tanpa menggunakan secara manual. Ia dapat mengurangkan beban mereka untuk

    memeriksa kuantiti buku teks jika masih ada, kerosakan atau hilang. Ia boleh mewujudkan

    pengurusan SPBT yang sistematik dan cekap berdasarkan ICT dan mewujudkan satu sistem

    yang boleh membantu dalam pemantauan dan penyelarasan pengurusan SPBT. Dalam

    merealisasikan penyelesaian ini, sistem sokongan pintar akan dicadangkan oleh pelajar.

  • TABLE OF CONTENTS

    Contents Pages

    ABSTRACT………………………………………………………………………………ii

    ABSTRAK………………………………………………………………………………..iii

    TABLE OF CONTENTS…………………………………………………………………iv

    CHAPTER I……………………………………………………………………………....1

    INTRODUCTION………………………………………………………………..1

    1.1 Background…………………………………………………………....1

    1.2 Problem Statement…………………………………………………….2

    1.3 Objectives…………………………………………………………..…3

    1.4 Scope……………………………………………………….…………3

    1.5 Limitation of Works………………………………………………….4

    CHAPTER II…………………………………………………………………………….5

    LITERATURE REVIEW…………………………………………….…………5

    2.1 Introduction……………………………………………………..……5

    2.2 Research………………………………………………………...……6

    2.3 Research Technique…………………………………………….….…14

    2.4 Chapter Summary…………………………………………...……..…14

    CHAPTER III…………………………………………………………………….….….15

    METHODOLOGY………………………………………..……………………..15

    3.1 Introduction……………………………………………..…………….15

  • 3.2 Project Methodology…………………………..…………….……...15

    3.2.1 Planning Phase……………...…………………..17

    3.2.2 Requirement Analysis Phase……………….….17

    3.2.3 Design Phase……………………………….……17

    3.2.4 Implementation Phase………..…………………18

    3.2.5 Testing Phase……………………………………18

    3.2.6 Deployment phase………………………………18

    3.3 System Requirement………….……………………….……………19

    3.3.1 Software Requirement……….…………….……19

    3.3.2 Hardware Requirement………….………………20

    3.4 Framework……………………………….…………………………..21

    3.5 Context Diagram……………………………………………………..22

    3.6 DFD Level 0……………………………………………………..……23

    3.7 DFD Level 1……………………………………………………..……26

    3.7.1 Manage User………………………………..…….26

    3.7.2 Manage Student…………………….…………….28

    3.7.3 Manage Book……………………………..………29

    3.7.4 Manage Supplier……………………………….…30

    3.7.5 Manage Order…………………………..…...……31

    3.8 Entity Relation Diagram………………………………………....……32

    3.9 Database Design…………………………………………..……..……34

    3.10 Data Dictionary………………………...…………………....……35

    3.10.1 Table Admin……………..………..…………….…35

    3.10.2 Table Buku…………………………………….…..36

    3.10.3 Table Form………………...……………..…..……37

  • 3.10.4 Table Guru Kelas………………….……….....……37

    3.10.5 Table Kelas……………………..…………...……38

    3.10.6 Table Pelajar………………………….……..……38

    3.10.7 Table Pelajar Buku……………………..…..……39

    3.10.8 Table Pembekal………………………………..…40

    3.10.9 Table Pembekal Buku…….………………..……41

    3.10.10Table Staff SPBT………..…………..…………...42

    3.10.11Table Status…………………..…………......…...43

    REFERENCES………………………………………………………………………....44

    APPENDIX A: GANTT CHART………………………………………………….....45

  • CHAPTER I

    INTRODUCTION

    1.1 Background

    The Textbook Loan Scheme Program (SPBT) was first implemented in 1975. SPBT is a

    textbook loan program for eligible students in all government schools and government aid

    schools. The SPBT program was originally intended to alleviate the financial burden incurred

    by poor parents or guardians and ensure that pupils from underserved families do not drop

    out of their schooling. However, beginning 2008, the Malaysian government has provided

    textbooks loans to all students who attend school at government schools regardless of their

    family's financial status. Hence, this situation makes the responsibility of the SPBT unit be

    more weighted to ensure that each book is processed and distributed to all students at SMK

    Tembila.

    Based on my observation and interview from En Adanan Bin Mohd Zin, the SPBT

    coordinator teacher at SMK Tembila, there was a problem when that school was still using

    manually to get and fill the information of students who had borrowed textbooks. Mostly,

    staff of SPBT will provide logbooks for students and students will write the details of the

    textbooks they have borrowed. To avoid that situation, we have come out with a system that

    offers a management for the textbook supervisors to manage the textbook without using

    manually. This proposed system will help the textbook supervisors to standardize the

    management and implementation of SPBT in SMK Tembila throughout the direction of

    excellence and commitment of administrators and teachers in the management and

    implementation of SPBT. This project is useful to save user’s time in management of SPBT

    with only simple click of a mouse.

  • Textbook Loan (SPBT) Management System is able to problems such as time

    constraints and reduced workload. This system will use Intelligent Decision Support

    System Technique because it provides the simplest and most understandable way of

    expressing knowledge.

    As for the conclusion, Textbook Loan (SPBT) Management System will be a good

    solution in solving real life problems and makes the user life easier and simpler.

    1.2 Problem Statement

    There are some problems faced by the staff SPBT who intended to manage the

    textbook. Firstly, it becomes harder and takes time for the staff SPBT to key-in the data of

    the students that borrows the textbooks because the staff SPBT works only 8 hours, so

    they do not have enough time to record all information of student that borrowed textbook

    so it will take a few days to complete key-in all the information data of students. Next, the

    staff SPBT must check the quantity of textbooks whether adequate or not. The staff SPBT

    must know how much total textbook in each subject, so they do not have to count and

    check each of the subject textbook whether adequate or not. Lastly, sometimes the

    textbook are damage or missing the then staff SPBT cannot know who was student that

    borrows. It because sometimes the student do not returning of textbook or textbook was

    damage, so the staff SPBT did not know student who responsible to textbook.

  • 1.3 Objectives

    The objectives of Textbook Loan (SBPT) Management System are:

    i. To design a system for staff SPBT manage the data information of student who

    borrowed the textbook

    ii. To develop and implement an intelligent support system to evaluate the textbook

    when accessing this system

    iii. To evaluate the performance and usefulness of an intelligent decision support

    system based on textbook information

    1.4 Scopes

    There are main actors which are the staff SPBT and admin

    1.4.1 Scopes of the User

    i) Admin

    Able to log in as admin

    Able to manage profile and update details or password

    Able to view all the report

    Able to manage security and maintenance of the system

    ii) Staff SPBT

    Able to register and log into management system

    Able to update profile and change password

    Able to manage details of textbooks, supplier and student

    Able to generates and view reports

  • 1.5 Limitation of Works

    This system only can access by admin and the staff SPBT who work at SMK Tembila.

    This system will only manage distribution textbook to the student that had borrowed.

  • CHAPTER II

    LITERATURE REVIEW

    2.1 Introduction

    This chapter will continue with the discussion and the idea from previous research. In

    general, literature review refers to survey books, scholarly articles, and any other sources

    relevant to a particular issue, area of research or theory and by so doing, provides a

    description, summary and critical evaluation of these works in relation to the research

    problem being investigated. This literature review contains the general description of the

    existing system and making comparison between existing systems.

  • 2.2 Research

    No. Author/Year Research Name System Description Methodology

    1. Haoyuan Li,

    Doctor of

    Philosophy in

    Computer

    Science

    University of

    California,

    Berkeley

    Professor Ion

    Stoica, Co-chair

    Professor Scott

    Shenker, Co-

    chair / 2018

    Alluxio: A Virtual

    Distributed File

    System

    -This dissertation proposes

    an architecture to have a

    Virtual Distributed File

    System (VDFS) as a new

    layer between the compute

    layer and the storage layer.

    -A scalable distributed file

    system performance

    evaluation framework to

    help researchers and

    developers better design

    and implement systems in

    the Alluxio ecosystem.

    VDFS called Alluxio

    (formerly Tachyon).

    2. Sajjad Ahmad

    and Slobodan

    P.Simonovic,

    Department of

    Civil,

    Architectural,

    and

    Environmental

    An Intelligent

    Decision Support

    System for

    Management of

    Floods

    The DSS is able to assist in:

    selecting suitable flood

    damage reduction options

    (using an expert system

    approach); forecasting

    floods(using artificial neural

    networks

    approach);modelling the

    Intelligent Decision

    Support System

  • Engineering,

    University of

    Miami, Coral

    Gables, FL

    33146-0630,

    U.S.A.;

    2Department of

    Civil and

    Environmental

    Engineering,

    University of

    Western

    Ontario,

    London, ON,

    N6A 5B9,

    Canada / 2006

    operation of flood control

    structures; and describing

    the impacts (area flooded

    and damage) of floods in

    time and space

    3. Michael

    Zohourian,

    Prescott Valley,

    Arizona / 2015

    Supply Chain

    Decision Making

    Under Demand

    Uncertainty and

    the Use of Control

    Systems: A

    Correlational

    Study

    To investigate the extent to

    which SCM control

    mechanisms predict

    optimized inventory

    levels (OPT) and reduced

    bullwhip effect (BWE)

    based on the perceptions of

    supply

    Model predictive

    control-based

    inventory

    optimization (MPC),

    internal

    model control-based

    inventory

    optimization (IMC),

  • chain (SC) senior-level

    managers of medium-size

    and large manufacturing

    firms in the

    United States

    postponement (POS),

    and

    collaboration (COL)

    4. Chih-Chin

    Liang,

    Department of

    BusinessAdmini

    stration,

    National

    Formosa

    University,

    No.64, Wunhua

    Rd., Huwei

    Township,

    Yunlin County

    632, Taiwan /

    2013

    Smart Inventory

    Management

    System of Food-

    Processing-and

    Distribution

    Industry

    Inventory management is

    therefore important to the

    food-processing-and-

    distribution industry

    because of the large amount

    of products typically stored.

    Large amounts of stored

    products increase inventory

    cost and management cost

    and can reduce warehouse

    efficiency.

    AHP analysis

  • 5. Mbam B.C.E.

    and Igboji,

    Kingsley O.

    Department Of

    Computer

    Science , Ebonyi

    State University

    – Abakaliki /

    2013

    Enhancing

    Cooperative Loan

    Scheme Through

    Automated Loan

    Management

    System.

    An automated system

    therefore, is a system

    designed to take in data and

    process it using a

    predefined format, thereby

    generating the expected

    result.

    Loan management system is

    being designed to automate

    the back office activities of

    financial institutions

    offering different types of

    loans.

    The Object Modeling

    Technique (OMT)

    Table 2.1 Comparison between the research

  • 1) Alluxio: A Virtual Distributed File System

    In the research paper, the system that is being developed is known as “Alluxio: A

    Virtual Distributed File System.” The aspects refer the amount of data that are

    generating, collecting, storing, managing, and analyzing is growing exponentially. To

    store and process these data has exposed tremendous challenges and opportunities. This

    increasing complexity in the stack creates challenges in multi-fold. Data is siloed in

    various storage systems, making it difficult for users and applications to find and access

    the data efficiently. this dissertation proposes an architecture to have a Virtual Distributed

    File System (VDFS) as a new layer between the compute layer and the storage layer.

    Alluxio presents asset of disparate data stores as a single file system, greatly reducing the

    complexity of storage APIs, and semantics exposed to applications. Alluxio is designed

    with a memory centric architecture, enabling applications to leverage memory speed I/O

    by simply using Alluxio.

    2) An Intelligent Decision Support System for Management of Floods

    In the research paper, the system that is being developed is known as ‘’An Intelligent

    Decision Support System for Management of Floods’’. This conceptual paper discusses an

    Intelligent Decision Support System (DSS) is developed to assist decision makers during

    different phases of flood management. The DSS is developed as a virtual planning tool and

    can address both engineering and non-engineering issues related to flood management.

    Different models (hydrodynamic, forecasting, and economic) that are part of the DSS share

    data and communicate with each other by providing feedback. The decision support

    environment allows a number of “what-if” type questions to be asked and answered, thus,

    multiple decisions can be tried without having to deal with the real life consequences.

  • 3) Supply Chain Decision Making Under Demand Uncertainty and the Use of

    Control Systems: A Correlational Study

    In the research paper, the system that is being developed is known as “Supply Chain

    Decision Making Under Demand Uncertainty and the Use of Control Systems: A

    Correlational Study”. In this research paper, the extent to which SCM control mechanisms

    predict optimized inventory levels and reduced the bullwhip effect based on the perceptions

    of SC senior level managers of medium-size and large manufacturing firms in the United

    States was investigated. Thus, it provided a means to identify the special needs of different

    manufacturing industry firms in coping with demand uncertainty and the bullwhip effect, so

    that manufacturing industry leaders may select appropriate control mechanisms. A multiple

    regression analysis was used to determine the relative contribution of each control

    mechanism to SCM performance by considering both the individual and collective approach

    on each of the four control mechanisms. Therefore, a SCM capable of responding to customer

    demand uncertainty effectively and efficiently, based on any combination of control

    mechanisms, is highly desirable.

  • 4) Smart Inventory Management System of Food-Processing-and Distribution

    Industry

    In the research paper, the system that is being developed is known as “Smart Inventory

    Management System of Food-Processing-and Distribution Industry”. This conceptual paper

    discusses the large amounts of stored products increase inventory cost and management cost

    and can reduce warehouse efficiency. Restated, inventory management should be the primary

    focus of the food-processing-and-distribution industry, especially for perishable foods. This

    study is therefore important to build up a system to predict possible forthcoming inventory.

    This study surveyed experts to identify key issues associated with inventory management in

    the food-processing-and distribution industry, and analyzed sequential patterns to find rules

    based on analytical results from the survey. This study also proposed a model for inventory

    prediction. Through AHP method, the factors could be found through surveying experts. The

    survey results could be applied to sequential-pattern analysis to predict the forthcoming

    materials in an inventory.

  • 5) Enhancing Cooperative Loan Scheme Through Automated Loan Management

    System.

    In the research paper, the system that is being developed is known as “Enhancing

    Cooperative Loan Scheme Through Automated Loan Management System”. This research

    paper, it involves utilization of computing or electronic devices to undertake the tasks that are

    being handled by people. It is a pertinent factor in a profitable and soundly run financial

    institution. Financial transactions through manual system of operation are prone to errors and

    unimagined complexities, making it so difficult a task maintaining all entries of users

    account, search records of activities, handle loan deduction errors and generate reports. The

    system essentially manages both short-term and long-term loans, and keeps track of cash

    inflow and outflow of a cooperative society among others. It utilized SQL Server database

    architecture at the back end and Visual Basic.Net framework at the front end. This makes it

    user-friendly and highly interactive. The Object Modelling Technique (OMT) is adopted for

    the analysis and design of the Loan Software. A pragmatic system bundles with several

    competent capabilities to eliminate data inconsistency and redundancy as well as ensuring

    data integrity and security, with guaranteed fast retrieval response time.

  • 2.3 Research Technique

    An IEDSS is an intelligent information system that reduces the time in which

    decisions are made in an environmental domain, and improves the consistency and quality of

    those decisions. ADSS is a computer system that assists decision makers in choosing between

    alternative beliefs or actions by applying knowledge about the decision domain to arrive at

    recommendations for the various options. It incorporates an explicit decision procedure based

    on a set of theoretical principles that justify the “rationality” of this procedure.

    2.4 Chapter Summary

    In this chapter, technique to be used is studied and few collection of literature review

    has been done. By this, knowledge have been gain to help to develop a good and functioning

    system. By literature review also helps to gain knowledge about techniques and past systems

    that has been used in previous research. In the phase, we will know that Intelligent Decision

    Support System is the best practice way to be implemented in Textbook Loan (SPBT)

    Management System. An intelligent decision support system by gathering and analysing

    evidence, identifying and diagnosing problems, proposing possible courses of action and

    evaluating such as proposed actions. The aim of the AI techniques embedded in an intelligent

    support system is to enable these tasks to be performed by a computer, while emulating

    human capabilities as closely as possible.

  • CHAPTER III

    METHODOLOGY

    3.1 Introduction

    In this chapter, it will be discussed about the methodology that used to develop this

    system. Hence, the System Development Life Cycle (SDLC) will be used which its

    Interactive and Incremental Model that is used for step in SPBT Loan Management System.

    It will explain more details of each phase involve in this project development based on the

    system requirements.

    3.2 Project Methodology

    Iterative and Incremental Process Model has been chosen as a methodology to

    develop this application in order to achieve the objectives of the project to solve the problem

    in managing textbook among the supervisor textbook. The phases of this methodology are

    Planning, System Analysis and Requirement, System Design, Implementation, Testing and

    Deployment. The project will be started with an initial planning and ended with deployment

    phase.

  • Figure 3.1 Iterative and Incremental Development Model

    This model is chose because it is a method of software development that begins with

    planning and continues through iterative development cycles involving user requirement and

    incremental addition of features concluding with the deployment of completed system at the

    end of each cycle. Hence, if the system is having some error, the developer able to fix the

    error with this cyclic model based on the allocated time given.

    Requirement

    Analysis

    Design

    Implementation

    Testing

  • 3.2.1 Planning Phase

    The requirement will be planned to complete the project based on the time givens.

    The phase started with brainstorming of any ideas with the supervisor in which the abstract of

    the project that contained title, problem, technique and the solution of the project problem.

    The proposed title that has been approved by the faculty was a management system called

    SPBT Loan Management System.

    3.2.2 Requirement Analysis Phase

    In this phase, the detailed of introduction has been decided in which project title,

    problem statement, objectives and scope of project. The survey of daily expenses among the

    students and employee generally were conducted for better understanding of the proposed

    system to be developed rather than the current or existing system. The objectives of this

    project have been determined after the survey is done. The requirements are discovered in

    order to build the better system to the user.

    3.2.3. Design Phase

    The required design was developed based on the requirement that has been analysed

    from the Requirement Analysis Phase previously. The certain diagrams such as Context

    Diagram (CD), Entity Relational Diagram (ERD), Data Flow Diagram (DFD) Level 0 and

    Framework were built as a guideline while developing this system. Then, the interface of this

    application will be sketched roughly, for example Mock Up.

  • 3.2.4 Implementation Phase

    In this phase, SPBT Management System is implemented into the coding based on the

    sub-module of the system requirements. This project is developed using PHP, Notepad and

    Xampp will be used as a local host server.

    3.2.5 Testing Phase

    Once the coding is implemented, the module is tested through unit testing to test the

    single part of the module in this application. In order to ensure the process of the system can

    be worked correctly, testing needs to be done. If the system is having some errors, the error

    must be fixed and testing the system again so that the first version of this system can be

    released.

    3.2.6 Deployment Phase

    The users are able to try this application after it has been released. Then, from user

    requirement or review, the developer will be know if this application has met the objectives

    of SPBT Management System that stated in Introduction of this project.

  • 3.3 System Requirement

    The stated requirements below required in order to develop this system properly such

    as software and hardware requirement.

    3.3.1 Software Requirement

    1. Microsoft Word 2010

    Software for writing project and report of project

    2. Dropbox

    Tool for cloud storage of back up data

    3. Jing

    Tool for screen shot the image to be used in this report

    4. Xampp Control Panel v3.2.1

    Tool for open source of web server

    5. Notepad++

    Tool for develop PHP

    6. PHP

    Language used to develop the system

    7. Google Chrome

    Used to do research on the project and to run the project

    8. Lucid Chart Diagram Software

    Used to draw CD and DFD model

  • 3.3.2 Hardware Requirement

    1. Laptop

    The laptop used was Lenovo 100-14IBD with Intel(R) Core(TM) i3-5005U CPU @

    2.00GHz 2.00 GHz. 6.00 GB RAM, 64-bit operating system, x64-based processor and

    Edition Windows 10 Home Single Language

    2. Pendrive

    The Pendrive user Data Traveler USB 32GB

    3. Printer

    The printer used was Epson L-210 to print out several documents such as proposal

    and report of project.

  • 3.4 Framework

    Figure 3.2 Framework for Textbook Loan (SPBT) Management System

    Framework is basically a board overview or outline of interlinked items which supports a

    particular approach to a specific objectives, and serves as a guide that can be modified as

    required by adding or deleting items.

  • 3.5 Context Diagram

    Figure 3.3 Context Diagram for Textbook Loan (SPBT) Management System

    Description:

    Based on the figure 3.4 above, there are three actors in this Textbook Loan (SPBT)

    Management System which are ADMIN, STAFF SBPT and SUPPLIER. The context

    diagram above display the flow between three actors and what are they involved in system

    based on their roles. Staff SBPT is able to insert their own details during registration and

    login. They have to insert student detail, book details and supplier details. Then, they can

    generate all the report detail by the system. Other than that, Supplier will take order detail

    from the staff SPBT and then payment detail will display after payment have pay.

    Meanwhile, Admin will be able to manage their profile and view all the report that system

    will display and also user’s information.

  • 3.6 DFD Level 0

    Figure 3.4 DFD Level 0 for Textbook Loan (SPBT) Management System

  • Description:

    The DFD has three entries which are ADMIN, STAFF SPBT and SUPPLIER. There are six

    processes involved in the system which are MANAGE USER, MANAGE STUDENT,

    MANAGE BOOK, MANAGE SUPPLIER, MANAGE ORDER, and GENERATE REPORT.

    There are six data stores created in the system which are STAFF RECORD, ADMIN

    RECORD, STUDENT RECORD, BOOK RECORD, SUPPLIER RECORD, and ORDER

    RECORD. The flow of the system is like below.

    1. STAFF SPBT input STAFF DETAILS into MANAGE USER process which outputs

    STAFF DETAILS into STAFF data store.

    2. STAFF SPBT input STUDENT DETAILS into MANAGE STUDENT process which

    outputs STUDENT DETAILS into STUDENT data store.

    3. STAFF SPBT input BOOK DETAILS into MANAGE BOOK process which outputs

    BOOK DETAILS into BOOK data store.

    4. STAFF SPBT input SUPPLIER DETAILS into MANAGE SUPPLIER process which

    outputs SUPPLIER DETAILS into SUPPLIER data store.

    5. ADMIN input ADMIN DETAILS into MANAGE USER process which outputs

    ADMIN DETAILS into ADMIN data store.

    6. SUPPLIER input SUPPLIER DETAILS into MANAGE ORDER process which

    outputs ORDER DETAILS into ORDER data store.

    7. When STAFF SPBT wants to view reports, STAFF INFO, ADMIN INFO,

    STUDENT INFO, BOOK INFO, SUPPLIER INFO, and ORDER INFO are taken

    from STAFF, ADMIN, STUDENT, BOOK, SUPPLIER and ORDER RECORDS

    data stores respectively into REPORT process which outputs REPORT to STAFF.

  • 8. When ADMIN wants to view reports, STAFF INFO, ADMIN INFO, STUDENT

    INFO, BOOK INFO, SUPPLIER INFO, and ORDER INFO are taken from STAFF,

    ADMIN, STUDENT, BOOK, SUPPLIER and ORDER RECORDS data stores

    respectively into REPORT process which outputs REPORT to ADMIN.

  • 3.7 DFD LEVEL 1

    3.7.1 Manage User

    3.7.1.1 Manage User (for staff)

    Figure 3.5 DFD Level 1 for Manage User (for staff)

    Description:

    1. STAFF SPBT input STAFF DETAILS into REGISTER process which output STAFF

    DETAILS into STAFF data store

    2. STAFF SPBT input STAFF DETAILS into LOGIN process which output STAFF

    DETAILS into STAFF data store

    3. STAFF SPBT input STAFF DETAILS into UPDATE PROFILE process which

    STAFF DETAILS into STAFF data store

  • 3.7.1.2 Manage User (for admin)

    Figure 3.6 DFD Level 1 for Manage User (for admin)

    Description:

    1. ADMIN input ADMIN DETAILS into LOGIN process which output ADMIN

    DETAILS into ADMIN data store.

    2. ADMIN input ADMIN DETAILS into UPDATE PROFILE process output ADMIN

    DETAILS into ADMIN data store.

  • 3.7.2 Manage Student

    Figure 3.7 DFD Level 1 for Manage Student (for staff)

    Description:

    1. STAFF SPBT input STUDENT DETAILS into ADD STUDENT process which

    output STUDENT DETAILS into STUDENT data store.

    2. STAFF SPBT input STUDENT DETAILS into UPDATE STUDENT process which

    output STUDENT DETAILS into STUDENT data store.

    3. STAFF SPBT input STUDENT DETAILS into DELETE STUDENT process which

    output STUDENT DETAILS into STUDENT data store.

  • 3.7.3 Manage Book

    Figure 3.8 DFD Level 1 for Manage Book (for staff)

    Description:

    1. STAFF SPBT input BOOK DETAILS into ADD BOOK process which output BOOK

    DETAILS into BOOK data store.

    2. STAFF SPBT input BOOK DETAILS into UPDATE BOOK process which output

    BOOK DETAILS into BOOK data store.

    3. STAFF SPBT input BOOK DETAILS into DELETE BOOK process which output

    BOOK DETAILS into BOOK data store.

  • 3.7.4 Manage Supplier

    Figure 3.9 DFD Level 1 for Manage Supplier (for staff)

    Description:

    1. STAFF SPBT input SUPPLIER DETAILS into ADD SUPPLIER process which

    output SUPPLIER DETAILS into SUPPLIER data store.

    2. STAFF SPBT input SUPPLIER DETAILS into UPDATE SUPPLIER process which

    output SUPPLIER DETAILS into SUPPLIER data store.

    3. STAFF SPBT input SUPPLIER DETAILS into DELETE SUPPLIER process which

    output SUPPLIER DETAILS into SUPPLIER data store.

  • 3.7.5 Manage Order

    Figure 3.10 DFD Level 1 for Manage Order (for supplier)

    Description:

    1. SUPPLIER input ORDER DETAILS into VIEW ORDER process which output

    ORDER DETAILS into ORDER data store.

    2. SUPPLIER input ORDER DETAILS into UPDATE ORDER process which output

    ORDER DETAILS into ORDER data store.

  • 3.8 Entity Relational Diagram

    Figure 3.11 ERD for Textbook Loan (SPBT) Management System

  • An entity relational diagram (ERD), also known as an entity relational model, is a

    graphical representation of an information system that shows the relationship among

    people, objects, places, concepts or events within that system.

  • 3.9 Database Design

    Database is a structured set of data held in a computer, especially one that is

    accessible in various ways. So basically, database is needed to hold all the data needed in

    the system.

    Figure 3.12 Table in Textbook Loan (SPBT) Management System Database

    There are eleven tables in database which are Admin, Buku, Form, Guru Kelas, Kelas,

    Pelajar, Pelajar Buku, Pembekal, Pembekal Buku, Staff SPBT and Status. For each table,

    there are attributes at every column.

  • 3.10 Data Dictionary

    3.10.1 Table Admin

    NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

    1 AdminID Represents the

    unique id

    VARCHAR 12 PRIMARY

    KEY

    2 NamaAdmin The attribute for

    admin’s name

    VARCHAR 100 -

    3 Password The attribute for

    admin’s password

    VARCHAR 12 -

    Table 3.10.1: Table Admin

  • 3.10.2 Table Buku

    NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

    1 NoSiriBuku Represents the

    unique id

    VARCHAR 12 PRIMARY

    KEY

    2 NamaBuku The name of the

    book

    VARCHAR 100 -

    3 HargaBuku Represents of the

    price of the book

    VARCHAR 20 -

    4 Penerbit The name of the

    publisher book

    VARCHAR 120 -

    5 BilanganBuku The quantity of

    the book

    INT 11 -

    Table 3.10.2: Table Buku

  • 3.10.3 Table Form

    NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

    1 FormID Represents the

    unique id

    VARCHAR 12 PRIMARY

    KEY

    2 JumlahBuku Represents of the

    total of the book

    that every form

    must have

    INT 11 -

    Table 3.10.3: Table Form

    3.10.4 Table Guru Kelas

    NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

    1 ICNoGuru Represents the

    unique id

    VARCHAR 12 PRIMARY

    KEY

    2 NamaGuru Represents the

    name of the

    teacher

    VARCHAR 100 -

    3 KelasID Represents the

    Kelas ID who

    teacher manage

    student

    VARCHAR 12 FOREIGN

    KEY

    Table 3.10.4: Table Guru Kelas

  • 3.10.5 Table Kelas

    NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

    1 KelasID Represents the

    unique id

    VARCHAR 12 PRIMARY

    KEY

    2 NamaKelas The name of the

    class

    VARCHAR 100 -

    Table 3.10.5: Table Kelas

    3.10.6 Table Pelajar

    NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

    1 ICNumber Represents the

    unique id

    VARCHAR 12 PRIMARY

    KEY

    2 NamaPelajar Represents the

    student’s name

    VARCHAR 100 -

    3 NoPhone Represents the

    student’s phone

    number

    VARCHAR 12 -

    4 Email Represents the

    student’s email

    VARCHAR 20 -

    5 Alamat Represents the

    student’s address

    VARCHAR 11 -

    Table 3.10.6: Table Pelajar

  • 3.10.7 Table Pelajar Buku

    NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

    1 FormID Represents the

    Form ID that

    following form

    VARCHAR 12 PRIMARY

    KEY

    2 ICNumber Represents the IC

    Number that

    student had

    borrow

    VARCHAR 12 FOREIGN

    KEY

    3 NoSiriBuku Represents the

    No Siri Book that

    had student

    borrow

    VARCHAR 12 FOREIGN

    KEY

    4 DateOfBorrow Represents the

    date of borrow

    book

    VARCHAR 20 -

    5 DateOfReturn Represents the

    date of return

    book

    VARCHAR 20 -

    6 StatusID Represents the

    status of return

    book

    VARCHAR 12 FOREIGN

    KEY

    Table 3.10.7: Table Pelajar Buku

  • 3.10.8 Table Pembekal

    NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

    1 PembekalID Represents the

    unique id

    VARCHAR 12 PRIMARY

    KEY

    2 NamaPembekal The name of the

    supplier

    VARCHAR 100 -

    3 NoPhone Represents of the

    supplier’s phone

    number

    VARCHAR 12 -

    4 Email Represents of the

    supplier’s email

    VARCHAR 20 -

    5 Alamat Represents of the

    supplier’s

    address

    VARCHAR 120 -

    6 Penerbitan Represents of the

    supplier’s

    publishing

    VARCHAR 100 -

    Table 3.10.8: Table Pembekal

  • 3.10.9 Table Pembekal Buku

    NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

    1 NoSiriBuku Represents the

    No Siri Book

    that supply by

    the supplier

    VARCHAR 12 PRIMARY

    KEY

    2 PembekalID Represents the

    supplier ID who

    supply the book

    VARCHAR 12 FOREIGN

    KEY

    3 NoInvoice Represents of the

    invoice of the

    supplier

    VARCHAR 20 -

    4 JumlahBayaran Represents of the

    amount of the

    book that have

    paid

    VARCHAR 20 -

    5 Tarikh Represents of the

    date of the

    invoice

    VARCHAR 20 -

    Table 3.10.9: Table Pembekal Buku

  • 3.10.10 Table Staff SPBT

    NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

    1 StaffID Represents the

    unique id

    VARCHAR 12 PRIMARY

    KEY

    2 NamaStaff The attribute for

    staff’s name

    VARCHAR 100 -

    3 NoPhone Represents the

    staff’s phone

    number

    VARCHAR 12 -

    4 Email Represents the

    staff’s email

    VARCHAR 100 -

    5 Alamat Represents the

    staff’s address

    VARCHAR 100 -

    6 Password The attribute for

    staff’s password

    VARCHAR 12 -

    Table 3.10.10: Table Staff SPBT

  • 3.10.11 Table Status

    NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

    1 StatusID Represents the

    unique id

    VARCHAR 12 PRIMARY

    KEY

    2 DescriptionStatus The description

    status

    ‘BORROW’,

    ‘RETURN’,

    ‘PENDING’ or

    ‘LOST’ of the

    book

    VARCHAR 100 -

    3 DateBorrowed Represents of

    date of borrow

    the book

    DATE - -

    4 DateReturned Represents of

    date of return the

    book

    DATE - -

    Table 3.10.11: Table Status

  • REFERENCES

    1. Haoyuan Li, Doctor of Philosophy in Computer Science University of California,

    Berkeley Professor Ion Stoica, Co-chair Professor Scott Shenker, Co-chair / 2018,

    Alluxio: A Virtual Distributed File System

    2. Sajjad Ahmad and Slobodan P.Simonovic, Department of Civil, Architectural, and

    Environmental Engineering, University of Miami, Coral Gables, FL 33146-0630,

    U.S.A.; 2Department of Civil and Environmental Engineering, University of Western

    Ontario, London, ON, N6A 5B9, Canada / 2006, An Intelligent Decision Support

    System for Management of Floods

    3. Michael Zohourian, Prescott Valley, Arizona / 2015, Supply Chain Decision Making

    Under Demand Uncertainty and the Use of Control Systems: A Correlational Study

    4. Chih-Chin Liang, Department of BusinessAdministration, National Formosa

    University, No.64, Wunhua Rd., Huwei Township, Yunlin County 632, Taiwan /

    2013, Smart Inventory Management System of Food-Processing-and Distribution

    Industry

    5. Mbam B.C.E. and Igboji, Kingsley O. Department Of Computer Science , Ebonyi

    State University – Abakaliki / 2013, Enhancing Cooperative Loan Scheme Through

    Automated Loan Management System.

  • APPENDIX A: GANTT CHART

    Task Name Week

    2

    Week 3 Week 4-

    5

    Week 5-

    6

    Week 7 Week 8-

    10

    Week 11-

    12

    Week 13-

    14

    Initial Phase

    Coordinator

    Briefing

    Topic

    Discussion

    Topic

    Register

    Planning

    Phase

    Gather

    Information

    Proposal

    Writing

    Proposal

    Progress

    Presentation

    and

    Evaluation

    Correction

    Proposal and

    System

    Methodology

    Requirement

    Phase

    Determine

    System

    Requirement

    Analysis

    Existing

    System

    Progress

    Proposal

    Analysis and

    Design

    Design

    Context

    Diagram

    Design Entity

    Relational

    Diagram

    Design Data

    Flow

    Diagram

    Design

    Framework


Recommended