SYAD Group Assignment

Module Code AAPP007-4-2-SYAD
Module Name SYSTEM ANALYSIS AND DESIGN

Intake Code UCDF2107ICT(SE)
Lecturer Name DR. KESAVA PILLAI A/L RAJADORAI @ RAJOO
Hand In Date 10/2/2023
Group Leader SHE JUN YUAN
STUDENT NAME STUDENT TP

GATLEEN KAUR A/P MADAN SINGH TP065173
LAW MEI JUN TP065265
PAN ZHIN HUEY TP065263
PHUAH KUANG YI TP065448
SHE JUN YUAN TP065157
TAN BINGSHEN TP065389
UCDF2107ICT(SE) System Analysis and Design Assignment AAPP007-4-2-SYAD
Table of Contents
1.0 Introduction .......................................................................................................................... 4
1.1 About the company .......................................................................................................... 4
1.2 Business Process .............................................................................................................. 4
1.3 Overview of Proposed System ......................................................................................... 6
1.4 Project Objective .............................................................................................................. 7
2.0 Problem and Proposed Solution ........................................................................................... 8
2.1 Problem Background ........................................................................................................ 8
2.2 Problem Statement ........................................................................................................... 8
2.3 List of Issues..................................................................................................................... 9
2.5 Objective of Proposed System ....................................................................................... 11
2.6 Scope of Proposed System ............................................................................................. 13
3.0 Project Planning ................................................................................................................. 14
3.1 System Development Life Cycle.................................................................................... 14
3.1.1 Planning Phase ......................................................................................................... 14
3.1.2 Analysis Phase ......................................................................................................... 16
3.1.3 Design Phase............................................................................................................ 18
3.1.4 Implementation Phase.............................................................................................. 20
3.1.5 Maintenance Phase .................................................................................................. 22
3.2 Gantt Chart ..................................................................................................................... 24
3.3 Workload Metrix ............................................................................................................ 25
4.0 Feasibility Study ................................................................................................................ 27
4.1 Operational Feasibility ................................................................................................... 27
4.2 Technical feasibility ....................................................................................................... 30
4.3 Economic Feasibility ...................................................................................................... 31
4.4 Schedule Feasibility ....................................................................................................... 35
5.0 System Analysis ................................................................................................................. 36
1
5.1 Functional Requirements................................................................................................ 36
5.2 Non-Functional Requirements ....................................................................................... 37
6.0 Design Diagram ................................................................................................................. 40
6.1 Context Diagram ............................................................................................................ 40
6.2 DFD Level 0 ................................................................................................................... 41
7.0 Interface Design ................................................................................................................. 42
7.1Wireframe and WIX Design ........................................................................................... 42
7.1.1 Customer Profile ...................................................................................................... 42
7.1.2 Home Page ............................................................................................................... 46
7.1.3 Book Page ................................................................................................................ 48
7.1.4 Product Page ............................................................................................................ 50
7.1.5 Checkout Page. ........................................................................................................ 51
7.1.6 Payment Method ...................................................................................................... 52
7.1.7 In-house Reading Booking Calendar ....................................................................... 53
7.1.8 Order Tracking ........................................................................................................ 54
7.1.9 Membership Plan Page ............................................................................................ 55
7.1.10 Form....................................................................................................................... 56
7.1.11 Staff View Panel .................................................................................................... 59
7.1.12 Staff Add Panel ...................................................................................................... 61
7.2 GUI Principles and Concepts ......................................................................................... 65
7.2.1 Consistency.............................................................................................................. 65
7.2.2 Simplicity................................................................................................................. 66
7.2.3 Attractiveness .......................................................................................................... 66
7.2.4 Accuracy .................................................................................................................. 68
7.2.5 Effectiveness ............................................................................................................ 68
8.0 Conclusion ......................................................................................................................... 71
9.0 Individual Component ....................................................................................................... 72
2
9.1 Gatleen Kaur A/P Madan Singh TP065173 ................................................................... 72
9.1.1 Requirement Gathering: Questionnaire ................................................................... 72
9.1.2 DFD Level 1 and Data Dictionary of 6.0 Generate Report ..................................... 77
9.2 Law Mei Jun TP065265 ................................................................................................. 82
9.2.1 Requirement Gathering: Sampling .............................................................................. 82
9.2.2 DFD Level 1 and data dictionary for 9.0 Generate Token ...................................... 86
9.3 Pan Zhin Huey TP065263 .............................................................................................. 89
9.3.1 Requirements Gathering: Interview......................................................................... 89
9.3.2 DFD Level 1 and data dictionary of 2.0 Manage In-house Reading ....................... 93
9.4 Phuah Kuang Yi TP065448............................................................................................ 98
9.4.1 Requirements Gathering: Research ......................................................................... 98
9.4.2 DFD Level 1 and data dictionary of 8.0 Generate Receipt ................................... 101
9.5 She Jun Yuan TP065157 .............................................................................................. 106
9.5.1 Requirement Gathering: Observation .................................................................... 106
9.5.2 DFD Level 1 and data dictionary of 3.0 Manage Order ...................................... 109
9.6 Tan Bingshen TP065389 .............................................................................................. 114
9.6.1 Requiremenet Gathering: Document Review ........................................................ 114
9.6.2 DFD Level 1 and data dictionary of 1.0 Manage Rental ...................................... 116
10.0Reference ........................................................................................................................ 121
3
1.0 Introduction
1.1 About the company
The largest bookstore in Malaysia, Bookworm Paradise (BWP), was founded in
February 2018 and is home to a vast selection of books from various generations and genres.
The bookstore, which is proud to offer the necessary materials sought by the numerous
customers who enter their "paradise" each day and is located at the centre of Kuala Lumpur,
takes delight in doing so.
With up to 800,000 square feet of retail space, it is regarded among Malaysians as one
of the country's largest bookstores. Three floors make up BWP, and each floor features book
racks filled with various reading materials organised into several categories. Additionally, the
cosy ambience in the bookshop allows consumers to relax and chill while reading books.
BWP offers a wide selection of books. BWP specialises in buying and selling books,
whether novels, biographies, storybooks, academic journals, comics, or magazines. In addition,
they also offer gift-wrapping services. If customers desire to, they can also wrap gifts for them.
1.2 Business Process

i. Selling Process
Figure1: Selling Process

ii. Buying Process
4
Figure2: Buying Process
iii. Book Management Process
Figure3: Book Management Process
5
iv. Accounting Process
Figure4: Accounting Process
1.3 Overview of Proposed System

Currently, Bookworm Paradise (BWP) likes to increase its services, such as allowing
customers to rent the book from Bookworm Paradise, allow eBook viewing for customers and
open a new in-house service. Thus, a proposed system has been developed to let Bookworm
Paradise implement the new features. The system allows the staff of Bookworm Paradise to
add all the books, such as novels, storybooks and so on, with the price to let the customer know
the available books that Bookworm Paradise have. In this system, the customer can buy or rent
the book they like to read. Besides, customers can choose to read a part of the book before
purchasing or renting it because Bookworm Paradise has a new in-house reading service. This
system allows the customer to book the slot for in-house reading to avoid insufficient space
during that time slot. Before the customers make a booking for in-house reading, purchasing,
or renting the book, they must register as a member using this system. Lastly, this system also
allows the staff to update the discount for their services based on categories such as
membership type, book genres and so on.
6
1.4 Project Objective

1. To allow customers to view and buy books online.
This project allows Bookworm Paradise's customers to preview and purchase the
desired books online without going to the physical store. This system brings huge
convenience to the customer. Customers can save time by eliminating the travel time
to the physical store to purchase one book.
2. To increase the overall sales of the Bookworm Paradise bookstore

This project enables books from Bookworm Paradise to be sold online on the website.
This technology enables the bookshop to serve more clients from states distant from
Kuala Lumpur, such as Johor and East Malaysia or other countries. The online
bookstore allows customers to easily access the desired books and purchase at any
time instead of following the actual operating time of the physical store.
3. To provide the latest information to Bookworm Paradise's customers

This project offers the most recent information about the bookstore's current activities.
Discounts, events, and promotions organised by the bookstore are included on the
website. Furthermore, information about the books, such as genres and availability of
the selected books, will be shown on the website.
7
2.0 Problem and Proposed Solution

2.1 Problem Background
As the digital age rises, technology has become normalised for people. Every person
will at least have a smartphone to bring everywhere. Thus, the rise of technology gave birth to
E-books that had a huge impact on physical bookstores. Since the start of the pandemic of
Covid-19 from 2019, people from all walks of lives had to quarantine and lower the rate of
outdoor activity. Hence, it has gotten worse for the physical bookstore, which includes
Bookworm Paradise (BWP), as this can reduce the number of customers that visit the physical
bookstore. Consequently, it reduced the earnings of the Bookworm Paradise. Furthermore, the
cost-effectiveness of e-books can reduce the cost of producing a physical book, and it is
portable and can be read and viewed at any time with just a smartphone in hand. Therefore, e-
books bring a huge drop to the demand for physical books and cause the business of physical
bookstores to decrease drastically, making it hard to earn money. Therefore, Bookworm
Paradise has decided to be digitised by developing a system with various functions to ease the
bookstore's day-to-day operations and customers' buying and selling process.
2.2 Problem Statement

Based on the problem background, the problem identified from Bookworm Paradise is
the loss of income. Based on a market research report on the bookstore industry in the United
States, bookstores continue to face a downfall as their revenue has declined briskly over the
last decade. With the times constantly changing, competition from online e-commerce
platforms has become fierce, especially after the surge of COVID-19. This gave way to
opportunities such as online bookstores to bloom, leaving retail bookstores further threatened.
This causes Bookworm Paradise's revenue and income to keep decreasing monthly since they
do not have an online platform to open more services. Besides that, another problem that
Bookworm Paradise faces is the loss of data and information. Throughout so many years, there
is a possibility that the data and information will be lost. This is because Bookworm Paradise
uses a manual system to record all the important data, which will cause many issues, such as
inaccurate data due to the loss of data and information.
8
2.3 List of Issues

1. Lack of national and international markets.
Bookworm Paradise is currently providing services only to customers who visit their
physical store in Kuala Lumpur. Despite this, there may be customers from other parts
of Malaysia and around the world who are unable to visit the bookstore physically and
wish to buy books from the bookstore. Therefore, besides conquering the local city
market, BWP wishes to expand into the national and international markets for
customers worldwide to explore different services provided.
2. Lack of online purchasing or delivery service.
Bookworm Paradise is currently exclusively selling books to customers who visit the
physical bookstore only. However, customers nowadays are more likely to purchase
books online because online purchases are more convenient because they can view and
sort the books they want and purchase them with just a few clicks. The books will be
delivered directly to their house after placing an order. BWP does not provide such
services, which limits BWP's potential target market.
3. Lack of e-book reading and in-house reading services.
Customers typically buy books from bookstores based on recommendations. Customers

may be unable to choose the right books they want using this method. As a result, a
customer will want to read a portion of the book to see if they are interested or not,
either by online or in-house. However, BWP does not provide e-book reading or in-
house reading, which may discourage customers from purchasing a book they are
interested in.
4. Lack of book rental service.
Bookworm Paradise (BWP) main service is purchasing and selling all reading materials.
However, in the modern era, customers who are interested in a book these days are
more likely to rent the book rather than buy it because some customers do not want to
9
keep their books forever. Book rental services will boost customer retention and attract
new customers, but BWP does not currently offer this service.
5. Lack of platform for advertisements and notifications.
Bookworm Paradise (BWP) does not have a platform to display its extensive collections
of books and keep customers up to date on the latest publications, discounts, and events.
BWP only uses posters for advertising promotions and events, causing some customers
who do not visit the bookstore to miss out on purchasing books since there is no other
platform for the bookstore's advertisement.
6. The bookstore utilises a manual system, which leads to data entry errors.
Bookworm Paradise utilises a manual system to maintain transaction history, customer

information, and book information due to the computer illiteracy of BWP's staff. This
manual system needs staff to enter every piece of information manually. Hence, many
errors and inconsistencies in data entry have occurred in the bookstore, resulting in a
jumbled and unorganised record of data in the database.
7. Difficulty in generating and printing reports using a manual system.
The manager of Bookworm Paradise requires reports such as a list of books sold and
revenue earned to ensure that the bookstore's operations are on track. However, due to
inconsistency in data entry, the manager finds it difficult to generate and print these
reports using BWP's manual system. When the manager needs the reports, the staff must
manually examine the records and prepare the reports for him.
10
2.5 Objective of Proposed System

The proposed system should be able:
1. To allow people from all around the world to access it.
The proposed system allows Bookworm Paradise to have an online platform that every
country can access to buy books from this bookstore. This allows people from all around
the world to access the system and buy books. With this system, Bookworm Paradise
will be able to achieve international market expansion and will be able to become well-
known in other countries.
2. To provide the customer with a platform to purchase the book online.
The proposed system allows customer to buy their favourite book online. This is
because most customers are too lazy to go to the physical shop to purchase their
favourite book. This proposed system and a better delivery service allow the customer
to choose Bookworm Paradise as their first choice to buy their book online, which will
rapidly increase the sales of Bookworm Paradise.
3. To provide e-book viewing and in-house reading booking features for the
customer
The proposed system will have e-book viewing functionality, allowing the customer to
view a part of the book to let the customer decide whether they want to buy this book
or not. Besides that, this proposed system will also have a platform for the customer to
book an in-house reading for them to read before they decide to have their physical
copy of the book.
4. To allow the customer to rent books from Bookworm Paradise
The proposed system will have a functionality called book rental. The customer can
choose to rent the book from Bookworm Paradise instead of purchasing the book. This
is because some customers like to read the book but do not like to keep the physical
copy of the book.
11
5. To provide a platform for advertising, discount, or sales to the customer
Customers will not be able to receive news, advertisement and notification for the sales
or discounts of Bookworm Paradise without this system. However, with this proposed
system, the customer can keep updated about when the sales of Bookworm Paradise
and how much discount will be provided during these sales.
6. To have a database that holds all the records for Bookworm Paradise
This proposed system enables the staff of Bookworm Paradise to reduce insert data
manually in the system. This is because, with this system, most of the data will be auto-
generated by the system and stored in the database. The staff only need to key in some
necessary information such as book information, membership package and so on and
all data will also be stored in the database. Thus, this proposed system will effectively
reduce data record errors and inaccuracy of the data.
7. To generate receipts and reports easily within a short time.
This proposed system will auto-generate the receipt once the customer has made the
payment through the system. The staff does not need to generate a receipt by manually
writing it and delivering it to the customer. Besides that, the proposed system will also
have the functionality to let the owner generates all reports. These allow Bookworm
Paradise to easily generate the receipt and all types of reports.
12
2.6 Scope of Proposed System

Below are the scopes of the proposed system for Bookworm Paradise:
 The proposed system should allow people from all around the world to access it and
let them make their orders.
 The proposed system must have a search function to let the customer search the
availability of the book that they like to read in Bookworm Paradise
 The proposed system must have a clear category of books to let customers easily find
the book based on the categories such as novels, comics, magazines and so on.
 The proposed system should be able to be used in mobile applications.
 The proposed system must have its database to store all the data related to the
Bookworm Paradise business.
 The proposed system should have a shopping cart function to let customers view their
order.
 The proposed system must support QR payment, Debit/Credit card payment or Bank
transaction payment method.
 The proposed system should be able to support other banking or QR payment
applications which are not from Malaysia.
13
3.0 Project Planning

3.1 System Development Life Cycle
3.1.1 Planning Phase
The planning phase is the stepping stone for the creation of any product according to
the System Development Life Cycle (SDLC). It determines the need for an advanced system
to exist and help a business reach its strategic goals. This is acknowledged as a preliminary
plan as well as a feasibility study to allow a company's corporate efforts to gain the appropriate
resources to enhance their products and services (Innovative Architects, n.d.). The planning
phase will aid Bookworm Paradise in discovering the scope in order to help them to solve the
issue that they currently face.
The first step in the planning phase is to identify the problem statement. Problem
statements are used to portray a clear and concise interpretation of the issue that a project is set
to solve (Birt, 2022). The system analyst will identify the problem faced by the Bookworm
Paradise and list out the issues that have been found in Bookworm Paradise. The problem can
be identified by the system analyst through the interview with the manager of the Bookworm
Paradise.
To be done next in the planning phase would be identifying the objective of the project.
Project objectives are defined as what is intended to be achieved or the end goals of a particular
activity (Martins, 2020). These goals should be time-dependent, manageable and definite. The
system analyst needs to come up with the project objectives based on the issues that have been
faced by Bookworm Paradise in order to develop a system that solves these problems.
Furthermore, the project scope is important to be set. Project scopes are a unified
summary consisting of the major parameters of the whole project. Project scopes will help the
system analyst tremendously as it initiates project boundaries. System analysts are accountable
for documenting the project scope of Bookworm Paradise as it will be used during further
stages of the project, such as the systems analysis phase.
Later in the planning phase, system analysts are required to come up with project
schedules. This is aimed at leading the team and used as a measuring medium to evaluate
project execution and its progress (Talbert, 2022). Three types of tools that can be used for
project scheduling are known as Work Breakdown Structure (WBS), Gantt Chart, and the
(Program Evaluation Review Technique) PERT Chart. Gantt Chart is the most popular among
14
the project schedules. Gantt Charts are more useful when a project is in the works as they are
adjustable in the event changes are made to the scope (Hennigan & Bottorff, 2022). System
analysts in Bookworm Paradise are advised to use these mediums in their development team
to ensure the project is smooth-sailing with effective results.
Next, system analysts must conduct a feasibility study to examine the systems request
and advocate specific actions. This is carried out in order to find out the functionality of a
proposed system (Bridges, 2022). The study should be based on aspects such as technical,
economic, schedule and operational must be executed. Thus, the system analyst is required to
take this important step to determine the probability that a project will succeed.
A preliminary investigation report to the management will be the end product of the
planning phase. After that, the system analyst needs to get in touch with managers, IT staff and
target customers to present the project, clarify accountabilities, clear doubts and input feedback.
This is where the team of people come together to pivot on enhancements instead of issues.
15
3.1.2 Analysis Phase

The analysis phase is the second stage of the system development life cycle. In this
phase, the analysis of the Bookworm Paradise business requirement will be conducted. The
identified system functions that Bookworm Paradise plans to build are translated into the
project goals. A lot of activities will also be carried out during the analysis phases. All these
activities will be explained clearly in this report.
The first activity that will be conducted during the analysis phases is requirement
gathering. Requirement gathering is the most important part of this phase of the SDLC. There
are many types of requirements, but the most important requirement is user requirement, which
is the statement that describes the services that the system users can expect from the system
and the limitations that must be met for it to function. It includes functional requirements and
non-functional requirements. All these requirements can be gathered using fact-finding
techniques such as observation, interviews, questionnaires, etc. For example, in this phase, the
consultant will interview the owner of Bookworm Paradise to define the project's expectations,
including who will use the system, how they would use it, and the specific details of any unique
system requirements. (Ransom, 2013). The functional and non-functional requirements will be
gathered through the interview process.
After the requirement gathering, logical modelling is the next step in the analysis phases.
A data flow diagram can be created in logical modelling after gathering the required
information for developing the Bookworm Paradise system. A data flow diagram (DFD)
depicts how data flows through a system or process (What Is a Data Flow Diagram, 2022). It
uses predefined symbols to show data inputs, outputs, storage places, and routes between each
destination. Data flow diagrams can range from simple hand-drawn process overviews to multi-
level DFDs that go deeper into the data processing process. Data flow diagrams are classified
into three levels: context diagram (high-level view of the system), DFD Level 0 (low-level
view of the system), and DFD Level 1 (detailed low-level view of the system).
The third step in the analysis phase is logical data modelling. In logical data modelling,
the analyst will create a data dictionary to develop the system. The data dictionary in the
analysis is a reference book of data about data (metadata) that the system analyst constructed
to help them with analysis and design. The aims of using a data dictionary during the analysis
phases are to verify the data flow diagram for correctness and completeness and establish a
foundation from which to build the screens and the reports.
16
The fourth step in the analysis phase is conceptual data modelling. In conceptual data
modelling, the system analyst will create an entity-relationship diagram using Chen's notation
style for the Bookworm Paradise system. ERD is a type of flowchart that depicts the
relationships between "entities" inside a system, such as people, things, or concepts.
(LucidChart, 2017). The purpose of creating the ERD is to debug, troubleshoot and analyse
and gather the design requirements. To create the entity relationship diagram, the ERD must
have entities, attributes and cardinality of a relationship such as one-to-one, one-to-many and
many-to-many.
After completing all the steps listed above, the system analyst is required to create a
system requirements document. This document, also known as a system requirement
specification, is a bundle of paperwork describing the system's functionality and features. It
consists of several components that make an effort to characterise the functionality that
Bookworm Paradise owner needs to satisfy their customer (System Requirements Document -
Javatpoint, n.d.). All the requirements for developing the Bookworm Paradise system that has
been gathered will be recorded in this document. This system requirement document will then
pass to the design phase for designing the system according to the requirements listed in this
document.
17
3.1.3 Design Phase

During the SDLC design phase, the system will be designed in accordance with the
requirement specification document. This phase establishes the overall system architecture and
is critical for the system's implementation phase. Flowcharts, sketches, sitemaps, and
prototypes are designed during this phase to achieve the project's objective (Kovalenko, 2022).
The system design phase consists of three major steps: reviewing system requirements,
designing the system, and documenting the system design.
The initial stage in the design phase is to review the system requirements. To construct
a logical design, the system analyst will organise data into a set of logical relationships known
as attributes and entities according to the needs of Bookworm Paradise. The logical design
specifies the system's inputs, procedures, and outputs. When designing the logical design, the
system developer will specify the user requirements in detail by identifying the information
flow in and out of the system (TutorialsPoint, 2020). Examples of logical design include
context diagrams and data flow diagrams.
After reviewing the system requirements, the second step is to design the user interfaces,
database, input processes, input and output formats and reports, and system architecture. When
designing the user interface, the system developer should design the overall user interface,
including commands, screens, controls, and features that allow users to interact with the system
to complete a process, such as purchasing a book online for a customer (Badugu, 2018). The
user interface should be attractive, convenient, secure, and extensible while guaranteeing that
users can easily perform their tasks with the system. Furthermore, the system developer should
create a database for the system by creating an architecture design and a strategy for converting
database data. Database design steps include describing the needed functions, such as database
design and layout, as well as business rules (Halwai, 2021). This is to ensure that data in the
database can be organised, maintained, updated, deleted and so on.
Moreover, the system developers will design the system's input processes by
determining how data will be entered into the system. In this phase, the system analyst will
identify BWP's input device to create the input design. The input design is critical to ensuring
the data input's effectiveness, accuracy, and consistency. Source documents and forms are also
designed to reduce data entry errors. In addition, the input and output formats, as well as the
reports, are designed. The physical layout of each input and output screen, as well as printed
reports, will be defined in this step. The output, such as reports for BWP's manager and
18
customer receipts, should be easy to read and professional, including design elements such as
headers and footers, alignment, fonts, and spacing (Halwai, 2021).
Furthermore, the system analyst must design the system architecture to begin
developing the prototype of BWP's system. System architecture design entails specifying the
systems' processing strategies and methods, network configuration, and client-server
interaction (Martin, 2019). Following the system architecture, a prototype is constructed to
validate all the designs and assumptions. Prototyping enables users to evaluate and test systems
before they are implemented. It will also validate whether the system meets the requirements
of the client.
The documentation and presentation of the system design is the final step in the design
phase. In this step, a system design specification document is developed that specifies the exact
design requirements and characteristics of the proposed system (Holishevska, 2022). After that,
the proposed system design will be presented to the client for approval before the
implementation phase.
19
3.1.4 Implementation Phase

In addition, the following steps in the SDLC are the implementation phase.
Implementation is the last stage before the finished product of the software is published to the
clients. It is when the project team develops the actual product through several processes. The
processes involved in this stage are coding and testing the system (Study.com, 2022).
For the coding phase, programmers must adhere to the coding standards assigned in the
project. The customers may request that the system be coded in a certain programming
language. Every programmer must follow the coding standard to have a neat and consistent
look, improve the readability of the code, and have a standardised coding style throughout the
company. This ensures that future code maintenance, amending and copying can be done easily.
Additionally, programmers need to practise a good naming convention when naming a

variable. For instance, a variable should be in lowercase, with no abbreviations and named with
meaningful names to reveal the intention of the variable. Besides, the codes can be improvised
through a process called refactoring before testing the system. Refactoring helps to change the
coding structure into more simplified code without changing, adding, or removing the main
function or external interfaces.
Following the completion of the coding phase, testing begins. The main purpose of this
process is to identify the code's defects and ensure it properly functions to meet the client's
Bookworm Paradise requirements before delivering the system to the clients. There are two
ways to check the software: desk checking and group review of three to five IT experts.
Desk checking is where one person reviews the program code to identify logic errors.
Group review of three to five IT experts is mainly to identify errors in the code, implement
quality standards and ensure that the generated software satisfies the requirements of the client's
system design specification. The following process after checking the program code will be
testing the software. This process is guided by a test plan which uses the sample data prepared
by the software tester experts, and the results are recorded in a table. The program needs to go
through three types of testing: unit testing, integration testing and system testing.
The first type of test is unit testing. It is used to test an individual program or module
coded by each programmer involved in the project. Unit testing aims to identify the execution
errors that might cause the program to terminate abnormally and eliminate logic errors that
were missed during the desk checking. Next, integration testing is used to test two or more
programs that depend on each other to be functional (sanjoy, 2018). The objective of
20
integration testing is to reveal defects when two or more components or units are interacting
(JavaTpoint, 2021).
The third type of test is system testing. This testing helps to validate that all the
components of the system are integrated correctly. The components verified in this test are an
end-to-end testing scenario where the fully developed software and the external peripherals are
tested to check the interaction between the overall components and the system (Hamilton,
2022). This is also where the software's input is evaluated to ensure the desired output is
obtained.
21
3.1.5 Maintenance Phase

The last stage for SDLC is the most important after the system has been deployed,
which is the maintenance phase. The maintenance phase entails implementing any necessary
improvements, corrections, and changes to ensure that the system remains functional and is
kept up to date in order to meet system objectives. It is vital to update the system periodically
to let the Bookworm Paradise's users continue using it and adjust to the changing demands
(Imam, 2018). There are three activities in the maintenance phase: to support the system users,
maintain the system and make system changes and adjustments.
The first activity discussed during the maintenance phase is supporting the system users.
This is because when the new system is being deployed, most users will not be sure how to use
it, and many will ask for support. Thus, on-the-job training should be offered to the Bookworm
Paradise staff to support them in using the new system. This training is frequently used in a
live-work practice, simulated or training setting to let the user learn how to utilise specific tools
or equipment of the new system.
Besides, the second activity during SDLC's last phase is maintaining the system. Four
types of maintenance tasks are needed to carry out: corrective maintenance, preventive
maintenance, perfective maintenance, and adaptive maintenance. The maintenance team will
carry out the first type of maintenance task: corrective maintenance. The objective of carrying
out corrective maintenance is to return the system as soon as possible to the normal operation.
This maintenance will diagnose and fix all the logic errors in the operational system. When the
system is being fixed by using corrective maintenance, the maintenance team will start to
identify and investigate the issue and develop a lasting fix to prevent the same issue from
happening again.
Besides, the next type of maintenance that the maintenance team will be carried out is
adaptive maintenance. Adaptive maintenance will be used to update and modify the software
when the software of the system operates is changing because of technology, policies and so
on (MERRILL, 2019). The product must be able to connect with new hardware or software for
the clients, which is why adaptive maintenance should be used. For example, the maintenance
team will carry out adaptive maintenance before the Bookworm Paradise system is not
compatible with the new version of the web browser.
22
Furthermore, the maintenance team will also perform the perfective maintenance when
involved in making changes to an operational system to increase the Bookworm Paradise
system's effectiveness, dependability, and maintainability. When performing perfective
maintenance, it will help optimise the speed of Bookworm Paradise system, enhancing the user
interfaces, functionality, usability, and performance of the Bookworm Paradise system. The
last type of maintenance task that the IT department will perform is preventive maintenance.
Making the system change for preventive maintenance will stop faults from happening in the
future. This maintenance will improve the system's capacity to be maintained by bringing down
the complexity. The tasks that require the IT department to carry out during preventive
maintenance are document update, which updates the information to reflect the Bookworm
Paradise system's status, and code optimisation to speed up the program execution.
The last activities that need to be conducted are system changes and adjustments. Many
reasons will cause the system changes and adjustments. The one reason that will be discussed
is organisation changes (Sitesbay.com, n.d.). The need to modify the original system may arise
if there is any business-level change at the client end, such as a drop in organisation strength,
the acquisition of another company, or the organisation starting a new business. Thus, the
overall features and layout of Bookworm Paradise may have some changes due to different
organisations having different ideas for the system.
23
3.2 Gantt Chart
Figure5: Project Gantt Chart
24
3.3 Workload Metrix
Name Area of responsibility

SHE JUN YUAN  Overview of Proposed System
 Objective of Proposed System
 Scope of Proposed System
 Maintenance Phase
 Economic Feasibility Study
 DFD Level 1 Diagram
 Interface Design
 Conclusion
 Observation
 DFD Level 1 and data dictionary for
3.0 Manage Order
GATLEEN KAUR A/P MADAN SINGH  Logo
 Problem Statement
 Planning Phase
 Schedule Feasibility Study
 Questionnaire
6.0 Generate Report
LAW MEI JUN  Business Process
 List of Issue
 Design Phase
 Operational Feasibility Study
 Non-Functional Requirement
 Sampling
9.0 Generate Token
PAN ZHIN HUEY  Objective of the project
25
 Gantt Chart
 Implementation Phase
 Operational Feasibility Study
 Context Diagram
 Interview
3.0 Manage In House Reading
Booking
PHUAH KUANG YI  Introduction to Company
 Problem Background
 Analysis Phase
 Technical Feasibility Study
 Functional Requirement
 Research
 DFD level 1 and data dictionary for
8.0 Generate Receipt.
TAN BINGSHEN  Introduction to Company
 Document Review
 DFD level 1 and data dictionary for
1.0 Manage Rental
26
4.0 Feasibility Study

4.1 Operational Feasibility
Definition The operational feasibility of a proposed system is a measure of how well
it solves difficulties and emphasises on opportunities identified during
scope definition, as well as how well it fulfils the requirements defined
during the system development requirements analysis phase (Kumar,
2021).
Operational feasibility also examines the organisation's willingness to

support the proposed system. It is essential to evaluate the management's
commitment to the proposed project to establish this feasibility (Jena,
2020). The PIECES framework can assist in identifying operational issues
and their importance.
PIECES PIECES is a problem-solving framework that may be utilised to structure

Framework research on obstacles, requirements, and opportunities. It consists of a
checklist for detecting issues in an existing information system.
Performance The need to improve performance.

1. Does the current system provide sufficient throughput?
No, only five works can be done in every 2 minutes.
2. Does the current system have high response times to a transaction
or request?
No, the current system takes an average of 8 minutes to respond to
a request or transaction.
3. Does the current system delay between a transaction or a request?
Yes, the current system delays an average of 10 minutes between a
transaction or a request.
4. Does the proposed system provide higher efficiency in producing
the throughput?
Yes, the proposed system is five times faster than the current system
and produces three times more output as compared to the current
system.
27
Information The need to improve information.

1. Does the current system capture data easily and accurately?
No, the data is difficult to capture and contains errors as a manual
system is implemented.
2. Does the current system store data in a systematic and secure
manner?
No, the current system is stored in multiple files and is not secure
from cyber-attacks or accidents.
3. Does the current system provide timely, accurate and useful
formatted information to the end users and managers?
No, the information is not provided timely and accurately and is not
in a useful format due to the unorganised data of the manual system.
4. Does the proposed system organise data and information better than
the current system?
Yes, the proposed system will capture data easily and store data in
a database which will allow it to generate accurate and useful
information.
Economy The need to improve the economy and control cost or profit.
1. Does the current system provide cost-effectiveness to the business?
No, the current system does not have an online shopping feature,
which causes the business to lose a large number of potential
customers
2. Will there be an increase in benefits in the business with the current
system?
No, the current system only serves physical store customers where
orders of books are only limited to a certain number of customers.
3. Does the current system help in marketing the business?
No, the system does not have functions to advertise the business
online to reach out to more customers.
4. Is the proposed system more cost-effective compared to the older
system?
28
Yes, the proposed system saved approximately 25% of the

maintenance costs as the system has lesser problems to be resolved.
Control The need to improve security and control.

1. Does the current system provide sufficient control to protect against
crimes?
No, the current system has little control, which may cause crimes
such as fraud to be committed against the data.
2. Does the current system guarantee the security of data and
information?
No, the firewall of the current system is old and may not protect the
security of data and information.
3. Does the current system provide effective control to protect against
data breach?
No, the current system has weak control that allows all employees
access to the system, which may lead to data breach.
4. Does the proposed system provide better control and security
compared to the current system?
Yes, the proposed system is equipped with the latest firewall and
grants managers privileged access to domain services.
Efficiency The need to improve the efficiency of processes and people.

1. Does the current system maximise the available resources, such as
people, time and flow of forms?
No, the resources are not maximised because the generation of
reports wastes time.
2. Does the current system waste resources when performing tasks?
Yes, the effort and material required for tasks are excessive, which
causes a waste of resources.
3. Does the proposed system need many people to use and maintain
the system?
No, the system will only need a few people to maintain.
4. Is the proposed system more efficient than the current system in
terms of utilisation of resources?
29
Yes, the proposed system will maximise the available resources and
reduce the wastage of resources
Services The need to improve customer service, suppliers, employees, etc.

1. Is the current system easy to use by the employees?
No, the current system is not user-friendly as customers'
information is keyed in manually into the system.
2. Does the current system produce accurate results?
No, the current system may produce inaccurate results due to human
error when inputting customer information.
3. Is the current system compatible to work with other systems?
No, the current system is not compatible with online payment
systems.
4. Is the proposed system flexible to change?
Yes, the new system is open to new upgrades and additional features
to enhance the system.
Conclusion Therefore, the current system has more disadvantages than advantages for
the organisation. As a result, a new system is necessary for the organisation
to grow and expand into the international market.
4.2 Technical feasibility

Definition A technical feasibility study helps organisations determine if they have
the technical resources needed to transform an idea into a fully
operating system. It facilitates in project troubleshooting before the
beginning of work. The analysis identifies possible issues and suggests
solutions. It may serve as a flowchart for how goods and services evolve
before their introduction to the market, which is useful for long-term
planning.
Analysis 1. Can the system be developed using the company's current
technology?
Yes, most of the hardware and software required to develop the
proposed system have always been used by the company.
30
2. Is the suggested technology workable?

Yes, the suggested technology is workable, as most of the
online bookstore systems have the same technology as the
proposed solution.
3. Do we have enough necessary technical expertise to develop
the proposed system?
Yes, we have 2 designers for designing the prototype of the
system, 2 professional programmers to code and develop the
system, and 2 expert testers to test the system in order to keep
the system free from bugs before releasing.
4. Is the technology currently in use the best option for the
product team to expedite the development and stay under
budget?
Yes, it can save costs with this strategy.
Conclusion All in all, after conducting the technical feasibility study, we can know
that we are able to develop the proposed solution system for Bookworm
Paradise as we have enough technology, such as hardware and software,
as well as enough technical expertise to produce the online bookstore
system for Bookworm Paradise successfully.
4.3 Economic Feasibility

Definition An economic feasibility study is a form of cost-benefit analysis
that determines if a project can be executed. This phrase refers to
the evaluation and analysis of a project's potential to aid decision-
making by identifying its strengths, shortcomings, opportunities,
and risks, as well as the resources needed to complete the project
and an estimate of its probability of success (Krzewiska, 2019).
The goal of an economic feasibility study (EFS) is to demonstrate

the net benefit of a proposed project for receiving or disbursing
electronic cash or benefits, taking into account the benefits and
drawbacks for the agency, other state agencies, and the general
public.
31
Analysis 1. What is the estimated cost of developing the system for

Bookworm Paradise?
- The estimated cost for developing the system for Bookworm
Paradise is RM76,100.00.
2. Does the budget provided by Bookworm Paradise is enough for

developing the system?
- Yes, the owner of Bookworm Paradise has provided a total
budget of RM80,000, which is more than the estimated cost of the
project.
3. When does the Bookworm Paradise company able to gain profit

from this project?
- The estimated time that Bookworm Paradise company can get
profit is in the second year.
4. How much is the return on investment for this project?

- The return on investment for this project is 47.19%.
5. How much is the net present value of this project?

- The net present value of this project is RM72,748.00
6. Why the estimated annual benefits can be set around

RM65,000?
- The estimated annual benefits are set as RM65,000 because,
through this system, Bookworm Paradise's goods and services
will be easier to access by people from all around the world, which
cost the sales will increase rapidly. Besides, by using this system,
Bookworm Paradise can be able to reduce many costs, such as the
salary of workers, high maintenance fees and so on.
Conclusion In a nutshell, throughout this economic feasibility study, the
company is able to know the estimated cost for this budget and
32
the estimated time that the company can gain profit from this
Bookworm Paradise system.
Table: Estimate Development Costs
Expenses Amount (RM)

Development Team salaries 24,000.00
Consultant fees 200.00
Hardware and software 20,000.00
Installation 5,500.00
Data conversion costs 6,000.00
Total Development Cost 55,700.00
Table: Estimate Operational Cost

Maintenances 4,000.00
Licensing 500.00
Cloud storage fee 400.00
Operational team salaries 12,000.00
Training 3500.00
Total Operational Cost 20,400.00
Table: Estimate Total Cost of Project

Development Cost 55,700.00
Operational Cost 20,400.00
Total Operational Cost 76,100.00
33
Annual Operational Cost 20,400.00

Annual Benefit 65,000.00
System Life 4 years
Discount Factor 15%
Cost- Benefit Analysis Without Discount Factor
Cost-Benefit Analysis- Bookworm Paradise System

Cost Year
0 1 2 3 4
Operational Cost 20,400.00 20,400.00 20,400.00 20,400.00
Total Cost 55,700.00 76,100.00 96,500.00 116,900.00 137,300.00
Benefit 65,000.00 65,000.00 65,000.00 65,000.00
Total Benefit 65,000.00 130,000.00 195,000.00 260,000.00
Total Benefit - Total Cost -55,700.00 -11,100.00 33,500.00 78,100.00 122,700.00
Cost- Benefit Analysis with Discount Factor
Cost-Benefit Analysis- Bookworm Paradise System

Cost Year
0 1 2 3 4
Operational Cost 20,400.00 20,400.00 20,400.00 20,400.00
Discount Rate (15%) 1 0.87 0.78 0.66 0.57
Discount Cost 55,700.00 17,748.00 15,912.00 13,464.00 11,628.00
Total Cost 55,700.00 73,448.00 89,360.00 102,824.00 114,452.00
Benefit 65,000.00 65,000.00 65,000.00 65,000.00
Discount Rate (15%) 1 0.87 0.78 0.66 0.57
Discount Benefit 56,550.00 50,700.00 42,900.00 37,050.00
Total Benefit 56,550.00 107,250.00 150,150.00 187,200.00
Total Benefit - Total Cost -55,700.00 -16,898.00 17,890.00 47,326.00 72,748.00
34
4.4 Schedule Feasibility

Definition Schedule Feasibility helps the developers figure out better if the
project can be concluded within a certain period. The study is
carried out to prevent the project from exceeding its completion
deadline. The duration can be set by the corporation or the clients.
The corporation is at risk of losing its clients if the deadline is
disobeyed or not set properly. Furthermore, the company may face
a high turnover of employees. This feasibility allows analysts to
dictate the speed of the process. For instance, if the progress is
slow, the number of members in a team can be increased.
(StuTalks, 2021)
Analysis 1. How much time that the owner of Bookworm Paradise
allocates for developing the system?
The owner of Bookworm Paradise allocates 4 months for
us to develop the system.
2. How much time needs to be allocated to complete the
online bookstore system?
An estimated time to complete the online bookstore system
is around 3 months.
3. What happens if the project is not completed by the
deadline?
Let the client be aware of it and prepare a proper
explanation to explain why the project was delayed, but the
risk of losing the whole project is present.
4. How can employees be more aware of the deadline?
Set automated alerts on calendars to ensure they are
reminded of the tasks that need to be done.
5. What is the best way for employees to finish a project by
the deadline?
Creating a project schedule allows the team to see the
project in smaller and more intermediate tasks, allowing
them to tackle it quicker.
35
Conclusion In conclusion, schedule feasibility is very important to be applied

in the making of this new online bookstore system to ensure the
success of its production in each period of time.
5.0 System Analysis

5.1 Functional Requirements
Customer
1. The system allows customers to register and login as Bookworm Paradise member to
make orders.
2. Customers can make purchases or rental for books through this system.
3. Customers can make payments for any purchase and rental through this system.
4. Customers can receive a receipt after making the payment of their order.
5. The system will have history features for the customers to view their payment history,
order history and booking history.
6. The system allows customers to view all the books that Bookworm Paradise can
provide.
7. The system allows customers to add the book that the customer like to purchase or
rent to the shopping cart.
8. The system allows customers to book a time for in-house reading in Bookworm
Paradise.
9. The system allows customers to edit their profile, password, and account details.
10. The system allows customers to online viewing half of the book.
11. Customers can choose a membership package through the system.
12. The system lets the customer track the book delivery that Bookworm Paradise
prepared through the website.
Staff (Bookworm Paradise)
1. The system allows staff to login to the Bookworm Paradise accounts system to use all
the functions in the system.
36
2. The system lets the staff to generate receipts and tokens for the customer after the
purchase and rentals.
3. The system allows staff to make confirmation about the information of in-house
booking from the customers.
4. The staff can manage payment for the customer by using this system.
5. The staff can manage and update the membership package for the customer by using
this system.
6. The staff can manage and upload the discount for the customer by using this system.
7. The system allows staff to add new books into the system in order to increase the
variety of books.
8. The staff allow can generate sales reports by using this system.
5.2 Non-Functional Requirements
Non- Functional Description

Requirements
Performance ● The system will load within 3 seconds.

● The system can support up to 4,000 concurrent users.
● The system can handle 3,000 requests per second.
● The system responds to 97% of the user's requests in less
than 2 seconds.
Compatibility ● The system is compatible with iOS (minimum iOS 10)

and Android (minimum Android 11) for mobile phones
and tablets.
● The system is compatible with macOS (minimum MacOS
10), Windows (minimum Windows 10), and all Linux
operating systems for laptops and desktop computers.
● The system will only support if there is network
connectivity.
37
Usability ● The system should operate 99.5% of the time.

● The system's interface must be clean, user-friendly, and
easy to use.
● The layout and design of the system must be consistent.
● The system must have less than a 5% error rate when the
user submits payment information.
Reliability ● The system must be precise to 0.001% in the calculation.

● The system must perform without failure in 98% of use
cases.
● The system's probability of downtime must be less than
0.1% per 1000 hours.
● The system must be able to back up data when data is
added, deleted, or updated.
● The system's transaction failure must be lower than
0.005% of all transactions.
Security ● The system will be installed with a powerful firewall,

Cisco ASA, to safeguard all the data and prevent cyber-
attacks.
● PCI DSS compliance is required for the system's payment
processing gateway.
● The system will lock the account after 5 incorrect
passwords are inputted.
Maintainability ● The average time to restore the system from system

breakdown must be less than 10 minutes.
● The system must eliminate bugs within 5 minutes.
● The performance and functionality of the system must be
upgraded every month.
38
Availability ● The system must be able to be accessed by all users at all

hours and in all places.
● The system must be available 99.8% of the time every
month.
● The monthly downtime of the system must be less than 10
hours.
Table: Non-functional Requirements
39
6.0 Design Diagram

6.1 Context Diagram
A context diagram displays the interaction of an internal software system with external
elements. This is a high-level diagram that does not go into great depth on the system's internal
workings. This diagram, on the other hand, presents a comprehensible, concise, and transparent
design of the entire system. (What Is a Context Diagram and How Do You Use It?, 2022). Its
primary purpose is to help the system analyst comprehend the scope of the Bookworm Paradise
management system. The system analyst can then decide on the optimum strategy to develop
the system. According to the context diagram below, there are 3 external entities: staff,
customer, manager, and 10 data flow.
Figure 6: Context Diagram
40
6.2 DFD Level 0

Compared with the context diagram, DFD Level 0 diagram is more detailed because DFD
Level 0 diagram is a low-level view of the system. It separates the pieces of the Context
Diagram. By dissecting the Context Diagram's high-level process of the Bookworm Paradise
management system into 9 main processes, it highlights the primary tasks that the Bookworm
Paradise management system is responsible for performing. The 9 main processes are manage
rental, manage in-house booking, manage order, update book inventory file, update book sales
file, generate report, update book rental file, generate receipt and generate token. The DFD
Level 0 diagram for Bookworm Paradise management system can be viewed in the diagram
below.
Figure 7: DFD Level 0 Diagram
41
7.0 Interface Design

7.1Wireframe and WIX Design
7.1.1 Customer Profile
Figure 8: Wireframe for Customer Profile
The wireframe above is the design for the customer profile. In the customer profile, there are
5 pages, which are My Orders Page, My Addresses Page, My Booking Page, My History Page
and My Account. All these 5 pages have the same design, which is consistent based on the
wireframe above. My Order Page is used for the customer to check their order status and history.
My Addresses Page is a page for the customer to manage or add their addresses which act as
the location for delivery of the customer order. Besides, the My Booking Page allows
customers to check their in-house reading booking status and booking history. My History Page
is used for the customer to check their payment history for them to know about their transaction
during purchasing or renting the books. Lastly is the My Account Page. This page allows the
customer to edit their personal details if the customer wishes to update to the latest details.
42
Figure 9: My Orders Page
Figure 10: My Address Page
43
Figure 11: My Booking Page
Figure 12: My History Page
44
Figure 13: My Account Page
45
7.1.2 Home Page
Figure 14: Wireframe of Homepage
The diagram above is the design for the homepage. The homepage has been divided into 3
main sessions. The first session is an image slider, which the staff will update their latest
advertisement poster here. The second session is divided into 3 parts: Bestsellers books,
recommended books and the Bookworm Paradise Slogan. The customer can learn the best-
selling and recommended books through this session. The last session is the event session,
which lets the customer know what events are coming soon in Bookworm Paradise. This
homepage design is attractive, which will attract the user to continue using this system to
purchase books.
46
Figure 15: Homepage
47
7.1.3 Book Page
Figure 16: Wireframe of Book Page
According to the wireframe above, this design of the book page can allow the customer to
easily access and view it when they are looking for their interested book. The customer is able
to view the book title and the book price clearly by using this design. There is also a search bar
for the customer to search for their interested book. The design will be the same when the
customer filters the book based on the book's categories or the book's price.
48
Figure 17: Book Page
49
7.1.4 Product Page
Figure 18: Wireframe of the product page
According to the wireframe of the product page, all the details regarding the book will be shown
clearly on this page. The customer can read the specific book description and the policies set
by the Bookworm. The customer can view half of the book as this system has eBook viewing
features. The customer can select whether to rent or purchase the book, select the book quantity,
and choose whether to add to the cart or buy now.
50
Figure 19: Product Page
7.1.5 Checkout Page.
Figure 20: Wireframe Checkout Page
Figure above is the wireframe for checkout page. The design has separated the order item and
the order summary into two different parts which allow the customers to see clearly the book
51
that they have ordered and the total cost of their order. The customers can also enter the promote
code if they have to get discord for their order. Once the customers confirm the order, they can
checkout and proceed to payment page.
Figure 21: Checkout Page
7.1.6 Payment Method
Figure 21: Wireframe for payment method page
The figure above is the wireframe for the payment method page. The payment amount will be
shown clearly at the above of the page. The customer can clearly know the payment amount
they need to pay. The customer can select a different type of payment method based on the
payment availability of the system.
52
Figure 22: Payment Method Page
7.1.7 In-house Reading Booking Calendar
Figure 23: Wireframe of Booking Calendar
In the wireframe for booking calendar of in-house reading, it divides to left right two part. The
left side part is the booking calendar. The customers can select their prefer date and time for
the in-house reading. At the right-side part is the service details. When the customers finish
selecting the date and time, the in-house reading details will be shown, and the customers can
check the details before they click done button to make the booking.
53
Figure 24: Booking Calendar Form
7.1.8 Order Tracking
Figure 25: Wireframe of order tracking
According to the wireframe above, there is a search bar for the customer to search for their
order track by key in the order id. By doing this, a result will be shown, and the order
tracking diagram will be able to view by the customer.
54
Figure 26: Order Tracking Page
7.1.9 Membership Plan Page
Figure 27: Wireframe of Membership Plan Page
In the wireframe of the membership plan, the plan has been divided into 3 boxes, allowing
the customer to view the information of the membership plan and choose their preferred plan.
55
Figure 28: Membership Plan Page
7.1.10 Form
Figure 29: Wireframe of Form
According to the wireframe above, it has been applied in different input forms into the system.
The wireframe is drawn based on the sign-up page of the system. Other pages with form will
use the same design but have different content and layout such as login page, contact us page,
56
and staff process payment page. For the functionality of each page, sign up page is used for the
customer to sign up as a member of Bookworm Paradise. The login page is used for the
customers to login and purchase the books and services available. Next, the contact us page is
used for the customers to ask their enquiries, while process payment page is used for the admin
to process the payment in the physical Bookworm Paradise store.
Figure 30: Sign Up Page
Figure 31: Log In Page
57
Figure 32: Contact Us Page
Figure 33: Staff Process Payment Page
58
7.1.11 Staff View Panel
Figure 34: Wireframe of Staff View Panel
The figure above is the wireframe of the staff view panel. The design of this wireframe has
been used in different pages such as the manage book page, manage booking page, manage
token page and manage membership plan page for the staff to view all the book details, booking,
tokens and membership plans.
59
Figure 35: View All Books Page
Figure 36: View Booking Page
Figure 37: View Token Page
60
Figure 38: View Membership Plan
7.1.12 Staff Add Panel
Figure 39: Wireframe of Staff Add Panel
A total of two pages are using the wireframe design of staff add panel above, which is
manage adding book and manage adding membership plan. For the design of manage adding
token page will be slightly different with the wireframe. The staff can add new books, tokens
and membership plans by using these pages.
61
Figure 40: Adding Book Page
Figure 41: Adding Token Page
62
Figure 42: Adding Membership Plan Page
7.1.13 Generate Report Page
Figure 43: Wireframe Generate Report Page
The diagram above is the wireframe of generate report page. The design of this page is simple
and clear, allowing the staff to select which type of report they want to select, such as a daily,
63
monthly or yearly report. After the report is generated, the staff can choose to print the report.
The output design of the report will be shown in figures below.
Figure 44: Generate Report Page
64
7.2 GUI Principles and Concepts

7.2.1 Consistency
The GUI of the website follows the consistency principle in its design by ensuring that
elements in the user interface are uniform. The Bookworm's Paradise's website has the same
page design, style and layout throughout to ensure website consistency. Besides, the website
also adheres to the consistency principle by using the same design and style guide for visual
and interactive elements. For example, the usage of the same colour scheme, which is blue and
white tones, as well as fonts of Georgia for the header and Futura for the content and button
styles. The application of consistency in GUI design results in a more consistent user
experience. It will also increase usability because regularly using the same style and design
will allow users to navigate the system and recognise common patterns easily. In addition, page
design consistency will help users understand how to utilise the interface and reduce the chance
of frustration and confusion when using the system.
Figure 46: Page Design
Figure 47: Colour Scheme
65
Figure 48: Font for Header
Figure 49: Font for Content
7.2.2 Simplicity
Figure 50: Bold text
The website design utilises bold and simple words to simplify the design. Bold words
can help to emphasise the important content and increase the readability of the texts. In addition,
it can focus the user's attention and ease the users to find the desired location on the webpage.
For example, bold fonts are eye-catching. This allows the users who visit the website to
instantly search for the desired books without having to look for the traditional search bar that
is small and hard to locate.
7.2.3 Attractiveness
The attractiveness in design is the visual appearance of the website design and the user
experience towards the website's interface. An attractive website may increase the user's
interest and boost overall product and service satisfaction when visiting the website. For
example, the arrangement of the books sold on the website is balanced and fits together on the
screen. This increases the interface's overall harmony and visual appearance. A well-designed
layout that is visually balanced and aesthetically pleasing to the eye can enhance the user
experience. Furthermore, using images and graphics helps create a visually attractive interface,
provided it is good quality, relevant and is used in a purposeful manner. For example, the
Bookworm Paradise website uses images on the order tracking page to enhance the website's
attractiveness, as shown in Figure 52.
66
Figure 51: Books sold in Bookworm Paradise
Figure 52: Order Status on Order Tracking Page
67
7.2.4 Accuracy
The website adheres to the accuracy principle by accurately portraying information and
functionalities in its design. The forms for in-house reading booking are placed correctly, labels
are used appropriately, and data and interactions are represented accurately. The booking form
on this website is accurate to help reduce frustration and confusion because users can easily
find what they are looking for and book in a few steps. Moreover, the use of accuracy in this
website includes the use of appropriate measurement to ensure that elements are accurately
scaled and positioned. For example, the available time slots for in-house reading use the same
measurement and are ordered appropriately to ensure the design is accurate and consistent. This
will make it easier for users to understand, which improves the overall user experience.
Figure 53: In-house Reading Booking Form
7.2.5 Effectiveness
Effectiveness in designing the interface refers to the ability of the users to achieve the
objectives and complete the purchasing process when visiting the website. An effective
interface design should be able to provide the users with a direct interaction between the system
and the users while accessing the needed information. For instance, the navigation bar on the
Bookworm Paradise website has descriptive headers and simple fonts, making it clear and easy
to understand. This makes it easier for the users to locate the webpage the users are searching
for and complete the tasks easily. Moreover, the website has many functions, such as a search
68
bar to search for books, track order function and add books to the cart, which increase the
efficiency and effectiveness when using the website to check the order, preview books and
purchase the books or services available.
Figure 54: Navigation Bar on Bookworm Paradise Website
For Output Design
Figure 55: Sample Monthly Sales Report Figure 56: Sample Receipt
The output design for reports and receipt is professional, attractive, and easy to read.
The explanation will focus mostly on the report, which has headers and footers. The header
contains the report's title, date, and other information. The footer contains the company's name,
the document's title, and the page number. Besides, the reports should be designed consistently
and accurately. The data in the reports are organised appropriately to deliver information to the
user in a concise, clear, and understandable manner. The reports also employ graphical
69
components such as graphs and charts to improve the report's usability. Besides, the layout of
reports is uniform for all reports, allowing the user to discover the information they need easily
and quickly. In short, the output design for reports is accurate and consistent to enhance the
understanding of the information presented.
70
8.0 Conclusion
All in all, the Bookworm Paradise management system project will be successfully
developed using the System Development Life Cycle guideline. The project will be able to
develop according to the budget and the time given by the owner of Bookworm Paradise. This
new system is able to help Bookworm Paradise to solve a lot of problems that this bookstore
faced previously. However, the limitation of the new system is that this system has no
subcategories for the customer to find the book online. Besides that, this system does not have
many choices of online payment methods. In order to enhance the use of this system by the
customer, subcategories for the customer to search for books and also increasing online
payment methods should be added into the system in the future.
71
9.0 Individual Component

9.1 Gatleen Kaur A/P Madan Singh TP065173
9.1.1 Requirement Gathering: Questionnaire
Definition
Questionnaires are a medium used during requirement gathering. It composes of a set

of systematic questions that are used to obtain functional and statistical details on a particular
topic from a group of respondents. Furthermore, questionnaires can be answered in many ways
such as in person, over the phone, through the mail and even through the web (Pahwa, 2021).
The primary objective of handing out a questionnaire is to reduce qualitative and quantitative
data from respondents. It is an economical, efficient, and agile method of gathering extensive
amounts of data and require even in the absence of the researcher directly. There are many
types of questionnaires, but the most popular question types used are known as Likert Scale,
open-ended, close-ended, multiple choice and rating questions (Formplus, 2022).
Advantages
Questionnaires have many advantages including being cost and time effective.
Questions can be created and regulated by the system analyst, eliminating the need to hire
external surveyors to carry out interviews. The questions can be posted on website or emailed
to the target audience to obtain results faster. The target audience can have the privilege of
taking their time to answer the questions at their convenience as there is no need to demand an
answer immediately. To add on, the respondents are more likely to be truthful than when a
researcher is present as they will be pressured into giving more socially sensible answers.
Regardless of the type of questionnaire, it will be less costly than subcontracting another market
research establishment. Although these methods are inexpensive, targeting is crucial if the
corporation wants many responses and authentic results (Debois, 2022).
Questionnaires are simple to evaluate and visualize as they are descriptively

quantitative, making the process of analysing results easier. According to an article by Gyant
(2022), Software like Google Forms and SurveyMonkey come with tools that allow people
without experience in statistics or scientific methodology to effectively go through the
responses to get valid results. Besides that, these platforms can give system analyst dynamic
comprehension of data by turning them into meaningful charts and tables. The system analyst
can then make better decisions for the requirement of the system based on these results.
72
Figure 57: Sample of visualized data (Chatterjee, 2020)
Questionnaires are also beneficial because of their scalability as it permits the

collection of data from an immense audience. Questions can be shared with anyone online in
any part of the world as long as they have a stable internet connection. System analyst does not
need to do this manually. The system analyst can address specific cities or countries for their
requirement gathering as geographical limitations are no longer a problem because of the
existence of the internet.
Disadvantages
One of the most common downsides of questionnaires is dishonest answers from

participants. They become response biased and answer the questions unreliably. Participants
do this at times because they want to portray a better version of themselves than they are. They
tend to lie to improve their perspective on self-worth. Moreover, they will try and provide
answers that are socially favoured thinking that it will “help” the system analyst. In the end,
they will make up alluring responses instead of standing their ground on their opinion and their
beliefs.
73
At times, they might not even answer the questions that aggravate them (Cornell,
2022). There are a few reasons behind why respondents hesitate to answer questions. Some
people may not want to disclose their information as they view it as sensitive matter that has
potential to cause harm to their self-image (NSF Consulting, 2023). Questions regarding
financial incomes, race and religion, sexual placement, experiences in criminal activities or
accidents are often considered strictly conscious to an individual. Participants may also be
unwilling to answer questions if it seems like they are out of context. Irrelevant questions that
differ from the scope of the survey are likely to be left out by respondents.
Different people may also have different understandings and judgements of the
questions. The results of the requirement gathering can differ without the presence of someone
there to explain the concept of a particular question and make sure that every individual has
the correct understanding. What may seem clear to the creator of the questions may be difficult
for the respondents to grasp. On the other hand, unlike face-to-face interviews, questionnaires
are not capable of apprehending a participant’s emotions or feelings (Debois, 2022). There is
a lack of observing the non-verbal characteristics of people such as facial expressions and body
language. Sometimes, useful data may be overlooked.
Location to Conduct Questionnaires
 Online
 Bookstore of the Bookworm Paradise
 Office of Bookworm Paradise
Target Audience to Answer Questionnaires
 Customers of Bookworm Paradise

 Employees of Bookworm Paradise
 Shareholders of Bookworm Paradise
 Suppliers of Bookworm Paradise
74
Sample Questions of the Questionnaires
1. Do you think that categories book is important features in Bookworm Paradise

management system?
o Yes
o No
2. Book should be found by having a search bar to search the book title.
o Strongly Disagree
o Disagree
o Neutral
o Agree
o Strongly Agree
3. Do you often use eBook features?

o Often
o Not Often
4. Do you think an Order Tracking System is important for you to track your book order?
o Yes
o No
5. What features that you like to have when Bookworm Paradise decide to have an online
platform to sells its book?
75
Steps to carry out Questionnaire-answering
1. Firstly, the system analyst should focus on recognizing the objective of the
questionnaire. By doing this, they will be able to ask questions that help to accomplish
the set objective.
2. The next step is to identify the group of contributors. This is done to find the target
population and samples for sampling. System analyst should sample everyone from
small groups and pick representatives from larger groups of user population.
3. If necessary, system analyst could separate users into various categories. This will allow
better insights from users as those from different categories will respond with different
input to particular questions.
4. System Analysis must choose the tools or medium needed to conduct the questionnaire-
answering. Following this, they must also determine the methods for respondents to
answer the questions be it through the mail, online or in person.
5. The next step is where system analyst must draft out the questions and check if the
responses will justify with the objective of the study. Some factors that need to be
considered are:
Type of questions
Topic and subject of questions
Terminology and phrasing of questions
Order and layout of the questionnaire
6. Testing for the questionnaire is required to regulate the amount of time needed for
participants to complete the survey. Thus, the system analyst is required to test the
questionnaire that prepare for collecting the requirement for Bookworm Paradise before
sending out.
7. System analyst is responsible and expected to give out a notification letter to
participants. Members of Bookworm Paradise will receive bonuses when they fill in
the questionnaires regardless of how. Questionnaire forms will also be available at the
physical outlet for walk-in customers.
8. The questionnaire is distributed to the target audience. Reminders are sent to ensure
responses are collected by the dedicated completion date.
76
9. System analyst will analyse and tabulate the data that is received. Helpful tools like
SSPS (Statistical Package for the Social Sciences) allow better processing of data and
informative charts and graphs are created. System Analyst are also advised to document
the results to help Bookworm Paradise make better corporate decisions and keep
information for future references.
9.1.2 DFD Level 1 and Data Dictionary of 6.0 Generate Report

DFD Level 1
Figure 58: DFD Level 1 of 6.0 Generate Report
The diagram above shows the subprocesses of how the Bookworm Paradise system generates
a report. Firstly, essential data such as information from receipts and the book inventory are
collected. The user of the system will then select the template or software to be used to make
the report. Data is then pulled from its source. Before making the available data neat and sorted,
the user is required to create the design and layout of the report. Once that is done, the data is
ready to be added into the report. The report is now generated and printed for the manager to
review.
Data Dictionary
External Entity: Manager
Name Manager
Description Manager views and analyzes reports, which generated by the system
to make decisions for the future of the company.
Input Data Flows -
Output Data Flows Report
77
Process: 6.0 Generate Report
Name 6.0 Generate Report
Description The system will collect the Receipt details and book inventory data
which required for generating reports to be given to the manager.
Input Data Flows Receipt details, Book inventory data, Report
Output Data Flows Report
Process START
FUNCTION generate_report ()
DISPLAY available software
SET report layout
DISPLAY data on report
PRINT report
END
START
READ receipt, book_inventory_data
CALL FUNCTION generate_report ()
END
Data Flow: Book Inventory data
Name Book Inventory data
Description Book Inventory data needs to be collected in order to generate reports

to be given to the manager.
Origin/Source Book Inventory (Data Store)
Destination/Sink 6.0 Generate Report
78
Data Structure Book inventory data = Book ID +
Book title +
Book author +
Book publisher +
Book genre +
Type of copy available +
Number of copies available
Data Element Book inventory data
Data Element Name: Book ID
Description: Unique code to identify book
Element Characteristics
Type: Alphanumeric
Length: 10
Output Format: XXXX999999
Data Element Name: Book Title
Description: Name of book purchased by customer
Type: Alphabetic
79
Length: 100
Output Format: xxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxxx

xxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxxx
xxxxxxxxxx
Data Element Name: Book Author
Description: Person who wrote the book
Type: Alphabetic
Length: 40
Data Element Name: Book publisher
Description: Company that published the book
Type: Alphabetic
Length: 40
Data Element Name: Book genre
Description: Category of books
Type: Alphabetic
Length: 15
80
Output Format: xxxxxxxxxxxxxxx
Data Element Name: Type of copy
Description: Version of book available (hardcopy, e-book)
Type: Alphabetic
Length: 10
Output Format: xxxxxxxxxx
Data Element Name: Number of copies
Description: Number of available copies of books
Type: Integer
Length: 5
Output Format: 99999
Data Store: Report
Name Report
Description To store the report that generated through the system
Input Data Flow Report
Output Data Flow Report
Data Structure Report = Report ID +

Report Type +
Report Generation Date +
Report Content
81
9.2 Law Mei Jun TP065265

9.2.1 Requirement Gathering: Sampling
Sampling
Definition
Sampling is the systematic selection of representatives from a population. It is assumed

that when these carefully chosen samples are examined, the analysis will provide useful
information about the overall population (McCombes, 2019). The primary goal of sampling is
to ensure that the entire population is represented accurately. When a system analyst must deal
with a large amount of data and has limited resources, or when the population is too large,
sampling is an excellent data gathering tool. There are several widely used sampling techniques,
including random sampling, stratified sampling, and systematic sampling.
Figure 59: Sampling (McCombes, 2019)
Advantages of Sampling
There are numerous advantages to using sampling techniques in data collection. The
first benefit is the low cost of sampling. Data collection for the entire population would be
prohibitively expensive. As a result, sampling is more cost effective because it divides the
population into smaller unit sizes, making data collection process much easier (Jeferson, 2015).
If sampling technique is not used, the system analyst will have to interview or conduct
questionnaires to the entire population, incurring unnecessary costs such as printing a very
large number of questionnaires.
82
Furthermore, the sampling technique is advantageous because it saves time during data
collection. This is because sampling allows system analysts to increase the speed of data
collection because system analysts do not need to go through every individual in the population.
With sampling, conducting interviews from a sample will be faster than conducting interviews
from a large population, which will take a long time (McCombes, 2019). The analysis will
also take less time with a sample than with a population.
Furthermore, the accuracy of data is high when using sampling during data gathering.
When this technique is used, the system analyst can achieve a higher level of data accuracy
because the exact information can be obtained by generalising sample to population. If
sampling is not used, the process will become too monotonous, and data handling issues may
arise due to the large amount of data that must be analysed (Jeferson, 2015). The data is also
more accurate with sampling because it provides detailed information on data even when
resources are limited.
Disadvantages of Sampling
Despite this, the sampling technique has drawbacks, such as the possibility of bias
depending on the system analyst's mindset when selecting the sample. In some cases, sampling
bias occurs when sample selection decisions are made in such a way that some people are more
likely than others to be chosen for the sample. As a result, sample bias will lead to inconclusive
and untrustworthy results. This will greatly impact the project's quality.
Moreover, the sampling has the disadvantage of being difficult to select a truly
representative sample. It is difficult to choose a sufficient and reliable sample that accurately
represents the population. A larger sample size provides greater accuracy in estimating the true
situation, but the benefits diminish as the sample size approaches the total population (Jeferson,
2015). As a result, when employing this technique, the system analyst must choose carefully
to ensure sample precision and optimal resource use.
83
Another disadvantage of sampling technique is the impossibility of sampling. When the

population is too small and the data set is heterogeneous, the sampling technique is inapplicable.
Obtaining a representative sample in such cases is difficult. System analysts cannot use this
technique if the population is too small because sampling is insufficient to obtain an accurate
result (McCombes, 2019). This is due to the fact that when the sample size is too small,
generalisation from sample to population will be inaccurate. In addition, sometimes errors are
possible even if samples are chosen with care.
Location to Carry Out Sampling
 Bookworm Paradise’s office

 Bookworm Paradise’s store
Target Audiences for Sampling
 Workers and managers of the Bookworm Paradise

 Customers of Bookworm Paradise
Objective of Sampling
 Selects a subset of the population for interview or questionnaire rather than conducting
interviews and questionnaires for the entire population, which is both costly and time-
consuming.
 Allows the system analyst to save time by not having to analyse data from the entire
population to avoid time and effort wastage.
 Improve the effectiveness of data collection by obtaining more accurate information.
Steps to Carry Out Sampling
1. System analyst will need to determine the information that will be collected or
described to conduct the sampling method for the BWP project. A realistic plan for
what will be done with the collected data is required by the system analyst.
2. System analyst must determine the objectives of the BWP project as well as the data
collection method to be used, which could be an interview, observation, or
questionnaire.
3. System analyst then determines the project's population, such as Bookworm Paradise
manager, workers, customers and so on. For example, the population of BWP must
include bookstore customers, particularly BWP members, because they are the primary
84
users of the system developed and their suggestions will have a significant impact on
the system.
4. System analyst will select the appropriate sampling technique in order to obtain the
most accurate result. The system analyst can use systematic sampling for the BWP
project, which is a probability sampling method in which a random sample with a fixed
periodic interval is selected from a large population (Fleetwood, 2018).
5. System analyst will select a sample size. To achieve a better result, the sample size
should be large enough. Therefore, the system analyst should choose a larger sample
but one that is smaller than the population which is around 10% of the population
(w3computing, 2014). The sample size should also be given in absolute terms. For
example, the system analyst will sample 100 people out of 1000 members and 10 people
out of 100 employees of BWP to obtain satisfactory results. The sample will then be
interviewed to obtain the information needed by the system analyst.
85
9.2.2 DFD Level 1 and data dictionary for 9.0 Generate Token
DFD Level-1
Figure 60: DFD Level-1 of Generate Token
The staff will first input token details and select type of token. This process's output, token
details, will be inputted the Fill in token details Process. Then, the staff will need to enter the
amount of discount during this process. The output, token info, will be used as the input for the
Create token process. This process will generate a unique code for the token and a token with
complete details will be generated. The token will then be delivered to the customer and stored
in a data store.
Data Dictionary
External Entity: Staff
Name Staff
Description The person who handles the business processes of the bookstore.
The staff will input token details into the system in order to
generate tokens for customers.
Input Data Flows Rental info, Booking info, Order info
Output Data Flows Token Details, Book Details
Process: 9.0 Generate Token
Name 9.0 Generate Token

Description The system will process the token details from staff and create
token for customer.
Input Data Flows Token Details
86
Output Data Flows Token

Process
Data Flow: Token
Name Token
Description The token consists of info of the token for the customers to read
and use for their next purchase.
Origin/Source 9.0 Generate Token
Destination/Sink Customer (External Entity)
Data Structure Token = Token Code +
Customer ID +
Discount +
Expiry Date
Data Element Data Element Name: Token Code
Description: Unique code to identify the token
Type: Alphanumeric
Length: 8
Output Format: xxxx9999
Data Element Name: Customer ID
Description: Unique code to identify the customer
Type: Alphanumeric
Length: 6
87
Output Format: xx9999

Data Element Name: Discount
Description: The percentage of the discount for the token
Type: Integer
Length: 2
Output Format: 99
Data Element Name: Expiry Date
Description: The expiry date of the token
Type: Date
Length: -
Output Format: YYYY-MM-DD
Data Store: BWP Token
Name BWP Token

Description To store token generated for the customer
Input Data Flow Token
Output Data Flow Token
Data Structure Token = Token Code +
Customer ID +
Discount+
Expiry Date
88
9.3 Pan Zhin Huey TP065263

9.3.1 Requirements Gathering: Interview
Definition
An interview is a formal face-to-face meeting with the purpose to extract information

from an individual or a group of individuals (Eid, 2015). An interview is the main requirement-
gathering technique when developing a project during the system analysis phases to collect
information for a proposed or existing system. An interview consists of two categories which
are structured interview and unstructured interview. A structured interview depends on a set of
standardised questions to be asked to the interviewee. There are two types of questions to be
asked when conducting a structured interview: open-ended and closed-ended. The open-ended
questions can help to elicit helpful information depending on different individuals' points of
view when interacting with the system (Formplus, 2022). On the other hand, the close-ended
questions are asked to obtain a specific answer by providing a set of fixed answers to choose
from. Next, unstructured questions are conducted in a question-and-answer format. This
approach offers more flexibility for the interviewee to answer the questions in their own words,
which helps the interviewer obtain more detailed information about a specific problem with
the system. Therefore, unstructured questions are best used to collect general information
regarding the proposed or existing system.
Advantages
When conducting an interview, the interviewee can answer the questions freely based
on their perspective and experience when using or reviewing the system. Therefore, the
interviewer can gather more information related to the system than other requirement-gathering
methods. For instance, an interview helps the software developer get more examples of what
the users like or dislike about the system and the requirements the users demand in a system.
Next, the interview helps the interviewer to analyse the interviewee's non-verbal
behaviour when answering the questions. Many details can be observed through interviewing
the interviewee as interviews are conducted face-to-face. For example, interviewees can
express their feelings with the existing or proposed system through body language when they
cannot put it into words.
89
In addition, conducting interviews gives a higher response rate (Sociology Group,

2022). This is because the interviewee is required to answer all the given questions on the spot.
An interview helps the interviewer get instant feedback compared to mailed questions. The
instant feedback the interviewee gives during an interview helps the interviewer extract more
information by asking further questions based on their response to specific questions.
Disadvantages
The downside of an interview is it is extremely time consuming. This is because an

interview can take up to more than ten minutes when interviewing an individual. Besides that,
preparing interview questions is extremely time consuming as well. This is because background
research is required to prepare the interview questions. Additionally, the questions must be
planned carefully for the interviewer to extract the most information out of the interviewee.
Other than time consuming, the disadvantage of conducting an interview is that an

expert interviewer is required. This is to ensure that the interview runs smoothly and effectively.
For instance, when an expert interviewer with knowledge of the business conducts the
interview, the interviewer knows what to ask and how to ask the questions depending on
different types and personalities of the various interviewees. The interviewer must have the
skills to organize, conduct and document the interview smoothly. Therefore, this helps the
interview to be effective by getting the most information out of the interviewee without any
pressure on the interviewee.
Next, another disadvantage of conducting an interview is it has less anonymity (Brooke,

2016). This concern often causes the interviewee to speak less than how they felt, as their
responses are not anonymous to the interviewer. Thus, the interviewee who has a shy
personality will not give much honest feedback regarding their experience with the existing or
proposed system. Conducting an interview may cause the respondents to feel fear of
embarrassment when providing their feedback on particular questions as they think that their
responses are not useful towards the projects and do not meet the objectives of the interview.
Location to conduct the interview
90
· Bookworm Paradise Bookstore
Target audience to interview
· Customers of Bookworm Paradise
· Employees of Bookworm Paradise
· Stakeholders of Bookworm Paradise
Set of questions to be asked during the interview
· How satisfied are you when purchasing books with Bookworm Paradise Bookstore?
· How do you search for the availability of a particular reading material you would like
to purchase from Bookworm Paradise Bookstore?
· Why do you prefer in-house reading than purchasing books from Bookworm Paradise
Bookstore?
· Why do you prefer buying reading materials online rather than purchasing from the
bookstore?
· Do you think renting reading materials from the bookstore is a better option compared
to purchasing them?
Steps to carry out interview
1. The interviewer will determine the right people to interview whether it is a group
interview or an individual interview or both.
2. The interviewer will establish the objectives when conducting the interview. Examples
of objectives determined are the areas to be discussed during the interview, the lists of facts
that need to be collected, collect the specific details obtained from the interviewee's
response and interview the stakeholders to provide a bigger picture to develop the system.
3. The interviewer will develop the interview questions based on the objectives that has
been established. The interviewer will create different types of questions with a mixture of
open-ended and closed-ended questions. Open-ended with the purpose of collecting details
91
from the interviewee and closed-ended questions are used to verify any facts. Below is an
example of a table formed when developing interview questions based on every objective
established.
Objective
Questions
4. The interviewer will start preparing for the interview after the questions are ready. The
time, place, duration, and topics will be determined. A confirmation email will be sent to
the interviewee once all the elements required to conduct the interview are determined.
5. On the day of the interview, the interviewer will establish a plan for the meeting. The
interviewer will begin the interview by self-introduction, explaining the purpose of
conducting the interview, and describing the project to the interviewees. During the
interview, the interviewer will give the interviewee adequate time to think about the
questions. The interviewer will pay full attention to listening to the feedback given by the
interviewee. The interviewer will summarise the interview session and seek confirmation
from every interviewee who participated in the interview.
6. After the interview, the interviewer must record the information from every interviewee
quickly because notetaking must be kept minimum during the interview. Then, the
interviewer is required to send a memo to express a gratitude towards the interviewee
followed by the time, date, location, purpose of the interview and the main topics discussed
in a summary via e-mail. The purpose of sending a summary of topics discussed is to allow
the interviewee to offer any additional information or corrections.
7. The last step is to evaluate the interview process. The information collected during
every interview must be assessed to ensure no bias is involved in the recorded facts.
92
9.3.2 DFD Level 1 and data dictionary of 2.0 Manage In-house Reading
DFD Level 1
Figure 71: DFD Level 1 of 2.0 Manage In-house Booking
Diagram below shows the DFD Level 1 diagram for manage in-house reading process.
This process begins with receiving booking details from the customers such as the customer
ID, customer name, phone number, email booking date, booking time and duration selected by
the customer. Then, the information provided by the customer will be send as booking details
to verify the availability of the specified period. Next, the availability status generated along
with the booking details will be sent to manage booking process. The booking details will be
stored in the booking data store. If the slots are available, the booking info which includes the
availability status will be retrieved from the data store to be sent to manage booking process to
generate a booking and booking ID. The updated booking info with booking ID included will
be sent to the staff to generate booking status. Simultaneously, the updated booking info from
the manage booking process will be sent to record booking information process to record the
complete booking information. The booking status generated by the staff will also be sent to
the record booking information process to record into the system and the system will send the
booking status as input to send booking status to customer process to be send to the customers.
Data Dictionary
Entity: Customer
93
Name Customer
Description Customers provide booking details that
enable the customer to book for in-house
reading slot through the system
Input Data Flows Booking Status, Receipt, Token
Output Data Flows Booking Details, Order Details, Rental
Details
Process: 2.0 Manage In-House Reading
Name Process 2.0: Manage In-house Reading

Description A process to check availability for the in-house reading slots
and generate a booking status for the customer after the
customer schedule for an appointment
Input Data Flows Booking Details, Booking Status, Booking Info
Output Data Flows Booking Status, Booking Info, Booking Details
Process:
Pseudocode for Book Appointment for In-House Reading and Generate Booking Status:
Data Store: Booking
Name Booking
Description To store in-house reading booking details
related to customer
Input Data Flow Booking Details
94
Output Data Flow Booking Info

Data Structure Booking Details =
First Name +
Last Name +
Email +
Phone Number +
Date +
Time +
Duration
Data Flow: Booking Details
Name Booking Details

Description The customer required to insert booking details to schedule an
appointment for in-house reading
Origin/Source Customer (external entity)
Destination/Sink 2.0 Manage In-house Reading
Data Structure Booking Details =
First Name +
Last Name +
Email +
Phone Number+
Date +
Time +
Duration
Data Element Data Element Name: First Name

Description: customer’s first name
Type: Varchar
Length: 225
Output Format: xxxxxxx xxxxxxx xxxxxxx
95
Data Element Name: Last Name

Description: customer’s last name
Type: Varchar
Length: 225
Output Format: xxxxxxx xxxxxxx xxxxxxx
Data Element Name: Email

Description: customer’s email
Type: Varchar
Length: 225
Output Format: xxxx@xxxx.com
Data Element Name: Phone Number

Description: customer’s phone number
Type: Varchar
Length: 225
Output Format: 000-000-0000
Data Element Name: Date

Description: booking date selected by customer
Type: date
Length: -
Data Element Name: Time

Description: booking time selected by customer
Type: time
96
Length: -
Output Format: HH:MI:SS
Data Element Name: Duration

Description: duration of in-house reading selected by customer
Type: time
Length: -
Output Format: HH:MI:SS
97
9.4 Phuah Kuang Yi TP065448

9.4.1 Requirements Gathering: Research
Definition
Research is the methodical consideration of investigation into a certain issue or topic

using scientific techniques. Research is a methodical inquiry to describe, explain, forecast, and
manage the observed phenomenon, according to American sociologist Earl Robert Babbie.
Both inductive and deductive techniques are used. Deductive techniques support an observable
occurrence whereas inductive techniques examine it. Deductive techniques are more frequently
connected with quantitative analysis, whereas inductive strategies are associated with
qualitative research (Fleetwood, 2018). This technique is frequently used to access the gathered
information when gathering information. It incorporates any prior data that the marketer may
have obtained from either internal or external sources. The purpose of carrying out research
during requirements gathering is to search through important article, journal and so on to find
the requirement that suitable to use in the Bookworm Paradise system.
Advantages of Research
There are a lot of pros when using research as the requirement gathering technique. The
first advantage that will be discussed is system analyst can save cost when conducting research.
This is due to the reason that all the material that use for researching such as journal, article
and so on can be found in online. The system analyst maybe will need to pay certain amount
of money in order to access the resources to gain the requirement that suitable with the system
that ongoing to be developed, but this technique is still cheaper that other requirements
gathering technique.
Besides that, the system analysis will save a lot of time to gain valuable information
when conducting research to gather the requirement of the system. This is because the system
analyst can easily access the valuable information such as journal through online. The system
analyst only needs to analyse the resource to get the valuable information for knowing the
requirement of the system. Thus, the system analyst will use lesser time during conducting
research when compared to questionnaire as the system analyst needs to think about the
questions and test the questions in order to get the valuable information from the people which
require a lot of time to make the questionnaire perfect.
Lastly, the next benefit of carrying out research to gather the requirement of the system
is the information that gather during research is more reliable. This is because the researcher
98
that written the article, journal and books might have years of expertise in collecting and
studying a certain kind of information (Niosi, 2020). The information that gains from this kind
of resources will be accuracy and very reliable. Thus, the system analyst can get an accuracy
requirement when conducting research.
Disadvantages of Research
Although carry out research brings a lot of benefits to the system analyst, but there are
some drawbacks that might be faced by the system analyst during conducting research. The
first cons that will be faced by the system analyst is they will find many outdated information
during research. Although there are a lot of resource that can use during research, but most of
the resources may have been done years ago. This kind of resource will provide the system
analyst the outdated information as the requirement that need by the people from all walks of
life will change based on the technology changes year by year.
Furthermore, one of the disadvantages of research is difficult to obtain the relevant

information. There are a lot of material can be used for research, but in order to get the material
that related to the topic that the system analyst like to research about to gain the requirement
of the system may be difficult. There may be less material that regarding about the topic that
the system analyst like to research. Although the system analyst found the material that related
to the topic which can be used for research, but the material may not provide the information
that the system analyst needs for getting the requirement of the system.
Location to Get Research Material (Rakiah, 2019)
- Library
- Bookworm Paradise Bookstore
- Website
- Google Scholar
- Microsoft Academic Search
- Directory of Open Access Journals (DOAJ)
- JSTOR
- EBSCO
Target material for research
- Journals
- Articles
99
- Books
- Seminars
- Meetings
- Videos
- Audios
Sample Research Questions
- How does the customer make payment after they selecting all their items through the
online system?
- How the customer search for their favourite book through an online system?
- How does the customer track their things that they purchased through the system?
- What functionally that the customer hope to have in e-commerce system?
- What kind of features of the system is useful for the staff to operate the company selling
business?
Step to Carry Out Research
1. The system analyst needs to determine a clear objective of research before start
conducting it. For example, the system analyst will come up with an objective about
find out the requirements that suitable with the Bookworm Paradise system.
2. The system analyst will then focus on where to find the material for doing the research
and what material can be used for doing the research in order to get the requirement for
developing the Bookworm Paradise system.
3. After locating the material, the system analyst needs to start analysing the material to
gain the information about what requirement can be include in the Bookworm Paradise
system.
4. During analysing the material, the system analyst needs to record down all the
important and relevant information that has been found through researching the
materials.
5. After done analysing, the system analyst requires to write a report regarding the
requirement that can be used in the Bookworm Paradise system through the useful
information which gain from the research materials.
100
9.4.2 DFD Level 1 and data dictionary of 8.0 Generate Receipt

DFD Level 1
Figure 72: DFD Level1 for 8.0 Generate Receipt
According to the DFD Level 1 above, the book rental data, which form Book Rental data store
and the book sales data, which from Book Sales data store will be received. Both data will be
passed to the second process, which is “Select Type of the Receipt. The system will determine
whether to prepare book rental receipt or book order receipt. After that, the receipt data will be
passed to “Create Receipt” process which the receipt will be generated out and will pass to the
customer who make rental or order. The receipt will also store in the Receipt data store in the
DFD Level 0 diagram.
Data Dictionary
External Entity: Customer
Name Customer
Description Customer can receive a receipt after the customer make their
order and rental by using this system.
Input Data Flows Receipt, Booking Status, Token
Output Data Flows Rental Details, Booking Details, Order Details
Process: 8.0 Generate Receipt
Name 3.0 Generate Receipt

