BOOK SHOP SYSTEM

MANAGEMENT
Software engineering – Final Project

JANUARY 9, 2023

SUBMITTED BY: ALBION NAZARI MENTOR: ALEKSANDAR KARADIMCE

 INDEX

Book Shop Management System Activity Diagram

Features Of The Activity UML Diagram Of Book Shop Management System

Login Activity Diagram Of Book Shop Management System

Book Shop Management System Class Diagram

Book Shop Management System Component Diagram

Sales Component

Online Book Store Dataflow Diagram

First Level Data Flow Diagram(st Level DFDJ Of Online Book Store

Second Level Data Flow Diagram (2nd Level DFD) Of Online Book Store

Book Shop Management System ER Diagram

Description of Book Shop Management System Database

Book Shop Management System Sequence Diagram

Book Shop Management System Use Case Diagram

Book Shop Management System Activity Diagram

 This is the Activity UML diagram of Book Shop Management System which
shows the flows between the activity of Inventory, Books, Sales, Stocks,
Publications. The main activity involved in this UML Activity Diagram of Book
Shop Management System are as follows:
   Inventory Activity
   Books Activity
 Sales Activity
 Stocks Activity
   Publications Activity

Features Of The Activity UML Diagram Of Book Shop Management System:

   Admin User can search Inventory, view description of a selected
Inventory, add Inventory, update Inventory and delete Inventory.
   Its shows the activity flow of editing, adding and updating of Books
   User will be able to search and generate report of Sales, Stocks,
Publications
   All objects such as ( Inventory, Books, Publications) are interlinked
   Its shows the full description and flow of Inventory.
Login Activity Diagram Of Book Shop Management System

This is the Login Activity Diagram of Book Shop Management System,

which shows the flows of Login Activity, where admin will be able to login using
their username and password.
After login user can manage all the operations on Sales, Inventory, Books,
Publications, Stocks.
All the pages such as Books, Publications, Stocks are secure and user can
access these page after login. The diagram below helps demonstrate how the login
page works in a Book Shop Management System.
The various objects in the Publications, Sales, Inventory, Books, and Stocks
page interact over the course of the Activity, and user will not be able to access this
page without verifying their identity.
Book Shop Management System Class Diagram
Book Shop Management System Class Diagram describes the structure of a
Book Shop Management System classes, their attributes, operations (or methods,
and the relationships among objects.
The main classes of the Book Shop Management System are Books, Receipts,
Sales, Inventory, Stocks, Publications

Classes of Book Shop Management System Class Diagram:

 Books Class: Manage all the operations of Books
 Receipts Class: Manage all the operations of Receipts
 Sales Class: Classes and their attributes of Book Shop Management System
Class Diagram:
  Books Attributes: book_id, book_customer_id, book_name, book_author,
book_publication_date, book_type, book_price, book_description
 Receipts Attributes: receipt_id, receipt_customer_id, receipt_number,
receipt_type, receipt_description
 Sales Attributes: sales id, sales customer_id, sales_amount, sales_type,
sales_description
 Inventory Attributes: inventory_id, inventory_items, inventory_number,
inventory_type, inventory_description
 Stocks Attributes: stock_id, stock_items, stock_number, stock_ type,
stock_description
 Publications Attributes: publication id, publication_book_id,
publication_date, publication_place, publication_number, publication type,
publication_name, publication_description

Classes and their methods of Book Shop Management System Class Diagram:
 Books Methods: addBooks(), editBooks(), deleteBooks(), updateBooks(),
saveBooks), searchBooks()
 Receipts Methods: addReceipts(), editReceipts(), deleteReceipts(),
updateReceipts(), saveReceipts(), searchReceipts)
 Sales Methods: addSales(), editSales(), deleteSales(), updateSales(),
saveSales(), searchSales()
 Inventory Methods: addinventory(), editInventory(), deletelnventory(),
updatelnventory(), savelnventory(), searchInventory()
 Stocks Methods: addStocks(, editStocks(), deleteStocks(), updateStocks(),
saveStocks(), searchStocks()
 Publications Methods: addPublications), editPublications),
deletePublications (, updatePublications(), savePublications), search
Publications)


Class Diagram of Book Shop Management System:

Book Shop Management System Component Diagram
This is a Component diagram of Book Shop Management System which shows
components, provided and required interfaces, ports, and relationships between the
Inventory, Books, Publications, Sales and Stocks. This type of diagrams is used in
Component-Based Development (CBD) to describe systems with Service-Oriented
Architecture (SO). Book Shop Management System UML component diagram,
describes the organization and wiring of the physical components in a system.

Components of UML Component Diagram of Book Shop Management System:

 Inventory Component
   Books Component
   Publications Component
 Sales Component
 Stocks Component

Featues of Book Shop Management System Component Diagram:

 You can show the models the components of Book Shop Management
System
   Model the database schema of Book Shop Management System
   Model the executables of an application of Book Shop Management
System
   Model the system's source code of Book Shop Management System

Online Book Store Dataflow Diagram

 Online Book Store Data flow diagram is often used as a preliminary step to
create an overview of the Book Store without going into great detail, which can
later be elaborated it normally consists of overall application dataflow and
processes of the Book Store process. It contains all of the userflow and their
entities such all the flow of Book, Customer, Order Update, Bills, Book Stocks.
All of the below diagrams has been used for the visualization of data
processing and structured design of the Book Store process and working flow.

Zero Level Data Flow Diagram (O Level DFD) of Online Book Store :
This is the Zero Level DFD of Online Book Store, where we have eloborated
the high level process of Book Store. It's a basic overview of the whole Online
Book Store or process being analyzed or modeled. It's designed to be an at-a-
glance view of Bills, Book Stocks and Delivery showing the system as a single
high-level process, with its relationship to external entities of Book, Customer and
Order. It should be easily understood by a wide audience. including Book, Order
and Bills In zero leve DFD of Online Book Store, we have described the high level
flow of the Book Store svstem

High Level Entities and process flow of Online Book Store:

   Managing all the Book
   Managing all the Customer
   Managing all the Order
   Managing all the Order Update
   Managing all the Bills
   Managing all the Book Stocks
 Managing all the Delivery
First Level Data Flow Diagram 1st Level DFDJ Of Online Book Store

First Level DFD (1st Level) of Online Book Store shows how the system is
divided into sub-systems (processes), each of which deals with one or more of the
data flows to or from an external agent, and which together provide all of the
functionality of the Online Book Store system as a whole. It also identifies internal
data stores of Delivery, Book Stocks, Bills, Order Update.
Order that must be present in order for the Book Store system to do its job
and shows the flow of data between the various parts of Book, Order, Book Stocks,
Delivery, Bills of the system.
DFD Level 1 provides a more detailed breakout of pieces of the 1st level DD.
You will highlight the main functionalities of Book Store.

Main entities and output of First Level DFD (1st Level DFD):
 Processing Book records and generate report of all Book
 Processing Customer records and generate report of all Customer
 Processing Order records and generate report of all Order
 Processing Order Update records and generate report of all Order Update
 Processing Bills records and generate report of all Bills
 Processing Book Stocks records and generate report of all Book Stocks
 Processing Delivery records and generate report of all Delivery
Second Level Data Flow Diagram (2nd Level DFD) Of Online Book Store

DFD Level 2 then goes one step deeper into parts of Level 1 of Book Store. It may
require more functionalities of Book Store to reach the necessary level of detail
about the Book Store functioning.
First Level DD (1st Level) of Online Book Store shows how the system is
divided into sub-systems (processes).
The 2nd Level DFD contains more details of Delivery, Book Stocks, Bills,
Order Update, Order, Customer, Book.

Low level functionalities of Online Book Store:

 Admin logins to the system and manage all the functionalities of
Online Book Store
 Admin can add, edit, delete and view the records of Book, Order, Bills,
Delivery Admin can manage all the details of Customer, Order Update,
Book Stocks
 Admin can also generate reports of Book, Customer, Order, Order
Update, Bills, Book Stocks
 Admin can search the details of Customer, Bills, Book Stocks
  Admin can apply different level of filters on report of Book, Order
Update, Bills
 Admin can tracks the detailed information of Customer, Order, Order
Update, Bills

Book Shop Management System ER Diagram

This ER (Entity Relationship) Diagram represents the model of Book shop

Management System Entity.
The entity-relationship diagram of Book Shop Management System shows all
the visual instrument of database tables and the relations between Receipts,
Inventory, Books, Publications etc. It used structure data and to define the
relationships between structured data groups of Book Shop Management System
functionalities. 4
The main entities of the Book Shop Management System are Books, Receipts,
Sales, Inventory, Stocks and Publications.

Book Shop Management System entities and their attributes:

  Books Entity: Attributes of Books are book id, book customer id, book
name, book_author, book_publication date, book_type, book_price,
 book_description
 Receipts Entity Attributes of Receipts are receipt_id,
receipt_customer_id, receipt_number, receipt_type, receipt_ description
 Sales Entity Attributes of Sales are sales_id, sales customer_id,
sales_amount, sales_type, sales_description
 Inventory Entity: Attributes of Inventory are inventory_id, inventory_
items, inventory_number, inventory_type, inventory_ description
 Stocks Entity Attributes of Stocks are stock_id, stock_items,
stock_number, stock type, stock_ description
 Publications Entity: Attributes of Publications are publication_ id,
publication_book_ id, publication_date, publication_place, publication
number, publication type, publication_name, publication_description

Description of Book Shop Management System Database:

 The details of Books is store into the Books tables respective with all
tables
 Each entity (Publications, Sales, Stocks, Receipts, Books) contains
primary key and unique keys.
 The entity Sales, Stocks has binded with Books, Receipts entities with
foreign key . There is one-to-one and one-to-many relationships
available between Stocks, Inventory, Publications, Books
 All the entities Books, Stocks, Sales, Publications are normalized and
reduce duplicacy of records
 We have implemented indexing on each tables of Book Shop
Management System tables for fast query execution.
ER Diagram For Book Shop Management System:
Book Shop Management System Sequence Diagram
 This is the UML sequence diagram of Book Shop Management System
which shows the interaction between the objects of Sales, Publications.
Books, Stocks, Inventory.
The instance of class objects involved in this UML Sequence Diagram of Book
Shop Management System are as follows:
 Sales Object
 Publications Object
 Books Object
 Stocks Object
 Inventory Object

Login Sequence Diagram Of Book Shop Management System

This is the Login Sequence Diagram of Book Shop Management System,

where admin will be able to login in their account using their credentials.
After login user can manage all the operations on Books, Sales, Publications,
Inventory. Stocks. All the pages such as Publications, Inventory Stocks are secure
and user can access these page after login.
The diagram below helps demonstrate how the login page works in a Book
Shop Management System. The various objects in the Inventory, Books, Sales,
Publications, and Stocks page interact over the course of the sequence, and user
will not be able to access this page without verifying their identity.

Sequence Diagram of Book Shop Management System:

 This is the UML sequence diagram of Book Shop Management System
which shows the interaction between the objects of Sales, Publications, Books,
Stocks, Inventory.
The instance of class objects involved in this UML Sequence Diagram of
Book Shop Management System are as follows:
 Sales Object
 Publications Object
 Books Object
 Stocks Object
 Inventory Object

Book Shop Management System Use Case Diagram

 This Use Case Diagram is a graphic depiction of the interactions among the
elements of Book Shop Management System. It represents the methodology used
in system analysis to identify, clarify, and organize system requirements of Book
Shop Management System.
The main actors of Book Shop Management System in this Use Case Diagram
are Super Admin, System User, Shopkeepers, Customers, who perform the
different type of use cases, such as Manage Books, Manage Receipts, Manage
Sales, Manage Inventory, Manage Stocks, Manage Publications, Manage Users
and Full Book Shop Management System Operations.
Major elements of the UML use case diagram of Book Shop Management
System are shown on the picture below.
The relationships between and among the actors and the use cases of Book Shop
Management System:
 Super Admin Entity: Use cases of Super Admin are Manage Books, Manage
Receipts, Manage Sales, Manage Inventory, Manage Stocks, Manage Publications,
Manage Users and Full Book Shop Management System Operations
 System User Entity: Use cases of System User are Manage Books. Manage Receipts,
Manage Sales, Manage Inventory, Manage Stocks, Manage Publications
 Shopkeepers Entity: Use cases of Shopkeepers are Manage Inventory, Create
Invoices, Manage Bills
 Customers Entity: Use cases of Customers are Make Payment, View Payment
History, Search Books

Use Case Diagram of Book Shop Management System: