The document describes a webpage mining service that provides information on the 12 faculties at UniSZA. The service displays faculty data on a single website for easy access without visiting each faculty site. It was developed using JSON format to integrate data from different faculty websites. The project objectives were to test the functionality of a searchable faculty information site, design a convenient user interface, and integrate faculty data. Methodologies included requirements analysis, design, testing, and a V-Model approach.

1. WEBPAGE MINING SERVICES
USING JSON
NAME : NAJAH FASIHAH BT MOHD ZAINUDDIN
MATRIC NO : 044445
COURSE : BACHELOR OF COMPUTER SCIENCE (SOFTWARE DEVELOPMENT)
SUPERVISOR : PROF DR. MOHD NORDIN BIN ABD RAHMAN

2. Introduction
The webpage mining service is a platform that
provides information about all the twelve faculties
available at UniSZA. It works as a web service that
displays all the information on one website.
Through this web site, users enable to find the
information related to the faculties faster and
easier without having to access the entire faculty
website.

3. Objectives
To test the functionality of a website that allows
user to search information about the faculties.
To design a website that can give convenience to
the user to minimize their time in finding the
information about the faculty at UniSZA.
To develop a website that can integrate
information from different faculty websites.

4. Scope
• A platform for the users to find information
about the faculties.
• Involves three users :
Super Admin Admin User

5. METHODOLOGY

6. V-model

7. Verification phase
1. Requirements analysis
• Analyze the requirements of the system
• Describe the system’s functional, physical,
interface, performance, data, security
requirements
• The user acceptance tests are designed in this
phase.

8. 2. System Design
• Analyze and understand the business of the
proposed system
• Figure out possibilities and techniques
• Generate software specification document
• System testing are prepared in this phase.

9. 3. Architecture Design(high-level design)
• Realize all which typically consists of
the list of modules
• The integration testing design is carried
out in this phase.

10. 4. Module Design (low level design)
• Designed system is broken up into smaller
units or modules
• contain a detailed functional logic of the
module, in pseudocode

11. Validation phase
1. Unit testing
• Developed during module design phase.
• To eliminate bugs at code level or unit level.
• The smallest entity which can independently
exist
• Verifies that the smallest entity can function
correctly when isolated from the rest of the
codes/units.

12. 2. Integration testing
• Developed during the Architectural Design
Phase.
• Verify that units created and tested
independently can coexist and communicate
among themselves.
• Test results are shared with customer's team.

13. 3. System testing
• Develop during system design phase.
• Composed by client's business team.
• Ensures that the expectations of the develop
application are met.
• Verifies that the functional and non-functional

14. 4. User acceptance testing
• Developed during the requirements analysis
phase.
• Composed by business users.
• Performed in a user environment that resembles
the production environment, using realistic data.
• Verifies that delivered system meets user's
requirement and ready for use in real time.

15. System Requirement
1. Hardware Requirement
• Acer’s Laptop
• Pendrive
• Printer

16. 2. Software Requirement
• Eclipse
• Xampp
• MySQL
• Dropbox
• Google Chrome
• Microsoft Word
• Microsoft Power Point

17. SYSTEM DESIGN

18. Framework
JSON
FORMAT

19. JSON Technique
JSON is a lightweight data-interchange format
which is human readable and easy for computers
to parse and use. JSON is known as JavaScript
Object Notation that represent simple data
structures. JSON is used for serializing and
transmitting the data over a network connection
that link between the server and the web
application.

20. Comprising between MYSQL and JSON
0
Time
MYSQL
JSON
Data

21. Context Diagram

22. Data Flow Diagram(DFD)

23. D
F
D
L
E
V
E
L
0

24. DFD level 1(manage admin)

25. DFD Level 1 (manage faculty)

26. Entity Relationship Diagram(ERD)

28. Database Table
1. Super Admin
Column Type Null Default Comments
S_adminID Varchar(20)PK No
adminID Varchar(20)FK No
name Varchar(100) No
password Varchar(20) No

29. 2. Admin
Column Type Null Default Comments
adminID Varchar(20)PK No
S_adminID Varchar(20)FK No
facultyID Varchar(20)FK No
name Varchar(100) No
password Varchar(20) No
email Varchar(50) No
datetime datetime No

30. 3.Faculty
Column Type Null Default Comments
facultyID Varchar(20)PK No
adminID Varchar(20) FK No
F_name Varchar(100) No
F_links Varchar(100) No
noTel Varchar(12) No
fax Varchar(12) No
campus Varchar(100) No