FORMAT FOR PREPARATION OF PROJECT REPORT FOR BACHELOR OF ENGINEERING 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 & Declaration 3. Acknowledgment 4. Abstract 5. Table of Contents 6. List of Tables 7. List of Figures 8. List of Symbols, Abbreviations and Nomenclature 9. Chapters 10. Appendices 11. 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 Hard cover/Card board. The cover should be printed in golden letters with black background and the text for printing should be identical. 3. PREPARATION FORMAT: 3.1 3.2 Cover Page & Title Page A specimen copy of the Cover page & Title page of the project report are given in Appendix 1. Bonafide Certificate & Declaration The Bonafide Certificate & Declaration shall be in double line spacing using Font Style Times New Roman and Font Size 14, as per the format in Appendix 2 & 3 respectively. The certificate shall carry the guides signature and shall be followed by the guides name, academic designation (not any other responsibilities of administrative nature), department and full address of the institution where the

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 1

guide has guided the student. The term GUIDE must be typed in capital letters between the guides name and academic designation. 3.3 3.4 Abstract Abstract should be 1 page synopsis of the project report typed one & half line spacing, Font Style Times New Roman and Font Size 12. 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 & Declaration 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 4 . 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. 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. 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. Chapters The chapters may be broadly divided into 4 parts (i) Introductory chapter, (ii) problem defenation (iii) Chapters developing the main theme of the project work (iv) future scope 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.

3.5

3.6

3.7

3.8

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

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 2

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.421425. Barnard, R.W. and Kellogg, C. (1980) Applications of Convolution Operators to Problems in Univalent Function Theory, Michigan Mach, J., Vol.27, pp.8194. 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.

2.

3.

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. GUIDELINES FOR STUDENTs The theme / topic of the project should be current and based on latest technology or as mentioned by the Dr.B.A.M. University. The candidate has to give a project brief or synopsis to the HODs through the guide(s) of his topic before commencing the project work. The length of the report as mentioned in the respective syllabus of Dr.B.A.M. University. The project must be Card-board Bounded with Lamination Sheet. (Spiral binding and other forms of binding will not be accepted). The project must be

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 3

submitted in * 3 + n duly signed by the Guide. The project should be neatly typed on one side and in A4 size Paper only. * 3 + n (where 3 = one each to examiner, department & Library & n= no of students in the project) Following Typing Instructions should be followed. i. One and a half spacing should be used for typing the general text. The general text shall be justified and typed in the Font style Times New Roman and Font size 12. ii. Subheading shall be typed in the Font style Times New Roman and Font size 12 and bold. iii. Heading shall be typed in the Font style Times New Roman and Font size 14 and bold. *****

SAVITRIBAI PHULE WOMENS ENGINEERING COLLEGE Sharnapur, Aurangabad Pin Code 431 003
29 march 2012 Instructions for project report writing 1. Prepare 2 + No of project members copies of your manuscripts. 2. The footer SPWEC, Computer Engineering Department 2012 should be included. (10, Times Roman, Center justified)

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 4

3. Main part of manuscripts should be Times Roman, 12 pts , justified and 1.5 line spacing. 4. Use paper size 8.5 x 11 or A4 (210 x 197 mm). Follow following margins. Margin Top Left Bottom Right Paper 8.5 x 11 1 1.5 1.25 1 Paper A4 25.4 mm 37 mm 32 mm 25.4 mm

5. All paragraphs will be 1.5 lines spaced with a double space between each paragraph. Each paragraph will begin with a five-space indentation. 6. Chapter tiles should be bold with 14 pt typed in all CAPITALS letters and should be aligning at the center of the page. 7. Section heading should be aligning at the left with 12 pt and bold and capitalized. 8. Section subheading should be aligning at the left with title case. 9. Leave two spaces between section heading and one space between two-section subheadings. 10. Illustrations (Charts, drawings, photographs and figures.) must be embedded in text. Illustrations must be sharp, clear, black and white. 11. References should be either in the order as they appear in the paper or in alphabetical order by the last name of the first author. 12. Symbols and notations if any should be included in nomenclature section only. 13. Order of report: - refer to reportformat2005.doc 14. All chapters, section heading and sub headings should be numbered. For chapter use numbers 1,2,3 and for sub headings 1.1,1.2, 1.3. And section subheadings 2.1.1,2.1.2 etc. Important dates to remember: -

Submission of soft copy and rough print of project report: 12th Apr 2012 Submission of final report and Hard copy of project report: 15th Apr 2012
(For Hard cover page and cover page)

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 5

APPENDIX 1 (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(S)

<Font Size 16>

in partial fulfillment for the award of the degree of

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

NAME OF THE DEGREE

<Font Size 16> IN

BRANCH OF STUDY
<Font Size 14>

Savitribai phule womens engineering college

<Font Size 16>

Sharnapur, Aurangabad Pin Code 415 708

<Font Size 14>

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 6

Dr. Babasaheb Ambedker marathewada university

<Font Size 16><1.5 line spacing>

MONTH & YEAR

<Font Size 14>

SPECIMEN

SOME PERFORMANCE ASPECTS CONSIDERATIONS OF A CLASS OF ARTIFICIAL NEURAL NETWORK

A PROJECT REPORT Submitted by

SANDHYA. A GAYATHRI.R

in partial fulfillment for the award of the degree of

BACHELOR OF ENGINEERING
in

INFORMATION TECHNOLOGY

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 7

SAVITRIBAI PHULE WOMENS ENGINEERING COLLEGE Sharnapur, Aurangabad Pin Code 415 708 DR. BABASAHEB AMBEDKER MARATHWADA UNIVERSITY

MAY 2012

APPENDIX 2 (A typical specimen of Bonafide Certificate) <Font Style Times New Roman>

DR. BABASAHEB AMBEDKER MARATHWADA UNIVERSITY

<Font Style Times New Roman size -16>

BONAFIDE CERTIFICATE
<Font Style Times New Roman size -16> <Font Style Times New Roman size -14>

Certified

that

this

project

report

.TITLE

OF

THE

PROJECT..

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 8

is the bonafide work of ..NAME OF THE CANDIDATE(S). who carried out the project work

under the designated guide and the said work is placed for approval before the examiners. The work carried is satisfactory for the award of degree of Bachelor in . Engineering of Dr. Babasaheb Ambedker Marathwada University.

Name & Signature Guide(s)

Name & Signature HOD

Name & Signature Internal Examiner

Name & Signature External Examiner

Name & Signature Principal

APPENDIX 3 (A typical specimen of Declaration) <Font Style Times New Roman>

DECLARATION
<Font Size 16>><BOLD><Centralized>

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 9

I/We hereby declare that the project entitled _____________ ____ ________ _____ ______ ________________________ submitted for the B.E. Degree is my/our original work and the project has not formed the basis for the award of any degree, associateship, fellowship or any other similar titles. Signature of the Student: Place: Date: Acknowledgements
First and foremost, I would like to thank my guide, Prof, for her guidance and support. I will forever remain grateful for the constant support and guidance extended by my guide, in making this project. Through our many discussions, he/she helped me to form and solidify ideas. The invaluable discussions I had with her and my colleagues, the penetrating questions he/she has put to me and the constant motivation, has all led to the development of the ideas presented in this project. I wish to express my sincere thanks to the Head of department, Prof also grateful thanks to Prof,, Prof., and the departmental staff members for their support. . I would also like to thank my wonderful colleagues for listening to my ideas, asking questions and providing feedback and suggestions for improving my ideas. I would like to thank all my friends for the continues encouragement and the positive support.

Miss..

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 10

Abstract
The trend in the development of large scale Object-Oriented systems has shifted toward testable, robust models with a focus on the prevention of faults and system failure. One process that supports the construction of robust software is testing. The basic unit of testing in an Java program is a class. There are number of classes exist in software having relation with each other. It is dicult to test each class or it may takes more time to test software. So as to reduce testing time it use class under test which produce card for that class which contains variables, methods, inheritance and other features of Object Oriented class then this card compares with existing testing techniques by implementing mapping algorithm. Result of mapping algorithm is produce cards one gives those testing techniques which is suitable for testing characteristics of that particular class and other gives list of characteristics that are not tested by any existing testing techniques. This report present a mapping algorithm that automates the process of identifying the testing techniques that are suitable for testing a given class. The algorithm accepts a class to be tested, generate the java card for given class i.e class under test(Cataloged entry i.e Classcard) then this Classcard map with the set of testing techniques available to the developer engaged in performing the test. Summary of class is based on the taxonomy that maps the features and characteristics of a classes in an object oriented system into feature properties(Variables, Methods) and Nomenclature. The output is generated after applying algorithm AutoIBTTCUTMap to classcard and the Implementation based testing techniques available to the tester represents the variable Result that references to three cards: 1. Result.Classcard is card for class that shows all characteristics of class. 2. Result.ClassTest - this card shows features of class suitably test by IBTTs.

APPENDIX 4 (A typical specimen of table of contents) <Font Style Times New Roman> TABLE OF CONTENTS CHAPTER NO. TITLE PAGE NO.

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 11

LIST OF TABLE LIST OF FIGURES LIST OF SYMBOLS

iv v vi

1.

INTRODUCTION 1.1 1.2 GENERAL ......... 1.2.1 1.2.2 General ..........

1 1 2 5 12 19 25 29 30 45 58 75 99 . 100

1.2.2.1 General 1.2.2.2 . . . . . . . . . . 1.2.2.3 . . . . . . . . . . 1.2.3 . . . . . . . . . . . . 1.3 1.4 2. 69 2.1 2.2 GENERAL ....... 2.2
Literature Review .. . . . . .

..................

: : :
Appendices References

Guidelines for writing Project Report Read all the following items before starting a writing project:

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 12

1. *Summary and conclusions should also contain such insights in

2. 3.
4.

5.

brief and also you must try to come up with some concrete improvements that can be done in this project. There should also be one paragraph that truly qualifies as a conclusion from your Literature survey. Generic outline of a Project report: Introduction, motivation for/definition of the problem, approaches for solving the problem, comparison of approaches, summary and conclusions. *Do not cut-and-paste figures from other sources. (If you must, cite the Figure number, etc of the source with permission). Always read your write-up at least THREE times in PRINTED FORM after you think you have finished it before submitting it. PRINT IT ON PAPER AND READ IT. Do NOT use your guide as a proof-reader. Specifically *Absolutely no spelling mistakes, no obvious errors e.g. due to wrong cut and pastes, no Figure/Table reference errors, no reference list formatting errors and no errors that have been pointed out below.

6. Pay attention to the format of references. Study how books, journal articles, conference articles, web sites, etc. are cited in a published article. Use that format. 7. IMPORTANT: Every sentence must follow from a previous sentence. Tell a story. Don't jump from one idea to another in consecutive sentences or consecutive paragraphs. 8. Please do not use the word ''works'' as in ''related works'' or ''other works'' or ''prior works'' when referring to existing literature. Correct usage: ''related work'' or ''other work'' or ''prior work.'' Make sure whether to use an ''s'' or not. 9. ''Notation'' not ''Notations. 10. Software, not Softwares. 11. Check your usage of singular and plural nouns. Should it be ''file transfers on circuit-switched networks'' or ''file transfer on circuitswitched network. It depends on the context. Pay attention. Even more important, check if the verb in the sentence corresponds to the noun with respect to it this singular vs. plural aspect. 12. Pay attention to the usage of the article "the". 13. Always cross-reference citations to references, figures, tables, section numbers, etc. 14. Always be consistent. For example if you refer to a node in a figure as "Node 1" in the text description of the figure, then

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 13

consistently use capital "N" even when the words "Node 1" occur in the middle of a sentence. Same thing applies to names of messages, parameters, etc. 15.Do not reference "forward." This means in Section 2, don't say this is explained in Section 4. Only exception is in the introduction section where you describe the whole outline of the paper. Or in a section introduction where you say what each sub-section does. 16.Use a comma before the last phrase if there are many phrases separated by commas in 1 sentence. Use "and" before the last phrase. Place the comma before the ''and''. 17.Quotes inside punctuation mark, could be a comma or a period, e.g., "Switch Mapping Table." 18.Always have exactly one space between the end of a sentence and the start of the next. 19. There should be a space after a comma also. 20. Always have a comma before "which" - use "that" instead of ''which'' in cases where a comma "feels" inappropriate. 21. If two words form an adjective, then use hyphen except if the first word ends with "ly." (*e.g. erroneously transmitted data vs. Fast-retransmit mechanism of TCP). 22. A paragraph needs a minimum of two sentences, i.e., no onesentence paragraphs. 23. Do not use words like ''don't'', ''doesnt,'' ''can't'' in technical writing. It should be ''do not,'' ''does not'', and ''cannot'' respectively. 24. Do not start a sentence with ''Because'' or ''And.'' 25. Draw a distinction between connection setup procedure'' where ''setup'' is a noun versus ''to set up a connection,'' where ''set'' is a verb. 26. Use present tense in the abstract, introduction and in the whole paper, except the conclusions and/or summary section. In the conclusions/summary section, use past tense. 27. When saying something like ''as shown in Equation (14)'' in your text, you should omit the word ''Equation.'' Just say (14).

Chapter 1 1 Introduction 1.1 Project Idea

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 14

1.2 Need of the Project

Chapter 2 2 Literature survey

Chapter 3 PROJECT WORK (Title of project) 3.1 Problem Statement and solution 3.1.1 Description of problem 3.1.2 solutiom 3.1.5 Hardware Resources Required 3.1.6 Software Resources Required 3.2 Area of Project
DFD Algorithm

Snap shot of output screen Testing and validation

Chapter 4 FUTURE WORK and CONCLUSION 4.1 FUTURE WORK Presently we have done the encryption and decryption of voice messages using Advanced Encryption Standard. The same can be done using different encryption standards as DES, triple DES and RC5 depending on the compatibility.

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 15

Encryption can also be done for other multimedia services to increase the security level of their transmission such as Video files etc

4.2 Conclusion
The Voice messages have been successfully encrypted at the senders server and decrypted at the receivers server. The encryption of voice messages gives the security feature to Asterisk user. It allows the voice-based messages to be carried in such a way over the network that it resists eavesdropping. Incorrect decipher key restricts the user from access to the original messages. Thus, AES algorithm has been used to enhance the security feature of Asterisk.

5. REFERENCES
REFERENCES
2 3 4 5 6 7 8 Paul Mahler, VoIP Telephony with Asterisk , Signate, July 2004. (ISBN-10 : 0975999206 ) Daemen, J. and Rijmen, V. Rijndael: The Advanced Encryptiom Standard Dr. Dobbs journal, March 2001 D Gomillion, B Dempster, Building Telephony Systems with Asterisk, Packt Publishing, September 2005. (ISBN-10 : 1904811159) J. Rosenberg, H. Schulzrinne, G. Camarillo rfc3261, June 2002 Bur Goode, Voice Over Internet Protocol, IEEE Chris Roberts, Voice Over IP, March 2005 VoIP specification, http://www.voipsurvival.com/VoIPSpecification.html

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 16

http://www.voip.org

10 http://www.Sipcenter.com

SPWEC, COMPUTER ENGINEERING DEPARTMENT 2012 17