A PROJECT REPORT ON

(Doctor AppointmentWebsite)

Submitted to the Department of Computer Applications in partial

fulfillment of the requirements for the award of the degree

Department of Computer Applications (MCA)

Submitted to: Submitted by:

Name (Santosh Kumar) Name:Mohd Sahil

Roll No. (2201330140110)
 NOIDA INSTITUTE OF ENGINEERING AND TECHNOLOGY,
GREATER NOIDA
(An Autonomous Institute Affiliated to AKTU, Lucknow)
FORMAT OF INDEX
Chapter No. Title Page No.

Bona fide i
Acknowledgement ii
Executive Summary iii
1 Introduction/Aims and Objective 1
2 System Analysis --
2.1 Identification of Need --
2.2 Preliminary Investigation --
3 Feasibility Study --
3.1 Technical Feasibility --
3.2 Economic Feasibility --
3.3 Operational Feasibility --
4 Analysis
4.1 DFD 0 Level, 1- Level and 2 Level --
4.2 ER Diagram --
4.3 Database, Table structure etc --
4.4 Sequential Diagram --
5 Software & Hardware Requirement Specification --
6 System Design
6.1 Module 1 --
6.2 Module 2, etc. --
7 Screen Shots of forms --
8 Validation Checks --
9 Implementation and Maintenance --
10 Testing --
(Testing techniques and Testing strategies)
11 Reports --
12 Future scope of the Mini Project --
13 Bibliography/References
 NOIDA INSTITUTEOF ENGINEERINGAND TECHNOLOGY,
GREATER NOIDA
(An AutonomousInstitute Affiliated to AKTU, Lucknow)

BONAFIDE CERTIFICATE

This is certified that the Mini Project titled "DocttoGo" is the bonafide work of "Mohd Sahil” and

university 2201330140110" who carried out the project under my supervision.

(Signature of Mentor)

Name of Mentor

Dr. C S Yadav Sir

Designation of Mentor

Asst Professor Date

:

(Signature of Dean) (Signature of HoD)

Prof. (Dr.) C. S. Yadav Dr. Apoorva Joshi

Dean, MCA HoD, MCA

Date: Date :
 Acknowledgment

We would like to express our sincere gratitude to all those who have contributed to the development and
success of [DocttoGo]. This project would not have been possible without the support and contributions of the
following individuals and organizations:

Many people assisted me in successfully finishing this project. I want to thank everyone involved in this
initiative. I’d like to thank my Python Teacher (Santosh Kumar) and (Anuj Sir), who helped me learn a lot
about this project. His ideas and comments aided in the completion of this project.

I am grateful to the college administration for providing me with such a significant chance. I believe I will
participate in more such activities in the future. I guarantee that this project was created entirely by me and is
not a forgery. Finally, I’d like to express my gratitude to my parents and friends for their excellent comments
and guidance during the completion of this project.

Sincerely,
[Mohd Sahil, MD Chand, Himanshu Goswami]
[Team Leader]
[DocttoGo]

Introduction/Aims and Objective

Introduction:
Welcome to [MedicalWebsite.com], your go-to online resource for reliable and up-to-date information on
various medical topics. In an era where health is a paramount concern for individuals worldwide, having
access to accurate and accessible medical information is crucial. Our platform is designed to bridge the gap
between medical professionals and the general public, providing a trustworthy source of information to
promote health literacy.

Aim:
The primary aim of [DocttoGo] is to empower individuals with knowledge about health and wellness, fostering
a proactive approach to personal well-being. We strive to create a comprehensive online space that caters to the
diverse informational needs of both medical professionals and the general public. By consolidating reputable
medical content, we aim to facilitate informed decision-making, promote preventive healthcare, and contribute
to the overall improvement of public health outcomes.

Objectives:

1. Information Accessibility:
- To provide easily accessible and understandable information on a wide range of medical topics, ensuring
that users can find answers to their health-related queries effortlessly.

2. Accuracy and Reliability:

- To uphold the highest standards of accuracy and reliability in all the content presented on the website. This
includes regular updates to align with the latest medical research and guidelines.

3. User Engagement:
- To engage users through interactive features such as forums, Q&A sessions, and expert-contributed articles,
fostering a sense of community and shared knowledge.

4. Health Education:
- To serve as an educational platform, offering articles, videos, and resources that promote health literacy,
disease prevention, and overall well-being.

5. Medical Professional Collaboration:

- To establish collaborations with medical professionals, experts, and organizations to ensure that the
information provided is validated by credible sources and reflects the latest advancements in the field.

6. Patient Empowerment:
- To empower individuals to take an active role in managing their health by providing tools, resources, and
information that facilitate informed decision-making and self-care.

7. Diversity and Inclusivity:

- To address the diverse health needs of our global audience by covering a broad spectrum of medical topics
and ensuring that content is culturally sensitive and inclusive.

8. Technology Integration:
- To leverage technology to enhance user experience, incorporating features such as user-friendly interfaces,
mobile responsiveness, and innovative tools for health tracking and management.
 System Analysis --
System Analysis for a Medical Website:

1. User Requirements:
- Identify the diverse user groups (patients, healthcare professionals, researchers) and their specific needs.
- Understand the varying levels of health literacy among users.
- Consider accessibility requirements for users with different abilities.

2. Content Requirements:
- Define the types of medical information to be provided (diseases, treatments, preventive measures).
- Identify the need for multimedia content, such as videos, infographics, and interactive tools.
- Ensure content is regularly updated based on the latest medical research and guidelines.

3. Functional Requirements:
- Specify the features required for user interaction (search functionality, forums, Q&A sections).
- Implement secure user authentication for personalized features (patient portals, health tracking).
- Integrate telemedicine capabilities for virtual consultations, if applicable.

4. Data Security and Privacy:

- Establish robust data security measures to protect user information.
- Comply with healthcare data privacy regulations (HIPAA, GDPR) if handling sensitive medical data.
- Implement secure communication channels for patient-doctor interactions.

5. Performance Requirements:
- Ensure the website is responsive and compatible with various devices and browsers.
- Optimize loading times to enhance user experience.
- Implement scalable infrastructure to accommodate potential increases in user traffic.

6. Interoperability:
- Consider integration with electronic health record (EHR) systems to facilitate seamless information exchange with
healthcare providers.
- Explore interoperability with wearable devices for health tracking.

7. Usability and User Experience:

 - Conduct usability testing to ensure an intuitive user interface.
- Optimize navigation for easy access to critical information.
- Implement responsive design for mobile users.

8. Collaboration with Medical Professionals:

- Develop mechanisms for medical professionals to contribute content and engage with users.
- Facilitate easy communication between users and healthcare experts.
- Implement a peer-review system for contributed medical content.

Feasibility Study –
Feasibility Study for the Medical Website:

1. Technical Feasibility:
- Infrastructure: Assess the technical requirements for hosting the website. Ensure the availability of scalable
hosting solutions to accommodate potential increases in traffic.
- Development Tools: Evaluate the feasibility of using current and widely accepted web development tools
and frameworks to facilitate efficient development and maintenance.
- Integration Capabilities: Examine the compatibility of the website with existing healthcare systems,
electronic health records (EHRs), and wearable devices.

2. Financial Feasibility:
- Development Costs: Estimate the initial costs for website development, including design, programming,
and testing.
- Operational Costs: Consider ongoing expenses for content creation, updates, server maintenance, and
potential support services.
- Revenue Streams: Explore potential revenue sources, such as sponsored content, advertisements, or
premium features for users.

3. Legal and Compliance Feasibility:

- Regulatory Compliance: Ensure compliance with healthcare data protection regulations (e.g., HIPAA,
GDPR) and other relevant legal requirements.
 - Intellectual Property: Assess potential legal issues related to content creation and user-generated content.
Implement measures to protect intellectual property.
- Liabilities: Identify and address potential legal liabilities, such as the accuracy of medical information and
user interactions.

4. Operational Feasibility:
- Content Management: Assess the feasibility of a robust content management system (CMS) to facilitate
easy content updates by administrators and contributors.
- User Support: Determine the feasibility of providing effective user support through multiple channels,
including FAQs, help sections, and customer service.
- Collaboration with Medical Professionals: Evaluate the willingness of medical professionals to contribute
and collaborate on the platform.

5. Schedule Feasibility:
- Development Timeline: Estimate the time required for website development, testing, and launch.
- Content Update Frequency: Establish a realistic schedule for updating and maintaining content to ensure
accuracy and relevance.
- Iterative Development: Consider the feasibility of adopting an iterative development approach to address
evolving user needs.

6. Market Feasibility:
- Target Audience: Assess the size and demographics of the target audience, considering the global nature of
health-related concerns.
- Competitive Landscape: Analyze existing medical websites and platforms to identify unique selling points
and differentiators.
- User Engagement: Evaluate the potential for user engagement through surveys, focus groups, or market
research.

7. Social Feasibility:
- Community Building: Assess the feasibility of building a supportive and engaged user community.
- Social Impact: Consider the potential positive impact of the website on public health awareness and
individual well-being.
- Feedback Mechanisms: Establish feasible mechanisms for gathering user feedback and incorporating user
suggestions.

Based on this comprehensive feasibility study, the project can proceed with a clear understanding of the
technical, financial, legal, operational, schedule, market, and social aspects involved in the development and
maintenance of the medical website. This information will be instrumental in making informed decisions and
ensuring the success of the initiative.

Analysis
4.1 DFD (Data Flow Diagram) .1-Level

DFD 1-Level:

The DFD 1-Level diagram of DocttoGo shows the various processes that take place within the system after a
user logs in to the platform.
 It includes the following entities:

- Patient
- Doctor
- Appointment System
- Payment System
- Admin
4.2 ER Diagram

The ER (Entity Relationship) diagram of DocttoGo depicts the relationships among the various entities in the
system.

It includes the following entities:

- Patient Details
- Appointment
- Treatment
- Prescription
- Medicine Type
- Material

The relationship between these entities is depicted using various symbols like lines, arrows, and shapes.

4.4 Sequential Diagram

The sequential diagram of World Crypto Hub shows the chronological order of various user actions in the
system.

It includes the following processes:

- User Authentication
- Dashboard Display
- Market Information Retrieval
- Community Forum Posting
- Portfolio Management
- Advertisement Display
The sequential diagram helps illustrate the flow and interaction between the system's different components and
provides a clear view of user actions and system responses.

Software Requirements Specification:

Software Requirements Specification (SRS) for Doctor's Appointment System:

1. Introduction:
1.1 Purpose:
The purpose of this software is to create a robust and user-friendly Doctor's Appointment System to
streamline the appointment scheduling process, improve communication between patients and doctors, and
enhance the overall efficiency of the healthcare system.

1.2 Scope:
The system will include features for patient registration, appointment scheduling, notifications, doctor
availability management, and basic administrative functions. It will be accessible to both patients and
healthcare providers.

1.3 Definitions, Acronyms, and Abbreviations:

- SRS: Software Requirements Specification
- EHR: Electronic Health Record
- UI: User Interface
- API: Application Programming Interface

1.4 References:
- Any relevant documents or resources that are referred to in the SRS.

1.5 Overview:
 - Briefly describe the key features and functionalities of the Doctor's Appointment System.

2. System Description:
2.1 System Overview:
- Provide a high-level overview of the system, including its main components and interactions.

2.2 System Architecture:

- Describe the architectural design of the system, outlining the relationships between different modules.

3. Functional Requirements:
3.1 Patient Module:
- User Registration
- Patient Profile Management
- Appointment Booking
- Appointment Cancellation

3.2 Doctor Module:

- Doctor Registration and Profile Management
- Availability Management
- Appointment Confirmation/Rescheduling
- Medical History Access (if integrated with EHR)

3.3 Receptionist/Clerk Module:

- Appointment Scheduling and Rescheduling
- Patient and Doctor Information Management

3.4 Administrator Module:

- User Management (Patients, Doctors, Receptionists)
- System Configuration
- Reporting and Analytics

3.5 Notification System:

- Automated Appointment Reminders
 - Communication between Users (Patients and Doctors)

4. Non-Functional Requirements:
4.1 Performance:
- Define response time requirements and system load handling capabilities.

4.2 Usability:
- Describe UI/UX requirements to ensure a user-friendly interface.

4.3 Reliability:
- Specify system reliability and availability requirements.

4.4 Security:
- Outline security measures to protect patient data and system integrity.

4.5 Scalability:
- Describe how the system can scale to accommodate an increasing number of users and data.

4.6 Compatibility:
- Specify compatibility requirements with browsers, devices, and operating systems.

5. Interface Requirements:
5.1 User Interfaces:
- Describe the interfaces for patients, doctors, receptionists, and administrators.

5.2 Hardware Interfaces:

- Specify hardware requirements, if applicable.

5.3 Software Interfaces:

- Describe any third-party software or APIs used by the system.

