Debre markos University Burie campus

Department of Computer Science

Title: - Web based Online Book Shop Project

NAME …………………………………..…………. ID

1, Samrawit mossie …………………………….....1404160

2, Eyerusealem Germachew …………………...140383789i898989

3 ,Shibesh Taddele .……………………………… 1404227

4 ,Desse Aweke...……………………………..…….1405913

5 ,Yhalem Ayalu ...…………………………….….1404472

INSTRUCTOR , NAME: - Temesgen

SUBMISSION,DATE:-20/11/2016,E.C
 Abstract
Mega Publishing and Distribution P. L. C is a business company established in September 2015
pursuant to the 1952 (EC) commercial code of Ethiopia. It is the leading book publisher and
distributor in Ethiopia book market for several years. The company is based in Addis Ababa
and has 32 book stores throughout Ethiopia.

The purpose of this project is to develop web based system with a user–friendly interface which
enables the organization and the customers and to communicate and share feedbacks effectively
and efficiently. In this project customer can get service without succulent delivered books in to
own house.

The possible outcomes of this system are performing the following activity by user ,Managers,
employer and administrator : - add book, add account, update account, delete account, update
book, comment and view feedback, post and view, generate report , buy and sell books , renting
books and soon. The system provides the username and password authentication method. We
will develop the system by used server side and client side script such as HTML, java script and
php. The problem of initiate to done this project in existing system is limited accessibility, time
consuming process, searching, Lack of real-time information and scalability limitation. We will
use Object Oriented Analysis and Design methodology and some data gathering techniques such
as observation, question and analysis documents.

I
Table of Contents
Abstract...........................................................................................................................................I

CHAPTER ONE............................................................................................................................1

1.1 Background (overview).................................................................................................................1

1.2 Statement of the problem...............................................................................................................1

1.3 Objective of the project..................................................................................................................2

1.3.1 General objective of the project......................................................................................2

1.3.2 Specific objectives of the project....................................................................................2

1.4 Feasibility analysis.........................................................................................................................2

1.4.1 Operational feasibility.....................................................................................................2

1.4.2 Technical feasibility........................................................................................................2

1.4.3 Economic feasibility........................................................................................................3

1.4.4 Political feasibility...........................................................................................................5

1.4.5 Time feasibility (Time scheduling).................................................................................5

1.5 Task break dawn.............................................................................................................................6

1.6 Scope of the project........................................................................................................................6

1.7 Significance and Beneficiaries of the project..............................................................................7

1.7.1 Significance of the project...............................................................................................7

1.7.2 Target benefit of the project............................................................................................7

1.8 Methodology...................................................................................................................................8

1.8.1 Data collection techniques...............................................................................................8

1.8.2 Systems Analysis and Design (approach).......................................................................9

II
 1.8.3 Development tools...........................................................................................................9

1.9 Testing procedures (types of testing used)................................................................................10

1.10 Implementation (Parallel/Partial/Direct)..................................................................................10

1.10 .1 Client Side Code……………………………………………………………………………………………………………….......10

1.10.2 Server Side Code……………..……………….…………………………………………………………………………….......67

1.11 Limitation of the project............................................................................................................69

1.12 Risks & contingencies...............................................................................................................69

1.13 Assumptions and Constraints....................................................................................................69

1.14 Team composition......................................................................................................................70

CHAPTER TWO.........................................................................................................................71

Description of the Existing System.............................................................................................72

2.1 Introduction of Existing System.................................................................................................72

2.2 Players in the existing system.....................................................................................................73

2.3 Major functions/activities in the existing system......................................................................74

2.4 Business rules...............................................................................................................................75

2.5 Report generated in the existing system....................................................................................75

2.6 Forms and other documents of the existing systems................................................................76

2.7 Bottlenecks of the existing system.............................................................................................76

2.7.1 Performance (Response Time)......................................................................................76

2.7.2 Input (Inaccurate/Redundant/Inflexible) and Output (Inaccurate)................................76

2.7.3 Security and Controls....................................................................................................76

2.7.4 Efficiency......................................................................................................................76

2.7.5 Scalability......................................................................................................................76

2.8 Practices to be preserved.............................................................................................................77

2.9 Proposed solution for the new system that address problems of the existing system...........77

III
2.10 Requirements of the Proposed System.....................................................................................78

2.10.1 Functional Requirements.............................................................................................78

2.10.2 Nonfunctional Requirements.......................................................................................79

IV
 CHAPTER ONE

1.1 Background (overview)

Mega Publishing and Distribution P. L. C is a business company established in September 2015
pursuant to the 1952 (EC) commercial code of Ethiopia. It is the leading book publisher and
distributor in Ethiopia book market for several years. The Shop is based in Addis Abeba and
has 2 book stores throughout Ethiopia. Mega Publishing and Distribution P. L. C. operate with
an established ethical business history and wide market out let all over Ethiopia. The company
has strong reputation in publishing and distribution of various types of books and educational
materials in Ethiopia. The motivation of develop this system is to reduce waste time of customer
and easily delivered books on time , reduce the workload of admin, employer, manager and other
personnel’s work in company. The main goal of our project is developed web based system for
customer to purchase, rented and paid payment online. And additional to reduce workload of any
employer work in mega book shop..

1.2 Statement of the problem

The main problem of the current system is the sorting, payment and searching process. For
example, the book which is imported may be different kinds of text books, fictions and non-
fiction with their categories, year of published, authors, titles including magazine and
newspapers. Therefore, there is a need of an algorithm for sorting them.

With regards to the searching process, one customer may come only with the name of the author,
or the title, or the type of the book. So the worker is responsible to search for the book
accordingly, and it is difficult and time consuming to search for one book from the collections of
books on the shelves.

To promote new books available in the store, currently the organization uses papers and stickers
which are costly, tedious and will only be used for a short period of time, because it can be
damaged by people, rain, and wind or even by sun. To sum it up, the following are the main

1
problems encounter on Mega bookstore and distribution center: - loss of data, time consuming,
prone to errors, tedious and workload problems.

1.3 Objective of the project

1.3.1 General objective of the project

The main objective of the project is to develop an automated system for book sales and rentals of
Mega book store and distribution center.

1.3.2 Specific objectives of the project

The specific objectives of the project are the following.

 To study and identify the problems of the existing system

 To develop a database for the recording system.
 To develop user friendly interfaces.
 To create a different access level in the system
 To test the system to overcome the system functions

1.4 Feasibility analysis

1.4.1 Operational feasibility

It is the measure of how will the solution works in the shop. This proposed system will achieve
each and every goal stated in the objective part of this proposal. To do so there should be skilled
workers who know about how to use computers and software’s in the shop. So, the project to be
operationally feasible there should be a short training about how to use the being developed
system to the workers. At the completion of the project there will be such kind of training for
those employees.

1.4.2 Technical feasibility

A large part of determining resources has to do with assessing technical feasibility. It considers
the technical requirements of the proposed project. The technical requirements are then
compared to the technical capability of the organization. The systems project is considered
technically feasible if the internal technical capability is sufficient to support the project

2
requirements.
The technical feasibility may address the following major issues:

 Is the proposed system or solution practical?

 Do we currently possess the necessary technologies?
 Do we possess the necessary technical expertise?
Therefore, the project technically incorporates the following major functionalities:
 Familiarity: the proposed system believes to insure maximum user friendly nature and
familiar with the user.
 Modification: the system will allow modifications like changing rules and data in the
database.
 Extensibility: the system will extensible; it is easy to add new functions when the user
demands additional features to be incorporated.
 Portability: The system will be portable, meaning it wills compatible to different
platforms.
 Technical expertise: The project’s team has taken all the necessary courses that called us
to develop the system.
 Availability of technology: The technology to develop the system is available.
Generally, since the project is developed by object oriented approach, it will enable to go
along with future technologies.
 Practicality: This proposed system is capable to be easily applied to the existing
problems. Moreover, the team believes that the system can be put into practice by
providing short term training to workers. It is also technically feasible, because we will
develop the project within a given resource of software and hardware implementation
tools.

1.4.3 Economic feasibility

It is the most frequently used method for evaluating the effectiveness of a new system. It can
measure the cost effectiveness of the project. That means it considers all cost and benefits
regarding to the project. It also defined as a cost-benefit analysis.

The project contains tangible and intangible benefits. This are:

3
 A) Tangible benefits: are usually measured in terms of monthly or annual profits to the shop.
There are some tangible benefits that we are identified.

 Reduction of personnel expense: when the new system is implemented the number of
personnel will be reduced.
 Error reduction: workloads and errors are common in the existing system. Hence the new
system will avoid such problems and also the organization will save some amount of
money.
B) Intangible benefits: based on our assessment the intangible benefits are listed below
 Fasten decision making
 Information efficiency will increase
 Work load of the personnel will decrease
Cost can also classified as tangible cost and intangible

C) Tangible cost: are costs that can be measured in terms of money. Some of the tangible
costs are:-
 One time cost: this cost refers a cost associated with project initiation and development.
It includes new hardware and software and user training cost.
 Recurring: It refers a cost result from the on-going evaluation and use of the system. It
 Includes maintenance cost, printing, copy and stationery’s.

Roll No Resource item quantity Unit Total

price(birr) price(birr)
1 R-CD 2 75 150
2 flash disk 1 400 400
3 Paper and pen 1 150 150
4 Printing paper 80(page) 3 240
6 software 6 ------- Gain from free
internet
7 computer 1 25000 25000
8 Other(reserved) 600

4
 9 Total 26540

Table 1: Cost breakdown

D) Intangible cost: - those are a cost that cannot be measured in birr such as
 Members are so tiered when activities didn’t get done on time.
 Reduce team members moral

1.4.4 Political feasibility

We will develop a new system is not contradict or conflict with the politics of the
Current system. So we develop a new system by comparing the current situation of System rules
and regulations. So no situation exists that in our system conflicts with the current system.

1.4.5 Time feasibility (Time scheduling)

 It describes the time or duration required to complete this project, it shows division of
time for each activity. We use the Gantt chart for showing time scheduling.

Time schedule of project

3-May 22-Jun 11-Aug 30-Sep 19-Nov
re- system system implmen- testing
requirment gathering 5 quirment analysis design tation
system analysis 20gathering

system design 37
start
implmentation 45390 45397 45420
150 45471 45629
time
testing 8
inter- 5 20 37 150 8
val

Figure 1: Gantt chart

5
1.5 Task break dawn

Samrawit Dessi Eyerusalem Shibesh Yhalem

Task
Mossie Aweke Geremachew Ayalu
Taddele

Requirement     
gathering
&Project
planning
System analysis     
System design     
Interface design     
Implementation     
Testing and     
documentation
Table 2: Task Breakdown

1.6 Scope of the project

The system is applicable on:
 Automating customer record, book searching, report generating, updating system
 Managing user account
 Document upload
 Accurate way of recording and storing information into database.\
 Enabling to make daily report for the sales, rentals and returned books.
 Presence of centralized database and organized records.


6
1.7 Significance and Beneficiaries of the project

1.7.1 Significance of the project

The significance of an automated system for book sales and rentals at a Mega book store and
distribution center has several significances:-

 Improved Efficiency: this project streamline the process of managing book sales and
rentals, leading to increased efficiency in operations. It gets to faster transactions, reduced
errors, and improved customer service.
 Cost Savings: By automating processes such as inventory management, ordering, and
tracking sales, the Mega book store can potentially reduce costs associated with manual labor
and human error. This lead to cost savings and improved profitability for the business.
 Enhanced Customer Experience: our system provide customers with a seamless and
convenient experience when purchasing or renting books. Features such as online ordering,
self-service kiosks, and personalized recommendations enhance the overall customer
experience and satisfaction.
 Data Analysis and Insights: our automated system generates valuable data and insights on
customer preferences, sales trends, and inventory levels. This data used to make informed
business decisions, optimize inventory management, and tailor marketing strategies to better
meet customer needs.
 Competitive Advantage: By implementing an automated system for book sales and rentals,
the Mega book store gains a competitive edge in the market. The ability to offer efficient and
convenient services to customers attract new customers, retain existing ones, and
differentiate the business from competitors.

1.7.2 Target benefit of the project

Customer:

 The searching time will become minimized

 Capable of viewing what is announcement in the store through internet
 The customers ask their interest easily.
Employee:

7
  Reduce the workload of the employee.
 The searching time will become minimized
Manager:

 Workload will become minimized

 Easy to manage employees
System administrator:
 Workload will become minimized
 Will become capable of controlling the system easily.
Organizational perspective

 Data storage and retrieval system will become automated.

 Capable of introducing new coming Books through the website.
Team perspective

 Improve project development and communication skill

1.8 Methodology
The methodology used for this project is the Object Oriented Analysis and Design (OOAD).
Object oriented methods provide a set of techniques for analyzing, decomposing, and
modularizing software system architectures. It enhances key software quality factors of a system
and its constituent components. In general, systems evolve and functionality changes, but
objects and classes tend to remain stable over time.
We had used to discovery where a development team models and understands the requirements
of the system. And additionally analyze the functional requirements for a system.

1.8.1 Data collection techniques

The shop is a major means of data gathering and as well as a case study for the proposed system.
Since gathering the necessary data is important for the success of the project, hence, the
following data collection mechanism will be used.

 Observation: we had obtained the information about how the current system works by
visit (observe) current website of company and we will fulfil limited or restricted
functionality of system like online payment method…

8
  Questionnaire: we had get necessary information by ask question the customers and got
information by meet the employer and manager in cell phone.
 Document analysis: we had get information by reading or analysis literature document
about it.

1.8.2 Systems Analysis and Design (approach)

We had used iterative methodology to done our project. Iterative methodology in

Systems Analysis and Design (SAD) refers to an approach where the development
process is broken down into multiple iterations or cycles. Each iteration typically
involves a subset of the overall project requirements, with the goal of delivering a
working product incrementally. It allows for feedback, adjustments, and improvements
to be made throughout the development process based on user input and changing
requirements. We have selected this approach to got Key characteristics of iterative
methodology those are: - Incremental Development, Feedback Loop, and Adaptability,
Risk Management, Continuous Improvement and others

1.8.3 Development tools

Activity tools

Client side code HTML

platform Ms windows

Database server mysql

Web server Apache or xampp server

Server side scripting php

browsers Chrome, Firefox

9
 editors Ms excel

documentation Ms word 2010

User training Video player , ppt

Varied technologies As per the technical requirement in future

1.9 Testing procedures (types of testing used)

There are various type of testing procedures used to ensure the quality, functionality, and
performance of the system being developed. We will use two types such as:-

 Unit Testing: This type of testing focuses on individual components or modules of the
system. It is usually performed by the developer. We will use it to validate each unit of
the system performs as intended.

 Integration Testing: Integration testing verifies that different components or modules of

the system work together as expected. We will use it to test the interactions between
integrated units to ensure that they communicate and function correctly.

1.10 Implementation (Parallel/Partial/Direct)

We had involved a partial implementation strategy. This would entail gradually introducing the
automated system in specific areas or departments of the book store and distribution center while
still maintaining existing manual processes in other areas. By doing so, the organization
minimize disruptions to daily operations and allow for a smoother transition to the new system.
This partial implementation approach also allows for testing and refinement of the automated
system in real-world scenarios before full deployment, reducing the risk of widespread issues.
Additionally, it provides an opportunity for staff to become familiar with the new system in
stages, ensuring proper training and support can be provided as each phase is rolled out. As a

10
result, a partial implementation strategy for this project can help manage potential challenges and
optimize the overall success of the automated system.

1.10.1, Client Side Code

HOMEPAGE HTML CODE

<!DOCTYPE html>

<html>

<head>

<title>Online Book Shop</title>

<link href="project.css.css" rel="stylesheet">

<meta name="=viewport" content="width=device-width,initial-scale=1.0">

<link href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.2/css/all.min.css"
rel="stylesheet">

<script src="project.js"></script>

</head>

<body>

<header>

<div class="logo"> Mega Book Shop</div>

<a href=" Mega Book Shop"></a></div>

11
</div>

<nav>

<div class="hamburger-menu">

<div class="bar"></div>

<div class="bar"></div>

<div class="bar"></div>

</div>

<ul class="nav-links">

<li><a href="#"> Home</a></li>

<li><a href="#"> Catagories</a>

<div class="submenu" >

<ul>

<li><a href="technology.html"> Technology</a></li>

<li><a href="fiction.html"> Fiction</a></li>

<li><a href="history.html"> History</a></li>

</ul>

</div>

</li>

<li><a href="contactus.html"> Contact us</a></li>

<li><a href="about us.html"> About us</a></li>

12
 </ul>

<div class="search">

<input type="text" placeholder="search book">

<button type="submit">Go</button>

</div>

</nav>

</header>

<div class="description">

<h2 id="animated-text">Welcome to Mega Book Shop!</h2>

<p class="des">

Welcome to Mega Book Shop, your ultimate destination for a wide range of books.
Whether you're passionate about technology, engrossed in fictional worlds, or fascinated by
history, we have something for everyone. Our carefully curated collection ensures that you find
the perfect read every time.

</p>

<p class="des">

Browse through our categories, explore our latest arrivals, and enjoy a seamless shopping
experience from the comfort of your home. Feel free to reach out to us for any inquiries or
recommendations. Happy reading!

</p>

</div>

<div class="hero">

<div class="hero content">

13
 </div>

</div>

<p> Featured Books</p>

<div class="maincontent">

<div class="books">

<div class="book">

<img src="images/2 (1).jfif" alt="info">

<h4>price:200ETB</h4>

</div>

<div class="book">

<img src="images/2 (10).jfif" alt="book">

<h4> price:300ETB</h4>

</div>

<div class="book">

<img src="images/2 (11).jfif" alt="book">

<h4> price:320ETB</h4>

14
</div>

<div class="book">

<img src="images/2 (2).jfif" alt="book">

<h4> price:200ETB</h4>

</div>

<div class="book">

<img src="images/2 (3).jfif" alt="book">

<h4> price:100ETB</h4>

</div>

<div class="book">

<img src="images/2 (9).jfif" alt="book">

<h4> price:350ETB</h4>

</div>

<div class="book">

<img src="images/2 (5).jfif" alt="book">

<h4> price:300ETB</h4>

</div >

15
<div class="book">

<img src="images/2 (6).jfif" alt="book">

<h4> price:250ETB</h4>

</div>

<div class="book">

<img src="images/2 (8).jfif" alt="book">

<h4> price:300ETB</h4>

</div>

<div class="book">

<img src="images/2 (7).jfif" alt="book">

<h4> price:280ETB</h4>

</div >

<div class="book">

<img src="images/f4.webp" alt="book">

<h4> price:270ETB</h4>

</div >

<div class="book">

16
 <img src="images/f10.jfif" alt="book">

<h4> price:240ETB</h4>

</div >

</div>

</div>

<p class="des">

Once you've found the books you love, come visit us at:

</p>

</div>

<footer>

<div class="footer-content">

<div class="socials">

<a href="https://www.facebook.com/yourpage" class="social-icon"><i class="fab fa-

facebook"></i></a>

<a href="https://www.instagram.com/yourpage" class="social-icon"><i class="fab fa-

instagram"></i></a>

<a href="https://www.twitter.com/yourpage" class="social-icon"><i class="fab fa-

twitter"></i></a>

<a href="https //www.telegram.com/yourpage" class="social-icon"><i class="fab fa-

telegram"></i></a>

</div>

17
 </div>

<div class="contact-info">

<p class="des"><strong>Address:</strong> Bole, DebreMarkos</p>

<p claas="des"><strong><i class="fas fa-phone"></i>Phone:</strong>

+251918361802</p>

</div>

<div class="footer-bottom">

<p class="des">&copy; 2024 Mega Book Shop. All rights reserved.</p>

</div>

</footer>

</body>

</html>

HOMEPAGE CSS CODE

*{

padding: 0px;

margin: 0px;

box-sizing: border-box;

font-family: arial;

18
}

