Chapter 2: Proposed System
2.1 Feasibility Study
A feasibility study evaluates the practicality and potential success of the Books & Co.
system. It includes technical, economic, and operational considerations.
1. Technical Feasibility:
○ The system uses well-supported technologies like PHP, MySQL, and
HTML/CSS, ensuring ease of development and maintenance.
○ Cloud hosting solutions like AWS provide scalability and availability.
2. Economic Feasibility:
○ Although initial development costs are higher, the system reduces operational
expenses, such as labor-intensive tasks, and minimizes manual errors.
○ Subscription or licensing models can help libraries offset the costs.
3. Operational Feasibility:
○ Easy-to-use interfaces ensure a smooth learning curve for members and
administrators.
○ Automating tasks like book issuance, return, and notifications increases
operational efficiency and user satisfaction.
2.2 Objectives of the Proposed System
The proposed system aims to achieve the following objectives:
1. Centralized Management: Consolidate book-related resources into a single platform
for easier management.
2. Enhanced User Experience: Provide a responsive and intuitive interface for
members and administrators.
3. Automation of Processes: Automate book issuance, returns, overdue tracking, and
notifications.
4. Scalability: Design the system to support future enhancements like e-book lending
or multimedia resources.
5. Accessibility: Ensure compatibility across devices, enabling users to access the
system from desktops, tablets, or smartphones.
6. AI Integration: Incorporate recommendation algorithms to personalize user
experiences.
2.3 Users of the System
The primary users of the system are:
1. Library Members:
○ Students, faculty, or general users who borrow books.
○ Access features like book searches, borrowing history, and personalized
recommendations.
2. Library Administrators:
○ Manage inventory, issue books, and handle member accounts.
○ Generate reports on library operations and track system performance.
3. Developers and Maintenance Teams:
○ Ensure smooth operation, bug fixing, and feature updates.
Chapter 3: Analysis and Design
3.1 System Requirements
Functional Requirements:
1. User Registration and Login: Secure sign-up and login features for members and
admins.
2. Book Management: Add, edit, delete, and track books in the inventory.
3. Issuance and Return: Automated processes with due date notifications.
4. Notifications: Email updates for account activities, book availability, and overdue
alerts.
5. AI Recommendations: Suggest books based on user preferences and borrowing
history.
Non-Functional Requirements:
1. Performance: The system should handle multiple concurrent users efficiently.
2. Security: Use SSL encryption and authentication protocols to safeguard user data.
3. Usability: Ensure an intuitive interface with clear navigation.
4. Reliability: Guarantee 99.9% uptime with cloud hosting services.
3.2 Module Hierarchy Diagram
A hierarchy diagram shows the relationship between system modules.
Modules:
1. Homepage:
○ Membership information and login access.
2. Member Dashboard:
○ Borrowing history, book search, and personalized recommendations.
3. Admin Portal:
○ Inventory management, book issuance/return, and member account
management.
4. Database Management:
○ Handles user accounts, book inventory, and borrowing records.
3.3 Sample Input and Output Screens
Input Screens:
1. Login Screen:
○ Inputs: Membership ID, Password.
○ Actions: Login validation and redirection to the dashboard.
2. Book Search:
○ Inputs: Book title, author, or ISBN.
○ Actions: Returns search results with availability status.
Output Screens:
1. Member Dashboard:
○ Displays borrowed books, due dates, and personalized recommendations.
2. Admin Dashboard:
○ Shows options to manage books, issue/return logs, and account statuses.