Project: Deliverables and Guidelines
Project 1 Due Date: October 31, 2008 (9:30AM)
Project 2 Due Date: December 8, 2008 (9:30AM)
Draft of this Document: September 30, 2008
Goal for Project 1
The goal of Project 1 is to construct a model and
a simulation (i.e., execution) of that model. The model
and simulation results must be visually represented, and
the simulation must be interactive so that model inputs
and parameters can be modified.
Goal for Project 2
The goal of Project 2 is the same as project 1, with
the ability to form teams (of no more than 2 people).
Also, it is possible to build simulation tools
if desired.
Project
Your project must have the following characteristics:
- Use one of the following programming platforms:
- Use one of the models learned in the class prior to the project
deadline date.
- Show, and allow interaction-with, both (1) the model of the
phenomenon and (2) the phenomenon. This means that these two
representations can either co-exist in the same visual space or
be connected to each other in some other functional way.
Grading
In general, the grade will reflect the quality of the overall project,
and how many perceived hours were put into it.
Ultimately, significance of a project is defined
relative to what other students in the class turn in.
In almost all cases, perceived effort (after viewing
all implementation aspects) corresponds well with
the grade. Grading, as in the exams, will be separate for each
class (CAP 4800 and CAP 5805).
Specific grading criteria include:
- Overall quality of work
- Perceived effort (time, resources) for project
- Completeness and functionality of work
- Complexity of the project (i.e., difficulty)
- Quality of documentation
- Creativity
Deliverable
Submit using VISTA (instructions will
be provided by the TA using the mailing list)
- FILES: All files (including source code and executables)
- DOCUMENTATION: Your documentation for the project should
be approximately four to five pages, containing figures and interaction
results. Start with the title, your name, your student
id, (1) a summary (abstract) of what you did, (2) an explanation
of what model you used and what you were modeling in terms of
an application (i.e., phenomenon), and (3) description
of the graphical interface layout and how one interacts with
your program. Use diagrams and snapshots of your interface to
fill out the document as required. If you used any libraries or
pre-existing code as part of your project, make it clear which parts
represent your contribution.
Ideas for Projects
- Use past experiences or your interests outside of class to
select a simulation
- Start with a model type discussed in class, and then search
on this model type name to get an idea of different applications
- Pick a domain of interest and search for " modeling",
" model", or " simulation". For Example,
"medicine simulation" or "medicine modeling" (or "modelling").