MCS 213 Solved Guess Paper 2026 is a 14 page exam preparation set built for students of Software Engineering in the IGNOU Master of Computer Applications (MCA_NEW) degree programme. It carries 13 questions with complete written answers, each one mapped to the block and unit it comes from, and each one sized to the marks it usually carries in the term end paper.
We did not guess these questions. Our team read the term end papers going back five years, then tabulated the six most recent sessions from June 2023 to December 2025 to see which topics genuinely repeat. The December 2025 paper was the last one added, and it changed two of our priority calls. Five of the 13 answers are reproduced in full further down this page so you can judge the writing before you ask for anything.
MCS 213 Guess Paper Key Facts
| Course code and title | MCS-213 Software Engineering |
|---|---|
| Programme | Master of Computer Applications (MCA_NEW), Semester I |
| Questions in the set | 13 questions with full answers |
| Shown on this page | 5 answers in full, 8 remaining in the complete file |
| Length | 14 pages including the exam strategy sheet |
| Syllabus covered | 4 blocks, 16 units |
| Sessions analysed | 6 papers, June 2023 to December 2025 |
| Target sessions | June 2026 and December 2026 |
| Paper pattern | 3 hours, 100 marks, weightage 70 per cent |
| Delivery | PDF on WhatsApp at 9899436384 |
What You Receive in the MCS 213 Guess Paper File
You receive one PDF of 14 pages holding 13 exam style questions for MCS 213 Software Engineering, each with a finished answer, a block and unit tag, a marks tag and a record of the sessions in which that topic last appeared.
- MCS 213 Solved Guess Paper 2026 covering all four blocks of Software Engineering, with 13 questions and 13 complete answers.
- Answers written to the marks they carry, so a 20 mark question runs to roughly 450 words and a 10 mark question to roughly 250 words.
- A block and unit tag on every question, so you can open the correct IGNOU unit and revise from the source when an answer needs more depth.
- A last appeared line on every question listing the exact sessions in which that topic was set, taken from the papers we read.
- A priority label of high, medium or low so you know what to write first when revision time runs short.
- A frequency table mapping 26 recurring topics against the six sessions from June 2023 to December 2025.
- An exam strategy page covering the paper pattern, the topics not worth over preparing and what examiners reward in answer scripts.
Every answer opens with the textbook definition, then breaks into numbered points, then closes with a short evaluative conclusion. That shape is deliberate. Evaluators scan for structure before they read for content, and a wall of unbroken prose loses marks that the same student would have earned with headings and numbering. If you want the wider set across your other papers, our IGNOU Solved Guess Paper collection follows the same format for every course code we cover.
MCS 213 Solved Guess Paper Sample Answers You Can Read Now
Five of the 13 answers are printed in full below, exactly as they appear in the file, so you can check the depth, the language and the structure before contacting us. The remaining eight follow the same standard. Nothing here is shortened or watered down for the web page.
Sample 1 of 5 | Software Development Models, Waterfall and Spiral
Question. Discuss the various software development models. Explain the Waterfall Model and the Spiral Model in detail, highlighting their features.
Meaning of Software Engineering. It is the application of a systematic, disciplined and quantifiable approach to the development, operation and maintenance of software. Large software needs systematic development, and applying an engineering approach to it produced the discipline we now call software engineering, covering cost estimation, design, coding, documentation, maintenance, quality assurance and testing.
Software development models.
- Build and fix. A simple two phase model in which code is developed in one phase and then fixed until the client is satisfied.
- Waterfall. The simplest, oldest and most widely used model, where each phase is completed before the next begins.
- Iterative enhancement. Construction and delivery happen iteratively, and each iteration is itself a full waterfall.
- Prototyping. A working prototype of lesser capability is built first so that requirements are captured more deeply.
- Spiral. Combines the strengths of the other models by treating development as an expanding, iterative spiral.
Waterfall Model. It gives a systematic and sequential approach through requirements analysis, design, coding, testing and maintenance. It improves on build and fix, but complete requirements must be available at commencement, it carries no risk assessment, and no working model exists between phases.
Spiral Model. Boehm's spiral model, published through the IEEE in 1988, treats development as a spiral with four activities followed iteratively. Objectives are finalised for the phase, risks are identified and analysed, development proceeds under a selected SDLC model, and planning reviews the work and decides whether to loop again.
The radial dimension of the spiral represents cumulative cost and the angular dimension represents progress. Because technical risk gets direct consideration in every loop, the model stays realistic for large scale, high risk projects where requirements cannot be frozen at the start.
Conclusion. The Waterfall Model suits projects with stable and well understood requirements, while the Spiral Model absorbs uncertainty through repeated risk analysis, which makes it the better fit for large and high risk software.
Sample 2 of 5 | Software Design, Coupling and Cohesion
Question. What is software design? Explain coupling and cohesion, and discuss the various types of each.
Meaning of software design. Software design applies engineering techniques to build models that define a software system in enough detail for actual realisation. Independence between modules is measured by two parameters, cohesion and coupling, and highly cohesive with loosely coupled modules is the desirable combination.
Cohesion, the functional strength of a module, has six types.
- Coincidental. The worst form, where a module performs unrelated tasks.
- Logical. The module performs a series of actions selected by a calling module.
- Procedural. Elements take up a single control sequence in a specific order.
- Communicational. All elements work on the same data set and produce the same output.
- Sequential. The output of one element is the input to another within the module.
- Functional. The best form, where the elements perform exactly one function.
Coupling, the interdependence between modules, also has six types.
- Data coupling. Modules interact only through parameters, which is the best case.
- Stamp coupling. Modules share a composite data structure.
- Control coupling. One module controls the logic flow of another through a flag.
- External coupling. Modules share an external data format.
- Common coupling. Modules share the same global data.
- Content coupling. One module modifies the data of another, which is the worst case.
Conclusion. Good design pushes cohesion up and coupling down, because the two correlate and together decide how easily the software can be maintained, reused and understood.
Sample 3 of 5 | Project Estimation, COCOMO and Putnam's Model
Question. Explain the COCOMO Model for software cost estimation, including its levels and classes of projects. Also explain Putnam's Model.
Meaning of COCOMO. COCOMO stands for Constructive Cost Model and was introduced by Barry Boehm. It is the best known and most documented software cost estimation model, and it provides three levels of model.
Levels of COCOMO.
- Basic COCOMO. A single value model that computes development cost as a function of the estimated lines of code.
- Intermediate COCOMO. Computes cost and effort as a function of programme size in LOC together with a set of cost drivers.
- Detailed COCOMO. Incorporates all intermediate characteristics plus the cost implications at each step of development.
Three classes of software projects.
- Organic. A small project where the development team has good experience of the application.
- Semi detached. An intermediate project based on rigid and semi rigid requirements.
- Embedded. Developed under hardware, software and operational constraints, flight control software being the standard example.
The effort equation is E = a.S^b.m, where E is effort, S is source size in lines of code and m is a multiplier drawn from 15 cost driver attributes such as database size, complexity, reliability and performance constraints. Boehm suggested that the detailed model lands within plus or minus 20 per cent of the actual value.
Putnam's Model. L. H. Putnam developed a dynamic multivariate model of software development on the assumption that effort distributed over the life of a project follows the Rayleigh Norden curve.
The model uses P = K.t.exp(t squared divided by 2T squared) divided by T squared, where P is the number of persons at time t, K is the total life cycle effort represented by the area under the Rayleigh curve, and T is development time. From this it derives S = Ck.K^(1/3).T^(4/3), linking delivered lines of code to time and effort.
Conclusion. COCOMO estimates effort and cost from size and cost drivers across three project classes, while Putnam's model uses the Rayleigh Norden curve to relate manpower, time and delivered code.
Sample 4 of 5 | Software Testing, Black Box against White Box
Question. Explain Black Box and White Box testing strategies. How do they differ from each other? Give one example of each.
Meaning of software testing. Black box testing derives test cases from the functional specification of the system, while white box testing derives them from the internal design specification or the actual code. A failure is a deviation of observed behaviour from the specification, a fault is an incorrect step or data definition, and an error is the difference between a computed value and the correct one.
Black box testing. Test cases are selected without reference to programme design or code, so the tester works only with functionality and features. The advantage is that it can start before design or coding and is strong at finding missing functions. The limitation is that it cannot detect additional, unspecified functions sitting in the code.
White box testing. Also called glass box testing, it selects test cases using the specification, the design and the code, which means access to internal detail. Its advantage is that it exercises every path the programme can take. Its limitation is that testing has to wait until design and coding are finished.
| Basis | Black box | White box |
|---|---|---|
| Source of test cases | Functional specification | Internal design and code |
| Knowledge of code | Not required | Required |
| Timing | Before design and coding | After design and coding |
| Detects | Missing functions | Unspecified or extra code |
Conclusion. Black box testing checks functionality from the outside and can begin early, while white box testing examines internal paths but needs completed code, so combining the two gives the strongest coverage.
Sample 5 of 5 | UML Classification and Diagram Types
Question. What is UML? Explain the classification of UML diagrams with the main diagrams under each category.
Meaning of UML. The Unified Modeling Language is a structured language that supplies a commonly agreed vocabulary to communicate, model and document the structural and behavioural aspects of a software system. It is standards based, general purpose and language independent, usable alongside Java, Python, C# and others, and it delivers the software blueprint in visual form.
Classification. UML diagrams fall into two broad categories, static or structure diagrams and dynamic or behaviour diagrams.
Static or structural diagrams. These represent the static physical elements of the system that stay unchanged, and they include the class diagram, the object diagram, the component diagram and the deployment diagram.
Dynamic or behavioural diagrams.
- Sequence diagram. Models a single use case or scenario using time ordered messages between objects.
- Activity diagram. Describes business logic, business process and work flows.
- State chart diagram. Describes system behaviour through the state transitions of an object on events.
- Use case diagram. Models the requirements and the components involved in a use case.
- Collaboration diagram. Depicts the interaction and the relationships among objects.
Conclusion. UML is a standard visual modelling language whose structural diagrams capture the static design and whose behavioural diagrams capture runtime behaviour, giving a complete blueprint of the system.
The Eight MCS 213 Questions Held in the Complete File
The five answers above are the preview. These eight are in the file and are not printed on this page.
- Software quality, its attributes and the metrics used to measure it, Block 1 Unit 4, 10 marks.
- Requirements engineering, functional against non functional requirements and the SRS outline, Block 1 Unit 2, 10 marks.
- Risk, the four phases of risk management and how software risks are identified, Block 2 Unit 6, 10 marks.
- Web software engineering, characteristics of a web application and team organisation, Block 3 Unit 9, 10 marks.
- Mobile software engineering and the four development approaches, Block 3 Unit 10, 10 marks.
- CASE tools, their three categories and the factors affecting deployment, Block 3 Unit 11, 10 marks.
- Process optimisation, the First Time Right framework and the role of SEI CMMi, Block 4 Unit 13, 10 marks.
- Emerging trends in software engineering together with data science phases and methods, Block 4 Units 14 and 16, 20 marks.
How the MCS 213 Guess Paper Was Built from Past Papers
The question list was produced by tabulating six term end papers from June 2023 to December 2025, marking every topic that appeared, and then ranking topics by repeat count and by recency. Nothing on the list is there because it looked important in the textbook.
The work ran in four passes. First we pulled the papers and typed out every question, not just the topic name, because the same topic gets asked in two or three different shapes. Second we mapped each question back to its block and unit using the official IGNOU units on eGyanKosh. Third we counted. Fourth we wrote the answers, checking each definition against the unit it came from rather than paraphrasing from memory.
The December 2025 paper mattered most and was read last. It moved software quality and risk management up, since both have now appeared in four of the last five sessions, and it flagged software reuse and configuration management as a fresh entry worth keeping as backup. If you want to run the same check yourself, start with the IGNOU Previous Year Question Paper archive and read the papers in reverse order.
One honest caveat. A guess paper narrows your revision, it does not replace it. Roughly 70 per cent of a term end paper tends to sit inside recurring territory and the rest does not. Treat these 13 questions as the core you write confidently, then keep the low priority topics as a thin backup layer rather than skipping them outright.
MCS 213 Software Engineering Block and Unit Index
MCS 213 runs to four blocks and 16 units, and the guess paper draws from 13 of those units. The table below lists what each unit actually contains at exam level, so you can see where each question sits and which units are thin ground for the term end paper.
| Block | Unit | Key topics at exam level | In this guess paper |
|---|---|---|---|
| Block 1, An Overview of Software Engineering | Unit 1, Software Engineering and Its Models | Definition of software engineering, build and fix, waterfall phases, iterative enhancement, prototyping, Boehm's four spiral activities, radial and angular dimensions | Yes, 20 mark question |
| Unit 2, Principles of Software Requirements Analysis | Requirements definition against requirements management, the RDD, functional against non functional requirements, four part SRS outline, validation | Yes, 10 mark question | |
| Unit 3, Software Design | Design models, modularity, six cohesion types from coincidental to functional, six coupling types from data to content | Yes, 10 mark question | |
| Unit 4, Software Quality and Security | Quality as conformance, nine attributes including auditability and traceability, defect metrics, mean time to failure, maintainability metrics | Yes, 10 mark question | |
| Block 2, Software Project Management | Unit 5, Software Project Planning | LOC based estimation, three COCOMO levels, organic and semi detached and embedded classes, 15 cost drivers, Putnam and the Rayleigh Norden curve | Yes, 20 mark question |
| Unit 6, Risk Management and Project Scheduling | Risk as potential problem, avoidance and detection and control and recovery, risk prioritisation, scheduling the who and what and when of each risk | Yes, 10 mark question | |
| Unit 7, Software Testing | Failure against fault against error, test case structure, black box selection, white box path coverage, cyclomatic complexity and control flow graphs | Yes, 10 mark question | |
| Unit 8, Software Change Management | Change control procedure, software configuration management, version and release handling, baselines | Backup only, low frequency | |
| Block 3, Web, Mobile and Case Tools | Unit 9, Web Software Engineering | Internet against intranet against extranet, layered architecture, thin client, server side processing, webmaster and application support team roles | Yes, 10 mark question |
| Unit 10, Mobile Software Engineering | Native development with platform SDKs, cross platform single codebase, rapid mobile application development, progressive web applications | Yes, 10 mark question | |
| Unit 11, Case Tools | Upper CASE for analysis and design, lower CASE for coding and configuration, integrated CASE, deployment factors such as methodology and staff training | Yes, 10 mark question | |
| Unit 12, Advanced Topics in Software Engineering | Cleanroom software engineering, software reuse, software reliability, re engineering against reverse engineering [VERIFY unit split against your own copy of the block] | Backup only, appears irregularly | |
| Block 4, Advanced Topics in Software Engineering | Unit 13, Software Process Improvement | Process optimisation, First Time Right framework and its nine categories, requirement traceability matrix, SEI CMMi process areas | Yes, 10 mark question |
| Unit 14, Emerging Trends in Software Engineering | Low code and no code platforms, artificial intelligence, blockchain, internet of things, augmented reality, containerisation, cloud and big data | Yes, part of a 20 mark question | |
| Unit 15, Introduction to UML | Static against dynamic classification, class and object and component and deployment diagrams, sequence and activity and state and use case and collaboration diagrams | Yes, 10 mark question | |
| Unit 16, Data Science for Software Engineers | Definition of data science, five phase process from requirements gathering to visualisation, clustering, collaborative filtering, regression, classification | Yes, part of a 20 mark question |
Units 8 and 12 are the two we deliberately did not build full answers around. They surface occasionally rather than reliably, and the marks you would spend memorising them are better placed elsewhere. Read them once from your MCS 213 Study Material so a short note question does not catch you cold, then move on.
MCS 213 Topic Frequency Across the Last Six Sessions
Twenty six recurring topics were tracked across six sessions, and eleven of them were classed high priority because they either repeated four or more times or filled a gap in the recent papers. A tick means the topic appeared in that session's paper.
| Topic | Jun 23 | Dec 23 | Jun 24 | Dec 24 | Jun 25 | Dec 25 | Priority |
|---|---|---|---|---|---|---|---|
| SDLC and software models | Yes | No | Yes | Yes | Yes | Yes | High |
| COCOMO model | Yes | No | Yes | No | Yes | Yes | High |
| Putnam's model | No | Yes | No | Yes | No | No | Medium |
| Software project estimation | Yes | No | No | No | No | No | Medium |
| Software quality and attributes | No | Yes | Yes | Yes | Yes | Yes | High |
| Software quality metrics | Yes | No | No | No | No | Yes | Medium |
| Software design, architectural and modular | No | Yes | Yes | No | No | Yes | High |
| Coupling and cohesion | No | No | No | Yes | Yes | No | Medium |
| Requirements engineering and SRS | No | Yes | Yes | No | Yes | No | Medium |
| Risk management and analysis | No | Yes | No | Yes | Yes | Yes | High |
| Software testing, black box and white box | No | No | Yes | No | Yes | Yes | High |
| Cyclomatic complexity and control flow graphs | Yes | No | No | No | Yes | No | Medium |
| Software change and change control | No | Yes | No | No | No | No | Low |
| Web software engineering | Yes | No | Yes | Yes | No | No | High |
| Mobile application development | Yes | No | Yes | Yes | No | No | High |
| CASE tools | Yes | No | No | Yes | No | No | Medium |
| Cleanroom software engineering | Yes | No | No | Yes | No | No | Medium |
| FTR framework and process optimisation | Yes | Yes | No | Yes | No | No | High |
| Capability maturity model, CMM and CMMi | No | No | Yes | No | No | No | Low |
| UML diagrams | No | Yes | Yes | No | No | No | High |
| Re engineering against reverse engineering | No | Yes | Yes | Yes | Yes | Yes | High |
| Emerging trends, low code and containerisation | Yes | Yes | No | No | No | No | Medium |
| Data science life cycle and methods | No | Yes | Yes | No | No | No | Medium |
| HCI and user experience in software design | Yes | No | No | No | No | Yes | Medium |
| Software reliability | No | No | No | Yes | No | No | Low |
| Software reuse, SCM and SPI | No | No | No | No | No | Yes | Low |
Two patterns are worth reading off this table. Re engineering against reverse engineering has now appeared in five straight sessions, which makes it the single most reliable topic in the course. Web software engineering and mobile application development, by contrast, ran hot through 2023 and 2024 and have been quiet since, which is exactly the profile of a topic due to return.
MCS 213 Exam Pattern and Answer Word Limits
MCS 213 is a three hour paper of 100 marks with a weightage of 70 per cent, where question one is compulsory and you attempt any three questions from the rest, giving four answers in total. Confirm the instruction line on your own hall paper, since the marks split within question one can vary by session [VERIFY against your latest question paper].
| Marks | Target length | Time to allow | Structure that scores |
|---|---|---|---|
| 20 marks | Around 450 words | 40 to 45 minutes | Definition, five to seven numbered points, diagram or table, three line conclusion |
| 10 marks | Around 250 words | 20 to 25 minutes | Definition, list with exact counts, one example, two line conclusion |
| 5 marks | Around 150 words | 10 minutes | Definition and three or four crisp points |
What evaluators reward in this paper is specific. Open with the textbook definition and name the source where the book names one, Boehm for the spiral and for COCOMO, Putnam for the Rayleigh Norden curve. Give exact counts and the full list, six types of cohesion and not four. Pair the concept with a comparison table wherever the unit compares two things.
What is not worth over preparing is equally specific. Skip heavy numerical derivation and hold on to the formula and its meaning instead. Do not memorise all 15 cost drivers or every UML notation symbol. Keep single appearance topics such as software reliability as a backup layer only. The same discipline applies across our MCA Guess Paper sets for the other first semester papers.
MCS 213 Practical File and Lab Record Index
MCS 213 is a theory paper and does not carry a practical file of its own, so the guess paper covers written answers only. Laboratory work in MCA (NEW) is assessed through the separate lab course of the semester rather than through this course code [VERIFY the lab course code with your study centre before submitting anything].
That said, several study centres ask software engineering students for a project record built around the same syllabus. Where that applies, the index we follow runs as below. It is a working index used by students rather than an IGNOU prescribed list, so match it against whatever your counsellor asks for.
- Problem statement and scope of the chosen system.
- Selection of a software development model with justification.
- Software Requirements Specification written to the four part outline.
- Data flow diagrams at level zero and level one.
- Use case diagram with actors and the use case description.
- Class diagram and object diagram for the same system.
- Sequence diagram and activity diagram for the core workflow.
- Modular design showing cohesion and coupling decisions.
- Effort and cost estimate worked through basic COCOMO.
- Project schedule with a Gantt chart and milestone list.
- Risk register with identification, analysis and mitigation.
- Test case table covering black box and white box cases.
- Test log with defects found and their resolution status.
- Conclusion, limitations and scope for future enhancement.
Who Should Use This MCS 213 Solved Guess Paper
This set is built for MCA (NEW) students who have limited time before the term end exam and need a defensible shortlist rather than the full 16 unit syllabus. It suits four situations in particular.
- Working students revising in the last three weeks. Thirteen prepared answers is a realistic load. Sixteen units is not, and attempting both usually means finishing neither.
- Students reappearing after a backlog. The frequency table tells you what the paper has actually asked recently, which is more useful than starting the book again from Unit 1.
- Students who understand the concepts but lose marks on presentation. The answers show the shape an evaluator rewards, with definitions, numbered lists and a closing judgement.
- Students weak in English expression. The language is deliberately plain, the sentences are short, and the answers can be learned and reproduced without translation trouble.
It is not the right buy if you are aiming to top the paper, if your study centre has flagged a changed syllabus, or if you have not opened the blocks at all. A guess paper compresses revision. It cannot substitute for a first reading of the units.
How to Get the Complete MCS 213 Guess Paper with Answers
Message us on WhatsApp at 9899436384 with your course code, MCS 213, and the session you are appearing in, and we will send the complete 14 page file with all 13 answers. The five answers on this page stay visible either way, so you can compare before you decide.
Tell us the session, June 2026 or December 2026, because the priority ordering we suggest shifts slightly between the two. If you are taking more than one first semester paper this session, say so in the same message and we will tell you which sets are ready rather than making you ask code by code.
Prepared by Prateek Talwar, founder of Unnati Educations, and reviewed by Sheetal Kirola, academic support head at Unnati Educations, who checks every set against the official unit content before it goes out. Questions about content accuracy reach the same number.
MCS 213 Guess Paper Questions Students Ask
What is included in the MCS 213 guess paper for 2026?
The file holds 13 exam style questions for MCS 213 Software Engineering with complete answers, each tagged with its block, unit, marks and the sessions in which the topic last appeared. It also carries a frequency table covering 26 topics across six sessions and a strategy page on the paper pattern and word limits. It runs to 14 pages in all.
How many MCS 213 answers can I read before contacting you?
Five of the 13 answers are printed in full on this page, covering software development models, coupling and cohesion, COCOMO with Putnam's model, black box against white box testing, and UML classification. Nothing in them is shortened. The remaining eight answers sit in the complete file and follow exactly the same structure and depth as the five shown here.
Is the MCS 213 guess paper valid for both June 2026 and December 2026?
Yes. The same file targets both 2026 term end sessions, since IGNOU sets MCS 213 from the same four blocks in June and December. We suggest a slightly different priority order for each session based on what the preceding paper asked, so mention your session when you message us and we will point you to the questions to attempt first.
Are the MCS 213 answers written from the IGNOU textbook?
Yes. Every definition is checked against the official unit on eGyanKosh rather than paraphrased from memory, and each answer names the block and unit it draws from. Where the book credits a source, such as Boehm for the spiral model or Putnam for the Rayleigh Norden curve, the answer names it too, because evaluators look for that attribution.
What is the exam pattern for MCS 213 Software Engineering?
MCS 213 is a three hour paper of 100 marks carrying 70 per cent weightage. Question one is compulsory and you attempt any three from the remaining questions, so four answers in total. Target roughly 450 words for a 20 mark answer and 250 for a 10 mark answer. Confirm the instruction line printed on your own question paper before you begin.
Does MCS 213 have a practical file in MCA (NEW)?
No. MCS 213 is a theory course, so there is no practical file attached to this code and the guess paper covers written answers only. Practical work in the semester is assessed through the separate laboratory course. If your study centre still asks for a software engineering project record, the index we follow is listed in the practical file section above.
Will preparing only the MCS 213 guess paper be enough to pass?
For most students it covers the bulk of what the paper asks, because these 13 questions come from topics that have repeated across six sessions. We would still be straight with you. Some marks always sit outside recurring territory, so read the low priority units once as backup rather than skipping them entirely, then write the prepared answers with confidence.
How will the complete MCS 213 file reach me after I message you?
Delivery is on WhatsApp at 9899436384. Send your course code and session, and the PDF comes back on the same chat, so there is no login, no portal and no waiting for a download link to arrive by email. If any answer is unclear once you start revising, reply on the same chat and the same team that wrote it will explain it.
Unnati Educations prepares this study aid independently. It is not an official IGNOU publication and carries no endorsement from the university. Question papers, unit content and examination rules remain the property of IGNOU.