UNIVERSITY OF COMPUTER STUDIES (THATON)

2023-2024 ACADEMIC YEAR

FOURTH YEAR (B.C.Sc) (SEMESTER-VIII)
OBJECT-ORIENTED DESIGN AND DEVELOPMENT

A PROJECT REPORT ON
BOOK SELLING SYSTEM

GROUP – III
UCSTT(17-18)-017 Mg Paing Thet Kyaw
UCSTT(18-19)-040 Mg Min Swe Mon
UCSTT(16-17)-003 Mg San Lin Oo
UCSTT(16-17)-006 Mg Thant Htet Sin
UCSTT(16-17)-015 Mg Zaw Naing Oo
UCSTT(16-17)-029 Mg Khant Maw Htoo
UCSTT(16-17)-109 Ma Ni Ni Htet

(SEPTEMBER, 2024)
 Project Outline
Chapter 1: Introduction
1.1 Project Description --------------------------------------------------------------------------------------------------- 1
1.2 Project Objectives --------------------------------------------------------------------------------------------------- 1
Chapter 2: Business Processes
2.1 Software Requirement Specification (SRS) -------------------------------------------------------- 2
2.2 Requirement Analysis ---------------------------------------------------------------------------------------------- 2
2.2.1 Functional Requirement ------------------------------------------------------------------------- 2
2.2.2 Non-functional Requirement ------------------------------------------------------------------ 3
2.3 Use Case Model Development ----------------------------------------------------------------------------- 3
2.3.1 Identify the actors and their usage ------------------------------------------------------- 3
2.3.2 Identify each actor and their functionalities ------------------------------------------ 3
2.3.3 Identify the user interface design -------------------------------------------------------------- 4
2.3.4 Represent the actors and functions in the use case diagram ------------- 4
2.3.5 Represent text description for each use case in the use case diagram -- 5
2.4 Use Case Diagram of Library Automation System ---------------------------------------- 10
Chapter 3: Defining Conceptual Classes and Relationships ---------------------------------------------------- 11
3.1 Identifying the Objects/Classes ------------------------------------------------------------------------- 11
3.2 Identifying Relationship Between Two or More Classes -------------------------------- 11
3.3 The Domain Model or Conceptual Model ----------------------------------------------------- 12
3.4 Interaction Modeling with Sequence Diagrams --------------------------------------------- 13
3.5 Classes Diagrams ------------------------------------------------------------------------------------------------ 17
Chapter 4: Implementing the User Interface
4.1 Main Menu ------------------------------------------------------------------------------------------------------------- 19
4.2 Register (User) ------------------------------------------------------------------------------------------------------------- 19
4.3 Login -------------------------------------------------------------------------------------------------------------------------- 20
4.4 View All Books 20
Chapter 5: Conclusion and References --------------------------------------------------------------------------- 21
5.1 Conclusion 21
5.2 References 21
 Chapter 1: Introduction
1.1 Project Description
The Book Selling System is a command-line application that lets users browse and view
details about books. The system focuses on providing essential information like titles, authors,
and published year, all through a simple text-based interface. It does not handle purchases or
payments just the book details.
This Book Selling System aims to simplify the process of discovering and obtaining
information about books for sale. By focusing on delivering a rich user experience and accurate
book details, the system will serve as a valuable tool for both casual readers and dedicated book
collectors.

1.2 Project Objectives

The Book Selling System Project aims to improve the experience for both customers and sellers
in the book industry. The main goals are:
 Streamline Book Discovery: Make it easy for users to search and find books by title.
 Ensure Accurate Information: Provide reliable and detailed book information,
including title, author, isbn, published year, price and description.
 Improve User Experience: Create a user-friendly command-line interface that is
easy to use for both casual and dedicated readers.
 Support Admin Management: Allow administrators to easily manage book listings
by adding, updating, or deleting entries.
 Optimize for Lightweight Design: Build a system that runs efficiently in a
command-line environment with minimal resources.

Chapter 2: Business Processes

1
2.1 Software Requirement Specification (SRS)
(1) User Registration: Users must be able to register for an account to access the full features of
the Book Selling System.
(2) System Login: Admin can login to system with user name and password (defined by the
system) and user can login with email and password they have registered.
(3) Add books to the collection: Administrators must be able to add new books to the
collection.
(4) Editing a book by ISBN: Administrators must be able to edit existing book details using the
book's ISBN.
(5) Delete a book by ISBN: Administrators must be able to delete books from the collection
using the book's ISBN.
(5) Viewing the lists of the book: Admin and user can view the book collection with details of
all books that stored in the system.

2.2 Requirements Analysis

2.2.1 Functional requirements
Functional requirements for the Book Selling System are as follows:
(1) Book Management: The system should handle tasks related to adding, updating, and
removing books from the collection, as well as managing book details such as title, author,
ISBN, and publication year.
(2) User Management: The system should support creating and managing user accounts,
including handling registration and login.
(3) Administrative Management: The system should enable administrators to perform tasks
such as managing book like add book, edit and delete book.
(4) Search and Retrieval: The system should provide a search function that allows users and
administrators to quickly find books by title.
(5) Reporting and Analytics: The system should offer clear error messages and feedback for
invalid inputs or system issues to guide users and administrators in resolving problems.
(6) Security and Access Control: The system should protect sensitive data and manage user
access by controlling who can view or modify information based on their role.

2
2.2.2 Non-functional requirements
Non-functional requirements for the Library Automation System are as follows:
(1) Usability: Designing the system to be easy to use and navigate, providing a positive
experience for all users, including both administrators and patrons.
(2) Scalability: Ensuring the system can handle an increasing number of books and users as the
collection and user base grow.
(3) Performance: Making sure the system responds quickly and processes requests efficiently to
maintain smooth operations.
(4) Reliability: Creating a dependable system with minimal downtime, ensuring continuous
availability of services.
(5) Security: Implementing strong security measures to safeguard against unauthorized access
and protect sensitive data.

2.3 Use Case Model Development

2.3.1 Identify the actors and their usage
Actor:
 Administrator: Manages book details, user accounts, and performs system
maintenance.
 User: Registers, logs in, and interacts with the book collection (e.g.,
searches for books).

2.3.2 Identify each actor and their functionalities

Administrator:
 Add Book: Input new book details into the system.
 Edit Book: Update details of existing books.
 Delete Book: Remove books from the collection.

User:
 Register: Create a new user account.
 Log In: Access the system with credentials.

3
  Search Books: Find books by title.
 View Book Details: See information about specific books.
2.3.3 Identify the user interface design
 Registration Page: A form where users enter their name, email, and
password.
 Login Page: A form for users to enter their email and password.
 Book Management Interface (Admin): Forms for adding, editing, and
deleting books, and viewing book details.
 Search Page: An interface for users to search for books by various title.
 Book Details Page: A page displaying detailed information about a
selected book.
2.3.4 Represent the actors and functions in the use case diagram
Use case diagram components
 Actors
 Admin
 User

 Use cases
 Add Book
 Edit Book
 Delete Book
 Search Book
 View Books
 Register
 Login
 Exit

2.3.5 Represent text description for each use case in the use case diagram
2.3.5.1 Use case for Login by a user
Table 2.1 Use case “Login”

4
Actions performed by the User Response form the system
1. User choose number No.1 form the Menu
provided by the system.
2. Accept No. and Request Name and
Password from user.
3. User provide Name and Password.
4. Accept name and password.
5. Response with “Successfully login”
message and display User Menu.

2.3.5.2 Use case for Login by Admin

Table 2.2 Use case “Login”
Actions performed by the Admin Response form the system
1. User choose number No.1 form the Menu
provided by the system.
2. Accept No. and Request Name and
Password from user.
3. User provide Name and Password.
4. Accept name and password.
5. Response with “Successfully login”
message and display Admin Menu.

2.3.5.3 Use case for Register by a user

Table 2.3 Use case “Register”
Actions performed by the User Response form the system

5
1. User choose number No.2 form the Menu
provided by the system.
2. Accept No. and Request Name, Email,
Address and password from user.
3. User provide Name, Email, Address and
password.
4. Accept Name, Email, Address and Password
5. Response with “Successfully Register”
message and redisplay main menu.

2.3.5.4 Use case for Add Book by Admin

Table 2.4 Use case “Add Book”
Actions performed by the Admin Response form the system
1. User choose number No.1 form the Menu
provided by the system.
2.Accept No. and Request title, author, ISBN,
published year, price and description of the
book
3.Admin provide title, author, ISBN,
published year, price and description
4. Accept title, author, ISBN, published year,
price and description
5. Response with “Book added successful.”
message and display User Menu.

2.3.5.5 Use case for Edit Book with ISBN by Admin

Table 2.5 Use case “Edit Book with ISBN”
Actions performed by the Admin Response form the system

6
1. User choose number No.2 form the Menu
provided by the system.
2. Accept No. and Request ISBN of the book
admin want to edit.
3. Admin type the ISBN of the book they
want to edit.
4. Accept the ISBN and if Book available and
display the detail of the book.
5. Request new title, new author, new
published year, new price and new description.
6. Admin type the value of the field they want to
edit.
7. Accept the value and update the table and
display “ Book update successfully”.

2.3.5.6 Use case for Delete Book by Admin

Table 2.6 Use case “Delete Book”
Actions performed by the Admin Response form the system
1. Admin choose number No.3 form the Menu
provided by the system.
2. Accept No. and Request ISBN of the book.
3. Admin provide ISBN of the book want to
delete.
4. Accept ISBN and delete the book from the
database.
5. Response “Book successfully delete”.

2.3.5.7 Use case for Search Book with Title by Admin

Table 2.7 Use case “Search Book”
Actions performed by the Admin Response form the system

7
1. Admin choose number No.4 form the Menu
provided by the system.
2. Accept No. and Request title of the book.
3. Admin provide ISBN title of the book
want to search.
4. Accept title of the book.
5. Response detail of the book ( name , author,
ISBN, published year, price, description).

2.3.5.8 Use case for Search Book with Title by User

Table 2.8 Use case “Search Book”
Actions performed by the User Response form the system
1. User choose number No.2 form the Menu
provided by the system.
2. Accept No. and Request title of the book.
3. User provide title of the book want to
search.
4. Accept title of the book and response by
displaying detail of the book ( name, author,
ISBN, published year, price, description).

2.3.5.9 Use case for View Books by Admin

Table 2.9 Use case “View Books”
Actions performed by the Admin Response form the system

8
1. Admin choose number No.5 form the Menu
provided by the system.
2. Accept No. and display lists of the books
from database.

2.3.5.10 Use case for View Books by User

Table 2.10 Use case “View Books”
Actions performed by the User Response form the system
1. User choose number No.2 form the Menu
provided by the system.
2. Accept No. and display lists of the books
from database.

2.4 Use case diagram

9
 Figure: 2.1 Use case diagram for Book Selling System

Chapter 3: Defining Conceptual Classes and Relationships

10
3.1 Identifying the Objects/Class

3.2 Identifying Relationship Between Two or More Classes

11
3.3 The Domain Model or Conceptual Model

Figure 3.3: Conceptual Models including classes and their associations

12
3.4 Interaction Modeling with Sequence Diagrams
3.4.1 Register

Figure: 3.1 Sequence diagram for Register

3.4.2 Login (User)

Figure: 3.2 Sequence diagram for Login(User)

3.4.3 Search Book By Title (User)

13
 Figure: 3.3 Sequence diagram for Search Book by title
3.4.4 View Books (User)

Figure: 3.4 Sequence diagram for View Books

\
3.4.5 Add Book (Admin)

14
 Figure: 3.5 Sequence diagram for Add Book

3.4.6 Edit Book (Admin)

Figure: 3.6 Sequence diagram for Edit Book

3.4.7 Delete Book (Admin)

15
 Figure: 3.7 Sequence diagram for Delete Book

3.4.8 Search Book by Title (Admin)

Figure: 3.8 Sequence diagram for Search Book by Title

3.4.9 View Books (Admin)

16
 Figure: 3.9 Sequence diagram for View Books

3.5 Classes Diagrams

Figure 3.5.1: Class diagram for BookSellingSystem

17
 Figure 3.5.2: Class diagram for Book

Figure 3.5.3: Class diagram for User

18
 Chapter 4: Implementing the User Interface
4.1 Main Menu

4.2 Register (User)

19
4.3 Login

4.4 View All Books

20
 Chapter 5: Conclusion and References
5.1 Conclusion
The Book Selling System successfully streamlines book management and user interactions. It
provides administrators with efficient tools for managing books, while offering users a simple
interface for discovering and exploring books. The system is secure, reliable, and scalable,
ensuring it can grow with future needs. Overall, this project delivers a functional and user-
friendly platform that meets its goals and supports both administrators and users effectively.
5.2 References
[1] Rajib Mall, ―Fundamental of Software Engineering‖, 4th Edition, 2014
• Chapter 8: Object Oriented Software Development
[2] Brahma Dathan and Sarnath Ramnath, ―Object-Oriented Analysis, Design and Implementation‖ , An
Integrated Approach, Second Edition, 2015, UTiCS, Springer.
• Chapter 7: Design and Implementation
[3] https://www.visual-paradigm.com/guide/uml-unified-modeling-language/
[4] https://www.tutorialspoint.com/object_oriented_analysis_design/ooad_object_oriented_paradigm.htm

21