Descriptio The system will generate receipt once the customer makes their order or rental
n and successfully make their payment.
Input Data Book Rental data, book sales data
Flows
101
Output Receipt
Data
Flows
Process
Data Flow: Receipt
Name Receipt
Description Receipt contains all the order or rental cost details, which will
pass it to the customer after payment successful.
Origin/Source 8.0 Generate Receipt (Process)
Destination/Sink Customer
Data Structure Receipt = Receipt ID + Receipt Date + Receipt Time
Customer Name + Book Name + Quantity + Total Product
Price + Subtotal + Shipping + Sales Tax + Total Amount
102
Data Element Data Element Name: receipt ID

Description: Unique ID to identify the receipt
Type: Alphanumeric
Length: 6
Data Element Name: Receipt Date
Description: the date that the receipt be generated
Type: date
Length: -
Data Element Name: Time
Description: the time that the receipt be genereted
Type: time
Length: -
Output Format: HH:MI: SS
Data Element Name: Customer Name
Description: The registered name of the customer
Type: Alphabet
Length: 64
Output Format: xxxxxxx xxxxxx xxxxxxxxx xxxxx
Data Element Name: Book Name
Description: the name of the book that ordered or rented by
the customer
Type: Alphanumeric
Length: 100
Output Format: xxxxx xxxx xxxxx xxxxxx
Data Element Name: Quantity
103
Description: the quantity of book that ordered or rented by

the customer
Type: Integer
Length: 2
Output Format: 99
Data Element Name: Total Product Price
Description: the total price of the book that ordered or rented
by the customer.
Type: Float
Length: 6
Output Format: 999.99
Data Element Name: Subtotal
Description: the subtotal of the rental or order by the
customer.
Type: Float
Length: 6
Data Element Name: Shipping
Description: the shipping price of the rental or order by the
customer.
Type: Alphanumeric
Length: 6
Data Element Name: Sales Tax
Description: the sales tax of the rental or order by the
customer.
Type: Float
Length: 6
104

Data Element Name: Total Price
Description: the total price of the customer’s order.
Type: Float
Length:5
Decimal: 2
Data Store: Receipt
Name Receipt
Description To store the data that relate to the receipt
Input Data Flow Receipt
Output Data Flow Receipt
Data Structure Receipt = Receipt ID + Customer Name + Book Name +
Quantity + Total Product Price + Subtotal + Shipping + Sales
Tax + Total Amount
105
9.5 She Jun Yuan TP065157

9.5.1 Requirement Gathering: Observation
Definition
Observation is a best requirement gathering technique when the analyst likes to have a
deeper knowledge of the user in their current work setting (Eid, 2015). The system analyst can
be helped through observation by having a personal understanding of how the user interacts
with the system. When a task's improvement is the goal, the system analyst can watch the user
and how their environment affects their interaction with the system. When stakeholders find it
challenging to describe precisely what their tasks entail and what their requirements might be,
observation might help offer the specifications. Observation will be widely used for
requirement gathering when the stakeholders have trouble effectively articulating their
requirements, the procedure is repeated in nature, and so on. There are two types of observation
that can be conducted, which is passive observation and active observation. Passive observation
entails stepping back, keeping oneself out of the way, and refraining from participating in the
action. The analyst will merely observe and make notes without interacting with the operator
or end users (Project Requirement Gathering: Observations, 2020). However, active
observation means that the analyst will participate in the process in some way. They will ask
some questions to the end user of the system in order to determine the requirements of the
system during their observation session.
Advantages of Observation
There are many benefits of using observation as the requirement gathering method. One
of the benefits is that observation is the easiest technique to be used. This is because even while
scientifically controlled observations need some technological expertise, the system analyst
nevertheless require very little technical knowledge and are simpler and more accessible than
other methods. In order to gather the requirements and collect the data, the analyst will notice
new things in the company operation every day, so it is simpler. An analyst can become expert
at studying their surroundings with little training (Prasanna, 2022).
Besides that, another benefit of observation is the requirement that being gathered will
be more accurate. This is due to the reason that information about the physical surroundings in
which the task is carried out can be gleaned through observation. In observation, the accuracy
of the information can be verified by several tests. Thus, data gathered by observation is far
more trustworthy and more accurate when compared to interview and questionnaire technique.
106
Furthermore, the last benefit that will be discussed is that observation requires less
cooperation of the respondents. This is because the willingness of the target audience to divulge
different details about business processes or systems is not necessary for observation except
the analyst is using active observation which requires them to ask some question during
observation. Thus, observation still is nevertheless easier to get the data and requirement
although have less cooperation of the respondents.
Disadvantages of Observation
Although using observation to gather the requirements has many benefits, analysts still
will face some drawbacks during using observation as the requirement gathering method. The
first drawback of observation is time-consuming. This is due to the reason that a long time
should be given to the system analyst to carry out observations in order to make sure the data
and requirements that have been gathered is accurate. It is challenging to accomplish an
investigation by observation in a constrained amount of time. Due to the length of the process,
there is a potential the analyst will grow disinterested and refuse to continue.
Apart from that, the second disadvantage is personal bias of the system analyst. This is
due to the reason that the system analyst’s own biases have a variety of effects on what they
observe. Additionally, this makes it difficult to draw reliable generalisations. The system
analyst may have their own perception of what is proper and wrong in relation to particular
circumstances. Additionally, they might have distinct ideas about the requirements to develop
the system.
Lastly, one of the cons of using observation as a requirement gathering method is being
unable to gain much information when compared with interview and questionnaire. This is
because during observation, some information unable to be gained such as the history of the
company and also the expectation of the worker and the customer of the company. Thus, the
analyst is unable to gain this type of information due to less communication occurring through
the observation process.
Location for the observation
● Bookworm Paradise bookstore
Target Audience for Observation
107
● Customer of Bookworm Paradise

● Staff of Bookworm Paradise
Set of Questions Prepare for Observation
● Who will be involved in the buying process of Bookworm Paradise?

● How does the customer search for the book？
● What is the step for the customer to purchase the book?

● How does the customer register as a member?
● How does the worker record the stock of the book?
● How does the worker record customers who register as a member?
Steps to Carry Out Observation
1. The system analyst will determine the objective of this observation. The system analyst
needs to clearly know about the objective of the observation in order for them to have
a focus point to observe so that they will be able to successfully gather the requirements.
2. The system analyst will start to determine the process to be observed. Based on the
process, the system analyst will list out some questions for use during observing the
process. Below are the tables that will be prepared during this step. The sample question
can be referred to the set of questions prepare for observation above.
Process Actor Questions
3. After preparing the questions, the system analyst can start to observe the process that
has been listed. The system analyst needs to conduct observations in different timing
such as peak, normal and low. The table to collect the data of the observation has also
been drawn. The system analyst will need to write down all his or her observations in
the table below in order for the system analyst to analyse their observations, which will
help in gathering the requirements of the Bookworm Paradise management system.
Process Peak Normal Low
108
4. After observing the process, the system analyst needs to prepare the data and analyse
the behaviours of the data. Throughout the system analyst of data that gather during
the observation, the requirement for the system will be able successfully gathered by
the system analyst.
9.5.2 DFD Level 1 and data dictionary of 3.0 Manage Order

DFD Level 1
Figure 73: DFD Level 1 for 3.0 Manage Order
First and foremost, the ‘Receive Customer Order’ process will receive the order details from
the customer once they have made the payment. The order details will then store in the order
data store. The data store will then pass back the order info and it will be sent to the next process
which is ‘Check for Payment’. The system will check where payment has been received from
this order. If the payment exists, the order details data flow will flow to 3 process which is
generate book sales increment, generate sales inventory decrements, and send the customer
order to the staff.
Data Dictionary
109
Name Customer
Description Customer can place their order to purchase their favourite
books. The customer needs to make payment in order to
proceed their order. The order will then manage by the system
Process: 3.0 Manage Order
Name 3.0 Manage Order

Descripti The system will process the order that made by the customer and process the
on order details in order to pass to the stuff of Bookworm Paradise to prepare the
order.
Input Order Details, Order Info
Data
Flows
Output Order Details, Order Info, Book Sales Details, Sales inventory Details
Data
Flows
110
Process
Data Flow: Order Details
Name Order Details

Description Order details is the order that has been made by the customer
through the system.
Origin/Source Customer (External Entity)
Destination/Sink 3.0 Manage Order
111
Data Structure Order Details = Order ID + Customer Name + Address +

Book Name + Quantity + Unit Price + Total Amount +
Payment Amount
Data Element Data Element Name: Order ID
Description: Unique ID to identify the order
Type: Alphanumeric
Length: 6
Type: Alphabet
Length: 64
Output Format: xxxxxxx xxxx xxxxx
Data Element Name: Address
Description: the address that the book will be delivered to.
Type: Alphanumeric
Length: 250
Output Format: xxxxxxxxxxxxx xxxxx xxxx xxxxxx…
Description: the name of the book that ordered by the
customer
Type: Alphanumeric
Length: 100
Output Format: xxxxxxxxxx xxxxxxx xxxxxxx xxxxx
Description: the quantity of book that ordered by the
customer
Type: Integer
112
Length: 2
Output Format: 99
Data Element Name: Unit Price
Description: the price of the book that ordered by the
customer.
Type: Float
Length:6
Description: the total price of the customer’s order.
Type: Float
Length:8
Data Element Name: Payment Details
Description: the total amount that customer pay for the order.
Type: Float
Length:5
Decimal: 2
Data Store: Order
Name Order
Description To store the data that relate to the customer order
Input Data Flow Order Details
Output Data Flow Order Info
Data Structure Order Details = Order ID + Customer Name + Address +
Payment Amount
113
9.6 Tan Bingshen TP065389

9.6.1 Requiremenet Gathering: Document Review
Definition
Document review is a way to gather data by looking over and reviewing existing
documents (CDC, 2009). The reports of all work processes, meeting minutes, newspapers,
program logs, etc. are a few examples of documents that may be reviewed. This documentation
may be found offline, online, or in electronic form. In order to comprehend the business and
project context and pinpoint needs or potential areas for development, system analyst must be
able to thoroughly examine relevant business, system, and project documentation. Prior to
planning stakeholder interviews or other surveys, this strategy collects data. to get background
information. Make careful to ascertain whether such a disparity exists and establish the
program's objectives before you start your assessment. By reading the existing documentation,
you may have a greater understanding of the history, guiding principles, and functioning of the
program you are assessing as well as the organization in which it runs. Additionally, it will be
simpler to build an observation guide, interview questions, questionnaires, or both to see if
program plans have been carried out. if you want information to help the development of further
data gathering instruments for the assessment.
Advantage of Document Review
Thus, the document review has some of the advantage which the first one is it do not
need any cost; it is relatively inexpensive. With document review method, we do not need any
expenses, what we need to do is just study the relevant business system or some project
documentation. Then understand the business and identify the requirements to make any
improvements. Next, the other advantage is the sources of the background information will be
very accurate and good. It is because when we doing the document review, we must be read
and study the documentation of a project, the documentation must be valid and accurate. So,
the source of the background information will be a good one and trusted. Last but not least,
another advantage is document review will provides a behind-the-scenes look at a program that
may not be directly observable which mean with this method it may bring up issues not noted
by other means. Sometimes, other may not be able to discover every of the issue which may
happen.
114
Disadvantage of Document Review
Although document review has lot of advantage, but the disadvantages are also very
crucial. First of all, the information may be inapplicable, disorganized, unavailable, or out of
date. It is because the documentation may be not updated since they posted. So, when we doing
the documentation review the information probably outdated and not as accurate as it newly
posted. Next, this method also could be biased because of selective survival of information.
This is very common in the 21st century, as the internet is known by everyone, the biased would
be happen. The documentation only chooses the information which they need and causes biased.
Which is also lead to the next disadvantage, the information may be incomplete or inaccurate.
Location to conduct Document Review
i) the Bookworm Paradise (BWP) at Kuala Lumpur, Malaysia

ii) Library
Target documents for reviewing.
i) Customer Feedbacks
ii) The products Feedbacks
iii) Business Process Documentation
iv) Company Memos
Step to carry out document review.
i) Prepare Stage – In this stage, the system analyst needs to determine which items or
materials are suitable for the Bookworm Paradise to conduct analysis.
ii) Review Stage – In this stage, the system analyst needs to study the items or materials,
take note about the information and list out the follow-up questions for the stakeholders.
iii) Wrap up Stage – In this stage, the system analyst will need to review the information
and notes with their stakeholder. Then seek out the follow-up questions together.
115
9.6.2 DFD Level 1 and data dictionary of 1.0 Manage Rental
Figure: DFD Level 1 for 1.0 Manage Rental
In the first process, the ‘Receive Customer Rental’ will be receiving the rental details of the
customer after the payment process. After that, the rental info will be going to the next process
which is the ‘Check for Payment’ process. In this process, the system will check whether the
customer had complete the payment and the validity of the payment. Next, the rental info will
be pass to the upcoming process which is ‘Send the customers’ rental info to staff’. This allow
the staff for other checking and send it to other processes. Beside that, after the ‘Check for
Payment’ process, the rental info will be pass to the process call ‘Generate the book rental
increment’. In this process, the system will generate the book rental increment and send the
book rental details to the 7.0 process which is to update the book rental file. Aside from that,
from the ‘Check for Payment’ process, the rental info will be also sent to the ‘Generate the
rental inventory decrements’ and pass the renal inventory details to update the book inventory
file.
Data Dictionary
116
Name Customer
Description The customer will use the system to rent book.
Process: 1.0 Manage Rental
Name 1.0 Manage Rental

Descripti The system will be managing the rental details and info in this process after the
on payment.
Input Rental Details, Rental Info
Data
Flows
Output Rental Info, Book Rental Details, Rental Inventory Details
Data
Flows
Process
117
Data Flow: Rental Details
Name Rental Details

