IEE 380 Arizona State University Engineering Probability and Statistics Project In this project, you will collect data and perform a test of hypothesis on

IEE 380 Arizona State University Engineering Probability and Statistics Project In this project, you will collect data and perform a test of hypothesis on the population mean, variance unknown. This topic is covered in the text section 9.3. IEE 380 Fall 2020 Project
Introduction
Most of IEE 380 is spent reading problems from the text and applying the methods and
techniques of the class. Data is provided for you in the problems. However, as working
analysts, you may have to collect or generate data. Sometimes this data collection is more
time consuming and challenging than the actual statistical analyses that follow.
In this project, you will collect data and perform a test of hypothesis on the population
mean, variance unknown. This topic is covered in the text section 9.3.
Objectives
The objectives of this project are to (a) provide students with data collection experience, (b)
give students a realistic statistical data analysis experience, (d) improve students’ technical
writing skills.
Directions
1. Collect at least 50 observations from data of your choice. The observations you collect
may be discrete data or continuous data. You can generate or collect the observations
yourselves, but you may not use mass emailing to the class to do so. You can obtain the
data from internet sites (probably a better idea while we “flatten the curve” of the corona
virus).
2. Before doing any computations, determine a null and alternative hypothesis on the
population mean of the data. As an example, suppose your data was the price of a 2020 Kia
Soul from 50 dealerships around the country. Your null and alternative hypotheses might
be:
H0: ? = $17,000
H1: ? > $17,000
The alternative hypothesis is left up to you.
3. Write up your findings per the report template provided at the end of this document.
4. Upload your report to the project submission link in the Project folder on Canvas no later
than 3 pm on Friday, May 1, 2020. You must upload a Word document. No pdfs.
Copyright 2020 by L. Chattin, M. Clough, and Arizona State University. May not be posted to any website
without permission from L. Chattin, M. Clough, and Arizona State University.
Grading
This project is worth 7% of your course grade. The data quality and analysis accuracy, along
with grammar, spelling, organization and technical writing professionalism will comprise the
project grade.
There is a checklist provided at the end of the report template. Use it to ensure your report
conforms to requirements.
Due Date, Submission Details and Warnings
Your report must be uploaded to Canvas with time stamp BEFORE 3 pm on Friday, May 1,
2020.
Late submissions will be penalized as follows:
Timestamp between 5/1/20 3:01 pm and 4:00 pm will receive a 5% grade penalty
Timestamp between 5/1/20 4:01 pm and 8:00 pm will receive a 10% grade penalty
Timestamp between 5/1/20 9 8:01 pm and 5/2/20 12:00 am 50% grade penalty
Timestamp after 5/2/20 12:01 am receives no credit for the project
You must upload a Word doc. No pdfs will be accepted.
All report submissions will be 100% pair-wise compared to other students in the class and to
other IEE 380 submissions for the past 4 years using Turnitin. You may not collaborate
with any other student from Dr. Chattin’s class. If your report is more than 50% similar to
any other submission from this or any other semester, you will be reported for plagiarism
and reported to the dean’s office for an Academic Integrity Violation.
Repeated: You are not permitted to use any portion of any project reports from
previous semesters from friends, Chegg.com, CourseHero.com or any other source.
You will be reported to the dean’s office for an Academic Integrity Violation if this
occurs.
The report may be uploaded up to two times. That means you get one mistake. The second
upload overwrites the first and will be the one that will be graded. Make sure that when you
upload, you have the correct file.
Reviews
Do not send files of your report to me or to any TAs. Instead, complete the report entirely.
Use the checklist to help you make your report look professional, and Google “professional
technical memo” to see examples of good technical writing.
DO NOT EMAIL PROJECT REPORTS FOR REVIEW.
Copyright 2020 by L. Chattin, M. Clough, and Arizona State University. May not be posted to any website
without permission from L. Chattin, M. Clough, and Arizona State University.
IEE 380 Project
Dr. Clough
Objectives
Re-state the project objectives.
Data Description
Describe what data you collected, how many observations you took, and how you collected the
observations (generated, collected on the internet, how?). If websites were used, include URLs and titles.
Data
Show the raw data here, in a table. Include units and any other necessary descriptors.
Null and Alternative Hypotheses
Show the null and alternative hypotheses here. In words, explain why you selected the value of m0
that you did, and why you selected the alternative hypothesis that you did (i.e., < , > , ?).
Test Statistic, Conclusion, P-Value
Present the sample mean and sample standard deviation values. Include units. Show the equation
for and computation of the test statistic, t0. State the numerical value of the p-value. Clearly state your
conclusion. Sketch the t pdf and shade the p-value on it.
References
If you used any outside sources (internet), cite here using APA formatting. If you did not use any
sources other than our notes and text, delete this section of the report.
Copyright 2020 by L. Chattin, M. Clough, and Arizona State University. May not be posted to any website
without permission from L. Chattin, M. Clough, and Arizona State University.
IEE 380 Project Report Checklist
Each item below that is non-compliant will lose FIVE (5) points.
?
?
?
?
?
?
?
?
?
?
?
?
?
?
The report template has been used.
The data collected are provided as tables and are not broken up over page breaks.
All text in this document is black. Remove all yellow highlighting.
Your name is correct.
Any equations needed are shown using a math editor. Do not use ^ for exponents, for example.
Use subscripts. Do not use x1, use x1, for example.
The report has been checked for grammar mistakes.
The report is written in the first person or passive voice (i.e., no “you”, “your”, “you’re”).
There are no sentence fragments in the report.
The font sizes (e.g., 12 pt.) and styles (e.g., Times New Roman) are consistent
Top, bottom, and side margins are consistent.
Names of software are capitalized (Excel, for example).
The sentences are spaced at 1.5 (go to Format, Paragraph, and under Line Spacing, drag to 1.5)
New paragraphs are indented.
Copyright 2020 by L. Chattin, M. Clough, and Arizona State University. May not be posted to any website
without permission from L. Chattin, M. Clough, and Arizona State University.

Purchase answer to see full
attachment