1

PROJECT RECORD CONTENTS ORDERED LIST.

ABSTRACT
1. Introduction
1.1 Introduction to the Project .
1.1.1 Scope.
1.1.2 Problem statement.
1.2 Existing System
1.3 Proposed System including modules.

2. Requirement Analysis
2.1 Feasibility study
2.1.1 Technical Feasibility
2.1.2 Economical Feasibility
2.1.2.1 Cost Benefit Analysis
2.1.3 Operational Feasibility
2.2. Software Requirement Specification
2.2.1 Functional Requirements
2.2.1.1. Input
2.2.1.2. Output
2.2.1.3. Computational
2.2.1.4. Storage ( database requirements)
2.2.2. Non-Functional Requirements
2.2.2.1. Quality Metrics
2.2.2.2. Reliability
2.2.2.3. Usability
2.2.2.4. Response Time
2.2.2.5. Throughput
2.2.2.6. Availability
2.2.2.7. Maintainability
2.2.3. Environment & Technology Requirements
2.2.3.1. Hardware Requirements
2.2.3.2. Software Requirements

3. Design
3.1. System Design
3.1.1. Introduction to UML.
3.1.2. UML Diagrams.
3.1.2.1. Scenarios.
3.1.2.2. Use-Case Diagrams.
3.1.2.3. Class Diagrams.
3.1.2.4. Object Diagrams.
3.1.2.5. Sequence Diagrams ( or Collaboration Diagrams).
3.1.2.6. Activity Diagrams.
3.1.2.7. State Diagrams.
3.1.2.8. Component Diagrams. (Optional)
 2

3.1.2.9. Deployment Diagrams ( Optional)

3.2. Interface Design ( Input forms)

3.3. Database Design

3.3.1. Introduction to Backend.
3.3.2. Normalization regarding the project tables.
3.3.3. Table Description.

4. Coding
4.1. Sample Code (3-4 pages).

5. Testing
5.1. Introduction to Testing.
5.2. Test Cases (module-wise)

6. Screenshots
6.1. Input Screens (Forms).
6.2. Output Screens (Reports).

7. Conclusion
Consists of two paragraphs one that concludes the project and another the
future scope of the project.

8. Bibiliography.

Note:
Font size: main headings – Times New Roman – 16 - bold
Side headings - Times New Roman – 14 - bold
Inner matter – Times New Roman – 12 – normal

PAGE FORMAT : Paper Size --- A4

Left Margin --- 1 ½”
Right Margin - - - 1”
Top Margin --- 1”
Bottom Margin - - - 1”
Line Space --- 1 ½”
Page Numbers at the Bottom Centre
2 Hard Bound copies are to submitted
 3

UML is a standard language for specifying, visualizing, constructing,

and documenting the artifacts of software systems.
UML was created by Object Management Group (OMG) and UML 1.0
specification draft was proposed to the OMG in January 1997.
OMG is continuously putting effort to make a truly industry standard.
 UML stands for Unified Modeling Language.
 UML is different from the other common programming languages
like C++, Java, COBOL etc.
 UML is a pictorial language used to make software blue prints.
So UML can be described as a general purpose visual modeling
language to visualize, specify, construct and document software
system. Although UML is generally used to model software systems but
it is not limited within this boundary. It is also used to model non
software systems as well like process flow in a manufacturing unit etc.
UML is not a programming language but tools can be used to generate
code in various languages using UML diagrams. UML has a direct
relation with object oriented analysis and design. After some
standardization UML is become an OMG (Object Management Group)
standard.
Goals of UML:
A picture is worth a thousand words, this absolutely fits while
discussing about UML. Object oriented concepts were introduced much
earlier than UML. So at that time there were no standard
methodologies to organize and consolidate the object oriented
development. At that point of time UML came into picture.
There are a number of goals for developing UML but the most
important is to define some general purpose modeling language which
all modelers can use and also it needs to be made simple to
understand and use.
UML diagrams are not only made for developers but also for business
users, common people and anybody interested to understand the
system. The system can be a software or non software. So it must be
clear that UML is not a development method rather it accompanies with
processes to make a successful system.
At the conclusion the goal of UML can be defined as a simple modeling
mechanism to model all possible practical systems in today.s complex
environment.
A conceptual model of UML:
To understand conceptual model of UML first we need to clarify What is
a conceptual model? and Why a conceptual model is at all required?
 A conceptual model can be defined as a model which is made of
concepts and their relationships.
 A conceptual model is the first step before drawing a UML
diagram. It helps to understand the entities in the real world and
how they interact with each other.
 4

As UML describes the real time systems it is very important to make a

conceptual model and then proceed gradually. Conceptual model of
UML can be mastered by learning the following three major elements:
 UML building blocks
 Rules to connect the building blocks
 Common mechanisms of UML

Object oriented concepts:

UML can be described as the successor of object oriented analysis and
design.
An object contains both data and methods that control the data. The
data represents the state of the object. A class describes an object and
they also form hierarchy to model real world system. The hierarchy is
represented as inheritance and the classes can also be associated in
different manners as per the requirement.
The objects are the real world entities that exist around us and the
basic concepts like abstraction, encapsulation, inheritance,
polymorphism all can be represented using UML.
So UML is powerful enough to represent all the concepts exists in
object oriented analysis and design. UML diagrams are representation
of object oriented concepts only. So before learning UML, it becomes
important to understand OO concepts in details.
Following are some fundamental concepts of object oriented world:
 Objects: Objects represent an entity and the basic building
block.
 Class: Class is the blue print of an object.
 Abstraction: Abstraction represents the behavior of an real
world entity.
 Encapsulation: Encapsulation is the mechanism of binding the
data together and hiding them from outside world.
 Inheritance: Inheritance is the mechanism of making new
classes from existing one.
 Polymorphism: It defines the mechanism to exists in different
forms.
OO Analysis and Design
Object Oriented analysis can be defined as investigation and to be
more specific it is the investigation of objects. Design means
collaboration of identified objects.
So it is important to understand the OO analysis and design concepts.
Now the most important purpose of OO analysis is to identify objects of
a system to be designed. This analysis is also done for an existing
system. Now an efficient analysis is only possible when we are able to
start thinking in a way where objects can be identified. After identifying
the objects their relationships are identified and finally the design is
produced.
So the purpose of OO analysis and design can described as:
 Identifying the objects of a system.
 Identify their relationships.
 5

 Make a design which can be converted to executables using OO

languages.
There are three basic steps where the OO concepts are applied and
implemented. The steps can be defined as
OO Analysis --> OO Design --> OO implementation using OO
languages
Now the above three points can be described in details:
 During object oriented analysis the most important purpose is to
identify objects and describing them in a proper way. If these
objects are identified efficiently then the next job of design is
easy. The objects should be identified with responsibilities.
Responsibilities are the functions performed by the object. Each
and every object has some type of responsibilities to be
performed. When these responsibilities are collaborated the
purpose of the system is fulfilled.
 The second phase is object oriented design. During this phase
emphasis is given upon the requirements and their fulfilment. In
this stage the objects are collaborated according to their
intended association. After the association is complete the design
is also complete.
 The third phase is object oriented implementation. In this phase
the design is implemented using object oriented languages like
Java, C++ etc.
Role of UML in OO design:
UML is a modeling language used to model software and non software
systems. Although UML is used for non software systems the emphasis
is on modeling object oriented software applications. Most of the UML
diagrams discussed so far are used to model different aspects like
static, dynamic etc. Now what ever be the aspect the artifacts are
nothing but objects.
If we look into class diagram, object diagram, collaboration diagram,
interaction diagrams all would basically be designed based on the
objects.
So the relation between OO design and UML is very important to
understand. The OO design is transformed into UML diagrams
according to the requirement. Before understanding the UML in details
the OO concepts should be learned properly. Once the OO analysis and
design is done the next step is very easy. The input from the OO
analysis and design is the input to the UML diagrams.

As UML describes the real time systems it is very important to make a

conceptual model and then proceed gradually. Conceptual model of UML can
be mastered by learning the following three major elements:
 UML building blocks
 Rules to connect the building blocks
 Common mechanisms of UML
This chapter describes all the UML building blocks. The building blocks of
UML can be defined as:
 6

 Things
 Relationships
 Diagrams
(1) Things:
Things are the most important building blocks of UML. Things can be:
 Structural
 Behavioral
 Grouping
 Annotational

Structural things:
The Structural things define the static part of the model. They represent
physical and conceptual elements. Following are the brief descriptions of the
structural things.
Class:
Class represents set of objects having similar responsibilities.

Interface:
Interface defines a set of operations which specify the responsibility of a
class.

Collaboration:
Collaboration defines interaction between elements.

Use case:
Use case represents a set of actions performed by a system for a specific
goal.

Component:
Component describes physical part of a system.

Node:
A node can be defined as a physical element that exists at run time.
 7

Behavioral things:
A behavioral thing consists of the dynamic parts of UML models. Following
are the behavioral things:
Interaction:
Interaction is defined as a behavior that consists of a group of messages
exchanged among elements to accomplish a specific task.

State machine:
State machine is useful when the state of an object in its life cycle is
important. It defines the sequence of states an object goes through in
response to events. Events are external factors responsible for state change.

Grouping things:
Grouping things can be defined as a mechanism to group elements of a
UML model together. There is only one grouping thing available:
Package:
Package is the only one grouping thing available for gathering structural and
behavioral things.

Annotational things:
Annotational things can be defined as a mechanism to capture remarks,
descriptions, and comments of UML model elements. Note is the only one
Annotational thing available.
Note:
A note is used to render comments, constraints etc of an UML element.

(2) Relationship :
Relationship is another most important building block of UML. It shows how
elements are associated with each other and this association describes the
functionality of an application.
There are four kinds of relationships available.
Dependency:
Dependency is a relationship between two things in which change in one
element also affects the other one.

Association:
Association is basically a set of links that connects elements of an UML
model. It also describes how many objects are taking part in that
relationship.
 8

Generalization:
Generalization can be defined as a relationship which connects a specialized
element with a generalized element. It basically describes inheritance
relationship in the world of objects.

Realization:
Realization can be defined as a relationship in which two elements are
connected. One element describes some responsibility which is not
implemented and the other one implements them. This relationship exists in
case of interfaces.

(3) UML Diagrams:

UML diagrams are the ultimate output of the entire discussion. All the
elements, relationships are used to make a complete UML diagram and the
diagram represents a system.
The visual effect of the UML diagram is the most important part of the entire
process. All the other elements are used to make it a complete one.
UML includes the following nine diagrams and the details are described in the
following chapters.
1. Class diagram
2. Object diagram
3. Use case diagram
4. Sequence diagram
5. Collaboration diagram
6. Activity diagram
7. Statechart diagram
8. Deployment diagram
9. Component diagram
We would discuss all these diagrams in subsequent chapters of this tutorial.

Any real world system is used by different users. The users can be
developers, testers, business people, analysts and many more. So
before designing a system the architecture is made with different
perspectives in mind. The most important part is to visualize the
system from different viewer.s perspective. The better we understand
the better we make the system.
UML plays an important role in defining different perspectives of a
system. These perspectives are:
 Design
 Implementation
 Process
 Deployment
And the centre is the Use Case view which connects all these four. A
Use case represents the functionality of the system. So the other
perspectives are connected with use case.
 9

 Design of a system consists of classes, interfaces and

collaboration. UML provides class diagram, object diagram to
support this.
 Implementation defines the components assembled together to
make a complete physical system. UML component diagram is
used to support implementation perspective.
 Process defines the flow of the system. So the same elements
as used in Design are also used to support this perspective.
 Deployment represents the physical nodes of the system that
forms the hardware. UML deployment diagram is used to support
this perspective.

It is very important to distinguish between the UML model. Different

diagrams are used for different type of UML modeling. There are three
important type of UML modelings:
Structural modeling:
Structural modeling captures the static features of a system. They
consist of the followings:
 Classes diagrams
 Objects diagrams
 Deployment diagrams
 Package diagrams
 Composite structure diagram
 Component diagram
Structural model represents the framework for the system and this
framework is the place where all other components exist. So the class
diagram, component diagram and deployment diagrams are the part of
structural modeling. They all represent the elements and the
mechanism to assemble them.
But the structural model never describes the dynamic behavior of the
system. Class diagram is the most widely used structural diagram.
Behavioral Modeling:
Behavioral model describes the interaction in the system. It represents
the interaction among the structural diagrams. Behavioral modeling
shows the dynamic nature of the system. They consist of the following:
 Activity diagrams
 Interaction diagrams
 Use case diagrams
All the above show the dynamic sequence of flow in a system.
Architectural Modeling:
Architectural model represents the overall framework of the system. It
contains both structural and behavioral elements of the system.
Architectural model can be defined as the blue print of the entire
system. Package diagram comes under architectural modeling.

UML is popular for its diagrammatic notations. We all know that UML is for
visualizing, specifying, constructing and documenting the components of
 10

software and non software systems. Here the Visualization is the most
important part which needs to be understood and remembered by heart.
UML notations are the most important elements in modeling. Efficient and
appropriate use of notations is very important for making a complete and
meaningful model. The model is useless unless its purpose is depicted
properly.
 11

Project Review Process

Part-I

1) Project Title Justification

2) Objective of the Project
3) a) Existing System
b) Proposed System
4) Flow of the Project
5) List of the Modules of the Project (Module names &
their Objectives)
6) Code Flow (Phase to Phase)
7) Functional Specification
8) Possibility of Future Enhancements of the project (if
any)
9) Testing
10) Conclusion

Part –II

11) Documents
a) PPT
b) UML Diagrams
12) Execution Process of the Project
12
13
14
 15

MCA
6th SEMESTER

With effect from 2007-08 admitted batch

Syllabi
( Tentative)

Chairman
Board of Studies
(2005-08)

Dept of Computer Science and Systems Engineering

College of Engineering
Andhra University
Visakhapatnam
 16
MASTER OF COMPUTER APPLICATIONS
Course Structure and Scheme of Examination
rd nd
3 Year –2 SEMESTER

With Effect from 2007-08 admitted batch

Code Name of the Subject EXTERNAL EVALUATION
MCA 3.2 Project 100 Marks

GUIDELINES for preparing the report of the Project Work

FORMAT FOR PREPARATION OF PROJECT REPORT

FOR

MCA

1. ARRANGEMENT OF CONTENTS:

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

1. Cover Page & Title Page

2. Bonafide Certificate
3. Abstract
4. Table of Contents
5. List of Tables
6. List of Figures
7. List of Symbols, Abbreviations and Nomenclature
8. Chapters
9. Appendices
10. References

The table and figures shall be introduced in the appropriate places.

2. PAGE DIMENSION AND BINDING SPECIFICATIONS:

The dimension of the project report should be in A4 size. The project report should be
bound using flexible cover of the thick white art paper. The cover should be printed in
black letters and the text for printing should be identical.
 17

3. PREPARATION FORMAT:

3.1 Cover Page & Title Page – A specimen copy of the Cover page & Title page of the project
report are given in Appendix 1.

3.2 Bonafide Certificate – The Bonafide Certificate shall be in double line spacing using Font
Style Times New Roman and Font Size 14, as per the format in Appendix 2.

The certificate shall carry the supervisor’s signature and shall be followed by the supervisor’s
name, academic designation (not any other responsibilities of administrative nature),
department and full address of the institution where the supervisor has guided the student.
The term ‘SUPERVISOR’ must be typed in capital letters between the supervisor’s name
and academic designation.

3.3 Abstract – Abstract should be one page synopsis of the project report typed double line
spacing, Font Style Times New Roman and Font Size 14.

3.4 Table of Contents – The table of contents should list all material following it as well as any
material which precedes it. The title page and Bonafide Certificate 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. A specimen copy of the Table of Contents of the project report is given in Appendix 3.

3.5 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.

3.6 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.

3.7 List of Symbols, Abbreviations and Nomenclature – One and a half spacing should
be adopted or typing the matter under this head. Standard symbols, abbreviations etc. should be
used.

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

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

 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.
 18

3.9 Appendices – Appendices are provided to give supplementary information, which is

included in the main text may serve as a distraction and cloud the central theme.

 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.

 Appendices shall carry the title of the work reported and the same title shall be made in
the contents page also.

3.10 List of References –The listing of references 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 example quoted above.

REFERENCES

1. Ariponnammal, S. and Natarajan, S. (1994) ‘Transport Phonomena of Sm Sel –

X Asx’, Pramana – Journal of Physics Vol.42, No.1, pp.421-425.

2. Barnard, R.W. and Kellogg, C. (1980) ‘Applications of Convolution Operators to

Problems in Univalent Function Theory’, Michigan Mach, J., Vol.27, pp.81–94.

3. Shin, K.G. and Mckay, N.D. (1984) ‘Open Loop Minimum Time Control of
Mechanical Manipulations and its Applications’, Proc.Amer.Contr.Conf., San Diego,
CA, pp. 1231-1236.

3.10.1 Table and figures - By the word Table, is meant tabulated numerical data in the body of the
project report as well as in the appendices. All other non-verbal materials used in the body of
the project work and appendices such as charts, graphs, maps, photographs and diagrams
may be designated as figures.

4. TYPING INSTRUCTIONS:

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

One and a half spacing should be used for typing the general text. The general text shall be
typed in the Font style ‘Times New Roman’ and Font size 14.
 19
*****
 20

(A typical Specimen of Cover Page & Title Page)

<Font Style Times New Roman – Bold>

TITLE OF PROJECT REPORT

<Font Size 18><1.5 line spacing>

A PROJECT REPORT
<Font Size 14>

Submitted by
<Font Size 14><Italic>

NAME OF THE CANDIDATE

<Font Size 16>

in partial fulfillment for the award of the degree of

<Font Size 14><1.5 line spacing><Italic>

MASTER OF COMPUTER APPLICATIONS

<Font Size 16>

< Emblem>

Name of the department

<Font Size 12>
Name of the college
< Font Size 14>
ANDHRA UNIVERSITY : VISAKHAPATNAM - 530003(for A.U. College)

AFFILIATED TO ANDHRA UNIVERSITY : VISAKHAPATNAM - 530003

(for A.U. affiliated College)

<Font Size 16><1.5 line spacing>

MONTH & YEAR
<Font Size 14>
 21
SPECIMEN

SOME PERFORMANCE ASPECTS CONSIDERATIONS OF

A CLASS OF ARTIFICIAL NEURAL NETWORK

A PROJECT REPORT

Submitted by

SANDHY. A

in partial fulfillment for the award of the degree of

MASTER OF COMPUTER APPLICATIONS

<Emblem>

DEPARTMENT OF COMPUTER SCIENCE AND SYSTEMS ENGINEERING

ANDHRA UNIVERSITY AUTONOMOUS COLLEGE OF ENGINEERING
ANDHRA UNIVERSITY:: VISAKHAPATNAM-530 003

MAY 2008
 22

CERTIFICATE FOR STUDENTS WHO HAD DONE PROJECT IN THE DEPARTMENT

CERTIFICATE

This is to certify that it is a bonafide work done by Mr./Ms.Mrs. __________________ during the

year 200 - 200 in partial fulfillment of the requirements for the award of degree of Master of Computer

Applications in the <name of the Department and College address> This work is not submitted to any

University for the award of any Degree / Diploma.

Name, Designation and Signature of INTERNAL GUIDE

HEAD OF THE DEPARTMENT

<Dept./College Stamp>
 23
CERTIFICATE FOR STUDENTS WHO HAD DONE PROJECT IN THE
INDUSTRY / ORGANISATION

This is to certify that it is a bonafide record of the Dissertation work entitled

“___________________________________________________” done by STUDENT NAME , a student
of MCA in <dept./college address> during the period 200 - 200 in partial fulfillment of the
requirements for the Award of Degree of MASTER OF COMPUTER APPLICATIONS. This work is not
submitted to any University for the award of any Degree / Diploma. This work is carried out in ( NAME
OF THE ORGANISATION ) with complete address.

INTERNAL GUIDE

HEAD OF THE DEPARTMENT

CERTIFICATE FROM INDUSTRY

To Date:

Head of the Department

College Address

CERTIFICATE OF PROJECT COMPLETION

This is to certify that _______________________________________________

Has completed the project in our organization as per the particulars given below.

PERIOD :

PROJECT TITLE :

SOFTWARE TOOLS USED :

SIGNATURE AND STAMP

INDUSTRY / ORGANISATION
OFFICE SEAL
 24

FORMAT OF M.TECH. DISSERTATION

The dissertation should be in the following format. Otherwise , the submission is rejected.
 Cover / Title Page
 1st Page=Cover Page
 Certificate(Dept. )
 Submit to the H.O.D
 Acknowledgements
 Abstract
 Table of Contents with page numbers
 Rest of the Dissertation : follow the guidelines given
 References

REFERENCES EXAMPLE:

1. Dias, F.J.O. , “Truth-table verification of an iterative logic array, ” IEEE Tans. On

Computers, Vol. C-25, PP 605-613 , June 1976.
2. “Signature analysis, “ Hewiett-Packard Journal , Vol. 28, No. 9, May 1977.
(1) (2) are to shown in text.
 Bibliography

BIBLIOGRAPHY EXAMPLE:

1. (Author) (Text Book) (Publisher), Year

 Appendix

PAGE FORMAT: Paper Size ……… A4

Left Margin ……… 1 ½’’
Right Margin ……… 1’’
Top Margin ……… 1’’
Bottom Margin ……… 1’’
Line Space ……… 1 ½”
Font-Times New Roman 12
Page Numbers at the Bottom Centre
3 Hard Bound copies are to be submitted
Students must have regular interaction with the project guide. Progress is to be submitted through guide
every two months to the Department. Project submission is not allowed for those students who fail to give
progress report ON TIME (every two months). Starting Day of Instruction for 6th Sem. MCA,
Last Day of Instruction for 6 th Sem. MCA, Last Day of MCA Project Submission, and Commencement
of MCA Project Viva Examination will be specified as per the academic calender

NOTE: The internal guide must be available during Viva-Voce Examination of the concerned
student(s).
 25

PRESENTATION MATERIAL FOR PROJECT VIVA:

Each student has to attend viva with not less than 20 and not more than 25 PPT slides covering
major key points of the work. Results of the Project work should be demonstrated on a PC. Soft copy of
the code must be kept in the folder attached to the last cover page. Projects without code cannot be
accepted.

MCA PROJECT GUIDE LINES

The purpose of this note is to describe how to organize the written Dissertation submitted as
partial fulfillment of your MCA. Degree.

The distinguishing mark of a dissertation is an original contribution to knowledge. The

dissertation is a formal document whose sole purpose is to prove that you have made an original
contribution to knowledge. Failure to prove that you have made such a contribution generally leads to
failure.

To this end, your dissertation mush show two important things :

1. You have identified a worthwhile problem, which has not been previously solved.
2. You have answered the question.

Your contribution to knowledge generally lies in your solution or answer.

The sole purpose of the dissertation is to prove that you have made an original and useful contribution to
knowledge. The examiners need answers to the following questions:

 What is this student’s research question?

 Is it a good question? (has it been answered before> is it a useful question to work on?)
 Did the student convince me that the question was adequately answered?
 Has the student made an adequate contribution to knowledge?

To prove the originality and value of your contribution, you must present a through review of the existing
literature on the subject, and on closely related subjects. Then, by making direct reference to your
literature review, you must demonstrate that your question.

(a) Has not been previously answered, and

(b) Is worth answering

Describing how you answered the question is usually easier to write about, since you have been
intimately involved in the details over the course of your studies.
 26

A Generic Dissertation Skeleton

1. INTRODUCTION

This is a general introduction to what the dissertation is all about-it is not just a description of the contents
of each section. Briefly summarize the question (You will be stating the question in detail later), some of
the reasons why it is a worthwhile question, and perhaps give an overview of you main results. This is a
birds-eye view of the answers to the main questions answered in the dissertation (see above).

2. BACKGROUND INFORMATION

A brief section giving background information may be necessary, especially if your work spans two or
more traditional fields. That means your readers may not have any experience with some of the material
needed to follow your dissertation, so you need to give it to them. A different title than that given above
is usually better; e.g., “A Brief Review of Frammis Algebra”.

3. REVIEW OF THE STATE OF THE ART

Here you review the state of the art relevant to your dissertation. Again, a different title is probably
appropriate; e.g., “State of the Art in Zylon Algotithm”. The idea is to present (critical analysis a little
bit later) the major ideas in the state of the art right up to, but not including, your own personal brilliant
ideas.

You organize this section by idea, and not by author or by publication. For example if there have been
three important main approachs to Zylon Algorithms to date, you might organize subsections around
these three approaches, if necessary:
3.1. Interactive Approximate of Zylons
3.2. Statistical Weighting of Zylons
3.3. Graph-theoretic Approaches to Zylon Manipulation

4. PROBLEM STATEMENT

Engineering dissertation tend to refer to a “problem to be solved.

 A concise statement of the question that you dissertation tackles

 Justification, by direct reference to section3, that you question is previously unanswered.
 Discussion of why it is worthwhile to answer this question.
 27

Item 2 above is where you analyze information which you presented in Section 3. For example, may be
your problem is to “develop a Zylon algorithm capable of handling very large scale problems in
reasonable time” (you would further describe what you mean by “large scale” and “reasonable time” in
the problem statement). Now in your analysis of the art ou would show how each class of current
approaches fails (i.e. can handle only small problems, o taks too much time). In the last part of this
section you would explain why having a large scale fast Xylon algorithm is useful; e.g., by describing
applications where it can be used.

5. DESCRIBING HOW YOU SOLVED THE PROBLEM

This part of the dissertation is much more free-form. It may have one or several sections and subsections.
But it all has only one purpose: to convince the examiners that you solved the problem that you set for
yourself in Section 4. So show what you did that is relevant to solving the problem: if there were blind
all eye and dead ends, do not include these.

6. CONCLUSIONS

You generally cover three things in the Conclusions section, and each of these usually merits a separate
subsection:

a) Conclusions
b) Summary of Contributions
c) Future Research

7. REFERENCES

The list of references is closely tied to the review of the state of the art given in section 3. most examines
scan your list of references looking for the important for the important works in the field, so make sure
they are listed and referred to in section 3. Truth be known, most examiners also look for their own
publications if they are in the topic area of the dissertation, so list these too. Besides, reading your
examiner’s papers usually gives you a clue as to the type of questions they are likely to ask.

All references given must be referred to in the main body of the dissertation. Note the difference from a
Bibliography, which may include works that are not directly referenced in the dissertation. Organize the
list of references either alphabetically by author surname (preferred), or b order of citation in the
dissertation.
 28

8. APPENDICES

What goes in the appendices? Any material which impedes the smooth development of your
presentation, but which is important to justify the results of a dissertation. Generally it is material that is
of too nitty-gritty a level of detail for inclusion in the main body of the dissertation, by which should be
available for perusal by the examiners to convince them sufficiently. Examples include program listings,
immense tables of data, lengthy mathematical proofs or derivations, etc.,

A NOTE ON COMPUTER PROGRAMS AND OTHER PROTOTYPE

The purpose of your dissertation is to clearly document an original contribution to knowledge. You
may develop computer programs, prototypes, or other tools as a means of providing your points, but
remember, the dissertation is not about the tool, it is about the contribution to knowledge. Tools such as
computer programs are fine and useful products, but you can’t get an advanced degree just for the tool.
You must use the tool to demonstrate that you have made an original contribution to knowledge; e.g.,
through its use, or ideas it embodies.

HOW TO WRITE AN ABSTRACT

ABSTRACT

Because on-line search databases typically contain only abstracts, it is vital to write a complete but concise
description of your work to notice potential readers into obtaining a copy of the full paper. This article describes
how to write a good computer architecture abstract for both conference and journal papers. Writers should follow
a checklist consisting of motivation, problem statement, approach, results, and conclusions. Following this
checklist should increase the chance of people taking the time to obtain and read your complete paper.

INTRODUCTION

Now that the use of on-line publication databases is prevalent, writing a really good abstract has become
even more important than it was a decade ago. Abstracts have always served the function of “selling” your work,
But now, instead of merely convincing the reader to keep reading the rest of the attached paper, an abstract must
convince the reader to leave the comfort of an office and go hunt down a copy- of the article from a library ( or
worse , obtain one after a long wait through inter-library loan). In a business context , an “executive summary” is
often the only piece of a report read by the people who matter ; and it should be similar in contest if not tone to a
journal paper abstract.
 29

CHECKLIST : PARTS OF AN ABSTRACT

Despite the fact that an abstract is quite belief , it must do almost as much work as the multipage paper that
follows it. In a computer architecture paper, this means that it should in most cases include the following sections.
Each section is typically a single sentence , although there is room for creativity. In particular , the parts may be
merged or spread among a set of sentences. Use the following as a checklist for your next abstract.

 MOTIVATION

Why do we are about the problem and the results? If the problem is not obviously “interesting” it might be
better to put motivation first; but if your work is incremental progress on a problem that is widely
recognized as important, then it is probably better to put the problem statement first to indicate which piece
of the larger problem you are breaking off to work on. This section should include the importance of your
work, the difficulty of the area , and the impact it might have if successful.

 PROBLEM STATEMENT

What problem are you trying to solve ? What is the scope of your work (a, generalized approach , or for a
specific situation)? Be careful not to use too much jargon. In some cases it is appropriate to put the problem
statement before the motivation, but usually this only works if most readers already understand I why the
problem is important.

 RESULTS
What’s answer? Specifically , most good computer architecture papers conclude that something is so many
percent faster , cheaper, smaller, or otherwise better that something else. Put the result there, in numbers.
Avoid vague, hand-waving results such as “very”, “small”, or “significant” . If you must be vague, you are
only given license to do so when you can talk about orders-of-magnitude improvement . There is a tension
here in that you should not provide numbers that can be easily misinterpreted, but on the other hand you do
not have room for all the caveats.

 CONCLUSIONS

What are the implications of your answer? Is it going to change the world (unlikely), be a significant “win”,
be a nice hack , or simply serve as a road sign indicating that this path is a waste of time (all of the
previous results are useful). Are , your results general, potentially generalizable, or specific to a particular
case?

OTHER CONSIDERATIONS

An abstract must be a fully self-contained , capsule description of the paper. It can’t assume ( or
attempt to provoke) the reader into flipping through looking for an explanation of what is meant by some
vague statement. It must make sense all by itself. Some points to consider include:

* Meet the word count limitation. If your abstract runs too long, either it will be rejected or
someone will take a chainsaw to it to get it down to size. Your purposes will be better served by doing
 30
the difficulty task of cutting yourself, rather that leaving it to someone else who might, be more
incrested in meeting size restrictions than an representing your efforts
in the best possible manner. An abstract word limit of 150 to 200 words is common.

 Any major restrictions or limitations on the results should be stated, if only by using “weasel-
words” such as “might” , “could”, “may” and “seem”.

 Think of a half-dozen search phrases and keywords that people looking for your work might
use. Be sure that those exact phrases appears in your abstract , so that they will turn up at the
top of a search result listing.

 Usually the context of a paper is set by the publication it appears in (for example , IEEE
computer magazines articles are generally about computer technology). But , if you r paper
appears in a some what un-traditional venue, be sure to include in the problem statement
the domain or topic area that it is really applicable to.

 Some publications request “keywords” . These have two purposes. They are used to facilitate
keyword index searches. Which are greatly reduced in importance now that on-line abstract
text searching is commonly used. However , they are also used to assign papers to review
committees or editors, which can be extremely important to your fate. So make sure that the
keyword’s you pick make assigning your paper to a review category obvious ( for example,
if there is a list of conference topics, use your chosen topic area as one of the keyword
tuples).

CONCLUSION

Writing an efficient abstract is hard work, but will repay you with increased impact on the
world by enticing people to read your publications. Make sure that all the components of a good abstract
are included in the one you write.

FURTHER READING

Mchaelson , Herbert, How to write & publish Engineering Papers and Reports, Oryx Press, 1990.
Chapter 6 discusses abstracts.
Cremmins, Edward, The art of abstracting 2nd Edition, info Resources Press , April 1996. This is an
entire book about abstracting , written primarily for professional abstracts.
 31

(A typical specimen of table of contents)

<Font Style Times New Roman>

TABLE OF CONTENTS

CHAPTER NO. TITLE PAGE NO.

ABSTRACT iii
LIST OF TABLE xvi
LIST OF FIGURES xviii
LIST OF SYMBOLS xxvii

1. INTRODUCTION 1

1.1 GENERAL 1
1.2 .... ......... 2
1.2.1 General 5
1.2.2 ........... 12
1.2.2.1 General 19
1.2.2.2 . . . . . . . . . . 25
1.2.2.3 . . . . . . 29
1.2.3 . . . . . . . . . . . . 30
1.3 . . . . . . . . . . .. 45
1.4 .................. 58
2. LITERATURE REVIEW 69
2.1 GENERAL 75
2.2 .......... 99
2.2 …………… 100

3. ……………………….
 32

---------------

MCA Regulations are same as M.E./M.Tech Regulations

ANDHRAUNIVERSITY
REGULATIONS RELATING TO MASTER OF ENGINEERING (M.E)/ MASTER OF TECHNOLOGY
(M.TECH)/ MASTER OF PLANNING DEGREE EXAMINATIONS UNDER SEMESTER SYSTEM

(with effect from 2007 – 2008)

1. The Degree of Master of Engineering (2 - year course in 4 semesters) / Master of Technology (2 -

year course in 4 semesters)/Master of Planning (2 - year course in 4 semesters) will be conferred on
a candidate who satisfies the following conditions.

(i) The candidate must have passed the Bachelor of Engineering/Technology/Architecture Degree in
appropriate branch of this University or an examination recognized by this University as equivalent there
to and secured not less than 55% marks in aggregate.

However, candidates who have qualified themselves at the GATE examination shall be given
priority in admission to M.E./M.Tech./M.Planning courses. Further, candidates seeking admission in to
specified P.G. courses shall be required to appear at a separate entrance test(s) to be conducted by the
University. In implementing the above regulation, the following guidelines are stipulated.

(a) Total number of candidates admitted in to a course (specialization) with or without GATE score
should not exceed approved sanctioned strength.
(b) Only after all GATE qualified candidates have been considered for admission, non GATE
candidates may be considered for admission in to those courses and under those categories (i.e.,
O.C., S.C., S.T., B.C., etc.) in which vacancies exist.

(ii) After passing B.E./B.Tech./B.Arch. Degree examination in the appropriate branch of this
University or an examination recognized by this University as equivalent thereto, the candidate should
have undergone a regular courses of study as here in after prescribed, for not less than four semesters
(each semester of about 16 weeks duration) and passed the prescribed examination.

(iii) Candidates pursuing the courses on a part-time basis (Evening course) should be employed in any
recognized local establishment or Institution or Government service and shall have a minimum of two
years experience after graduation. The duration of the course for part-time students shall be six
semesters.
 33
(iv) Members of the teaching staff of the University College of Engineering and other local
Engineering colleges may be permitted to undergo the course on a part-time basis (Daytime) and
complete the whole course and examination in not less than six semesters taking two or three papers
only in a semester.

1.1 The normal duration of the course is 2 academic years for M.E / M.Tech/M.Planning Degree.

1.2 Candidates shall have pursued a regular course of study , as detailed below, for not less than two
academic years, and shall have fulfilled the academic requirements laid down and shall have passed
all the prescribed examinations.

2.1 A regular course of study during an academic year/semester means a minimum attendance of 75% of
all the subjects computed by totaling the number of periods conducted over the semester as specified
in the schemes of instructions.

However, in special cases and for sufficient causes shown, Chairman of Board of Governors may, on
the recommendation of the Principal, Dean (Academic Affairs) and Head of the Department
concerned, condone the deficiency in the average attendance to an extent of 10% for reasons such as
ill-health, if the application for condonation is submitted at the time of actual illness and is supported
by certificate of authorized Medical Officer approved by the Principal.

In the case of students, who participate in co- curricular, extra curricular activities like student
seminars, N.S.S, N.C.C, Inter-collegiate tournaments approved by the College and any other
activities conducted by Andhra University, Inter-University tournaments conducted by the Inter-
University Boards and any such other activities involving the representation of the College/University
with the prior approval of the Principal, the candidate may be deemed to have attended the college
during the actual period of such activity, solely for the purpose of attendance.

2.2 A candidate who cannot satisfy the attendance requirements as specified in the clause 2.1, because of
late admission under special circumstances, reasonable and acceptable to the College of Engineering
on the basis of documents, shall attend at least 50% of the total scheduled periods during that semester
and shall have attended at least 90% of the total periods of instructions held from the date of
admission.

2.3 The criterion for promotion from 1 st semester to 2nd semester and to the subsequent semesters is based
on the requisite attendance put up by the candidate.

2.4 A candidate who fails to satisfy the regulation under the clause 2.1 or 2.2, shall not be allowed for the
University examinations at the end of the semester and shall not be allowed for promotion to the next
semester of study. He/ She shall be required to repeat the entire course of study of that semester.

3.1 The period of instruction shall comprise of a minimum of 15/16 weeks. The semester end
examinations shall ordinarily be held after completion of 15/16 weeks.
 34
3.2 There shall be no supplementary examinations.
4. The examinations for the M.E/M. Tech Degree shall be conducted as per the prescribed Schemes in all
the branches of study offered by AU College of Engineering (Autonomous).

5. Assessment for the award of the Degree shall consist of

(i) Internal evaluation of the work done by the students during the semester for 30 marks in each
theory subject and for 50 marks or such other marks prescribed in the scheme of examination, in
each practical/ Industrial Training/project.

(ii) Semester end examination as detailed in the scheme of examination for 70 marks in each theory
subject as given in the scheme.
.
5.1 The marks for the internal evaluation shall be awarded by the concerned teachers based on class work,
quiz, viva-voce, two mid-examinations out of which one may be online examination etc., according to
a scheme/schedule to be notified by the Department at the beginning of the semester.

5.2 The semester end examination in each theory subject, for a maximum of 70 marks, shall be conducted
by the University/College.
5.3 The semester end examination in practical/Industrial Training/ project for 50 marks or such other
marks prescribed in the scheme of examination shall be conducted by the Department.
5.4 Candidates shall be required to produce complete and certified records of the work done by them in
each of the practical subjects at the time of semester end practical examination, failing which they will
not be allowed for such examination.
5.5 The candidate is required to obtain a minimum of 28 marks out of 70 in the semester end examination.
5.6 There is no sessional marks minimum in each subject.

5.7 THE MARKS THUS OBTAINED WILL BE CONVERTED TO GRADES ON A 10.0 POINT
SCALE AND THEN TO SEMESTER GRADE POINT AVERAGE (SGPA) AND
SUBSEQUENTLY CUMULATIVE GRADE POINT AVERAGE IS AWARDED AT THE END OF
THE COURSE
GRADES AND GRADE POINT DETAILS

S. No Range of Marks Grade Grade Points

1. ≥ 90% O 10.0 points
2. 80% - 89% A 9.0
3. 70% - 79% B 8.0
 35
4. 60% - 69% C 7.0
5. 55% - 59% D 6.0
6. 50% - 54% E 5.0
7. < 50% F (Fail) 0.0
The grade W represents failure due
8. to insufficient attendance in a year W 0.0
or semester
Incomplete (subsequently to be
9. changed into pass or E to O or F I 0.0
grade in the same semester)

Further these letter grades carry points associated with them in a quantified hierarchy.

For example if a student gets the Grades in one semester A, A, B, B, B, D in the subjects having 2(s 1),
4(s2), 4(s3), 4(s4), 4(s5), 2(s6) credits respectively,

The SGPA is calculated from the following :

SGPA = [9(A)  2(s1) + 9(A)  4(s2) + 8(B)  4(s3) + 8(B)  4(s4) + 8(B)  4(s5) + 6(D)  2(s6)] /
[2(s1) + 4(s2) + 4(s3) + 4(s4) + 4(s5) + 2(s6)]
=162/20 = 8.1

If a student gets the grades in another semester D, A, B, C, A, E, A in the subjects having credits
4(s1), 2(s2), 4(s3), 2(s4), 4(s5), 4(s6), 2(s7) respectively,

The SGPA is

SGPA = [6(D)  4(s1) + 9(A)  2(s2) + 8(B)  4(s3) + 7(C)  2(s4) + 9(A)  4(s5) + 5(E)  4(s6) + 9(A)
 2(s7 ) ] / [4(s1) + 2(s2) + 4(s3) + 2(s4) + 4(s5) + 4(s6) + 2(s7)]
= 162/22 = 7.36

The CGPA of the above two semesters is

CGPA = (9  2 + 9  4 + 8  4 + 8  4 + 8  4 + 6  2 + 6  4 + 9  2 + 8  4 + 7  2 + 9 4 + 5  9
+ 9  2) /(22 + 20)
= 7.7

6.1 A candidate shall be declared to have passed in any subject (theory) if he /she secures not less than
“E” Grade in theory and practical/industrial training/project, provided that the result otherwise is
withheld.

6.2 A candidate shall be deemed to have satisfied the minimum requirement for the award of the Degree;

(i) If he/she is declared to have passed all the subjects (theory and practical subjects) included
in the Scheme of Examination of 4 semesters
 36
and

(ii) If he/she secures 5.0 CGPA by the end of fourth semester.

6.3 A candidate may be permitted to improve his/her performance by reappearing for the whole of the
University examinations, only in all the theory subjects of a semester , after completion of the 2
years course of study and during the four consecutive examinations only.

Such an improvement can be availed of only once, for each of the semester examinations of the course
of study, provided that all the subjects of the semester shall have been passed as per the clause 6.1.
When considered in its totality, better of the two performances (as a whole but not subject wise) shall
be taken into consideration for the purpose of awarding First Class. There shall be no subject wise
improvement permitted in any semester of study for the above purpose. In any case, no such
improvement shall be permitted after completion of four academic years from the year of admission.

6.4 Candidates, who fail to satisfy clause 6.2 (ii) may be permitted to obtain 5.0 CGPA within 2 years
after completing the course of study by appearing at the University examinations only of
M.E/M.Tech/M.Planning subjects of their choice. Any candidate, who fails to attain the minimum
CGPA of 5.0 even after such appearances, during a total of four academic years from the year of
admission, shall become ineligible for the award of M.E/ M.Tech/M.Planing Degree.

6.5 There shall be no provision for the improvement of internal assessment marks in any theory or
practical subject in any semester of study.

7. The viva voce examination on the dissertation or project or thesis shall be conducted by a Board
of minimum four examiners consisting of

1. The Head of the Department as Chairman

2. Chairman, Board of studies of the concerned Department
3. Internal Guide and External Guide ( if any)
4. External examiner ( from other University/College/Institution/)

The valuation of the dissertation, project or thesis shall be as provided in the scheme of examination of
each course.

8. Whenever there is a change of regulations, scheme and syllabi, a candidate who fails in any subject
or who wants to improve his/her performance as per clause 6.4 , will be permitted to appear for the
University examinations conducted during the subsequent 2 years only, under the previous
regulations, scheme and syllabi.

9. All the candidates who have satisfied the minimum requirement as specified above, shall be arranged
in two classes (first class and second class) based on the CGPA obtained in the examinations.

(i) The First Class is awarded for those who have obtained a CGPA of 6.0 and above,

and

(ii) The Second Class is awarded for those who obtained a CGPA of 5.0 and above but less than 6.0.
 37
Candidates who pass in first class without failure in any one of the subjects in the entire course of
study and obtained a CGPA of 7.0 and above shall be declared to have passed in First Class with
Distinction. However, candidates who have improved their performance as per clause 6.4 shall not be
eligible to be awarded First Class with Distinction.

10. The CGPA can be converted to percentage by multiplying CGPA with 10.0, in case of requirement by
any other University or any other purpose.