Scribd
Upload
8 views

Documentation Guidelines

The document provides guidelines for formatting a report for an MCA program. It specifies page layout details like margins and paragraph formatting. It outlines the required report structure including a title page, declaration, table of contents, and minimum of 6 chapters covering topics like introduction, analysis, design, project management, testing and future work. Appendices for figures and code are also required.

Uploaded by

krn.rna.2003
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
8 views

Documentation Guidelines

The document provides guidelines for formatting a report for an MCA program. It specifies page layout details like margins and paragraph formatting. It outlines the required report structure including a title page, declaration, table of contents, and minimum of 6 chapters covering topics like introduction, analysis, design, project management, testing and future work. Appendices for figures and code are also required.

Uploaded by

krn.rna.2003
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Department of Computer Applications

Graphic Era University, Dehradun, INDIA‐248002


Guidelines for Report (MCA)
Pagination:
Page: A4
Margins:
Top ‐ 1 inch
Bottom ‐ ‐ 1 inch
Left ‐ 1 inch
Right‐ 1 inch
Gutter ‐ 0.5 inch

Paragraph Formatting:
Interline spacing ‐ 1.5
Before ‐ 6 points
After ‐ 6 points
First line indent ‐ 0.5

Page order:
1. First Page ‐ Title Page
2. Candidate Declaration
3. Internal Guide Certificate
4. Internal Guide Certificate (Sample Attached)
5. Acknowledgement
6. Preface (optional)
7. Table of Contents (TOC) ‐ Chapter number, Headings and Subheadings with proper
page number

Chapterization (Number of Chapter 6‐8)

Chapter 1‐ Introduction
(Topics ‐ Company introduction, Project introduction, Motivation, Objective & Scope,
H/W & S/W requirement, ...).

Chapter 2‐ System Analysis & Requirements Specifications


Covering the DFDs, System Chart, Sequence Diagrams, Use Case diagrams (which ever
diagrams applicable to your project)

Chapter 3‐ System Design


Covering the ER Diagram, Flow charts, Algorithms, Design of solution (which ever
diagrams applicable to your project)

Chapter 4 – Project Management


4.1 Project Planning and scheduling
4.1.1 Project Development Approach (Process Paradigm) and Justification
4.1.2 Project Plan including Milestones, Deliverables, Roles, Responsibilities and
Dependencies
4.2 Risk Management
4.2.1 Risk Identification (it is concerned with discovering possible risk to the project)
4.2.2 Risk Analysis (each identified risk is considered in turn and a judgment made
about the probability and the seriousness of the risk)
4.2.3Risk Planning (Identify strategies to manage the risk)

4.3 Estimation
4.3.1 Cost Analysis (Total cost of the project including resources and labors. Labor cost
should be broken down into the areas of design, analysis, prototype construction,
software development, hardware-software integration, testing, design modifications
and documentation. A cost analysis is NOT a tabulation of your expenditure)

Chapter 5 ‐ Input Design


‐ Including all input screens/forms

Chapter 6‐ Output Design


‐ Including all outputs screen shots/reports and/or results

Chapter 7‐ System Testing, Implementation & Maintenance


‐ Specific to your project only

Chapter 8‐ Summary and Future Scope

References/Bibliography

Appendices
Note:
All the figures are to be Numbered & Labelled
The Module/Class code is required to be included in the Appendices numbered as:
Appendix A
Appendix B
Footer ‐ Page Numbering like: ~ 1 ~
Header ‐ Follow any of the Header style used in attached reports; Do not use Your
Name,University Name, Project Name as Header ‐ as its not in any standard. Header can be the
Chapter and Heading name.

You might also like