MCSP 232, the short versionThe IGNOU MCA Project is MCSP 232, a 12-credit semester IV course of the MCA_NEW programme in which you build working software and document it. Send the proposal after entering semester III, between 1 April and 30 June or 1 October and 31 December, to your Regional Director. Once it is approved, the bound report of about 100 to 125 pages (code excluded) goes in by 30 September or 31 March. The report carries 150 marks and the viva 50, with 40 percent needed in each.
- 12credits, the semester IV project
- 150 + 50marks for the report and the viva
- 40%needed in each part, separately
- 100 to 125pages of documentation, roughly, code excluded
- 5IGNOU MCA students per guide at most
- 3editions of the guidelines still in circulation
What the July 2026 MCSP 232 guidelines settle
- For MCA_NEW, the proposal and the report both go by post to the Regional Director of your Regional Centre. Section V says the proposal must not be sent to SOCIS in New Delhi under any circumstances, and sections I and VI name the Regional Director, not the Student Evaluation Division, for the report.
- One document prints three approval times and two synopsis lengths: 30 days (p. 4), four to six weeks (p. 9) and six to eight weeks (p. 11); 14 to 18 pages (p. 6) and 15 to 20 pages (p. 10). Plan for the longer wait and write 15 to 18 pages, which meets both ranges.
- The project is not marked out of 100. The report is evaluated for 150 marks and the viva for 50, and you must score 40 percent in each separately (section VII).
- There is no 31 May or 30 November deadline for MCA. Your report window follows your approval slot: 1 July to 30 September, or 1 January to 31 March (section I).
- MS-Access, FoxPro, Visual FoxPro, dBase III Plus and a Visual Basic plus MS-Access combination are barred outright, and C or C++ is barred for any information management system (section VIII).
- The copy linked from IGNOU’s own MCA_NEW assignments page is the July 2024 and January 2025 edition, which still prints the old Rs 2,500 pro-rata fee. The July 2026 edition is the one this page follows; check the cover of yours before relying on any rule.
IGNOU MCA Project Basics: MCSP 232 Is 12 Credits of Software You Build
Every IGNOU MCA Project is registered as MCSP-232, the project course of the two-year Master of Computer Applications (programme code MCA_NEW) run by the School of Computer and Information Sciences (SOCIS). It is worth 12 credits in semester IV of an 80-credit programme made of 15 theory courses, 6 lab courses and this one project, according to the MCA_NEW Programme Guide (July 2025). You may send the proposal once you enter semester III. IGNOU’s own files and Regional Centre notices write the code three ways, MCSP-232, MCSP 232 and MCSP232, and all three mean the same course.
The rule that decides most topics comes first in the guidelines: “the project work should compulsorily include the software development.” Physical installations, configuring a LAN or WAN, theoretical projects and studies of existing systems with no software development are not allowed. A real-life project in an industry, research laboratory, educational institution or software company is preferred, though it is not compulsory, and you may frame a problem with your guide instead. Do not repeat the topic you did at BCA level.
Semester IV lists four counselling sessions, eight hours in all, for discussion on the project (Programme Guide, July 2025). They are the sessions the Programme Guide sets aside for project discussion.
Heard at our MCA desk
MCA students often tell us that IGNOU gave them no class on how to write a synopsis or a project report, and that choosing the topic is where they feel most lost. Ask your Learner Support Centre when those four project sessions run, and take both questions there.
Many students are also unsure about the project fee and mix up the Rs 300 and Rs 500 amounts. MCSP-232 is a 12-credit project, so the Rs 500 slab for projects above 4 credits applies, paid with the Term-End Examination form (Common Prospectus, July 2026, p. 27).
| Programme | Project course | Status |
|---|---|---|
| MCA_NEW (two-year MCA, distance mode) | MCSP-232, 12 credits | Current; this page |
| MCAOL (MCA online) | MCSP-232, 12 credits, separate MCAOL guidelines | Current; differences in the next section |
| Older three-year MCA | MCSP-060 | Legacy; RC Bangalore’s list for the viva-voce held on 7 March 2026 still covers MCSP60 beside MCSP232 |
| BCA_NEW | BCSP-165 | A different project; see our BCA project page |
| M.Sc. (Data Science and Analytics) | MCSP-079 | A different programme; see our MSCDSA project page |
| M.Sc. (Artificial Intelligence and Machine Learning) | MCSP-090 | A different programme; see our MSCAIML project page |
Codes for every other programme are listed in our IGNOU project course codes table.
Same Code, Two Routes: MCA_NEW by Post, MCAOL on the LMS
An IGNOU MCA_NEW project and an MCAOL project share the code MCSP-232, the same synopsis contents (MCA_NEW prints them under twelve numerals, MCAOL numbers them i to xiii) and the 150 plus 50 marking, yet they travel by different routes. MCA_NEW papers go by post to your Regional Director; MCAOL learners upload everything on the Learning Management System. Check the programme code on your ID card before you follow any IGNOU MCA project instruction, this page included.
MCA_NEW (distance mode)
- Proposal and guide bio-data posted to the Regional Director of your Regional Centre.
- Certified copy of the guide’s identity proof; a self-addressed envelope with stamps.
- Synopsis 14 to 18 pages (p. 6) or 15 to 20 pages (p. 10).
- One original bound report with a CD of the executables fixed to the last page, by registered insured post.
- Viva face to face at the Regional Centre.
MCAOL (online)
- Proposal uploaded “through LMS only”.
- Guide’s self-attested degree certificate and identity proof.
- Synopsis 15 to 20 pages; bibliography in IEEE, APA or MLA style.
- Report uploaded as a single PDF on the LMS; no CD, but keep the executables for the viva.
- Viva online, intimated by e-mail from your Nodal Regional Centre.
| Point | MCA_NEW (July 2026 edition) | MCAOL (July 2024 edition) |
|---|---|---|
| Approval notice | 30 days, four to six weeks, or six to eight weeks, in three places | Approx. 30 days in the calendar; four to six weeks by e-mail or LMS; about 5 to 6 weeks in another place |
| Two students on one project | Prior recommendation from the MCA Project Coordinator, SOCIS, with a handwritten application | Prior recommendation by e-mail to mcaolsocis@ignou.ac.in |
| Pro-rata fee after failing | Demand draft in favour of IGNOU; ask your Regional Centre for the amount | Paid online “as per University norms” |
| Project Trainee Letter | Attested by the Project Coordinator, Regional Director or Assistant Regional Director | Attested by the Project Coordinator or the Regional Director of the nodal RC |
| Same in both | 12 credits; the same two proposal slots and report windows; 150 plus 50 marks with 40 percent in each; the same guide criteria and five-student limit; the same barred software; approval valid for one year (two slots); 100 to 125 pages of documentation | |
Wrong desk, wrong channel
Some MCA_NEW students are unsure whether the synopsis goes to the Study Centre or the Regional Centre, and a few carry it to Maidan Garhi themselves; that packet is rejected. Section V settles it: the Regional Director of your Regional Centre, and never SOCIS in New Delhi.
Some students e-mail the finished report. Neither route accepts that: MCA_NEW asks for registered insured post to the Regional Director, and MCAOL for a single PDF uploaded on the LMS.
Many students think the synopsis and the report go together on one last date, and some send both without the guide’s signature. MCSP-232 runs in two stages with separate windows, and a report can only follow an approved proposal.
Documents You Need and Where Each Lives
Two kinds of files support an IGNOU MCA Project, and they should never be confused: IGNOU’s own documents, and the study reference files we publish to help you read them. Only the first kind carries rules.
| Kind | Document | Issuer and edition | Where to get it |
|---|---|---|---|
| IGNOU DOCUMENT | MCSP-232 Project Guidelines (MCA_NEW), with the proforma (p. 5), the enclosure list (p. 6), the Project Trainee Letter (p. 19), the Certificate of Originality (p. 20) and the sample cover (p. 21) | SOCIS, July 2026 and January 2027 | eGyanKosh, MCSP-232 guidelines |
| IGNOU DOCUMENT | MCSP-232 Project Guidelines (MCA_NEW), previous edition, still the copy linked from IGNOU’s MCA_NEW assignments page | SOCIS, July 2024 and January 2025; superseded, use only to compare | 2024 edition PDF |
| IGNOU DOCUMENT | MCSP-232 Project Guidelines for MCAOL (online learners) | SOCIS, July 2024 and January 2025 (latest MCAOL edition found in October 2026) | MCAOL guidelines PDF; check the LMS for a newer copy |
| IGNOU DOCUMENT | MCA_NEW Programme Guide (structure, counselling, contacts) | SOCIS, July 2025 | Programme Guide PDF |
| IGNOU DOCUMENT | Common Prospectus (fees, project evaluation fee) | IGNOU, July 2026 | Prospectus PDF |
| STUDY REFERENCE | Sample synopsis: a calibration and preventive maintenance tracker, all twelve components, watermarked | Ignouproject.com, October 2026, not for submission | Download the sample synopsis (PDF) |
| STUDY REFERENCE | Project report format template: binding order, chapter shells, test and access tables, no results | Ignouproject.com, October 2026, not for submission | Download the report format (PDF) |
The sample synopsis shows the depth an evaluator looks for; it is not a synopsis you may submit. The guidelines forward copied work to the Exam Discipline Committee as an unfair means case, so choose your own topic and write every line yourself.
The proforma mix-up
Many students are not sure what the proforma is. Some forget to attach it; others attach one from another programme or from an older edition. The MCSP-232 proforma is on p. 5 of the same guidelines PDF, and in the July 2026 edition its header has separate Study Centre Code and Study Centre Name lines.
Stuck on a box or a slot? Send your MCSP-232 question on WhatsApp to +91 93546 37830, and say whether you are on MCA_NEW or MCAOL.
Chat on WhatsAppTwo Slots In, Two Slots Out: The MCSP 232 Calendar
An IGNOU MCA Project moves on two proposal slots a year, and each slot is paired with one report window and one viva period, as section I of the guidelines sets out.
| Proposal submitted at the Regional Centre | Report window after approval | Viva period printed |
|---|---|---|
| 1 April to 30 June | 1 July to 30 September | November or January |
| 1 October to 31 December | 1 January to 31 March | May or July |
- Approval time. The guidelines print three figures. If no letter reaches you within four to six weeks after the last date of the slot, contact your Regional Centre (p. 9).
- Validity: an approved proposal is valid for one year, that is two slots. Miss both report windows and you need a fresh synopsis approval (section V, point 3).
- Not approved: resubmit only in the next slot, so a proposal not approved in April to June goes back in October to December (p. 9).
- Failed students follow the same calendar; there are no separate slots for them.
Real viva dates can fall outside the printed months. RC Bangalore’s list for the MCSP60 and MCSP232 viva-voce held on 7 March 2026 falls in a month the calendar does not print, so watch your own Regional Centre’s notices.
When the slot is closing
In our records, 70 to 80 percent of students become active only in the last month before a submission date. For MCSP-232 that last month is June or December for a proposal and September or March for a report.
Students often ask whether a published last date is for the synopsis or the report. Here they are different dates: 30 June and 31 December close the proposal slots, while 30 September and 31 March close the report windows.
Many synopses are posted in the final week of a slot. The slot dates are dates for submission at the Regional Centre, so leave time for the envelope to arrive.
Who Can Guide an IGNOU MCA Project
An IGNOU MCA Project guide must meet one of two routes in section IV of the guidelines, and the asterisk on box 4 of the proforma limits the starred degrees to Computer Science or IT.
| Guide’s degree | Minimum experience | Note |
|---|---|---|
| Ph.D. or M.Tech. in Computer Science | 1 year | Route 1 |
| B.E. or B.Tech. (Computer Science), MCA, or M.Sc. (Computer Science) | 2 years | Route 2; preferably in software development |
| Any other degree or discipline | Not eligible | Choose another guide before you fill the proforma |
At any time a guide may supervise no more than five IGNOU MCA students, so if your guide already has five, you would be the sixth and the proposal falls outside the rule. The guide advises; the complete project work “should be done by the student only” (p. 9). If you work in a company, the Project Trainee Letter asks for a guide “preferably from the same organization”. Guide rules for other programmes are compared on our IGNOU project guide eligibility page.
Guide bio-data checklist
The guidelines ask for a bio-data signed and dated by the guide, with a certified copy of the guide’s identity proof (p. 6). The other lines are what we look for, so that section IV can be confirmed from the bio-data itself.
- Signed and dated by the guide.
- Degree and discipline that match the box ticked on the proforma.
- Years of working or teaching experience, enough for the degree held.
- MCA_NEW: a certified copy of the guide’s identity proof. MCAOL: a self-attested degree certificate and identity proof.
- The number of IGNOU MCA students the guide supervises now (our suggestion, so the five-student limit can be confirmed).
- The same signature you will need later on the Certificate of Originality.
Guides, from our side of the table
Most students we meet do not know the section IV criteria, and some pick a guide who does not meet them. Check the degree, the discipline and the years before anyone signs.
Many tell us IGNOU did not allot a guide, so they approached a relative or a contact at work. That person can guide you only if section IV is met, so run the same check on them as on anyone else.
We have seen synopses come back when the guide’s bio-data had no stamp or working ID. The MCSP-232 guidelines ask for a bio-data signed and dated by the guide with a certified copy of the guide’s identity proof; they print no stamp rule, so put your effort into that certified copy.
MCA Project Topics the Guidelines Accept, Stacks They Reject
IGNOU publishes no list of MCA project topics. What the guidelines ask of an IGNOU MCA Project topic is that it be “complex and large enough to justify as a MCA project”, and the synopsis names its category: RDBMS, OOPS, networking, artificial intelligence, expert systems, machine learning, data science, image processing, mobile computing or another. Since the July 2026 edition the software list in section VIII is titled “Suggested Software”, and note (iv) says the list is only suggested.
| Barred | Rule |
|---|---|
| dBase III Plus, FoxPro, Visual FoxPro, MS-Access | Old packages may not be used (note i) |
| Visual Basic front end with MS-Access back end | Combination barred (note i) |
| C or C++ for an information management system | Barred for hospital, reservation, library, school, college and similar management systems (note ii) |
| Old software versions | “latest versions of the software are to be used” (notes i and iii) |
| No software development | Physical installation, LAN or WAN configuration, theoretical study or a study of a system is not a project |
Built from section VIII of the July 2026 MCSP-232 guidelines.
Allowed stacks from the list include Python, Java, C#, PHP, JavaScript frameworks such as ReactJS, AngularJS and Vue.js, Flutter and ASP.Net, with back ends such as MySQL, Oracle, SQL Server, DB2 and NoSQL databases. Tools outside the list are allowed if they are part of the latest technologies (note iii).
| Course you studied | Direction (not a title) | Category | What makes it MCA-sized |
|---|---|---|---|
| MCS-220 Web Technologies (Spring Boot, Hibernate, Spring Security) | A role-based approval workflow for a real office process you can observe | RDBMS, web | Several roles, state changes, role-based login, audit trail |
| MCS-221 Data Warehousing and Data Mining | A small data mart with OLAP reports for an organisation that shares its anonymised data | Data Science | ETL, star schema, a mining step, a report layer |
| MCS-224 Artificial Intelligence and Machine Learning | A classifier inside a working application, for example routing incoming requests | Machine Learning | Data preparation, model, evaluation, and the application that uses it |
| MCS-226 Data Science and Big Data | A pipeline and dashboard on public open data with a scheduled refresh | Data Science | Ingestion, cleaning, storage, a visual layer, tests |
| MCS-227 Cloud Computing and IoT | A sensor monitoring system with a cloud back end and alerts | Networking, IoT | Device data, storage, a rules engine, dashboard, security |
| MCS-230 Digital Image Processing and Computer Vision | An image quality or document check built into an upload workflow | Image Processing | The processing step plus the system around it |
| MCS-231 Mobile Computing | An offline-first field data app that syncs to a server | Mobile Computing | Local storage, sync conflicts, a server API, access rights |
Our suggestions, not an IGNOU list: course titles are from the MCA_NEW Programme Guide (July 2025); turn a direction into your own title with your guide.
Keep that title unchanged from the proforma to the last page of the report. Choosing well across programmes is covered in our guide to choosing an IGNOU project topic.
Topic talks with MCA_NEW students
Many students believe they must pick a title printed in the guidelines, word for word. MCSP-232 prints no titles at all: section VIII lists software and broad application areas, and note (iv) calls even that list a suggestion.
Topics taken from widely shared material, or from the same outside source, often arrive with the same title as other students’ work, and duplicate topics are a common reason for return.
Evaluators’ comments on returned synopses often ask that the work be based on the student’s own city or location. A system for an office, clinic or business near you answers that comment before it is written.
IGNOU MCA Project Synopsis: Twelve Components, 15 to 18 Pages
An IGNOU MCA synopsis is one of the four enclosures of the project proposal, and it must cover every item listed in section V. The evaluator reads it together with the proforma and the guide’s bio-data, so each component needs content about your system, not definitions from a textbook.
| Item | Component | What to show for your system |
|---|---|---|
| i | Title of the project | The exact title you will keep on the proforma, report and certificate |
| ii | Introduction and objectives | The present system, its problems, and objectives that each map to a requirement |
| iii | Project category | RDBMS, OOPS, networking, AI, expert system, ML, data science, image processing, mobile computing or another |
| iv | Tools, platform, hardware and software specifications | Languages, frameworks, database and versions; development and deployment hardware |
| v | Problem definition, requirement specifications or literature review, planning and scheduling | Functional and technical requirements with IDs; a Gantt chart and a PERT chart |
| vi | Scope of the solution | What is in and what is out |
| vii | Analysis | DFDs at levels 0, 1 and 2; a complete ER diagram with cardinality; activity, class or state diagrams as your design needs |
| viii | Database and tables | Every table with primary keys, foreign keys and field constraints |
| ix | Complete structure | Number of modules with description and process logic, data structures, implementation methodology, reports to be generated |
| ix (second) | Overall network architecture | If your project needs one; the guidelines number this item ix a second time |
| x | Security mechanisms at various levels | Application, database and network measures |
| xi and xii | Future scope; bibliography | Enhancements that follow from your limits; sources you actually read |
The two printed lengths overlap at 15 to 18 pages, and a synopsis of that size meets both. MCAOL learners write 15 to 20. General synopsis guidance for all programmes is on our IGNOU synopsis page.
This tool needs JavaScript. If the button does not respond, refresh the page or open it in Chrome.
MCSP-232 Proposal Readiness Checker
Built line by line from the MCSP-232 guidelines (MCA_NEW edition of July 2026, MCAOL edition of July 2024), read in October 2026.
It lists gaps and your dates. It cannot tell you whether an evaluator will approve the proposal.
Rules the checker applies. Every rule comes from the MCSP-232 guidelines. Guide: at least 1 year of experience with a Ph.D. (or M.Tech.); at least 2 years with a B.E., B.Tech., MCA or M.Sc. (Computer Science); any other degree fails; five students already under the guide fails (p. 5 note and section V, point 9). Project: anything without software development fails; MS-Access, FoxPro, dBase, and Visual Basic with MS-Access fail; C or C++ for a management system fails (section VIII); a repeated BCA topic fails (p. 3). Length for MCA_NEW: 15 to 18 pages meets both printed ranges, 14 or 19 to 20 meets only one, anything else fails; for MCAOL the range is 15 to 20. Every missing component or enclosure is listed. Dates: April to June maps to a report window of 1 July to 30 September and a viva in November or January; October to December maps to 1 January to 31 March and a viva in May or July; the second report window inside the one-year validity is also shown (sections I and V). A date outside both slots is reported with the next slot.
Synopses that reach us with gaps
Many students do not know the synopsis structure and leave out core parts. For MCSP-232 the core parts are the twelve items in the table above; tick each one off before the guide signs.
Many synopses are drafted with ChatGPT or another AI tool before anyone has read the MCSP-232 guidelines, so the plan misses what this course asks for: a Gantt and PERT plan, levelled DFDs, tables with keys and a security section.
Some synopses and reports run far past the length the guidelines set and come back for that reason. For MCA_NEW keep the synopsis inside 14 to 18 or 15 to 20 pages and the documentation near 100 to 125 pages, code excluded.
Before It Is Posted: Have Your MCSP-232 Synopsis or Report Checked
What we often find first
Many students leave the synopsis so late that there is no time left to write the missing parts properly themselves.
In many synopses the literature review cites work that never appears in the bibliography, or the bibliography lists sources the review never uses. Items v and xii of section V have to agree.
The guidelines reject an incomplete proforma “summarily”, return a report without the original approved proforma, synopsis, signed bio-data, Certificate of Originality or CD, and allow rejection “at any stage” for any violation. Most of these are paper faults that surface only after a slot is lost. Send us the IGNOU MCA Project synopsis or report you wrote, and we check it line by line against the July 2026 MCSP-232 guidelines and return it with corrections marked.
In your synopsis packet we look for
- All twelve section V components, in order, written about your system
- DFD levels 0, 1 and 2, ER cardinality, tables with keys and constraints
- Gantt and PERT charts that agree with each other
- Barred software, C or C++ in a management system, software development present
- Guide degree, experience and the five-student limit as the bio-data shows them
- Every proforma box, both signatures and dates, the page count and the envelope details
In your bound report we look for
- Original approved proforma, synopsis, bio-data, certificate and CD in place
- One title throughout; the evaluator’s suggestions carried out
- SRS structure, data dictionary, normalisation to 3NF, integrity rules
- Your own test cases and test reports, debugging notes, security measures
- Writing about your project in place of textbook theory
- Page, table and figure numbering, titles and binding order
Synopsis correction Rs 1,000; project report correction Rs 2,000, as listed on our services and charges page in October 2026. You remain the author of your project, your guide signs only what they have supervised, and approval is decided by IGNOU’s evaluator.
The MCSP 232 Proforma, Box by Box
The proforma for an IGNOU MCA Project proposal is on p. 5 of the guidelines, under a printed warning that an incomplete proforma “in any respect will be summarily rejected”. The July 2026 edition splits the old single Study Centre line into a code and a name.
| Box | Filled by | What to watch |
|---|---|---|
| Project Proposal No. | Office | Leave blank; quote it later in every letter |
| Enrolment No. | Student | Your current enrolment number |
| Study Centre Code | Student | New separate line in the July 2026 edition |
| Study Centre Name | Student | New separate line in the July 2026 edition |
| Regional Centre | Student | The centre the proposal is posted to |
| RC Code | Student | The code of that same centre |
| Student | An address you will check for the approval letter | |
| Mobile No. | Student | A number you will answer |
| 1 Name and address of the student | Student | The address where the stamped envelope can reach you |
| 2 Title of the project | Student | Final wording; it must stay identical through the report |
| 3 Name and address of the guide | Student | The same as on the bio-data |
| 4 Educational qualification of the guide | Student, from the bio-data | Tick Ph.D., M.Tech., B.E. or B.Tech., MCA or M.Sc.; starred degrees count only in Computer Science or IT; attach the bio-data |
| 5 Working or teaching experience of the guide | Student, from the bio-data | At least 1 year (Ph.D., M.Tech.) or 2 years (others); the five-student limit is printed under this box |
| 6 Software used in the project | Student | Nothing barred by section VIII; latest versions |
| 7 Is this your first submission? | Student | “No” means you attach the earlier synopsis and the Not Approved proforma |
| Signature of the student, with date | Student | Dated |
| Signature of the guide, with date | Guide | This signature must match the one on the Certificate of Originality later |
| Approved box | Evaluator | Leave blank |
| Not Approved box | Evaluator | Leave blank |
| Name of the Project Proposal Evaluator | Evaluator | Leave blank |
| Signature, designation and stamp; date | Evaluator | Leave blank |
| Suggestions for reformulating the project | Evaluator | If approved, carry them into the report; if not, into the next proposal |
Proformas we send back
Many proformas reach us half filled: the guide’s details incomplete, and now and then the student’s own name, address or e-mail left blank. Every box on p. 5 except the office boxes is yours to fill.
Synopses are returned when box 2, the title, is left empty. Write the final wording there, because the same title has to run through the report and the Certificate of Originality.
Posting the Proposal: Four Enclosures, One Envelope, Never SOCIS
An IGNOU MCA Project proposal leaves home as one packet, and p. 6 of the guidelines lists what goes in it:
- The proforma, filled in every box and signed and dated by you and your guide.
- The guide’s bio-data with signature and date, and a certified copy of the guide’s identity proof.
- The synopsis.
- A self-addressed envelope with postage stamps, for ordinary post.
Write “MCA_NEW Project Proposal (MCSP-232)” on top of the envelope and post it to the Regional Director of your Regional Centre. Keep a photocopy of the whole packet, which the guidelines ask you to retain. MCAOL learners upload the same package on the LMS, with the guide’s self-attested degree certificate and identity proof, and send nothing by post.
At the envelope stage
Many students do not know which documents travel with the synopsis, or whether it should be bound or filed. The four enclosures above are the full list, and the MCSP-232 guidelines do not say how the synopsis itself is to be bound.
Many students forget to keep proof of posting. Keep the postal receipt with your photocopy of the packet; it records the date the proposal left you.
Some students send a handwritten synopsis. The guidelines say nothing about the synopsis on this point, but the report “should normally be printed” on A4, so we suggest preparing the synopsis the same way. Our note on handwritten or typed IGNOU projects covers the question for all programmes.
The Approval Letter: 30 Days, Six Weeks or Eight
Once an IGNOU MCA Project proposal is posted, the waiting time depends on which page of the guidelines you read: 30 days on p. 4, four to six weeks on p. 9 and six to eight weeks on p. 11. The evaluated proforma comes back marked Approved or Not Approved, with any suggestions for reformulating the project, and the office fills in the Project Proposal number at the top.
In every letter about your project, quote your enrolment number, Project Proposal number and Project Report number, and address it to the Regional Director of your Regional Centre (p. 10). MCAOL approvals arrive by e-mail or on the LMS.
While students wait for the letter
Most students do not know whom to contact when a month or two passes without news. For MCSP-232 it is the Regional Director of your own Regional Centre; SOCIS is not the office for approval enquiries.
In our experience the approval letter for an IGNOU MCA Project synopsis takes two to three months to arrive, well beyond the 30 days in the calendar. Plan your report window on the longer figure.
Most approvals we see arrive with correction or modification points attached.
Cost and Effort: Function Points for the Report and the Plan
Section VII says project planning should include cost estimation and scheduling, and that “the cost and efforts estimation is to be done with the help of functional point analysis or other similar methods”. That line sits among the analysis checkpoints the evaluator applies to the report; section V does not list it as a synopsis item, though a synopsis whose Gantt and PERT plan already rests on an estimate is easier to defend. It is also the easiest part of an IGNOU MCA Project report to copy from a textbook example. The estimator below builds the count from your own list of inputs, outputs, inquiries and files, so you can defend every number at the viva.
This tool needs JavaScript. If the count boxes do not appear or the button does not respond, refresh the page or open it in Chrome.
MCSP-232 Function Point and Effort Estimator
An estimate, not an IGNOU calculation: section VII lists function point analysis or a similar method among the analysis checkpoints for the report and sets no weights, hours or rates.
The weights are the standard IFPUG ones; the hours and the rate you enter are your own assumptions, to be justified in your report.
The arithmetic behind the estimate. Unadjusted function points (UFP) are each count multiplied by its IFPUG weight: external input 3, 4, 6; external output 4, 5, 7; external inquiry 3, 4, 6; internal logical file 7, 10, 15; external interface file 5, 7, 10 (simple, average, complex; IFPUG Counting Practices Manual 4.0 weights). The 14 characteristics are added to give the total degree of influence (0 to 70). Value adjustment factor = 0.65 + 0.01 x total, so it lies between 0.65 and 1.35. Adjusted function points = UFP x value adjustment factor. Effort in hours = adjusted function points x your hours per function point; person-months = effort / your hours per month; cost = effort x your hourly rate. IFPUG has treated the adjustment factor as optional since manual release 4.3, so report both the unadjusted and the adjusted count.
Planning slips we see
When a guide asks for several rounds of changes, a synopsis can slip by weeks. Put those rounds into your Gantt chart as tasks of their own, so the schedule you show the evaluator is one you can keep.
IGNOU MCA Project Report Format: 100 to 125 Pages, Code Excluded
The IGNOU MCA project report documentation “may be about 100 to 125 pages (excluding coding)”, printed with single line spacing on one side of A4 paper, with every page, table and figure numbered and every table and figure titled (section VI). The guidelines set no font or margin. They also warn against generic writing: theory available in reference books “should be avoided as far as possible”.
| Chapter | Contents required | Evaluator’s checkpoints |
|---|---|---|
| Introduction and objectives | The need and the objectives | A real problem in your setting |
| System analysis | Identification of need; PERT and Gantt; SRS; software engineering paradigm; data models | Function point or similar estimate; PERT decomposition; Gantt validity; SRS to IEEE or another standard, not running text; ER with cardinality linked to the SRS; levelled DFDs (context, level 1, level 2); data dictionary |
| System design | Modularisation; data integrity and constraints; database and procedural or object-oriented design; user interface; unit and system test cases | Tables in at least 3NF; referential and entity integrity with keys, alternate keys and value ranges; flowchart, pseudo code or PDL; consistent interface and naming; validation checks |
| Coding | SQL or object descriptions for creation with constraints, for data collection, cleaning, generation and insertion, and for access rights; complete code with comments | Comments giving inputs, outputs, calls, parameters, variables, data types and logic |
| Standardisation of coding | Code efficiency; error handling; parameter passing; validation checks | Naming conventions, nesting depth, exception handling |
| Testing | Techniques and strategies; test plan; test reports for unit and system test cases; debugging and code improvement | Your own test designs and results for unit, integration and system testing, not definitions |
| System security | Database and data security; user profiles and access rights | Views, GRANT and REVOKE, access rights, steps against hacking |
| Reports and screens | Sample report layouts; screen layouts in order | Placed for ready reference |
| Future scope, bibliography, appendices, glossary | Enhancements; sources; extra material; terms | Organisation, page numbering, print quality |
The free MCSP-232 report format template (PDF) gives an empty shell for each chapter, from the SRS outline and data dictionary to the test report and access rights tables. It holds no results, because results can only come from the software you build and test.
After approval, in the report
Approval often arrives with comments that must be worked into the report, and many students skip them. Note iii on p. 6 is blunt: suggestions not carried into the final project can lead to rejection at any stage of evaluation.
After approval many students tell us they do not know which format the report should follow. Section VI is the format: the chapter list above, on A4, one side, single spaced, with every page, table and figure numbered.
In many reports the bibliography follows no fixed style and does not match the sources cited in the text. MCA_NEW sets no style, so choose one and use it throughout; MCAOL learners are asked for IEEE, APA or MLA.
Your Code, Your Tests: Where MCSP 232 Draws the Originality Line
Every IGNOU MCA Project is judged on work the student did. The guidelines say the complete project work “should be done by the student only” (p. 9), that a student found not involved in any phase, for example coding, may have the project rejected at any stage (p. 14), and that copied work goes to the Exam Discipline Committee as an unfair means case (pp. 3 and 17). Your guide then signs a Certificate of Originality stating that the report is your authentic and original work.
That makes three things yours alone: the code on the CD, the test reports in the testing chapter, and the data your system collects, cleans or generates. A test report should come from a run of your own build, with the inputs you used and the output you saw.
Where originality breaks
Some students submit an AI-written synopsis or report as it stands, which is one reason the same topics keep reappearing. A report that does not describe your own code and your own test runs leaves you with nothing to say when the examiner asks you to explain it.
Many students paste material from internet sources and submit it without checking it for plagiarism. Check every borrowed paragraph before binding, and cite it or rewrite it in your own words.
Some students write results on assumed data instead of data they actually collected or generated. Section VI asks you to show how data was collected, cleaned, generated and inserted, and invented figures cannot meet that requirement or the certificate you sign.
Binding, CD and Envelope: Posting the Report
For MCA_NEW, an IGNOU MCA Project report received without the approved proforma in original, the synopsis, the guide’s signed bio-data, the Certificate of Originality and the CD “will be summarily rejected and returned to the student for compliance” (section VI). Bind the copy in the order section VI lists those items:
- A cover page laid out as the sample on p. 21.
- The original approved proforma and the approved project proposal.
- The guide’s bio-data, signed and dated.
- The Certificate of Originality, signed and dated by you and your guide. Section VI says its format is “on Page 23”; in the July 2026 edition it is on p. 20.
- The project documentation, with a table of contents and page numbers.
- A CD with the executable files, fixed to the last page and never sent separately.
Send only one original bound copy to the Regional Director by registered insured post, inside your report window, with “MCA PROJECT REPORT (MCSP-232)” written on top of the envelope. A photocopy is not accepted for submission. MCAOL learners upload one PDF of the full report on the LMS. Two students may share a project only when it needs one human-year or more, with the Project Coordinator’s prior recommendation and separate reports on different modules.
In bound MCA reports
Many reports reach us without one of the five items section VI demands, and any one missing sends the report back.
Many students are unsure of the page order. Follow the list above, behind a cover laid out as the sample, with the CD on the last page.
Some reports arrive without the guide’s signature on the Certificate of Originality. It must be there, and it must match the signature on the proforma.
MCSP 232 Viva and Marks: 150 Plus 50, Pass Each Separately
The IGNOU MCA Project report is evaluated for 150 marks and the MCSP 232 viva for 50. To pass you need 40 percent in each component separately, which means at least 60 of 150 and at least 20 of 50. If you submit the report and miss the viva, the project remains incomplete, and the guidelines tell you to contact your Regional Centre.
For MCA_NEW the Regional Director intimates the viva by letter; it is held face to face at the Regional Centre, never at the examiner’s workplace or residence. MCAOL vivas are held online after an e-mail from the Nodal Regional Centre. Besides questions on the project and your courses, you may be asked to run a demo and to write code for a problem on the spot.
| Chapter | Be ready to explain |
|---|---|
| Analysis | How you counted function points; your critical path; one requirement traced to its test |
| Design | Why each table is in 3NF; one foreign key and what it protects; your ER cardinalities |
| Coding | One function line by line; how errors are handled; how a user’s rights are enforced |
| Testing | A defect you found, its cause and the fix |
| Demo | The full flow of your main use case, run from the CD or your executables |
A preparation list from our desk, built on the viva description in section VII; IGNOU sets no question list.
Common viva questions for all programmes are on our IGNOU project viva questions page, and your MCA results are explained on the IGNOU MCA grade card page.
The week of the viva
Many students ask whether a viva applies to them. For MCSP-232 it always does: the viva is compulsory and carries 50 of the 200 marks.
Many are unsure how many copies to make. Send one original bound copy, and keep one photocopy and an identical CD to carry to the viva.
Some students skip the receipt when they post the report. Keep the registered insured post receipt with that photocopy.
Which Edition You Hold: What the July 2026 MCSP 232 Project Guidelines Changed
Three editions of the MCSP 232 project guidelines are still online, and IGNOU’s own MCA_NEW assignments page links the July 2024 and January 2025 one. Five details inside the document, and the place the file is posted, tell you which one you have.
| Check | July 2022 and January 2023 | July 2024 and January 2025 | July 2026 and January 2027 |
|---|---|---|---|
| Pro-rata fee for a failed project | Rs 2,500 by demand draft | Rs 2,500 by demand draft | No amount printed; “get in touch with concerned RC for the pro-rata fee” |
| Proforma header | One Study Centre line | One Study Centre line | Separate Study Centre Code and Study Centre Name |
| Section VIII | “Software and broad areas of application”, notes (i) to (iii) | The same | “Suggested Software”; new note (iv): the list is only suggested |
| Project Coordinator | Not named | Not named | Prof. P. V. Suresh |
| Normalisation | “minimum 3NF”, with reasons for any denormalisation | The same | “at least 3NF” |
| Where it is posted | IGNOU webservices, 2022 folder | IGNOU webservices, 2024 and 2025 folders; linked from the MCA_NEW assignments page | eGyanKosh |
Built from the three editions themselves, read in October 2026.
The page counts, the 150 plus 50 marks, the three approval times and the barred software read the same in all three editions, and the slots and guide criteria are unchanged between 2024 and 2026.
Not Approved or Failed: The Way Back
Proposal not approved. The evaluator’s suggestions for an IGNOU MCA Project come back with the proforma. Revise the synopsis, fill a new proforma, add the guide’s bio-data with signature, attach a copy of the earlier synopsis and the original or a photocopy of the Not Approved proforma, and send them in the next slot (pp. 9 and 11). You may also change the topic, software or guide and send a fresh proposal instead. Related questions are answered on our page about changing an IGNOU project topic after approval.
Project failed. You redo the whole life cycle from a new proposal, with a new topic advised, in the normal slots. A pro-rata fee is paid by demand draft in favour of IGNOU, payable at the city of your Regional Centre, along with the resubmitted report; the July 2026 edition no longer prints the old Rs 2,500 figure, so ask your Regional Centre for the current amount.
After a Not Approved letter
When asked to resubmit, many students forget to attach the earlier synopsis. Pages 9 and 11 want these together in the next slot: the revised synopsis with a new proforma, the guide’s signed bio-data, a copy of the earlier synopsis, and the Not Approved proforma.
The correction we see most often is in the review of literature, where students are asked to bring it up to date. If item v of your synopsis carries a literature review, date-check every source before it goes back.
We have seen cases where no approval letter reached the student and the session ran out. An approved proposal is valid for one year, two slots, so if nothing has arrived by the time the first report window opens, write to your Regional Director at once.
MCSP 232 Questions Students Ask
Can the IGNOU MCA project be submitted online?
For MCA_NEW, no: the July 2026 guidelines ask for a posted proposal and one bound report sent by registered insured post to the Regional Director. MCAOL learners upload both on the LMS. Follow an online link for MCA_NEW only if your Regional Centre issues a written notice for it.
Is the IGNOU MCA_NEW project the same as the MCAOL project?
Same code, the same synopsis contents (numbered i to xiii in the MCAOL guidelines), the same 150 plus 50 marks and the same slots. The route differs: MCA_NEW goes by post to the Regional Director with a CD, and MCAOL is uploaded on the LMS, with an online viva.
Is MCSP 232 out of 100 marks?
No. The report is evaluated for 150 marks and the viva for 50, and you must secure 40 percent in each separately.
How many pages is an IGNOU MCA synopsis?
The MCA_NEW guidelines print 14 to 18 pages on p. 6 and 15 to 20 pages on p. 10, so 15 to 18 pages meets both. MCAOL learners write 15 to 20 pages.
Who approves my MCA synopsis, my guide or IGNOU?
A Project Proposal Evaluator marks the proforma Approved or Not Approved. Your guide signs the proforma and guides the work but does not approve it, and the MCSP-232 guidelines name no list of approved guides: the guide only has to meet section IV.
Does IGNOU allot a guide for MCSP-232?
The guidelines describe no allotment: the steps on p. 9 begin with “Select a topic and a suitable Project Guide”, which is the student’s step.
Students often tell us they asked the Study Centre coordinator for a guide and none was allotted. For MCSP-232 that is expected, so look for an eligible person yourself and check them against section IV.
Will IGNOU extend the MCSP 232 slot?
The guidelines print fixed slots and say nothing about extensions.
Many students assume every last date will be pushed back by a month, so they wait for the second date before starting. We cannot predict extensions; plan on the printed slot and treat any extension as spare time.
Can I make an MCA project in C or C++?
Not for an information management system such as a hospital, reservation, library, school or college management system; section VIII bars it there. The rule names only that kind of project, so system or network programming in C or C++ is outside the bar, provided the project includes software development and uses current tools.
Is PHP with MySQL allowed for MCSP-232?
Yes. Both appear in section VIII. Use current versions; the barred items are MS-Access, FoxPro, Visual FoxPro, dBase III Plus and Visual Basic with MS-Access.
Do I need a project in a real company?
It is preferred, not mandatory. You may frame a problem with your guide. If you need to do the project in an organisation or software company, the Project Trainee Letter on p. 19, attested by the Project Coordinator, Regional Director or Assistant Regional Director, asks that organisation to take you on for it (p. 11, point 8).
Can two students submit one MCA project?
Preferably not. At most two may share a project that needs one human-year or more, only with the MCA Project Coordinator’s prior recommendation, and each submits a separate proposal and report on different modules.
Can I spiral-bind the report?
The guidelines ask for the report “in the bound form” and name no binding style.
Some students send the report spiral bound. Choose a binding that holds every page firmly and keeps the CD fixed to the last page, which is what the guidelines do spell out.
How long is my approval valid?
One year, that is two slots. If no report is submitted in either window, a fresh synopsis approval is needed for the IGNOU MCA Project.
Before You Post Your IGNOU MCA Project: A Last Look
Read these lines against your own packet the day before it goes into the envelope. All but the last match a rejection or return clause in the guidelines, so a miss on one of them can stop an IGNOU MCA Project at that stage; the last is your own record.
- The title is word for word the same on the proforma, the synopsis, the report cover and the Certificate of Originality.
- The guide meets section IV and supervises fewer than five other IGNOU MCA students.
- No barred package or combination appears anywhere, and the software versions are current.
- The proposal is going in its slot, or the report in the window its approval allows.
- Every evaluator suggestion is visibly carried out in the report.
- Test reports come from your own runs, and the CD on the last page holds the same build you will demo.
- You keep a photocopy, an identical CD and the postal receipt.
After the viva, follow your report and result with the steps in our IGNOU project status guide. All project pages across programmes are listed on our IGNOU projects hub, and the SOCIS information security project has its own MSCIS project page.
Documents Behind This Page
Every rule on this IGNOU MCA Project page comes from the documents below, read on 17 October 2026.
- MCSP-232 Project Guidelines, MCA_NEW, July 2026 and January 2027, SOCIS, IGNOU (eGyanKosh). All MCA_NEW rules on this page.
- MCSP-232 Project Guidelines, MCA_NEW, July 2024 and January 2025, SOCIS. Used for the edition comparison.
- MCSP-232 Project Guidelines, MCA_NEW, July 2022 and January 2023, SOCIS. Used for the edition comparison.
- IGNOU MCA_NEW assignments page, labelled January 2025, which links the 2024 edition.
- MCSP-232 Project Guidelines, MCAOL, July 2024 and January 2025, SOCIS. The online route.
- Programme Guide, MCA (MCA_NEW), July 2025, SOCIS. Programme structure, course titles and project counselling sessions.
- IGNOU Common Prospectus, July 2026. The project evaluation fee (p. 27).
- IGNOU RC Bangalore, list for the MCSP60 and MCSP232 project viva-voce held on 7 March 2026.
ignouproject.com is an independent service and is not affiliated with or endorsed by IGNOU. Rules, fees and dates are taken from the documents named on this page as of October 2026; confirm anything time-sensitive with your Regional Centre. Study reference files on this page are for learning the format and must not be submitted 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.
