MANUAL FOR PREPARATION OF PROJECT REPORT

1. GENERAL :
The project report should be in an organized and scholarly fashion, an account of
original project work of the candidate leading to the discovery of new facts or
techniques or correlation of facts already known

2. NUMBER OF COPIES TO BE SUBMITTED:

Students should submit four copies to the Principal on or before the specified
date. The Principal should send (i) One copy to the University. (ii) One copy to
the Department library (iii) one copy to the internal/ external examiner and (iv)
One copy to the student concerned.

3. ARRANGEMENT OF CONTENTS OF PROJECT REPORT:

The sequence in which the project report material should be arranged and bound
should be as follows:

1. Title page
2. Bonafide Certificate ( format enclosed)
3. Project Completion certificate from project manager
4. Declaration
5. Acknowledgement
6. Abstract
7. Table of Contents
I. Introduction
1.1 Background
1.2 Objectives
1.3 Purposes scope and Applicability
1.3.1 Purpose
1.3.2 Scope
1.3.3 Applicability
1.4 Achievements
1.5 Organisation of Reports

II. Survey of Technologies

About the Technology

III. Requirements and Analysis

III.1 Problem Definition
III.2 Requirements specifications
III.3 Planning and scheduling
III.4 Software and Hardware requirements
 III.5 Preliminary Product Description
III.6 Conceptual Models.

IV. System Design

IV.1 Basic Modules
IV.2 Data Design
IV.2.1 Schema Design
IV.2.2 Data Integrity and constraints

IV.3 User Interface design

IV.4 List of tables(if any)*
IV.5 List of figures (if any)*
IV.6 Security issues
IV.7 Test cases Design

V. Implementation and Testing

V.1 Implementation Approaches
V.2 Coding details and code Efficiency
5.2.1 Code Efficiency
V.3 Testing approach
V.3.1 Unit testing
V.3.2 Integrated testing

V.4 Modification and Improvements

VI. Results and Discussions

VI.1 Test reports

VI.2 Use documentation

VII. Conclusions

VII.1 Conclusion
VII.2 Limitation of the system
VII.3 Future scope of the project

VIII. List of Symbols, Abbreviations

IX. References and Bibliography
X. Appendix

*The Tables and Figures shall be introduced in the appropriate places.

Explanation of Contents
Certificate of authenticated work

Sample format of certificate of authenticated work

Acknowledgements

CHAPTER I

INTRODUCTION
Background: A description of the background and context of the project and its
relation to work already done in the area.

Objectives: Concise statements of the aims and objectives o fthe project. Define
exactly what you are going to go in the project; the objectives should be about
30/40 words

Purpose, scope and applicability:

Purpose: description of the topic of project and explain its significance

and theoretical framework.

Scope: Explain the main issues and in direct implications of the work.

Applicability: Explain the direct and indirect implications of the work.

Organization of report: Summarizing the remaining chapters of the project

report

CHAPTER II

SURVEY OF TECHNOLOGIES

Demonstrate the awareness and understanding of available technologies related

topic or project. Give the detail of all related technologies that are necessary to
complete the project.

CHAPTER III

REQUIREMENTS AND ANALYSIS

Problem Definition: Define the problems that are working in the project.
Requirements specification: Define the requirements of the system.

Planning and scheduling: Planning takes the account, rules, known as

constraints which control when certain tasks can or cannot open. Scheduling can
be thought of as determining whether adequate resources are available to carry
out plan. Should show the gatt chart and program Evaluation Review Techniques
(PERT)

Software and hardware requirements:

Hardware requirements: In this section, the equipment, graphics card,

numeric co processor. Disk capacity, Ram capacity etc.

Software requirements: The compiler, testing tools, linker and the

libraries etc.

Preliminary product description: Define the functions and operation of the

application/system that developing as the project.

Conceptual models: Describe the operations that can be performed on the

system, and the allowable sequences of those operations. ie DFS,ER diagrams,
object oriented diagrams, system flow charts etc.

CHAPTER IV

Basic modules: divide the overall problem into more manageable parts and
develop each part or module desperately.

Data design:

Schema design : define the structure and explanations of scheme as used

in your project.
Data Integrity and constraints: Explain all the validity checks and
constraints providing to maintain data integrity

Use interface design: Describe the internal and external components and the
architecture of your interface

Security issues: Real time considerations and security issues related to project

Test cases design: test cases will provide easy detection of errors and mistakes
with in a minimum period of time and with the least effort.
CHAPTER V
IMPLEMENTATION AND TESTING

Implementation approaches: Define the plan of implementation, and the

standards used in implementation

Coding details and code efficiency: Include only the important

codes(Algorithm, applets code, forms code etc. The program should contain
comments needed for explaining the work a piece of code does
Explain the function of the code with a shot of the output screen of that program
code.

Code efficiency : code optimization.

Testing approach: Testing the scheme presented in the system design and
follow some suitable model eg category partition, state machine based

Unit testing: Unit testing deals with testing a unit or modules as a whole.

Integrated testing: Bring all the modules together into a special testing
environment, check the errors, bugs and interoperability

CHAPTER VI

RESULTS AND DISCUSSION

Test Reports : The test results and reports based on the test cases.

User documentation ; explain its different functions, components with screen

shots

CHAPTER VII

CONCLUSIONS

Conclusions; Summarized in short

Limitations of the system: explain the limitations encountered during the testing
of your software.

Future scope of the project describes new areas of investigation prompted by

developments in the project.
REFERENCES

To acknowledge the work of others that used the project or to provide the
essential background of the project.

GLOSSARY

Include acronyms, abbreviations and symbols or uncommon terms in the project

report then their meaning should be explained where they first occur.

APPENCICES

Provide to include further details of results, mathematical derivations, certain

illustrative parts of the program code.(eg. Class interfaces,) User documentation
etc.
Format for Bonafide Certificate

Certified that this project report titledis the

bonafide work of Mr./ Ms.., with Register
Number--------------------------------- at
-----------------------------------------------------------, in partial fulfillment of
the requirement for the award of the degree of Master of Computer
Applications of Calicut University

Internal Guide Principal (MCA)

Internal Examiner: External Examiner: