FORMAT OF COVER PAGE & FIRST PAGE

A Mini-Project Report on

(Title of the Project)

Submitted in partial fulfillment of requirement

for the V Semester MCA Mini-Project -13MCA58
Under
Visvesvaraya Technological University, Belgaum
Karnataka
By
(Name and Reg.No. of the candidate)
Under the Guidance of
Internal Guides name
Designation
College Address

R. V. COLLEGE OF ENGINEERING
MYSORE ROAD, BENGALURU 560 059
NOV 2016

FORMAT OF SECOND PAGE

COLLEGE CERTIFICATE
R. V. COLLEGE OF ENGINEERING, BENGALURU - 560059
DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS
AFFILIATED TO VISVESVARAYA TECHNOLOGICAL UNIVERSITY, BELAGAVI
APPROVED BY ALL INDIA COUNCIL FOR TECHNICAL EDUCATION, NEW DELHI

NOV 2016

CERTIFICATE
This is to certify that the Mini-project entitled <<name of the project>> submitted in partial
fulfillment of the V sem MCA Mini Project 13MCA58 is a result of the bonafide work carried out by
<<student name and USN No>> during the academic year 2016

Name
Designation
Internal Guide
Department of MCA
R. V. College of Engineering
Bengaluru 560 0 59

Dr. Usha J
Professor and Director
Department of MCA
R.V.College of Engineering
Bengaluru 560 059

UNDERTAKING BY THE STUDENT

I, <<Student Name>>, <<USN>>, hereby declare that the Mini-project <<Project Title>>
is carried out and completed successfully by me and is my original work.

SIGNATURE
(STUDENT NAME)

ACKNOWLEDGEMENT
(IN ORDER OF POSITION)
(The order of acknowledgement should be Internal Guide, external guide (if any), Director of the MCA
department, head of the institution)

[contents]

ii

LIST OF FIGURES
(This page consists of the list of figures with respective title and page numbers existing in the Mini-project
report)

iii

LIST OF TABLES
(This page consists of the list of tables with respective title and page numbers existing in the Miniproject report)

iv

ABSTRACT
Its a one page document consisting of below paragraphs.
First para :
Brief introduction about the Mini project which should include background, Areas /type of applications,
market size (if available) and hence the importance of the domain. Key developments in the domain,
unresolved issues or/and new emerging opportunities in the domain areas and hence the problem or the
issue that is proposed to be addressed in the project or the objective. If it is theory or simulation based
add all the existing theory/algorithms names and what is it that the project is based on, their essentially
advantage or drawbacks in brief and hence the motivation to work on the project.
Second Para :
Methodology of your project including the key theory, design tools or software tools or / and the
experimental tools that will be used, the key specifications including constrains or boundary conditions
or approximations or assumptions that have been considered for the work. The sequence in which the
work is to be carried out.
Third para :
Key findings, results or outcome of the work including experimental data of the out come or / and
percentage in terms of working efficiency of the developed product or system.
(No need to quote any references for this. )

INDEX

Undertaking by the student

Acknowledgement
List of Figures
List of Tables
Abstract

i
ii
iii
iv
v

Chapter 1: Preamble
Page No
1.1 Brief Description/Explanation about the project Concept: [200 words].
Before any subsections in the introductory chapter there should at least one paragraph
giving a broad introduction to the topic.
It should have at least a five references reviews /whitepapers, including mandatorily
some reference published in the year of the submission of the Project Report (namely
2013)
1.2State of Art developments in the relevant domain
1.3Literature Review / Survey ( One page Only)
- Write a literature survey of references with respect to the complete project
work.
- For every survey reference write explanation for the outcome of the reference
related to the project.
- The references could be books/technical papers/web portals/manuals (students
are required to write the complete path of the reference).
- Literature survey cannot be some text information.
1.4Unresolved Issues and Emerging Opportunities or new directions
1.5Motivation
1.6Main objective or problem statement & Scope of the project
1.61. Objective or Problem Statement
1.62. Features of the project
(5-10 identified unique technical features of the project)
1.7 Methodology in brief
1.7.1 Platform / Tools used in implementing the project
1.8 Dissertation / Report Organization
(Chapter wise brief explanation starting from Chapter 2 onwards)

Chapter 2: Project Description

Page No

Theory and Concept relevant to the project including details of process technology,/
experimental principles/ analytical models/ numerical models/ type of algorithms etc as the case
may, to be defined by the Guide
Chapter 3 : Methodology
Methodology specific to the Mini project - Software / System /Hardware Requirement
Specifications / requirement specification Project Methodology (Opening statement shall
be written)
Flow chart Mandatory (governing equations, Standards, Assumptions, Boundary
Condition, Specifications, Tools, Techniques,)
Brief description about the Hardware and Software specifications / Platform and Tools
used
3.1 Introduction
Definitions, Acronyms and Abbreviations
Overview
3.2 General Description
Product Perspective and funcitons
User Characteristics
General Constraints
Assumptions and Dependencies
3.3 Functional Requirement
Introduction
Input
Processing
Output
3.4 External Interfaces Requirements (If applicable )
User Interfaces
Hardware Interface
Software Interface
3.5 Performance Requirements
3.6 Design Constraints
Standard Compliance
Hardware Limitations
3.7Other Requirements (If applicable)

(CHAPTER 4 IS BASED ON OBJECT ORIENTED / PROCEDURAL APPROACH USED IN

THE PROJECT.)

Chapter 4 : Implementation and Design

4.1 Architectural Design
Page No
Problem Specification
Block Diagram
Data definition/Dictionary
Module specification
Assumptions made
4.2System Design
Brief description about three stages of object oriented design such as object
modeling, dynamic modeling and functional modeling
Object Modeling
o Class diagram
Dynamic modeling
o Use case diagram
o Sequence diagram
o Activity diagram
o State machine diagram
Functional Modeling
o Data Flow diagrams
Assumptions made
Note : 2-3 lines of explanation to be given for all the modules / diagrams in this chapter.
The diagrams should be properly numbered and titled.
(For standard notations of the diagrams see the attachment)

Chapter 4: Design Document Specification (FOR PROCEDURAL APPROACH)

4.1 Architectural Design
Page No
Problem Specification
E-R diagram
Data Flow Diagram
Structure charts
Data definitions/Dictionary
Module Specification
o Modules shown in the structure chart are specified
o Module 0
Name of the module
Inputs
Outputs
Sub ordinates
Purpose
(Similar details should be given for all the modules)
Assumptions made
4.2Detailed design
Design decisions : Decisions that are taken regarding the data structures and the
approach to be followed
Logic design: Logic design to be specified in the PDL for each module
Note : 2-3 lines of explanation to be given for all the modules / diagrams in this chapter.
The diagrams should be properly numbered and titled.
(For standard notations of the diagrams see the attachment)

Chapter 5: Testing
(Testing: Do not explain all the testing techniques available in general. Explain
only the testing methods adopted in the respective project).
Explain the test cases clearly for both Pass and Fail cases.

Chapter 6: Results and Discussions

(Include the tested clear output screens shots / Results and explain in sentences)

Chapter 7 : Conclusion and Future Enhancement

Conclusion (should contain the key results/ inference / key conclusions /outcomes in terms of
points and not in the form of tables, graphs etc, nor should it have any references.) & Future
Scope

References
Overall project references to be mentioned with respect to each chapter except Synopsis
and Premable showing the complete path of the reference.
Sample Reference:
1. Honig, M.L., Steiglitz, K., and Gopinath, B.: Multichannel signal processing for data communication in
the presence of crosstalk, IEEE Trans. Communications., 38, (4), pp. 551558, April 1990,
2. F. Axisa, P. M. Schmitt, C. Gehin, G. Delhomme, E. McAdams, and A. Dittmar, Flexible technologies
and smart clothing for citizen medicine, home healthcare, and disease prevention, IEEE Trans. Inf.
Technol. Biomed., vol. 9, no. 3, pp. 325336, 2005.
3. V. Lumelsky, M. Shur, and S. Wagner, Sensitive skin, IEEE Sensors J., vol. 1, no. 1, pp. 4151, Jun.
2001.
4. The International Technology Roadmap for Semiconductors, 2011 ed., Dec. 2012. Available:
http://www.itrs.net/ home.html.
5. A. Krost and A.Dadgar, GaN-based optoelectronics on silicon substrates Mater. Sci. Eng. B, Vol. 93,
no. 13, pp. 7784, May 30, 2002.

TEXT PAGE FORMAT

Title of the Mini project or abbreviated title

Department of MCA, RVCE

Nov 2016

page no

ATTACHMENT Chapter 4
FOR PROCEDURAL ORIENTED APPROACH
Standard Notations ER Diagram

Input /output
Standard Notations Data
Flow Diagram

File /data store

or

Data flow

For process / function

either

Or

FOR OBJECT ORIENTED APPROACH

Standard Notations UML Diagram
Pattern Instance of Command Pattern

Use case Diagram for a switch connected to a light source

Activity Diagram for Switch connected to a light source

Class Diagram for Switch connected to a light Source

Sequence Diagram for Switch connected to a light Source

Communication Diagram for Switch connected to a light Source

State machine diagram for a Switch connected to a light source

General Instruction for Mini Project Report

1. Chapter Main Heading should be centered and bold with Times New Roman 14.
Next level sub chapter headings should be left justified with Times New Roman 13.
Second and any further levels sub headings to be left justified with Times New Roman 11.
2. The text in the chapters should be with Times New Roman 12 with line spacing 1.5 and justified.
Paragraphs should be separated with a tab.
3. Figures should be centered with correct number and titled at the bottom with respect to the chapter.
For example if the figure is from chapter 1, then it is fig 1.1 with the title and further numbering.
4. Tables should be centered with correct number and titled at the bottom with respect to chapter. For
example if the table is from chapter 3, then it is tab 3.1 with the title and further numbering.
5. Number of copies of the report to be prepared: one for the student, one for the department, one to the
university.
6. The report should be soft bound.

Coordinator

Director, MCA