VI SEMESTER MCA PROJECT WORK

GUIDELINES

Dr.M.A.Jayaram
Professor and Head

DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

SIDDAGANGA INSTITUTE OF TECHNOLOGY
TUMKUR-572103
 MCA Project work guidelines

PREAMBLE

This manual provides general guidelines to VI semester MCA project

work. The material presented in this manual will help the students
regarding what is to be presented during the three project seminars
and how the project report is to be written. However, special emphasis
is laid on writing a scientific article in general and project report in
particular. Students are requested to find the time to read this manual
carefully.

The production of a good piece of a project report is as much a part of

the project as doing the experimental work. However excellent and
original a piece of work the project may be, unless the results are
properly communicated to other people, it may as well not have been
done! . Communicating results of an investigation in a clear and useful
way is a key part of science and is the reason for devoting a lot of
effort to this aspect.

It is not necessary, or even desirable to describe every minute detail of

what was done. One of the most important aspects of good technical
writing is to be concise, yet remain informative. The ability to select
what is essential, and to omit what is merely incidental detail, is a skill
every student needs to develop.

While writing a project works, following points are to be borne in mind;

• Make sure you mention the background to, and aim of the work.
• Include the basic concepts and theory relating to the work.
• Describe the procedures used. Identify major sources of error
and explain how they were dealt with.
• Only data directly relevant to the calculation of final results
should be presented, omit raw data. Graphs are a particularly
effective way of presenting results - only use table where it
would make more sense than providing a graph.
• Final results should be presented clearly and concisely; include
an analysis of errors, but omit details of arithmetical
manipulations.
• If computer code was used or written, give details of the checks
and validations you performed on the code.
• The interpretation of the results must be discussed, and
improvements and possible extensions of the work is to be
suggested.

2
 MCA Project work guidelines

• Give references to any books, articles or other sources of

information (e.g. web sites) that have proved useful in preparing
the report, or carrying out the work.

To be acceptable as an MCA project work, your project must conform to the

requirements stipulated by Visvesvaraya Technological University. Additional
requirements are:
• The report should demonstrate an appropriate level of professional
competence in the practical development of a suitable application, tool or
similar work.
• Projects must give a clear description of the life-cycle stages undertaken and
must describe the use of appropriate tools.
• A description of how verification and validation have been applied to each
stage of the project must also be included. [Note the word 'how': you're not
expected to include details like test plans or test results in the body of the
report, although these may be appropriate in appendices.]

Good writing is simple writing

• Writing in a formal style doesn't mean that your report should be hard to read
because it's full of long words and complicated sentences. Concentrate on
getting over the information (facts, reasons) to the reader as clearly as
possible.
• By all means use common technical terms in the field, but avoid unnecessary
jargon or long words, which are just designed to impress. You won't.
• Long and complex sentences should be broken up. The same is true of
paragraphs. (On the other hand, sequences of very short sentences and
paragraphs are irritating.)
• Spelling, punctuation and grammar should be perfect. Use appropriate tools
to check. Spelling checkers are normally good (don't forget to set them to
British English). In my personal experience, the grammar checker in Microsoft
Word is of great use. Try to get someone else to proof read your report:
remember that other people are generally better at spotting your mistakes
than you are.

Plagiarism is cheating by claiming someone else's work as your own. Don't do it!
Consequences can be very severe.
Accusations of plagiarism in a report can always be avoided by quotation and proper
referencing.

3
 MCA Project work guidelines

• You cannot copy and paste any text from any source unless it is quoted to
make it clear that it is copied and not your own words.

• Material, which is quoted, must be referenced in the text, that is there must
be a direct indication in the text of its source, using some standard
convention (e.g. numbers such as [1], or names and dates such as Smith
2001).
• Material which is paraphrased or otherwise directly used must also be
referenced. Where you paraphrase ideas or use re-write material in your own
words, you must still acknowledge the source, e.g. by writing ‘The outline
presented here is based on Smith (1999)’.
• There is a distinction between a list of references at the end of a piece of
work and a bibliography. The list of references gives full details of the
references in the text, whether these are numbers or names/dates. The
bibliography lists sources you consulted that have contributed to the work in a
general way, but which are not specifically referenced in the text. Usually the
list of references should be much longer than the bibliography.
You are not expected to re-invent the wheel; indeed you can legitimately be
penalized for doing so. It's good software engineering practice to re-use code. But
you must make clear which parts of your code are taken from elsewhere and which
are original. Carefully commenting your code can achieve this. You also need to
take precautions against other people copying your project, leading to you being
falsely accused of collusion. If your code and project report are on a networked
machine, make sure the permissions do not allow viewing. Put your name as author
in every Java class/C++ class.

I trust this manual will be a useful reckoner in your hands.

Dr.M.A.Jayaram
Professor and Head
Department of MCA

4
 MCA Project work guidelines

1.INTERNAL EVALUATION

1.1Project Seminars

You are required to present three seminars at various stages of your project
work. The date and time of your presentation will be communicated to you well in
advance. All the faculty of the department will evaluate your project work. The
seminars are crucial in getting good internal marks.

1.2First Seminar:

Weightage: 5 marks.
Duration: 15 minutes.

Content of the seminar:

You are expected to present about the domain (area) you have chosen.
Following are the high spots in your presentation:

• What is the area?

• What is my understanding about the area?
• What am I planning to do?
• What is the background work I have done? (Like literature survey, learning
a programming language or a software package etc,,,,,)
• What are the related works already available as referrals?
• A brief summary.

1.3 Second Seminar:

Weightage: 10 marks.
Duration: 15 minutes.

Content of the seminar:

5
 MCA Project work guidelines

You are expected to include the following in your presentation in the second
seminar;

• How the implementation of the project is planned?

• The Components/ Modules of the Project.
• ER and Data flow diagrams (in case of DBMS oriented projects).
• Data Structures to be used (in case of a non-DBMS oriented projects)
• A brief summary.

1.4 Third Seminar

Weightage: 10 marks.
Duration: 15 minutes.

Content of the seminar:

You are expected to include the following in your presentation in the third
seminar;

• The Demo along with brief explanation.

• If live demo is not possible, screen snap shots showing all the sessions
with the software developed.
• Briefing on tests/validations conducted.
• A brief summary.

Internal Evaluation Break-Up

Particulars Marks
1.Seminar-I 05
2.Seminar-II 10
3.Seminar-III 10
4.Report 25
Maximum Marks: 50

2. EVALUATION BY UNIVERSITY

2.1 Evaluation of the project report/dissertation

At the university level, the project report gets evaluated for 125 marks. The
project report undergoes double evaluation i.e., by the respective guide and by

6
 MCA Project work guidelines

the external examiner designated by the University. The parameters that are
seen during the evaluation are;

2.2 Evaluation through viva-voce

An external examiner and internal examiner both designated by the university will
conduct viva-voce and the student will be evaluated for 75 marks. The candidate
will be examined for the extent of the work done, originality, usefulness and
relevance.

3. DETAILS OF SUBMISSION

The number of reports to be prepared is at least FOUR.

• One to be submitted to the office of the Principal.

• One to the Department.
• One to the Concerned Guide(s)
• One to the candidate.

It is required to submit the reports well within the date specified by VTU. The
students, who fail to submit within the last date given, will be permitted to submit
dissertation reports later during the next subsequent semester examinations
only. Normally the last date for submission will be placed somewhere during
second or third week of June.

4. PROJECT REPORT

4.1 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
3. Abstract
4. Acknowledgement
5. Table of Contents
6. List of Tables
7. List of Figures
8. List of Symbols, Abbreviations or Nomenclature (Optional)

7
 MCA Project work guidelines

9. Chapters
10. Appendices
11. References

4.2 PAGE DIMENSIONS AND MARGIN

The dimensions of the final bound copies of the project report should be 290mm
x 205mm. Standard A4 size (297mm x 210mm) paper may be used for preparing
the copies.

The final five copies of the project report (at the time of submission) should have
the following page margins:

Top Margin: 30 mm
Bottom edge: 30 mm
Left side: 35 mm
Right side: 25 mm

The project report should be prepared on good quality white paper preferably not
lower than 80 Gms /Sq. Meter.

Tables and figures should conform to the margin specifications. Large size
figures should be photographically or otherwise reduced to the appropriate size
before insertion.

4.3 MANUSCRIPT PREPARATION

The student shall supply a typed copy of the manuscript to the guide for the
purpose of approval. In the preparation of the manuscript, care should be taken

8
 MCA Project work guidelines

to ensure that all textual matter is typed to the extent possible in the same format
as may be required for the final project report.

Hence, some of the information required for the final typing of the project report is
also included in this section.

4.3.1 Title page – A specimen copy of the title page for project report is given in
Appendix 1.

Bonafide Certificate – A sample certificate is appended in appendix-II

4.3.3 Abstract – Abstract should be an essay type of narrative not exceeding

two pages, outlining the problem, the methodology used for tackling it and a
summary of the findings. The abstract should be spaced at 11/2 line spacing.
Sample abstracts are appended in Appendix-1

4.3.4 Acknowledgement – It should be brief and should not exceed one page
when typed double spacing.

4.3.5 Table of contents – The table of contents should list all material following
it as well as any material which precedes it. The title page, bonafide Certificate
and acknowledgement will not find a place among the items listed in the table of
contents but the page numbers of which are in lower case Roman letters. One
and a half spacing should be adopted for typing the matter under this head.

4.3.6 List of Tables – The list should use exactly the same captions as they
appear above the tables in the text. One and a half spacing should be adopted
for typing the matter under this head.

9
 MCA Project work guidelines

4.3.7 List of Figures – The list should use exactly the same captions as they
appear below the figures in the text. One and a half spacing should be adopted
for typing the matter under this head.

4.3.8 List of Symbols, Abbreviations and Nomenclature – One and a half

spacing should be adopted for typing the matter under this head. Standard
symbols, abbreviations etc. should be used.

4.3.9 Chapters – The chapters may be broadly divided into 3 parts (i)
Introductory chapter, (ii) Chapters developing the main theme of the project
report, (iii) Results, Discussion and Conclusion.

The main text will be divided into several chapters and each chapter may be
further divided into several divisions and sub-division.

Each chapter should be given an appropriate title.

Tables and figures in a chapter should be placed in the immediate vicinity of the
reference where they are cited.
Footnotes should be used sparingly. They should be typed single space and
placed directly underneath in the very same page which refers to the material
they annotate.

4.3.10 Appendices – Appendices are provided to give supplementary

information, which if included in the main text may serve as a distraction and
cloud the central theme under discussion.

Appendices should be numbered using Arabic numerals, e.g. Appendix 1,

Appendix 2, etc.

Appendices, Tables and References appearing in appendices should be

numbered and referred to at appropriate places just as in the case of chapters.

10
 MCA Project work guidelines

4.3.11 List of References – Any work of other researcher is used either directly
or indirectly. The origin of the material thus referred to at appropriate places in
the project report should be indicated. A paper, a monograph or a book may be
designated by the name of the first author followed by the year of publication,
placed inside brackets at the appropriate places in the project report should be
indicated. The citation may be written in any one of the following forms.

4.3.12 Examples of citation

An improved algorithm has been adopted in literature [Tsychiya 1980]
An elaborate discussion on this topic is found in the reference [Tenonbam, 2004]
The problem of high dimensional problem space is often referred to as curse of
dimensionality [Goldberg, 2001].

The listed should be typed 4 spaces below the heading “REFERENCES” in

alphabetical order in single spacing left justified. The reference material should
be listed in the alphabetical order of the first author. The name of the
author/authors should be immediately followed by the year and other details. A
typical illustrative list given below relates to the citation examples quoted above.

4.3.13 References
Book: (Author(s) name(s), Title of the Book, Publisher, Place, Year)

1. Eberhart R.C., Simpson P.K., Dobbins RW. : Computational Intelligence PC

Tools, Academic Press Professional, Boston (1996).

Paper in a Journal: (Author(s), Title of the paper, Journal, Volume (issue), year,
Page to page)

2. Fogel D.B.: An Introduction to Simulated Evolutionary Optimization, IEEE

Trans. Neural Networks, 5(1), 1994, 3-1.

11
 MCA Project work guidelines

Web Site

3. http://engr.iupui.edu/~shi/Conference/psopap4.html/

4.3.14 Tables and Figures – By the word Table, is meant tabulated data in the
body of the project report as well as in the appendices. All other material used in
the body of the project report and appendices such as charts, graphs, maps,
photographs, and screen snap shots and diagrams may be designated as
figures.

A table or figure including caption should be accommodated within the prescribed

margin limits. The caption should be typed on the top of the body of table. All the
tables should be numbered in the sequence they appear in a particular chapter.
Table 1.2 means, second table in first chapter. Similarly, figures

Tables and figures on half page 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 triple spacing.

Two or more small tables or figures may be grouped if necessary in a single

page.

Photographs and screen snap shots should be included in the colour Xerox form
only. More than one photograph can be included in a page.

5 GUIDELINES FOR TYPING

5.1 General
This section includes additional information for final typing of the project report.
Some information given earlier under ‘Manuscript preparation’ shall also be
referred.

12
 MCA Project work guidelines

• The impressions on the typed copies should be black in colour.

• Uniformity in the font of letters in the same project report shall be
observed.
• A sub-heading at the bottom of a page must have at least two full lines
below it or else it should be carried over to the next page.
• The last word of any page should not be split using a hyphen.
• One and a half spacing should be used for typing the general text.
• Single spacing should be used for typing:
o Long Tables
o Long quotations
o Footnotes
o Multiline captions
o References

• All quotations exceeding one line should be typed in an

indented space – the indentation being 15mm from either margin.

• Double spacing should be used for typing the Bonafide

Certificate and Acknowledgement.

5.2 Chapters
The format for typing chapter headings, divisions’ headings and sub division
headings are explained through the following illustrative examples.

Chapter heading: CHAPTER 1

Division heading: INTRODUCTION

Division heading: 1.1 OUTLINE OF PROJECT REPORT

Sub-division heading: 1.1.2. Literature survey.

The word CHAPTER without punctuation should be centered 50mm down from
the top of the page. Two spaces below, the title of the chapter should be typed

13
 MCA Project work guidelines

centrally in capital letters. The text should commence 4 spaces below this title,
the first letter of the text starting 20mm, inside from the left hand margin.

The division and sub-division captions along with their numberings should be left
justified. The typed material directly below division or sub-division heading should
commence 2 spaces below it.

6. TYPING INSTRUCTIONS

6.1 General
This section includes additional information for final typing of the project report.
Some information given earlier under ‘Manuscript preparation’ shall also be
referred.

The impressions on the typed copies should be black in colour.

Uniformity in the font of letters in the same project report shall be observed.

A sub-heading at the bottom of a page must have atleast two full lines below it or
else it should be carried over to the next page.

The last word of any page should not be split using a hyphen.

One and a half spacing should be used for typing the general text.

Single spacing should be used for typing:

Long Tables
Long quotations
Foot notes
Multiline captions
References

All quotations exceeding one line should be typed in an indented space – the
indentation being 15mm from either margin.
Double spacing should be used for typing the Bonafide Certificate and
Acknowledgement.

6.2 Chapters

14
 MCA Project work guidelines

The format for typing chapter headings, divisions’ headings and sub division
headings are explained through the following illustrative examples.

Chapter heading : CHAPTER 1

Division heading INTRODUCTION

Division heading : 1.1 OUTLINE OF PROJECT REPORT

Sub-division heading : 1.1.2. Literature review.

The word CHAPTER without punctuation should be centered 50mm down from
the top of the page. Two spaces below, the title of the chapter should be typed
centrally in capital letters. The text should commence 4 spaces below this title,
the first letter of the text starting 20mm, inside from the left hand margin.

The division and sub-division captions along with their numberings should be left
justified. The typed material directly below division or sub-division heading should
commence 2 spaces below it and should be offset 20mm from the left hand
margin. Within a division or sub-division, paragraphs are permitted. Even
paragraph should commence 3 spaces below the last line of the preceding
paragraph, the first letter in the paragraph being offset from the left hand margin
by 20mm.

7. GUIDELINES FOR NUMBERING

7.1 Page Numbering
All pages numbers (whether it be in Roman or Arabic numbers) should be typed
without punctuation on the bottom right hand corner. The preliminary pages of
the project 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), the page immediately following the title page shall be numbered
(ii) and it should appear at the bottom right hand corner as already specified.

15
 MCA Project work guidelines

Pages of main text, starting with Chapter 1 should be consecutively numbered

using Arabic numerals.

7.2 Numbering of Chapters, Divisions and Sub-Divisions

The numbering of chapters, divisions and sub-divisions should be done, using
Arabic numerals only and further decimal notation should be used for numbering
the divisions and sub-divisions within a chapter. For example, sub-division 4
under division 3 belonging to chapter 2 should be numbered as 2.3.4. The
caption for the sub-division should immediately follow the number assigned to it.

Every chapter beginning with the first chapter should be serially numbered using
Arabic numerals. Appendices included should also be numbered in an identical
manner starting with Appendix 1.

7.3 Numbering of Tables and Figures

Tables and Figures appearing anywhere in the project report should bear
appropriate numbers. The rule for assigning such numbers is illustrated through
an example. Thus if as figure in Chapter 3, happens to be the fourth then assign
3.4 to that figure. Identical rules apply for tables except that the word Figures is
replaced by the word Table. If figures (or tables) appear in appendices then
figure 3 in Appendix 2 will be designated as Figure A 2.3. If a table to be
continued into the next page this may be done, but no line should be drawn
underneath an unfinished table. The top line of the table continued into the next
page should, for example read Table 2.1 (continued) placed centrally and
underlined.

7.4 Numbering of Equations

Equations appearing in each Chapter or Appendix should be numbered serially,
the numbering commencing a fresh for each Chapter or Appendix. Thus for
example, an equation appearing in Chapter 2, if it happens to be the eighth
equation in that Chapter should be numbered (2.8) thus:

16
 MCA Project work guidelines

min f ( x) (2.8)
x∈R

While referring to this equation in the body of the project report it should be
referred to as Equation (2.8).

8. BINDING SPECIFICATIONS
Project report submitted should be bound using flexible cover of thick white art
paper. The spine for the bound volume should be of Light Blue. The cover should
be printed in black letters and the text for printing should be identical to what has
been prescribed for the title page.

9. CHAPTER CONTENTS

Chapter 1. : Introduction: Theoretical background of the area chosen for the

project work, Definition of the problem.

Chapter 2: System Analysis & Design: User Requirements, System planning,

Methodology adopted.

Chapter 3: Design of the System: ER-Diagrams, Data Flow Diagrams, Data

Structures Used, Input and Output Screen Design, Process involved,
Methodology used for testing, Test Report, Printout of the Reports, Printout of the
Code Sheet, User/Operational Manual - including security aspects, access rights,
back up, controls, etc.

Chapter 3: System Implementation: Details of Hardware & Software Used,

System Maintenance & Evaluation, Cost and benefit Analysis Detailed Life Cycle
of the Project.

Chapter 5: A session with the software: Screen snap shots in the chronological
order with brief explanation for each.

17
 MCA Project work guidelines

Chapter 6: Conclusions and Future Directions

APPENDIX 1
(A typical Specimen of Title Page)

A GUI PACKGE FOR KOHONEN’S SELF

ORGANIZED MAPS
Submitted in partial fulfillment of the requirements
for the award of the degree

Of

MASTER OF COMPUTER APPLICATIONS

Of
Visvesvaya Technological University

By

(Name of Candidate)
USN

18
 MCA Project work guidelines

DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

Siddaganga Institute of Technology
Tumkur-572103
2007

APENDIX-II
(Format of the Bonafide certificate)

SIDDAGANGA INSTITUTE OF TECHNOLOGY

Department of Master of Computer Applications
Tumkur-572103

CERTIFICATE

Certified that this project report titled…………………………submitted in partial

fulfillment of the requirement of the degree of Master of Computer

Applications is the bonafide work of Mr./ Ms………………………………..who

carried out the project under my supervision. Certified further, that to the best of

19
 MCA Project work guidelines

my knowledge the work reported herein does not form part of any other project

report or dissertation on the basis of which a degree or award was conferred on

an earlier occasion on this or any other candidate.

Name and Designation of the Guide Signature of External Guide

Principal
Head of the Department

APENDIX-III
(Sample abstracts)

An Abstract is basically a summary or gist of the project. It should preferably, be

of about 2-3 pages. The content should be as brief as is sufficient enough to
explain the objective and implementation of the project. The write up must
adhere to the guidelines and should include the following;

• Name / Title of the Project

• Statement about the Problem
• Few lines are the chosen area to bring out its significance.
• Why is the particular topic chosen?
• Objective and scope of the Project
• Methodology adopted/proposed.
• Hardware & Software used
• Testing Technologies used
• What contribution would the project make?

Following are two typical examples of abstracts.

20
 MCA Project work guidelines

Example 1:

A GUI BASED GENETIC ALGORITHM OPTIMISER

A genetic algorithm (GA) is a search technique used in computing to find exact or

approximate solutions to optimization and search problems. Genetic algorithms
are categorized as global search heuristics. Genetic algorithms are a particular
class of evolutionary algorithms (also known as evolutionary computation) that
use techniques inspired by evolutionary biology such as inheritance, mutation,
selection, and crossover.

Genetic algorithms are implemented as a computer simulation in which a

population of abstract representations (called chromosomes or the genotype or
the genome) of candidate solutions (called individuals, creatures, or phenotypes)
to an optimization problem evolves toward better solutions. Traditionally,
solutions are represented in binary as strings of 0s and 1s, but other encodings
are also possible. The evolution usually starts from a population of randomly
generated individuals and happens in generations. In each generation, the
fitness of every individual in the population is evaluated, multiple individuals are
stochastically selected from the current population (based on their fitness), and
modified (recombined and possibly randomly mutated) to form a new population.
The new population is then used in the next iteration of the algorithm. Commonly,
the algorithm terminates when either a maximum number of generations has
been produced, or a satisfactory fitness level has been reached for the
population. If the algorithm has terminated due to a maximum number of
generations, a satisfactory solution may or may not have been reached.

This project work is an attempt to develop a GUI based package for the
implementation of simple genetic algorithm based optimizations in any field that
is user specific. The package is provided with an efficient user interface with
explanation facility so that even a novice user can participate in the development

21
 MCA Project work guidelines

of optimization model in his/her chosen domain. The front end has been created
using Java Swing. At the back end the algorithm has been coded in Java.

The validation has been done for some benchmark problems availed from the
literature. The system yielded encouraging results in terms of optimized decision
variable values. Though the package has given satisfactory results at academic
level, the package needs to be field tested for its adaptability and usefulness.

Example 2:

REAL ESTATE ADMINISTRATIVE MANAGEMENT SYSTEM

In real estate administration, providing ready information about location, nature

cost of lands and related operations on the data can be a very costly and time-
consuming process. To remain competitive, an organization needs to automate
the process of collecting the backup information for these operations. In addition,
real estate companies that manage huge volumes of tenant billing backup data
should integrate their billing systems and ensure easy correspondence
management with their customers. Ensuring that journal entry imaging for
property reporting and audit purposes is a built-in component is also critical to
best practices and reduced business operating costs. The typical data sources
and operations are Investing, Converting, Leveraging real estate assets, and
management for your properties, their administration financial reporting issues,
turnovers and many more.

22
 MCA Project work guidelines