Description Rental details are the rental that made by the customer which
consist of Rental ID, Customer Name, Address, Book
Name , Quantity, Unit Price , Total Amount, and Payment
Amount
Origin/Source Customer (External Entity)
Destination/Sink 1.0 Manage Rental
Data Structure Rental Details = Rental ID + Customer Name + Address +
Payment Amount
Data Element Data Element Name: Rental ID
Description: Unique ID to identify the rental
Type: Alphanumeric
Length: 6
Type: Alphabet
Length: 64
Output Format: xxxxxxx xxxx xxxxx
Data Element Name: Address
Description: the address that the book will be delivered to.
Type: Alphanumeric
Length: 250
Output Format: xxxxxxxxxxxxx xxxxx xxxx xxxxx
Description: the name of the book that rented by the customer
Type: Alphanumeric
118
Length: 100
Output Format: xxxxxxxxxx xxxxxxx xxxxxxx xxxxx
Description: the quantity of book that rented by the customer
Type: Integer
Length: 2
Output Format: 99
Data Element Name: Unit Price
Description: the price of the book that rented by the customer.
Type: Float
Length:3
Decimal: 2
Description: the total price of the customer’s rental.
Type: Float
Length:5
Decimal: 2
Data Element Name: Payment Details
Description: the total amount that customer pay for the rental.
Type: Float
Length:8
Data Store: Rental
Name Rental
Description To store the data that relate to the rental
119
Input Data Flow Rental Details

Output Data Flow Rental Info
Data Structure Rental Details = Rental ID + Customer Name + Address +
Payment Amount
120
10.0Reference
Badugu, P. (2018, July 12). Software Engineering | User Interface Design - GeeksforGeeks.
GeeksforGeeks. https://www.geeksforgeeks.org/software-engineering-user-interface-
design/
Birt, J. (2022, June 2). What Is a Problem Statement: Definition, How-To and Example.
Indeed. https://www.indeed.com/career-advice/career-development/what-is-a-
problem-
statement#:~:text=A%20problem%20statement%20is%20a,any%20gaps%20between
%20the%20two.
Bridges, J. (2022, August 30). What Is a Feasibility Study? How to Conduct One for Your
Project. ProjectManager. https://www.projectmanager.com/training/how-to-conduct-
a-feasibility-study
Brooke, C. (2016, January 28). The Pros and Cons of 10 Information Gathering Techniques
for Projects. Business 2 Community.
https://www.business2community.com/strategy/pros-cons-10-information-gathering-
techniques-projects-01437727
CDC.(2009). Evaluation Briefs No. 18 Januart 2009 Data Collection Methods for Evaluation:
Document Review. https://www.cdc.gov/healthyyouth/evaluation/pdf/breif18.pdf
Chatterjee, M. (2020, December 22). Introduction to Data Visualisation - Tools, Techniques,
Examples. Great Learning Blog: Free Resources What Matters to Shape Your Career!
https://www.mygreatlearning.com/blog/introduction-to-data-visualisation-why-is-it-
important/
121
Cornell, J. (2022, December 14). 12 Advantages & Disadvantages of Questionnaires.
ProProfs Survey Blog. https://www.proprofssurvey.com/blog/advantages-
disadvantages-of-questionnaires/
Debois, S. (2022, March 8). 10 advantages and disadvantages of questionnaires. Pointerpro.
https://pointerpro.com/blog/questionnaire-pros-and-cons/
Eid, M. (2015, November). Requirement Gathering Methods. Umsl.edu.

https://www.umsl.edu/~sauterv/analysis/F2015/Requirement%20Gathering%20Metho
ds.html.htm#:~:text=While%20in%20active%20observation%2C%20the
Fleetwood, D. (2018, April 27). What is Research - Definition, Types, Methods & Examples.
QuestionPro. https://www.questionpro.com/blog/what-is-research/
Fleetwood, D. (2018, November 13). Types of Sampling: Sampling Methods with Examples |
QuestionPro. QuestionPro. https://www.questionpro.com/blog/types-of-sampling-for-
social-research/
Formplus Blog. (2022, July 27). 4 Types of Questionnaire + Free Question Examples.
Formplus. https://www.formpl.us/blog/questionnaire-types
Formplus. (2022, July 27). Structured vs Unstructured Interviews: 13 Key Differences.

FormPlus. https://www.formpl.us/blog/structured-unstructured-
interview#:~:text=A%20structured%20interview%20is%20a%20type%20of%20inter
view%20that%20relies
Halwai, S. (2021, February 20). Design Phase in SDLC - A Complete Guide [2021]. OpenXcell.
https://www.openxcell.com/blog/design-phase-in-sdlc/
122
Hamilton, T. (2022, October 29). What is System Testing? Types & Definition with Example.
Guru99.com. https://www.guru99.com/system-testing.html
Hennigan, L., & Bottorff, C. (2022, July 4). PERT Chart Vs. Gantt Chart: Which System Is
Best For Project Management? Forbes Advisor.
https://www.forbes.com/advisor/business/pert-chart-vs-gantt-
chart/#:~:text=PERT%20charts%20are%20best%20used,adjusted%20if%20the%20sc
ope%20changes.&text=PERT%20charts%20have%20a%20specific,calculate%20time
%20estimates%20for%20tasks.
Holishevska, A. (2022, October 31). How To Write The Design Specification? [Quick Guide].
Northell. https://northell.design/blog/how-to-write-the-design-specifications-quick-
guide
Imam, A. (2018, August 29). Software Development Life Cycle: The phases of SDLC -
TestLodge Blog. TestLodge Blog. https://blog.testlodge.com/software-development-
life-cycle/
Innovative Architects. (n.d.). SDLC: Seven Phases of the System Development Life Cycle.
https://www.innovativearchitects.com/KnowledgeCenter/basic-IT-systems/system-
development-life-cycle.aspx
JavaTpoint. (2021). Integration Testing - javatpoint. Www.javatpoint.com.

https://www.javatpoint.com/integration-testing
Jeferson. (2015, October 1). Advantages and Disadvantages of Sampling. Money Matters | All
Management Articles. https://accountlearning.com/advantages-and-disadvantages-of-
sampling/
123
Jena, S. (2020, June 26). Types of Feasibility Study in Software Project Development.
GeeksforGeeks. https://www.geeksforgeeks.org/types-of-feasibility-study-in-
software-project-development/
Krzewińska, N. (2019). Economic feasibility. CEOpedia | Management Online.

https://ceopedia.org/index.php/Economic_feasibility
Kovalenko, O. (2022, February 21). SDLC Design Phase: Definition, Activities, Goals [2022].
IDAP Blog. https://idapgroup.com/blog/sdlc-design-
phase/#:~:text=In%20SDLC%2C%20the%20design%20phase
Kumar, A. (2021, May 28). Feasibility Study in System Analysis & Design - FreeEducator.com.
2021 Free Study - 2022. https://www.freestudy.com/feasibility-study-in-system-
analysis-design/
LucidChart. (2017). ER diagram tutorial. Lucidchart.com.

https://www.lucidchart.com/pages/er-diagrams
Martins, J. (2020, October 24). How to Write An effective Project Objective, With Examples
[2023] • Asana. Asana. https://asana.com/resources/how-project-objectives
McCombes, S. (2019, September 19). Sampling Methods | Types and Techniques Explained.
Scribbr. https://www.scribbr.com/methodology/sampling-methods/
MERRILL, C. (2019, April 30). Understanding Software Maintenance: Perfective, Corrective,

& More. Custom Software Development Insights | Zibtek Blog.
https://www.zibtek.com/blog/software-maintenance-understanding-the-4-main-types/
124
Niosi, A. (2020). Pros and Cons of Research. Pressbooks.pub; Pressbooks.
https://kpu.pressbooks.pub/openimc/chapter/primary-research-v-s-secondary-
research-pros-cons/
NSF Consulting. (2023). Unwillingness to answer. 4 reasons why people refuse to respond.
http://nsfconsulting.com.au/4-reasons-for-survey-refusals/
Pahwa, A. (2021, July 20). Questionnaire: Definition, Types, Examples & How To Design.
Feedough. https://www.feedough.com/what-is-questionnaire/
Prasanna. (2022, January 5). Advantages and Disadvantages of Observation Method | Merits
and Demerits of Observation in Marketing. A plus Topper.
https://www.aplustopper.com/advantages-and-disadvantages-of-observation-
method/#:~:text=Very%20minimal%20technical%20knowledge%20is
Project Requirement Gathering: Observations. (2020, April 23). PM Majik.

https://www.pmmajik.com/project-requirement-gathering-observations/
Rakiah. O. (2019, January 22). The Most Reliable Places to Find Credible Information |
Presentation Guru. Presentation-Guru.com. https://www.presentation-guru.com/the-
most-reliable-places-to-find-credible-data/
Ransom, N. (2013). Requirement Gathering & Analysis Phase in SDLC - Video & Lesson
Transcript | Study.com. Study.com. https://study.com/academy/lesson/requirement-
gathering-analysis-phase-in-
sdlc.html#:~:text=The%20most%20important%20phase%20of
125
sanjoy. (2018, October 10). Software Engineering | Integration Testing - GeeksforGeeks.

GeeksforGeeks. https://www.geeksforgeeks.org/software-engineering-integration-
testing/
Sociology Group. (2022). Advantages and Disadvantages of Interview in Research. Sociology

Group; Sociology Group. https://www.sociologygroup.com/advantages-
disadvantages-interview-research/
Sitesbay.com. (n.d.). Maintenance Phase in SDLC - Software Engineering Tutorial.

Www.sitesbay.com. https://www.sitesbay.com/software-engineering/se-sdlc-
maintenance-phase
Study.com. (2022). Implementation & Coding Phase in SDLC - Video & Lesson Transcript |
Study.com. Study.com. https://study.com/academy/lesson/implementation-coding-
phase-in-sdlc.html
System Requirements Document - Javatpoint. (n.d.). Www.javatpoint.com.

https://www.javatpoint.com/system-requirements-document
Sitesbay.com. (n.d.). Maintenance Phase in SDLC - Software Engineering Tutorial.

Www.sitesbay.com. https://www.sitesbay.com/software-engineering/se-sdlc-
maintenance-phase
Talbert, M. (2022, October 18). Project Schedules 101: Why You Need Them and How to
Make Your Own. Asana. https://asana.com/resources/project-timeline-schedules
TutorialsPoint. (2020). System Analysis & Design - System Design - Tutorialspoint.

Tutorialspoint.com.
https://www.tutorialspoint.com/system_analysis_and_design/system_design.htm
126
Martin, M. (2019, July 18). SDLC (Software Development Life Cycle) Tutorial: What is,
Phases, Model. Guru99.com. https://www.guru99.com/software-development-life-
cycle-tutorial.html
w3computing. (2014, August 19). Sampling Design in Information Gathering. W3computing.

https://www.w3computing.com/systemsanalysis/sampling-design/
What is a context diagram and how do you use it? (2022, May 18). MiroBlog.
https://miro.com/blog/context-diagram/
What is a Data Flow Diagram. (2022). Lucidchart. https://www.lucidchart.com/pages/data-

flow-diagram
127

SYAD Group Assignment

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SYAD Group Assignment

Uploaded by

Copyright:

Available Formats

Module Code AAPP007-4-2-SYAD

Module Name SYSTEM ANALYSIS AND DESIGN

STUDENT NAME STUDENT TP

1.1 About the company .......................................................................................................... 4

1.2 Business Process .............................................................................................................. 4

1.3 Overview of Proposed System ......................................................................................... 6

1.4 Project Objective .............................................................................................................. 7

2.0 Problem and Proposed Solution ........................................................................................... 8

2.1 Problem Background ........................................................................................................ 8

2.2 Problem Statement ........................................................................................................... 8

2.3 List of Issues..................................................................................................................... 9

2.5 Objective of Proposed System ....................................................................................... 11

2.6 Scope of Proposed System ............................................................................................. 13

3.0 Project Planning ................................................................................................................. 14

3.1 System Development Life Cycle.................................................................................... 14

3.1.1 Planning Phase ......................................................................................................... 14

3.1.2 Analysis Phase ......................................................................................................... 16

3.1.3 Design Phase............................................................................................................ 18

3.1.4 Implementation Phase.............................................................................................. 20

3.1.5 Maintenance Phase .................................................................................................. 22

3.2 Gantt Chart ..................................................................................................................... 24

3.3 Workload Metrix ............................................................................................................ 25

4.0 Feasibility Study ................................................................................................................ 27

4.1 Operational Feasibility ................................................................................................... 27

4.2 Technical feasibility ....................................................................................................... 30

4.3 Economic Feasibility ...................................................................................................... 31

4.4 Schedule Feasibility ....................................................................................................... 35

5.0 System Analysis ................................................................................................................. 36

5.1 Functional Requirements................................................................................................ 36

5.2 Non-Functional Requirements ....................................................................................... 37

6.0 Design Diagram ................................................................................................................. 40

6.1 Context Diagram ............................................................................................................ 40

6.2 DFD Level 0 ................................................................................................................... 41

7.0 Interface Design ................................................................................................................. 42

7.1Wireframe and WIX Design ........................................................................................... 42

7.1.1 Customer Profile ...................................................................................................... 42

7.1.2 Home Page ............................................................................................................... 46

7.1.3 Book Page ................................................................................................................ 48

7.1.4 Product Page ............................................................................................................ 50

7.1.5 Checkout Page. ........................................................................................................ 51

7.1.6 Payment Method ...................................................................................................... 52

7.1.7 In-house Reading Booking Calendar ....................................................................... 53

7.1.8 Order Tracking ........................................................................................................ 54

7.1.9 Membership Plan Page ............................................................................................ 55

7.1.11 Staff View Panel .................................................................................................... 59

7.1.12 Staff Add Panel ...................................................................................................... 61

7.2 GUI Principles and Concepts ......................................................................................... 65

7.2.3 Attractiveness .......................................................................................................... 66

7.2.4 Accuracy .................................................................................................................. 68

7.2.5 Effectiveness ............................................................................................................ 68

8.0 Conclusion ......................................................................................................................... 71

9.0 Individual Component ....................................................................................................... 72

9.1 Gatleen Kaur A/P Madan Singh TP065173 ................................................................... 72

9.1.1 Requirement Gathering: Questionnaire ................................................................... 72

9.2 Law Mei Jun TP065265 ................................................................................................. 82

9.2.1 Requirement Gathering: Sampling .............................................................................. 82

9.3 Pan Zhin Huey TP065263 .............................................................................................. 89

9.3.1 Requirements Gathering: Interview......................................................................... 89

9.4 Phuah Kuang Yi TP065448............................................................................................ 98

9.4.1 Requirements Gathering: Research ......................................................................... 98

9.5 She Jun Yuan TP065157 .............................................................................................. 106

9.5.1 Requirement Gathering: Observation .................................................................... 106

9.6 Tan Bingshen TP065389 .............................................................................................. 114

9.6.1 Requiremenet Gathering: Document Review ........................................................ 114