← All guides
Documentation11 min read

MCA final year project report format: chapters, sample contents page and viva checklist

MCA project report format: every chapter, typical page counts, a sample contents page, a test-case table, IEEE references and a viva checklist.

This is the MCA version of the report format question. If you want the general chapter-by-chapter guide for BCA, MCA and B.Tech together, that is the final year project report format guide. This page goes deeper on what an MCA examiner expects: a requirements specification, three families of design diagrams, a real test-case table, IEEE references and the checks to run before you bind it.

One caution before anything else. Every number below, such as page ranges, font sizes and margins, is what is commonly asked for, not what your university necessarily requires. Universities and even departments differ. Your university's project guidelines or template, and your internal guide, override this page every time.

The structure at a glance

The page ranges are typical for a full MCA project of one semester, not targets. A report padded to hit a number reads worse than a tight one.

PartWhat it holdsTypical length
Front matterTitle page, certificate, declaration, acknowledgement, abstract, contents, lists of figures and tables8 to 12 pages
1. IntroductionProblem, motivation, objectives, scope, report organisation4 to 8 pages
2. Literature survey and feasibilityExisting systems, gaps, technical, economic and operational feasibility5 to 10 pages
3. System requirements (SRS)Functional and non-functional requirements, use cases, hardware and software needs8 to 15 pages
4. System designArchitecture, ER diagram, DFD levels, UML diagrams, schema, interface design15 to 25 pages
5. ImplementationTechnology choices, module descriptions, key algorithms, selected code10 to 20 pages
6. TestingStrategy, test-case tables, defects found and fixed6 to 12 pages
7. Results and discussionScreenshots against objectives, metrics, limitations5 to 10 pages
8. Conclusion and future scopeWhat was achieved, what was not, what comes next1 to 3 pages
References and appendicesIEEE references, sample code, user manual, extra screenshots5 to 20 pages

Front matter, in the order it usually appears

  • Title page. Project title, your name and enrolment number, degree and semester, guide, department, university and year. Layout is almost always dictated by the university, so copy theirs.
  • Certificate. A signed statement from your internal guide and head of department that the work is genuine. Leave space for the signatures and the college seal. If an external company guided the project, a company certificate often sits next to it.
  • Declaration. A short first-person statement that the work is your own and has not been submitted elsewhere. Write it only when it is true.
  • Acknowledgement. Two or three paragraphs thanking your guide, department and anyone who actually helped. Keep it plain.
  • Abstract. Usually one page, around 200 to 300 words: the problem, what you built, the stack in one clause, and what the results showed. Write it last, when you know what the project really does.
  • Contents, list of figures, list of tables. Generate these from heading styles in Word rather than typing them, so page numbers stay correct after edits. Front matter commonly uses roman numerals (i, ii, iii) and the main chapters restart at 1.

A sample table of contents you can adapt

This is a realistic skeleton for a web or AI project. Rename sections to fit your system; do not keep ones that do not apply.

Certificate ........................................ i
Declaration ........................................ ii
Acknowledgement .................................... iii
Abstract ........................................... iv
List of Figures / List of Tables ................... v

1  INTRODUCTION
   1.1 Background and motivation
   1.2 Problem statement
   1.3 Objectives
   1.4 Scope and limitations
   1.5 Organisation of the report
2  LITERATURE SURVEY AND FEASIBILITY
   2.1 Existing systems and their gaps
   2.2 Comparison table
   2.3 Technical, economic and operational feasibility
3  SYSTEM REQUIREMENTS SPECIFICATION
   3.1 Functional requirements
   3.2 Non-functional requirements
   3.3 Use cases
   3.4 Hardware and software requirements
4  SYSTEM DESIGN
   4.1 Architecture
   4.2 ER diagram and database schema
   4.3 Data flow diagrams (level 0, 1, 2)
   4.4 UML: use case, class, sequence, activity
   4.5 Interface design
5  IMPLEMENTATION
   5.1 Technology stack and why
   5.2 Module-wise implementation
   5.3 Key algorithms and code excerpts
6  TESTING
   6.1 Test strategy
   6.2 Test cases and results
   6.3 Defects found and fixed
7  RESULTS AND DISCUSSION
8  CONCLUSION AND FUTURE SCOPE
REFERENCES
APPENDICES  A. Source code excerpts  B. User manual

Chapters 1 and 2: introduction, literature survey and feasibility

State the problem in terms of a person who has it: who, what goes wrong today, what it costs them. Then number your objectives so the conclusion can answer each one. Under scope, list what the system does not do; a declared boundary is stronger than a vague promise.

For the literature survey, MCA examiners want real systems or papers, not a textbook definition of your topic. Name three to six existing tools or published approaches, say what each does badly for your problem, and put it in a comparison table. Feasibility gets a short, honest paragraph each for technical (do you know the stack), economic (free tiers, open source) and operational (will the intended users actually use it).

Chapter 3: the SRS

Many MCA departments follow the IEEE 830 style of software requirements specification, or a trimmed version of it. Whatever your university calls it, the working core is:

  • Numbered functional requirements (FR1, FR2, ...) written as testable statements, such as “The system shall reject a second booking for the same doctor and slot.”
  • Non-functional requirements with a measurable edge where you can: response time, concurrent users, password handling, browser support.
  • Use cases for each actor with a short description of main and alternate flows.
  • Hardware and software requirements for both development and deployment.

Number requirements on purpose. Your test-case table in Chapter 6 should point back to them, which is the thread that makes a report look engineered rather than assembled.

Chapter 4: design, where most marks sit

Include only diagrams that describe your system, and draw them from the built version. A typical MCA set is:

  • Architecture diagram. Client, server, database and any external service, with the direction of each call.
  • ER diagram and schema. Entities, keys and relationships, then each table with column, type and constraint. Mention normal form if your department expects it.
  • DFDs. Level 0 (context), level 1 (major processes) and, where the system is large, level 2 for one process. Keep data stores and external entities consistent between levels.
  • UML. A use case diagram, a class diagram, and a sequence diagram for the one flow that matters most, for example login or booking. An activity or state diagram suits workflow-heavy projects.
  • Interface design. Wireframes or screenshots of the main screens.

Under each diagram, write two sentences: what it shows and why you drew it that way. A diagram with no explanation is an image, not design.

Chapter 5: implementation

Do not paste the whole codebase. Describe each module: its purpose, its inputs and outputs, and the one or two decisions inside it. Use pseudocode or a short excerpt for the core algorithm, such as the slot conflict check or the ranking function, and put longer listings in an appendix. If you used a library for something hard, say so. Examiners respect clear credit far more than silence.

Chapter 6: testing, with a sample test-case table

Describe your strategy in a paragraph (unit, integration, system, and user acceptance where applicable), then show the cases. A useful table ties each case to a requirement, states the input, the expected result and the actual result. The rows below are an illustrative style for an appointment-booking system; yours must come from tests you really ran.

IDRequirementInputExpectedActualStatus
TC-01FR1 LoginValid email and passwordDashboard for the user's role opensAs expectedPass
TC-02FR1 LoginValid email, wrong passwordError shown, no token issuedAs expectedPass
TC-03FR4 BookingBook a free slotAppointment saved, slot marked takenAs expectedPass
TC-04FR4 BookingBook a slot already takenRejected with a slot-taken messageAs expectedPass
TC-05NFR2 AccessPatient calls an admin API route403 ForbiddenAs expectedPass
TC-06FR6 BillingComplete a visit with two servicesBill total equals fee plus servicesTotal off by one service, fixed in build 14Fixed, retested

Including a failed-then-fixed row is not a weakness. It shows testing actually changed the software. After the table, list known bugs and limitations honestly.

Chapters 7 and 8: results, conclusion and future scope

Results map back to the numbered objectives: objective, what you built, evidence (screenshot, metric or test result). For an ML project, report your dataset size, split, metric and at least one failure case. The conclusion is short: what was achieved, what was not, and two or three concrete future-scope items that follow from your real limitations, rather than a list of fashionable technologies.

Formatting norms, and why to verify each one

ElementCommonly askedCheck against your template
Body fontTimes New Roman, 12 ptSome ask for Arial or Calibri
Line spacing1.5, text justifiedSome specify double spacing
MarginsAbout 1.5 in left, 1 in on other sidesBinding margin differs by university
HeadingsNumbered; chapter title 14 to 16 pt bold, sections 12 to 14 ptNumbering depth varies
Page numbersRoman in front matter, Arabic from Chapter 1Position varies
Figures and tablesNumbered by chapter (Figure 4.2), caption below figures and above tablesSome use continuous numbering
Binding and copiesHard or spiral bound, often 2 to 3 copiesColour, cover and copy count are set by the department

References in IEEE style

IEEE is a numbered style: cite as [1] in the text, and list sources in order of first appearance. Include only what you read and used. A short, real list beats thirty padded entries you cannot discuss. Patterns:

[1] A. Author and B. Author, "Title of paper," Journal Name, vol. 12, no. 3, pp. 45-58, 2023.
[2] C. Author, Title of Book, 2nd ed. City: Publisher, 2021.
[3] "Page or tool name," Organisation. Available: https://example.com/page (accessed 15 Nov. 2026).

Those are format patterns with placeholder details, not real citations. Always include an access date for web sources, and cite documentation for the frameworks and datasets you used.

Plagiarism and originality checklist

Many universities run reports through similarity software, and each sets its own acceptable threshold. Ask your department what theirs is and whether references are excluded from the score. Before submitting:

  • Every paragraph is in your own words; definitions copied from Wikipedia or a seniors' report are rewritten from your understanding.
  • Anything quoted is in quotation marks and cited.
  • Diagrams are your own, or the source is credited.
  • Code from a tutorial, repository or library is acknowledged in the report and in the code comments.
  • Your project differs meaningfully from others in your batch; copied titles and structures are noticed.
  • The report describes the system you built, not a more impressive one.

Viva checklist for the report

The report is also your viva script. Before the date, check that you can do each of these without notes:

  1. State the problem and your objectives in under a minute.
  2. Draw the ER diagram on a whiteboard and explain each relationship.
  3. Walk the level-1 DFD and name what flows on each arrow.
  4. Open any screenshot from the report and show the same screen running.
  5. Explain one test case that failed first, and what you changed.
  6. Say what the system cannot do, and why it is out of scope.
  7. Explain every library and every reference you listed.

For the questions panels ask in return, read the viva questions guide and how to explain your project in the viva.


Want to see a finished report before you write yours? The sample project report shows a complete one with SRS, diagrams, implementation and test cases, and the templates page has the layout to start from. Next in this series: the MCA project synopsis with a worked sample you submit before building, and how to use MCA projects with source code properly. Still choosing a topic? See MCA final year project topics.

The BCA-level documents and a 12-week plan are in choosing a BCA final year project. For smaller projects earlier in the course, see mini project ideas.

Quick answers

How many pages should an MCA project report be?
Most MCA reports land between 60 and 120 pages including front matter and appendices, but this is a common range, not a rule. Some universities set a minimum or maximum, and some count only the main chapters. Check your own project guidelines and ask your internal guide.
What font and spacing does an MCA project report use?
A common choice is Times New Roman 12 pt for body text, 1.5 line spacing, justified, with chapter headings at 14 to 16 pt bold. Margins of about 1.5 inches on the binding side and 1 inch elsewhere are also common. These vary by university, so follow your template if it states something different.
Which referencing style should I use in an MCA report?
IEEE numbered style is the usual choice in computer applications reports: citations as [1], [2] in the text, and a numbered list at the end in order of first appearance. Some universities ask for APA or Harvard instead, so check which one your department specifies.
Does the MCA report need to match the code I submit?
Yes. Examiners often open one screen or one table from the report and ask you to find it in the running system. Every diagram, table name and screenshot in the report should match the final build, not an earlier draft.

Want to build it together in live classes?

You get a design and a module-by-module plan, then we build it together in daily live classes, with you writing part of every module and every report chapter reviewed, until you can defend it. Tell me what you need and your deadline.