Memorandum

To:Dr. ElifGuler

From: Heather Switzer

Date: September 12th, 2016

Subject:Proposal to Create a Mathematica Beginner’s Guide

Problem:

Being a transfer student, I came to this university without knowing the programs used in the higher level mathematics classes here. I was placed into Math 361 (Or Multivariable Calculus) and was asked to do multiple assignmentsand labs on a program called Mathematica, because it could simulate 3-Dimensional Graphs and Vector Plots, as well as calculate integrals, along with many other functions crucial to the course that are very difficult to do by hand. When the professor reviewed in class with us on how to use it, he explained it very briefly because Mathematica was “Something you should have seen in Calculus II.” Going online, I looked up the help section on how to run different functions, but the online manual was of no help, so I had to partner up with someone who did understand the program, at least to some degree.

Speaking to my fellow Mathematics Majors, just about all of them (including the Juniors and Seniors) still have a hard time using Mathematica for anything other than simple equations, while the lower level students just avoid using it altogether. In order to resolve this issue, I propose on creating an easy-to-use manual on how to work the basics of Mathematica. I had a class last semester that forced me to learn Mathematica because the professor would only accept projects through there, which were due every two weeks of the course. It took me hours and hours of frustration and looking up help forums online, but I finally get the hang of it, and it actually is not too difficult to use, if you can understand the basics.

Audience:

My primary audience for this manual would be new Mathematics Majors or even those taking regular math classes, as it can be an extremely helpful resource which can save hours of time and confusion. These students are mainly targeted because the upper level students (and by upper level, and mean 300+ level courses) usually have seen Mathematica before, so they have some sort of clue on how to use it, even if not incredibly efficiently. My secondary audience would be the upper-level math students who need a refresher on how to use Mathematica’s functions, as well as professors that may use this manual to help better educate their students.

The initial audience would be the Mathematics majors that I use the read to manual in order to validate the quality and usefulness. Other initial audiences may include Professor Guler, as she is the one grading it, and my fellow classmates who may be peer reviewing it in class. The Gatekeepers would be the math professors, because it is their decision whether or not to recommend and give exposure of this manual to their students. Finally, the Watchdog audience would also be the professors, because they would be the ones intensely reading over it to make sure everything is how they would like it and works correctly.

Topics to Investigate:

  • The Wolfram Alpha Current manual online
  • Example of code used to solve common problems on unofficial forums
  • Talk to the professors and other students as to which topics would be the important to include

Methods and Procedures:

In order to create this manual, I would first interview professors as to which commands they find would be most beneficial to their students to learn. After, I would consult with the Mathematics Majors as to their opinions on the same matter, and what sections need to be elaborated on more because they can be more difficult to understand. Talking to the new students would be beneficial as well in order for me to understand my audience and to ask what they are struggling with when it comes to solving problems in Mathematica. After collecting this information, I will create a manual that covers the basic fundamentals of the program, including key codes and shortcuts before getting into the more complicated code.

After the first rough draft of the manual is complete, I will take it to one of my peers who is familiar with Mathematica in order to validate that the information is correct after I review the instructions myself. From there, any revisions necessary will be made before taking it to another peer who does not fully understand Mathematica to see whether that person can understand the instructions written out for them. Another revision will be made, and at that point I will add formatting to the document. If I read through and deem information unnecessary or decide to add information, I will correct it at this stage. Finally, at this stage I will take the manual to a classmate not in the Mathematics major or professor for peer review to check for any grammar issues or communication issues. The final edits will then be made.

Qualifications and Resources:

I have now been a Mathematics Major here at Longwood for a little over a year. Over the past year, the learning curve with Mathematica for me was extremely sharp. Last spring, I was dumped into a class where we have to complete a long project every two weeks only using Mathematica. During the first couple of projects I struggled to understand what I was supposed to do, because programming in Mathematica is similar to learning a new coding language. Luckily, during the first two projects I had a partner who could work the program efficiently, but that’s where my luck ended. In the following projects throughout the semester, I was forced to learn and master the program, because my partners refused to. By the end of the semester, I was fluent in the Mathematica “Language”.

The sources I would use for this manual would be the Mathematica Help forums and other unofficial forums found on the internet. Also, I will be using my professors and peers as sources in order to read over my manual to give me feedback.

Work Schedule:

Task / Time Required / Estimated Completion Date
Research both the Mathematica website’s help section, and online help forums. / 4 days / September 16th
Talk to professors and students as to what they would include in the manual. / 1 week / September 23th
Write a rough draft of the manual. / 1 week / September 30th
Have peers from the Math Department review the draft. / 3 days / October 2nd
Make revisions to draft that are appropriate. / 1 week / October 8th
Peer review with those outside of my department / 4 days / October 12th
Make final changes to manual before final submission. / 5 days / October 17th