BCA Subjects List with Course Codes and Credits

This page is the reference list: every course code, course name and credit hour in the BCA programme, semester by semester. Course codes are the part of the structure people look up most often, because they appear on registration slips, internal assessment sheets, lab report covers and project documents.

The lists below follow the published curriculum order. Nothing has been added, renamed or rounded, so you can use the tables directly when a form asks for a code or a credit value.

How the course code system works

The codes are grouped by semester. Semester I uses BCA 101 to BCA 106, Semester II uses BCA 151 to BCA 156, Semester III uses BCA 201 to BCA 206, Semester IV uses BCA 251 to BCA 256, Semester V uses BCA 301 to BCA 306, Semester VI uses BCA 351 to BCA 356, Semester VII uses BCA 401 to BCA 406, and Semester VIII uses BCA 451 to BCA 454.

The grouping is a useful habit to build early. If a code starts with 1, it belongs to the first year; 2 is the second year, 3 is the third year, and 4 is the fourth year. That means an unfamiliar code on a notice board still tells you roughly where in the programme it sits.

Semester I subjects

Semester II subjects

Semester III subjects

Semester IV subjects

Semester V subjects

Semester VI subjects

Semester VII subjects

Elective-I and Elective-II are slots rather than single fixed courses. Each slot is worth 3 credits and offers a published choice, which is covered separately in the electives guide.

Semester VIII subjects

Reading the credit column

Most courses carry 3 credits, which reflects three lecture hours a week in the published table. Three courses sit at a lower value: Hardware Workshop in Semester I and Principles of Management in Semester II are 1 credit each, Applied Economics in Semester III and Financial Accounting in Semester VII are 2 credits each, and Technical Writing in Semester VI is 2 credits. Project-I is 2 credits, while Project-II, Project-III and Project-IV are 3 credits each.

Credit value is not a difficulty rating. A 1-credit workshop still requires attendance and a pass, and a 2-credit course still needs a C+ grade like every other course in the semester.

Where the practical hours sit

In the published tables, courses such as Programming in C, Digital Logic, Data Structure and Algorithms, Database Management System, Web Technology-I, Operating Systems, Python Programming, Computer Network, Artificial Intelligence, Mobile Programming, Cloud Computing and the elective slots list three practical hours a week alongside three lecture hours. Hardware Workshop lists two practical hours, Project-I lists four, and Project-II, Project-III and Project-IV list six.

Those hours are the reason a semester with several coding courses feels heavier than its credit total suggests. Plan the lab time first and the reading around it. You can also check how each course is weighted in the BCA course structure guide and browse the current term in the subject browser.

How to keep this list useful through the programme

Course codes come up more often than you would expect. Registration forms, internal assessment sheets, lab report covers, project documentation and transcript queries all expect the printed code, and a code copied incorrectly in the first week can follow you through a whole semester. Save this page, or copy the tables into one notes file, and update it only when your department issues an official change.

It also helps to hold on to the difference between a course and a slot. Elective-I, Elective-II, Elective-III and Elective-IV are slots worth 3 credits each, and the subject you actually study in that slot depends on the option you choose. Everything else in the lists above is a fixed course with a fixed name and a fixed credit value.

The numbering also hints at what a course expects from you. A code beginning with 2, 3 or 4 generally follows on from earlier courses in the same subject area, such as OOP in Java before Advance Java Programming, or Web Technology-I before Web Technology-II. Checking the code family first is a quick way to see whether a subject is new ground or a continuation.

One last habit worth building: when you receive an internal assessment sheet or a result slip, check the codes against this page rather than against memory. It takes a minute and it catches transcription errors before they reach an official form.