Project Title: "ONLINE BOOKSTORE MANAGEMENT SYSTEM"
Project Members:
1. Adil Majeed (059)
2. Sufyan Arshad (63)
BSCS (4th Semester)
Section-B
School of Computer Science
Minhaj University Lahore
Overview:
The Online Bookstore Management System (OBMS) is designed to offer an efficient, user-
friendly platform for buying and selling books online. It aims to streamline the process for customers to
browse, search, and purchase books while providing administrators with tools to manage inventory,
orders, and user information.
1. Requirement Analysis
Objective:
Develop an Online Bookstore Management System (OBMS) that allows users to browse, search,
and purchase books online, while also enabling administrators to manage book inventory, orders,
and user information.
Stakeholders:
Customers
Administrators
Vendors
Delivery Personnel
Key Requirements:
User registration and authentication
Book browsing and searching
Shopping cart and checkout process
Order management
2. Feasibility Study
Technical Feasibility:
The project will be developed using web technologies such as HTML, CSS, JavaScript
for the front end, and Python (Django framework) for the back end.
Database: PostgreSQL for storing user, book, and order information.
Economic Feasibility:
Initial cost involves web hosting, domain purchase, and development tools.
Maintenance costs include server upkeep and updates.
Revenue can be generated through book sales, advertisements, and affiliate marketing.
Operational Feasibility:
Users and administrators can easily interact with the system through an intuitive
interface.
Training will be provided for administrators to manage the system efficiently.
3. Requirement Elicitation
Methods Used:
Interviews with potential users and administrators
Questionnaires to gather user preferences
Workshops with stakeholders to understand business processes
Elicited Requirements:
User login and registration
Book catalog with search and filter options
Detailed book descriptions and reviews
Shopping cart and order summary
4. Requirement Validation
Validation Techniques:
Reviewing requirements with stakeholders to ensure they meet business needs.
Prototyping to gather user feedback.
Use cases to validate functional requirements.
Validated Requirements:
Functional requirements are confirmed with stakeholders.
Non-functional requirements like performance, security, and usability are agreed upon.
Software Requirements Specification (SRS) Document
1. Introduction
Purpose:
Define the functionalities and requirements of the OBMS.
Scope:
The system will provide an online platform for users to purchase books and for administrators to
manage inventory and orders.
Definitions:
OBMS: Online Bookstore Management System
Admin: Administrator who manages the system
2. Functional Requirements
1. User Registration and Login:
Users can register with their email and password.
Users can log in with their credentials.
2. Book Catalog:
Users can browse and search for books.
Books are categorized by genre, author, and publication date.
3. Shopping Cart:
Users can add and remove books from the cart.
Users can view the cart and proceed to checkout.
4. Order Management:
Users can place orders and make payments.
Users can view order history and track current orders.
5. Inventory Management:
Admins can add, update, and delete book listings.
Admins can manage stock levels.
6. Payment Processing:
Integration with secure payment gateways.
Users can make payments using credit/debit cards or online banking.
7. User Reviews and Ratings:
Users can write reviews and rate books.
Admins can moderate reviews.
3. Non-Functional Requirements
1. Performance:
The system should handle up to 10,000 concurrent users.
Page load time should be less than 2 seconds.
2. Security:
User data should be encrypted.
Payment processing should comply with PCI-DSS standards.
3. Usability:
The interface should be intuitive and user-friendly.
The system should provide accessibility features.
4. Reliability:
The system should have 99.9% uptime.
Data backup should occur daily.
Use Case Diagram:
Class Diagram:
Activity Diagram:
Sequence Diagram:
