0% found this document useful (0 votes)
22 views

Final Project Guidelines

Uploaded by

Manish Nishad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
22 views

Final Project Guidelines

Uploaded by

Manish Nishad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

DETAILED GUIDELINES FOR PROJECT (KCA-353)

MCA PROJECT DOCUMENTATION

[I] INTRODUCTION

The final year project work in MCA should represent a coherent body of original work by the
students using the technical knowledge and skills acquired during the three years of course. It
should portray a scholarly approach and thorough knowledge of the subject. MCA project report
is an organized documentation of this work, involving correlation of facts already known
(analytical, experimental, hardware oriented/simulation based etc.). This report should
demonstrate a quality as to make a definite contribution to the advancement of knowledge and the
students’ ability to present the findings in an appropriate manner along with actual
accomplishments of the work plainly stated and honestly appraised.

In view of above, detailed guidelines and formats for MCA project report documentation are
explained in the succeeding paragraphs.
(1) MCA project report will be submitted Spiral bounded. The Report should be upto the
guidelines in spiral binding.
(2) Students should submit ONE Copy of the project report in the Department.

[II] GENERAL TYPING INSTRUCTIONS

(1) (a) Standard A4 size (297mm x 210mm) paper should be used for preparing the report
. The report should be printed on a good quality white paper (20-40 lb bond).

(b) Complete project work report will be typed in English using MS Word.

(c) Table and figures should conform to the margin specifications (i.e. inline with the
text). Large size figures should be photographically or otherwise reduced to the
appropriate size before insertion.

(2) For copying and binding purposes-

(a) The margins of every page of the report should be follows:

Top:- 1” Bottom:- 1” Right 1” Left:- 1.5”


(b) To ensure that the margins are correct:

Header: - 0.5” Footer: - 0.5”

(c) All the data /text should fit within the above specified margin
requirements (including tables, figures, graphs etc.) Full paper points of
diagrams/images should confirm to the sure margins as specified above.

[MCA DEPARTMENT, SRMCEM, LUCKNOW]


(d) Right Header : project Title (In Italicized Font)

(e) Left Footer: Name of Deptt, College.

[E.g.: MCA DEPARTMENT,SRMCEM, Lucknow]

(f) Right Footer: page No.

(3) Other specifications will be as under-


(a) Font type -Times New Roman
(b) Chapter Headings
-Center/Right Aligned, Bold and Underlined with
Font size 18-20.

(c) Sub Heading -Bold & Font size 14-16 (may be underlined if

required)

(d) Contents -Font size 12

(e) Paragraphs -Justified

(f) Line spacing -11/2


(g) Single line spacing should be used for typing: Long Tables; References.

(h) Foot notes /contents within header/footer can be 9 or 10 point size.(i.e.should be less

than normal text).

(i) The Title of the project should be in ‘Title Case’ or ‘All Caps’.
(j) The Title of all the entries in the ‘Table of Contents’ should be in Title Case.

[III] NUMBERING INSTRUCTIONS

(a) All the page numbers (whether it is Roman or Arabic number) should be typed without
punctuation in sequence. The preliminary page of the report (such as Title page,
Acknowledgement, Table of Contents etc.) should be numbered in lower case Roman
Numerals. The title page will be numbered as (i) but this should not be typed. The page
immediately following the title page shall be numbered (ii) and it should appear at the
right hand corner in the footer as already specified. Pages of main text, starting with
chapter 1 should be consecutively numbered using Arabic numerals. Please ensure that
there are no missing, blank, or duplicate pages.
(b) Minimum font size is 10-point for page nos. and should be kept consistent throughout
the text.
(c) Equations appearing in each chapter or Appendix should be numbered serially; the
numbering commencing a fresh for each chapter or appendix. All the equations can be

[MCA DEPARTMENT, SRMCEM, LUCKNOW]


either center or left aligned. However, this should be followed consistently throughout
the text.
(d) Tables and Figures appearing anywhere in the project should bear appropriate numbers.
The rule of assigning such numbers is illustrated through an example.
Eg:-If a figure in Chapter 3 happens to be the fourth then assign Figure 3.4. Identical
rules apply for tables except that the ‘word’ ‘figure’ is replace by the word ‘table’. If
figures (or tables) appear in appendices then figure 3 in Appendix 2 will be designated
as figure A2.3

[IV] TABLES & FIGURES

The term ‘Table’ is meant for tabulated numerical data in the body of the report as well
as in the appendices. All other non- verbal material used in the body of the report and appendices
such as charts, maps, photographs and diagrams may be designated as ‘figures’.

(a) A ‘Table’ or a’ Figure’ including their caption should be accommodated within the
prescribed margin limits. It should appear on the page following the text where their
first reference has been made.

(b) Tables and Figures on half or less in length may appear on the same page along with
the text. However, they should be separated from the text both above and below by
appropriate spacing.

(c) Two or more small tables or figures may be grouped if necessary, in a single page.

(d) Unless colors are significant; Figures, Images are Tables should be printed on gray
scale,

(e) The Figure captions are always appended at the bottom of the figure, while the Table
caption is included at the top of the table.
[V] MANUSCRIPT PREPARATION

The headings of all items listed under this head should be typed in capital letter without
Punctuation. The page numbering for all items mentioned under (A) & (C) should be done
using lower case Roman Numerals and the pages thereafter under (B) should be numbered
using Arabic Numerals.(from Chapter-1)

The sequence in which the project Report should be arranged and bound should be as
follows-

Preliminary pages (to be numbered with lower case Roman Numerals)

Cove page (Must be printed on front Hard bound cover)

[MCA DEPARTMENT, SRMCEM, LUCKNOW]


Title page (From Title page your project report will start.)

Certificate (Project Completion certificate of Company)

Certificate (Project Completion certificate of College)

Acknowledgement

Preface

Table of Contents
Table of Contents

S No. Topics Page No.


1 Title of the project
2 Introduction
3 Aims & Objective
4 Project Category

5 Requirement Analysis
Hardware Requirement
Software Requirement

6 (i) Problem Definition


(ii) Project Planning & Project Scheduling
7 Scope of Solution
8 Modules Description

9 Analysis Diagrams
(i) Data Flow Diagrams
(ii) ER Diagram
10 Database Structure
11 System Security & Maintenance
12 Future Scope of the Project
13 Bibliography

(A) Appendices [Continuation of lower case Roman Numerals from (A)]


List of Figures

[MCA DEPARTMENT, SRMCEM, LUCKNOW]


List of Tables
List of Abbreviations and symbols Used
Publications /Awards (optional) (If Applicable)
Glossary (optional)
References & Bibliography
• Cover / title page: The first page of the report is the cover page; and the print
out of this should be taken on glossy paper (refer format in Appendix ‘A’).
• Certificate: The certificate shall be typed in double line spacing using font
style times new roman, size 14 (refer format in Appendix ‘B’). The certificate
should bear original signatures of project guide and HOD appended with the
HODs stamp and the Department seal.(please ensure that HODs stamp and
Department’s seal are available in department)
• Declaration: This should be written as per the format mentioned in Appendix
‘C’ it should be signed in original by all the students (project team members).
• Acknowledgement: The acknowledgement shall be brief and should not
exceed on page. The students’ signature shall be made at the bottom of the page
(above their name typed n capital).Over here the students can acknowledge the
help and guidance received from different persons.
• Preface: The first paragraph of the preface should give a brief introduction to
the work and the subsequent paragraphs should cover the overview of how the
material is structured and covered chapter-wise in the body of the project
report.
• Problem Statement: This is the most important part of the project report. It
should be a distillation of the entire work -a concise description of the problem
addressed, methodology used to solve it along with obtained results and the
conclusions drawn. It should be always written in third persons’ language and
not exceeding on page.
• Introduction: The introduction should detail out the actual overview to the
project. This should cover the identification of need, preliminary investigation
and feasibility study. This study (feasibility) includes the technical, economical
as well as operational feasibility.
• Proposed methodology: This chapter should cover the following heads as
applicable-
(a) Formulation & presentation of problem: This should cover the problem
definition along with its aims and objectives.
(b) Solution Approach: This should detail the propose path of solution of the
problem. The complete block diagram (supported with flow diagrams) of
the project should be given and explanation should be mentioned block-
wise in detail it should detail out the entire methodology used.
(c) Software/Hardware requirements and specifications: Depending upon
whether the project is a hardware model/software model of both the basic

[MCA DEPARTMENT, SRMCEM, LUCKNOW]


requirements and specifications for the hardware/software setup should be
given for the implementation of the problem. (Other necessary details such
as various parameters used during the course etc. can be appended.)
Software models may also include the ‘Software Engineering paradigm’
applied.
(d) Implementation (Design & Coding).
(i) The implementation part covers the modular description of the
entire work as how the work has been classified and worked out
under different modules so as to fulfill the objective. Detailed
explanation of each module is required. It gives a complete idea of
how the proposed design methodology works.
(ii) Module description in case of hardware projects should be
supported by circuit diagrams and their operational explanations.
This should be followed by the details of Module Assembly;
Demonstration; List of Components; Complete Circuit Diagrams;
Designing Procedure and the images of entire Hardware layout.
(iii) In case of software projects the software design approach and the
choice of platform should be highlighted. Module description
covers the working of each module along with its
algorithm/flowchart followed by the source code of the particular
sub-routine/function. If the coding part is very lengthy; a print out
of the source code should be annexed in the appendices. It should
also contain User’s manual/Help file.(To be customized as per the
individual projects requirement).
(iv) Sequence Architecture, ER Diagrams, and Database schematic
Diagrams etc.
Result Analysis and Discussion-
(a) Testing (Inputs/Outputs, test data or Validation Checks):
(i) In case of Hardware projects this is supported by Input/output
waveforms as various stages or bit sets given at inputs and
corresponding outputs. For software projects qualitative and
quantitative analysis of the proposed algorithms should be done.
(ii) Initial set points, threshold values should be highlighted and
screen shots/clippings of test data should be attached showing
inputs given and the corresponding outputs.
(iii) Any other obtained result, can be presented in the form of
figures of tables as applicable. This can contain comparative
analysis of the results obtained from the proposed as well as
existing methods.
(b) Inferences: This should contain the inferences/logical findings
drawn on the results obtained from the current proposed technique.

[MCA DEPARTMENT, SRMCEM, LUCKNOW]


(c) Advantages & Applications/Limitations of the projects this should
cover the various merits and demerits of the project. The advantages
should be associated and elaborate as applications.
• Conclusion: This covers the various set of conclusions that are
derives at the end of the work.
• Future scope of the project: The limitations (discussed
previously) serve as a source for the future improvements/ updating
of the project. Enhancements done. In exceptional cases, chapters on
conclusion and future scope can be combined together.
• Appendices: Appendices are provided to give supplementary
information, which if included in the main text may serve as a
distraction to the central theme under discussion. Appendices
should be numbered using Arabic numerals, e.g. Appendix 1,
Appendix 2, etc. Mathematical Relationships, Tables, Figures and
References appearing in appendices should be numbered and
referred to appropriate places just as in the case of chapters. This
should cover the Glossary; List of abbreviations (optional); List of
Tables & List of Figures (refer format in Appendix ‘D’); List of
symbols (if any); Data sheets of various ICs used. If the source code
is lengthy, font size may be reduced to 9 to 10 and can be also
attached as a part of appendix.
• References & Bibliography: The format for writing
‘Bibliography’ & ‘References’ should be followed as per the
instructions given earlier. The listing should be listed in the order
of appendices in the body of the text. Reference should be written
as pre standard IEEE pattern (refer format in Appendix ‘E’). Typing font
size should be 10 or 11 (Times new roman). The extracted text from the
sources should be indexed in the body of the project report serially, i.e.
the reference numbers should be included within the body of the report.
• Except for the standard formats; it is not mandatory to stick
exactly to the headings stated above. The idea and the content
should be the same while the chapter headings may vary. The other
concerned details (in exceptional cases) should be appended or
updated as per the requirements specific to a particular project
work.