body{

box-sizing: border-box;

font-family: sans-serif;

min-height: 100vh;

header{

color:white;

background:rgb(2, 59, 59);

padding:20px 60px;

display:flex;

justify-content: space-between;

align-items: center;

position:sticky;

top:0;

z-index: 100;

.logo{

font-size: 20px;

font-weight: bold;

19
text-transform: uppercase;

margin-right: 4px;

.logo a{

color: white;

text-decoration: none;

margin-right: 5px;

nav{

display:flex;

align-items: center;

.nav-links{

display:flex;

align-items: center;

justify-content: center;

.nav-links li{

margin-left: 30px;

list-style: none;

20
}

.nav-links li a{

color:white;

text-decoration: none;

font-size: 20px;

font-weight: bold;

transition: 0.4s ease;

border-radius: 2px;

.nav-links li a:hover{

color:white;

background-color:green;

border-radius: 0px;

.nav-links li a:active{

background-color: darkblue;

color:white;

.nav-links {

list-style-type: none;

21
 margin: 0;

padding: 0;

li {

position: relative;

display: inline-block;

li a {

text-decoration: none;

color: white;

padding: 10px 15px;

display: block;

.submenu {

display: none;

position: absolute;

top: 100%;

left: 0;

22
 background-color:rgb(4, 92, 92);

box-shadow: 0 8px 10px rgba(0,0,0,0.2);

z-index: 1;

.nav-links li:hover .submenu {

display: block;

.submenu ul {

list-style-type: none;

margin: 0;

padding: 0;

display: block;

.submenu li {

padding: 8px 16px;

.submenu li a {

23
 text-decoration: none;

color: white;

display: block;

padding: 8px 16px;

.submenu li a:hover {

background-color:rgb(4, 82, 4);

.search{

position:relative;

margin-left: 25px;

.search input{

padding: 10px;

border:none;

border-radius: 20px;

background-color: #444;

color:#fff;

24
}

.search button{

position: absolute;

top:0;

right:0;

padding:10px;

border: none;

border-radius: 15px;

background-color:white;

color:#444;

font-weight: bold;

.hamburger-menu {

display: none; /* Hide by default on larger screens */

cursor: pointer;

.bar {

width: 25px;

25
 height: 3px;

background-color: #fff;

margin: 4px 0;

transition: transform 0.3s ease;

@media (max-width: 768px) {

.nav-links {

display: none;

flex-direction: column;

align-items: flex-start;

width: 100%;

background-color: #333;

position: absolute;

top: 60px;

left: 0;

padding: 10px;

z-index: 1;

.nav-links.active {

26
 display: flex;

.nav-links li {

margin: 10px 0;

.hamburger-menu {

display: flex;

align-items: center;

media (max-width: 768px) {

.hamburger-menu {

display: block; /* Show on smaller screens */

cursor: pointer;

position: fixed;

top: 20px;

right: 20px;

z-index: 1500;

27
 .hamburger-menu .bar {

width: 25px;

height: 3px;

background-color: #333;

margin: 5px 0;

transition: 0.4s;

.hamburger-menu.active .bar:nth-child(1) {

transform: translateY(8px) rotate(45deg);

.hamburger-menu.active .bar:nth-child(2) {

opacity: 0;

.hamburger-menu.active .bar:nth-child(3) {

transform: translateY(-8px) rotate(-45deg);

28
h2{

text-align: center;

font-size: 40px;

text-transform: uppercase;

padding-top: 15px;

text-shadow: 2px 5px;

p{

text-align: center;

font-size:30px;

text-decoration: underline;

.description {

background-color: #f9f9f9;

padding: 20px;

margin: 20px 0;

border-radius: 8px;

box-shadow: 0 0 10px rgba(0, 0, 0, 0.1);

29
}

.description h2 {

font-size: 2.5rem;

color: #333;

margin-bottom: 15px;

.des{

font-size: 25px;

text-decoration: none;

@keyframes moveLeftRight {

0%, 100% { transform: translateX(0); }

50% { transform: translateX(20px); }

/* Apply animation to the h2 element */

#animated-text {

animation: moveLeftRight 2s ease-in-out infinite alternate;

color: blue;

30
 }

.p1{

width:200px;

height:230px;

display:inline-block;

border-radius:10px;

padding:15px 25px;

box-sizing: border-box;

cursor:pointer;

margin:10px 15px;

background-image: url("ph11.jpg");

background-position: center;

background-size: cover;

transform: translatey(-10px);

@media (max-width: 768px) {

nav {

flex-direction: column;

31
 align-items: flex-start;

.search {

width: 100%;

margin-top: 10px;

nav ul {

flex-direction: column;

width: 100%;

nav ul li {

margin: 10px 0;

.maincontent {

flex-direction: column;

padding: 10px;

32
 .books {

flex-direction: column;

align-items: center;

.book {

width: 80%;

margin: 10px 0;

@media (max-width: 1120px) {

.book {

width: 45%; /* Adjust for smaller screens */

@media (max-width: 980px) {

.book {

width: 100%; /* Full width on smaller devices */

33
}

.maincontent{

background-image: url(images/1.jpg);

padding:30px;

border-radius: 10px;

box-shadow: 0px 0px 10px rgba(0,0,0,0.2);

.books{

display:grid;

grid-template-columns: repeat(auto-fill,minmax(250px,1fr));

grid-gap:10px;

margin-top: 20px;

.book{

display:felx;

flex-direction: column;

align-items:center;

text-align: center;

34
padding: 10px;

.book img{

max-width: 100%;

margin-bottom:10px;

height: auto;

border-radius: 5px;

transition: transform 0.3s ease;

.book img:hover{

transform: translatey(-50px);

@media (max-width: 768px) {

.books {

grid-template-columns: 1fr; /* Display books in a single column on smaller screens */

h3{

35
 text-align: center;

font-size: 20px;

margin-top: 10px;

padding-top: 15px;

padding-bottom: 20;

text-decoration: dashed;

h4{

color:white;

footer {

background-color:rgb(5, 88, 88);

color: #fff;

padding: 20px 0;

.footer-content {

max-width: 1200px;

margin: 0 auto;

display: flex;

justify-content: space-between;

36
 align-items: center;

.socials {

font-size: 30px;

text-align: center;

.socials a {

color: #fff;

text-decoration: none;

margin: 0 10px;

transition: color 0.3s ease; /* Smooth transition for color change */

text-align: center;

.socials a:hover {

color: #ffd700; /* Change color on hover */

.contact-info {

37
 text-align: left;

.contact-info p {

margin: 5px 0;

.footer-bottom {

margin-top: 20px;

font-size: 18px;

.fas.fa-phone {

margin-right: 5px;

TECHNOLOGY BOOK HTML CODE

<!DOCTYPE html>

<html>

<head>

<link href="technology.css" rel="stylesheet">

</head>

<body>

38
 <p> Here Are our Available Technology Books</p>

<aside>

<h2 >About This Page</h2>

<p class="asa">This page showcases a selection of technology books available at Mega

Book Shop. Each book is accompanied by its price in Ethiopian Birr (ETB). Explore our
collection and find the perfect book for your interests!</p>

</aside>

<div class="maincontent">

<div class="books">

<div class="book">

<img src="images/tt1.jpg" alt="info">

<h4>Price:180ETB</h4>

</div>

<div class="book">

<img src="images/tt3.jpg" alt="book">

<h4>Price:260ETB</h4>

</div>

<div class="book">

<img src="images/tt4.jpg" alt="book">

39
<h4> price:340ETB</h4>

</div>

<div class="book">

<img src="images/tt5.jpg" alt="book">

<h4> price:300ETB</h4>

</div>

<div class="book">

<img src="images/tt6.jpg" alt="book">

<h4> price:290ETB</h4>

</div>

<div class="book">

<img src="images/tt8.jpg" alt="book">

<h4> price:250ETB</h4>

</div>

<div class="book">

<img src="images/t22.jpg" alt="book">

40
 <h4> price:275ETB</h4>

</div >

<div class="book">

<img src="images/t13.jpg" alt="book">

<h4> price:350ETB</h4>

</div>

</div>

<footer class="footer">

<p class="p1">© 2024 Mega Book Shop. All rights reserved.</p>

</footer>

</div>

</body>

</html>

TECHNOLOGY BOOK CSS CODE

.maincontent{

background-image: url(images/1.jpg);

padding:30px;

border-radius: 10px;

box-shadow: 0px 0px 10px rgba(0,0,0,0.2);

41
 }

aside {

background-color: #fff;

padding: 20px;

box-shadow: 0 0 10px rgba(0, 0, 0, 0.1);

width: 100%;

aside h2 {

font-size: 1.5em;

margin-top: 0;

color: #333;

.asa {

color: #666;

font-size: 25px;

background-color: white;

.books{

display:grid;

42
 grid-template-columns: repeat(auto-fill,minmax(300px,1fr));

grid-gap:5px;

margin-top: 20px;

.book{

display:felx;

flex-direction: column;

align-items:center;

text-align: center;

.book img{

max-width: 100%;

margin-bottom:10px;

.book img:hover{

transform: translatey(-10px);

@media (max-width: 1120px) {

43
 .books {

flex-direction: column;

.book {

width: 100%;

h3{

text-align: center;

font-size: 20px;

margin-top: 10px;

padding-top: 15px;

padding-bottom: 20;

text-decoration: dashed;

h4{

color:white;

font-size: 20px;

p{

text-align: center;

44
 font-weight: bold;

font-size: 50px;

background-color: brown;

color:white

.footer {

background-color:rgb(5, 88, 88);

color: #fff;

padding: 20px 0;

text-align: center;

.p1{

color:white;

background-color: rgb(5, 88, 88);

font-size: 20px;

FICITION BOOK HTML AND INLINE CSS CODE

<!DOCTYPE html>

<html>

45
 <head>

<style>

.maincontent{

background-image: url(images/1.jpg);

padding:30px;

border-radius: 10px;

box-shadow: 0px 0px 10px rgba(0,0,0,0.2);

.books{

display:grid;

grid-template-columns: repeat(auto-fill,minmax(350px,1fr));

grid-gap:5px;

margin-top: 20px;

.book{

display:felx;

flex-direction: column;

align-items:center;

text-align: center;

46
.book img{

max-width: 60%;

margin-bottom:10px;

.book img:hover{

transform: translatey(-10px);

h3{

text-align: center;

font-size: 20px;

margin-top: 10px;

padding-top: 15px;

padding-bottom: 20;

text-decoration: dashed;

h4{

color:white;

font-size: 20px;

47
 p{

text-align: center;

font-weight: bold;

font-size: 50px;

background-color: brown;

color:white

</style>

</head>

<p> Available fiction Books</p>

<div class="maincontent">

<div class="books">

<div class="book">

<img src="images/ff1.jpg" alt="info">

<h4>price:230ETB</h4>

</div>

<div class="book">

<img src="images/ff3.jpg" alt="book">

48
<h4> price:400ETB</h4>

</div>

<div class="book">

<img src="images/ff4.jpg" alt="book">

<h4> price:350ETB</h4>

</div>

<div class="book">

<img src="images/ff5.jpg" alt="book">

<h4> price:370ETB</h4>

</div>

<div class="book">

<img src="images/ff6.jpg" alt="book">

<h4> price:340ETB</h4>

</div>

<div class="book">

<img src="images/ff7.jpg" alt="book">

<h4> price:310ETB</h4>

49
 </div>

<div class="book">

<img src="images/ff8.jpg" alt="book">

<h4> price:180ETB</h4>

</div >

<div class="book">

<img src="images/ff16.jpg" alt="book">

<h4> price:380ETB</h4>

</div>

<div class="book">

<img src="images/ff17.jpg" alt="book">

<h4> price:240ETB</h4>

</div>

</div >

</div>

</div>

50
</body>

</html>

HISTORY BOOKS HTML CODE

<!DOCTYPE html>

<html>

<head>

<link href="histrory.css" rel="stylesheet">

</head>

<body>

<p> Here Are our Available Technology Books</p>

<div class="maincontent">

<div class="books">

<div class="book">

<img src="images/h2.webp" alt="info">

<h4>price:400ETB</h4>

</div>

<div class="book">

<img src="images/h3.webp" alt="book">

<h4> price:270ETB</h4>

51
</div>

<div class="book">

<img src="images/h11.webp" alt="book">

<h4> price:420ETB</h4>

</div>

<div class="book">

<img src="images/h4.webp" alt="book">

<h4> price:300ETB</h4>

</div>

<div class="book">

<img src="images/h6.webp" alt="book">

<h4> price:360ETB</h4>

</div>

<div class="book">

<img src="images/h7.webp" alt="book">

<h4> price:340ETB</h4>

</div>

52
<div class="book">

<img src="images/h8.webp" alt="book">

<h4> price:310ETB</h4>

</div >

<div class="book">

<img src="images/h9.webp" alt="book">

<h4> price:240ETB</h4>

</div>

<div class="book">

<img src="images/h10.webp" alt="book">

<h4> price:390ETB</h4>

</div>

<div class="book">

<img src="images/h5.webp" alt="book">

<h4> price:220ETB</h4>

</div >

<div class="book">

53
 <img src="images/h20.webp" alt="book">

<h4> price:300ETB</h4>

</div >

<div class="book">

<img src="images/h21.webp" alt="book">

<h4> price:330ETB</h4>

</div >

</div>

</div>

</body>

</html>

HISTORY BOOKS CSS CODE

.maincontent{

background-image: url(images/1.jpg);

padding:30px;

border-radius: 10px;

54
 box-shadow: 0px 0px 10px rgba(0,0,0,0.2);

.books{

display:grid;

grid-template-columns: repeat(auto-fill,minmax(300px,1fr));

grid-gap:3px;

margin-top: 20px;

.book{

display:felx;

flex-direction: column;

align-items:center;

text-align: center;

.book img{

max-width: 100%;

margin-bottom:10px;

.book img:hover{

55
 transform: translatey(-10px);

h3{

text-align: center;

font-size: 20px;

margin-top: 10px;

padding-top: 15px;

padding-bottom: 20;

text-decoration: dashed;

h4{

color:white;

font-size: 20pxS;

p{

text-align: center;

font-weight: bold;

font-size: 50px;

background-color: brown;

color:white

56
 }

“ABOUTS US “ HTML AND INLINE CSS CODE

<!DOCTYPE html>

<html lang="en">

<head>

<meta charset="UTF-8">

<meta name="viewport" content="width=device-width, initial-scale=1.0">

<title>About Us - Mega book Shop</title>

<style>

body {

font-family: Arial, sans-serif;

line-height: 1.6;

margin: 20px;

background-image: url(images/1.jpg);

color:white;

.container {

max-width: 800px;

margin: auto;

h1, h2 {

57
 color: white;

text-align: center;

p{

margin-bottom: 20px;

color:white;

</style>

</head>

<body>

<div class="container">

<header>

<h1>Welcome to Mega Book Shop</h1>

</header>

<section>

<h2>Our Story</h2>

<p>At Mega Book Shop, we believe in the transformative power of books. Nestled in the
heart of DebreMarkos, we have been proudly serving book lovers since 2015E.c. Our passion for
literature drives us to curate a diverse collection that caters to every taste and interest.</p>

<p>Founded by avid readers Aster Nega, Mega Bookshoop began as a humble corner
bookstore with a vision to connect people with stories that inspire, educate, and entertain. Over
the years, we have grown into a cherished community hub where bookworms of all ages gather
to explore new worlds between the pages of our carefully selected books.</p>

58
 </section>

<section>

<h2>What Sets Us Apart</h2>

<ul>

<li><strong>Handpicked Selection:</strong> Every book on our shelves is handpicked

by our knowledgeable team, ensuring quality reads that span genres and cultures.</li>

<li><strong>Personalized Service:</strong> Whether you're seeking a bestseller or a

hidden gem, our friendly staff is here to help you discover your next favorite book.</li>

<li><strong>Community Engagement:</strong> We host book clubs, author readings,

and literary events that foster a love for reading and discussion among our patrons.</li>

</ul>

</section>

<section>

<h2>Our Commitment</h2>

<p>At Mega book Shop, we are committed to promoting literacy, supporting local
authors, and celebrating the written word. By shopping with us, you not only enrich your own
reading experience but also contribute to the vibrancy of our literary community.</p>

</section>

<section>

<h2>Visit Us</h2>

<p>We invite you to visit Mega Book Shop and explore our shelves. Whether you're
searching for a classic novel, the latest bestseller, or a gift for a fellow book lover, we look
forward to helping you find exactly what you need.</p>

59
 </section>

<footer>

<p>Thank you for being part of our journey. Happy reading!</p>

</footer>

</div>

</body>

</html>

YOUR CONTACT HTML AND INLINE CSS CODE

<!DOCTYPE html>

<html lang="en">

<head>

<meta charset="UTF-8">

<meta name="viewport" content="width=device-width, initial-scale=1.0">

<title>Contact Us</title>

<style>

body {

font-family: Arial, sans-serif;

margin: 0;

padding: 0;

background-image: url(images/1.jpg);

60
.container {

width: 80%;

margin: auto;

overflow: hidden;

#main-header {

background-color:rgb(2, 49, 49);

color: #fff;

padding-top: 30px;

min-height: 70px;

border-bottom: #77aaff 3px solid;

#main-header h1 {

text-align: center;

text-transform: uppercase;

margin: 0;

font-size: 24px;

#contact-form {

padding: 20px;

61
 margin-top: 30px;

border-radius: 5px;

box-shadow: 0 0 10px rgba(0,0,0,0.1);

.form-group {

margin-bottom: 15px;

.form-group label {

display: block;

margin-bottom: 5px;

.form-group input,

.form-group textarea {

width:40%;

padding: 10px;

border: 1px solid #ddd;

border-radius: 5px;

label{

color:white;

62
}

.form-group button {

display: inline-block;

background: blue;

color: #fff;

padding: 5px 5px;

border: none;

border-radius: 2px;

cursor: pointer;

font-size: 20px;

.form-group button:hover {

background: red;

#address {

background: #fff;

padding: 20px;

margin-top: 30px;

border-radius: 5px;

box-shadow: 0 0 10px rgba(0,0,0,0.1);

63
 h3{

color:#ddd;

social-icons {

list-style: none;

padding: 0;

display: flex;

gap: 10px;

.social-icons li {

display: inline;

.social-icons a {

text-decoration: none;

color: white; /* Set to the desired color */

font-size: 18px; /* Adjust as needed */

padding: 10px;

border-radius: 50%;

transition: background-color 0.3s, color 0.3s;

64
}

.social-icons a:hover {

background-color: #f0f0f0; /* Set to the desired hover background color */

color: #0073e6; /* Set to the desired hover text color */

</style>

</head>

<body>

<header id="main-header">

<div class="container">

<h1>Contact Us</h1>

</div>

</header>

<div class="container">

<section id="contact-form">

<form action="submit.php" method="POST">

<div class="form-group">

<label for="name">Name:</label>

<input type="text" id="name" name="name" required>

</div>

65
 <div class="form-group">

<label for="email">Email:</label>

<input type="email" id="email" name="email" required>

</div>

<div class="form-group">

<label for="message">Message:</label>

<textarea id="message" name="message" rows="5" required></textarea>

</div>

<div class="form-group">

<button type="submit">Submit</button>

</div>

</form>

</section>

<section id="social-media">

<h3>Follow Us</h3>

<ul class="social-icons">

<li><a href="https://www.facebook.com/yourpage"
target="_blank">Facebook</a></li>

<li><a href="https://www.twitter.com/yourpage" target="_blank">Twitter</a></li>

<li><a href="https://www.instagram.com/yourpage"
target="_blank">Instagram</a></li>

66
 <li><a href="https://www.linkedin.com/yourpage"
target="_blank">LinkedIn</a></li>

</ul>

</section>

</div>

<footer class="footer">

<p class="p1">© 2024 Mega Book Shop. All rights reserved.</p>

</footer>

</div>

</body>

</html>

1.10.2, SERVER SIDE CODE

PHP CODE

<?php

$conn = mysqli_connect("localhost", "root", "","WEBPROGRAMMING");

// Check connection

if($conn === false){

die("ERROR: Could not connect. " . mysqli_connect_error());

echo "Connect Successfully " ;

// sql to create table

67
$sql = "CREATE TABLE CONTACTPAGE (

name VARCHAR(30) NOT NULL,

email VARCHAR(20)NOT NULL,

message char(80)NOT NULL,

)";

if(mysqli_query($conn,$sql))

echo"table created Successfully";

else

echo "ERROR: Could not able to execute $sql. " .

mysqli_error($conn);

$conn->close();

1.11 Limitation of the project

The system has limitations on:

 The limitation of our project is only use for book item for mega organization.

68
  Not support impaired person.
 Support only English and Amharic language.

1.12 Risks & contingencies

The project faces several risks that require proactive contingency planning. One key risk is the
potential for technical issues during system development and implementation, such as software
bugs or compatibility problems with existing systems. To address this, the project should
implement thorough testing and quality assurance processes to identify and resolve any technical
challenges before deployment. Another risk is the possibility of resistance to change from store
staff or customers who may be accustomed to manual processes or traditional sales methods. A
contingency plan for this risk could involve providing comprehensive training and support to
ensure a smooth transition to the automated system, as well as ongoing communication to
address stakeholder concerns and feedback.

Data security and privacy are also critical considerations, as there is a risk of breaches or
unauthorized access to customer information stored in the system. To mitigate this, the project
should implement robust security measures, such as encryption protocols and access controls, to
protect sensitive data and comply with relevant data protection regulations.

Furthermore, external factors like changes in market trends or economic conditions could pose a
risk to the project's success. A contingency plan for this risk could involve conducting regular
market analysis and adapting the system's features and offerings to meet evolving customer
needs and preferences.

1.13 Assumptions and Constraints

The key assumptions for this project include the active engagement and availability of
stakeholders, such as store managers, sales staff, and IT personnel, for requirements gathering,
testing, and feedback sessions. It is also assumed that the technology infrastructure, including
hardware, software, and network connectivity, will be stable and capable of supporting the
system's requirements.

69
The project may face several constraints, including budget constraints that limit the financial
resources available for system development and implementation, potentially impacting the scope
of features and functionalities that can be included. Time constraints with fixed deadlines for
system deployment and operationalization could also influence the project schedule and delivery
timeline. Technical constraints, such as compatibility requirements with existing systems or
limitations on available technology platforms, may restrict the selection of software tools and
development approaches. Resource constraints, such as limitations on skilled personnel or IT
support, may impact the project's progress and successful completion. Lastly, scope constraints
may define the boundaries of the system's capabilities and features based on business priorities
and project objectives, potentially limiting the extent of customization or integration with other
systems. Addressing these assumptions and constraints proactively can help ensure the
successful execution of the project and alignment with stakeholder expectations.

1.14 Team composition

Project title System for mega publishing and distribution P.L.C

Prepared s.no name Id responsibility
by 1 Samirawit Mossie …. …….…...1404160 analysis and implementation
2 Eyerusalem Giremachew…. …...1403837 design and implementation
3 Dessie Aweke…. ……………....1405913 data analysis and implementation

70
 4 Shibesh Taddele .……………….1404221 data gather and documentation
5 Yhalem Ayalu.……………….….1404472 data gather and documentation
date 20/11/2016 E.C
instructor Temesgen

CHAPTER TWO

Description of the Existing System

2.1 Introduction of Existing System

The system that is currently working In Mega has different manual oriented functions such as
manually storing Books on the shelf. Employees are also records the Books manually, which are

71
on rental or sales and report the recording data to the manager of the organization. The
procedures that the organization follows for executing daily tasks are described below:

Input

 Request books by customers

 If the customer want to rent the employee registers customer’s name and address
 Accept customers id and for payment
 If the customer want to buy the employee tells the price

Process: How the system transforms input to output.

 The employee accept customers request

 The employee also search books that customers want
 The customer pay the fee to the employee

Out put

 Finally the customer can receive the book that he/she want to rent or buy.

2.2 Players in the existing system

The Mega Book Store and Distribution Center currently operates a manual system for managing
book sales and rentals. This traditional approach involves various processes and procedures
carried out by store staff, including customer service representatives, sales associates, inventory
management personnel, store managers, and IT support staff. The customer service
representatives are the frontline employees who interact directly with customers. They assist
customers in selecting books, process sales and rental transactions, and handle customer inquiries
and concerns. The sales associates work alongside the customer service representatives,
providing additional support and expertise to guide customers through the book selection
process, as well as maintaining the physical book displays.

72
The inventory management personnel are responsible for overseeing the store's book inventory.
They track the movement of books, monitor stock levels, and coordinate the replenishment of
titles from the distribution center. This ensures the store has the right books in stock to meet
customer demand. The store managers oversee the overall operations of the Mega Book Store,
including the work of the customer service representatives, sales associates, and inventory
management staff. They ensure the manual systems and processes are running smoothly and
make strategic decisions regarding product selection, pricing, and store policies. Finally, the IT
support staff provides technical assistance and maintenance for the store's existing systems, such
as the point-of-sale terminals and inventory management software. Their role is crucial in
maintaining the functionality of the manual systems and troubleshooting any technical issues.
Together, these key players work collaboratively to deliver a seamless book sales and rental
experience for customers within the constraints of the existing manual system.

2.3 Major functions/activities in the existing system

The existing manual system at the Mega Book Store and Distribution Center involves several
key functions and activities, including inputs, processes, and outputs. The primary input in this
system is the customer's request for purchasing or renting a book. Customers physically browse
the store's shelves, select the desired titles, and approach the sales counter. At this stage, the
customer service representatives gather the necessary information, such as the customer's details
and the specific book(s) they wish to acquire. The core processes within the manual system
involve the various actions taken by the store staff to fulfill the customer's request. This includes
manually retrieving the selected book(s) from the inventory, processing the sales or rental
transaction, and handling the payment. The inventory management personnel also play a crucial
role in this process, as they track the movement of books, update stock levels, and ensure the
timely replenishment of titles from the distribution center.

73
The key outputs of the manual system include the physical provision of the book(s) to the
customer, either through a sale or rental. The customer service representatives also provide the
customer with a physical receipt, which serves as a record of the transaction. Additionally, the
store generates various internal reports and records, such as sales logs, rental histories, and
inventory reports, to support the overall management and decision-making processes.
Throughout these functions and activities, the store staff, including the customer service
representatives, sales associates, inventory management personnel, and store managers, work
together to deliver a seamless customer experience and maintain the efficient operation of the
Mega Book Store's manual system.

2.4 Business rules

 Business Rules for the Existing Manual System at Mega Book Store:-
1, all book transactions, including sales and rentals, must be processed through the physical sales
counter. Customers are not permitted to self-checkout or complete transactions without the
involvement of customer service representatives.

2, the store's pricing structure must be accurately applied by customer service representatives.
This includes the predetermined prices for book purchases and rental fees, as well as any
applicable discounts or promotional offers.

3, for book rentals, customers are required to provide valid identification and contact
information. They are responsible for the safe return of rented books within the specified time
frame. Late returns or damaged books may result in additional fees or penalties.

4. Inventory management is governed by strict policies. The store's inventory personnel must
regularly update physical stock records, track the movement of books, and ensure that popular
titles are readily available to meet customer demand. Reordering and replenishment processes
are also based on predefined thresholds and procedures.

74
5, The Mega Book Store has established security and record-keeping protocols within the manual
system. All sales and rental transactions are recorded in physical logs, and customer information
is securely stored. Cash handling and reconciliation processes are also strictly followed to
maintain financial accountability.

2.5 Report generated in the existing system

The Mega Book Store and Distribution Center's existing manual system generates a variety of
reports to support the overall management and decision-making processes. These reports provide
valuable insights into the store's operations, customer behavior, and inventory performance. One
of the key reports is the daily sales log, which records all book purchases and rental transactions
that occurred during the business day. This report includes details such as the customer's name,
the titles of the books sold or rented, the transaction date and time, and the total revenue
generated. This information is crucial for tracking sales trends, monitoring cash flow, and
identifying popular book titles. The store also generates customer rental history reports, which
provide a comprehensive record of each customer's book rental activity. This includes the titles
they have rented, the rental dates, and the return status of the books. These reports assist the
customer service representatives in managing customer accounts, identifying late returns, and
ensuring the timely return of rented books. Furthermore, the manual system produces various
financial reports, such as daily cash reconciliation statements and monthly sales summaries.
These reports help the store managers monitor the financial performance of the Mega Book
Store, track revenue trends, and identify any discrepancies or areas for improvement. All of these
reports are maintained in physical, paper-based formats, as the existing manual system does not
incorporate any digital or automated reporting capabilities.

2.6 Forms and other documents of the existing systems

75
2.7 Bottlenecks of the existing system

2.7.1 Performance (Response Time)

The existing manual system at the Mega Book Store and Distribution Center often experiences
slow response times, particularly during peak customer traffic periods. The reliance on physical
paperwork and the need for customer service representatives to manually process each
transaction can lead to lengthy wait times for customers, as well as delays in completing essential
tasks like inventory management and reporting.

2.7.2 Input (Inaccurate/Redundant/Inflexible) and Output (Inaccurate)

The manual system's heavy reliance on handwritten forms and documents introduces the
potential for human error and inaccuracies in the input of customer, inventory, and financial data.
Additionally, the lack of integration between different processes and the need for redundant data
entry can lead to inconsistencies and discrepancies in the overall system.

2.7.3 Security and Controls

The paper-based nature of the existing manual system presents challenges in terms of data
security and control. The physical storage and handling of sensitive customer information, as
well as the potential for misplaced or lost documentation, can expose the store to risks such as
data breaches and unauthorized access. The manual system also lacks robust audit trails and
control mechanisms to ensure the integrity of transactions and records.

2.7.4 Efficiency
The manual system's reliance on physical processes and paperwork can significantly impact the
overall efficiency of the Mega Book Store's operations. Tasks such as inventory management,
reporting, and customer account management require a substantial amount of manual effort and
time, which can limit the store's ability to respond quickly to changing market conditions and
customer needs.

2.7.5 Scalability
As the Mega Book Store and Distribution Center continues to expand its operations, the existing
manual system may struggle to scale effectively. The store's growth in terms of customer base,

76
inventory, and transaction volume could exacerbate the existing bottlenecks, leading to further
delays, errors, and operational challenges.

2.8 Practices to be preserved

Despite the various bottlenecks identified in the existing manual system, the Mega Book Store
has developed several practices and processes that have served the business well and should be
preserved in any future system upgrades or transformations. One of the key practices to be
preserved is the personal customer service approach. The store's customer service representatives
have developed strong relationships with regular customers and are adept at providing
personalized attention and support throughout the sales and rental processes. This high-touch,
personalized service has been a significant factor in the store's ability to build customer loyalty
and maintain a competitive edge in the local market. Another practice to be preserved is the
store's comprehensive documentation and record-keeping procedures. The detailed sales receipts,
rental agreements, inventory logs, and customer account records provide a robust paper trail that
helps the store maintain accurate financial records, track inventory, and resolve any customer
disputes or issues that may arise. This level of documentation has been essential in ensuring the
integrity and accountability of the store's operations.

The Mega Book Store's inventory management practices, including the use of the book order
forms and receiving/inspection procedures, have also proven to be effective in maintaining an
accurate and well-stocked inventory. These processes help the store to anticipate customer
demand, minimize stock outs, and ensure the timely replenishment of popular book titles.

2.9 Proposed solution for the new system that address problems of
the existing system
To address the limitations of the existing manual system, Mega Book Store should implement a
comprehensive, technology-driven solution that can streamline operations and enhance
efficiency, accuracy, and customer experience. At the heart of this proposed solution is a robust,
integrated point-of-sale (POS) system that can handle all aspects of book sales and rentals. The
new POS system should be designed to automate and digitize key processes, such as customer
account management, inventory tracking, and financial reporting. It should feature a user-
friendly interface that allows customer service representatives to quickly and accurately process

77
transactions, returns, and account updates. By integrating with a centralized customer database,
the system can maintain detailed customer profiles and transaction histories, reducing redundant
data entry and improving record accuracy. To address performance and response time issues, the
POS system should be equipped with reliable infrastructure, including high-speed internet,
secure cloud storage, and efficient data processing capabilities. This will enable the system to
handle increased customer traffic and transactions without compromising the user experience.

The proposed solution should also incorporate advanced inventory management functionalities,
including automated reordering, real-time stock level tracking, and seamless integration with the
distribution center's systems. This will help the store maintain optimal inventory levels,
anticipate customer demand, and minimize stock outs and delays. Furthermore, the new system
should prioritize data security and control mechanisms, such as role-based access controls, audit
trails, and encrypted data storage, to protect sensitive customer and financial information and
mitigate the risks associated with the existing manual system.

2.10 Requirements of the Proposed System

2.10.1 Functional Requirements

 Performance Requirements: The system able to handle a high volume of transactions,
process data quickly, and provide real-time updates to ensure smooth and efficient
operations. It able to accommodate peak customer traffic and demand without
compromising performance or response times.
 Process Requirements: The system automate and streamline key business processes,
such as customer account management, inventory tracking, order fulfillment, and
financial reporting. It seamlessly integrates these processes to improve overall workflow
and productivity.
 Input-related Requirements: The system provides user-friendly interfaces for customer
service representatives to quickly and accurately enter sales, rental, and customer
information. It also supports seamless integration with the distribution center's systems to
enable efficient inventory management and order processing.

78
  Output-related Requirements: The system generates comprehensive reports, invoices,
and customer-facing documents that are easy to understand and navigate. It should also
provide real-time visibility into key performance metrics, inventory levels, and financial
data to support informed decision-making.
 Storage-related Requirements: The system offer secure, scalable, and reliable data
storage solutions, such as cloud-based platforms, to maintain customer records,
transaction histories, and other critical business information. Robust backup and recovery
mechanisms should be in place to ensure data integrity and business continuity.

2.10.2 Non-functional Requirements

 Performance: The system designed to handle increased transaction volumes and user
traffic without compromising response times or system stability. It able to scale up as the
business grows and adapt to changing customer and market demands.
 User Interface: The system's user interface intuitive, visually appealing, and easy to
navigate for customer service representatives. It minimizes training requirements and
enables efficient task completion.
 Security and Access Permissions: The system implements robust security measures,
including role-based access controls, multi-factor authentication, and data encryption, to
protect sensitive customer and financial information. It also maintains detailed audit trails
to ensure accountability and compliance.
 Backup and Recovery: The system have a comprehensive backup and disaster recovery
plan in place to safeguard critical data and ensure business continuity in the event of
system failures or other unforeseen disruptions.
 Resources: The system designed and implemented with the necessary hardware,
software, and human resources to ensure its long-term sustainability and effective
maintenance. This may include infrastructure upgrades, software licensing, and the
recruitment and training of IT support staff.

79
 Chapter Three: System Analysis

3.1 Introduction

3.2 System Requirement Specifications (SRS)

80
3.2.1 Use case diagrams
A use case diagram at its simplest is a representation of a user's interaction with the system that

Shows the relationship between the user and the different use cases in which the user is involved.

A use case diagram can identify the different types of users of a system and the different use case
and will often be accompanied by other types of diagrams as well.

81
82
3.2.2 Use case documentation
Use Case 01 Login

Use case name Login

Use case id UC 01
Actor Employee ,manager and system administrator
Description This allow to identify system user and access system
functionality
Precondition Users must have user name and password

Work flow 1. The system should be started and the user clicks the login link.

2. The user fills his/her user name and password.

3. Click login button

4. The system checks the validity of the user name and

password.A1

5. The system displays the required page.

A1 The system displays error message and redirects to the login

form.

Post condition System transfer control to user main required page to precede
actions.

Table 3: System Use Case for Login

Use case 02 Record borrower

Use case name Record book/and user data

Use case id UC 02
Actor Employee
Description This use case used to record full information about customers and
their interest.
Precondition Being employee

Work flow 1. The employee must login to the employee main page and clicks
the record customer link.
2. The employee record customers required information. A1
3. The employee clicks the save button.

A1 If the information recorded is invalid, the system will alert the

error and the employee will redirect to this form.

83
Post condition The information will be stored in the database.
Table 4: System use case for record book/and user data

Use case 03 Sold book

Use case name Sold book

Use case id UC 03
Actor Employee
Description This use case used to record full information about the book that the
customers buy.
Precondition Being employee

Work flow 1. The employee login to the employee main page and clicks the
record buyer link.
2. The employee record customer’s and books required
information.A1
3. The employee clicks the save button.

A1 If the information recorded is invalid, the system will alert the error
and the employee will redirect to this form.

Post condition The information will be stored in the database.

Table 5: System use case for sold book

Use case 04 Generated report

Use case name Generated report

Use case id UC 04
Actor Employee
Description This use case used to view the generated report about the daily rent,
returned and sale books to the manager
Precondition Being employee
Work flow 1.The employee starts the system and login to the system.A1

2. The employee clicks on the generate report link.

A1
The employee fails for login. The employee can try again by
entering username and password.

Post condition The report will be displayed.

Table 6: System use case for generated report

84
 Use case 05 add book

Use case name Add Book

User case ID UC 05

Actor Manager

Description Add new books to the store with all the details of the book to the
database.

Precondition The required book that going to be add must be available

Work flow 1.The manager starts the system and login to the system.A1

2. The manager clicks on the add book link

3. The System displays the form required to fill the details of the
book.

4. The manager fills the required information.A2

5. The manager clicks the save button.

A1 If the login is unsuccessful the manager should enter user name

and password again.

If the information is invalid the system will alert the error and
redirect the user to the form.
A2

Post condition The book detail will be added to the database.

Table 7: System use for Add book

Use case 06 Remove book

Use case name Remove book

User case ID UC 06

Primary Actors Manager

Description The old and damaged books in the store must remove from the
database.

Precondition To remove the book must be part of the database or registered

85
 in the database.

Work flow 1. The manager must start the system and login to the system.A1
2. The manager clicks the remove book link.
2. The manager fills the book detail that he/she want to remove
from the database.A2
3. Then click the remove button.

Post condition The book detail is removed from the database.

A1 If the login is unsuccessful the manager should enter user name

and password again.

If the detail of the book that the manager fills is not found in
the database alert message and redirect to fill again.
A2

Table 8: System use case for remove book

Use case 07 Search book

Use case name Search book

Use case id UC 07
Actor Customer, Employee, manager
Description This use case is used to search available book in the database
Precondition The system should be started and the users should be in the
search page

Work flow 1. The user clicks the search link.

2. The user inserts the required book detail in the search
box.A1
3. Then the user clicks the searching button on the searching
form.
A1 If the book detail entered is invalid the system will display the
error message and the system redirects the user to the form.
Post condition The user can get full information about the existing book and
the employee can provide the available book.

Table 9: System use case for search book

Use case 08 Return book

Use case name Return book

86
Use case id UC 08
Actor Employee
Description The customer must return the books to the employee.
Precondition The system should be started and customer should come
with the book.

Work flow 1.The employee login to the system and clicks return
link.A1
2.The employee fills the required information on the
form.A2
3. The employee clicks on the save button.
A1
If the login fails the employee should enter user name and
A2 password again.

If the information is invalid the system will alert the error

and redirect to the form.
Post condition The book will be returned
Table 10: System use case for return book

Use case 09 Feedback

Use case name Feedback
Use case id UC 09
Actor Customer
Description This use case used to give feedback to the organization.
Precondition The system should be started and the customer should be in the
feedback page.

Work flow 1. The customer clicks the feedback link.

2. The customer fills the required information on the feedback
form.A1
2. The customer clicks the send button.
A1 If the information entered in the feedback form is invalid, the
system will alert the error message and redirect the customer to fill
the form again.
Post condition The comments will send to the database.
Table 11: System use case for feedback

Use case 10 View report

Use case name View report

Use case id UC 10
Actor Manager

87
Description This use case is used when the manager want to view the daily
report generated by the employee.
Precondition The system should be started.

Work flow 1. The manager must be login.A1

2. The manager clicks the view report link.
A1 If the manager enters incorrect pass word and user name the system
redirects to the login form
Post condition The manager views the report.
Table 12: System use case for view report

Use case 11 view feedback

Use case name View Feedback

Use case id UC 11
Actor Administrator, Manager, Employee
Description This use case used to view the feedback of customers.
Precondition Being Administrator, Manager, Employee

Work flow 1. The user should be login to the system.A1

2. The user clicks the view feedback link.
A1 If the user enters incorrect pass word and user name the system
redirects to the login form.
Post condition The feedback will be displayed from the database

Table 13: System use case for check Feedback

Use case 12Post announcement

Use case name Post announcement

Use case id UC 12
Actor Manager
Description This use case used to upload pictures and text to the database.
Precondition The material that is going to be posting must be available.

Work flow 1.Themanager must login.A1

2. The manager clicks the upload link.

3. select the data

4. Then click the upload button to post the announcement.
A1 If the login fails the manager should enter user name and password again.
Post condition The posted data will be stored on the database and it will be displayed on

88
 the news page.

Table 14: System use case for post announcement

Use case 13 Create account

Use case name Create account

Use case id UC 13

Actor System administrator

Description This use case allows to manage user account

Precondition The user should have login as an administrator.

Work flow 1. System administrator login to his account from the home page.A1

2. System administrator click on the create account link.

3. Administrator fill user name and password to the form for the new user
and press create button

4. The system checks that the account is not created before.A2

A1 If the login fails the user should enter user name and password.

The system displays error message stating username and password is already
exists and redirect to the form.
A2

Post condition The new account will be created.

Table 15: System use case for creating account

Use case 14 Delete account

Use case name Delete account

Use case id UC 14

Actor System Administrator

Description This use case allows to delete user account

89
Precondition The user should have login as an administrator and the user account should be
exist.

Work flow 1. System administrator login to his account from the home page.A1

2. System administrator clicks on the delete account link.

3. Administrator select the user and press delete button

A1 If the login fails the user should enter user name and password again

Post condition The new account will be created.

Table 16: System use case for deleting account

Use case 15 Update account

Use case name Update account

Use case id UC 15

Actor System Administrator

Description This use case allows to change user name or password of the user account

Precondition The user should have login as an administrator.

Work flow 1. System administrator login to his account from the home page.A1

2. System administrator click on the create account link.

3. Administrator change user name or password of the existing account and

press update button.

A1 If the login fails the user should enter user name and password.

Post condition The new account will be created.

90
3.2.3 Sequence diagram
Sequence diagram shows the sequence or procedure of each activities when users are interacting
with the system. Sequence diagrams are a popular dynamic modeling solution. Dynamic
modeling focuses on the the interactions occurring within the system. Sequence diagrams
specifically focus on the "lifelines" of an object and how they communicate with other objects to
perform a function before the lifeline ends.

Login

91
Buy book

92
Provide feedback

93
Generate report

94
Create account

95
3.2.4 Activity Diagram
Login

96
Buy book

97
Add book

98
Report generate

99
100