To provide a list of programming projects to aid in the understanding of course concepts and gaining of valuable development experience.

A core part of your work in the course will revolve around performing projects. This will offer you many opportunities to both learn and apply important concepts, and achieve a better mastery of material.

The method of undertaking a project will generally take the following form:

1. Identify a project: Figure out what interests you and what you'd like to do
2. Create a page on your portfolio on the wiki and create the proposal
3. Justify your case for the project on the proposal
4. Notify me of your project proposal (send me a URL to the proposal)
5. Upon reading your proposal, I will communicate approval, disapproval, or suggestions to improve the proposal to work towards approval.
6. Once receiving approval, you will commence on project implementation, extending the proposal document into a general project documentation page on your portfolio
7. All development will utilize both the wiki and subversion – only you (or your group) and I will have access to your project repository
8. If you have any questions on the implementation of your project, this documentation should be able to assist debuggers in helping to diagnose any problems you encounter should you have questions/problems
9. When completed, notify me so I can review your documentation (wiki) and code (subversion)
10. I will offer feedback on the project along with final results (did you satisfactorily achieve the desired attributes, etc.)

The aim here is two-fold:

• To generate content for your portfolio (this is an investment that will only increase in value over time)
• To provide a “paper trail” so I know you are doing work, you have content that can be viewed/reflected upon, and you gain experience performing projects

Before starting on a project, you must obtain approval from me regarding the following items:

• The project idea (what is it you are pursuing?)
• The project development environment (who all is working on it? Multi-person projects need good justification. Each group member needs to maintain a documentation page on their own portfolio page)
• The project documentation (where are you putting the documentation? Put all this proposal information on a portfolio page on the wiki and give me the URL)
• The project scope (how detailed are you going to get? This can be difficult to pinpoint exactly, but basically try to describe your anticipated approach)
• The project attributes (why do you feel your project is worthy of certain attributes? Make the case for each of them)
• The project deadline (how long are you anticipating working on the project?)

If desired, a sample template is available here that you can copy and paste into an applicable portfolio page.

All projects undertaken need to be documented on the wiki in your portfolio namespace. Specifically, you should set up a front page at:

• http://lab46.corning-cc.edu/user/username/portfolio

And link to projects within the namespace:

• http://lab46.corning-cc.edu/user/username/portfolio/oneofmyprojects
• http://lab46.corning-cc.edu/user/username/portfolio/anotherproject

Project documentation needs to have (at least) the following sections:

• Objective: state the purpose of this project. What is the point of this project? What do we hope to accomplish by undertaking it?
• Prerequisites: what items/ducks do you need to get in order before starting on the project?
• Background: an informative description of the purpose or nature of the project. Be sure to describe the core process being undertaken, any pertinent theories or concepts. Your program/project represents a solution to such concepts/theories. You'll want to give a general overview of what is going to be accomplished.
• Concept Attributes: an identification of the attributes this project possesses (you can claim at most 5 attributes per project, and attribute eligibility is approved by me before starting on the project)
• Scope: present on the project proposal- give some initial brainstorming/overviews of the steps you anticipate taking to accomplish the project.
• Procedure: For non-code specific projects- the actual steps taken to accomplish the project.
• Source Code: the actual source code of your project contained with wiki <code> </code> blocks.
  • Code must have the following identification information in a comment banner at the top of the code:
    • author
    • course
    • semester
    • project identification information/abstract
    • compiling/build instructions
    • execution instructions
  • Code must have intuitive comments throughout, especially:
    • clear identification of important/central processing tasks in the code
    • description/purpose of any functions
    • organization of code components (variables, preprocessor directives, etc.)
  • Code must be indented, which means:
    • usage of a consistent indentation pattern (single tab per level of scope, four spaces, etc.)
    • recognition of blocks of scope (an if statement should not be at the same level as the function it resides within)
    • easy visual comparison among peer blocks and parent/child blocks of scope
  • code is organized and easy to read
    • no intentional double spacing of code
    • intuitive variable names
    • intuitive function names
• Sample execution: within <cli> </cli> blocks (if textual, screenshots if otherwise), an appropriate sampling of your project's execution or output.
• Reflection: thoughts, observations, analyses, conclusions you made while performing the project.
• References: a list of (at least) 2 sources of information pertinent to the project.
• Any unused template items need to be removed; display only pertinent content to the project on the wiki page.

The following are the programming attributes you must consider while undertaking a project for credit in this course:

There are a total of 48 items needed; with a maximum of 8 attributes achievable per project, that makes for a minimum of 6 projects you must perform during the semester.

Note that where multiple quantities of attributes are concerned, only a single instance of an attribute can be achieved on any single project.

You need to keep an inventory of the total attributes you've achieved, displayed on your project portfolio page for this course.

The following are possible sources of projects you can undertake in this course. Note that while most of these can be solved by hand, and some have a single solution, your task is to implement a computer program to solve the problem, making use of the programming concepts and creating effective algorithms for accomplishing these tasks.

Projects here are listed in no particular order, please do not correlate difficulty with arrangement.

Again, these are not the only nor required projects, they are suggestions and worthwhile explorations. It is highly recommended you at least start with some of these projects, then as you find a particular direction or interest, pursue it.

A couple things to keep in mind:

• be creative in your design and implementation of your project code.
• consistently indent your code so that it is readable!
• document your code so I know you know what you're doing
  • and, weeks from now, so will you.
• Polish your output so it appears consistent to the end user(s).

In addition to posting the appropriate project documentation under your portfolio namespace, you must also attend to the following:

• placement of your code in your ~/src/hpc1 directory (or subdirectory therein)
• addition/commit of source file(s) into your repository
• notify me of project submission