How this page was researched: every rule below was read in Project Guidelines: BCSP-165 (School of Computer and Information Sciences, July 2026, all 77 pages), the BCA_NEW Programme Guide (Version 2.0, July 2026), the BCA_NEW programme page and the Common Prospectus July 2026, on 08 October 2026. Where these documents disagree, the page says so and names both.
The IGNOU BCA project is BCSP-165, a 12-credit Semester VI course for BCA_NEW and BCA_NEWOL learners. You send a 12 to 15 page synopsis, the signed proforma and your guide’s bio-data to your Regional Director in the 1 April to 30 June or 1 October to 31 December slot. After approval you build and test the software and post one hard-bound report of about 100 double-spaced pages. The report carries 150 marks and the viva 50, and the viva includes a compulsory coding demonstration.
- BCSP-165 is not BCSP-064 renamed. Credits rise from 8 to 12, the report from 50 to 80 pages to about 100, the proforma shrinks from 9 items to 6, and the old bans on MS-Access, FoxPro and C or C++ for database projects are gone (BCSP-064 guidelines 2023 and BCSP-165 guidelines 2026).
- The July 2026 documents disagree on the pass mark. The BCSP-165 guidelines ask for 50 percent in the report and in the viva; the BCA_NEW Programme Guide v2.0 says 40 percent in each. Plan for 50.
- The 77-page guidelines are two documents joined. Sections 1 to 3 are adapted from MCS-044 and Section 4 from BCSP-064. Where they clash (spacing, length, where to post, group work), Section 4 is the part written for BCSP-165.
- The synopsis template ends with a mapping rule. ER entities, DFD data stores and database tables must map to each other, modules must map to Level 1 DFD processes, and every Level 1 process needs a Level 2 diagram (Annexure-2). The checker on this page tests it.
- Your code will be run. Annexure-1 calls the coding demonstration at the viva a must that carries significant weightage, and the complete code must be attached unless the organisation you worked for refuses in writing.
- Some page references inside the guidelines are stale. Section 4 still points to “page no. 6”, “13” and “15” of the old BCSP-064 file; in the 2026 file the proforma is on p. 59, the Certificate of Originality on p. 70 and the tools list on p. 66. The remuneration form still says “8 Credits”.
BCSP-165 or BCSP-064: Which IGNOU BCA Project Code Is Yours
Your project code follows your programme structure. The BCA_NEW programme (Programme Guide v2.0, for admissions from July 2024) and BCA_NEWOL list BCSP-165, Project, 12 credits, Semester VI; the Common Prospectus July 2026 shows the same on p. 214. The older BCA (Revised Syllabus) lists BCSP-064, 8 credits, with its own BCSP-064 guidelines. Check the course list on your registration record before you download anything.
The calendar, the guide rules, the 12 to 15 page synopsis, the 150 plus 50 marks and the Regional Director address are the same for both codes. The differences are below.
OFFICIAL-RULE: what changed
| Point | BCSP-064 (BCA Revised, guidelines 2023 to 2024) | BCSP-165 (BCA_NEW / BCA_NEWOL, guidelines July 2026) |
|---|---|---|
| Credits | 8 | 12 |
| Pass mark in its guidelines | 40 percent each: 60/150 report, 20/50 viva | 50 percent each: 75/150 report (the Programme Guide says 40) |
| Report length | 50 to 80 double-spaced pages, code excluded | About 100 double-spaced pages, code excluded, 10 percent either way |
| Proforma | 9 items, including the guide’s designation and a tools note | 6 items; designation is asked on the certificate and remuneration form instead |
| Tools | VB with MS-Access, and C or C++ for database projects, forbidden; dBase, FoxPro, MS-Access barred | Not restricted; Section VII says “always try to use the latest ones” |
| Synopsis and report templates | Item lists only | Annexure-2 (synopsis) and Annexure-3 (report) chapter templates, with three mapping notes |
| Envelope label | BCA PROJECT REPORT (BCSP-064) | BCA_NEW/BCA_NEWOL PROJECT REPORT (BCSP-165) |
Annexure-1, the assessment sheet, is headed “BCSP-064/BCSP-165”, so both codes are marked on the same areas. One more trap: the BCSP-165 course text on the IGNOU programme page still tells learners to “adhere to the BCSP-064 project guidelines”. The July 2026 BCSP-165 file is the newer, course-specific document.
Two Official Files, Two Study Files: the BCSP-165 Document Map
Only the official files carry IGNOU’s rules. The two study files on the right are ours: built on Annexure-2 and Annexure-3 to show the format, watermarked, and not for submission.
IGNOU documents
ignouproject.com samples
Copied synopses and reports “will be awarded very low score and may be sent to Unfair Means Committee of IGNOU” (Section V). Use the samples to see the format, then write your own.
Stuck on your BCA project synopsis or report? Ask us on WhatsApp.
Two Proposal Slots a Year, Each Paired With One Report Window
BCSP-165 has no single deadline. Section I of the guidelines fixes two proposal slots, and the report window and viva month follow from the slot in which your proposal was approved.
OFFICIAL-RULE: Section I calendar
| Proposal slot (to your Regional Director) | Decision | Report window (one bound copy) | Viva-voce |
|---|---|---|---|
| 1 April to 30 June | About 30 days after receipt | 1 July to 30 September | January |
| 1 October to 31 December | About 30 days after receipt | 1 January to 31 March | July |
Section IV puts the decision “within four weeks” of receipt, which matches the calendar’s 30 days. A proposal that is not approved can be resubmitted only in the next slot, so a rejection moves the whole calendar by six months.
BCSP-165 Slot and Viva Planner
This tool needs JavaScript. If this line stays visible after the page loads, the script was blocked.
Choosing an IGNOU BCA Project Topic From Your Semester V and VI Courses
IGNOU publishes no BCSP-165 topic list. The guidelines set three conditions instead: the project “should compulsorily include the software development”, the topic should be “complex and large enough to justify” a BCA project, and it should preferably solve a real problem in a software firm, research body or organisation (Section III and the coordinator’s message). The directions below start from courses only BCA_NEW learners have studied, which makes the subject-area questions at the viva easier to answer.
PLANNING-AID: directions, not approved topics
| BCA_NEW course you studied | A project direction (not a title) | Why it is BCA-sized |
|---|---|---|
| BCOS-184 E-Commerce (Sem V) | Order, stock and delivery manager for a neighbourhood shop that takes orders online | Several roles, stock and order tables, payment status, reports |
| BECS-184 Data Analysis (Sem V) | Feedback survey app for a training institute with a results dashboard | Form builder, response storage, charts, export |
| MSEI-023 Cyber Security (Sem V) | Phishing-report and triage register for a small office | Reporting, status workflow, role-based access, audit log |
| MSEI-027 Digital Forensics (Sem VI) | Evidence chain-of-custody register for a small investigation team | Every hand-over logged, tamper flags, printable custody record |
| BCOS-185 Entrepreneurship (Sem VI) | Lead and follow-up tracker for a home-based tiffin or tuition business | Customers, schedules, reminders, monthly summary |
| MCS-207 DBMS and BCS-053 Web Programming | Hostel room allotment with fee-due reminders | Allocation rules, constraints, notices, dues report |
| BCS-041 Computer Networks | Lab network device inventory and fault log | Device records, fault tickets, uptime summary |
Two cautions. If you plan to join IGNOU’s MCA, its MCSP-232 project guidelines tell learners not to repeat the topic undertaken at BCA level; our IGNOU MCA project (MCSP-232) guide explains what that course asks for. And the title you write on the proforma is the title your report must carry, word for word.
IGNOU BCA Project Synopsis: Eight Items, One Mapping Rule
Section III lists what the proposal must contain, and Annexure-2 turns it into a chapter template. Use both: Section III says what, Annexure-2 says where.
OFFICIAL-RULE: Section III against Annexure-2
| Section III item | Annexure-2 heading where it goes |
|---|---|
| 1. Title of the project | Title page (Appendix 1 format, p. 72) |
| 2. Introduction and objectives | 1.1 Background, 1.2 Objectives, 1.3 Purpose, Scope and Applicability |
| 3. Project category (RDBMS, OOPS, Networking, Multimedia, AI, Expert Systems) | No heading in Annexure-2; add it in Chapter 1 |
| 4. Analysis: DFDs at least up to the second level, ER or class diagrams, database design | 2.3 Conceptual Models; 3.2 Database Design |
| 5. Complete structure: modules, data structures, process logic, testing process, reports | 3.1 Basic Modules, 3.2, 3.3 Procedural Design, 3.6 Test Cases Design |
| 6. Tools, platform, hardware and software | 1.4 Software and Hardware Technologies |
| 7. Industry or client: yes or no, with name and address | No heading in Annexure-2; add it in Chapter 1 |
| 8. Future scope and further enhancement | No heading in Annexure-2; add it after 3.6 |
Annexure-2 also lists front matter: the title page, the original proforma, a “Certificate of Authentication of Work”, an abstract, an acknowledgement and a table of contents. No format is printed for that certificate; the nearest is the Certificate of Originality on p. 70, so ask your guide which wording to use. The three notes at the foot of Annexure-2 are the part most often missed: they decide whether your diagrams, modules and tables tell the same story. The sample synopsis shows one way to meet them: six modules, six Level 1 processes, six data stores, six entities and six tables.
BCSP-165 Synopsis Traceability Checker
This tool needs JavaScript. If this line stays visible after the page loads, the script was blocked.
Type one name per line (or separate with commas). Numbers like “1.0”, “D1” or “M1” at the start are ignored when names are compared.
Before an Evaluator Reads Your BCSP-165 Synopsis or Report
An incomplete proposal is “summarily rejected” (Section IV), and a report missing a signature, a certificate or the approved title is returned for compliance (Section VI). Each costs you a slot of six months. Our team checks the synopsis or report you have written against these BCSP-165 rules and sends it back with corrections marked.
What we check in your synopsis
- All eight Section III items present, placed under the Annexure-2 headings
- DFDs carried to the second level for every first-level process
- Entities, data stores and tables that map to each other
- Modules that match the Level 1 processes
- Length of 12 to 15 pages; tools in 1.4 matching proforma item 6
- Proforma and bio-data: every box filled, every signature dated, guide route valid
What we check in your report
- Title identical to the approved title
- Annexure-3 chapters complete, about 100 double-spaced pages, code excluded
- Unit, integration and system tests designed and reported separately
- Evaluator’s synopsis comments carried into the report
- Approved proforma, synopsis, bio-data and Certificate of Originality bound in
- Contents page, page numbers, figure and table numbering
Synopsis correction Rs 1,000. Project report correction Rs 2,000.
See how synopsis and report correction worksYou remain the author of your synopsis and report, and you sign them. We return corrections on your draft; we do not write, sign or submit the work. Approval is decided by IGNOU’s Project Proposal Evaluator, and marks by IGNOU’s examiners.
The BCSP-165 Proforma, Box by Box
The “Proforma of BCA_NEW/BCA_NEWOL Project Proposal” is printed on p. 59 of the guidelines. It has six numbered items, signature lines and an office-use box. This map shows who fills each part and what returns a proposal.
OFFICIAL-RULE: proforma field map, p. 59
| Box | Who fills it | What to watch |
|---|---|---|
| Enrolment No., Regional Centre Code, Study Centre | You | Copy them from your ID card; the Study Centre is your Learner Support Centre |
| 1. Name and address, e-mail, telephone | You | The decision comes by post in the self-addressed envelope you enclose, so the address must be current |
| 2. Title of the Project | You, with your guide | This title locks the report title; a different title gets the report returned (Section VI, point 7) |
| 3. Name and address of the Guide | You; guide checks | Same name and address as on the bio-data |
| 4. Qualification of the Guide: Ph.D., M.Tech., B.Tech., MCA, Any other | Guide | The degree must be in Computer Science or IT. M.Sc. (Computer Science) is a valid route under Section IV but has no box: tick “Any other” and write it. Attach the bio-data |
| Note under item 4 | Read it | A guide may guide at most 8 BCA_NEW/BCA_NEWOL learners at any time |
| 5. Industrial or teaching experience (years) | Guide | B.E./B.Tech. (CS), MCA and M.Sc. (CS) guides need at least 2 years (Section IV) |
| 6. Software used for this project | You | Name the stack you will really use; it must match 1.4 of the synopsis and the report |
| Printed notes | Read them | Refer to Section VII; demonstrating the project at the viva is a must; synopsis comments must be implemented in the report |
| Signature of the student, with date | You | Every signature needs a date (Section VI, point 2) |
| Signature of the guide, with date | Guide | Original signature, dated |
| Important 1 and 2 | Read them | Bind this proforma, the bio-data and the synopsis into the report later; one student per project |
| Office use: Approved / Not approved, evaluator’s signature, designation, stamp, date | Project Proposal Evaluator | Leave blank |
| Suggestions for reformulating the project | Project Proposal Evaluator | Whatever is written here must be carried into the report |
Guide bio-data checklist
The guidelines ask for the guide’s bio-data “with her/his signature and date” but print no format. Include what the evaluator needs to test the Section IV route:
- full name, current designation and organisation, postal address
- each degree with discipline, university and year, showing the Computer Science or IT degree
- years of teaching or industry experience
- the guide’s signature and the date
Who Can Guide an IGNOU BCA Project: Two Routes, Eight Learners
OFFICIAL-RULE: Section IV
| Route | Qualification | Experience |
|---|---|---|
| 1 | Ph.D. or M.Tech. in Computer Science | None stated |
| 2 | B.E./B.Tech. (Computer Science), MCA or M.Sc. (Computer Science) | At least 2 years in industry or teaching |
The proforma adds that every listed degree “must have been awarded in Computer Science/IT only”, and the remuneration form repeats the cap of eight learners at any time. IGNOU pays the guide through the remuneration form, which the guide signs and you send in a separate envelope with the report. For guide questions common to all programmes, see IGNOU project guide eligibility.
What Goes in the Envelope to Your Regional Director
- The proforma, “duly filled and signed by both the student and the Project Guide with date”.
- The guide’s bio-data, signed and dated by the guide.
- The synopsis, 12 to 15 pages.
- A self-addressed envelope with postage stamps affixed, for the reply by ordinary post.
Address it to the Regional Director of your Regional Centre, not to SOCIS at Maidan Garhi; the calendar and Section IV both name the Regional Director. Keep a photocopy of the complete package. A widely shared BCA synopsis front page addresses the proposal to a “Project Co-ordinator (BCA), SOCIS”; that is not where BCSP-165 proposals go.
IGNOU BCA Project Report Format: Annexure-3 Chapter by Chapter
Annexure-3 is the BCSP-165 report template. The page budget in the last column is our planning suggestion for reaching about 100 pages; IGNOU prescribes only the total.
OFFICIAL-RULE headings, PLANNING-AID budget
| Part | Annexure-3 headings | Planning budget (pages) |
|---|---|---|
| Front matter | Title page; original approved proforma; Certificate of Authenticated Work; abstract; acknowledgement; table of contents; table of figures | Not counted |
| 1. Introduction | 1.1 Background; 1.2 Objectives; 1.3 Purpose, Scope and Applicability; 1.4 Used Software and Hardware Technologies | 6 to 8 |
| 2. Requirements and Analysis | 2.1 Problem Definition; 2.2 Requirements Specification; 2.3 Conceptual Models | 15 to 20 |
| 3. Basic System Design | 3.1 Basic Modules; 3.2 Database Design (schema, integrity); 3.3 Procedural Design (flow charts, algorithms); 3.4 User Interface; 3.5 Security Issues; 3.6 Test Cases Design | 20 to 25 |
| 4. Implementation and Testing | 4.1 Implementation Approaches; 4.2 Coding Details, 4.2.1 Connectivity of code segments as per flowchart; 4.3 Testing: unit, integrated, any other; 4.4 Input and Output Screens | 25 to 30, code listing excluded |
| 5. Results and Discussion | 5.1 Test Reports; 5.2 User Documentation | 8 to 10 |
| 6. Conclusions | 6.1 Conclusion; 6.2 Limitations; 6.3 Future Scope | 3 to 4 |
| Back matter | References; Glossary; Appendix A; Appendix B (complete code) | Code not counted |
Format rules (Sections V and VI): A-4, typed in double space, hard bound; spiral binding is not permitted and a photocopy of the report is not accepted. It must have a contents page and numbered pages, and bind in the original approved proforma, the signed synopsis, the signed bio-data and the Certificate of Originality, with every signature dated. Section 2 adds Times New Roman 12 pt, a 2-inch left margin, 1-inch margins elsewhere, and references numbered in order of use. Test case designs and test reports must be kept separate for unit, integration and system testing, with details of debugging and code improvement. If your software has a user name and password, show how they are protected in transmission to the server.
Posting it: send one hard-bound original to the Regional Director by registered insured post in the report window paired with your approval slot. Mark the top of the envelope “BCA_NEW/BCA_NEWOL PROJECT REPORT (BCSP-165)”. Send the guide’s remuneration form in a separate envelope with it, and keep one identical copy to carry to the viva. The project evaluation fee is Rs 500 for projects above 4 credits, paid with the Term-End Examination form (Common Prospectus July 2026, p. 27); check the amount on the exam form before you pay. The report format template lays out every heading with empty tables.
Where the 150 Marks Come From, and the 40 or 50 Percent Question
OFFICIAL-RULE: Section V and Annexure-1
| Component | Marks | What Annexure-1 looks at |
|---|---|---|
| Project report | 150 | Analysis (SRS, ER, class and data flow diagrams, data dictionary); design (modules, integrity, database and procedural design, interface); coding (comments, standards, error handling, complete code attached); testing (unit, integration and system test design, reports, debugging); report organisation (binding, contents, page numbers, original printouts) |
| Viva-voce | 50 | Presentation of analysis, design, coding, coding demonstration and testing; explanation of the subject area related to the project |
Annexure-1 names the areas but prints no split of marks between them. On the pass mark, the two July 2026 documents differ: Section V of the guidelines says “at least 50% marks separately” in the report (75/150) and the viva, and prints the viva minimum as “50/100” although the viva carries 50 marks. Programme Guide v2.0 gives 40 percent in each (60/150 and 20/50). Work to 50 percent in both, and if your result depends on the difference, write to bca@ignou.ac.in.
The Viva in January or July: Your Code Will Be Run
Reports posted from 1 January to 31 March are examined at a viva in July, and reports posted from 1 July to 30 September in January. Your Regional Centre sends the schedule by letter. Carry your own copy of the report; Section VI says you are “supposed to carry” it. The guidelines do not say whose computer the demonstration runs on, so ask your Regional Centre and be ready to run the software from your own machine.
Annexure-1 tells you what the examiners assess, so prepare against it:
- Walk through your Level 1 DFD and show which module implements each process.
- Open a table in the running database and name the ER entity and data store it maps to.
- Run two test cases from 3.6 live, one that passes and one that rejects bad input.
- Explain one algorithm from 3.3 and point to the code that implements it.
- Show how passwords are stored and protected in transmission.
- Answer questions on the subject area of the project, not only the code.
These are preparation prompts built from Annexure-1, not a list of questions IGNOU asks. For general practice, see IGNOU project viva questions.
Not Approved, or Not Successful: Two Different Restarts
OFFICIAL-RULE: Sections IV and V
| Situation | What the guidelines say | What to send |
|---|---|---|
| Proposal not approved | Suggestions for reformulating are sent to you; resubmit only in the next slot (an April to June proposal can return only in October to December) | Revised synopsis, a new proforma, a copy of the earlier synopsis and the non-approval proforma |
| Project not successful | Section V gives two readings: “re-do the whole cycle” from the synopsis, with a new topic advised; or submit the same project after following the assessment-sheet comments | Synopsis in a normal slot, then the report with the pro-rata fee by demand draft favouring IGNOU, payable at your Regional Centre city |
Failed learners get no separate slots. Because Section V contradicts itself, ask your Regional Centre in writing which route applies before you start again. To follow a report already posted, use the IGNOU project status guide.
Where the July 2026 BCSP-165 Documents Disagree
Information from the documents themselves
| Point | One document says | Another says | Safer reading |
|---|---|---|---|
| Pass mark | Guidelines Section V: 50 percent each | Programme Guide v2.0: 40 percent each | Plan for 50 |
| Credits | Prospectus, Programme Guide, programme page: 12 | Remuneration form in the guidelines: “8 Credits” | 12 |
| Line spacing | Section 2.5 (from MCS-044): single | Section VI (BCSP-165): double | Double for the report |
| Report length | Section 2.5: 80 to 100 pages for analysis, design and testing | Section V: about 100 pages excluding code, 10 percent either way | 90 to 110 pages excluding code |
| Where the report goes | Section 2.5: Study Centre | Sections I and V: Regional Director, registered insured post | Regional Director |
| Group projects | Section 2.3.4 mentions students doing the project in a group | Sections II and VI: not more than one student per project | One student |
| Report outline | Section 1 adds a Role and Responsibility Form, Achievements and other headings | Annexure-3 omits them | Annexure-3; ask your guide before adding |
| Program disk or CD | Section 2: in the appendices “when appropriate” | Section 4: not mentioned | Ask your Regional Centre |
The pattern is consistent: Sections 1 to 3 were “partially adapted” from MCS-044 and Section 4 from BCSP-064, as the credits page of the guidelines states. Where Section 4 speaks, it is the part written for BCSP-165.
IGNOU BCA Project: Questions Students Ask
Can I send my BCA synopsis in Semester V?
The guidelines encourage project work “in their final semester” and set two slots a year, but they do not say whether a Semester V proposal is accepted. Confirm with your Regional Centre before you post it; the planner on this page shows both options.
Do I send the BCA synopsis to SOCIS or to my Regional Centre?
To the Regional Director of your Regional Centre, in the 1 April to 30 June or 1 October to 31 December slot (Section I and Section IV).
How many pages should the IGNOU BCA project synopsis be?
12 to 15 pages, as printed in the proposal checklist on p. 60 of the BCSP-165 guidelines.
Do I need a CD or a plagiarism report with the BCA project report?
The BCSP-165 section asks for neither. Section 2, adapted from MCS-044, says appendices should include a program disk or CD “when appropriate”. Ask your Regional Centre whether it wants one.
Can two of us submit one BCA project?
No. Sections II and VI say not more than one student is permitted to work on a project.
Can I use Python, PHP, React or a NoSQL database?
Yes. Section VII lists current tools across web, mobile, databases, cloud and AI and says the choice “is not restricted”; the old BCSP-064 bans do not apply to BCSP-165.
Can I reuse my BCA project topic in IGNOU MCA?
The MCSP-232 MCA project guidelines tell learners not to repeat the topic undertaken at BCA level, so plan a different MCA topic. The MCSP-232 project guide covers the MCA rules.
What fee is paid for the BCA project?
The Common Prospectus July 2026 (p. 27) sets the project evaluation fee at Rs 500 for projects above 4 credits, paid with the Term-End Examination form. A failed project resubmitted later carries a pro-rata fee by demand draft (Section V).
Official Sources Used on This Page
- Project Guidelines: BCSP-165, SOCIS, IGNOU, July 2026 (Sections 1 to 4, Annexures 1 to 3), eGyanKosh handle 123456789/123879. Read in full 08 October 2026.
- BCA_NEW Programme Guide, Version 2.0, SOCIS, July 2026: structure, BCSP-165 evaluation scheme, durations.
- BCA_NEW programme page, accessed 08 October 2026: BCSP-165 12 credits, fee Rs 8,300 per semester, 36 to 72 months.
- Common Prospectus July 2026, IGNOU: p. 27 project evaluation fee; pp. 213 to 214 BCA_NEW structure.
- BCSP-064 Project Guidelines (BCA Revised Syllabus), SOCIS, July 2023 to January 2024.
- MCSP-232 Project Guidelines, MCA_NEW, SOCIS, 2025: rule against repeating the BCA topic.
- SOCIS page, School of Computer and Information Sciences. Coordinator e-mail in the guidelines: BCA@ignou.ac.in, BCAOL@ignou.ac.in.
Related pages: all IGNOU project guides, IGNOU synopsis format, IGNOU BCA syllabus, IGNOU BCA assignments and the IGNOU CGPA calculator.
ignouproject.com is an independent service and is not affiliated with or endorsed by Indira Gandhi National Open University (IGNOU). The sample synopsis and report template are study references; do not submit them as your own work.
BK Sahni iD 0009-0005-8092-459X
Founder, Shri Chakradhar Publication Pvt. Ltd. & ignouproject.com — helping IGNOU distance-learning students since 2010 (5,00,000+ students supported across MBA, MCom, MA & more). Author of IGNOU exam guides, solved assignments & project reference books.
Disclosure: Shri Chakradhar Publication Pvt. Ltd. and ignouproject.com are independent third-party study-help services — not the official IGNOU website. Always verify final dates and rules on ignou.ac.in.
