P-Town Online Book Store

BY

Manish Maharjan

Prajan Ghimire

Pranish Shakya

Pratham Rana Magar

National College of Computer Studies (NCCS)

A MIS Project Report Submitted to

Faculty of Management, Tribhuvan University
In partial fulfillment of the requirements for the degree of

Bachelor of Information Management

Paknajol
August/2024
 ACKNOWLEDGEMENT
With the successful completion of the P-Town Book Store project, we would like to express
our sincere gratitude to everyone who contributed, encouraged, and supported us throughout
the process. First and foremost, we extend our heartfelt thanks to teacher Sachita Maharjan
for their cooperation and invaluable insights throughout the entire project. Your willingness to
share information and provide access to resources greatly facilitated our research efforts. We
would also like to thank the National College of Computer Studies (NCCS) for providing us
with the opportunity to participate in this valuable project. Furthermore, we appreciate the
patrons of P-Town Book Store who participated in surveys, interviews, and provided
feedback, allowing us to gain a deeper understanding of their needs and preferences. Lastly,
we would like to thank our colleagues and peers for their encouragement and assistance during
the preparation of this project.

ii
 EXECUTIVE SUMMARY
P-Town Book Store is desktop-based application, aimed at modernizing its operation and
providing enhanced services in the book store.
In the first page of this report, the background of the study has been written which is for the
project study in details. In the introduction of the organization the operating system in book
store is mentioned. The project serves as a partial fulfillment of the requirements for the BIM
(Bachelor of Information Management) program while addressing the specific needs of the
bookstore. Information was gathered through interviews and questionnaires with staff and
management during site visits. MS Word, Visual Paradigm, NetBeans, XAMPP, and MYSQL
were utilized for report creation and project development.
In the second the part of the report, analysis of task and activities of current existing system is
written. The current status of the organization is written. After the research and questionnaire
the problem of the organization is analyzed. So, requirement specification is specified into
functional and non-functional requirement. Feasibility study is done as technical, operational,
economic and technological feasibility. The system is analyzed and show in different UML
diagramslike for data modeling, ERD, class diagram are presented likewise use case diagram
show the functions of the system actors, activity diagram, sequence diagram are shown the
system models.
After the detail study of the organization the conclusion is drawn to overcome the problem of
the society.

iii
 TABLE OF CONTENT

Title Page

ACKNOWLEDGEMENT.........................................................................................................................ii

EXECUTIVE SUMMARY.......................................................................................................................iii

TABLE OF CONTENT...........................................................................................................................iv

LIST OF FIGURES...............................................................................................................................vii

LIST OF TABLES.................................................................................................................................viii

ABBREVIATIONS...................................................................................................................................ix

CHAPTER I: INTRODUCTION.......................................................................................................10

1.1. Background..........................................................................................................................10

1.2. Introduction of the organization...........................................................................................10

1.3. Current situation of the organization...................................................................................10

1.4. Issues/problems of the project.............................................................................................10

1.5. Objectives of the project......................................................................................................10

1.6. Methodology/Procedure adopted for writing the project.....................................................11

1.6.1. Project Framework...............................................................................................................11

1.6.2. Data and Information...........................................................................................................11

1.6.3. Tools to be used...................................................................................................................11

1.6.4. Technique of project report analysis....................................................................................12

CHAPTER II: TASKS AND ACTIVITIES PERFORMED............................................................13

2.1. Analysis of tasks, activities, problems, issues.....................................................................13

2.1.1. Analysis of task and activities..............................................................................................13

2.1.2. Analysis of problems and issues..........................................................................................13

iv
 2.2. Requirement Specification...................................................................................................13

2.2.1. Functional Requirements:....................................................................................................13

2.2.1.1. Use Case Diagram...............................................................................................................14

2.2.2. Non-Functional Requirements.............................................................................................15

2.3. Feasibility Study..................................................................................................................15

2.3.1. Technical Feasibility............................................................................................................15

2.3.2. Operational Feasibility.........................................................................................................16

2.3.3. Economic Feasibility...........................................................................................................16

2.4. System Analysis...................................................................................................................16

2.4.1. System Designing and Modeling.........................................................................................16

2.4.1.1. Activity Diagram.................................................................................................................17

2.4.1.2. Entity Relationship Diagram...............................................................................................18

2.4.1.3. Sequence Diagram...............................................................................................................19

2.5. System Design.....................................................................................................................20

2.5.1. UI Design/ System Architecture..........................................................................................20

2.6. Implementation....................................................................................................................21

2.7. Testing.................................................................................................................................21

2.8. System Requirements...........................................................................................................22

2.8.1. Software Requirements........................................................................................................22

2.8.2. Hardware Requirements.......................................................................................................22

2.9. Findings...............................................................................................................................22

CHAPTER III: STRATEGY USED IN ORAGANIZATION........................................................23

3.1. Customer Relationship Management...................................................................................23

3.2. Agile Methodology..............................................................................................................24

CHAPTER IV: DISCUSSION AND CONCLUSION......................................................................25

iv
 4.1 Discussion...................................................................................................................................25

4.2 Conclusion...................................................................................................................................25

References

APPENDICES

iv
 LIST OF FIGURES

Figure 1 Use Case Diagram..................................................................................................................14

Figure 3 Activity Diagram....................................................................................................................17

Figure 4 ER Diagram............................................................................................................................18

Figure 5 Sequence Diagram..................................................................................................................19

Figure 6 System Architecture................................................................................................................20

vii
 LIST OF TABLES

Table 1 Use Case Description...............................................................................................................15

Table 3 Test Case Table........................................................................................................................21

viii
 ABBREVIATIONS

BIM Bachelor of Information Management

TU Tribhuvan University

CSS Cascading Style Sheet

HTML Hyper Text Mark-up Language

MYSQL My Structured Query Language

XAMPP Cross-Platform (X), Apache (A), MySQL (M), PHP (P)

SDLC Software Design Lifecycle

GUI Graphical User Interface

UML Unified Modeling Language

UI User Interface

IDE Integrated Development Environment

POS Point of sales

ix
 CHAPTER I: INTRODUCTION

1.1. Background
This report is prepared on behalf of MIS Project entitled “P-Town Online Book Store”. This
application can be used by admin. Admin will manage the book store by using the
computerized system where he/she can add books, record orders, edit books, delete books, and
record various transactions. With this computerized system there will be no loss of data of
student and admin which generally happens in the non-computerized system. This project has
encouraged a student to study the unit of the organization, analyze the problems and to
develop an application to overcome the problem of the organization. This statement signifies
the culmination of knowledge and skills acquired throughout five semesters of study, evident
in the content of this report.

1.2. Introduction of the organization

P-Town Bookstore is located at Maitidevi, Kathmandu, owned by Mrs. Sarina Tuladhar. It is a
cozy place filled with books, welcoming everyone who loves to read. Since 2017, people have
been coming here to find their favorite stories. The bookstore has a friendly atmosphere and a
wide selection of books for all tastes. Inside P-Town Bookstore, you will smell the fresh scent
of books. It feels inviting, like a place where you can get lost in a good story. The staff are
friendly, and the wooden floors creak softly as you walk around. Everything about the store
makes you feel like you are part of a community that loves books.

1.3. Current situation of the organization

Currently provided services of P-Town book store are:
 Currently, admin rely on manual process for books management and customer transactions.
 With non-computerized system, there is increased errors in managing book records.

1.4. Issues/problems of the project

The issues/problems of the project are:
 Using manual process for recording the books.
 Lack of proper inventory management system.

1.5. Objectives of the project

The main objectives of the project are:
 To provide a digital system for managing book inventory records.
 To implement an online system that protects data integrity and ensures a secure environment
for managing book inventory.

10
1.6. Methodology/Procedure adopted for writing the project
To know about the background and surrounding of the organization, we first visit the
organization and conduct a meeting with the owner of the organization. Then the current
situation of the organization is discussed and for the further process the objectives and
questionnaire are prepared for analyzing the collected data.
1.6.1. Project Framework
The entire project is divided into three segments. They are:
i. Introduction
The project aims to enhance its operations and customer experience through the
implementation of modern frameworks. This introduction provides an overview of the
project's objectives, highlighting the importance of upgrading the bookstore's systems to meet
the evolving needs of its patrons. It outlines the key areas of focus, such as improving
inventory management, streamlining sales processes, and enhancing online presence.
ii. Analysis
This section conducts a thorough analysis of P-Town Book Store's current operations and
identifies areas for improvement. This includes developing the software dependent on how the
issues and objectives were analyzed. To show how the work was done and how the system
was made, we used different pictures. These pictures include an activity picture, a use case
picture, and a class picture.

iii. Discussions and conclusions

In the conclusion, instead of using the old manual technique the admin of P-Town Book store
can use the new software, that we have been developing which is more effective and it can
overcome the problems that they are facing in the store.

1.6.2. Data and Information

For the collection of data, questionnaire method was used. The data generally includes the
information and services provided by the organization. The data collected are:
 Direct interview with the staff and owner
We had met with the owner and asked about the problems they are facing in the organization
and after the interview, it was found that there was not an e-commerce website.
 Questionnaire
We prepared a pile of question and asked it to the visitors and owners themselves abouts the
problems and possible outcomes for the problem.

1.6.3. Tools to be used

 Front-end: Java swing
 Back-End: Java
 Database: MYSQL, XAMPP
 IDE: NetBeans 8.2

11
1.6.4. Technique of project report analysis
Agile model is used for making this project. Agile methodology is a flexible and iterative
approach to this project which emphasizes on collaboration, customer feedback and small,
rapid releases. It was used to address the limitation of traditional, linear project management
method like the waterfall model.

12
 CHAPTER II: TASKS AND ACTIVITIES PERFORMED

2.1. Analysis of tasks, activities, problems, issues

2.1.1. Analysis of task and activities
The organization we have surveyed follows a manual process for recording orders and billing
transactions. To buy a book, the customers have to wait for a long time. The admin has to
records the books in manual process which consumes a lot of time. Since the organization
follows the pen and paper for the records, there can be the error, the record might lose which
creates a problem later. In the manual process, it is difficult to find the books because it is
quite hard to organize the store.

2.1.2. Analysis of problems and issues

Problems and issues that we have identified after research and survey are:
 Limited use of technology, such as outdated point-of-sale systems or absence of an online
presence, hindering the store's ability to compete in the digital age.
 The POS system lacks adequate facilities for storing and viewing data in a structured manner.

2.2. Requirement Specification

P-town book store includes both functional and non-functional requirements.

2.2.1. Functional Requirements:

Functional Requirement includes actual functionality of an application that consists the
admin, customers.
 Login: Admin can login to further use of system.
 Records: Admin can view records of the students.
 Manage books: Admin can update, edit, and delete books. If books are out of stock, then
admin can make it active and inactive.
 Search: Admin can search books.
 Logout: It will redirect admin to login page.

13
2.2.1.1. Use Case Diagram
Use-case Diagram is the interaction between system and customers. In the given use-case
diagram it shows the interaction between Online Book Store and actors i.e., Admin. Use-case
diagram shows which actors can perform which functions of the system and the relationship
between them as well.

Figure 1 Use Case Diagram

14
 Table 1 Use Case Description

Actors Admin.

Description For instance, admin login to the system. He/ She add, edit and
delete books and check records.

Data Data includes books, admin and student information.

Stimulus Command can be issued by all the actors. For example, admin
can add books.
Response For the stimulus instance provided above, the system may
respond as update in the table, adding the provided data and
letting the admin view the updated table.

2.2.2. Non-Functional Requirements:

