Professional Documents
Culture Documents
Introduction
The project dissertation is a part of curriculum, occupying your time from the end of
seventh semester through to the end of eight. You may find it to be enjoyable and
stimulating thing of your course. The objectives of the project dissertation are to
encourage and reward individual inventiveness. The project will develop your ability to:
• Design and Implement a project from initial stage, through thorough analysis of
the problem area.
• Plan, schedule, and monitor your work: You should demonstrate your work in
different of ways, e.g. being prepared for meetings with your project guide;
• Defend your ideas and presentations: Plan ahead, find evidence and describe
your ideas;
• Use library and other information sources: This demonstrates your ability to work
on your own and find further relevant information and tools for your project;
• Apply relevant tools and techniques: understand the theory and demonstrate the
practical skills;
• Communicate your findings (e.g. written report, Underer and viva).
• Finally, to demonstrate your work to the examiners for final evaluation.
The project constitutes one of the major parts of your degree. 03 credits will be awarded
for 'Project - I' and 12 credits will be awarded for 'Senior Project'.
Your project is of individual one and may fit into one of the following categories.
Experimental: These projects involve the investigation and evaluation of a new piece of
technology. It may involve a substantial amount of software/hardware implementation
and the application of scientific measurements and investigations to ascertain its
properties and usefulness. Such a project will necessarily describe the theoretical
foundations of the technology, implementation and the experimental procedures used
and an analysis of the results, together with an assessment of the relationship between
the project work and other published work. There should be a discussion of the problems
of existing methods and how the new ideas overcome any of these problems.
Design and build: These projects should involve the main activities associated with the
development of a well-engineered software system for carrying out the particular task
required by the project: requirements analysis, specification, program design,
implementation, system testing (including field testing and user comments),
documentation and maintenance. Most of these stages are likely to be included in the
report and the reasons for the various design decisions will be carefully described.
Project stages
You must complete the following stages as per the schedule. The effective management
of your time could be a major factor in the quality of your project. You should start basic
work on your project during the semester 6, then work consistently during the semester
7 and 8. Each project has three assessments –
i. the supervisor (throughout the project period),
ii. The committee constituted in the department (during the middle and end of
the project period) and
iii. The examiners (internal examiners during the process and internal & external
examiners during the end of the project period). The schedule is given as
follows:
Assistance
• Progress: If things start to go wrong it is important to talk to your project
supervisor, your proctor, the project coordinator or to the Head. This will help us
to help you more quickly and effectively.
• Extensions to deadlines: Extensions may be granted if you are ill
(obtain a valid medical certificate), or any other exceptional extenuating
circumstances. You must inform your supervisor about the above circumstances.
The medical certificate must be submitted to the department forwarded by the
project guide and the proctor.
• Late start: If you are not allocated a project until the 3rd week of
semester VII, you must approach the project coordinator, the proctor or the head
of the department and you can still meet the deadlines listed above. You should
make sure that your supervisor records the date that you start your project as
this detail may be useful when the project is assessed.
Stage 1 - Selecting a Project
This takes place during semester VI of your programme.
• Project preparation period: Read the project outlines, consult individual
lecturers about their areas of interest.
• Return form-1: Submit to the project coordinator within the deadline.
• Project allocation: You will be allocated a project based on your submitted
choices. Your previous performance may be considered for the allotment of
supervisor. If your choices are not available then you may be asked to submit
some more choices.
• Meet with supervisor: Immediate to the announcement of supervisor, you
should obtain the date for the meeting to discuss your project in greater detail,
gathering references and reading material curing the vacation. If your supervisor
is unavailable for a meeting you may request him for the list of materials via e-
mail.
Stage 2 - Synopsis Submission
You are required to submit two copies of the project synopsis to the coordinator. This
will be read by both your supervisor and other internal examiner. Your supervisor will
then give feedback in a subsequent meeting with you. If this feedback has not happened
within two weeks of submitting the report, please contact the Project coordinator.
This report sets the scene for your project work. It should discuss the relevant
background to the project and identify some of the problems and processes involved in
the work. The report should be no more than 3 A4 pages in length.
The main component of this report will be an extensive literature survey (or similar
technology/mathematical survey for certain types of project). In addition, the report
should contain the description of the work done so far and a clear presentation of what
the project is aiming to achieve in the subsequent semester. It is expected that the
project will be well under way at this stage. The contents of the report should be 10-15
A4 pages long. Many pitfalls can be avoided if you submit a draft of your report to
your supervisor two weeks before the deadline.
Assessment
• The examiners will examine the candidate. Accordingly, suggestions will be
made. Project Guide should monitor implementation of the suggestions during the
remaining period of the project work.
Attendance at the Underer session is compulsory for all the candidates. Academic staff
will be there, since they will be marking your Underers, asking you questions and
assessing your performance. It is open to all.
Assessment
You will be assessed on your ability to summarise your work and professionally present it
in an interesting manner. Three areas will be focussed on in the assessment process:
Assessment
The supervisor and second examiner will mark the final dissertation independently. Each
examiner will submit the Form-2 independently and submit the Form-3 together. Also
included below is a table that gives an indication of what is being looked for in the
overall work - note however that this is only a guide. The following list gives an
indication of what is being looked for in the overall work. Note however that this is only a
guide.
Dissertation structure
There are different types of project and so it is difficult to produce a detailed set of
recommendations to suit every single dissertation. Thus the dissertation structure given
below is only a suggestion.
• Title page
• Certificate
• Signed declaration
• Abstract
• Acknowledgments
• Contents
• Chapter 1: Introduction
• Chapter 2: Literature Review
• Chapter 3 onwards: Requirements and analysis/Design/Implementation and
testing/ Results and discussion etc.
• Final Chapter Conclusions
• References
• Appendices
• Program code: will be collected electronically, and should not be printed
Title page format
MSRIT Emblem
LOGO
CERTIFICATE
External Viva-Voce
1.
2.
Abstract
This should be two or three short paragraphs (100-300 words total), summarising the
dissertation. It is important that this is not just a restatement of the original project
outline. A suggested flow is background, project aims and main achievements. From the
abstract a reader should be able to ascertain if the project is of interest to them and
presents results of which they would like to know more details.
Acknowledgments
Thanks to whoever may have helped you in any way.
Contents
Contents include titles and page numbers of all sections and subsections. Chapter 1
begins on page 1. Use roman numerals for all previous pages, eg. title page (i), abstract
(ii), acknowledgments (iii) and contents (iv).
The best often include a separate list of all the figures (List of Figures) in the dissertation
(figure number, label, page number), and a separate list of all tables (List of Tables) in
the dissertation (table number, label, page number).
Chapter 1: Introduction
The introduction has several purposes. First one is to set the scene for the project by
giving a little relevant background information. Second one is to clearly elucidate the
aims, objectives and scope of the project. If the project involves the solution of a
specific problem or the production of a specific system this should be clearly specified in
an informal way. Finally, the introduction should summarise the remaining chapters of
the dissertation.
Chapter 2: Literature Review
This chapter is open for discussion. The main thrust of this chapter is to review of
relevant work of other authors and the relationship between their and your work. If
several other people have done closely related work in a different way then highlight the
reasons for your approach here. Project1 report may be helpful at this point of time.
A literature review is not simply an annotated list of papers you may have read, the cited
papers should be compared and contrasted. A literature review should cover a range of
relevant material to your project. Everything you use should be cited by reference. As
an example: "...some early work by Brooks [1] suggests that throwing men at a problem
is counter-productive". This would then be listed in the reference section as follows:
Everything that you write must be your own words and you must cite other people using
references. You may also quote sentences from the work of others. These must be
included in quotation marks and again the relevant work must be cited. Your signed
declaration means that you will fail your dissertation if you do not cite the work of
others.
Chapter 3 onwards:
Subsequent chapters may cover the requirement and analysis, Design, implementation
and testing, results and discussion etc. This may vary from one project type to another.
Guides are requested to go through the report thoroughly and advice the student
accordingly.
Final Chapter: Conclusions
The conclusions can be summarised in a fairly short chapter (2 or 3 pages). This chapter
brings together many of the points that you will have made in other chapters, especially
in the results and discussion chapter. Do not be afraid of repeating some of your earlier
statements here, albeit using different wording. This chapter may contain Goals
achieved, and future scope.
Goals achieved - describes the degree to which the findings support the original
objectives laid out for the project. The goals may be partially or fully achieved.
Further work - describes the new areas of investigation prompted by developments, and
parts of the work which were not completed due to time constraints and/or problems
encountered.
Appendices
These may be provided to include further details of results, mathematical derivations,
certain illustrative parts of program code (e.g. class interfaces), user documentation, log
of project milestones. In particular, if there are technical details of the work done that
might be useful to others who wish to build on this work, but that are not sufficiently
important to the project as a whole to justify being discussed in the main body of the
dissertation, then they should be included as appendices.
Program code
Do not include an appendix containing all your source code listings – instead, a CD may
enclose along with the report. What may be worth doing, perhaps, is that if there are
any code fragments of particular novelty, then you could include these in an appendix,
so that they could be referenced in any descriptions in the main text of the chapters.
Also a copy of the source code should be submitted to coordinator along with inputs.
Form-1
USN Names
1. 1.
2. 2.
3. 3.
4. 4.
Contact number:
E-mail address:
Guide Assigned:
Programme:
…………………………………………………………………………………………………………………..
Observations :
Project Guide :
Second Examiner :
Form-3
………………………………………………………………………………………………….
Programme :
Observations :
Project Guide :
Second Examiner:
Form-4A
M.S. Ramaiah Institute of Technology
(Autonomous Institute, Affiliated to VTU)
Department of Information Science & Engineering
Total
Name of the Evaluator Signature with date
Form-4B
M.S. Ramaiah Institute of Technology
(Autonomous Institute, Affiliated to VTU)
Department of Information Science & Engineering
INTERNAL EXAMINER
………………………………………………………………………………………………….
Total