BCA Sixth Semester: Subjects, Project-III and Study Plan

The sixth semester sits in the middle of your third year, and it is the point where the BCA programme stops feeling like a list of unrelated subjects. You still carry a full theory load, but Project-III gives you a sustained piece of work that runs alongside your classes rather than appearing only at the end of the programme.

This guide covers the six courses you register for in the semester, BCA 351 to BCA 356, and sets out a study rhythm that keeps the project moving while the theory papers still get the attention they need.

What the sixth semester contains

The published curriculum registers 17 credits in this semester across six courses. Five of them are taught courses and one is the project course.

BCA 354 is the lightest course by credit weight and it carries two tutorial hours rather than a practical. BCA 351, 352, 353 and 355 each pair three lecture hours with three practical hours, so four of your six courses have a lab component. BCA 356 carries six practical hours and no lecture hours, which tells you plainly where the semester expects your time to go.

The taught courses in outline

BCA 351 Computer Graphics and animation

A three-credit course with a weekly practical. Graphics and animation work rewards patience with detail: small changes in numbers or timing produce very visible differences in output, so the lab is where the theory becomes real. Start your practical folder in week one and keep every working file, because your own earlier programs become the best revision material you have.

BCA 352 Mobile Programming

Mobile development has a heavy practical footprint and a long setup tail. Install and test your toolchain in the first two weeks rather than the night before the first lab submission, and keep a device or emulator that actually works. Ask your teacher early about the environment the department expects you to use.

BCA 353 Cryptography and Network Security

Security content is cumulative. If you fall behind in the first month, later material becomes guesswork rather than reasoning. Revise the previous week for twenty minutes before each class, and write short summaries in your own words rather than copying slides.

BCA 355 Distributed System

This course is more conceptual than its three practical hours suggest. Diagrams, timelines and worked examples of message flow are worth more to you than dense notes. Draw each idea once by hand and label it fully; that single habit makes exam answers easier to structure.

BCA 354 Technical Writing

Two credits, two lecture hours and two tutorial hours, with no practical. Treat it as an ally rather than a soft option: the conventions you learn here are the same ones your project and internship reports will be judged against. Write your project documentation in this course’s format from the beginning.

How the marks are weighted

A course with lab work carries 20% internal, 20% lab work and 60% external weightage. You must secure a minimum of 40% in each category, and a minimum grade of C+ (GPA 2.3) in each course. That means the lab component is not a formality: it is a fifth of your marks and it has its own pass threshold.

The final theory paper for a course with practical work has three groups: ten brief answer questions of one mark each, six short answer questions of five marks each, and two long answer questions of ten marks each. Group A and Group B together are forty of the fifty marks, so most of the paper is answered in short form. Practise being brief and accurate instead of writing long introductions.

A study rhythm for sixteen weeks

Each semester has sixteen weeks of teaching, excluding examinations, spread over 96 working days. That is enough time if you decide early how you will use it.

1. Week 1: put every course code and its practical hours into one calendar, then block fixed study slots around them.
2. Weeks 2 to 6: keep up with new material week by week. Practicals are far easier when the lecture is still fresh.
3. Weeks 6 to 8: settle the Project-III topic and get it approved in writing before you build anything.
4. Weeks 9 to 12: run the project in small weekly increments and protect one hour a week purely for documentation.
5. Weeks 13 to 16: switch to revision. Rebuild old practicals from memory rather than only re-reading them.

Sitting Project-III alongside theory courses

Project-III is a three-credit course with six practical hours, and it is the second of four project courses in the programme. Students often lose marks here not because the work is weak but because the documentation was written in the final fortnight. Keep a working log, and read our BCA project guide before you choose a topic.

If you want the wider picture of where this semester sits, the course structure page explains how the eight semesters fit together and how credits accumulate.

Mistakes that cost marks

• Treating the lab component as free marks. It has a 40% minimum of its own.
• Choosing a project topic that needs data or hardware you cannot access by week six.
• Skipping lectures in BCA 354 because there is no practical. It teaches the documentation format you will be graded on.
• Leaving lab files on a single laptop with no backup.
• Calculating your standing only at the end of the semester. Track it as you go with the GPA calculator.