Department of Computer Application

School of Computer Sciences

Kavayitri Bahinabai Chaudhari North Maharashtra University, Jalgaon
Format for Project Report for MCA

The report should have title page, certificate from director (examiner), certificate from the chief of
company where the training/ project is done, table contents, list of tables, list of figures, list of
special symbols ( if any ) on separate pages. Times new roman font with font size 12 should be
used for the running text. Typing should be done on assuming to be printed on a A4 sized paper.
The report should be submitted as hard bound copy with “BLACK REXINE” and
“GOLDEN EMBOSSING”. You have to prepare Three copies of the report. Two copies to
be submitted at the School and the third copy to be kept with you for your personal use.

The project report should typically consists of 5 to 7 chapters.

Chapter 1 should discuss in brief about the organization where the student is undergoing the
training and may include services offered, clients and products. It should also give a brief
introduction to the project including need and motivation (if applicable), problem definition,
limitation of existing system (If any), objective and scope of the project etc.

The last chapter must be “Concluding Remarks” where the strengths and limitations of the product
developed must be highlighted.

The core chapters (i.e., between the first and last chapter) should include the standard approaches
with the detailed description of the chosen approach for software development starting for system
analysis, feasibility study, proposed system, preliminary design, detailed design, software testing
etc…

After “Concluding remarks”, a detailed list of “References” must be included. The references must
include the Software Manuals referred, the books, research papers, technical reports, data sets
already prepared by others etc.

All appendices should follow after references. The report must include all important parts of
“Software Development Document”. The report must include, as Appendix, a “User Document”
for using the software. The user of the software is expected to be non-Programmer (and in many
cases a person who has only a working knowledge of operating computer).

The listing of all programs developed should be included as separate appendices (if permissible by
the organization). The input and output data for these programs should be included with the listing.
 A

Project Report

on

Title of the Project

at

Name of the Organization/Company

Place
Submitted By:

Name of the Student

to

School of Computer Sciences

Kavayitri Bahinabai Chaudhari North Maharashtra University,
Jalgaon
In the partial fulfillment of the requirement for the award of the degree of
Master of Computer Application
June 2024
 || अंतरी पेटवू ज्ञानज्योत ||

कवयित्री बहिणाबाई चौधरी उत्तर मिाराष्ट्र ववद्िापीठ, जळगाव

संगणकशास्त्त्र प्रशाळा

KAVAYITRI BAHINABAI CHAUDHARI NORTH MAHARASHTRA UNIVERITY, JALGAON

SCHOOL OF COMPUTER SCIENCES

CERTIFICATE

This is to certify that ______________, a final year student of 'Master of Computer

Application' from School of Computer Sciences, Kavayitri Bahinabai Chaudhari North
Maharashtra University, Jalgaon has successfully completed the project entitled (Title of
the Project) as a part of six months full time industrial training during academic year
2023-24.

Head
Department of Computer Application,
School of Computer Sciences,
KBCNMU Jalgaon

External Examiner External Examiner

Post Box No. 80, Umavi Nagar, Jalgaon – 425001 (M.S.) Tel. No: 0257- 2257453
Website: www.nmu.ac.in Email: [email protected]
 (To be printed on the organizations letterhead)

To whomsoever it May Concern

Master/Miss (Your name in full) a student of Department of Computer Application, School

of Computer Sciences, Kavayitri Bahinabai Chaudhari North Maharashtra University, Jalgaon has

undergone INDUSTRIAL TRAINING in this organization for a period of six months from

1/12/2023 to 31/05/2024. During his/her training he/she has completed project work on (Title of

the Project). The matter embodied in this project work has not been submitted earlier for award

of any degree or diploma to the best of my knowledge and belief.

Project Guide/Team Leader etc Signature of the Manager

Signature and Seal Signature and Seal

.
 Acknowledgement (Optional)

Acknowledgements (Optional): This is an optional section which acknowledges the help,

assistance and advice given to the student during his internship and the preparation of his report.
Acknowledgements should be expressed to all concerned members of the company /organization
who has helped during the project work.

Name and Signature of the Student

 Table of Contents
(Should contain Chapter Name, Sub points for each chapter and Page nos)

Title Page
No
1 Introduction 1
1.1 Company Profile ……………………………………………………….. 1
1.1.1 Services Offered ……………………………………………………….. 2
1.1.2 Clients and Products ……………………………………………………….. 3
1.2 Introduction to Company ……………………………………………………….. 4
1.2.1 Need and Motivation ……………………………………………………….. 5
1.2.2 Problem Definition ……………………………………………………….. 6
1.2.3 Objective and Scope ……………………………………………………….. 7
List of tables
List of figures
List of special symbols (if any)
 Chapter 1
Introduction
1.1 Organization Profile
1.1.1 Services Offered
1.1.2 Clients and Products

1.2 Introduction to the Project

1.2.1 Need and Motivation
1.2.2 Problem Definition
1.2.3 Limitation of Existing System (If any)
1.2.4 Objective and Scope
 Chapter 2
System Requirement Analysis
2.1 System Requirement Analysis

2.1.1 Pre Analysis

2.1.2 Situation analysis
2.1.3 Stakeholder analysis
2.1.4 Problem analysis
2.1.5 Needs analysis
2.1.6 SWOT analysis

2.2 Scope of Proposed System

2.3 Technical Specification
 Chapter 3
Feasibility Study
3 Feasibility Study

3.1 Introduction
3.2 Technical Feasibility
3.3 Time Feasibility
3.4 Operational Feasibility
 Chapter 4
Proposed System
4.1 Proposed System
4.2 User Privileges
4.3 Objective of the System
 Chapter 5
Preliminary Design
5 Preliminary Design

5.1 Use Case Diagram

5.2 Sequence Diagram
5.3 Data Flow Diagram
5.4 ER Diagram
 Chapter 6
Detailed Design
6 Detailed Design

6.1 Screen Shots

6.2 Database Design
6.3 Activity Diagram
6.4 Class Diagram
6.5 Deployment Diagram
 Chapter 7
Testing

7 Testing

7.1 Introduction
7.2 Unit Testing
7.3 Integration Testing
7.4 User acceptance Testing
7.5 Test cases

7.5.1 Login Activity

7.5.2 Admin Activity
 Chapter 8
Concluding Remarks
(The last chapter must be “Concluding Remarks” where the strengths and limitations of the
product developed must be highlighted. )

8 Concluding Remarks

8.1 Strengths of System

8.2 Limitations of system
8.3 Scope for future development
8.4 Conclusion
 References
After “Concluding remarks”, a detailed list of “References” must be included. The references
must include the Software Manuals referred, the books, research papers, technical reports, data
sets already prepared by others etc. References should be listed alphabetically, in the same as
the following example.

1. Pfleeger, Shari (2001) Sofwtare Engineering: Theory and Practice, Prentice Hall ,
Upper Saddle River, NJ.
2. Sommerville, Ian (2011) Software Engineering, Addison-Wesley , Boston, MA.
3. Stephens, Rod (2015) Beginning Software Engineering, Wrox.
4. Tsui, Frank , Orlando Karam and Barbara Bernal (2013) Essentials of Software
Engineering, Jones & Bartlett Learning , Sudbury, MA.