Scribd
Upload
19 views15 pages

Diary

The weekly report details the progress of the Capstone Project 'Panchayat Pay' by students from Ajeenkya DY Patil School of Engineering. Over 14 weeks, the team planned and executed various activities including software installation, frontend and backend development, API integration, and final testing. The project culminated in the submission and presentation of their work to the department.

Uploaded by

sayali shilwant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
19 views15 pages

Diary

The weekly report details the progress of the Capstone Project 'Panchayat Pay' by students from Ajeenkya DY Patil School of Engineering. Over 14 weeks, the team planned and executed various activities including software installation, frontend and backend development, API integration, and final testing. The project culminated in the submission and presentation of their work to the department.

Uploaded by

sayali shilwant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

Ajeenkya DY Patil School of Engineering (Polytechnic)

Via Lohegaon, Pune- 412 105

Department of Computer Engineering


2024-25[6th Sem]
Weekly Report for Capstone Project
ON

“Panchayat Pay”

Submitted By
Roll No. Name of the students Enrollment No.

04 Vedant Waghunde 2216490136

14 Sayali Shilwant 2216490149

17 Gaurav Thakare 2216490152

41 Shreyash Chikane 2216490187

125 Tanmay Padale 2216490179

Under the Guidance of


Prof. Nita Pawar
Project Diary

Week 1

Activities Planned:

Conversation regarding project topic deciding of multiple project aspects. Planning of


resources and its availability.

Action Executed:

Researched tax collection issues. Collected tools: Node.js, HTML, CSS, Java script ,
MySQL.

Reason for delay, if any:

No such

Corrective measures adopted:

No such

Remark and Signature of the Guide:


Week 2

Activities Planned:

Installed all the software required and done the setup of all the developing environment.
Discuss system design.
Action Executed:

Installed Node.js, HTML, CSS, Java script , MySQL. Designed initial architecture.

Reason for delay, if any:

No such

Corrective measures adopted:

No such

Remark and Signature of the Guide:


Week 3

Activities Planned:

We planned the coding part of the application, first start with user interface coding,
basically work on frontend part of the application so planning the frontend.

Action Executed:

Planned resident dashboard. Coded 20% of frontend.

Reason for delay, if any: No such

Corrective measures adopted: No such

Remark and Signature of the Guide:


Week 4

Activities Planned:

Continue frontend coding. Test UI responsiveness.

Action Executed:

Coded 50% of frontend.Tested UI on devices.

Reason for delay, if any:

Minor UI issues.

Corrective measures adopted:

Fixed CSS.

Remark and Signature of the Guide:


Week 5

Activities Planned:

Finalized frontend.
Started backend.
Draft synopsis.

Action Executed:

Completed resident UI.


Set up APIs.
Drafted synopsis.

Reason for delay, if any:

API errors.

Corrective measures adopted:

Debugged APIs.

Remark and Signature of the Guide:


Week 6

Activities Planned:

Develop QR code module.


Start PPT preparation.

Action Executed:

Built QR code system. Completed 30% of PPT

Reason for delay, if any:

No such

Corrective measures adopted:

No such.

Remark and Signature of the Guide:


Week 7

Activities Planned:

Integrate payment gateways.


Progress PPT to 50%.

Action Executed:

Added UPI APIs.


Reached 40% PPT completion.

Reason for delay, if any:

API clarifications needed.

Corrective measures adopted:

Consulted documentation.

Remark and Signature of the Guide:


Week 8

Activities Planned:

Build admin dashboard.


Plan database schema.
Action Executed:

Completed admin UI. Designed MySQL schema.

Reason for delay, if any:

No such

Corrective measures adopted:

No such

Remark and Signature of the Guide:


Week 9

Activities Planned:

Connect backend to database.


Complete 75% of PPT.

Action Executed:

Linked Node.js to MySQL.


Finished 75% of PPT.

Reason for delay, if any:

No such

Corrective measures adopted:

No such

Remark and Signature of the Guide:


Week 10

Activities Planned:

Test backend APIs.


Start Black Book.

Action Executed:

Tested APIs and queries.


Began Black Book outline.

Reason for delay, if any:

No such delays

Corrective measures adopted:

No such

Remark and Signature of the Guide:


Week 11

Activities Planned:

Integrate full system.


Continue Black Book.

Action Executed:

Integrated frontend, backend, QR codes.


Reached 50% Black Book progress.

Reason for delay, if any:

Integration bugs.

Corrective measures adopted:

Debugged issues.

Remark and Signature of the Guide:


Week 12

Activities Planned:

Test full system.


Finalize coding.

Action Executed:

Tested system, fixed minor errors.


Completed coding.

Reason for delay, if any:

No such

Corrective measures adopted:

No such

Remark and Signature of the Guide:


Week 13

Activities Planned:

Finalize Black Book.


Conduct final testing.

Action Executed:

Completed Black Book draft.


Finished end-to-end testing.

Reason for delay, if any:

No such

Corrective measures adopted:

No such

Remark and Signature of the Guide:


Week 14

Activities Planned:

Submit project.
Present to department.

Action Executed:

Submitted project and Black Book.


Presented to Mrs. Nita Pawar.

Reason for delay, if any:

No such

Corrective measures adopted:

No such

Remark and Signature of the Guide:

You might also like