This document provides guidelines for students to follow when preparing their six-week industrial training report at Lovely Professional University in India. It outlines the required format and structure of the report, including formatting of preliminary pages, chapters, tables, figures, and references. Key requirements include having 5 chapters (Introduction, Company Profile, Training/Project Identification, Implementation Details, and Results and Discussion), a minimum of 10 references, and specific formatting for the cover page, table of contents, and other elements. The guidelines are intended to help students submit reports that are of the highest quality and follow a consistent structure.
DISSERTATION GUIDELINE, The dissertation is a scholarly communication that demonstrates a specific point of view as a result of original research that is conducted by students during their graduate study. It is a requirement for an award of master degrees offered by Institute of Accountancy Arusha in collaboration with Coventry University. Dissertation includes a study of research methods and gives students the opportunity to enact a piece of individual research or problem-solving.
The directorate sets the minimum format of your dissertation while the content and the specific details is decided by you and your supervisor. It should also be noted that grammar, punctuation, spelling and other mechanical issues are your sole responsibility as a student.
DISSERTATION GUIDELINE, The dissertation is a scholarly communication that demonstrates a specific point of view as a result of original research that is conducted by students during their graduate study. It is a requirement for an award of master degrees offered by Institute of Accountancy Arusha in collaboration with Coventry University. Dissertation includes a study of research methods and gives students the opportunity to enact a piece of individual research or problem-solving.
The directorate sets the minimum format of your dissertation while the content and the specific details is decided by you and your supervisor. It should also be noted that grammar, punctuation, spelling and other mechanical issues are your sole responsibility as a student.
Assignment DetailsYou are required to submiti) Two (soft .docxssuser562afc1
Assignment Details
You are required to submit:
i) Two (soft bound for marking) complete printed copies; and
ii) One electronic copy of the Final Dissertation, including Appendices
Note: None of these copies of your dissertation will be returned to you. You will need to make further copies if you wish to keep your own copy of the report.
The two main reports must be bound so that pages cannot be easily removed. However, appendices containing bulky material may be grouped together separately in suitable binders or containers (A4 ring binders are acceptable). All such separate materials must have the dissertation title with the student's name, number, year of submission and supervisor's name clearly shown on the outside.
The word limit is 8,000 words (+/-10%). This excludes footnotes and appendices but includesquotations. The appendices should not normally exceed 2,000 words. Dissertations are assessed by quality – not quantity. Part of the technique of technical writing is to get over an unambiguous message in a clear and succinct document. Marks will be reduced if there is evidence of padding, duplication or inessential illustrations or appendices.
Remember:
· You must keep to the word limit
· You must demonstrate that you have met the learning outcomes
· As you construct and present your work, consider the assessment criteria
Presentation Instructions
It is your responsibility to ensure that your work is neatly and accurately presented.
Typical Example of Dissertation Format
i) Title Page
ii) Abstract
iii) Acknowledgements
iv) Contents Page
v) List of Illustrative Materials
vi) Chapter 1: General Introduction
1.1 Introduction (hypothesis, if any)
1.2 Aims and Objectives
1.3 Research Methodology
1.4 Summary of Dissertation (chapter summaries)
1.5 Main Achievements (related to 1.1, 1.2 & 1.3)
vii) Chapter 2: Literature Review
2.1 Introduction
2.2.......
2.? Summary
Other Chapters as necessary
vii) Chapter (n-1): Research
3.1 Introduction
3.2 Methodology
3.3 Data
3.4 Analysis and Discussion
3.5 Summary
viii) Chapter (n): Conclusions and Recommendations
4.1 Introduction
4.2 Conclusions and Recommendations
4.3 Recommendations for Further Research
ix) References (if using Harvard System or similar)
x) Bibliography (if any)
xi) Appendices
xii) Index (if supplied) - not really necessary in an undergraduate work
xiii) Oversize Materials
Style
Pagination of the body of the text is to be in Arabic numerals in the centre bottom of the page. The pagination begins with the first page of the first chapter and runs continuously through the material forming the body of the text. All blank pages and inserted pages containing tables, maps, photographs, etc. are to be numbered within the main sequence.
Pagination of material preceding the body of the text is to be in small Roman numerals.
The body of the text is to be double spaced in ...
Assignment DetailsYou are required to submiti) Two (soft .docxssuser562afc1
Assignment Details
You are required to submit:
i) Two (soft bound for marking) complete printed copies; and
ii) One electronic copy of the Final Dissertation, including Appendices
Note: None of these copies of your dissertation will be returned to you. You will need to make further copies if you wish to keep your own copy of the report.
The two main reports must be bound so that pages cannot be easily removed. However, appendices containing bulky material may be grouped together separately in suitable binders or containers (A4 ring binders are acceptable). All such separate materials must have the dissertation title with the student's name, number, year of submission and supervisor's name clearly shown on the outside.
The word limit is 8,000 words (+/-10%). This excludes footnotes and appendices but includesquotations. The appendices should not normally exceed 2,000 words. Dissertations are assessed by quality – not quantity. Part of the technique of technical writing is to get over an unambiguous message in a clear and succinct document. Marks will be reduced if there is evidence of padding, duplication or inessential illustrations or appendices.
Remember:
· You must keep to the word limit
· You must demonstrate that you have met the learning outcomes
· As you construct and present your work, consider the assessment criteria
Presentation Instructions
It is your responsibility to ensure that your work is neatly and accurately presented.
Typical Example of Dissertation Format
i) Title Page
ii) Abstract
iii) Acknowledgements
iv) Contents Page
v) List of Illustrative Materials
vi) Chapter 1: General Introduction
1.1 Introduction (hypothesis, if any)
1.2 Aims and Objectives
1.3 Research Methodology
1.4 Summary of Dissertation (chapter summaries)
1.5 Main Achievements (related to 1.1, 1.2 & 1.3)
vii) Chapter 2: Literature Review
2.1 Introduction
2.2.......
2.? Summary
Other Chapters as necessary
vii) Chapter (n-1): Research
3.1 Introduction
3.2 Methodology
3.3 Data
3.4 Analysis and Discussion
3.5 Summary
viii) Chapter (n): Conclusions and Recommendations
4.1 Introduction
4.2 Conclusions and Recommendations
4.3 Recommendations for Further Research
ix) References (if using Harvard System or similar)
x) Bibliography (if any)
xi) Appendices
xii) Index (if supplied) - not really necessary in an undergraduate work
xiii) Oversize Materials
Style
Pagination of the body of the text is to be in Arabic numerals in the centre bottom of the page. The pagination begins with the first page of the first chapter and runs continuously through the material forming the body of the text. All blank pages and inserted pages containing tables, maps, photographs, etc. are to be numbered within the main sequence.
Pagination of material preceding the body of the text is to be in small Roman numerals.
The body of the text is to be double spaced in ...
1. Describe five of the barriers and challenges that may exist thSantosConleyha
1. Describe five of the barriers and challenges that may exist that can prevent meaningful employee involvement in the development and implementation of a safety management system. Provide an example of each, and explain how it could be overcome.Your response must be at least 300 words in length.
2. Identify the differences between using a safety management system to achieve a desired level of safety performance and using a behavior-based approach. Define the strengths, weaknesses, and outcomes of both approaches. Describe how both approaches can be used together to effectively manage safety performance.Your response must be at least 300 words in length.
3. Imagine that you are a forensic detective and you have been tasked with analyzing a complete skeleton. How might you go about determining if the skeleton is male or female? What characteristics would you look for?Your answer must be at least 200 words in length.
4. Discuss the difference between general senses and special senses. Then, of the special senses, decide which you think is either most important or least important and explain your position.Your answer must be at least 200 words in length.
Guide to Technical Writing
Fall 2018
Material revised and adapted for use as
Supplementary material for
ENGL 1261 - TEWP
1
1. INTRODUCTION
Technical writing requires a strong foundation in general writing, including knowledge of common
grammar and punctuation conventions. The process is iterative and involves multiple reviews and
revisions prior to publication. The Chicago Manual of Style is used in this guide because it is the College
of Engineering standard. Be aware that other style manuals are often required as a writing standard.
This writing guide provides a format for writing and revising text and details on how to develop content
that meets professional standards. Prior to submitting work, complete several iterations of editing and
improving the text. Proofread again after several days, or at least hours, after the last examination. Then
request an external reviewer to provide detailed constructive criticism. Consider and incorporate relevant
feedback, then proofread the final document before submitting.
The Biosystems Engineering program provides many opportunities to learn from feedback on written
assignments. By writing and revising, the ability to communicate effectively with both clarity and brevity
will improve. Writing well is hard work but critical to academic and professional success.
2. TECHNICAL WRITING
Technical writing is direct, informative, clear, and concise language written specifically for an identified
audience. The content must be accurate and complete with no exaggerations. To deliver the intended
message, the text must be objective and persuasive without being argumentative. Developing technical
documents that meet these requirements and standard guidelines is time consuming. This section
provides an ove ...
1. Describe five of the barriers and challenges that may exist thBenitoSumpter862
1. Describe five of the barriers and challenges that may exist that can prevent meaningful employee involvement in the development and implementation of a safety management system. Provide an example of each, and explain how it could be overcome.Your response must be at least 300 words in length.
2. Identify the differences between using a safety management system to achieve a desired level of safety performance and using a behavior-based approach. Define the strengths, weaknesses, and outcomes of both approaches. Describe how both approaches can be used together to effectively manage safety performance.Your response must be at least 300 words in length.
3. Imagine that you are a forensic detective and you have been tasked with analyzing a complete skeleton. How might you go about determining if the skeleton is male or female? What characteristics would you look for?Your answer must be at least 200 words in length.
4. Discuss the difference between general senses and special senses. Then, of the special senses, decide which you think is either most important or least important and explain your position.Your answer must be at least 200 words in length.
Guide to Technical Writing
Fall 2018
Material revised and adapted for use as
Supplementary material for
ENGL 1261 - TEWP
1
1. INTRODUCTION
Technical writing requires a strong foundation in general writing, including knowledge of common
grammar and punctuation conventions. The process is iterative and involves multiple reviews and
revisions prior to publication. The Chicago Manual of Style is used in this guide because it is the College
of Engineering standard. Be aware that other style manuals are often required as a writing standard.
This writing guide provides a format for writing and revising text and details on how to develop content
that meets professional standards. Prior to submitting work, complete several iterations of editing and
improving the text. Proofread again after several days, or at least hours, after the last examination. Then
request an external reviewer to provide detailed constructive criticism. Consider and incorporate relevant
feedback, then proofread the final document before submitting.
The Biosystems Engineering program provides many opportunities to learn from feedback on written
assignments. By writing and revising, the ability to communicate effectively with both clarity and brevity
will improve. Writing well is hard work but critical to academic and professional success.
2. TECHNICAL WRITING
Technical writing is direct, informative, clear, and concise language written specifically for an identified
audience. The content must be accurate and complete with no exaggerations. To deliver the intended
message, the text must be objective and persuasive without being argumentative. Developing technical
documents that meet these requirements and standard guidelines is time consuming. This section
provides an ove ...
Project Title
Final Project Report
Submitted as partial fulfillment of the requirements for
ENGT 4050
Senior Technology Capstone
Professor Richard Springman
Project Team A-00
Rocky Rocket, Team Lead
Allis Chalmers
John Deere
Cyrus McCormick
Faculty Advisor
Dr. Myron Noodleman
Sponsor
Mr. Anton Hulman
Indianapolis Motor Speedway
July 4, 1776
The University of Toledo
College of Engineering
Engineering Technology Department
This page intentionally left blank
An Abstract of
Project Title
by
Team A-00
Rocky Rocket, Team Lead
Allis Chalmers
John Deere
Cyrus McCormick
for
ENGT 4050
Senior Technology Capstone
Fall Semester 2013
The University of Toledo
The title material above is single-spaced and centered at the top of the Abstract page, with equal
spacing between each component (i.e., one blank line). This information must agree with that
which is presented on the title page. Use two spaces between the title material and the text of the
abstract. Abstract page material must be printed in the same font as is used for all other textual
material (i.e., do not use bold, italics, underline, etc. here).
The abstract text must be a concise statement of the problem, procedure or methods utilized,
results obtained, and a brief conclusion. There is no prescribed length for the abstract, but in no
case should it exceed 350 words.
Acknowledgments
This section is included for the purpose of identifying and/or recognizing those who have helped,
assisted or provided support to the design team in the execution of the senior capstone project.
Table of Contents
Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iii
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
List of Tables
List of Figures
List of Abbreviations
List of Symbols
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Project Objectives
Project Team
Design and Analysis
Results
Discussion and Conclusions
References
Appendices
Team Resumes
Gantt Chart
Budget
.
Project Title
General Formatting
Your report must be in suitable condition for binding and printed on one side only (i.e., no
double-sided printing). Textual material may be formatted “ragged-right” or “flush” with the
right margin. This choice may be influenced by the typesetting capabilities of the software used
to prepare your report. Hyphenations are permitted, except when the hyphenated word is split
over two page.
New folderfac_lee023_HW06_WR5_FuncDecomp (3).pdfECE380 Pr.docxcurwenmichaela
New folder/fac_lee023_HW06_WR5_FuncDecomp (3).pdf
ECE380 Professional Seminar
Spring 2017
HW5 (WR5): Functional Decomposition
Date assigned: 3/13/17, Monday
Due date: Noon, 3/20/17, Monday
Max points: 20 pts.
Description:
Written Report 5 is on completing 3-level (i.e., Level 0, Level 1, and Level 2) functional
decomposition of your project. Each student shall individually submit one report that
shows complete functional decomposition of the project but also clearly identified
individual responsibilities for implementation. As such, all team members of a project
should first discuss and come up with a complete set of Level 1 subsystems that could be
implemented under balanced workloads among the team members. Then, each member
shall further elaborate his/her assigned Level 1 subsystems into Level 2.
This report should include block diagrams of all Level 0 ~ Level 2 subsystems and
corresponding tables of ALL subsystems with module name, inputs, outputs,
functionality (see pp. 93 ~ 98 of textbook by Ford and Coulston), AND responsible team
member.
Submission instructions:
Report length: No limit
How to submit: Upload onto EvalTools by the deadline shown above.
Grading:
Overall functional decomposition – team performance
Subsystems – individual performance
New folder/fac_lee023_HW11_WR6_FinalReport (1) (1).pdf
ECE380 Professional Seminar
Spring 2017
HW11: Final Report
Date assigned: 4/10/16, Monday
Due date: Noon, Monday, 4/24/17
Max points: 100 pts.
Description:
Each team’s final report must contain properly revised details of all project aspects covered
in this course, i.e., marketing and engineering requirements, proper description of the
project, 3-level functional decomposition, and project management including a well-
planned project plan presented in a Gantt chart.
To give incentive to a proper revision of functional decomposition, the final report will
carry 100 points of which 40 points will be allocated to the revised functional
decomposition (presented within the final report). Gantt chart (presented within the final
report) will have 10 points among the total of 100 points for the final report. The rest 50
points will go to the overall quality of the report as described in the review criteria.
Submission instructions:
Final Reports are team submissions so each document shall have all team member names
and only one person in the team shall upload the report to the designated submission link.
New folder/fac_lee023_HW11_WR6_FinalRpt_Guideline (1) (1).docxFinal Project Report Title ECE 380 Professional Seminar
by
Author(s) Name(s)
Author Affiliation(s)
E-mail
Date
Department of Electrical and Computer Engineering
Gannon University, Erie, PA
Acknowledgement
If you have any positive remarks this is the place to show your gratitude.
Abstract
The abstract is to be in fully-justified italicized text, as it is here, ...
Title of Your Research Idea by Your Whole Name TakishaPeck109
Title of Your Research Idea
by
Your Whole Name
(Descriptive, Experimental, or Qualitative) Prospectus
Submitted to the College of Technology
Eastern Michigan University
Dissertation Candidacy Qualifying Examination Committee
in partial fulfillment of the requirements
for the degree of
DOCTOR OF PHILOSOPHY
Candidacy Qualifying Examination Committee:
Faculty Name, PhD (Note: This is your potential dissertation chair)
Faculty Name, PhD (Note: This is your potential research methods representative)
Faculty Name, PhD (Note: This is your potential academic advisor or concentration adviser)
Month Day, Year
Ypsilanti, Michigan
ii
Table of Contents
(Delete this text; include only the TOC.) The wording of headings in the Table of
Contents must correspond exactly to the wording of those headings in the text. Include a
listing of the preliminary pages with page number references (except for the title page and
the Table of Contents pages themselves). Ellipsis marks (also called “dot leaders”) to page
number references are required.
Introduction ............................................................................................................................... 1
Statement of the Problem .............................................................................................. 4
Nature and Significance of the Problem ....................................................................... 4
Objective of the Research ............................................................................................. 5
Hypothesis and/or Research Question(s) ...................................................................... 5
Limitations and Delimitations ....................................................................................... 5
Definition of Terms....................................................................................................... 6
Assumptions .................................................................................................................. 6
Methodology ............................................................................................................................. 6
Research Design............................................................................................................ 6
Population, Sample, and Subjects ................................................................................. 7
Human subjects approval. ..................................................................................... 7
Data Collection ............................................................................................................. 8
Data Analysis ................................................................................................................ 8
Personnel ....................................................................................................................... 8
...
Important Student NotesFollow the guidelines of the CU ResearMalikPinckney86
Important Student Notes:
Follow the guidelines of the CU Research guide for structure Following the specifications of APA for format
REMINDERS:
· Each student submission will be checked for plagiarism. Note: Turnitin has a very good historical memory and is capable of accessing reports from both internal and external resources (i.e. Universities, Governments, etc.) including those originally written in non-English written languages. Plagiarism will result in a grade of zero (non-negotiable) for the assignment and may results in other university actions. The department chairperson will be notified of the violation. Additional Campbellsville University penalties may be applicable. Please see class syllabus for additional details.
· Only one submission attempt is permitted – BE SURE BEFORE DEPRESSING ENTER. Acceptable file formats for submissions include Microsoft Word (doc, docx). No otherformats are acceptable.
· A minimum of five (5) peer-reviewed journal articles are required.
· Formatting should be double-spaced, one-inch boarders, no extra space for headings, no extra white space, no more than two levels of heading, page numbers, front and back matter).
· Extra white space use to enhance page count will negatively affect student grade.
· Graduate student are expected to be proficient in the use of the English language. Errorsin grammar, spelling, or syntax will affect student grade. The Professor, will not provide remedial help for writing problems. If the student is unable to write clearly and correctly, the student should be urged to contact the program office for sources of remedial help.
· IMPORTANT - please refer to the following url for additional help on writing skillsnecessary at the graduate level (https://owl.purdue.edu/site_map.html).
· APA formatted citations are required for the final submission. IMPORTANT - pleaserefer to the following url for help with APA: https://owl.purdue.edu/owl/research_and_citation/apa_style/apa_style_introduction.html. Please reach out to our librarians for additional citation management and APA help.
· Long quotations (i.e. paragraphs) are NOT permitted. Only one quoted short sentence (less than 14 words) is permitted per page.
· Footnotes are NOT permitted.
Document Details
This area provides additional details about the content of each of the needed Research Report Chapters (5). The final submission should include DETAILS of each of following:
Abstract with at least 5 key words
1) Chapter 1 – Introduction
2) Chapter 2 – Literature Review
3) Chapter 3 – Methodology Specifics (comparative analysis)
4) Chapter 4 – Findings, Analysis, and Summary of Results
5) Chapter 5 – Conclusion and Future Recommendations
6) References - APA
Chapter 1 Introduction
Introduction
In this section, present enough information about the proposed work such that the reader understands the general context or setting. It is also helpful to include a summary of how the rest of this doc ...
Appropriate TopicsThe Research Report, select one of the fo.docxYASHU40
Appropriate Topics:
The Research Report, select one of the following research areas:
i) 5G Networks
ii) Serverless Computing
iii) Blockchain
iv) 3D Printing
vii) Artificial Intelligence
viii) Internet of Things (IoT)
ix) Medical Technology
Introduction
Literature Review
Methodology Specifics (comparative analysis)
Findings and Results
Conclusion and Future Recommendations
References - APA
Appendices
Your
paper is to have a title page, introduction, well defined literature review(body), findings, conclusion, and reference pages. The paper must be at least 2,500 words.
Use
graphs, charts, tables or figures.
The research paper must be at least 2,500 words supported by evidence (citations from
peer-reviewed sources).
Note: the research should be thorough and exhaustive.
A minimum of five
(5) peer-reviewed journal citations
are required.
Formatting should be double-spaced, one-inch boarders, no extra space for headings, no
extra white space, no more than two levels of heading, page numbers, front and back
matter). Extra white space use to enhance page count will negatively affect student grade.
The research paper
must only
include materials derived solely from peer reviewed
journals or peer reviewed conference proceedings. Newspapers, websites (URLs),
magazines, technical journals, hearsay, personal opinions, and white papers
are NOT
acceptable citations.
All images, tables, figures are to be included in the appendices and
IS NOT
included in the 15-page requirement. This means appendices are not included in the 15 pages requirement.
A total of at least 15 full pages is required (no extra whitespace).
Formatting Details
Margins
The left-hand margin must be 1inches (4 cm.). Margins at the right, top, and bottom of the page
should be 1.0 inch. (See exception for chapter title pages below.) The Research Report text may
be left-aligned (leaving a ragged right edge) or may be both left- and right-aligned (justified).
Line Spacing
Double-spacing is required for most of the text in documents submitted during the Research
Report process.
Paragraph Spacing
The text of the document is double-spaced. There should be no extra spaces between paragraphs
in sections, however, indent the first line of each paragraphs five spaces.
Page Numbering
All pages should have page numbers in Arabic numerals in the upper right-hand corner.
Type Style
The body text, the student should use 12-point Times New Roman. Text for the cover page may
be larger but should not exceed 14-point size. Text for the chapter title text should be 14-point
size. Be consistent in the use of typefaces throughout the document. Do not use a compressed
typeface or any settings on the word processor that would decrease the spacing between letters or
words. Sans serif typefaces such as Helvetica or Arial may be used for relatively short blocks of
text such as chapter headings and captions but should be avoided in long passages of text as the.
bohat achcha hai pdh lena kaam aaye to kr lena aur nai bhi aaye to download krke rkh lena . thike aur kuch jankaari chaiye ho to scribd pr mt. aana je bht hi kutti website h :'df;ds'sjhsjfkas lkjsad ;asdhf kjdshhjhjdhjdhdjhjhjhhjhjhjj
How To Write Your Research DissertationChris Jobling
This presentation describes the standard structure of your research dissertation and suggests a methodology for its successful production using modern word processing tools.
Similar to 11575 1 guidelines for preparing training report (2) (20)
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentations
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
How to Get CNIC Information System with Paksim Ga.pptx
11575 1 guidelines for preparing training report (2)
1. Guidelines
For The Preparation of Six weeks Industrial Training Report
Version 1.0
Lovely Professional University Jalandhar – Delhi G. T Road (NH-1),
Phagwara, Punjab, 144402, India
2013
2. 1. INTRODUCTION
This document covers the general rules of format and appearance. It is the
student’s responsibility to read and follow the requirements presented here
and to submit documents of the highest quality. The final copies will not be
accepted with corrections, insufficient margins, or if they are of such poor
quality that reproduced and/or microfilmed copies cannot be made.
The final version of the Training Report must be free from typographical,
grammatical and other errors when submitted as Examination Copy. While
this is the responsibility of the student.
2. REPORT
2.1 The arrangement of parts of Training Report
The sequence in which the training material should be arranged and bound
should be as follows:
1) Cover Page
2) Inside Cover Page
3) Candidate/s Declaration
4) Dedication Page (Optional)
5) Objective of Training or Project
6) Acknowledgements
7) Table of Contents
8) List of Tables
9) List of Figures
10) List of Symbols, Abbreviations or Nomenclature (Optional)
11) Enclosures
12) Chapters
Maximum Number of Chapters are recommended to be five (Chapter one is
Introduction, Chapter two is company profile , Chapter three is Identification
of the training /project , Chapter four is Design Details, Implementation and
Testing and Chapter five is Results, Discussion and conclusion).
13) Appendices
3. 14) References
Minimum References must be 10.
The formats in various headings are given below
Title Page See Annexure 1 (Inside cover page same as cover page)
Dedication page (if any) should not exceed one page
Candidate declaration, see Annexure 2
Objective of Training or Project see Annexure 3 (Abstract should not exceed
two pages (about 600 words))
Acknowledgements should not exceed two pages
Table of Contents see Annexure 4
List of Tables see Annexure 5
List of Figures see Annexure 6
Abbreviations see Annexure 7
Notations see Annexure 8
References see Annexure 9
3. GUIDELINES FOR PREPARATION OF TRAINING REPORT
The training manuscript has three basic parts: the preliminary pages, the text
and the reference materials.
3.1 Preliminaries
The preliminary materials consist of the Title Page, Thesis Certificate,
Abstract, Dedication (optional), Acknowledgements, and Table of contents,
List of Tables, List of Figures and other lists.
Preliminary pages are paginated separately from the rest of the text. The title
page is counted, but it is not numbered. Beginning with the page immediately
following the title page, place page numbers in lowercase Roman numerals
centered at the bottom of the preliminary pages. The Roman numerals are
continued up to the first page of the text. Proper Order of Preliminary Pages
is:
4. a. Title Page
The title of the Training/project report should be as concise as possible. It
must occur consistently in every respect, including punctuation,
capitalization, and hyphenation, on the abstract and approval forms. On the
title page, the identical title must appear in title case with each line centered
on the page. The month in which the Training is submitted, e.g., May,
August, or January is to be printed at the bottom of the page. The title page is
not numbered, but it is counted. Size of the institute logo should be 3cm x 4
cm.
b. Objective of Training or Project
The Objective should provide a succinct, descriptive account of the
training/project including a statement of problem procedure and method,
results and conclusion. It must not include diagrams and should not include
mathematical formulas unless essential. The Objective should be in the range
of 400 to 600 words with 1.5 line spaced. It should adhere to the same style
manual as the thesis manuscript. A lower-case Roman numeral is used on the
abstract page and number of keywords not more than six.
c. Dedication (optional)
The dedication is brief, single-spaced, and centered on the page. No heading
is used. The word "To" customarily begins the dedication.
d. Acknowledgements
This section begins with the title ACKNOWLEDGEMENTS centered in all
capital letters. This page is used to thank those persons who have been
instrumental to the student in completing the degree requirements.
Acknowledgement of grants and special funding received to support the
Training/Project also may be made on this page.
e. Table of Contents
The Table of Contents must include all Chapter headings, Section headings,
Subsection headings, Appendices (optional if any) and References. Entries
are 1.5 lines spaced. The headings of major sections (i.e., Chapters,
5. Appendices and References) are written in all capital letters. Table of
contents headings must be identical to those in the text. Page numbers must
be bottom centered and each entry must have leader dots, which connect it to
its corresponding page number. The words TABLE OF CONTENTS must
be centered on the page two inches from the top of the first page only.
f. List of Tables (if tables appear in document)
The heading, LIST OF TABLES, appears centered on the page two inches
from the top of the first page only. All table numbers and captions are listed
exactly as they appear in the text.
g. List of Figures (if figures appear in document)
The heading, LIST OF FIGURES, appears centered on the page two inches
from the top of the first page only. All figure numbers and captions are listed
exactly as they appear in the text.
h. Other Lists (nomenclature, definitions, glossary of terms, etc.)
The appropriate title in all capital letters is centered two inches from the top
of the first page only.
3.2 Text
The text must be divided into a logical scheme that is followed consistently
throughout the document. The larger divisions and more important minor
divisions are indicated by suitable, consistent headings. All headings and
subheadings should be presented in the same way in each chapter, in terms of
capitalization, placement on the page and kind of type used. No headers,
giving the titles of chapters or other sections, are allowed at the top of the
pages. Chapter organization as practiced by the discipline should be
followed. Program code may be placed in the Appendix. The
Student/Research Scholar and the academic department are responsible for
the quality and content of the text. Specific requirements for text presentation
are given below.
a. Section and Subsection
The student may use Section headings and Sub-Section headings to subdivide
the chapter/s, but a consistent sequence of section headings as identified in
the style guide selected must be followed. The Student/Research Scholar do
6. not change the sequence and style of headings from chapter to chapter. Once
the sequence is chosen, it must be followed consistently throughout the
thesis. Footnotes should be in 10 point character with single spaced lines.
b. Pagination
Lower-case Roman numerals are used to number all pages preceding the text.
Although the preliminary paging begins with the title page, no number
appears on the title page. However, it is counted as i, The page immediately
following the title page is numbered with a lower- case Roman numeral ii.
Beginning with the first page of the text, all pages are to be numbered with
Arabic numerals consecutively throughout the thesis document, including the
appendix and the bibliography or list of references. The page numbers must
be positioned at the bottom centered of the page. Page headers or running
heads may not be used in the thesis. All page numbers must be in the same
font and size.
c. Tables and Figures
The term "table" refers to a columnar arrangement of information, often data
sets, organized to save space and convey relationships at a glance. The term
"figure" refers to graphs, drawings, diagrams, charts, maps, or photographs.
All such details should be inserted in the text near where they are first
mentioned. A table or figure may appear on the same page as the text that
refers to it or on a immediate next page. Each figure or table must be
numbered and have a caption. Captions are placed below figures and pictures
and above tables. Captions may be single spaced.
d. Illustrations
Each illustration must be referred to in the text and it must be placed after,
and as near as possible to, the first reference to it in the text. All illustrative
materials in the thesis must be prepared on paper that is the same weight (or
stronger) and use the same font type as elsewhere in the manuscript. If
illustrations are mounted, dry mounting must be used. Illustrations may not
be mounted with rubber cement, staples, mucilage, or photo-mounting
corners. Illustrative material must be drawn or computer-generated in black.
7. Material may be laser-printed. Color should be used only if it is essential to
the thesis.
e. Photographs
It is recommended that the student use a high quality, high contrast copying
machine to reproduce photographic material for submission in lieu of
photographs. If original photographs are used, they should be printed on
single-weight, fiber-based paper with a matte finishes. All prints must be
processed for nationally established standards for chemical permanence.
Black-and-white prints are preferable. Photograph page number placement
follows the standard pagination requirements.
f. Appendix
The appendix (or a series of appendices) immediately follows the main text.
The appendix includes material that may be helpful to the reader of the thesis
but may be too long for inclusion in the text or footnotes. The title,
APPENDIX, appears only on the first page of the section, in capital letters
centered two inches from the top. Examples of such material include
questionnaires, letters, original data, sample forms, and derivations.
Reference should be made in the text to the inclusion of these materials in the
appendix. Each appendix is a separate subdivision of the text and must begin
on a separate page. Each appendix must be listed in the
e. Table of Contents.
f. Enclosures: enclose the photo copy of certificate provided by
Industy/Institute.
3.3 References
Referencing style may follow IEEE, Harvard, or Chicago styles. For
referencing you may use font size of 11.
8. 4.1 Chapter and Section format
The title of Chapter one shall be Introduction. It shall justify and highlight the
problem poser and define the topic, aim and scope of the work presented in
the thesis. It may also highlight the significant contributions from the
investigation. Use only Arabic Numerals. Chapter Numbering should be
centered on the top of the page with bold.
Example:
CHAPTER 1
INTRODUCTION
Sections
A chapter can be divided into Sections, Sub-sections and Sub-sub-sections so
as to present different concepts separately. Sections and Sub-sections can be
numbered using decimal points, e.g., 2.2 for the second Section in Chapter 2
and 2.3.4 for the fourth Subsection in third Section of Chapter 2. Use only
Arabic Numerals with decimals. Section numbering should be left justified
using large bold print.
Example:
1.1 BACKGROUND
1.2 GSM
Sub Sections
Use only Arabic Numerals with two decimals. Sub section numbering should
be left justified with bold.
Example:
1.1.1 Block Ciphers
1.1.2 Data Encryption Standards
(Required no. of pages: 2-3 Pages)
9. CHAPTER 2
COMPANY PROFILE
2.1 INTRODUCTION
2.2 …
This shall normally the Chapter 2 and shall present the detail of the work
done in Company.
(Required no. of pages: 2-3 Pages)
CHAPTER 3
IDENTIFICATION OF TRAINING/PROJECT
3.1 INTRODUCTION
3.2 …
This shall normally the Chapter 3 and shall present the identification of the
training/project.
(Required no. of pages: 2-3 Pages)
CHAPTER 4
IMPLEMENTATION DETAIL
4.1 INTRODUCTION
4.2 …
This shall normally the Chapter 3 and shall present the Design Details,
Implementation and Testing.
(Required no. of pages: 15-20 Pages)
CHAPTER 5
RESULTS AND DISCUSSION
5.1 INTRODUCTION
5.2 …
This shall form the penultimate chapter of the Training/Project and shall
include a thorough evaluation of the investigation carried out and bring out
the contributions from the Training. The discussion shall logically lead to
inferences and conclusions as well as scope for possible future work. Table /
Figure Format As far as possible tables and figures should be presented in
10. portrait style. Small size table and figures (less than half of writing area of a
page) should be incorporated within the text, while larger ones may be
presented in separate pages. Table and figures shall be numbered chapter –
wise. For example, the fourth figure in Chapter 5 will bear the number figure
5.4 or Fig.5.4. Table number and title will be placed above the table while the
figure number and caption will located below the figure and will be centered
left. Reference for Table and Figures reproduced from elsewhere shall be
cited in the last and separate line in the table and figure caption, e.g. [12].
Text in tables may be in font size of 10.
Table 4.6: Cell values and key sequence
Equations
All the equations should be typed in equation editor/LaTeX and should be
properly numbered.
For Example,
(Required no. of pages: 4-7 Pages)
11. 5. PAGE DIMENSIONS AND MARGIN
The Training/Project should be prepared on good quality white paper.
Standard A4 size (210 mm X 297 mm) paper should be used for preparing
the copies. The final Training/Project should have the following page
margins and the same margins should be used throughout a thesis.
Top edge: 1 inch
Left side: 1.25 inch
Bottom edge: 1 inch
Right side: 1.25 inch
6. TYPE-SETTING, TEXT PROCESSING AND PRINTING
The text shall be printed employing Laserjet and the text having been
processed using a standard text processor. The standard font shall be Times
New Roman of 12 pts with 1.5 line spacing. The text must be 1.5 lines spaced
and printed on only one side of each page
7. BINDING
Spiral Binding
8. FRONT COVERS
The front cover shall contain the following details:
• Full title of thesis in 20 point’s font size properly centered and positioned at
the top.
• Full name of the candidate in 14 point’s font size properly centered at the
middle of the page.
• A 3 x 4 cms size of the Institute emblem followed by the name of the
Institute and the year of submission, each in a separate line and properly
centered and located at the bottom of the page.
12. Annexure 1
Title of the Training/Project
A Training/project report submitted in partial fulfillment of the requirements
for the award of the degree of
Name of the Student 1 (Registration Number)
Centered, Bold
Font size is 14 pt.
Lovely Professional University Jalandhar – Delhi G. T Road (NH-1),
Phagwara, Punjab, 144402, India
Centered, Bold
Font size is 20 pt.
2013
Centered, Bold , Font size is 18 pt.
Size 3:4
13. Annexure 2
(Sample)
CANDIDATE/S DECLARATION
I hereby certify that the work, which is being presented in the report/
Training/Project entitled Title of the Report/ Training/Project, in partial
fulfillment of the requirement for the award of the Degree of Bachelor of
Technology submitted to the institution is an authentic record of my/our own
work carried out during the period Month-Year to Month-Year under the
supervision of supervisor(s) name. I also cited the reference about the
text(s)/figure(s)/table(s) from where they have been taken.
Date: Signature of the Candidate
This is to certify that the above statement made by the candidate is correct to
the best of my /our knowledge.
Date: Signature Supervisor
14. Annexure 3
(Sample)
OBJECTIVE OF TRAINING/PROJECT
The main goal of this work is to
Plan the installation of BTS through survey,
Detect areas of the poor signal strength through Drive test and Post
processing of collected data,
Improve the signal strength of poor coverage areas through
sectorization at BTS.
15. Annexure 4
(Sample)
TABLE OF CONTENTS
Title Page No.
ABSTRACT .................................................................................................................. v
LIST OF TABLES..........................................................................................................vii
LIST OF FIGURES...................................................................................................... .ix
CHAPTER 1 INTRODUCTION
1.1 General ................................................................................................................... 1
1.2 Objectives................................................................................................................ 2
1.3 Organization of the Report/Thesis…………………………………………..……..3
CHAPTER 2 LITERATURE REVIEW
2.1 Introduction ....................................................................................................…….3
2.2 Vulnerability Scanners………............................................................................... .3
2.3 The nmap port Scanner........................................................................................... 3
2.4 The Nessus Vulnerability Scanner...........................................................................3
2.5 Packet Sniffers………............................................................................................. 4
2.6 Intrusion Detection………….................................................................................. 6
CHAPTER 3 METHODOLOGY
3.1 Introduction……………..........................................................................................7
3.2 Public-key Cryptography
3.2.1 Rivest-Shamir-Adleman Algorithm for public-key Cryptography..................... 7
3.2.2 Proof of the RSA Algorithm ............................................................................... 8
3.2.3 Computational Issues Related to RSA................................................................. 8
3.3 Experimental Procedure .......................................................................................... 9
3.3.1 Emulsion preparation............................................................................................ 9
3.3.2 Extraction process............................................................................................... 10
3.4 Operating Conditions............................................................................................. .11
CHAPTER 4 RESULTS AND DISCUSSION
4.1 Introduction .............................................................................................................39
4.2 Some Mathematical Preliminaries……………………………………….………....39
4.3 Success Probability of the Attack …………………………………………………41
4.3.1 Modelling the Statistical Experiment ……………………………………….…..41
16. 4.3.2 A Simplified Statistical Experiment …………….………………………..……. 45
4.3.3 Towards the Good Distribution ………………………………………..………...47
CHAPTER 5 CONCLUSION AND FUTURE WORK
5.1 Introduction..............................................................................................................54
5.2 Conclusions ............................................................................................................ 64
5.3 Scope for Future Work ........................................................................................... 71
REFERENCES……………………………………………………..……………….…73
APPENDIX…………………………………………………………………………...75
A.1 Name of Appendix 1 ……………………………………………………..…..…...76
A.2 Name of Appendix 2 ……………………………………………………..…..…...77
LIST OF PUBLICATIONS……………………………………………………….…..79
Resume of the Research Scholar (only for Ph.D.)……………………………… .…....80
17. Annexure 5
(Sample)
LIST OF TABLES
Table No. Title Page No.
1.1 RSA, DL and EC key sizes for equivalent security levels ………..……. 10
2.1 OEF example parameters………………………………………............... 22
2.2 Computational details for inversion inOEFs ……………………………..25
2.3 Computational details for inversion inOEFs ……………………………. 35
2.4 Admissible orders of elliptic curves over F37…………………………… 45
3.1 Isomorphism classes of elliptic curves over F5 …………………………..48
3.1 Operation counts for arithmetic on y2 = x3 −3x +b …………………… .49
3.7 Operation counts for arithmetic on y2 +xy = x3 +ax2 +b…………………50
4.1 Point addition cost in sliding versus window NAF methods ……………..51
4.2 Operation counts for computing kP +lQ ………………………………….55
4.4 Operation counts in comb and interleaving methods ……………………..65
5.1 Koblitz curves with almost-prime group order ……………………………75
18. Annexure 6
(Sample)
LIST OF FIGURES
Figure No. Title Page No.
1.1 Basic communications model ………………………………………………2
1.5 Symmetric-key versus public-key cryptography …………………………. .4
2.2 Representing prime-field element as an array of words ……………………29
2.3 Depth-2 splits for 224-bit integers (Karatsuba-Ofman multiplication) …….33
3.3 Depth-2 splits for 192-bit integers (Karatsuba-Ofman multiplication) …….34
3.4 Representing binary-field element as an array of words …………………...47
3.5 Right-to-left comb method for polynomial multiplication ……………..…..49
3.6 Left-to-right comb method for polynomial multiplication…………….........49
19. Annexure 7
(Sample)
LIST OF ABBREVIATIONS
ACM Association for Computing Machinery
ADES Advance Data Encryption Standard
CBC Cipher Block Chaining
CFB Cipher Feedback Mode
DDES Double Data Encryption Standard
DES Data Encryption Standard
ECD Electronic Codebook Mode
IEEE Institute of Electrical and Electronics Engineers
NIST National Institute of Standards and Technology
OFB Output Feedback Mode
OTP One Time Pad
TDES Triple Data Encryption Standard