6. Data Requirements:
6.1 Data Storage:
 - Specify data storage requirements and the structure of the database.

6.2 Data Retrieval:

- Define how data is retrieved and presented to users.

7. Operational Requirements:
7.1 Maintenance:
- Outline maintenance procedures and requirements.

7.2 Training:
- Specify training requirements for users.

8. Legal and Regulatory Requirements:

8.1 Compliance:
- Ensure that the system complies with relevant healthcare regulations and data protection laws.

9. Appendices:
- Any additional information, charts, or diagrams that support the SRS.

10. Revision History:

- Document any changes made to the SRS and the dates of those revisions.

This Software Requirements Specification serves as a comprehensive guide for the development team,
ensuring a clear understanding of the project's goals, functionalities, and constraints. It is subject to review and
approval by stakeholders before the commencement of the development process.
 Screen Shots of Project

Home Screen
Book Appointment

Team
 System Design

System Design for Doctor's Appointment Online Portal:

1. Architectural Design:
1.1 Client-Server Architecture:
- The system will adopt a client-server architecture.
- Clients (web browsers or mobile apps) will interact with a central server hosting the appointment portal.

1.2 Three-Tier Architecture:

- Presentation Tier: User interfaces for patients, doctors, receptionists, and administrators.
- Application Tier: Business logic and functionality for appointment scheduling, notifications, and user
management.
- Data Tier: Database for storing patient and doctor information, appointments, and system configurations.

2. Database Design:
 2.1 Entity-Relationship Diagram (ERD):
- Define entities such as Patient, Doctor, Appointment, User, and other relevant entities.
- Establish relationships between entities (e.g., a patient schedules appointments with a doctor).

2.2 Database Schema:

- Specify the structure of database tables, including primary keys, foreign keys, and attributes for each
entity.

3. User Interface Design:

3.1 Patient Interface:
- Registration and login functionality.
- Profile management for updating personal information.
- Appointment booking and cancellation features.

3.2 Doctor Interface:

- Registration and login functionality.
- Profile management and availability settings.
- View and manage appointment requests.

3.3 Receptionist/Clerk Interface:

- Appointment scheduling and rescheduling features.
- Patient and doctor information management.

3.4 Administrator Interface:

- User management (add, edit, delete users).
- System configuration settings.
- Reporting and analytics dashboard.

4. Application Logic:
4.1 Appointment Scheduling Algorithm:
- Define the algorithm for scheduling appointments based on doctor availability and patient preferences.
- Consider factors such as urgency, doctor specialization, and historical appointment data.
 4.2 Notification Logic:
- Implement logic for automated appointment reminders.
- Enable communication channels between patients and doctors within the platform.

5. Security Design:
5.1 User Authentication:
- Implement secure authentication mechanisms for user logins.
- Utilize encryption for sensitive data, such as passwords.

5.2 Role-Based Access Control (RBAC):

- Define roles (patient, doctor, receptionist, administrator) and assign appropriate permissions.
- Ensure that users can only access functionalities relevant to their roles.

5.3 Data Encryption:

- Use encryption protocols for data transmission to protect sensitive information during communication.

6. System Integration:
6.1 Integration with External Systems:
- Integrate with Electronic Health Record (EHR) systems if applicable.
- Ensure compatibility with other healthcare systems for seamless information exchange.

6.2 APIs and Third-Party Services:

- Identify and integrate necessary APIs for features like payment processing, location services, or external
databases.

7. Testing Strategy:
7.1 Unit Testing:
- Test individual components (modules, functions) for correctness and reliability.

7.2 Integration Testing:

- Verify the interaction between different modules to ensure they work together seamlessly.

7.3 User Acceptance Testing (UAT):

 - Conduct testing with real users to validate that the system meets their needs and expectations.

8. Deployment Strategy:
8.1 Rollout Plan:
- Define a phased deployment strategy, considering factors such as geographic locations, user roles, or
functionalities.

8.2 Data Migration:

- Plan for the migration of existing data, if applicable, to the new system.

9. Maintenance and Support:

9.1 Maintenance Procedures:
- Outline procedures for routine maintenance tasks, bug fixes, and system updates.

9.2 Customer Support:

- Establish channels for user support, including helpdesk, FAQs, and user manuals.

10. Scalability and Performance:

10.1 Scalability Measures:
- Design the system to handle a growing user base by implementing scalable infrastructure and databases.

