[CSC 415] Presentation Format for Next Week

[Christian Steinmeyer]

Here is a dummy presentation, that we could use:
https://docs.google.com/presentation/d/12J_oTHBdLnXehur5pj0vfE63KybKfkFE15LKQfEXr_4/edit?usp=sharing

2015-04-29 15:25 GMT-04:00 Andrew J. Pounds <pounds_aj at mercer.edu>:

>  Okay -- so for the presentation next Tuesday I would like there to be
> some form of a "powerpoint" style presentation.   Since you will most
> likely be working under Linux to make it easy to switch back and forth
> between the presentation and the tank program,  I would prefer that the
> presentation be done in "Google Slides".  This should also make it very
> easy for you all to collaborate on the document.
>
> Here are some of the specifics:
>
> 1. Title of project, with all your names as authors
>
> 2. A brief list denoting what each of you were responsible for
> contributing to the project. I believe this is listed on the Wiki.
>
> 3. A slide briefly describing the process of "building" the code.   In
> other words, how did each of you start making contributions?  Was there any
> planning?
>
> 4. With respect to planning and development, describe if and how using a
> code management system helped in the development process.  Just for grins,
> take a look at the "Tank" network in GITLAB.
>
> 5. For each major component (Like buildings, the tank, collision
> detection, explosions, subwindows, pipeline, etc.) there needs to be a
> slide denoting who the actual major contributor(s) to each component were
> and if there were any ancillary contributors.  Following each of these
> slides needs to be a list of the "challenges" you faced in getting this
> feature to work and the things you had to learn (graphically,
> mathematically, coding wise, etc) to make this feature work.  Each person
> needs to talk about his slide(s)
>
> 6. After you describe all of the features, fire up the program and
> demonstrate the great work you have done.
>
> 7. Finally, return to your slideshow and describe any improvements you
> would like to make to the tank program and propose how you would do it.
> Each developer should contribute at least one idea.
>
> --
> Andrew J. Pounds, Ph.D.  (pounds_aj at mercer.edu)
> Professor of Chemistry and Computer Science
> Mercer University,  Macon, GA 31207   (478) 301-5627http://faculty.mercer.edu/pounds_aj
>
>
> _______________________________________________
> csc415 mailing list
> csc415 at theochem.mercer.edu
> http://theochem.mercer.edu/mailman/listinfo/csc415
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://theochem.mercer.edu/pipermail/csc415/attachments/20150429/92c3ae83/attachment.html>