IGNOU MCA Project (MCSP-232): The Complete 2026 Guide to Synopsis, Report and Viva
Updated 11 November 2026 · Checked against the July 2026 & January 2027 MCSP-232 guideline · 25 min read
By IGNOU Buddy Team · Checked against IGNOU’s official documentsWhat is the IGNOU MCA project (MCSP-232)?
MCSP-232 is the 12-credit software development project in Semester 4 of IGNOU’s MCA programme. First you get a synopsis (project proposal) approved, sent between 1 April–30 June or 1 October–31 December. Then you build the software and submit a 100–125 page report. The report is marked out of 150 and the viva out of 50, and you must score at least 40% in each.
- Check which rulebook you follow before anything else. MCA_NEW (distance) learners post their papers to the Regional Centre. MCAOL (online) learners upload everything on the LMS.
- You can send the proposal once you enter Semester 3. Approval takes 30 days on paper; plan for up to 8 weeks.
- Your guide needs a PhD or MTech in Computer Science plus 1 year of experience, or a BE/BTech (CS), MCA or MSc (CS) plus 2 years. A guide can take at most 5 IGNOU MCA students at a time.
- The project must involve software development. MS Access, FoxPro and dBase are barred, and so are C/C++ for management systems such as hospital or library systems.
- An approved proposal stays valid for one year (two report slots). A failed project means starting again with a new proposal.
At a glance
| Fact | Detail |
|---|---|
| Project code | MCSP-232 (12 credits, Semester 4) |
| Programme(s) | MCA_NEW (post) and MCAOL (LMS) |
| Current guideline | July 2026 & January 2027 edition |
| Synopsis | 15–18 pages, 1 Apr–30 Jun or 1 Oct–31 Dec |
| Approval reply | 30 days to 8 weeks |
| Report | 100–125 pages, code excluded, with a CD (MCA_NEW) |
| Viva | Compulsory, 50 marks |
| Pass rule | 40% in report (60/150) and viva (20/50) separately |
| Guide limit | 5 MCA students |
| December 2026 deadline | 30 Nov 2026, 11:59 PM on OPMS (fee on Samarth by 30 Nov 2026) |
Last checked 11 November 2026 against the official documents listed under Sources.
Table of contents 19 sections
- Which guideline applies to you
- Calendar and slot planner
- Who can be your project guide
- Topics and software IGNOU accepts
- Synopsis format: the 12 parts
- Filling the proforma
- Sending the proposal: checklist
- Approval and “Not Approved”
- Project report structure
- What the evaluator marks
- Formatting, cover page and binding
- Submitting the report
- Viva voce and passing marks
- Failed project or missed slot
- Two students, trainee letter
- Why MCA projects get rejected
- MCA project topic ideas
- A 6-month work plan
- Submit for December 2026
- Check status and result
- हिंदी में संक्षेप
- Get expert guidance
- FAQs
Which MCSP-232 guideline applies to you?
Short answer: MCA_NEW learners follow the July 2026 & January 2027 guideline, which IGNOU published on eGyanKosh in 2026. MCAOL (online MCA) learners follow the separate MCAOL guideline. Both use the same course code, MCSP-232, so many students end up reading the wrong document.
Search results still show older PDFs on IGNOU’s webservices site, and some of them rank above the current file. Check the session printed on the cover before you rely on any rule.
Edition differences that matter
| Point | July 2024 & Jan 2025 edition | July 2026 & Jan 2027 edition (current) |
|---|---|---|
| Fee to resubmit a failed project | ₹2,500 pro-rata fee by demand draft | No amount printed: “get in touch with concerned RC for the pro-rata fee” |
| Software list (section VIII) | “Software and broad areas of application” | “Suggested Software…”, with a new note: the list is only a suggestion, so pick your area of interest or an emerging technology |
| Normalisation | Minimum 3NF; explain any denormalisation | Normalise to at least 3NF |
| Proforma header | One “Study Centre” line | Separate Study Centre Code and Study Centre Name fields |
| Project Coordinator | Not named | Prof. P. V. Suresh, MCA (MCA_NEW) Project Coordinator |
These stayed the same: 12 credits, both proposal slots, both report windows, the guide rules, the five-student limit, the barred software, 150 + 50 marks, and 100–125 pages of documentation.
MCA_NEW vs MCAOL: same code, different route
| Step | MCA_NEW (distance) | MCAOL (online) |
|---|---|---|
| Send the proposal | By post to the Regional Director of your Regional Centre | Upload on the LMS only |
| Guide documents | Signed bio-data plus a certified copy of the guide’s identity proof | Signed bio-data plus a self-attested degree certificate and identity proof |
| Synopsis length | 14–18 pages (p. 6) or 15–20 pages (p. 10). Aim for 15–18. | 15–20 pages; bibliography in IEEE, APA or MLA style |
| Return envelope | A self-addressed, stamped envelope | Not needed |
| Approval notice | By post; 30 days to 8 weeks | By e-mail or on the LMS; about 4–6 weeks |
| Submit the report | One original bound copy with a CD of the executables, by registered insured post | A single PDF on the LMS; keep the executables for the viva |
| Viva | Face to face at your Regional Centre, called by letter | Online, called by e-mail from your Nodal Regional Centre |
| Two-student projects | Prior recommendation from the Project Coordinator, SOCIS, with a handwritten application | Prior recommendation by e-mail to mcaolsocis@ignou.ac.in |
The MCA_NEW guideline asks for the report by post. IGNOU also runs an online project-report portal for some term-end cycles; its June 2026 notice asked for a single scanned PDF that includes the approved proforma, synopsis, guide bio-data and originality certificate. Follow the route your Regional Centre announces in writing for your cycle. If none is announced, follow the guideline and post it.
When to submit: the MCSP-232 calendar
Short answer: Send the proposal between 1 April and 30 June, or between 1 October and 31 December. Submit the report in the window that matches your approval: 1 July–30 September for an April–June proposal, or 1 January–31 March for an October–December proposal.
| Stage | Slot A | Slot B |
|---|---|---|
| Send proposal (synopsis) | 1 Apr – 30 Jun | 1 Oct – 31 Dec |
| Approval comes back | “30 days after the project proposal is received” (calendar). Elsewhere the same guideline says 4–6 weeks and 6–8 weeks, so plan for 8. | |
| Submit report | 1 Jul – 30 Sep | 1 Jan – 31 Mar |
| Viva held | November or January | May or July |
| Second chance (approval valid 1 year) | 1 Jan – 31 Mar | 1 Jul – 30 Sep |
Source: MCSP-232 guideline (July 2026), section I “Calendar for the MCA Project” and section V point 3.
Who can be your IGNOU MCA project guide?
Short answer: Either a person with a PhD or MTech in Computer Science and at least 1 year of experience, or a person with a BE/BTech (Computer Science), MCA or MSc (Computer Science) and at least 2 years of experience, preferably in software development. The proforma adds that the degree must be in Computer Science or IT.
- You choose the guide. The guideline’s steps begin with “Select a topic and a suitable Project Guide”. IGNOU does not allot one.
- The limit is 5 students. At any time, a guide should not supervise more than 5 IGNOU MCA students. Ask before you fill the proforma.
- The guide guides; you do the work. “The complete project work should be done by the student only.” If you skip a phase such as coding, the project can be rejected at any stage.
- Signatures must match. The guide’s signature on the Certificate of Originality must match the one on the proforma.
- The guide signs the proforma but does not approve the project. An IGNOU Project Proposal Evaluator marks it Approved or Not Approved.
Which topics and software does IGNOU accept for MCSP-232?
Short answer: Any topic that involves real software development and is “complex and large enough to justify as a MCA project”, built with current software versions. Your BCA project topic cannot be repeated.
Allowed
- Web, mobile, desktop or cloud applications with a real database
- AI, machine learning, data science, image processing and other emerging areas (named in the 2026 note)
- Networking or socket programs where you write the software
- Any language or tool that is part of the latest technology, even if it isn’t on the list
- A self-defined project agreed with your guide. A company project helps but is not compulsory.
Not allowed
- Physical installation, LAN/WAN configuration, theory-only projects or “study of a system” with no software development
- dBase III Plus, FoxPro, Visual FoxPro, MS Access, or Visual Basic with an MS Access back end
- C or C++ for an information management system (hospital, reservation, library, school or college management)
- Old software versions
- The same topic you did for BCA, or anything copied
Suggested software in the guideline includes Java, Python, C#, .NET, PHP, JavaScript, React, Angular, Vue, Flutter and TypeScript, with MySQL, SQL Server, Oracle, DB2 or NoSQL databases. The 2026 edition calls this list “only suggested”.
The guideline says a copied project is sent to IGNOU’s Examination Discipline Committee as an unfair-means case. Use samples only to understand the format, then write your own.
IGNOU MCA synopsis format: the 12 parts
Short answer: The synopsis (project proposal) should be 15–18 pages and cover twelve parts, from the title to the bibliography. The structure is fixed by section V of the guideline. The tips below show what makes each part strong.
| # | Part (as in the guideline) | What to include so it gets approved |
|---|---|---|
| i | Title of the project | Specific and testable, e.g. “Hostel Allotment and Mess Billing System for a College”. Keep the same title through the synopsis, report and cover. |
| ii | Introduction and objectives | The problem, who faces it, and 4–6 measurable objectives. |
| iii | Project category | One of RDBMS, OOPS, Networking, AI, Expert Systems, Machine Learning, Data Science, Image Processing, Mobile Computing, etc. |
| iv | Tools/platform, hardware and software requirements | Exact versions of the language, framework, database and OS, and minimum hardware. |
| v | Problem definition, requirement specifications, literature review, planning and scheduling | Functional and technical requirements, plus both a Gantt chart and a PERT chart. |
| vi | Scope of the solution | What the system will do, and what it won’t. |
| vii | Analysis | Level 0, 1 and 2 DFDs; a complete ER diagram with cardinality; activity, class and state diagrams as the project needs. |
| viii | Database and table details | Every table with its primary and foreign keys and field constraints. |
| ix | Complete structure | The number of modules with a description and process logic for each, the data structures, the implementation method, and the reports the system will produce. |
| x | Network architecture | Only if your project needs it. |
| xi | Security mechanisms | Login and roles, database-level security, input validation. |
| xii | Future scope and bibliography | Realistic next features, and the books and links you used (MCAOL: IEEE, APA or MLA style). |
How to fill the MCSP-232 proforma, box by box
Short answer: Fill every box. The guideline says an incomplete proforma “will be summarily rejected”.
- Your detailsEnrolment number, Study Centre code and name, Regional Centre and RC code, e-mail and mobile number.
- Name and address of the studentUse the address where you can receive post. The approval comes back in your own stamped envelope.
- Title of the projectThe exact title. It must not change later.
- Guide’s name, address and qualificationTick the degree (PhD, MTech, BE/BTech, MCA or MSc in Computer Science or IT) and attach the bio-data.
- Guide’s working or teaching experienceYears and organisation. It must meet the 1-year or 2-year rule.
- Software usedName the front end, back end and tools with versions, checked against section VIII.
- First submission?Tick Yes, or No if you are resubmitting, and enclose the earlier Not Approved proforma.
- Signatures and datesBoth you and your guide sign and date it. Leave the “For Office Use Only” area blank.
How to send the MCA project proposal
Short answer (MCA_NEW): Post four things to the Regional Director of your Regional Centre: the proforma, the guide’s bio-data with a certified ID copy, the synopsis, and a self-addressed stamped envelope. Write “MCA_NEW Project Proposal (MCSP-232)” on top of the envelope.
The guideline says: “Under no circumstances, should the project proposal be sent to SOCIS, IGNOU, New Delhi.” It goes to your own Regional Centre.
MCAOL learners upload the same documents on the LMS, plus the guide’s self-attested degree certificate.
How long does approval take, and what if it’s “Not Approved”?
Short answer: The calendar says 30 days. Other pages of the same guideline say 4–6 weeks and 6–8 weeks, so plan for 8. If you hear nothing 4–6 weeks after the slot closes, contact your Regional Centre. Quote your enrolment number and Project Proposal number in every letter.
If your proposal comes back Not Approved
- Read the evaluator’s suggestionsThey are written on the returned proforma.
- Fix every pointThe guideline requires the suggestions to be “incorporated in the new project proposal”.
- Resubmit in the next slot onlyRejected in April–June means resubmitting in October–December. Send a new proforma, the revised synopsis, a copy of the earlier synopsis and the Not Approved proforma.
- Or start freshYou may change the topic, software or guide. It then becomes a fresh proposal, still sent with a copy of the Not Approved proforma.
Even an approved proposal can carry suggestions. They must appear in the final project, “otherwise the project may be rejected at any stage of evaluation”.
IGNOU MCA project report structure
Short answer: About 100–125 pages of documentation, not counting the code. Write about your system, not textbook theory. The guideline says theory from reference books “should be avoided as far as possible”. Every component below carries weight in the marking.
Front matter (attach in this order)
- The original approved proforma and project proposal
- The guide’s bio-data, signed and dated
- The Certificate of Originality, signed by you and your guide
- A table of contents with page numbers
Main chapters
| Chapter | What goes in it |
|---|---|
| 1. Introduction and objectives | The problem, users, objectives and scope |
| 2. System analysis | Identification of need; project planning and scheduling (PERT and Gantt); SRS; the software engineering paradigm; DFDs, control flow, state or sequence diagrams, ER model, and class, use-case or activity diagrams as relevant |
| 3. System design | Modularisation; data integrity and constraints; database design; procedural or object-oriented design; user interface design; unit and system test cases |
| 4. Coding | SQL for creating the database with constraints, loading data and setting user access rights; the complete project code with comments; code efficiency, error handling, parameter passing and validation checks |
| 5. Testing | Techniques and strategy, test plan, unit and system test reports, and how you debugged and improved the code |
| 6. System security | Database and data security, user profiles and access rights |
| 7. Reports | Sample layouts of the reports the system generates, plus screenshots |
| 8. Future scope | Further enhancements |
| 9. Bibliography, appendices, glossary | Sources, extra material and terms |
What does the evaluator check in your MCA project?
Short answer: Three things: the quality of your report, the technical merit (the depth of your thinking) and the project execution (how much work you put in). Section VII of the guideline lists the checkpoints below.
| Area | Checkpoints from section VII |
|---|---|
| Planning | Cost and effort estimate using function point analysis or a similar method; a PERT chart with proper stages; a valid Gantt chart |
| SRS | Follows a standard such as IEEE, or has a proper engineering structure rather than running text |
| ER diagram | Correct symbols for attributes, entities and relationships; cardinality shown; clearly linked to the SRS |
| DFD | Levelled (context, level 1, level 2) with proper inputs and outputs, and linked to the data dictionary |
| Data dictionary | Explains every entity, relationship and data flow |
| Design | Modules specified; tables normalised to at least 3NF; keys and constraints defined; flowchart, pseudocode or PDL; a consistent UI with validation; architecture explained |
| Coding | Comments describing inputs, outputs, parameters and logic; naming standards; error handling; security using views, GRANT/REVOKE, user rights and anti-hacking steps |
| Testing | Real test case designs and results for unit, integration and system testing, not definitions |
| Presentation | Sample reports, screenshots in order, proper binding, cover page and page numbers |
Formatting, cover page and binding rules
- Paper: A4, single line spacing, printed on one side only.
- Numbering: every page, table and figure is numbered, and every table and figure has a title.
- Title: exactly as in the approved synopsis, everywhere.
- CD (MCA_NEW): a CD with the executable files of the complete project, fixed to the last page of the report. Never send it separately, and keep an identical copy for the viva.
- Binding: one original copy in bound form. “A photocopy of the project report is not acceptable for submission.”
- Copies: print two. Submit one and keep the other for the viva.
Sample cover page (as in section XI)
Student’s Full Name
Enrolment No: __________
Project Guide’s Full Name
Master of Computer Applications (MCA)
Year of Submission
Maidan Garhi, New Delhi – 110068
How to submit the MCA project report
Short answer (MCA_NEW): Send one original bound report, with the CD on the last page, by registered insured post to the Regional Director of your Regional Centre, within your report window. Write “MCA PROJECT REPORT (MCSP-232)” on top of the envelope. MCAOL learners upload a single PDF on the LMS.
A report is “summarily rejected and returned” if it arrives without the original approved proforma, the synopsis, the guide’s signed bio-data, the Certificate of Originality or the CD.
MCSP-232 viva voce and passing marks
Short answer: The viva carries 50 marks and is compulsory. For MCA_NEW it is held face to face at your Regional Centre, never at the examiner’s home or workplace, and you are told by letter. For MCAOL it is held online and you are told by e-mail. If you submit the report but miss the viva, your project stays incomplete.
What happens in the viva
- Questions on your project and on related MCA courses
- A live demo of the software
- Writing part of the code for a problem, to show you can code
Our viva preparation list
These are the questions students most often need to be ready for. They are our advice, not an official list.
- Why did you pick this problem, and who will use the system?
- Walk me through your ER diagram. Why is this relationship one-to-many?
- Show the level 1 DFD and trace one process to the tables.
- Normalise this table to 3NF in front of me.
- Why this language and database? What would you change?
- Show one unit test case and one system test case with results.
- How did you secure logins and the database?
- Write a query or function for this small task.
- What would you add next (future scope)?
Carry the report copy and the identical CD (or the executables, for MCAOL). Make sure the demo runs offline on a laptop.
Failed the project or missed your slot?
Missed the report window
- An approval is valid for one year (two slots).
- Submit in the next report window.
- Miss that too, and you need a fresh synopsis approval.
Failed the project
- “Re-do” the whole cycle, starting with a new proposal. A new topic is advised.
- There are no special slots; use the normal calendar.
- Pay a pro-rata fee by demand draft. The 2026 edition says to ask your RC for the amount; the 2024 edition printed ₹2,500. MCAOL pays online.
Can two students do one MCA project? Project trainee letter
Short answer: Normally one student per project. Two are allowed only if the project needs at least one person-year of work (six person-months each), and only with prior recommendation from the MCA Project Coordinator, SOCIS. Each student submits their own proposal and report covering different modules. Only the introduction and conclusion may be similar.
Project trainee letter: To do your project in a company, use the “Project Trainee Letter” in section IX of the guideline and get it attested by the Project Coordinator or your Regional Director.
Why IGNOU MCA projects get rejected
- Incomplete proforma or missing signatures and dates
- Guide not eligible, already guiding 5 students, or bio-data and ID proof missing
- No software development (a study, theory or network-setup project)
- Barred software: MS Access, FoxPro, dBase, VB with Access, or C/C++ for a management system
- Sent outside the slot, or to SOCIS instead of your Regional Centre
- Thin analysis: no Gantt or PERT, unlevelled DFDs, or no keys and constraints
- Evaluator’s suggestions ignored in the revised proposal or final report
- Title changed between the synopsis and the report, or the guide’s signatures don’t match
- Report missing the original proforma, certificate or CD, or a photocopy sent instead of the original
- Copied work, which is referred as an unfair-means case
IGNOU MCA project topic ideas, by category
Short answer: IGNOU publishes no list of approved topics. Choose one that fits the project categories in the guideline, is big enough for 100+ pages, and uses an allowed stack. These ideas follow those rules.
- Hostel allotment and mess billing · PHP (Laravel) + MySQL
- Clinic appointment and e-prescription · Python (Django) + PostgreSQL
- Housing society maintenance billing · ASP.NET Core + SQL Server
- Inventory and barcode billing for a shop · Java + MySQL
- Coaching centre fee and batch manager · C# .NET + SQL Server
- Bus pass booking and renewal app · Flutter + Firebase
- QR-code attendance app · Kotlin + Room + REST API
- Fake product review detection · Python, scikit-learn
- Loan default risk scoring · Python, XGBoost + Flask
- Mandi crop price dashboard and forecast · Python, Pandas + Streamlit
- Student drop-out early warning · Python + Power BI
- Number-plate recognition for parking · Python + OpenCV
- Face-recognition attendance · Python + OpenCV + MySQL
- Crop disease advisory expert system · Python rule engine
- Admission enquiry chatbot · Python (Rasa) + MySQL
- LAN chat and file transfer · Java socket programming
- Network bandwidth usage monitor · Python sockets + SQLite
A full MCA topics page with module lists is coming soon. Meanwhile, ask an expert to shortlist topics that suit you.
A 6-month work plan for MCSP-232
A realistic schedule that fits IGNOU’s slots. Start one month before your proposal slot opens.
| When | What to finish |
|---|---|
| Month 0 | Pick the topic and stack; find an eligible guide; collect their bio-data and ID copy |
| Weeks 1–3 | Write the synopsis: requirements, Gantt and PERT, DFDs, ER diagram, tables, modules |
| Inside the slot | Post the proposal (or upload it, for MCAOL) and keep a photocopy |
| While waiting (4–8 weeks) | Finalise the SRS, set up the project and build the login and master-data screens |
| After approval: weeks 1–3 | Apply the evaluator’s suggestions; complete database design and UI design |
| Weeks 4–11 | Build all modules; write the code comments as you go |
| Weeks 12–13 | Unit, integration and system testing, with test reports |
| Weeks 14–16 | Write the 100–125 page documentation, take screenshots, burn the CD, print and bind |
| Report window | Post by registered insured post (or upload); keep your copy and CD |
| Before the viva | Rehearse the demo offline; practise the viva list above |
IGNOU MCA project: frequently asked questions
What is the course code and credit value of the IGNOU MCA project?
Is the IGNOU MCA project out of 100 marks?
When can I submit my IGNOU MCA project proposal?
How many pages should the IGNOU MCA synopsis be?
How many pages should the IGNOU MCA project report be?
Can I submit the IGNOU MCA project online?
Does IGNOU allot a guide for the MCA project?
Who approves my MCA synopsis, my guide or IGNOU?
Can I use C or C++ for my IGNOU MCA project?
Is PHP with MySQL allowed for MCSP-232?
Do I have to do the project in a real company?
Can I repeat my BCA project topic?
Can two students do one IGNOU MCA project?
How long is an approved MCA project proposal valid?
What happens if I fail the MCA project?
Is the MCA project viva online or offline?
Does IGNOU Buddy write my project for me?
What is the last date to submit the IGNOU MCA project for December 2026?
How do I submit the IGNOU MCA project online?
How do I pay the IGNOU project fee?
How can I check my IGNOU MCA project status?
Can I download a sample IGNOU MCA project report?
What should be on the front page of an IGNOU project?
Sources (opened 10 November 2026)
- MCSP-232 Project Guidelines, MCA_NEW, July 2026 & January 2027 (eGyanKosh): the main source for this page
- MCSP-232 Project Guidelines, MCA_NEW, July 2024 & January 2025 (PDF): used for the edition comparison
- MCSP-232 Project Guidelines, MCAOL, July 2024 & January 2025 (PDF): the online MCA route
- IGNOU MCA_NEW programme page: course structure and credits
- IGNOU online project-report submission notice, June 2026 cycle
- IGNOU OPMS: Project Submission Guidelines, TEE December 2026
- IGNOU announcement: Project/Internship/Practical course fee, TEE December 2026 (last date 30 Nov 2026)
- IGNOU ISMS: Assignment/Project/Practical marks status
How to submit your MCA project for December 2026
Short answer: Pay the project fee in your Samarth login, then upload your report as one PDF on IGNOU’s OPMS portal by 30 November 2026, 11:59 PM. IGNOU says no further extension will be given.
- Check you are eligibleYour registration must be valid and not time-barred. If you already passed the project, don’t resubmit; if you failed, you may resubmit.
- Pay the fee on Samarth by 30 November 2026The upload link in OPMS appears only after the fee is paid in your IGNOU Samarth Portal login.
- Arrange the report in IGNOU’s orderWhere applicable: the approved original proposal proforma, synopsis, guide’s bio-data, and the Certificate of Originality signed and dated by you and your guide.
- Scan it as one PDF per coursePages clear, not blurred, in the right order, with the same orientation throughout.
- Upload on OPMS with your Samarth loginSeparate uploads: guide’s signed bio-data (max 5 MB), approval of the synopsis (max 5 MB), synopsis (max 10 MB), and the complete report with declarations (max 40 MB).
- Keep your recordsSave the fee receipt and every uploaded file. Don’t post a hard copy after uploading. Reports sent by e-mail aren’t accepted.
What the first page must show (OPMS)
- Title of the project report
- Your name
- Programme code
- Enrolment number as on your ID card (not the control number)
- Regional Centre code
- Course code(s)
The MCSP-232 guideline describes posting one bound copy with a CD to your Regional Director in the report window (MCAOL: LMS). For December 2026, IGNOU’s OPMS notice asks for online upload and says not to send a hard copy after submitting. If your Regional Centre has given a different written instruction for your programme, follow your Regional Centre.
Queries: project-related, projects@ignou.ac.in; technical upload problems, preexamcs@ignou.ac.in or your Regional Centre. IGNOU opens a new submission window every June and December cycle, and we update this section each cycle.
How to check your MCA project status and result
Short answer: Open IGNOU’s Assignment/Project/Practical status page, enter your enrolment number and programme code, and submit. A status shows only after marks have been sent on by the evaluating centre; the final result appears on your grade card.
- Status not showing yet? That is normal until evaluation is complete and marks are sent on.
- Viva: Held face to face at your Regional Centre (MCA_NEW) or online (MCAOL); your RC tells you the date.
- Marks not updated after the result? Write to projects@ignou.ac.in with your enrolment number, programme code, course code and submission details (OPMS screenshot or PR number).
- Synopsis approval status: your Regional Centre (or the office you sent it to) sends the approval letter. Ask them if nothing arrives within the stated time.
हिंदी में: IGNOU MCA प्रोजेक्ट कैसे बनाएं और जमा करें
- कोड MCSP-232 (12 क्रेडिट, चौथा सेमेस्टर)।
- सिनॉप्सिस 15–18 पेज; 1 अप्रैल–30 जून या 1 अक्टूबर–31 दिसंबर में भेजें।
- रिपोर्ट 100–125 पेज (कोड के अलावा); वाइवा 50 अंक का है।
- पास होने के लिए रिपोर्ट और वाइवा दोनों में 40% चाहिए।
- दिसंबर 2026: फीस Samarth पर और रिपोर्ट OPMS पर 30 नवंबर 2026 तक।
Get expert guidance for your MCA project
Short answer: Tell us your programme and where you’re stuck. An IGNOU Buddy project expert first understands your requirement and stage, then guides you from topic selection to viva.
Where are you right now? Tap to message an expert on WhatsApp:
- Share your programme, code and stage
- Talk to an expert, who understands what you need
- Get guidance and feedback at each step until you submit
✓ You write and submit your own work, as IGNOU requires. We don’t sell ready-made reports or promise approval.
IGNOU Buddy Team. IGNOU Buddy is an independent study-help website for IGNOU students. We check every rule on this page against IGNOU’s official guidelines and update it each exam cycle.
Related guides
IGNOU Buddy is an independent study-help website. It is not affiliated with or endorsed by Indira Gandhi National Open University (IGNOU). We quote IGNOU’s published guidelines and link to them; rules, fees and dates can change, so always check the current guideline and your Regional Centre’s notices before you submit.