[MCA DEPARTMENT, SRMCEM, LUCKNOW]


A
Mini Project Report
On

FEES MANAGEMENT SYSTEM


Submitted in partial fulfillment of the
requirements for the award of the
degree of
MASTER OF COMPUTER APPLICATION
2023-24(Odd Semester)

By

[Manish Nishad]
[Roll.No:2201220140046]
Under the Guidance
Of
[Khushnuma ashraf]

SHRI RAMSWAROOP MEMORIAL COLLEGE OF


ENGINEERING &MANAGEMENT, LUCKNOW

Affiliated to
Dr. A.P.J. ABDUL KALAM TECHNICAL UNIVERSITY,
LUCKNOW, UTTAR PRADESH,

[MCA DEPARTMENT, SRMCEM, LUCKNOW]


SHRI RAMSWAROOP MEMORIAL COLLEGE OF
ENGINEERING &MANAGEMENT, LUCKNOW
DEPARTMENT OF
MCA

CERTIFICATE

[GUIDE NAME] [NAME OF HOD]


PROJECT COORDINATOR, MCA HOD, MCA

[MCA DEPARTMENT, SRMCEM, LUCKNOW]


SHRI RAMSWAROOP MEMORIAL COLLEGE OF
ENGINEERING &MANAGEMENT, LUCKNOW

DECLARATION

I hereby declare that the work, which is being presented in Project, entitled Fees
management system in partial fulfillment for the award of Degree of Master of
Computer Application and submitted to the Department of
Ramswaroop Memorial College of engineering & management, Lucknow is a record of my
own developed under the guidance of Khushnuma Ashraf, lecturer.
I have not submitted the matter presented in this report anywhere for the award of any other
work.

[MANISH NISHAD]
[2201220140046]

[MCA DEPARTMENT, SRMCEM, LUCKNOW]


SHRI RAMSWAROOP MEMORIAL COLLEGE OF
ENGINEERING &MANAGEMENT, LUCKNOW

ACKNOWLEDGEMENT

The project report on FEES MANAGEMENT SYSTEM is an outcome of guidance, moral


support and devotion bestowed on me through my work. For this let me acknowledge and
express our performance sense of gratitude and thanks to everybody who have been source
of inspiration during the project preparation.

First and foremost, I offer my sincere phrases of thanks with innate humility to Dr. Qaim
Mehdi Rizvi (H.O.D) Ramswaroop Memorial College of engineering & management,
Lucknow and my project guide for providing help whenever needed.
The consistence guidance and support provided by Mrs. Khushnuma Ashraf lecturer,
Ramswaroop Memorial College of engineering & management, Lucknow. So, we are very
thankful to acknowledge for key role played by him in providing me with his precious ideas,
suggestion and help that enabled in shaping project work.
If I can say in words, I must at the outset tender my intimate and receipt of affectionate care
to Ramswaroop Memorial College of engineering & management, Lucknow for providing
such stimulating atmosphere & work environment.
I acknowledge here our debt to those who contributed significantly to one or more steps.
I take full responsibility for any remaining sins of omission and commission.

[MANISH NISHAD]
[2201220140046]
[MCA DEPARTMENT, SRMCEM, LUCKNOW]
SHRI RAMSWAROOP MEMORIAL COLLEGE OF
ENGINEERING &MANAGEMENT, LUCKNOW

[MCA DEPARTMENT, SRMCEM, LUCKNOW]


SHRI RAMSWAROOP MEMORIAL COLLEGE OF
ENGINEERING &MANAGEMENT, LUCKNOW

PREFACE

[MCA DEPARTMENT, SRMCEM, LUCKNOW]

You might also like