10.2 Performance Monitoring:

- Implement tools for monitoring system performance, identifying bottlenecks, and optimizing response
times.

This system design provides a comprehensive blueprint for the Doctor's Appointment Online Portal, covering
architectural, database, user interface, application logic, security, integration, testing, deployment, and
maintenance aspects. The design aims to create a scalable, secure, and user-friendly platform for efficient
doctor-patient interactions.

Validation Checks

Validation checks are essential to ensure the accuracy, completeness, and consistency of data in the Doctor's
Appointment Online Portal. Here are five validation checks that can be implemented:
1. Date and Time Validation:
- Purpose: To ensure that appointment scheduling is based on valid and future dates and times.
- Validation Criteria:
- Appointments cannot be scheduled in the past.
- Only available time slots should be selectable.
- Prevent overlapping appointments for a specific doctor.

2. User Input Validation:

- Purpose: To validate user inputs and prevent potential errors or malicious activities.
- Validation Criteria:
- Ensure that required fields (e.g., patient name, contact information) are not left blank.
- Validate email addresses, phone numbers, and other contact details.
- Implement input length checks to prevent excessively long or short entries.

3. Doctor Availability Validation:

- Purpose: To ensure that appointments are scheduled during times when doctors are available.
- Validation Criteria:
- Check the doctor's availability for the selected date and time.
- If a doctor is not available, provide alternative time slots or suggest another available doctor.

4. Appointment Conflict Validation:

- Purpose: To prevent double booking and conflicts in the appointment schedule.
- Validation Criteria:
- Check the appointment database to ensure that a patient does not have overlapping appointments.
- Verify that a doctor does not have multiple appointments scheduled for the same time.

5. User Role-Based Validation:

- Purpose: To ensure that users have appropriate permissions based on their roles.
- Validation Criteria:
- Implement role-based access controls to restrict access to specific functionalities based on the user's role
(e.g., patient, doctor, administrator).
- Restrict users from performing actions outside their designated roles.
These validation checks contribute to the overall reliability and integrity of the Doctor's Appointment Online
Portal by preventing data inconsistencies, ensuring the accuracy of scheduling, and enhancing the overall user
experience. Implementing these checks helps in maintaining a system that is both secure and user-friendly.

Implementation and Maintenance

Implementing and maintaining a Doctor's Appointment Online Portal involves several crucial steps to ensure a
smooth and reliable operation. Here are seven steps for the implementation and maintenance of the system:

1. Project Planning and Requirements Clarification:

- Implementation:
- Develop a detailed project plan outlining tasks, timelines, and resource requirements.
- Clarify and finalize the system requirements in collaboration with stakeholders, including healthcare
professionals, administrators, and potential users.

- Maintenance:
- Regularly review and update the project plan to accommodate changes and improvements.
- Conduct periodic reviews with stakeholders to ensure the system continues to meet evolving
requirements.

2. System Development and Testing:

- Implementation:
- Develop the online portal based on the defined system design, incorporating user interfaces, application
logic, and database components.
- Conduct thorough unit testing, integration testing, and user acceptance testing to identify and resolve
issues.

- Maintenance:
- Implement a version control system to track changes to the codebase.
- Establish a testing environment for ongoing testing of new features, updates, and bug fixes.

3. Deployment and User Training:

- Implementation:
- Deploy the system in a phased manner, starting with a controlled release to a limited user group.
- Provide training sessions for users (patients, doctors, administrators) on how to use the portal effectively.

- Maintenance:
- Conduct periodic refresher training sessions for users to introduce new features or address common
issues.
- Collect feedback from users to identify areas for improvement in the training process.

4. Data Migration and System Integration:

- Implementation:
- Migrate existing data from legacy systems to the new portal, ensuring data integrity.
- Integrate the portal with external systems such as Electronic Health Records (EHRs) or billing systems.
 - Maintenance:
- Regularly audit and optimize data storage to maintain system performance.
- Monitor and update integrations to accommodate changes in external systems.

5. Security Implementation and Monitoring:

- Implementation:
- Implement robust security measures, including encryption, secure authentication, and role-based access
controls.
- Conduct penetration testing to identify and address potential vulnerabilities.

- Maintenance:
- Regularly update security protocols to address emerging threats.
- Monitor system logs for any suspicious activities and implement measures to mitigate security risks.

6. Regular Updates and Enhancements:

- Implementation:
- Release regular updates with new features, improvements, and bug fixes based on user feedback and
changing requirements.
- Implement a feedback mechanism to gather input from users.

- Maintenance:
- Establish a schedule for regular updates and maintenance tasks.
- Continuously analyze user feedback and system performance to prioritize and plan future enhancements.

7. Ongoing Support and Monitoring:

- Implementation:
- Provide initial support during the rollout phase to address any immediate issues.
- Establish a helpdesk or support system for users to report problems.

- Maintenance:
- Maintain a dedicated support team to address user inquiries and technical issues.
- Monitor system performance, conduct regular health checks, and promptly address any issues that arise.

By following these seven steps, you can ensure a successful implementation of the Doctor's Appointment
Online Portal and establish effective maintenance practices for long-term system reliability and user
satisfaction.
Future scope of the Mini Project
The future of a Doctor's Appointment Online Portal holds several promising opportunities for enhancement
and expansion. Here are some potential future scopes for the system:

1. Telemedicine Integration:
- Explore the integration of telemedicine features, allowing patients to have virtual consultations with
healthcare professionals.
- Implement secure video conferencing and real-time communication tools within the portal.
2. Artificial Intelligence (AI) for Appointment Prediction:
- Integrate AI algorithms to predict appointment demand based on historical data, helping optimize
scheduling and resource allocation.
- Implement smart scheduling systems that consider factors like seasonality and demographic trends.

3. Mobile Application Development:

- Develop dedicated mobile applications for iOS and Android platforms to enhance accessibility for users.
- Implement additional features, such as appointment reminders and health tracking, within the mobile app.

4. Advanced Analytics and Reporting:

- Enhance the analytics and reporting capabilities to provide detailed insights into appointment trends,
patient demographics, and system usage.
- Implement predictive analytics to forecast future demands and improve resource planning.

5. Patient Engagement Features:

- Implement features to enhance patient engagement, such as personalized health information, wellness tips,
and interactive tools for self-assessment.
- Integrate a patient feedback system to gather insights on their experiences and satisfaction.

6. EHR and Health Data Exchange:

- Strengthen integration with Electronic Health Records (EHRs) to provide a seamless flow of patient
information between healthcare systems.
- Explore partnerships with other healthcare providers to enable secure health data exchange.

7. Blockchain for Data Security:

- Explore the use of blockchain technology to enhance data security and integrity, ensuring patient
information remains confidential and tamper-proof.
- Implement smart contracts for secure and automated appointment processes.

8. Automated Prescription and Refill Requests:

- Integrate features for doctors to electronically prescribe medications and allow patients to request
prescription refills through the portal.
- Implement secure and compliant e-prescribing functionalities.
9. Enhanced AI Chatbots for Patient Assistance:
- Develop AI-driven chatbots to provide instant assistance to patients regarding appointment scheduling,
general health inquiries, and follow-up care instructions.
- Implement natural language processing for more intuitive interactions.

10. Global Expansion and Multilingual Support:

- Consider expanding the portal's reach to a global audience by providing multilingual support.
- Collaborate with healthcare providers in different regions to adapt the system to local healthcare practices
and regulations.

11. Wearable Device Integration:

- Explore integration with wearable devices to capture and monitor real-time health data.
- Implement features that allow doctors to access patient-generated health data for more informed decision-
making.

12. Remote Patient Monitoring:

- Explore the integration of remote patient monitoring devices for continuous tracking of vital signs and
health parameters.
- Implement alert systems for doctors in case of abnormal readings, enhancing proactive healthcare
management.

By considering these future scopes, the Doctor's Appointment Online Portal can evolve into a comprehensive
healthcare management platform, offering advanced features and contributing to the ongoing digital
transformation in the healthcare industry..

NOIDA INSTITUTEOF ENGINEERINGAND TECHNOLOGY,

GREATER NOIDA
(An AutonomousInstitute Affiliated to AKTU, Lucknow)
 BONAFIDE CERTIFICATE

This is certified that the Mini Project titled "Name of the Project" is the bonafide work of "Students

Name and university Roll No" who carried out the project under my supervision.

(Signature of Mentor)

Name of Mentor

Dr. C S Yadav Sir

Designation of Mentor
Date :

(Signature of Dean) (Signature of HoD)

Prof. (Dr.) C. S. Yadav Dr. Apoorva Joshi

Dean, MCA HoD, MCA

Date: Date :