BCA 320 Minor Project Report Sample for GGSIPU BCA Sem 6
Bachelor of Computer Applications
- Classification
- Practical
- Credits
- 6
- Internal marks
- 40
- External marks
- 60
Subject overview
The BCA 320 Minor Project Report from Unnati Educations is a complete 121-page model report on FoodieExpress, an online food ordering system built in Python and Django, with a 4-page synopsis, 8 chapters, 38 figures, 37 tables and 61 passing automated tests. It follows the GGSIPU BCA scheme for the batch admitted in 2024-25 onwards.
Available Study Materials
No materials available yet
Explore the other subjects and available resources in this academic period.
Browse related subjectsBCA 320 Minor Project at a glance: GGSIPU BCA Sem 6 credits, marks and report format
BCA 320 has no units and no written end-term paper. You build one software project in Semester 6 and submit a synopsis plus a bound report. It sits with the other GGSIPU BCA Semester 6 papers.
| Code, title, semester | BCA 320 Minor Project (no T or P suffix), BCA Semester 6 |
|---|---|
| Category and credits | PRJ (Major/Minor Project), L 0, T/P 14, 6 credits |
| Marks | 100: 40 internal + 60 external |
| Applies to | Batch admitted in academic session 2024-25 onwards |
| What you submit | One summary/abstract (synopsis, about 3-4 pages) and one hard copy of the report, about 75 pages excluding coding |
| Written exam | None; no paper-setter instructions or duration printed |
| Who does it | Every BCA student by default; supervisor allotted at the end of Semester 5 |
| Topic rule | "The student shall do the Minor project in any emerging technology" |
| Exam and result rules | GGSIPU Ordinance 11 |
BCA 320 Minor Project Report chapter-wise: 8 chapters, 38 figures and 61 tested cases on FoodieExpress
The sample project is FoodieExpress, an ordering site one restaurant can own: customers browse 22 dishes, check out and track orders, while staff process orders and read sales reports. It is a Django project report for BCA, and its chapters follow the order printed in the official report format. Notes for every other paper: GGSIPU BCA notes.
You can open the cover, contents, synopsis and four chapter pages through the sample PDF above, then judge whether this IPU BCA minor project report matches the depth your guide expects. Use the report as a model of structure, depth and evidence; your own project, code and certificates must be your own work.
BCA 320 Synopsis: the 10-heading summary submitted with the report
Four pages, also bound inside the report (pages x-xiii). It answers the eight points the guidelines ask for, then adds Resources and Limitations and a Conclusion, with a Level 0 DFD on page 3.
BCA 320 Chapter 1: Objective and Scope of the Project
Pages 1-5 (also covered as "Introduction, Objective and Scope of the Project"). It sets out why phone-and-paper orders fail, eight numbered objectives, three user types (guest, customer, staff) and a road map of the report.
| Within scope | Outside present scope |
|---|---|
| Single restaurant, one menu | Multiple restaurants |
| Cash or UPI on delivery | Online payment gateway |
| Order tracking by status | Live GPS rider tracking |
| On-screen messages | SMS, e-mail and push alerts |
Quick look: in scope vs future work (from page 4)
- Within scope
- Single restaurant, one menu
- Outside present scope
- Multiple restaurants
- Within scope
- Cash or UPI on delivery
- Outside present scope
- Online payment gateway
- Within scope
- Order tracking by status
- Outside present scope
- Live GPS rider tracking
- Within scope
- On-screen messages
- Outside present scope
- SMS, e-mail and push alerts
BCA 320 Chapter 2: Theoretical Background and Definition of Problem
Pages 6-11. Theory on HTTP sessions, Django's Model-View-Template pattern, ORM, transactions and PBKDF2 password hashing, then the existing system (seven problems), a one-paragraph problem definition and an old-vs-new comparison.
| Aspect | Existing | Proposed |
|---|---|---|
| Billing | Manual, error-prone | Automatic, rule-based, tested |
| Capacity | One call at a time | Many customers together |
| Order status | Unknown to customer | Five-step online tracker |
| Reports | Manual totalling | Instant day-wise reports |
Quick look: existing vs proposed system (from page 10)
- Aspect
- Billing
- Existing
- Manual, error-prone
- Proposed
- Automatic, rule-based, tested
- Aspect
- Capacity
- Existing
- One call at a time
- Proposed
- Many customers together
- Aspect
- Order status
- Existing
- Unknown to customer
- Proposed
- Five-step online tracker
- Aspect
- Reports
- Existing
- Manual totalling
- Proposed
- Instant day-wise reports
BCA 320 Chapter 3: System Analysis and Design vis-a-vis User Requirements
Pages 12-25: 16 functional and 8 non-functional requirements with IDs, 9 business rules, a five-part feasibility study, three detailed use cases, a three-tier architecture, a six-table data dictionary and a site map.
| Rule | What it says | Enforced in |
|---|---|---|
| BR-1 | Minimum item total Rs. 99 | place_order() |
| BR-2 | Rs. 30 delivery below Rs. 299, free at or above | calculate_bill() |
| BR-4 | Max 10 units of one dish | add_to_cart() |
| BR-9 | Order keeps the price at ordering time | OrderItem.unit_price |
Quick look: four of the nine business rules (from page 14)
- Rule
- BR-1
- What it says
- Minimum item total Rs. 99
- Enforced in
place_order()
- Rule
- BR-2
- What it says
- Rs. 30 delivery below Rs. 299, free at or above
- Enforced in
calculate_bill()
- Rule
- BR-4
- What it says
- Max 10 units of one dish
- Enforced in
add_to_cart()
- Rule
- BR-9
- What it says
- Order keeps the price at ordering time
- Enforced in
OrderItem.unit_price
BCA 320 Chapter 4: System Planning (PERT Chart)
Pages 26-30: three-point estimates for 11 activities, forward and backward pass, an activity-on-node PERT chart, a Gantt chart, COCOMO and a six-row risk register, with every calculation shown.
Quick look: basic COCOMO for a 1.309 KLOC project (from page 29)
- Organic mode: Effort = 2.4 × (KLOC)1.05 person-months.
- Effort = 2.4 × (1.309)1.05 ≈ 3.18 person-months.
- Time = 2.5 × (3.18)0.38 ≈ 3.88 months.
- Staffing = 3.18 ÷ 3.88 ≈ 0.82, so one developer fits one semester.
BCA 320 Chapter 5: Methodology Adopted, System Implementation, Hardware and Software Used, System Maintenance and Evaluation
Pages 31-36: why Iterative Waterfall, hardware and software tables (Python 3.13, Django 6.1.2, SQLite 3.45), folder structure, deployment with Gunicorn and Nginx, security measures, four maintenance types and an objective-wise evaluation.
Quick look: commands that set up and test the project (from page 34)
pip install django pillow
python manage.py migrate
python manage.py seed_data
python manage.py runserver
python manage.py test -v 2The seed loads 6 categories, 22 dishes, 5 customers and 65 orders; the last command runs the 35 Django tests.
BCA 320 Chapter 6: Detailed Life Cycle of the Project
Pages 37-60: E-R diagram in Chen notation, Level 0-2 DFDs, 11 input and output screens, a flowchart, a state diagram, pseudo-code, the test method and tables, a volume test, a defect log, report printouts and the code sheet.
| Input | Boundary values tested |
|---|---|
| Item total for free delivery | 298, 299 |
| Item total for ordering | 90, 0 |
| Quantity per dish | 10, 11, 0 |
| Pincode | 11, 1100, 110058 |
Quick look: boundary values tested (from page 52)
- Input
- Item total for free delivery
- Boundary values tested
- 298, 299
- Input
- Item total for ordering
- Boundary values tested
- 90, 0
- Input
- Quantity per dish
- Boundary values tested
- 10, 11, 0
- Input
- Pincode
- Boundary values tested
- 11, 1100, 110058
BCA 320 Chapter 7: Coding and Screenshots of the Project
Pages 61-97: 31 pages of commented code (models, services, views, templates, tests) and 10 screenshots of error cases, cancellation and the staff side.
Quick look: the delivery rule inside calculate_bill() (from page 65)
subtotal = _r(subtotal)
gst = _r(subtotal * Decimal(settings.GST_RATE) / 100)
if subtotal == 0 or subtotal >= settings.FREE_DELIVERY_ABOVE:
delivery = _r(0)
else:
delivery = _r(settings.DELIVERY_CHARGE)For an item total of Rs. 298 this gives GST 14.90 and delivery 30, so the total is Rs. 342.90 (test TC-U02).
BCA 320 Chapter 8: Conclusion and Future Scope
Pages 98-100 plus 15 references: achievements tied to evidence, five limitations and ten future features.
| Limitation | Future scope |
|---|---|
| Payment only on delivery | Payment gateway with auto refunds |
| No SMS or e-mail on status change | SMS, e-mail or WhatsApp alerts, OTP login |
| Single restaurant | Multi-outlet support on PostgreSQL |
| No live rider location | Delivery staff page with live location |
Quick look: limitation and the planned fix (from pages 99-100)
- Limitation
- Payment only on delivery
- Future scope
- Payment gateway with auto refunds
- Limitation
- No SMS or e-mail on status change
- Future scope
- SMS, e-mail or WhatsApp alerts, OTP login
- Limitation
- Single restaurant
- Future scope
- Multi-outlet support on PostgreSQL
- Limitation
- No live rider location
- Future scope
- Delivery staff page with live location
Finding the critical path in a minor project PERT chart: excerpt from page 28 of the BCA 320 report
Excerpt from page 28
4.3.2 Critical Path
The critical path is the longest path through the activity network, and every activity on it has zero float. For FoodieExpress it runs A → C → E → F → H → I → K: topic selection, system analysis, UI design, coding of the customer module, unit testing, integration testing and final review. Together these take 48 working days.
A delay in any of these seven activities delays the submission itself, so they were checked every week. The other activities had useful slack. The staff dashboard (G) could slip by 5 days and the report documentation (J) by 21 days, which is why the report was written alongside the coding instead of after it.
How likely is it to finish on time?
In PERT, the variance of the whole project is the sum of the variances of the critical activities only. Here that sum is σ² = 4.111, so the standard deviation is σ = 2.03 days.
To find the chance of finishing within 52 days, convert the deadline to a Z value: Z = (T − Te) / σ = (52 − 48) / 2.03 = 1.97. From the normal table, Z = 1.97 corresponds to a probability of about 97.6%. In plain words, a 4-day buffer over the expected 48 days gives the plan a comfortable margin.
Why this matters in your own report
Many students draw a PERT chart but stop at the picture. A guide reading Chapter 4 looks for three things this page shows: the critical path named activity by activity, the float of the other activities and how it was used, and a probability worked from the variances.
If your project has different activities, the method stays the same: list the activities, run the forward and backward pass, mark zero-float activities, add their variances and compute Z for your deadline.
How to write the BCA 320 synopsis: the eight points the guidelines ask for, shown on FoodieExpress
The guidelines want the synopsis "as brief as is sufficient", about 3-4 pages. The FoodieExpress synopsis is 4 pages and answers each required point under its own numbered heading, so an examiner can tick them off.
| Required point | What the sample writes |
|---|---|
| Statement about the problem | Five concrete failures of phone-and-paper orders, plus why aggregators do not solve it |
| Objective and scope | Four objectives with the real billing rules, then what is outside scope |
| Methodology | Model, architecture, three modules, seven tables and a Level 0 DFD |
| Testing technologies | Django TestCase (35 tests) and Playwright (26 browser tests) |
BCA 320 synopsis points and how the sample answers them
- Required point
- Statement about the problem
- What the sample writes
- Five concrete failures of phone-and-paper orders, plus why aggregators do not solve it
- Required point
- Objective and scope
- What the sample writes
- Four objectives with the real billing rules, then what is outside scope
- Required point
- Methodology
- What the sample writes
- Model, architecture, three modules, seven tables and a Level 0 DFD
- Required point
- Testing technologies
- What the sample writes
- Django TestCase (35 tests) and Playwright (26 browser tests)
Worked example. A weak problem statement says "manual systems are slow". The sample names wrongly noted items, billing errors, no order history, no status for the customer and no daily sales figures, plus aggregator commission. Each point later becomes a Chapter 3 requirement.
Copy three habits: put the topic at the very start, keep an "outside present scope" line so the viva does not drift into features you never built, and end with what makes the system stand out (here, a report cut from 3.5 seconds to about 55 milliseconds).
The same structure works for any GGSIPU BCA Sem 6 minor project synopsis, whether your topic is a hospital system or a machine learning app. Theory behind these chapters, such as DBMS and software engineering, has exam-style practice on GGSIPU BCA important questions.
BCA 320 viva and testing corner: 61 automated tests and 5 logged defects in FoodieExpress
A minor project is judged on evidence, and Chapter 6 gives a lot of it. Every automated test passed on the final code.
| Level | Tool | Test cases | Passed |
|---|---|---|---|
| Unit | Django TestCase | 20 | 20 |
| Integration | Django test client | 15 | 15 |
| System (end-to-end) | Playwright + Chromium | 26 | 26 |
| Volume | Django test client | 5 pages | 5 |
BCA 320 sample report: test results by level (from Table 6.6)
- Level
- Unit
- Tool
- Django TestCase
- Test cases
- 20
- Passed
- 20
- Level
- Integration
- Tool
- Django test client
- Test cases
- 15
- Passed
- 15
- Level
- System (end-to-end)
- Tool
- Playwright + Chromium
- Test cases
- 26
- Passed
- 26
- Level
- Volume
- Tool
- Django test client
- Test cases
- 5 pages
- Passed
- 5
The BCA 320 report documents 61 automated test cases across unit, integration and end-to-end levels, 5 logged defects, 38 figures and 37 tables in 8 chapters.
Viva-style questions the report answers, with where to look:
- Why did you store money as Decimal and not float? Float cannot hold 0.1 exactly; Decimal with half-up rounding matches a hand-made bill (pages 32-33).
- Which SDLC model did you follow, and did you really use its feedback? Iterative Waterfall; two real loops sent the work back to coding and design (page 31).
- How do two orders at the same moment avoid the same number? The next number is read with
select_for_updateinside the saving transaction, with a UNIQUE column as backup (pages 50-51). - What did your volume test find? A 30-day sales report at about 3.6 seconds; one GROUP BY query and two indexes brought it to about 55 milliseconds (pages 55-56).
More practice sits in the BCA 320 important questions.
BCA 320 and the GGSIPU BCA Sem 6 papers it connects to
BCA 320 has no paired lab; the full paper list sits on the GGSIPU BCA syllabus page.
Several Semester 6 papers feed the report directly. BCA 306T Software Project Management supplies the PERT, critical path, COCOMO and risk register of Chapter 4. BCA 302T Distributed Systems and Cloud Computing links to the deployment notes in Chapter 5 (Gunicorn, Nginx, a cloud server). BCA 316T Web Security, an elective, matches the security table of Chapter 5.
Other Semester 6 papers: BCA 304T Machine Learning, BCA 302P and BCA 306P labs, BCA 304P Machine Learning Lab, electives BCA 312T/312P Data Visualization and Analytics, BCA 314T/314P Deep Learning with Python, BCA 316P Web Security Lab, BCA 318T/318P Mobile Application Development, and BCA 374 (NUES).
Earlier papers the report names also show up: BCA 102T Database Management System in the data dictionary, BCA 105T Web Technologies in the templates, BCA 201T Python Programming in the code, BCA 108T Software Engineering in the analysis and BCA 204T Software Testing in Chapter 6.
The report is mapped to the BCA 320 guidelines in the GGSIPU BCA scheme for the batch admitted in 2024-25 onwards. The 2026-27 edition uses Python 3.13 and Django 6.1.2, and its screenshots come from the project's own Playwright test runs. Last updated 13 October 2026. Read how we check content in our editorial policy.
Does the BCA 320 report follow the full GGSIPU format?
Yes. Every item of the official "Format of the student project report" is present, in the printed order. The one point to adjust for your own project is length: the sample has about 71 numbered pages outside the 31 code pages, close to the "about 75 pages" guideline.
| Official item | Where in the report | Status |
|---|---|---|
| I. Cover page as per format | Cover with title, course code, guide and student blocks | Covered |
| II. Acknowledgement | Page i | Covered |
| III. Certificate of the project guide | Page ii, plus a self certificate on page iii | Covered |
| IV. Synopsis | Pages x-xiii, plus a separate 4-page copy | Covered |
| V (i-ii). Objective and scope; theoretical background and definition of problem | Chapters 1-2, pages 1-11 | Covered |
| V (iii-iv). System analysis and design; system planning (PERT chart) | Chapters 3-4, pages 12-30 | Covered |
| V (v). Methodology, implementation, hardware and software, maintenance and evaluation | Chapter 5, pages 31-36 | Covered |
| V (vi). Life cycle: ERD, DFD, screens, process, testing, test report and code sheet | Chapter 6, pages 37-60 | Covered |
| VI. Coding and screenshots | Chapter 7, pages 61-97 | Covered |
| VII-VIII. Conclusion and future scope; references | Chapter 8 and 15 references, pages 98-102 | Covered |
Official BCA 320 report format vs the FoodieExpress report
- Official item
- I. Cover page as per format
- Where in the report
- Cover with title, course code, guide and student blocks
- Status
- Covered
- Official item
- II. Acknowledgement
- Where in the report
- Page i
- Status
- Covered
- Official item
- III. Certificate of the project guide
- Where in the report
- Page ii, plus a self certificate on page iii
- Status
- Covered
- Official item
- IV. Synopsis
- Where in the report
- Pages x-xiii, plus a separate 4-page copy
- Status
- Covered
- Official item
- V (i-ii). Objective and scope; theoretical background and definition of problem
- Where in the report
- Chapters 1-2, pages 1-11
- Status
- Covered
- Official item
- V (iii-iv). System analysis and design; system planning (PERT chart)
- Where in the report
- Chapters 3-4, pages 12-30
- Status
- Covered
- Official item
- V (v). Methodology, implementation, hardware and software, maintenance and evaluation
- Where in the report
- Chapter 5, pages 31-36
- Status
- Covered
- Official item
- V (vi). Life cycle: ERD, DFD, screens, process, testing, test report and code sheet
- Where in the report
- Chapter 6, pages 37-60
- Status
- Covered
- Official item
- VI. Coding and screenshots
- Where in the report
- Chapter 7, pages 61-97
- Status
- Covered
- Official item
- VII-VIII. Conclusion and future scope; references
- Where in the report
- Chapter 8 and 15 references, pages 98-102
- Status
- Covered
Source: BCA Scheme of Examination and Syllabi, batch 2024-25 onwards. The page rules for BCA 320 (margins, Times New Roman, double spacing) appear in the third- and fourth-year syllabus approved on 19.08.2026; the report body uses Times New Roman.
Every course in GGSIPU notes is mapped to its official PDF the same way.
BCA 320 minor project notes FAQs
How do I get the full BCA 320 report?
Send a WhatsApp message to 9899436384 using the button on this page. The BCA 320 report comes only as a printed book; it is not sold as a PDF. The team confirms the edition, price and delivery on WhatsApp. Before ordering, open the sample PDF above to check the cover, contents, synopsis and four chapter pages and see if the depth suits your project.
Can I submit the BCA 320 sample report as my own project?
No. The guide's certificate in every BCA 320 report says the project is your authentic work, and the viva tests whether you built it. Use FoodieExpress as a model: copy the chapter order, the depth of the tables, the PERT arithmetic and the style of the test report, then apply them to your own topic, your own code and your own screenshots.
How many marks is BCA 320 out of, and what is the passing mark?
BCA 320 is marked out of 100: 40 internal and 60 external, with 6 credits. The BCA scheme of examination does not print a separate pass percentage or evaluation method for BCA 320. For minimum marks, re-appear and result rules, read GGSIPU Ordinance 11 on ipu.ac.in and ask your college project coordinator how the external evaluation is held.
How long should a BCA 320 minor project report be?
The guidelines say "about 75 pages (excluding coding)", with a synopsis of about 3-4 pages. The FoodieExpress sample has about 71 numbered pages outside its 31 pages of code, plus front matter and a 4-page synopsis. Body text should be Times New Roman 12 with double spacing, and code in Courier New 10, as the guidelines state.
Which technology does the BCA 320 sample project use?
Python 3.13 with Django 6.1.2, an SQLite database, HTML5 templates and a hand-written CSS3 style sheet, Git for version control and Playwright with Chromium for browser testing. It shows the Model-View-Template pattern, a separate service layer for business rules and Decimal-based billing, all explained in Chapters 2 and 5. The same chapter plan works for any other stack.
Is BCA 320 compulsory for every GGSIPU BCA student?
Yes, by default. The scheme says every student does the Minor Project (BCA 320) in Semester 6, with a supervisor allotted by the college at the end of Semester 5. Students who continue to BCA (Hons.) then do Major Project-1 (BCA 405) in Semester 7 and Major Project-2 (BCA 402) or an internship (BCA 404) in Semester 8.
Get the full BCA 320 Minor Project Report on WhatsApp
The full report is sold as a printed book only; it is not available as a PDF. It is the complete 121-page FoodieExpress project, laid out in the BCA 6th semester minor project report format, so you can keep it beside you while writing your own chapters.
| Part | Pages |
|---|---|
| Unnati cover page | 1 |
| Separate synopsis | 4 |
| Front matter: cover, acknowledgement, two certificates, contents, list of 38 figures and 37 tables, synopsis | 14 |
| Chapters 1-6: analysis, design, planning, life cycle and testing | 60 |
| Chapter 7: code (31 pages) and 10 screenshots | 37 |
| Chapter 8 and references | 5 |
| Total | 121 |
What the BCA 320 report book contains
- Part
- Unnati cover page
- Pages
- 1
- Pages
- 4
- Part
- Front matter: cover, acknowledgement, two certificates, contents, list of 38 figures and 37 tables, synopsis
- Pages
- 14
- Part
- Chapters 1-6: analysis, design, planning, life cycle and testing
- Pages
- 60
- Part
- Chapter 7: code (31 pages) and 10 screenshots
- Pages
- 37
- Part
- Chapter 8 and references
- Pages
- 5
- Part
- Total
- Pages
- 121
Orders are taken on WhatsApp at 9899436384; price and delivery details are shared in the chat.
Order the BCA 320 Minor Project Report book on WhatsApp (8 chapters, 121 pages)
Unnati Educations is an independent education provider based in Vikaspuri, Delhi. We are not affiliated with, authorised by, or endorsed by Guru Gobind Singh Indraprastha University (GGSIPU). 'GGSIPU' and 'IPU' are used only to describe the syllabus our notes follow. For official information, visit ipu.ac.in.
Unnati Education is an independent educational resource provider. Refer to the official university scheme and notifications for authoritative academic requirements.