Week 5 computer forensics

Week 5

YOU SHOULD CREATE AN OUTLINE AND OVERVIEW OF YOUR PLANNED PROJECT FOR PERSONAL PLANNING PURPOSES. 

SUBMIT YOUR PLAN IN A MS WORD DOCUMENT FORMAT

THE OUTLINE / OVERVIEW SHOULD INCLUDE:

1.     Name of the fictitious company you plan to highlight in your report.

2.     The background and industry profile of your fictitious company.

3.     Describe the forensic scenario you will target with your project.

4.     Describe WHY this forensics report is necessary for this company / industry.

This exercise should help you to start your project.  By planning ahead, you should be able to manage the project and stay on track.

This goes with the final project that will be due in week 8

Final Project Overview: Forensics Report (This project is due at the end of week 8)

• Submit the Final Report for you Forensics Project here.
• Your Final Report should be an MS Word document, at least six pages in length.
• Your forensics report should be about a fictitious company going through any of the scenarios learned in this class.
• Use hypothetical questions to guide and support your opinion. Hypothetical questions are based on factual evidence and should include only those facts supporting your opinion or conclusion. Remember that hypothetical questions can be abused and made so complex that the finder of fact (expert) might not be able to evaluate the answer.
• Your report should include:
  1. Abstract
  2. Table of contents
  3. Body of report
  4. Conclusion
  5. Glossary
  6. Acknowledgments
  7. Appendixes
• When writing a report you should consider:
  1. Communicative quality
  2. Ideas and organization
  3. Grammar and vocabulary
  4. Punctuation and spelling
• Your report organization is very important. You should lay out ideas in a logical order and build arguments piece by piece, grouping related ideas and sentences into paragraphs and paragraphs into sections.
• Pay attention to your writing style:
  1. Use a natural language style
  2. Avoid jargon, slang, and colloquial terms
  3. Define technical terms
  4. Avoid repetition and vague language
  5. Be precise and specific
  6. Use active rather than passive voice
  7. Avoid presenting too many details and personal observations
  8. Include signposts