IGNOU MCA Project: What the MCSP 232 Project Asks You to Build

MCSP 232 before the shelf

The IGNOU MCA project is MCSP 232, a 12-credit fourth-semester course of MCA_NEW in which you develop working software, send a synopsis for approval, then submit a documented report with a CD and face a compulsory viva. The report carries 150 marks and the viva 50, each with its own 40 percent minimum.

The IGNOU MCA project is the largest single course in MCA_NEW: the July 2026 Common Prospectus lists 80 credits for the programme, and MCSP 232 Project alone takes 12 of them in Semester IV, beside MCS 230 (Digital Image Processing and Computer Vision) and MCS 231 (Mobile Computing). The SOCIS guidelines for July 2026 and January 2027 allow you to send the proposal once you have entered the third semester, so the work really starts a semester before the course appears on your registration.

The guidelines rule out three kinds of work in so many words: physical installations, LAN or WAN configuration, and theoretical projects or system studies that involve no software development. Everything on this page follows from that one condition. The proposal must describe software you can build, the report must document how you built it, and the viva may ask you to run it and write code in front of the examiner.

MCA students who reach our desk most often say the topic is where they stall: nobody taught them how an MCSP-232 synopsis is put together, and the guidelines list what to include without showing a finished example.

Open any part of the MCSP 232 route (tap here)

Reference Synopses and Reports for the IGNOU MCA Project, by Stage

This category holds IGNOU MCA project reference material for MCSP 232: sample synopses and sample project reports, laid out to the structure of the current SOCIS guidelines. What a student needs from a sample changes with the stage, so start from the step you are on.

MCA reference sets by the step you are on

Your stepWhat to study in a reference setWhere
Third semester, no topic yetHow a project category, tool stack and module list hang together in one synopsisSample synopses in this category
Synopsis drafted, not postedLevelled DFDs, an ER diagram with cardinality, a table design with keys, a Gantt and a PERT chartSample synopses in this category
Approved, software being builtHow SRS, design, coding standards, test reports and security chapters are documentedSample project reports in this category
Theory courses still openMCS course help books and solved assignmentsButtons below

After the approval letter arrives, many MCA students tell us they have no picture of what a finished MCSP-232 report looks like. Seeing an SRS, a 3NF schema and a set of unit test reports laid out in one volume answers that faster than the section headings do.

Ask Which MCSP 232 Set Fits Your Stage

All IGNOU Project Soft CopiesIGNOU MCA BooksIGNOU MCA Solved Assignments

December 2026: The Guidelines Say Post It, OPMS Says Upload It

For the December 2026 term-end cycle, two IGNOU documents give an IGNOU MCA project student two different routes for the final report. The MCSP-232 guidelines (July 2026 and January 2027) say one bound original goes to the Regional Director of your Regional Centre by registered insured post, with the CD fixed inside. IGNOU’s OPMS guidelines for TEE December 2026 say project reports are uploaded through the Online Project Management System with your Samarth login by 30 November 2026, and that no hard copy is to be sent to SED or the Regional Centre after submission. The OPMS text names no programme and no exclusion, so it does not tell an MCA student that MCSP-232 is outside it.

Guideline route against the December 2026 upload route

Built from the MCSP-232 guidelines (July 2026 and January 2027) and IGNOU’s OPMS guidelines for TEE December 2026, both read in November 2026.

PointMCSP-232 guidelinesOPMS, TEE December 2026
Where the report goesOne bound original to the Regional Director, registered insured postSingle scanned PDF of the original, uploaded in OPMS
When1 July to 30 September, after approval in the April to June slotBy 30 November 2026, 11:59 PM; no extension
Hard copyRequired; a photocopy is not acceptedNot to be sent to SED or the Regional Centre after submission
CD of executablesFixed on the last page; never sent separatelyNo upload slot for it
FeeNot stated, except a pro-rata fee for failed studentsPaid in Samarth first; the upload link opens only after it shows
EmailNot a route at allReports sent by email are not considered
VivaFace to face at the Regional Centre, on a letter from the Regional DirectorWhere applicable, under the Regional Centre

The reading that loses nothing: if your bound MCSP-232 report already went to the Regional Director in the July to September slot, keep the postal receipt and ask the Regional Centre in writing whether an OPMS upload is still expected. News coverage of the OPMS launch said hard copies already received need not be uploaded again; the OPMS text itself does not say so. If you have not submitted yet and are sitting the December 2026 examination, pay the project fee in Samarth, upload the scanned report with the approved proforma, synopsis and guide bio-data in their separate slots, and still carry the report and the identical CD to the viva.

