0% found this document useful (1 vote)
577 views

Mca Project

This document provides guidelines and requirements for submitting a project report for the Master of Computer Application degree at Kalinga Institute of Industrial Technology. It includes an example table of contents for a project report covering topics like introduction, system analysis, system design, coding, testing, security, and future work. The guidelines specify the project report should be around 100 pages and include details of the analysis, design, coding, testing, and implementation done for the project. It provides examples of diagrams and documents that could be included. The important dates specified are April 19-20, 2017 for report submission and viva voce.

Uploaded by

Rahul yadav
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (1 vote)
577 views

Mca Project

This document provides guidelines and requirements for submitting a project report for the Master of Computer Application degree at Kalinga Institute of Industrial Technology. It includes an example table of contents for a project report covering topics like introduction, system analysis, system design, coding, testing, security, and future work. The guidelines specify the project report should be around 100 pages and include details of the analysis, design, coding, testing, and implementation done for the project. It provides examples of diagrams and documents that could be included. The important dates specified are April 19-20, 2017 for report submission and viva voce.

Uploaded by

Rahul yadav
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

KSCA WEBSITE Name/Title of

the Project
(www.ksca.ac.in)

Project submitted in partial fulfilment for the award of the degree of


Master of Computer Application

Submitted by
Prasun Kumar (770083) Name(s) of the Student
with Roll-Number(s)
Rahul Raj (775666)

Under the Guidance of


Name(s) of the Guide
Dr. Ram Prasad Mishra with Designation
Project Manager, Infosys

School of Computer Applications


Kalinga Institute of Industrial Technology
[Deemed to be University]
May 2019

<CERTIFICATE (see the format below) FROM THE ORGANIZATION WHERE

YOU ARE DOING THE PROJECT WILL NEED TO BE ON THIS PAGE IN THE

ORGANIZATION’S LETTER HEAD, SIGNED BY THE PROJECT GUIDE OR THE

HEAD >

CERTIFICATE OF ORIGINALITY

This is to certify that the project report entitled __________________________________


submitted to School of Computer Application, KIIT University in partial fulfilment of the
requirement for the award of the degree of MASTER OF COMPUTER APPLICATIONS
(MCA) , is an authentic and original work carried out by Mr. /
Ms.___________________________________ with Roll no. _______________________and
Regd. No. ...........................under my guidance.

The matter embodied in this project is genuine work done by the student and has not been
submitted whether to this University or to any other University / Institute for the fulfilment of the
requirements of any course of study.

………………………. ...…………………….

Signature of the Student: Signature of the Guide

Date: ……………….. Date:


…………………
Name,
Designation

School of Computer Application


KIIT University, Bhubaneswar

CERTIFICATE

This is to certify that the project work entitled ........................................ Submitted

by (NAME)................. bearing roll no. .............. , is an authentic and original work.

Signature Signature

(Internal Examiner) (External Examiner)

Date.................. Date..................
DECLARATION

I , Student name, roll no do hereby declare that the project report entitled

_______________________________ submitted to School of Computer Application, KIIT

University, Bhubaneswar for the award of the degree of MASTER OF COMPUTER

APPLICATION (MCA) , is an authentic and original work carried out by me from 1st Jan 2011

to 1st May 2011 (Mention your starting date and completion date as par the date mentioned by you

in synopsis) at Organization name under the guidance of External Guide Name and Internal

Guide Name.

Signature of the student

Date..................
ACKNOWLEDGEMENT

Date Signature of the student


Place Name of the student
Roll_no:
Table of Contents
S.No. CONTENTS PAGE No.
1. Chapter-1 Name 01
1.1 aaa 01
1.2 bbbbb 01
1.3 ccccc 01
1.4 ddddd 01
2. Chapter-2 Name 02
2.1 aaaa 02
2.2 bbbb 03
2.3 ccccc 04
2.3.1 caaaa 05
2.3.2 cbbbbb 05

<< Scroll Down to see the Guidelines and


Important Dates>>
Project documentation guidelines:
1. The project documentation should be approximately around 100 pages (excluding
coding).
2. The project documentation should not be too generic in nature. The project report
documentation should include the analysis, design, coding, use of testing techniques /
strategies, etc., that you have done for developing your project.
Note: Do not write the textbook description of the above. You are required to mention how
you have implemented the above in your project.

3. The project documentation should include the topics given below. Each and every
component shown below carries certain weight age in the project report evaluation.
 Table of Contents / Index with page numbering
 Introduction / Objectives / Scope
 System Analysis
 Identification of Need
 Feasibility Study
 Software requirement specifications (SRS)
 Software Engineering Paradigm applied
 Data model, Control Flow diagrams, State Diagrams/Sequence diagrams ERD’s/
Class Diagrams/CRC Models/Collaboration Diagrams/Use-case
Diagrams/Activity Diagrams depending upon your project requirements
 System Design
 Modularisation details
 Data integrity and constraints
 Database design/Procedural Design/Object Oriented Design
 User Interface Design
 Coding
 Comments and Description
 Standardization of the coding /Code Efficiency
 Error handling
 Parameters calling/passing
 Validation checks
 Testing
 Testing techniques and Testing strategies used along with the test case designs
and test reports
 Debugging and Code improvement
 System Security measures (Implementation of security for the project developed)
 Database/data security
 Creation of User profiles and access rights
 Reports and screen (sample screenshots should be included)
 Future scope and further enhancement of the Project
 Assumptions
 Bibliography / references
 Appendices (if any)
 Glossary.
 Should attach a copy of the CD containing the executable file(s) of the complete
project. In case the student is pursuing a live project and is unable to provide the
actual code due to the organization’s non disclosure agreement, the student needs
to get a letter stating the same from his project head. However the student in any
case will have to show the demo of the application by either remote access to the
server or any other means as per the convenience.

4. The project report should normally be printed with single line spacing on A4 paper (one
side only). All the pages, tables and figures must be numbered. Tables and figures should
contain titles.

5. Only one copy of the original project report per student in the bound form of the project
is to be submitted to the SCA, KIIT UNIV. One photocopy of the same Project Report and
the CD containing the executable file(s) must be retained by each student, which should be
produced before the examiner at the time of viva-voce.

Important Dates

Submission of Project Report: 19th and 20th


April’ 2017
(Two copies) in Hard bound form
(Not spiral bound)

Project Viva-Voce: 19th and 20th April 2017.

You might also like