A project for C/C++ programming, CSCS1320S14, by Alana Whittier during the Spring semester 2014.

This project was begun on March 7, 2014 and it took nearly 3 days to complete.

The purpose of this project is to write a program that utilizes a mental math trick to determine what day of the week that January 1st of any given year falls on in the 21st century. A two digit year (between 2001 and 2099) is input from the user and is computed using a series of selection statements to derive the day of the week that Jan 1st falls on per calendar year, minus one day for leap years.

In order to successfully accomplish/perform this project, the listed resources/experiences need to be consulted/achieved:

Resources:

• http://vpcalendar.net/when-is-the-next-leap-year.html
• project assignment page
• consultation with C/C++ programming instructor, Matt Haas

Experiences:

• ability to obtain user input
• ability to obtain the day of the week January 1st falls on per given year.
• ability to use selection statements to achieve desired result
• ability to use Bitwise && to distinguish between leap year and non-leap year

The purpose of this project is to use a mental math technique to programmatically compute the day on which January 1st falls per given calendar year in the 21st century. The “mental math” trick is used to simplify the process of computation without being dependent on a calculator. To see how this particular technique works for computing the week day that January 1st falls on, see the assignment link below. Project: MENTAL MATH (DAY OF WEEK) To implement the program to compile and execute successfully, it is required to know how to determine leap years from non-leap years. As we experience leap years as much as every four years, simple algorithms can be used to determine the leap year. However, every 100 years, a leap year is skipped to make up for the 11 minutes removed from the 365.25 day calendar year.

Give a general overview of your anticipated implementation of the project. Address any areas where you are making upfront assumptions or curtailing potential detail. State the focus you will be taking in implementation.

State and justify the attributes you'd like to receive upon successful approval and completion of this project.

• attribute1: why you feel your pursuit of this project will gain you this attribute
• attribute2: why you feel your pursuit of this project will gain you this attribute
• etc…

The actual steps taken to accomplish the project. Include images, code snippets, command-line excerpts; whatever is useful for intuitively communicating important information for accomplishing the project.

Upon completion of the project, if there is an applicable collection of created code, place a copy of your finished code within <code> </code> blocks here.

/*
 * hello.c - A sample "Hello, World!" program
 * 
 * written by NAME for COURSE on DATE
 *
 * compile with:
 *   gcc -o hello hello.c
 *
 * execute with:
 *   ./hello
 */
 
#include <stdio.h>
 
int main()
{
    printf("Hello, World!\n");    // Output message to STDOUT
    return(0);
}

Again, if there is associated code with the project, and you haven't already indicated how to run it, provide a sample run of your code:

lab46:~/src/cprog$ ./hello
Hello, World!
lab46:~/src/cprog$ 

Comments/thoughts generated through performing the project, observations made, analysis rendered, conclusions wrought. What did you learn from doing this project?

In performing this project, the following resources were referenced:

• URL1
• URL2
• URL3 (provides useful information on topic)
• URL4

Generally, state where you got informative and useful information to help you accomplish this project when you originally worked on it (from Google, other wiki documents on the Lab46 wiki, etc.)