Specifications for Student Work in MTH 325

This document can be found online:

The rubrics below are used to determine whether your work on various assessments receives a Pass or No Pass mark. Therefore you should keep a copy of these specifications nearby when doing your work and make yourself familiar with them.

In what follows, we will define the standard audience for MTH 325 to be:

Classmates in MTH 325 who are familiar with the mathematical ideas discussed in the class and have the appropriate background knowledge for the class, but who are unfamiliar with the particular problem whose solution you are presenting.

Specifications for Concept Checks

Most Concept Check items will be objective in nature (true/false, multiple choice, etc.) where only the answer is graded. The sole specification for this work is that the answer must be correct and clearly indicated on the Concept Check form.

Specifications for CORE-M objective problems

These are done during timed assessment periods and address CORE-M objectives, which are usually computations or construction of examples. Your work on these problems must follow these specifications:

Specifications for Learning Modules

Learning Modules involve solving problems, like you will do on CORE-M problems, but with significantly more high-level work involved. All Learning Modules must abide by the following basic formatting rules:

Work on Learning Modules includes not only solving applied mathematical problems but also programming, writing mathematical proofs, and writing responses to questions that are not necessarily mathematical in nature. Below are lists of specifications for each kind of work.

Specifications for general writing

In addition to particular specifications that might be given in the Learning Module itself (for example, a minimum word count), all written work -- including writing that is part of a mathematical calculation or proof as well as writing outside of a mathematical context -- must abide by the following:

Specifications for mathematical problem solutions (that are not proofs)

When writing a solution to a mathematical problem, or writing a narrative that contains significant mathematical work in it, your work should abide by the general specifications for writing above and the specifications for mathematical work listed in the section on CORE-M problems above. This applies to all problems that are not proofs or programs; for specifications for proofs and programs, see below.

Specifications for mathematical proof

If you are writing a mathematical proof, your work should meet all the specifications for general writing and all the specifications for mathematical writing, and the following:

For more details on proof specifications, please see Appendix A: Guidelines for Writing Mathematical Proofs from Ted Sundstrom's Mathematical Reasoning: Writing and Proof provided on the Blackboard site. These guidelines are the standard specifications for proof writing used in all proof-based courses at GVSU.

Specifications for computer programs and code

Some Learning Modules involve writing and submitting computer code in the form of user-defined functions written in Sage or single computations done in Sage. Often, these are to be turned in by placing them in a folder in your SageMath Cloud shared MTH 325 project. Computer work must follow these specifications: