Academic Year 2025-26

DEPARTMENT OF COMPUTER ENGINEERING

Minor Project Log-Book

Course Code-CEPR53
Course Name-Project Based Learning: Minor Project Lab-II

Roll No Name of Student Signature of Student

17 Hamza Gandhi
21 Mohamed Hamza Godil
28 Husein Khorakiwala
30 Abbas Makasarwala

Name of Project- “Streamlined Commerce: A Stripe-Powered Payment Solution”

Name of Guide- Dr. Shyamal Virnodkar

PBL Outcomes

At the end of the course, the student will be able to:

Sr. No PBL Outcomes

1 Identify societal/research/innovation/entrepreneurship problems
through appropriate literature survey.
2 Identify methodology for solving above problems and apply engineering
knowledge to solve and validate the result using test cases /benchmark
data/theoretical/inferences/ experiments/ simulations.
3 Use standard norms of engineering practices and project management principals
to analyze and evaluate the impact of solution / product / research / innovation /
entrepreneurship towards societal / environmental / sustainable development.
4 Communicate through technical report writing and oral presentation.
5 Gain technical competency towards participation in competitions, hackathons,
etc.
6 Demonstrate capabilities of self-learning in a group, which leads to lifelong
learning to develop interpersonal skill to work as a member of a group or as a
leader.
Continuous Assessment

Distribution of Term work marks for both semesters shall Practical

be as below: Marks
Marks awarded by guide/ supervisor based on implementation 10
Marks awarded by review committee 10
Quality of Project report 05

Guidelines for Minor Project

Sr. No Guidelines
1 Minor project may be carried out in one or more form of following: Product
preparations, prototype development model, fabrication of set-ups, laboratory experiment
development, process modification/development, simulation, software development,
integration of software (frontend-backend) and hardware, statistical data analysis,
creating awareness in society/environment etc.
2 Students shall form a group of 3 students, as it is a group activity.
3 Students should do survey and identify needs, which shall be converted into problem
statement for minor project in consultation with faculty supervisor/head of
department/internal committee of faculties.
4 Students shall submit implementation plan in the form of Gantt/PERT/CPM chart, which
will cover weekly activity of minor project.
5 The work may result in research/white paper/ article/blog writing and publication and
also the work may result in business plan for entrepreneurship product created. The work
may result in patent filing.
6 Faculty supervisor may give inputs to students during minor project activity; however,
focus shall be on self-learning.
7 Students in a group shall understand problem effectively, propose multiple solution and
select best possible solution in consultation with guide/ supervisor.
8 Students shall convert the best solution into working model using various components of
their domain areas and demonstrate.
9 The solution to be validated with proper justification and report to be compiled in
standard Format. Software requirement specifications (SRS) documents, research papers,
competition certificates may be submitted as part of annexure to the report.
10 With the focus on the self-learning, innovation, addressing societal problems and
entrepreneurship quality development within the students through the Minor Projects, it
is preferable that a single project of appropriate level and quality to be carried out in two
semesters by all the groups of the students. i.e. Minor Project 1 & 2 in semesters V and
VI.
11 However, based on the individual students or group capability, with the mentor’s
recommendations, if the proposed Minor Project adhering to the qualitative aspects
mentioned above gets completed in odd semester, then that group can be allowed to work
on the extension of the Minor Project with suitable improvements/modifications or a
completely new project idea in even semester. This policy can be adopted on case by
case
basis.
Assessment Index Sheet
Week No. Detailed Explanation Signature of
guide with date
Week 1 Project Brief & Planning
● Client provides the initial brief and
project requirements.
● Team discusses and documents
project scope and deliverables.
● Roles assigned: frontend, backend,
API, payment integration.

Week 2
State Management & Setup
● Frontend begins implementing basic state
management.
● Backend sets up database schema (users,
products, pricing).
● UI wireframes/mockups are created and
reviewed.

Week 3
UI Building & API Foundations
● Frontend starts building main UI screens
and layout.
● Backend connects to database and starts
basic API endpoints.
● Create and test initial APIs for product
creation and retrieval.
Week No. Detailed Explanation Signature of
guide with date
Week 4
Stripe Product API Integration
● Backend creates API for Stripe
product_id.
● Connect Stripe dashboard to
application backend.
● Ensure API returns Stripe product
data correctly.
● Integrate basic product listing on
frontend.
Week 5
Maps Integration & Mid-Testing
● Start integrating Google Maps API
for location mapping.
● Frontend displays map component on
relevant screens.
● Backend prepares
coordinates/locations
● Run first internal testing round for
state & product flow.
Week 6
Dynamic Dropdowns for State & Brand
● Frontend creates dynamic
dropdown for state selection.
● Backend API built for fetching list
of states.
● Brand dropdown implemented; API
for listing brands developed.
● Test dropdown interactivity and
data fetch accuracy.
Week No. Detailed Explanation Signature of
guide with date

Week 7
Pricing Tier Mapping & Display
● Backend maps Stripe price_id to pricing
tiers in DB.
● Pricing tiers displayed on frontend.
● Ensure filtering and categorization by
pricing tier.
● Validate Stripe price linking and tier logic.

Week 8
Checkout Session & Slot API
● Backend creates checkout session
using Stripe API.
● Implement frontend "Book Now" or
"Checkout" flow.
● Slot creation API developed post-
payment attempt.
● Link checkout session with selected
product and slot.

Week 9
Webhooks & Payment Confirmation Logic
● Stripe webhook events handled (success,
failure, recurring).
● On success: assign slot to user and store in
DB.
● On failure: log attempt and notify user.
● Handle recurring payments; update
slot/payment history.
Week No. Detailed Explanation Signature of
guide with date

Week 10
Mid-Project Testing & Integration
● Run second testing covering full
booking flow.
● Test webhook reliability and slot
assignment.
● Frontend refinements based on
test results.
● Backend error logging and
validation
Week 11
Testing
● Tested Individual API’s
● created individual test webhooks part
with stripe

Week 12
Full System Testing
● End-to-End Testing from UI to
payment confirmation.
● Fix major bugs and polish UI for
delivery.
● Test responsiveness, error handling,
and edge cases.