Students regularly ask us whether a date in a notice is for the synopsis or for the report. The 30 November 2026 OPMS date is a report date; it does nothing for an MCA proposal, which still follows the October to December slot in the MCSP-232 calendar.

A belief we keep meeting is that IGNOU will push every last date back by a month, so starting late feels safe. The OPMS notice for December 2026 says there will be no extension, and an MCA_NEW student who waits on that hope has nothing to fall back on.

Some students simply email their report to the Regional Centre. Neither route open to an MCA project student accepts that: the MCSP-232 guidelines want a bound copy by registered insured post, and OPMS says emailed reports will not be considered.

IGNOU MCA Project Submission Last Date: Two Slots In, Two Slots Out

The IGNOU MCA project submission last date depends on which slot your proposal used. MCSP-232 runs on fixed windows twice a year, set out in Section I of the guidelines, and there are no separate slots for students repeating a failed project.

MCSP-232 windows, proposal to viva
StageCycle ACycle B
Proposal with guide bio-data, to the Regional Director1 April to 30 June1 October to 31 December
Approval, as printed in the calendar30 days after receipt30 days after receipt
Bound report, one copy, to the Regional Director1 July to 30 September1 January to 31 March
Viva-voceNovember or JanuaryMay or July

An approved proposal is valid for one year, which the guidelines count as two slots. Miss your report window and you may submit in the next one; miss that too and a fresh synopsis approval is needed. Many pages give 31 May or 30 November as the MCA report date: those are not in the MCSP-232 calendar, and a report posted on 31 May has already missed the window that closed on 31 March. The December 2026 OPMS date of 30 November is a separate, cycle-specific instruction covered in the section above.

At our desk, 70 to 80 percent of the students in our records start moving only in the final month before a date. For an MCSP-232 proposal that means June for the slot closing on 30 June and December for the one closing on 31 December, which leaves little room if the guide wants changes.

Many MCA proposals are posted in the final week of the slot. Post the MCSP-232 packet early enough that it reaches the Regional Centre inside the slot.

We also see students leave the MCSP-232 synopsis so late that there is no time left to prepare it properly themselves. A 14 to 18 page MCA synopsis with DFDs, an ER diagram and table designs is not a weekend job.

IGNOU MCA Project Topics Seeded From Your Own MCA_NEW Courses

Good IGNOU MCA project topics come out of courses you have already studied, because the viva may test both the project and “the courses concerned”. The guidelines ask for a topic complex and large enough to justify an MCA project, ask you not to repeat your BCA topic, and list synopsis categories that line up closely with the MCA_NEW course list.

Project shapes seeded from MCA_NEW courses

A planning aid: the course list is from the July 2026 Common Prospectus and the categories from Section V of the guidelines; the pairings and project shapes are our suggestions, not IGNOU’s.

MCA_NEW courseSynopsis categoryProject shape that still counts as software development
MCS 213 Software Engineering, MCS 219 Object Oriented Analysis and Design, MCS 220 Web TechnologiesRDBMS or OOPSA web application for a real organisation’s process, with user roles, a 3NF schema and reports; no C or C++ for information management systems
MCS 224 AI and Machine Learning, MCSL 228Artificial Intelligence or Machine LearningAn application that trains on a dataset you collect, serves predictions to logged-in users and records outcomes
MCS 226 Data Science and Big Data, MCS 221 Data Warehousing and Data MiningData ScienceA system that collects, cleans and loads data into tables, then generates the reports a manager reads
MCS 227 Cloud Computing and IoT, MCS 218 Data Communication and Computer NetworksNetworkingSoftware that logs device or sensor data to a cloud back end with access rights; a network installation alone is barred
MCS 230 Digital Image Processing and Computer VisionImage ProcessingAn application that reads images, extracts data and stores it against records
MCS 231 Mobile ComputingMobile ComputingA mobile client with a server and database, documented like any other MCSP-232 system
MCS 215 Security and Cyber LawsAny categoryFeeds synopsis heading (x), security at various levels, and the report’s System Security chapter

A question we hear from MCA_NEW students is which topic from the official list they are supposed to pick. MCSP-232 prints no topic list at all; Section VIII gives software and broad application areas, and its own note calls them only suggested.

Across the IGNOU synopses we see returned, a frequent evaluator comment asks for the study to be grounded in the student’s own city or place. For MCSP-232, which prefers a real-life project in an organisation, a client near you gives the proposal that grounding.

When MCA proposals draw on the same outside source or on widely shared material, their titles often match other students’ work, and a repeated topic is a common reason for a return. A narrow problem from your own workplace is harder to duplicate.

Match a Reference Set to Your Topic and Stack

Which Software MCSP-232 Bars, and Which It Merely Suggests

Software rules decide more IGNOU MCA project returns than students expect. Section VIII bars dBase III Plus, FoxPro, Visual FoxPro and MS-Access, and bars Visual Basic as a front end with MS-Access as the back end. C and C++ must not be used for any information management system, for example a hospital, reservation, library, school or college management system. Latest versions are expected throughout.

Everything else in Section VIII is a suggestion. It names front ends such as JavaScript, ReactJS, AngularJS, Vue.js, Flutter, TypeScript, Bootstrap and HTML5; back ends such as Oracle, MySQL, SQL Server, DB2 and NoSQL databases; languages such as Python, Java and C#; and the .NET platform. Its note says tools outside the list are acceptable if they belong to current technologies. Whatever you choose goes into box 6 of the proforma and must stay the same through the synopsis and the report.

Can an AI or machine learning model be an MCA project?

A model on its own is not enough, because the project must include software development. The guidelines’ categories include artificial intelligence, expert systems, machine learning, data science and image processing; for projects outside the DBMS family, Section VII asks for class diagrams, a behaviour model or state transition diagram, and details of the data structures used, in place of the ER and DFD set.

Many proposals we read rest on secondary data alone. MCSP-232 allows it; its objectives also include fact-finding to determine requirements, and its coding section asks for the SQL or object descriptions you used to collect, clean and insert data, so plan where your data comes from.

IGNOU MCA Project Guide Eligibility, Read Line by Line

IGNOU MCA project guide eligibility has two routes in Section IV. The first is a Ph.D. or M.Tech in Computer Science with at least one year of experience. The second is a B.E or B.Tech (Computer Science), MCA or M.Sc (Computer Science) with at least two years of experience, preferably in software development. The proforma adds that the starred degrees count in Computer Science or IT only, and the guidelines repeat four times that a guide may not supervise more than five IGNOU MCA students at any time.

The guidelines make you responsible for choosing the guide: the first step listed is to select a topic and a suitable Project Guide. The guide’s role is guidance when a problem comes up; the complete work must be done by the student.

Most MCA students we meet have not read the guide criteria before choosing, and some pick a person who does not meet Section IV. Check the degree subject and the years of experience first, then ask.

Students often go to the study centre coordinator expecting a guide to be allotted for MCSP-232. The guidelines leave that choice with you, so the useful question at the study centre is whether a counsellor there meets the Section IV criteria and has fewer than five IGNOU MCA students.

When no guide is offered, some MCA students ask a relative or an acquaintance in IT without checking the criteria. A software engineer with a B.Tech in a field other than Computer Science does not meet the second route as printed, however experienced.

The Guide’s Bio-Data, Identity Proof and Signature

The IGNOU MCA project proposal must carry the guide’s bio-data with the guide’s signature and date, and the checklist printed after the proforma adds a certified copy of the guide’s proof of identity. The guidelines print no bio-data template, so build one that shows exactly what the proforma asks for: qualification with subject, and working or teaching experience. The same signature appears again on the Certificate of Originality in the final report, and Section VI says the two must match.

We have seen proposals returned when the guide’s bio-data had no stamp or working ID behind it. For MCSP-232 the printed requirement is a signed, dated bio-data plus a certified identity proof; an employer ID or letter showing the years of experience closes the remaining doubt.

A guide who asks for three or four rounds of changes can push an MCA synopsis back by weeks. With only two proposal slots a year, a delay past 30 June or 31 December costs a full six months, so agree the review dates with the guide at the start.

IGNOU MCA Project Synopsis: Thirteen Headings and What Goes Under Each

The IGNOU MCA project synopsis is the approval document, and Section V lists what it must cover. The numbering runs to (xii) but uses (ix) twice, so there are thirteen headings. The right-hand column shows the Section VII checkpoint each heading later feeds, which is why a weak synopsis turns into a weak report.

Section V headings with the checkpoint each one feeds
HeadingWhat goes under itFeeds, in the report
(i) TitleThe title you will keep word for word to the cover pageEvery page and certificate
(ii) Introduction and objectivesThe problem, the users and what the software will doIntroduction and objectives
(iii) Project categoryRDBMS, OOPS, networking, AI, expert systems, machine learning, data science, image processing, mobile computingWhich diagram set the evaluator expects
(iv) Tools and platformHardware and software requirement specificationsProforma box 6 and the SRS
(v) Problem definitionFunctional requirements and technical specifications or a literature review, plus planning and scheduling with a Gantt chart and a PERT chartCost and effort estimate, PERT decomposition, Gantt time lines
(vi) Scope of the solutionWhat the software covers and what it leaves outFuture scope chapter
(vii) Analysis0, 1 and 2 level DFDs, a complete ER diagram with cardinality, activity, class or state diagrams as neededER, DFD and data dictionary checkpoints
(viii) Database and tablesEvery table with primary and foreign keys and field constraints3NF schema and data integrity
(ix) Complete structureModules with descriptions and process logic, data structures, implementation method, list of reportsProgram structure and report layouts
(ix) Network architectureOnly if your project needs itArchitecture explanation
(x) Security mechanismsSecurity at the levels your system has: login, roles, databaseViews, grant and revoke, user access rights
(xi) Future scopeFurther enhancement you can describe honestlyFuture scope chapter
(xii) BibliographyBooks, papers and documentation you actually usedReport bibliography

Many MCA students do not know this structure and leave core parts out. For MCSP-232 the core parts are the thirteen headings above; a proposal without the analysis or the database heading leaves the evaluator little to approve.

Proposals also come back when the time frame or the structure of the work is missing. In an MCA synopsis, those sit in the Gantt and PERT charts under heading (v) and the module list under (ix); a synopsis without them gives the evaluator no plan to approve.

Returns where the reason for the study is missing are common too. For MCSP-232, the problem definition under heading (v) should say whose problem the software solves and why the current way fails.

How Long the Synopsis Should Run, and Where Its Sources Go

The IGNOU MCA project synopsis has two printed lengths: the checklist after the proforma says 14 to 18 pages, and Section V says 15 to 20. Writing 15 to 18 pages meets both. A 1,000-word synopsis, which some pages recommend, cannot hold thirteen headings, levelled DFDs and table designs. The report has its own length, about 100 to 125 pages excluding code.

Heading (v) lets you write requirement specifications or a literature review. If you take the literature route, every work you discuss should appear in the bibliography under heading (xii), and the bibliography should list nothing you did not use.

Over-long files get returned as well. For MCSP-232 the limits are printed: 14 to 20 pages for the synopsis across its two figures, and about 100 to 125 pages of documentation for the report, code excluded.

In many synopses that reach us, the works discussed in the literature review do not match the bibliography. On an MCSP-232 proposal, check each name in heading (v) against the list in heading (xii) before the guide signs.

The correction we see most often across IGNOU approvals is a request to bring the literature review up to date. An MCA proposal that takes the review route under heading (v) should cite current versions of the frameworks and papers it relies on.

The Approval Proforma for an IGNOU MCA Project

The IGNOU MCA project proforma in Section II is a single page with a header block and seven numbered boxes, signed and dated by both you and the guide, followed by a checklist of what goes with it. The note at its top says an incomplete proforma will be summarily rejected.

Seven numbered boxes and the header block
FieldWhat to enter
HeaderEnrolment number, study centre code and name, Regional Centre and RC code, email, mobile; Project Proposal No. is for office use
1 and 2Your name and address; the project title, exactly as in the synopsis
3 to 5Guide’s name and address, qualification (tick the degree; starred degrees in Computer Science or IT only), working or teaching experience
6Software used, checked against Section VIII
7Whether this is your first submission
SignaturesStudent and guide, each with a date; the lower block is for the evaluator

Some students are not sure what the proforma is and post the synopsis without it, or attach a form from another course. For MCSP-232 it is the Section II form headed Proforma for the Approval of MCA Project Proposal, and its original returns to you to be bound into the report.

Half-filled MCA proformas are a regular sight at our desk: guide details incomplete, and now and then the student’s own name, address or email left blank. The note on the MCSP-232 form says an incomplete proforma is rejected outright.

An empty title box sends a proposal back. On the MCSP-232 proforma the title also starts the chain that must stay identical through the report, so write it in full there first.

Posting the Synopsis Packet to Your Regional Director

An IGNOU MCA project proposal travels as one packet of four items: the signed proforma; the guide’s signed and dated bio-data with a certified identity proof; the synopsis; and a self-addressed envelope with postage stamps for the reply by ordinary post. It goes to the Regional Director of your Regional Centre with “MCA_NEW Project Proposal (MCSP-232)” written on top of the envelope. Section V says that under no circumstances should the proposal be sent to SOCIS in New Delhi. Keep a photocopy of the whole packet; a later resubmission needs it.