Non-functional requirements, also known as quality attributes or constraints, specify criteria
that describe the operation of a system rather than its specific behaviors. They define how a
system should perform its functions, rather than what functions it should perform. Therefore,
the non-functional requirements are listed below:
 Security: The system has robust security measures in place to protect customer data.
 Usability: The system is user-friendly and intuitive, with clear navigation and easy-to-use.
 Scalability: The is able to scale up to accommodate future growth.
 Maintainability: The system is easy to maintain and update, with clear documentation.

2.3. Feasibility Study

The feasibility study serves as a crucial component within a report, offering valuable insights
and analysis. Its primary purpose lies in justifying the proposed project or initiative by
showcasing its practicality and viability. There are many types of feasibility analysis made for
this project. Through a comprehensive assessment of technical, economic, and operational
factors, the study provides a solid foundation for decision-making to evaluate the risks and
benefits associated with the proposed changes.

2.3.1. Technical Feasibility

Assessing the technical feasibility of an ecommerce website for P-Town Bookstore involves
evaluating infrastructure, integration capabilities, security measures, user interface design, and
optimization for search engines. By carefully considering these factors, P-Town Bookstore can
determine the viability of implementing an ecommerce platform and ensure its successful
launch and operation.

15
2.3.2. Operational Feasibility
Assessing the operational feasibility of implementing an ecommerce website for P-Town
Bookstore involves simple GUI and understandable by non-technical user. Customers do not
have to be confused about where they are going on the site. By carefully considering these
aspects, P-Town Bookstore can determine the feasibility of implementing an ecommerce
platform and ensure a smooth transition into its operations.

2.3.3. Economic Feasibility

This system is economically feasible for the user. It is economically feasible for this project
because the overall cost to develop this system is very low. Generally, it assesses whether a
system falls within financial constraints and confirms that this system has been proven to be
economically feasible.

2.4. System Analysis

System analysis involves a comprehensive examination and evaluation of a system's
components, functions, processes, and interactions to understand its current state and identify
opportunities for improvement. It encompasses gathering and analyzing data, defining
requirements, modeling system behavior, and proposing solutions to enhance efficiency,
effectiveness, and overall performance.

2.4.1. System Designing and Modeling

System designing and modeling involve the creation of detailed plans and representations that
depict how a system will function and be structured. This process typically follows system
analysis, where requirements and objectives are identified. System designing focuses on
translating these requirements into concrete specifications and blueprints for the system's
architecture, interfaces, and components.

16
2.4.1.1. Activity Diagram
An activity diagram is a type of behavioral diagram in the Unified Modeling Language (UML)
that depicts the flow of activities within a system or business process. It provides a visual
representation of the sequence of actions, decisions, and transitions that occur as part of a
specific workflow or process.

Figure 2 Activity Diagram

17
2.4.1.2. Entity Relationship Diagram
An entity-relationship diagram (ER diagram) is a visual representation of the relationships
between entities in a database. It's a fundamental tool used in database design to model the
logical structure of a database system. The elements ofan ERD are: Entities, Relationships
and Attributes.

Figure 3 ER Diagram

18
2.4.1.3. Sequence Diagram
A sequence diagram is a type of interaction diagram in the Unified Modeling Language
(UML) that illustrates the interactions between objects or components within a system over
time. It provides a visual representation of the sequence of messages exchanged between
objects or components to accomplish a specific task or scenario.

Figure 4 Sequence Diagram

19
2.5. System Design
System design is the process of defining the architecture, components, modules, interfaces,
and data for a system to meet specified requirements. It involves transforming the
requirements identified during system analysis into a blueprint that outlines how the system
will be implemented and structured.

2.5.1. UI Design/ System Architecture

User Interface (UI) design focuses on creating visually appealing and user-friendly interfaces
for software applications or systems. It involves designing the layout, appearance, and
interaction elements of the user interface to enhance usability and provide a seamless user
experience. It defines how different parts of the system are organized and how they
communicate with each other to fulfill the system's functionality.

Figure 5 System Architecture

This software has following sub-components:

Admin: They are the main operator of the software.

View: View represents the user interface (UI) component of an application. It is responsible
for presenting the data to the user and capturing user unput, such as mouse clicks, keyboard
inputs, or touch gestures.
Controller: Controller acts as an intermediary between the View (user interface) and the
Model (data and business logic). It handles user input, processes requests, and updates the
Model accordingly.
Model: Model represents the data and business logic of an application. It encapsulates the
application's data structure, storage, and processing logic, independent of the user interface
(View) or user input handling (Controller).
Database: It is the storage of the system where all the information is stored.

20
2.6. Implementation
This system is built for the academic purpose, but this system can be implemented as partial
testing as well. The system is developed as a prototype, allowing for seamless integration into
the organization to facilitate specific activities conveniently.
Implementation, also known as the development phase of the software, is a critical stage in the
software development process. It involves translating the design specifications and
requirements into a functioning software system. To develop this software different tools were
used. We have used NetBeans IDE and to connect the database We have used XAMPP. The
software is developed using the Java.
2.7. Testing
A test case is a detailed set of conditions, inputs, actions, and expected results developed to
determine whether a software application or system behaves as intended. Test cases are
designed based on requirements, user stories, or design specifications and are executed to
validate the functionality of the software.
Project name: P-Town online Book Store

Table 2 Test Case Table

Login
ID TEST CASE ADMIN INPUT PASS CRITERIA

U_LOG_1 Admin Login Admin enters a Display message

wrong username invalid credentials.

U_LOG_2 Admin Login Admin enters a Display message

wrong password invalid credentials.

U_LOG_3 Admin Login

Admin enters correct Login Successfully
username and
password.

21
2.8. System Requirements
2.8.1. Software Requirements
 XAMPP installed and running.
 Web Browser: Google Chrome, Opera, Microsoft Edge.

2.8.2. Hardware Requirements

 Processor: Intel, Ryzen
 Memory: 4 GB minimum

2.9. Findings
Initially, problems were identified and thoroughly analyzed. Potential solutions were then
evaluated, and some ideas were even implemented. This software solution was designed and
developed as a response to the identified problems. The findings encompass the problems
themselves, the proposed solutions, and the methods used to translate solution ideas into
tangible features within the system.

22
 CHAPTER III: STRATEGY USED IN ORAGANIZATION

3.1. Customer Relationship Management

Customer Relationship Management (CRM) is a management philosophy that aims to achieve
long-term success through customer satisfaction. Applying CRM to a book inventory
management system involves a holistic approach to ensure accuracy, efficiency, and customer
satisfaction.

Core Principles of CRM in Book Inventory Management:

Customer Focus
It is paramount in book inventory management. By understanding the specific needs of
librarians, booksellers, and patrons, the system can ensure accurate, up-to-date book
information, efficient search capabilities, and timely order processing. To exceed expectations,
the system should offer additional value-added features such as book recommendations,
reading lists, and personalized services.

Total Employee Involvement

It is crucial for a successful book inventory management system. By empowering employees
to contribute to decision-making and problem-solving, organizations can harness their
valuable insights. Providing comprehensive training equips staff with the necessary skills to
effectively utilize the system. Recognizing and rewarding employees for their contributions
fosters a positive work environment and encourages continued dedication to system
improvement.

Measurement and Analysis

It can be crucial for data-driven decision-making in book inventory management. By tracking
key performance indicators such as inventory accuracy, order fulfillment time, search response
time, and customer satisfaction, organizations can gain valuable insights into system
performance. Analyzing this data helps identify trends, pinpoint problems, and uncover
opportunities for improvement. Benchmarking against industry standards provides a
comparative perspective and sets targets for continuous enhancement.

