What Is the IGNOU MCA Project (MCSP-232), and Why Plan It Backwards From the Viva?
The IGNOU MCA project is MCSP-232, a 12-credit course in the fourth semester of MCA_NEW. You must build working software; a system study, a network installation or a theoretical project is not accepted. The project report carries 150 marks and a compulsory face-to-face viva carries 50, and each part must be passed separately with 40 percent.
Every document you prepare for MCSP-232 feeds that viva. The examiner may ask for a demonstration of your software, ask you to write code on the spot, and check the CD you carry against the one bound into your report. So plan backwards: decide what software you can build and defend, then the report that documents it, then the synopsis an evaluator can approve. The synopsis goes, once you have entered the third semester, to the Regional Director of your own Regional Centre. This page follows that order and quotes the July 2026 and January 2027 MCSP-232 guidelines throughout.
On this page:
- MCA project report format and the CD
- Marks, viva, fee and what happens if you fail
- Sample MCA project reports and synopses
- Submission dates for synopsis, report and viva
- Where the guidelines contradict themselves
- Synopsis format, proforma and guide
- Topics and software allowed
- MCAOL, old MCA and other SOCIS project codes
IGNOU MCA Project Report Format: What the 100 to 125 Pages and the CD Must Contain
The MCSP-232 project documentation runs to 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. It is bound with the original approved proforma and proposal, the guide’s signed bio-data, the Certificate of Originality and a CD of executables.
The guidelines are blunt about content: the documentation must describe how you did the analysis, design, coding and testing of your project, and theory that is already available in reference books should be avoided as far as possible. Each component carries weightage in evaluation, so a missing Gantt chart or test report is a direct loss of marks. The table below lists the components in the order the MCSP-232 guidelines give them, which is the table of contents an evaluator expects. No font size or margin is prescribed; pick a readable, consistent setting.
| Report part | What the MCSP-232 guidelines ask for |
|---|---|
| Opening | Table of contents with page numbering; introduction and objectives |
| System analysis | Identification of need; project planning and scheduling with both a PERT chart and a Gantt chart; software requirement specification (SRS); the software engineering paradigm applied; data models such as DFDs, ER model, class, use-case, sequence, state or activity diagrams as your project needs |
| System design | Modularisation details; data integrity and constraints; database design and procedural or object-oriented design; user interface design; unit and system test cases |
| Coding | SQL commands or object descriptions for creating the database with constraints, for collecting, cleaning and inserting data, and for user access rights; complete project code with comments and descriptions of code segments |
| Standardisation of coding | Code efficiency, error handling, parameter calling and passing, validation checks |
| Testing | Testing techniques and strategies, the testing plan, test reports for unit and system test cases, debugging and code improvement |
| System security | Database and data security; creation of user profiles and access rights |
| Closing | Sample report layouts; future scope and further enhancement; bibliography; appendices if any; glossary |
What must the IGNOU MCA project front page show?
Section XI of the MCSP-232 guidelines prints the sample cover page. It carries the University name, the course code MCSP-232, the title of the project, your full name and enrolment number, the words “Under Guidance of” with your guide’s full name, a line stating that the report is 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), the year of submission, and the IGNOU address at Maidan Garhi, New Delhi 110068. The title on this cover, on the certificate and on every page must match the approved synopsis word for word; the guidelines state that rule twice.
Where do I send the IGNOU MCA project report?
One original copy of the MCSP-232 report, in bound form with the CD fixed to its last page, goes to the Regional Director of your Regional Centre by registered insured post within your report slot. Write “MCA PROJECT REPORT (MCSP-232)” on top of the envelope. A photocopy is not accepted for submission, and the CD must never be sent separately. Print two copies: you keep one, with an identical CD, and you carry both to the viva. A report that arrives without the original approved proforma, the synopsis, the guide’s signed bio-data, the Certificate of Originality or the CD is summarily rejected and returned. Pages that send the MCA report to the Registrar (SED) are describing other IGNOU project courses, not MCSP-232.
How Is the MCSP-232 Project Marked, and What Happens at the Viva?
MCSP-232 is marked out of 200: 150 for the project report and 50 for the viva-voce. You must secure 40 percent in each component separately, which means at least 60 of 150 and at least 20 of 50. A strong report cannot rescue a weak viva, and missing the viva leaves the project incomplete.
According to the guidelines, assessment rests on three things: the quality of the report, the technical merit of the project, meaning the depth of intellectual effort, and project execution, meaning how much work you actually put in. Section VII then names specific checkpoints. Most of them are things a student can verify before posting the report, which is why we reproduce them as a checklist rather than as general advice. Several sites still describe this course as a 100-mark project; that figure does not appear anywhere in the MCSP-232 guidelines.
| Area | Checkpoint named in the MCSP-232 guidelines |
|---|---|
| Planning | Cost and effort estimated with function point analysis or a similar method; PERT chart with proper decomposition of stages; Gantt chart with valid time lines |
| SRS | Follows IEEE or another international standard, or at least a sound structure, rather than running text |
| ER diagram | Proper symbols for entities, attributes and relationships, cardinality shown, and a clear link back to the SRS |
| DFD | Levelled as context, level 1 and level 2, with proper inputs and outputs, tied to a data dictionary that explains every entity, relationship and data flow |
| Database | Tables normalised to at least 3NF; keys, alternate keys, value constraints and ranges defined; referential diagram explained |
| Design and code | Procedural design by flowchart, pseudo code or PDL; consistent interface and naming; exception handling; database security through views, grant and revoke, and user access rights |
| Testing | Actual test case designs, reports and results for unit, integration and system testing, not definitions |
What does the examiner ask in the MCA project viva?
The MCSP-232 viva is held face to face at your Regional Centre, never at the examiner’s workplace or residence, and you are informed by a letter from the Regional Director. The guidelines say the examiner may ask about the areas of your project and the courses concerned, may ask you to demonstrate the software, and may ask you to write portions of code for a problem to show your coding ability. Bring your retained copy of the report and the identical CD. In practice this means you should be able to explain every table in your schema, every level of your DFD and every test case in your report, because the viva is where a report that is not your own work becomes visible.
What is the project evaluation fee for MCSP-232?
The July 2026 Common Prospectus sets the project evaluation fee, for students admitted from the January 2023 admission cycle, at Rs 300 for project work up to 4 credits and Rs 500 for project work above 4 credits. MCSP-232 is 12 credits, so the Rs 500 band applies. The fee is submitted with the Term-End Examination form through the SED portal and is neither refundable nor adjustable. This is a separate charge from the pro-rata fee described below for students who fail the project.
What if the MCA synopsis is not approved, or the project fails?
If the proposal is not approved, the evaluator’s suggestions are sent to you. You resubmit a revised synopsis with a new proforma, a copy of the earlier synopsis and the non-approved proforma, and you may do so only in the next slot; you may also change the topic, the software or the guide and submit a fresh proposal. If the project itself fails, you repeat the whole cycle from a new proposal, preferably on a new topic, within the normal calendar, and pay a pro-rata fee by demand draft in favour of IGNOU payable at your Regional Centre’s city. The July 2026 edition prints no amount for that fee; the earlier July 2024 and January 2025 edition printed Rs 2,500. Confirm the current figure with your Regional Centre.
Sample IGNOU MCA Project Reports and Synopses: How to Use One Safely
This category holds MCSP-232 reference material for IGNOU MCA students: sample synopses and sample project reports in PDF, prepared to the structure of the current guidelines. Use a sample to see how an SRS, a levelled DFD, a normalised schema and a set of test reports fit together inside one project, then build and document your own software.
A sample cannot be submitted as your project, and MCSP-232 makes that easy to detect: you and your guide sign a Certificate of Originality, copied reports go to the Exam Discipline Committee as unfair means cases, and the examiner can ask for a live demonstration and code written on the spot. So choose a reference set for what it teaches. Check that it is for MCSP-232, not the old MCSP-060, and that its category and stack resemble yours. These reference sets come from Shri Chakradhar Publication Pvt. Ltd., a Delhi publisher that has served IGNOU distance learners since 2010 with its own writing team and printing press.
Ask for MCSP-232 Sample Topics
All IGNOU Project Soft CopiesIGNOU MCA Help BooksIGNOU MCA Solved Assignments
IGNOU MCA Project Submission Dates: The Two Slots for Synopsis, Report and Viva
MCSP-232 runs on two fixed slots a year. Send the synopsis between 1 April and 30 June, or between 1 October and 31 December. A proposal approved in the April to June slot leads to report submission from 1 July to 30 September; one approved in October to December leads to report submission from 1 January to 31 March.
| Stage | Slot A | Slot B |
|---|---|---|
| Synopsis with proforma and guide bio-data, to the Regional Director | 1 April to 30 June | 1 October to 31 December |
| Approval | 30 days after receipt, per the calendar (see the conflicts section) | 30 days after receipt, per the calendar |
| Bound project report with CD, to the Regional Director | 1 July to 30 September | 1 January to 31 March |
| Viva-voce at the Regional Centre | November or January | May or July |
Many pages tell MCA students that the project is due on 31 May or 30 November. Those dates belong to other IGNOU project courses; MCSP-232 has its own calendar, and a report posted on 31 May has missed the window that closed on 31 March. There are no separate slots for students repeating a failed project: they use the same calendar.
How long is an approved MCA project proposal valid?
An approved MCSP-232 proposal is valid for one year, which is two slots. If you cannot submit the report in your slot, you may submit it in the subsequent slot. If you miss that one too, you need a fresh synopsis approval before any report will be accepted.
Can I send the MCA synopsis in the third semester?
Yes. The project belongs to the fourth semester of MCA_NEW, but the guidelines let you submit the proposal after entering the third semester, as per the calendar. If you enter the third semester in a July session, the first slot open to you is 1 October to 31 December. The MCA_NEW Programme Guide (July 2025) schedules four counselling sessions of two hours each in the fourth semester for discussions on the project. The programme itself runs a minimum of two years and a maximum of four.
Where the MCSP-232 Guidelines Contradict Themselves, and the Safe Reading
The July 2026 MCSP-232 guidelines give three different approval times, two synopsis lengths and a page reference for the originality certificate that does not exist. None of these is a trap if you follow the stricter reading, which satisfies every version at once. The table lists each conflict, where it sits in the document and the reading we recommend.
| Point | One place says | Another place says | Safe reading |
|---|---|---|---|
| Approval time | Calendar (Section I): 30 days after the proposal is received | Section IV: within four to six weeks. Section V: within 6 to 8 weeks | Plan for eight weeks. If nothing arrives four to six weeks after your slot’s last date, contact your Regional Centre, as Section IV advises |
| Synopsis length | Checklist after the proforma: 14 to 18 pages | Section V: 15 to 20 pages | Write 15 to 18 pages, which meets both |
| Synopsis headings | Section V numbers them (i) to (xii) | Number (ix) is used twice, so there are thirteen headings | Cover all thirteen; network architecture only where your project needs it |
| Guide’s subject | Section IV: PhD or M.Tech in Computer Science; B.E. or B.Tech (Computer Science), MCA, M.Sc. (Computer Science) | Proforma: qualification “in Computer Science / IT only” | A Computer Science degree is safe. If your guide’s degree is in IT, ask your Regional Centre in writing before the guide signs |
| Guide’s identity proof | Checklist after the proforma: attach a certified copy of the guide’s proof of identity | Section V’s list of proposal contents omits it | Attach it |
| Certificate of Originality | Section VI: format given on page 23 | The document ends at page 21; the format is Section X on page 20 | Use the Section X format |
| Who receives the report | Section XI cover: submitted to the School of Computer and Information Sciences | Sections I and VI: post to the Regional Director. Section V: never send the proposal to SOCIS | Keep the cover wording as printed; post the papers to your Regional Director |
Two of these conflicts, the approval time and the synopsis length, also appear in the earlier July 2024 and January 2025 edition, so they are carried forward from edition to edition rather than introduced recently. Until SOCIS reconciles them, the safe readings above are the cheapest insurance against a returned proposal and a lost slot.
IGNOU MCA Synopsis Format: The Proposal Package, Proforma and Guide
An MCSP-232 project proposal is a package of four items: the proforma filled in and signed with dates by you and your guide; the guide’s signed and dated bio-data with a certified copy of identity proof; the synopsis itself; and a self-addressed envelope with postage stamps for the reply by ordinary post. An incomplete proforma is summarily rejected.
What the MCSP-232 synopsis must cover
Section V lists these headings, in this order. A synopsis of around 1,000 words, which some pages recommend, cannot hold them; the guidelines expect pages, not paragraphs.
- Title of the project.
- Introduction and objectives of the project.
- Project category, such as RDBMS, OOPS, networking, artificial intelligence, expert systems, machine learning, data science, image processing or mobile computing.
- Tools and platform, with hardware and software requirement specifications.
- Problem definition, requirement specifications (detailed functional requirements and technical specifications) or literature review, and project planning and scheduling with a Gantt chart and a PERT chart.
- Scope of the solution.
- Analysis: 0, 1 and 2 level DFDs, a complete ER diagram with cardinality, and activity, class or state diagrams as the project requires.
- A complete database and table design with primary and foreign keys and proper field constraints.
- A complete structure: the number of modules with descriptions and process logic, data structures for all modules, the implementation methodology and the list of reports likely to be generated.
- Overall network architecture, if your project requires it.
- Implementation of security mechanisms at various levels.
- Future scope and further enhancement.
- Bibliography.
What does the MCSP-232 proforma ask for?
The proforma in Section II asks for your enrolment number, study centre code and name, Regional Centre and its code, e-mail and mobile number; your name and address; the project title; the guide’s name, address, qualification and working or teaching experience; the software used, with a pointer to Section VIII; and whether this is your first submission. You and the guide both sign and date it. Keep a photocopy of the complete proposal, because a revised proposal must later travel with the original or a copy of the non-approved proforma.
Who can be my IGNOU MCA project guide?
The MCSP-232 guidelines accept a guide through either of two routes: a PhD or M.Tech in Computer Science with at least one year of experience, or 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. At any given time a guide may supervise no more than five IGNOU MCA students, so ask before you fill in the proforma. The guide’s role is guidance when you hit a problem; the complete project work must be done by you. The guidelines print no fixed bio-data template, so make sure the bio-data shows the qualification, subject and years of experience that match the proforma, and carries the guide’s signature and date. The same signature must later appear on the Certificate of Originality.
How do I post the MCA synopsis?
Send the complete proposal to the Regional Director of your Regional Centre and write “MCA_NEW Project Proposal (MCSP-232)” on top of the envelope. Under no circumstances should it go to SOCIS in New Delhi. Enquiries about approval go to the same Regional Director; quote your enrolment number and project proposal number in every letter.
Which Topics and Software Are Allowed for an IGNOU MCA Project?
Any topic is allowed if it produces working software large enough for an MCA, built with current versions of current tools. The MCSP-232 guidelines reject physical installations, LAN or WAN configuration, theoretical projects and system studies without development, and they bar dBase III Plus, FoxPro, Visual FoxPro, MS-Access and a Visual Basic front end on an MS-Access back end.
One more restriction catches many students: C and C++ must not be used for information management systems such as hospital, reservation, library, school or college management systems. Section VIII then suggests, without limiting you to them, 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. The list is advisory: tools that are not listed are acceptable if they belong to current technologies. Whatever you choose, it must appear identically in the proforma, the synopsis and the report.
Can I reuse my BCA project topic for MCSP-232?
No. The Project Coordinator’s message in the MCSP-232 guidelines 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, since the effort may be treated as six months of experience by some software companies.
Can I do an AI, machine learning or data science MCA project?
Yes. The synopsis project categories include artificial intelligence, expert systems, machine learning, data science, image processing and mobile computing. The condition is the same as for every MCSP-232 project: it must include software development, so a model on its own is not enough. Package it in an application with analysis, design, testing and security, and use the documentation the guidelines name for non-database projects: class diagrams, behaviour models or state transition diagrams, and details of the data structures used.
Must I do the MCA project in a company?
It is preferred, not required. The guidelines expect most students to work on a real-life project in an industry, R&D laboratory, educational institution or software company, but a student may also formulate a problem with the guide. If an organisation asks for a letter, the guidelines provide a Project Trainee Letter, attested by the Project Coordinator, Regional Director or Assistant Regional Director.
Can two students do one IGNOU MCA project?
Preferably not. At most two students may share a project that needs one human-year or more, at six human-months each, and 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.
Match a Sample to Your Topic and Stack
Not on MCA_NEW? MCAOL, Old MCA (MCSP-060) and Other SOCIS Project Codes
MCSP-232 is the project course for both MCA_NEW in distance mode and MCAOL in online mode, but the two follow different submission routes. The old three-year MCA used MCSP-060, and two SOCIS M.Sc. programmes carry 12-credit projects under codes of their own. Check the project code on your registration before you follow any guideline.
| Programme | Project code | Where it sits | What differs |
|---|---|---|---|
| MCA_NEW (distance mode) | MCSP-232 | Semester IV, 12 credits | Proposal and bound report with CD by post to the Regional Director; viva face to face at the Regional Centre |
| MCAOL (online mode) | MCSP-232 | Semester IV, 12 credits | Proposal and report uploaded through the LMS, the report as a single PDF; viva online |
| MCA (old, three-year) | MCSP-060 | Final (sixth) semester; proposal after entering the fifth | Older guidelines; same 150 plus 50 marks and Regional Director route |
| M.Sc. Data Science and Analytics (MSCDSA) | MCSP 079 Project Work | Semester IV, 12 credits | A different course; do not assume MCSP-232 rules |
| M.Sc. Artificial Intelligence and Machine Learning (MSCAIML) | MCSP 90 Project Work | Semester IV, 12 credits | A different course; do not assume MCSP-232 rules |
| M.Sc. Mathematics with Applications in Computer Science (MSCMACS) | MMTP 001 | Semester IV, 4 credits | A different course; see the MSCMACS project hard copy category |
How is the MCAOL project different from MCA_NEW?
The MCAOL MCSP-232 guidelines (July 2024 and January 2025 edition, the latest we found online) keep the same slots, the same 150 plus 50 marks and the same guide eligibility, but move everything online. The proposal is uploaded through the LMS only, together with the proforma, the guide’s signed bio-data and a self-attested copy of the guide’s degree certificate and identity proof. The report is uploaded as a single PDF of the original, the viva is conducted online, and enquiries go to the Regional Director of the Nodal Regional Centre. Requests to share a project between two students go to [email protected]. The 2024 and 2025 MCAOL edition does not mention a CD. If a newer MCAOL edition reaches you through the LMS, follow it.
BCA students looking for a project should know that the BCA project is a separate course, BCSP-064, with its own guidelines; the IGNOU BCA help books are listed separately on this site.
Confirm Which Material Fits Your Code
IGNOU MCAOL Help BooksIf you would rather have work prepared around your own approved title than study a reference set, our customised project service handles that on a separate site.
About This Page: Author, Review Date and Official Sources
Written and reviewed 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 reviewed: 8 October 2026.
Research note: every rule on this page was checked against the MCSP-232 Project Guidelines for July 2026 and January 2027, read in full, and compared with the July 2024 and January 2025 MCA_NEW edition, the MCAOL edition, the IGNOU Common Prospectus for July 2026 and the SED fee portal. Where IGNOU’s own documents disagree, the page says so instead of choosing one silently. If a later notice from SOCIS or your Regional Centre differs from what is written here, the notice prevails.
Disclaimer: shrichakradhar.com is an independent publisher of IGNOU reference material. It is not affiliated with, authorised by or endorsed by Indira Gandhi National Open University. Questions about your enrolment, approval or result should go to your Regional Centre. For questions about our material, contact Shri Chakradhar Publication on 9354637830 or 9958947060.
Official IGNOU sources used:
- MCSP-232 Project Guidelines, MCA_NEW, July 2026 and January 2027 edition (SOCIS, IGNOU), the current edition, read in full (circulated by SOCIS; not yet posted on the assignments page we checked)
- MCSP-232 Project Guidelines, MCA_NEW, July 2024 and January 2025 edition
- MCSP-232 Project Guidelines, MCAOL, July 2024 and January 2025 edition
- MCA_NEW programme page, ignou.ac.in
- MCA_NEW Programme Guide, July 2025
- MCAOL Programme Guide, July 2024
- IGNOU Common Prospectus, July 2026 (MCA_NEW section 3.26 and examination fees)
- SED project evaluation and practical fee portal
- MCA_NEW assignments and project guidelines page, webservices.ignou.ac.in
- MCSP-060 Project Guidelines, old MCA