This project brings out the development of an online estate agent system, which
could be deployed either by a real estate agent or a prospective buyer. The
project is more of a Web Enabled Agent (WEEA), which is internet-based
application. This system is intended to be used for storing and searching the
property portfolios.

The main modules of the system include Property Portfolio Management, User
Management, and General Management. Property portfolio management deals
with maintaining information related to properties. User management deals with
maintaining user information depending on the user category, transaction type,
property category and property subcategory. General management deals with
concepts like advertisements and sending buyer information to the seller.

The project is developed in Industrial Competency Laboratory, using Java2

Enterprise edition and Oracle 8i at the back end. This project presents the
development of a GUI based package that caters to all the information needed
for the users. It is felt that this package is of great help for the people who need
their land property be sold and also for the people who are desirous of
purchasing of such property.

The system has given satisfactory results at academic level testing. However,
field-testing of the software is yet to be done to improve the software.

23
 MCA Project work guidelines

APENDIX-III
(Sample Conclusions)

The conclusion of your project work should provide a final critical reflection on the
study and its contribution to literature and the area of investigation. It should also
point to issues that could be pursued in future project work.

Conclusions are usually short and should not contain new material. They are
often difficult to write, as you are likely to feel that you have said it all by this
stage. As a result, many students simply summarize what they have said in
previous chapters…unfortunately, this is NOT concluding! The conclusion of your
project has three main roles.

• First, it provides an ending to the project – as mentioned above, it

provides the opportunity for you to say what your project means.
• Second, it provides you with the opportunity to say how your project can
contribute to our understanding of the knowledge in the area, of current
practice and/ or relevant methods.
• Third, it leaves the reader with a final impression of the quality of your
work.

Two sample conclusions are provided here for your reference.

24
 MCA Project work guidelines

Example 1:

A GUI BASED GENETIC ALGORITHM OPTIMISER

This project report brought out the development of a simple genetic algorithm
(SGA) shell, which can be a useful tool in the hands of any user to develop SGA
model for optimization problem in his/her domain of interest. The package has
been provided with highly interactive user interface. Based on the project work,
following conclusions could be drawn.

1. A Graphical User Interface (GUI) based optimizer like the one developed
in this work is of immense help for any user as he/she could effortlessly
model the chosen domain.

2. A user can directly type the objective function and constraints so that the
user would be at ease.

3. The package can cater to any number of decision variables. The results
are tuned to third decimal place of accuracy,

4. With minor modification, the package can be uploaded over to the net.
This enables a large number of people to make use of the effort.

Finally, the reported work is open to suggestions, comments, and modifications

by the experts in the field of Evolutionary optimization techniques.

Future Enhancements

The project carried out is amenable for future enhancements. Following are the
improvements suggested:

25
 MCA Project work guidelines

1. The selection operator used in the development of software is Roulette

Wheel selection. However, provisions could be made to implement other
selection methods like Rank selection, steady state selection and Elitism.

2. Simple single crossover operator is used in the development; other cross

over operations like arithmetic crossover and uniform cross over could be
implemented.

3. Binary coding is adopted to encode decision variables, real, octal and

hexadecimal coding techniques could be tried as a future enhancement.

Example 2:

REAL ESTATE ADMINISTRATIVE MANAGEMENT SYSTEM

This project presented the development of Real Estate Administration

Management System. The main aim of the project was to bring various activities
related to real estate such as buying, selling, mortgaging and description of the
property.

The development of the software was done on a modular basis. Following are
the facilities provided:

1. Description of the property to be sold or bought.

2. Approximate price, name and details of the owner.

3. Search information

4. Update information

26
 MCA Project work guidelines

5. Deleting Information.

It is felt that this kind of a package is useful in the hands of real estate people
and the others involved in buying and selling land properties. The interface has
been extremely good such that even a novice user can work with the software.

Future Enhancements
There is still lot of scope for the enhancement of this work. Following are the
suggested future enhancements.

1. Details of location of the plot need be graphically shown with the relevant
area map.

2. The details of predominant monuments and the like in the neighborhood of

the property are to be displayed.

3. The foreseeable improvements that may happen around the property be

highlighted.

27