Strictly follow the specification file uploaded below.
A self-driving car manufactured by AlseT crashed into a tree in adverse weather conditions. Fortunately, none of the passengers were seriously hurt. Unfortunately, the car is a total wreck.
Gecko, the car owner’s insurance company, is suing AlseT, arguing that, according to AlseT’s advertising and technical specifications, the car’s collision-avoidance system should have been able to prevent this accident. AlseT disputes this argument, asserting that its software functioned properly, and that the driver was at fault for not observing the guidelines and specifications outlined in the driver’s manual.
Your Role: Technical Expert
You have been hired as a technical expert by one of these companies to determine the real cause or causes of the accident and to write a short technical report explaining your findings. The audience for this report is the judge who will be hearing the case, so your report should be written for a non-technical audience. At the same time, your argument must be technically rigorous and be supported by evidence. For example, you might describe what you observed during an inspection of the wrecked vehicle, cite the results of tests you conducted, or refer to specifications and other documentation you studied. But remember, you’ve been hired for your technical knowledge and background, and are not expected to have any legal training. (You’re an engineer, not a lawyer.)
You are an engineer who has been hired for your technical expertise in self-driving car technology. (Lucky you!) Write a short technical report that takes either Gecko or AlseT’s side in the above-mentioned dispute. Write the report as a memo.
Your report should include, but not be limited to, the following sections.
- Observations, data, findings, and results
- Information Sources
You are encouraged to tailor your headings to your report by making them more specific and informational. You may add sections or subheadings as needed.
The purpose of this assignment is to demonstrate your ability to do the following:
- write a short technical report based on a realistic scenario;
- apply the principles of writing for a non-technical audience;
- demonstrate clear, concise, coherent, and audience-appropriate writing;
- make a convincing argument that is supported with evidence;
- apply the principles of “noise-free” writing;
- use graphics effectively to illustrate or support your argument.
- You need to choose whether you have been hired by AlseT or by Gecko.
- You may need to do a bit of research on self-driving cars to make sure you use the proper terminology, but your understanding of the topic can be superficial.
- Your report will be graded primarily on the clarity of your writing and the strength of your argument, not on your technical understanding of autonomous cars.
- Don’t fall into the trap of focusing on the legal aspects; you are an engineer, not a lawyer.
- This is a fictionalizedaccount of events. You will need to use your imagination to fill in the details. Creativity is encouraged! Things you might consider:
- Weather conditions on the day
- Time of the accident (day or night?)
- Condition and/or location of the road
- Number of passengers
- Other factors
Refer to the textbook and lectures for guidance
For guidance on writing a short technical report, review lecture presentations and relevant chapters in Technical Communication, 11thedition, by Mike Markel, including the following:
- Chapter 17: Writing Informational Reports
- Chapter 12: Creating Graphics
- Chapter 14: Writing Correspondence
- Chapter 10: Writing Effective Sentences
Assignment and Formatting Instructions:
- Word document;
- Length: 3-4 pages;
- Memo heading (single spaced);
- 1.5 spacing in body of memo;
- 1” margins;
- Body text: 12-point Times New Roman;
- Headings:12-point Helvetica or Arial (bold);
- Subheadings: 12-point Times New Roman, italics;
- Paragraphs and headings: left-aligned, non-indented; Do not “justify”;
- Add one line of space between paragraphs and after headings for readability;
- Page numbers, bottom right corner;
- Use correct pagination for report (page numbers begin on page two);
- Create two or more original graphics (figures and/or tables) to support your argument;
- Label graphics correctly and integrate them in the report correctly;
- Choose appropriate fonts for graphics (your choice), but make sure they are readable;
- Photos can also be included;