Process Improvement
It is essential for optimizing book inventory management. By mapping out the entire process
from acquiring books to their eventual disposal, organizations can identify areas for
enhancement. Eliminating unnecessary manual tasks, errors, and inefficiencies streamlines
operations and reduces costs. Continuous improvement, driven by data analysis and feedback,
ensures the system's ongoing adaptation to evolving needs and challenges.

23
 By adopting a CRM approach, a book inventory management system can achieve higher
levels of efficiency, accuracy, and customer satisfaction, ultimately contributing to the overall
success of the organization.

3.2. Agile Methodology

Agile is a management philosophy that aims to achieve long-term success through customer
satisfaction. Applying Agile to a book inventory management system involves a holistic
approach to ensure accuracy, efficiency, and customer satisfaction.

Core Principles of Agile in Book Inventory Management:

Customer Collaboration
Foster strong relationships with librarians, booksellers, and patrons through regular
communication and feedback. This collaboration ensures that the system is continuously
aligned with user needs and delivers features that enhance their experience, such as
personalized book recommendations and efficient search capabilities.

Empowered Teams
Encourage team members to actively participate in decision-making and problem-solving. By
leveraging their insights and expertise, the organization can drive innovation and system
improvements. Empowered teams are more motivated and can quickly adapt to changing
requirements, ensuring the system remains effective and efficient.

Iterative Development
Implement changes and improvements in small, manageable increments. This approach allows
the system to evolve through rapid updates, making it easier to incorporate user feedback and
address issues promptly. Iterative development ensures that the system continuously adapts to
meet user expectations and organizational goals.

Adaptability and Flexibility

Continuously analyze performance metrics and user feedback to identify opportunities for
improvement. By embracing change and remaining flexible, the system can adapt to evolving
industry trends and user needs. This approach ensures that the book inventory management
system remains relevant and effective in a dynamic environment.

By adopting an agile approach, a book inventory management system can achieve higher
levels of efficiency, accuracy, and customer satisfaction, ultimately contributing to the overall
success of the organization.

24
 CHAPTER IV: DISCUSSION AND CONCLUSION

4.1 Discussion
The system for P-town Bookstore has been developed through a combination of primary and
secondary data collection methods. In primary data gathering, field visits and surveys were
conducted to gain firsthand insights into the bookstore's operations and challenges. Additionally,
interviews and questionnaires were administered to the management team and owners to
gather information about the existing systems and the problems associated with them. After
identifying the online book store system is developed. The system will be efficient for the
admin as it will overcome the lack of e-commerce problem and admin can manage the orders
and keep the billing transactions in the database. During this summer project, following data
and information were discussed.
• Current situation of the organization.
• Issues problems of the organization.
• Advantages of using web-based software.
• How software will help to overcome problems.

4.2 Conclusion
In conclusion, the new software system for P-town Bookstore will bring big improvements. It
makes things easier for both the managers and customers. With better ways to manage
inventory and serve customers, the bookstore is set to do even better. Everyone worked
together to make the system just right for the store. Now, P-town Bookstore is ready to move
forward confidently, making shopping simpler and more enjoyable for everyone. The project
improved my technical skills and enhanced my understanding of software development
methods. It also gave me insights into various programming languages and why online
systems are essential for organizational branches.

25
 References

chitrasingla2001. (2008). Functional vs Non-Functional Requirements. Retrievedfrom

GeeksforGeeks: https://www.geeksforgeeks.org/functional-vs-non-functional-requirements/

team, d. (2005). The easiest way for Confluence teams to collaborate using diagrams. Retrieved from
draw.io: https://app.diagrams.net/

26
 APPENDICES

Appendix 1: Questionnaire
1. Does the system support multiple users with different access levels?
2. How satisfied are you with your current bookkeeping system?
3. Is the system easy to set up and configure?
4. How satisfied are you with the current system?
5. How important is data accuracy in your library’s bookkeeping system?
6. What type of devices do you primarily use to access the library system?
7. What improvements would you suggest for the current library bookkeeping system?

27
Appendix 2: Screenshots

28
29
30
31
32