Professional Documents
Culture Documents
Rsms 2
Rsms 2
A’s
Annasaheb Magar Mahavidyalaya
Hadapsar, Pune – 411 028
DEPARTMENT OF COMPUTER SCIENCE
2023-2024
A
Project Report
On
Developed By
Of T.Y.B.Sc.(Computer Science)
CERTIFICATE
Prof. Prof.
(Project Guide) (H.O.D. Computer Science)
INDEX
1. Acknowledgement
2. Company Profile
3. Existing System
4. Proposed System
1. Objective of Proposed System.
2. Scope of the System.
3. Need for Computerization
4. Fact Finding Techniques
5. Feasibility Study
6. Structured Analysis
1. Entity Relationship Diagram ( ER - Diagram )
2. UML Diagram
7. Data Dictionary
8. Design Phase
1. INPUT - OUTPUT Screen
2. Report
9.Testing Strategies.
13. Bibliography
ACKNOWLEDGEMENT
Last but not least, I am indebted to my family for their unwavering love,
understanding, and encouragement throughout this journey.
This project would not have been possible without the collective efforts
of all those mentioned above. Thank you for being a part of this
endeavor.
Abhishek Kirve
Feel free to customize it further to include specific names or
organizations that were particularly helpful or influential in your project.
Company profile
## Overview
## Mission Statement
## Contact Information
- Email: abhishekkirve47@gmail.com
- Phone: 9822240550
- Address: AM college road , Hadapsar
## Legal Information
RSMS is a registered trademark of RSMS. All rights
reserved. Unauthorized reproduction or distribution of any
part of our software solutions is strictly prohibited.
1. Customer Management:
- Registration of new customers.
- Storage and retrieval of customer information
including contact details and service history.
- Updating customer records as needed.
3. Inventory Management:
- Tracking inventory levels for spare parts and
accessories.
- Reordering of inventory items as needed to maintain
optimal stock levels.
- Notification of stock shortages or low inventory levels.
4. Staff Management:
- Management of staff details including names, contact
information, and work schedules.
- Assignment of tasks and tracking of staff performance.
- Monitoring and adjustment of work schedules as
required.
5. Financial Management:
- Recording and management of financial transactions
such as sales, purchases, payments, and expenses.
- Generation of invoices and receipts for customer
transactions.
- Compilation of financial reports for analysis and
decision-making.
5.Feasibility Study:-
Hardware Requirement:-
Processor: Windows pentium /i3 /i5/i7 all generations
Ram: 4GB or Above
Software Requirement :-
O.S: Windows XP and Above
Fronted: HTML,CSS,JS
Backend: PHP
Database:MySQL
6.Structured Analysis
Admin Table
Employee Table
Status_name Varchar Name of the repair status (e.g., “Pending”, “In Progress”, “Completed”).
EmployeeID INT Identifier for the employee assigned to the work
Description VARCHAR(100) Description of the repair status.
Status VARCHAR(20) Status of the work (e.g., In Progress, Completed)
Customer Table
Project URL:http://localhost/rsms/index.php
Home Page
Admin login
Check status
Our services
Contact us
Dashboard
Repair list
Client list
Service list
List of inquiries
Testing strategies:
1. Functional Testing:
- Repair Order Management: Test the functionality
related to creating, updating, and tracking repair orders.
- Customer Management: Verify that customer
information can be added, edited, and deleted accurately.
- Inventory Management: Test inventory-related
features such as adding, updating, and removing
inventory items.
- Financial Transactions: Ensure that sales, purchases,
payments, and expenses are recorded accurately.
- Reporting and Analytics: Verify that reports are
generated correctly and provide accurate insights into
business performance.
3. Performance Testing:
- Test the system’s performance under normal and peak
loads to ensure it can handle a high volume of
transactions efficiently.
- Measure response times for key functionalities to
identify any performance bottlenecks.
4. Security Testing:
- Conduct security testing to identify and address
potential vulnerabilities in the system.
- Test authentication and authorization mechanisms to
ensure that only authorized users can access sensitive
information.
- Verify that data encryption and protection mechanisms
are in place to safeguard customer and business data.
5. Integration Testing:
- Test the integration of the Repair Shop Management
System with external systems or APIs, such as payment
gateways or accounting software.
- Verify that data is exchanged accurately between
different components of the system.
6. Regression Testing:
- Perform regression testing after each software update
or change to ensure that existing functionalities are not
affected.
- Re-run previously executed tests to verify that no new
defects have been introduced.
8. Accessibility Testing:
- Test the accessibility of the system to ensure that it can
be used by individuals with disabilities.
- Verify compliance with accessibility standards such as
WCAG (Web Content Accessibility Guidelines).
1. Hardware Compatibility:
The system's compatibility
with various hardware devices
may be limited, requiring
specific hardware
configurations or operating
systems for optimal
performance.
3. Customization Constraints:
While the system may offer
some level of customization,
users may encounter
limitations in customizing
certain features or
functionalities to suit their
specific business needs.
6. Integration Challenges:
Integrating the system with
existing software or hardware
systems used by the repair
shop may pose challenges,
especially if compatibility
issues arise or if the system
lacks robust integration
capabilities.
11.Future Enhanceent
12. Conclusion
13. Bibliography
www.goggle.com
Chatgpt
Phpmyadmin
Xampp
Notepad++