Project Introduction

During this project, you will write a program that demonstrates what you have learned about C++. The theme or type of program is up to you except the project cannot be a store (retail establishment selling items), solar system catalog, stellar catalog, or contact list. Also, the topic must be respectful of others and appropriate for a family-oriented audience. Be sure you have covered all topics listed in the specifications.

Project Specifications

Develop an object-oriented computer program illustrating the following features of the C++ language. Code from assignments may be reused, but must be applied to a different application than the original assignment. The numbers in parenthesis are the point value for successfully using the feature, as described in the grading criteria.

Do NOT use global variables (-10 if you do), create a prohibited project (-20 if you do) or use inappropriate material (-5 per item if you do).

Global constants are acceptable.

Construct one or more objects from at least one class that you wrote and make use of the objects in a meaningful way. (6)

Each class must have one or more private member variables and one or more member functions. Your class cannot be named "Product", "Cat", "Bear", "Person" or other example we did in class or homework.

Code and use these control structures:

while or do-while loop (2)

for loop (2)

if or if-else (2)

Code and call these types of functions, besides constructors and main():

void return type (2)

non-void return type (2)

Pass-by-value parameters (2)

Pass-by-reference parameters (2)

Code and call one or more overloaded functions. (2)

List at least two line numbers in the report to identify both versions of the overloaded function. Also, your project must call both functions. An overloaded constructor does NOT meet this specification.

Code and call one or more overloaded constructors. (2)

List at least two line numbers in the report to identify the versions of overloaded constructor. Also, your project must construct objects using all the constructors.

Extra Credit

Present your completed project one class meeting or more earlier than the due date. (2 points)

Develop a graphics-based application (2 points)

Code a function that makes a recursive call. (2 points)

Code a vector of objects for a class that you wrote and process the vector in a for-loop and making use of the size() function. (2 points)

Write and call a function named drawShape() that contains nested loops that displays a shape in your program. The shape must be one we have not used in a lesson exercise of the course. (2 points)

Write and call a sorting function using a known algorithm and apply it to a vector. Name your function sortXXX() where XXX is the algorithm. State your source for the algorithm in your "README.txt" file. (2 points)

Create HTML documentation for your program using Doxygen and submit the documentation in a zip file. (1 point)

Use your imagination and code C++ features not covered in this course -- be sure to clearly identify your creative features and state in your README.txt where you got the extra credit idea or feature. (0 to 4 points)

0: Extra credit feature is trivial, does not work or source is not stated in README.txt

1: Extra credit is simple and works

2: Two simple extra credit features or one complex or imaginative use of a feature

3: Three simple features or one simple features and one complex or imaginative use of a feature

4: Four simple features, two complex or imaginative use of a feature, or some combination

Make certain that your README.txt file lists any extra credit attempted and the file and line number of the extra credit where appropriate. Without the file and line number I may not see the extra credit.

Project Report

The final report is an enhanced README.txt file. Start with the usual README.txt information but add the following:

Brief introduction describing the purpose of your project and application

One paragraph is sufficient

A description of how to use your program

A list of the specifications with a specification number, short specification description, file name, line number and other information as needed whether you met the specification or not.

If you do not list the specification, with a specification number, short specification description, file name, and line number, then you will not get credit. One example is sufficient though some examples, like overloaded functions, require two line numbers.

Project Presentation

You must demonstrate your project on the assigned day, but not necessarily in front of the class

When everyone else is done, you may present it to the instructor individually

Make certain you upload your project to Canvas before class

Give a copy of your project report to the instructor before your presentation

Plan on keeping the presentation to 5 minutes or less.

Suggested Presentation Flow

State your name and your project's name.

Briefly state your program's purpose.

Compile your source code.

Demonstrate your program, explaining features and source code as you go including:

Show the file that your program reads from and writes to

If implemented, show recursive function calls

Show creative code features

Show and explain source code when requested

Feel free to refer to or display your written report during the presentation. Show the file that your program reads from and writes to. Point out as many of the cool features as possible so we can all admire them.

Summarize the project.

When the demonstration is over, or your time is up, then quickly summarize the program's purpose. Then pause for about 10 seconds to give us a chance to applaud!

Lab Exercises

Keep doing the CodeLab exercises each week before the specified due date while you work on your project. Refer to the assigned reading for the next lesson to help you understand the problems. Use the online lecture notes for more information as the notes become available.

Grading Criteria

The instructor will evaluate your assignment using the following criteria. Each criteria represents a specific achievement of your assignment and has a scoring guide. The scoring guide explains the possible scores you can receive.

Some scoring guides have a list of indicators. These indicators are a sign of meeting, or a symptom of not meeting, the specific criterion. Note that a single indicator may not always be reliable or appropriate in a given context. However, as a group, they show the condition of meeting the criterion.

Deliverables

Submit your assignment following the instructions for homework. Do not turn in the in-class exercises. If you decide you must turn in the in-class exercises, create a folder named "exercises" (without the quotes) and place all your exercises from lesson 13 and 14 into this folder. Then zip the folder into a single archive file. CodeLab is submitted automatically.

Include the following items for grading:

README.txt file containing the project report

All source code files for your project

Any data files required

A separate zipped folder containing your lesson exercises (optional)

You must submit all the files needed to make your project function properly. Do not assume that the instructors has any files. Your assignment must work as submitted.

Provide a paper copy of the README.TXT report to the instructor before presenting your project.

Submit your project report as the README.txt file. Do NOT submit any Word files, as the instructor does not want any bloated files or viruses.