BHARATI VIDYAPEETH

COLLEGE OF ENGINEERING (DIPLOMA),

KOLHAPUR
Department of Computer Engineering

Students Details
Enrollment Roll
Name of Student Email ID
No. No.
Jatin C. Mali
2105400029 3008 [email protected]
Atharva A. Shinde
2105400051 3018 [email protected]
Prathmesh S. Sodage
2105400053 3019 [email protected]

2105400044 3015 Suleman N. Patwekar [email protected]

2105400050 3017 Ubada Mohammad Shaikh [email protected]

Name of Internal Guide: Miss.Vanare S. S.

Email Id:[email protected]
 UNDERTAKING BY STUDENTS

We are the students of Third Year Computer Engineering is hereby assuring

that we will follow all the rules and regulations related to the Capstone Project
activity for the academic year 2023 -2024.

The project entitled- “OrderEzy” will be fully prepared by us.

Name Of Student Signature

Jatin C. Mali

Atharva A. Shinde

Prathmesh S. Sodage

Suleman N. Patwekar

Mohammadubada Shaikh
 Rules & Regulations

1. The presentation should cover Literature survey, Scope of project, methodology,

diagrams, data-table discussion and conclusion.

2. Handle the work book very carefully.

3. All students must enter the correct information in the work book.

4. All the entries in the work book must be verified by the concerned guide.

5. Student must report to their respective guide on practical as per the time table.

6. It is expected that students meet their guide twice a week. This meeting details need
to be filled in the table titled “Formal meeting between student and Guide”

7. Activity planned should be completed as per the schedule only.

8. Submit soft copies of report.

9. Work book must be brought at the time of practical/presentation & Final exam.

10. Changes, if any, must be countersigned by the concerned guide.

11. For project presentation/ project examination all the students must report 15 minutes
before the schedule.

12. For queries if any contact your guide.

13. This diary must be submitted to Guide / Coordinator / Committee or the Head of Dept.
Sr. No. Content Page

1) Title

2) Certificate

3) Acknowledgement

4) Abstract

5) Action Plan

6) Rational

7) Introduction

8) Literature Review

9) Problem Definition

10) Proposed Detailed Methodology

11) Resource Required

12) Reference
Weekly Planning Sheet

Week No.: 1
Choosing a Topic
Activities Planned:
• In this week finalizing groups and the research Topic.
• Group members are discussed and talk about research ideas.
• Choose the topic for which a main idea comes most naturally.

Activities Executed:
• In this week, discussed all the topics in different languages.
• Project Execution Phase Activities include:
• Begin work.
• Manage workflow for project tasks.
• Issue management.
• Manage project communications with all stakeholders.

Reasons for delay(if any):

Corrective measures adopted:

Discussed all the topics in different languages.

Remark And Signature of Guide:

Week No.: 2
Researching and outlining.

Activities Planned:
• Describing the Project: Initiated by defining the nature and objectives of the project.
• Defining Scope and Goals: Outlined the specific boundaries and objectives set for the
project.
• Research Commencement: Initiated the groundwork and preliminary research
necessary for the project's commencement.

Activities Executed:
• Initial Phase of Research: Began the execution of the research project, initializing
primary data collection and analysis.
• Defining Preliminary Parameters: Outlined the fundamental aspects required to shape
the project's scope.
• Data Collection Initiation: Started gathering initial resources, information, and
literature relevant to the project.

Reasons for delay (if any):

Corrective measures adopted:

Remark And Signature of Guide:

Week No. 3
Project Proposal

Activities Planned:

• In this week we first decide to make proposal of our project.

• Introduce yourself and provide background information.
• We plan to search introduction, motivation, rational, resource required and project
details of our project

Activities Executed:

We plan our project group members find proposal of project uses advantages and all we Work
together and create rough planning of project.

Reasons for delay (if any):

Corrective measures adopted:

Remark And Signature of Guide:

Week No. 4
Requirement Analysis

Activities Planned:

• In this week we Plan to search which resources are necessary for our project.
• We plan to search information of resources required.
• In overall in this week, we plan about what resources we will need for our project in
the future.

Activities Executed:

• Identifying Resources.
• Gathering Resources.
• Analysing Resources.
• Sorting Necessary Resources for the project.

Reasons for delay (if any):

Corrective measures adopted:

Remark And Signature of Guide:

Week No. 5
Abstract of project.

Activities Planned:
• This week's plan focuses on creating a concise abstract of the project. It includes an
outline of the project's motivation, challenges, the proposed solution, and a summary of
the obtained results.
• The goal is to start searching for information on the required resources and assembling
a comprehensive overview.
• In this week we Create a small abstract of project.
• We plan to search information of resources required. A summary of the motivation,
challenge and solution proposed and results.

Activities Executed:

• Identifying Resources.
• Gathering Resources.
• Analysing Resources.
• Sorting Necessary Resources for the project.
• The executed activities revolve around identifying, gathering, and analysing resources
essential for the project. The focus has been on sorting and selecting the necessary
resources critical to the project's successful execution.

Reasons for delay (if any):

No specific reasons for delay.

Corrective measures adopted:

The provided report lacks details on corrective measures undertaken to resolve any potential
issues or hurdles faced during the project
Remark And Signature of Guide:
Week No. 6
Software requirement and installation.

Activities Planned:
• The main focus of this week is to detail the software requirements necessary for the
project. This involves creating a concise abstract of the project, outlining its
motivation, challenges, the proposed solution, and summarizing the attained results.
• The aim is to initiate the search for information on the necessary resources and compile
a comprehensive overview.
• Planning to create a brief abstract of the project that includes a summary of the
motivation, challenges, proposed solutions, and results.
• Search for the required resources is intended.

Activities Executed:

• Identification, gathering, and analysis of resources were carried out.

• The focus was on sorting and selecting the necessary resources crucial for the project's
successful execution.
Reasons for delay (if any):
No specific reasons for delay were recorded.

Corrective measures adopted:

The provided report lacks details on corrective measures undertaken to resolve any potential
issues or hurdles faced during the project

Remark And Signature of Guide:

Week No. 7
Compiling the research.

Activities Planned:
• Focusing on detailing the essential software requirements for the project. This
encompasses creating a concise abstract outlining the project's motivation, challenges,
proposed solutions, and results summary.
• Initiating a comprehensive search for necessary resources, aiming to compile an
overview.
• Planning to create a brief abstract encompassing the project's motivation, challenges,
proposed solutions, and achieved results.
• Intending to search for the required resources.

Activities Executed:

• Conducted identification, gathering, and analysis of resources.

• Emphasized the sorting and selection of necessary resources critical for the project's
success.
Reasons for delay (if any):
No specific reasons for delay were recorded.

Corrective measures adopted:

The provided report lacks details on corrective measures undertaken to resolve any potential
issues or hurdles faced during the project

Remark And Signature of Guide:

Week No. 8
Planning of Project

Activities Planned:
• Focused planning on structuring the project's components, including defining tasks,
timelines, and goals.
• Conducting a detailed analysis of the project requirements and dependencies.
• Scheduling the allocation of tasks to the concerned team members, assigning
responsibilities, and establishing the overall project roadmap.
• Setting milestones, identifying potential risks, and formulating contingency plans to ensure
project continuity.
• Initiating discussions and collaborations to strategize and streamline the project plan.

Activities Executed:

• Comprehensive structuring of the project components, defining essential tasks, timelines,

and objectives.
• Detailed analysis conducted to ascertain the project's specific requirements and
dependencies.
• Allocation of tasks to the relevant team members, establishing clear responsibilities, and
defining the overall project roadmap.
• Identification of milestones, risk analysis, and development of contingency plans to ensure
project stability and success.
• Initiated discussions and collaborations among the team to refine and streamline the project
plan.
Reasons for delay (if any):
No specific reasons for delay were recorded.

Corrective measures adopted:

The provided report lacks details on corrective measures undertaken to resolve any potential issues
or hurdles faced during the project

Remark And Signature of Guide:

Week No. 9
Design Part 1 with Testing

Activities Planned:
• Initiating the design phase with a focus on creating the initial part of the project's design.
• Setting up a framework for testing during the design phase to ensure better quality and
fewer errors in the final product.
• Planning and organizing the design aspects, which includes data flow, UI/UX, database
design, etc.

Activities Executed:

• Commenced the design phase with a focus on developing the primary components of the
project's design.
• Established a structured testing framework to ensure comprehensive testing during the
design phase, aiming for a higher-quality end product.
• Organized the essential design elements including data flow, user interface, user
experience, and database design.
Reasons for delay (if any):
No specific reasons for delay were recorded.

Corrective measures adopted:

The provided report lacks details on corrective measures undertaken to resolve any potential issues
or hurdles faced during the project

Remark And Signature of Guide:

Week No. 10
Algorithm, System Architecture, Advantages and Disadvantages, and Future Scope

Activities Planned:
• Detailing the algorithms to be utilized within the project, ensuring efficiency and reliability.
• Planning and outlining the system architecture for the project's components and
interactions.
• Analysing the project's advantages and disadvantages to develop strategies for leveraging
strengths and mitigating weaknesses.
• Defining and discussing potential future scopes and scalability factors for the project.

Activities Executed:

• Documented and outlined the algorithms to be employed, emphasizing efficiency and

reliability.
• Designed and detailed the system architecture for the project, mapping its components and
interactions.
• Conducted a comprehensive analysis of the project's strengths and weaknesses, forming
strategies to enhance strengths and mitigate weaknesses.
• Outlined and discussed potential future scopes and factors for scalability within the project.
Reasons for delay (if any):
No specific reasons for delay were recorded.

Corrective measures adopted:

The provided report lacks details on corrective measures undertaken to resolve any potential issues
or hurdles faced during the project

Remark And Signature of Guide:

Week No. 11
Coding Part 2 with Testing

Activities Planned:
• Continuing the coding phase of the project, focusing on developing the subsequent
components.
• Intensifying testing procedures to ensure accuracy and reliability within the developed
components.
• Incorporating design considerations into the coding phase for better implementation of the
intended design.

Activities Executed:

• Progressed the coding phase, implementing additional components as planned.

• Strengthened the testing procedures, aiming to ensure the accuracy and reliability of the
newly developed components.
• Integrated design considerations effectively into the coding phase, ensuring alignment with
the intended design.
Reasons for delay (if any):
No specific reasons for delay were recorded.

Corrective measures adopted:

The provided report lacks details on corrective measures undertaken to resolve any potential issues
or hurdles faced during the project

Remark And Signature of Guide:

Week No. 12
Preparation of Final Report

Activities Planned:
• Focused on the preparation of the final report, compiling and organizing all project-related
information.
• Drafting a comprehensive report outlining the entire project, including methodologies,
findings, analysis, and recommendations.
• Ensuring the final report adheres to the defined standards and fulfills all requirements.

Activities Executed:

• Engaged in compiling and organizing all project-related information to form the final
report.
• Drafted a detailed and comprehensive report encompassing methodologies, findings,
analysis, and recommendations derived from the project.
• Verified that the final report meets the established standards and encompasses all the
necessary project components.
Reasons for delay (if any):
No specific reasons for delay were recorded.

Corrective measures adopted:

The provided report lacks details on corrective measures undertaken to resolve any potential issues
or hurdles faced during the project

Remark And Signature of Guide: