PROJECT REPORT DOCUMENTATION GUIDELINESS

(Student must and should follow the guidelines given below)

The documentation should be arranged as per IEEE standards as detailed below:

1.

Outer Title page over black bounded copy As per format (Annexure I). Certificate As per format, duly signed by the guide (Annexure II).

2.

3. Abstract in about 500 words. The Abstract This short section, which is on a separate page following the title page, is used to give a clear picture of the aims and methods and to summaries briefly the principal conclusions. It is intended to provide a frame of reference that will allow the nature of the project to appreciate quickly. It is quite difficult to illustrate in a few words what your project set out to do. You may need several attempts before you achieve a sufficiently brief, informative statement. It is recommended that you write this section last, to ensure that it accurately reflects what is in the main body of the thesis. 4. Acknowledgment. Acknowledgements You may wish to acknowledge the help given to you in the preparation of your thesis. If so, acknowledgements come after the abstract page. 5. List of Figures with page numbers.
1

6. List of Tables with page numbers.

7. List of Abbreviations. 8. Contents a. Introduction Main Introduction about the project. b. Chapter I, Chapter I I, . Chapter N. c. Conclusions. d. Bibliography / References. e. Appendixes. All the pages of items from 3 to 9 above should be numbered with small roman letters ( i, ii, iii, ..). There should be a Main Introduction in the beginning about the project work. Then the Chapter I & II etc. to be arranged. Every Chapter should have an Introduction in the beginning about that chapter and conclusions at the end of the chapter. All the pages starting from Introduction to last page should be numbered in serial order.

 The sub headings of each chapter should be bold and number as 1.0, 1.1, 1.2, etc.

The last chapter should be of conclusions. The References and Bibliography to be enclosed. Finally Appendixes etc to be included. All the numbers of the above items and chapters should be depicted in the contents at the side of the Titles / Sub Titles.

( Annexure I )

TITLE OF THE PROJECT

(Submitted in partial fulfillment of the academic requirements for the award of Degree of Bachelor of Technology Computer Science & Engineering )

By ROLL NOs & NAMEs OF THE CANDIDATES

UNDER THE ESTEEMED GUIDANCE OF Guides Name with designation

NALLA MALLA REDDY ENGINEERING COLLEGE

(Affiliated to JNTU, Approved by AICTE)
DIVYANAGAR 500 088 R.R. Dt., A..P.

(Write Batch No.)

( Annexure III )

NALLA MALLA REDDY ENGINEERING COLLEGE

DIVYANAGAR 500 088 R.R. Dt., A..P. (Affiliated to JNTU, Approved by AICTE)

Department of Computer Science Engineering,

CERTIFICATE
This is to certify that this is a bonafide record of the Project Work done satisfactorily at Nalla Malla Reddy Engineering College by Mr./Ms.______________ _____________ in partial fulfillment of his / her B.Tech Examination.

Internal Guide

HOD Department of Computer Science & Engineering

External Examiner

CHAPTERS Chapter 1: Introduction Chapter 2: Requirement Specification (SRS). Chapter 3: Analysis Chapter 4: Design Chapter 5: Test cases and Testing Chapter 1: Introduction Chapter 6: GUI Screens. Chapter 7: Reports Chapter 8: Conclusions or Results Chapter 9: Bibliography Chapter 10: References Chapter 11: Appendixes

The introduction sets out the background to the project, states the problem investigated, notes the central focus of the investigation and mentions the proposed contribution to practical or theoretical issues. It is important that the introduction gives a clear idea of the motivation for the work - why is it worth doing? and who will benefit from the work?
Write detailed introduction to the whole project. Chapter 2: Requirement Specification (SRS). Write SRS according to IEEE 830 standard: Chapter 3: Analysis Only Object Oriented System Development using UML should be used for the development of the project. ii) USE-CASE Model Identifying and listing the Use-Cases. Writing Use-Case description tables
6

USE CASE NAME: PARTICIPATING ACTORS: DESCRIPTION: PRE-CONDITION: TYPICAL COURSE OF EVENTS(Main Flow): Step 1: Step 2: Step 3: Step 4: Step 5: Step 6: Step 7: Step 8: Step 9: ALTERNATE FLOW : AF 1: AF 2: AF 3: AF 4: POST-CONDITION: NON FUNCTIONAL REQ.

USE CASE ID:

Actor Action

System Response

Drawing Use-Case diagram Draw Activity diagrams shows different activities of the objects in realizing the Use-Case. Draw State diagrams where ever necessary. iii) ANALYSIS Model Identifying Analysis Class (In terms of Boundary, Control and entity Class). Draw Collaboration diagrams using analysis class for respective Use-Case diagrams. Draw Sequence diagrams using analysis class for respective UseCase diagrams. Chapter 4: Design Model ARCHITECTURAL DESIGN . INTERFACE DESIGN.
7

 DATA DESIGN. COMPONENT DESIGN. DEPLOYMENT DESIGN. Chapter 5: Test cases and Testing Chapter 6: GUI Screens. Chapter 7: Reports Chapter 8: Conclusions or Results

Conclusions Before writing this section, it is important to read through the whole thesis and make a note of key points. Only conclusions that can be justifiably drawn from the results should be made, and avoid including an opinion for which no evidence is provided in the thesis. Readers who want a quick idea of what the project is about will look at the abstract, possibly the introduction and almost certainly at the conclusions. Therefore, this section should be clearly expressed to enable readers to readily understand what work has been done and the conclusions that have been drawn from the results. Results This is the heart of the thesis and will consist of text plus graphs, tables and figure, depending on the nature of the project. The way results are presented is important. Tables, charts, graphs and other figures should illustrate and illuminate the text. The text, which should be written after the results have been obtained and presented as figures, should not duplicate information in the tables and figures. It should highlight the significant aspects of the findings, so that all relevant facts are presented in a way that draws the reader's attention to what is most important. For design projects results include the measurements and observations
8

made to assess the design with respect to its functional and performance specifications.

Chapter 9: Future Work

Future Work This section includes the main aspects of the project that require further development. Each aspect has to be covered in sufficient depth and be supported by argument. Many projects are continued by other students the following year, so this section should provide them with good guidance on what the next steps should be.
Chapter 9: Bibliography List all the books and web sites that were gone through for any purpose. Chapter 10: References

All theses will require a list of references. References give specific details about books and articles that have been referred to in the thesis. The followings list the information the reference should contain. For books: author, title of book place of publisher, publication, date, pages referenced (if applicable). For articles: author, title of article in quotes, name of journal, volume number, issue, pages referenced, and year. For web addresses: author (if known), URL, date on which the page was accessed (important to include this), organisation (if applicable), title of page/site, date page was written/last updated (if known). If you look at the references in a number of different textbooks and journals you will find that there are a number of
9

different styles, varying in their numbering systems, ordering of information, and their use of quotes, Italics and parenthesis. You may use whatever style you wish (consult your supervisor if necessary), however, you must be consistent and use the same style for all references. Some Example References 1. E.D. Fabricius, Introduction to VLSI Design, McGraw-Hill, New York, 1990, pp. 137-139. 2. J.S. Oakland, Statistical Quality Control (2nd edition). ButterworthHeinmann, Oxford, 1990. 3. J.J. Plunkett and B.G. Dale, "Quality costs a critique of some economic cost of quality models", Int. J. Prod. Res., Vol. 26, No. 11, pp. 1713-1726. 4. M. Mrup "Design for Quality", PhD Thesis, Institute for Engineering Design, Technical University of Denmark, Lyngby, 1994.
Chapter 11: Appendixes

Appendices Appendices should include items which are required for reference purposes, but which would clutter (confuse)the main body of the thesis. Data sheets should only be included if they are referred to in detail in the text.
Code should be included. Explanation of certain topics which were used (like formulae, concepts, theorems etc.) should be written here. Each topic should be included as Appendix A, B, C, etc.

Text Font Use Times New Roman font (or similar) unless stated otherwise.
10

Thesis Title 20 points type size Upper case Bold Arial normal font (or similar) Centred in the middle of the page Authors name 14 points type size Page Numbers

Upper and lower case for name Normal (not italic) Bold Centred under the title Supervisors information etc As authors name Centred name under the authors

All pages must be numbered at the bottom centre. If there are difficulties with numbering due to use of pages printed from different software packages numbering by hand will be accepted. Contents List There must be a contents list containing section numbers and titles and their pages numbers. Most word processors have facilities to create contents lists automatically if you define you section headings correctly.

Major-Headings 14 point type size Upper and lower case Bold normal font Aligned with left margin

Sub-Headings 12 point type size Upper and lower case Bold Normal Aligned with left margin
11

Text Information 12 point type size TimesNewRoman Normal (others when necessary; e.g. italic) Justified 1.5 line spacing, 2 lines between paragraphs Quotations If other text from other authors is quoted (copied) it must be indented from the main text and be in a different font (e.g. Italics) so that it is distinct from the main text. The source must be referenced and the copy must be accurate. This includes text from web pages. Figures, Tables, Charts and Graphs All figures must be given a title and a figure numbers 10 point minimum type size for text on figures Captions in upper and lower case Caption centred under the graph or chart. If a figure is copied or very similar to one from another author the source must be referenced (this includes figures taken from web pages). A4 Paper Size - Margins Top margin 2.6 cm or 1. Bottom margin 2.0 cm or 0.8. Left margin 3.2 cm 1.25. Right margin 1.8 cm or 0.7.

12

13