MCA students ask us whether the synopsis goes to the study centre, the Regional Centre or Maidan Garhi. For MCSP-232 the answer is printed plainly: the Regional Director of your own Regional Centre, never SOCIS.

Many students are unsure which papers travel with the synopsis and whether it needs binding. The MCSP-232 list is the four items above; the guidelines set no binding for the synopsis, only for the final report.

Students who post an MCA proposal often keep no receipt. The postal slip is your only proof that the packet reached the Regional Centre inside the slot, and the enquiry letters Section IV asks for will need it.

How Long IGNOU MCA Project Approval Takes, and When to Chase It

IGNOU MCA project approval has three printed time frames: 30 days after receipt in the calendar, four to six weeks in Section IV, and six to eight weeks in Section V. Plan for eight. Section IV says that if nothing reaches you within four to six weeks of the slot’s last date, contact your Regional Centre. Enquiries go to the Regional Director, quoting your enrolment number and Project Proposal Number.

In our experience an IGNOU synopsis approval often takes two to three months to arrive, longer than any figure printed in the MCSP-232 guidelines. Build the MCA development schedule on the later date.

Most students do not know whom to ask when a month or two passes without news. For an MCA proposal it is the Regional Director of your Regional Centre, by letter or email with the enrolment and proposal numbers.

We have seen cases where no approval letter arrived and the session ran out. For an MCSP-232 proposal, write to the Regional Director as soon as the six-week mark after the slot passes.

Approved With Suggestions, or Not Approved: What Changes Next

An approved IGNOU MCA project proposal may still carry suggestions for reformulating the project, and the note after the proforma says they must be incorporated in the final project or it may be rejected at any stage. A Not Approved proposal brings the evaluator’s suggestions; you resubmit a revised synopsis with a new proforma, a copy of the earlier synopsis and the original or a photocopy of the non-approved proforma, in the next slot only. You may also change the topic, the software or the guide and send a fresh proposal.

Approval often arrives with comments that students then forget to act on. On an MCSP-232 proforma those comments sit in the evaluator’s suggestions box, and the report must show where each one was dealt with.

Most approvals we see carry some correction or modification point. Treat an MCA approval letter with suggestions as normal, not as a near-rejection.

When an MCA proposal is resubmitted, the earlier synopsis and the non-approved proforma are often left out. MCSP-232 asks for both, which is why the photocopy of the first packet matters.

Company Projects, the Trainee Letter and Two-Student Projects

Section IV expects most students to work on a real-life IGNOU MCA project in an industry, R&D laboratory, educational institution or software company, but says it is not mandatory: you may formulate a problem with your guide instead. If an organisation wants a letter, Section IX prints a Project Trainee Letter for attestation by the Project Coordinator, Regional Director or Assistant Regional Director.

One student per project is the preferred rule. A project needing one human-year or more may be shared by at most two students, at six human-months each, only with prior recommendation from the MCA Project Coordinator, SOCIS, Block-C, Visveswarayya Bhawan, Maidan Garhi, obtained by sending both complete synopses with a handwritten application. Each student then submits a separate proposal and report on different modules and goes through every phase of the life cycle.

IGNOU MCA Project Report Format: The Documentation the Evaluator Expects

The IGNOU MCA project report format is set by Section VI: documentation of about 100 to 125 pages excluding code, printed in single line spacing on one side of A4 paper, with every page, table and figure numbered and every table and figure titled. The guidelines say each component carries weightage, that theory already in reference books should be avoided, and that the documentation must describe your own analysis, design, coding and testing.

Documentation parts in the order of Section VI
PartContents named in the guidelines
OpeningTable of contents with page numbering; introduction and objectives
System analysisIdentification of need; planning and scheduling with both PERT and Gantt charts; SRS; software engineering paradigm; data models such as DFDs, ER model, class, use-case, sequence, state or activity diagrams
System designModularisation; data integrity and constraints; database and procedural or object-oriented design; user interface design; unit and system test cases
CodingSQL or object descriptions for database creation with constraints, for data collection, cleaning and insertion, and for user access rights; complete code with comments and descriptions
Standardisation of codingCode efficiency, error handling, parameter calling and passing, validation checks
TestingTechniques and strategies, testing plan, test reports for unit and system test cases, debugging and code improvement
System securityDatabase and data security; user profiles and access rights
ClosingSample report layouts; future scope; bibliography; appendices if any; glossary

The order of the parts is a question we answer often. For MCSP-232 the table above is the order Section VI prints, and the evaluator reads the report against it.

In many reports the analysis is too thin to carry the objectives. In an MCA report the matching part is System Analysis, and Section VII judges it on whether the SRS has a proper structure and the DFDs tie to a data dictionary.

Bibliographies in many reports follow no single format and list sources the text does not use. MCSP-232 sets no citation style, so pick one consistent format and keep each entry tied to something in your MCA report.

Before You Print: Section VII as a Self-Check

Section VII says assessment of an IGNOU MCA project rests on the quality of the report, its technical merit and the work actually put in, and then names checkpoints. Most can be checked at home before the report goes to print.

Section VII checkpoints turned into a pre-print check
AreaCheck before printing
PlanningCost and effort estimated by function point analysis or a similar method; PERT stages properly decomposed; Gantt time lines valid
SRSFollows IEEE or another standard, or at least a sound structure, rather than running text
ER diagramProper symbols, cardinality shown, strong link to the SRS
DFD and data dictionaryContext, level 1 and level 2, proper inputs and outputs; dictionary explains every entity, relationship and flow
SchemaNormalised to at least 3NF; keys, alternate keys, value constraints and ranges; referential diagram explained
Design and codeFlowchart, pseudo code or PDL; consistent interface and naming; exception handling; views, grant and revoke, access rights
TestingActual test case designs, reports and results for unit, integration and system testing, not definitions
PresentationSample reports, screen layouts in order, proper binding, cover page, page numbering, clean print of text and images

Some students write their data chapters on assumed figures with no real work behind them. In MCSP-232 the examiner can ask for a live demonstration, so each test result, sample report and screenshot in the MCA report must come from software you actually ran.

The supporting material at the back is often missing. For an MCA report that means the sample report layouts and the screen dumps Section VII asks to see in proper order, and any appendix your design refers to.

What Goes Inside the Bound Report, Front Cover to CD

Section VI lists what an IGNOU MCA project report must contain besides the documentation, and paragraph 4 says a report missing any of the listed items will be summarily rejected and returned. In the order a binder would assemble them:

  1. Cover page in the Section XI pattern.
  2. The original approved proforma and the project proposal (synopsis).
  3. The guide’s bio-data with signature and date.
  4. The Certificate of Originality in the Section X format, signed by you and the guide.
  5. The project documentation, in the Section VI order.
  6. A CD of the executable files of the complete project, attached to the last page.
Cover lines: Section XI plus what OPMS adds
LineSource
MCSP – 232; [TITLE OF THE PROJECT]; by [your full name]; Enrolment No: [your enrolment number]Section XI
Under Guidance of [guide’s full name]Section XI
Submitted to the School of Computer and Information Sciences, IGNOU, in partial fulfilment of the requirements for the award of the degree Master of Computer Applications (MCA)Section XI
[Year of submission]; Indira Gandhi National Open University, Maidan Garhi, New Delhi 110068Section XI
Programme code: MCA_NEW; Regional Centre code: [your RC code]; enrolment number as on your ID cardOPMS first-page list (December 2026 uploads)

Reports come back when students do not know which documents must be bound in. For MCSP-232 the list is fixed: original approved proforma, synopsis, guide’s signed bio-data, Certificate of Originality and the CD.

An originality certificate without the guide’s signature is something we still see. On an MCA report the guide’s signature there must also match the one on the proforma, which Section VI checks.

Some reports reach the Regional Centre spiral bound. MCSP-232 asks for the report in bound form and lists proper binding among the organisation checkpoints Section VII names, so settle the binding before the MCA volume is printed.

Sending the Report: One Original to the Regional Director

Under the MCSP-232 guidelines, the IGNOU MCA project report goes as one original bound copy, with the CD enclosed on the last page, to the Regional Director of your Regional Centre by registered insured post within your report window. Write “MCA PROJECT REPORT (MCSP-232)” on top of the envelope. A photocopy is not accepted, and the CD is never sent separately. Take two print-outs: keep the second copy and an identical CD for the viva. For the December 2026 cycle, read the OPMS section near the top of this page first.

How many copies, and to whom, is one of the most frequent MCA questions we get. Under MCSP-232 it is one bound original to the Regional Director, and one identical copy with its CD kept by you.

Some students send the synopsis and the finished report together near the last date, without the guide’s signature, and the whole packet fails. MCSP-232 runs in two stages: the report is accepted only with the original approved proforma bound in, after approval in an earlier slot.

The registered insured post receipt is the piece of paper students most often lose. Keep it with your MCA retained copy until the result is out; it is your proof that the report reached the Regional Director inside the window.

IGNOU MCA Project Viva: Demo, Live Code and the 40 Percent Rule

The IGNOU MCA project viva is compulsory and carries 50 of the 200 marks. The guidelines set a minimum of 40 percent in the report and in the viva, counted separately, so a strong report cannot carry a weak viva.

How the 200 MCSP-232 marks split
ComponentMaximumMinimum in this component
Project report15060
Viva-voce5020

The Regional Director informs you by letter, and the viva is held face to face at the Regional Centre, never at the examiner’s workplace or residence. The examiner may ask about the project and the courses concerned, ask for a demonstration of the software, and ask you to write portions of code for a problem. Carry your retained copy of the report and the identical CD. If you submit the report but miss the viva, the project remains incomplete until you contact the Regional Centre. Printed viva months are November or January, and May or July; actual dates are set by each Regional Centre, and RC Bangalore, for example, scheduled MCA vivas for the December 2025 examination on 7 March 2026.

Students across IGNOU courses ask whether a viva applies to them. For MCSP-232 there is no doubt: the viva is compulsory, and without it the MCA project stays incomplete.

Rs 500 Evaluation Fee, and the Pro-Rata Fee After a Fail

The IGNOU MCA project evaluation fee comes from the July 2026 Common Prospectus, not from the guidelines. For admissions from the January 2023 cycle onwards, it sets Rs 300 for project work up to 4 credits and Rs 500 above 4 credits, paid with the term-end examination form and neither refundable nor adjustable. MCSP-232 is 12 credits, so the Rs 500 rate applies. For the December 2026 cycle, IGNOU’s fee notice set 30 November 2026 for paying project fees in Samarth, and the OPMS upload link opens only after the fee shows there.

A student who fails the project repeats the whole cycle from a fresh proposal, preferably on a new topic, within the normal calendar, and pays a pro-rata fee by demand draft in favour of IGNOU payable at the city of the Regional Centre. The July 2026 edition prints no amount, so ask your Regional Centre for the figure.

The Rs 300 and Rs 500 amounts confuse many students we speak to. At 12 credits MCSP-232 falls in the upper slab, so an MCA_NEW student pays Rs 500.

Seven Places the MCSP 232 Project Guidelines Disagree With Themselves

The MCSP 232 project guidelines for July 2026 and January 2027 contradict themselves in seven places. Each one is harmless if you follow the stricter reading, which satisfies every version at once. Two of them, the approval time and the synopsis length, also appear in the July 2024 and January 2025 edition.

Seven internal disagreements and the reading that satisfies both
PointOne place saysAnother saysSafe reading
Approval timeCalendar: 30 days after receiptSection IV: four to six weeks; Section V: six to eight weeksPlan for eight weeks; chase after six
Synopsis lengthChecklist after the proforma: 14 to 18 pagesSection V: 15 to 20 pages15 to 18 pages
Synopsis headingsNumbered (i) to (xii)(ix) used twice, so thirteen headingsCover all thirteen
Guide’s degree subjectSection IV: Computer ScienceProforma: Computer Science or ITComputer Science is safe; ask the RC in writing before relying on IT
Guide’s identity proofChecklist: attach a certified copySection V’s contents list omits itAttach it
Certificate of OriginalitySection VI: format on page 23The file ends at page 21; the format is Section X on page 20Use Section X
Who receives the reportSection XI cover: submitted to SOCISSections I and VI: post to the Regional DirectorKeep the cover wording; post to the Regional Director

IGNOU MCAOL Project and Other Computer Applications Codes

The IGNOU MCAOL project uses the same course code, MCSP-232, but the online programme has its own guidelines (the July 2024 and January 2025 edition is on IGNOU’s assignments site). They keep the two slots, the 150 plus 50 marks and the five-student limit per guide, and move the route online: the proposal goes through a link on the Learning Management System, approval is printed as about 30 days in the calendar and four to six weeks in the communication section, the report is submitted as a soft copy, and the guide’s bio-data travels with a self-attested copy of the guide’s degree certificate and identity proof. The MCAOL coordinator’s email in those guidelines is mcaolsocis@ignou.ac.in.

Computer applications project codes compared
ProgrammeProject codeRoute
MCA_NEW (distance)MCSP-232, 12 credits, Semester IVProposal and bound report by post to the Regional Director; viva face to face
MCAOL (online)MCSP-232, 12 credits, last semesterProposal through the LMS link; report as a soft copy
MCA (old programme)MCSP-060Its own older guidelines; do not mix them with MCSP-232

MCAOL learners will find their help books in the IGNOU MCAOL books category. BCA students have a separate project course with its own guidelines; their study material is in the IGNOU BCA books category.

Using a Sample Without Copying It

A reference IGNOU MCA project shows how the parts fit together; it cannot be submitted as yours. MCSP-232 makes copying easy to catch: you and your guide sign a Certificate of Originality, the Project Coordinator’s message says a copied report will go to the Exam Discipline Committee as an unfair means case, and the examiner can ask you to run the software and write code on the spot. Use a sample to see the shape of an SRS or a test report, then document the software you built.

Many students draft their synopsis with an AI chatbot before reading the guidelines, and the plan that comes out does not match what MCSP-232 asks for in its thirteen headings and its software rules.

An AI-generated MCA synopsis or report handed in unchanged is another reason the same titles keep repeating, and some students do exactly that. A viva in which the examiner can ask for a demonstration and for code written on the spot leaves such an MCA report exposed.

Material pulled from the internet often goes into an MCA report unchecked for plagiarism. Run your own check on the text and rewrite borrowed theory; Section VI already asks you to avoid book theory and describe your own project.

Questions MCA Students Bring to Our Desk

Is the IGNOU MCA project out of 100 marks?

No. Several pages still say 100, but the MCSP-232 guidelines give 150 marks for the report and 50 for the viva, 200 in all, with 40 percent needed in each part.

Where can I download the MCSP-232 project guidelines PDF?

The July 2026 and January 2027 edition is on eGyanKosh, and older editions sit on the MCA_NEW assignments page of webservices.ignou.ac.in; both links are in the sources list below. Check the edition label on the cover before following any date.

Must the bound report have a particular cover colour?

The guidelines set no colour, font size or margin. They ask for bound form, single line spacing on one side of A4, numbered pages, tables and figures, and titled tables and figures.

Can I reuse my BCA project topic?

No. The Project Coordinator’s message asks students not to repeat the topic undertaken at BCA level, and says the topic should be complex and large enough to justify an MCA project.

Does the Project Trainee Letter mean I must work in a company?

No. Section IV says a real-life project is preferred but not mandatory; the letter exists for students whose organisation asks for one.

Your First Fortnight on the IGNOU MCA Project

Fourteen days, from course list to posted packet

  1. Days 1 to 3: list two problems from your workplace or town that software could solve, and match each to an MCA_NEW course from the topics table.
  2. Days 4 and 5: check the stack against Section VIII and drop anything barred.
  3. Days 6 and 7: confirm a guide meets Section IV, has fewer than five IGNOU MCA students, and will sign bio-data with an identity proof.
  4. Days 8 to 12: draft the thirteen headings, the DFDs, ER diagram, tables, modules and charts; keep it to 15 to 18 pages.
  5. Days 13 and 14: fill the proforma, get both signatures, photocopy everything, and post the packet to your Regional Director inside the slot.

If you would rather have your own approved title worked through one to one, our customised project service handles that on a separate site. Questions about the reference material on this page go to 9354637830.

Tell Us Your MCSP 232 Stage

Whatever material you use, the IGNOU MCA project is passed on software you built, documented and can defend in the viva.

Official Documents Behind This MCA Page

By BK Sahni, founder of Shri Chakradhar Publication Pvt. Ltd., New Delhi, which has served IGNOU distance learners since 2010 with its own writing team and printing press. Last updated:

Prepared from the MCSP-232 project guidelines for July 2026 and January 2027, IGNOU’s OPMS guidelines for TEE December 2026 and the July 2026 Common Prospectus, read in November 2026; the drafting was AI-assisted, every rule was checked against the official sources listed above, the desk observations come from BK Sahni’s own work with IGNOU students, and BK Sahni publishes this page under his editorial responsibility.

shrichakradhar.com is an independent publisher of IGNOU reference material and is not affiliated with, authorised by or endorsed by Indira Gandhi National Open University. Sample synopses and reports are study reference, not for submission as your own work. Questions about your enrolment, approval or result go to your Regional Centre.

No products were found matching your selection.
Shopping cart0
There are no products in the cart!
Continue shopping
0