This assignment has been designated by the Department of Computer Science for assessment of certain expected outcomes for its degree programs, as required by our accreditation agencies, the University, and the State of Florida. Departmental policy does not permit a final grade of "C-" or better to be assigned unless the student has earned a grade of "C-" or better on this assignment, regardless of performance on other work in the course.
Presentations are scheduled at recitation time. Recitation attendance is mandatory. An attendence sign-up sheet will be distribtuted at each recitation. There is some time left by the end of the recitation section for questions on the lecture material and projects.
Oral Presentation and Presentation Paper Requirements
An oral classroom presentation is required by each student, see the presentation schedule below. The presentation material (the presentation slides) together with a paper describing your investigation of the topic should be submitted for grading at the end of the term before exam week starts:
- Presentations will be held at recitation time on Monday 1:25PM (Section 1) and Wednesday 2:30PM (Section 2) according to a presentation schedule. Presentations in PPT or other electronic format is required (see below). Upload your presentations to your home page to enable classroom PC access. You can bring your laptop computer, but be prepared to run the presentation from the classroom PC in case the laptop cannot be used. Presentations should take 12 minutes. Presentations must not exceed 15 minutes and will be terminated when 15 minutes have passed.
- The individually-written technical paper on the presentation topic must be submitted for grading before exam week. The paper must address the topic at sufficient depth.
Departmental policy: You need to earn a grade of "C-" or better for the oral presentation and a "C-" or better for the written paper to pass this course.
Students with disabilities will be given an alternative option for the oral presentation. Please contact the instructor to discuss these options.
The format of the oral presentation is electronic in a format of your chosing, e.g. OpenOffice, PowerPoint, PDF, or text. However, visual aids such as images, tables, and graphs must be presented in a clearly understandable format. You may use the whiteboard (or blackboard) if you wish to comment on questions, but you must not depend on them.
The presentation paper should have a title page (with title, author, and date), a short abstract that summarizes the content in one paragraph, an introduction section that states the question/problem to investigate with a discussion on how you approached the problem, the paper body (several sections), a conclusion that summarizes your results and findings, and a bibliography of references to papers and web sites you consulted.
Evaluation and Grading
The grade breakdown of the presentation component of the course (10% of the total final grade) is 5% credit for the oral presentation and 5% credit for the paper.
The evaluation of the quality of the presentation (as well as the paper) will take into account the originality, relevance, and currency of information that you present, as well as the clarity of the presentation. The presentation will be scored according to the following table.
Grading criteria for oral presentations (50 pts possible):
- Student is prepared and ready to begin on time (0 or 5)
- Student is within the prescribed time limits of 12 to 15 minutes. (0 or 5)
- Student speaks audibly and clearly. (0 to 5)
- Student presentation is well organized. (0 to 10)
- Student's visual aid is appropriately used and enhances the presentation. (0 to 5)
- Student addresses all issues mentioned in the topic description. (0 to 10)
- Student explains the material well, going appropriately in depth given time constraints. (0 to 10)
To address all issues in the topic description you need to find resources for your presentation, such as textbooks, Web sources (you can trust), and/or technical papers (when applicable). Consult these resources to prepare a presentation that explains what your topic is about and what it does. Suggested is to add a bit of history that explains the origin and/or the context of the topic, when applicable.
Please be prepared to start on time when you are presenting. If you get started late not only will you lose points, but we will have difficulty finishing within the class period.
A presentation will be graded with 0 points if you don't show up, or spent less than 8 minutes on your presentation, or if your presentation material is not legible.
The presentation paper will be graded using the following criteria (50 points possible):
- Organization: title, introduction, conclusions, and layout of sections. (0 to 10)
- Completeness of references in bibliography (did you check up-to-date technical papers, textbooks, and/or trusted on-line resources?). (0 to 10)
- Depth and thoroghness of your research (are the questions answered with sufficient evidence provided by your results?). (0 to 10)
- Accuracy of your conclusions (are the conclusions an accurate summary of your findings and recommendations?). (0 to 10)
- Clarity of writing and use of correct grammar. (0 to 10)
The paper length is not limited, but should be at least four pages of double-spaced 11pt font.
Warning on plagiarism: do not copy/paste material without properly quoting the text and citing the recourses. For example, if you found a definition of a term in a paragraph that you would like to refer to, use the common citation requirements: "...sentence..." [ref], where ref is a citation in your bibliography. Note that quotes are needed when you copy text literally.
Four presentations are scheduled per recitation section. For a description of the presentation topic, see below (refresh this page to see changes).
||COP4020 Section 1
Mondays 1:25 PM to 2:15 PM
Presentation Topic :- Name
A2 :- Weaver Hastings
A3 :- Bryan Franklin
A4 :- Shawn Rutledge
A5 :- Reynaldo Campos
A6 - David Fernandez
A9 :- Benjamin Buzbee
A11 :- Michael Marshall
A13 :- Kenta Sugimoto
B1 :- Josh Decker
B2 :- Christopher Cassano
B4 :- Thomas Cubertson
B5 :- Stephan Walters
B7 :- William Rodrique
B9 :- Adnan Chowdhury
B10 :- Ricardo Pascal
B11 :- Justin Oglesby
B13 :- Brandon Davis
C3 :- Caitlin Carnahan
C7 :- Brendan Blanks
C8 :- Bryan Pollack
C13 :- Cody Hansen
C14 :- Andrew Wilcox
C15 :- Troy Rosenberg
C16 :- Steven Rutkowski
A1 :- Brian Wilder
||COP4020 Section 2
Wednesdays 2:30 PM to 3:20 PM
Presentation Topic :- Name
||A7 :- Luke Johnson
A8 :- Daniel Porrello
||A10 :- Jason Eick
A12 :- Manuel Montes De Oca
B3 :- William Sinkey
||B6 :- Heidy Khlaaf
B8 :- Amanda Kerber
B12 :- William Hightower
||B14 :- Nkemdirim Dockery
B15 :- Matt Fisher
C1 :- Christopher Burt
||C2 :- Richard Kirk
C3 :- Michael Longchamps
C4 :- Charles Maranto
||C5 :- Thomas Licostie
C6 :- Michael Backherms
C7 :- Christopher Shirley
||C9 :- Troix Douglas
C10 :- Tristan Capron
C11 :- Michael Sodders
||C12 :- Gabriel Enslein
C13 :- Scott Hess
C17 :- Caleb Gross
||Reserved for scheduling changes
The presentation topic assignments are decided by the instructor based on student preferences. Students can pick one topic from each of the three categories A, B, C below, thus indicate three preferenes. The instructor will match a topic to a student based on preferences, though there is no guarantee that all students can be matched if the presentation topics of their choice is popular. The preference selection sheet is downloadable .doc here.
- Ruby: describe the scripting language Ruby.
- Python: describe the Python scripting language.
- PHP: describe the server-side scripting language PHP.
- Perl: describe the Perl scripting language.
- LSL: describe the Linden scripting language used in Second Life.
- ActionScript: describe Apple's ActionScript scripting language.
- VBScript: describe the Visual Basic Scripting Edition language.
- Lua: describe the Lua scripting language.
- APL: describe the APL programming language known for "throw-away programming"
- NXT-G: describe the NXT-G graphical programming language developed by National Instruments in LabVIEW for LEGO NXT.
- MEL: describe the Maya Embedded Language (MEL) used in Autodesk Maya.
- Squirrel: describe the Squirrel script language used in some video games.
- COBOL: describe the COBOL programming language.
- Objective-C: describe the C++-like OO programming language. How does it compare to C++?
- Forth: describe the Forth programming language.
- Go: describe Google's programming language Go.
- D: describe the programming language D.
- Scala: describe the Scala programming language.
- Mercury: describe the logical programming language Mercury that is based on Prolog and Haskell concepts.
- ADA 2005: describe the ADA 2005 programming language.
- Delphi: describe the Pascal-like Delphi programming language.
- HPF: describe the High-Performance Fortran programming language. How is parallel execution specified in HPF? How are distributed arrays specified?
- Erlang: describe the functional language Erlang inspired by Prolog (e.g. show the similarity of Erlang variables with Prolog variables).
- Caml: describe the Caml programming language.
- Eiffel: describe the OO programming language Eiffel and the "design by contract" principle.
- Icon: describe the Icon programming language.
- Basic: describe the original Basic programming language or one of the many dialects such as Quick Basic (do not pick Visual Basic - see VBScript).
C. Tools and Specification Languages:
- Lint: describe the "lint" tool to find problems in C code. Also discuss its relative "splint" for finding security vulnerabilities.
- Doxygen: describe the "Doxygen" tool and how it can be used to document C and C++ source code.
- Make: describe the "make" utility and its specification language that defines the project build dependences and commands. For this topic a focus on advanced features is preferred.
- Eclipse: describe the "Eclipse IDE" and show its support for C, C++, or Java project development.
- SWIG: describe the "SWIG" specification language and tool.
- Z: describe the specification language based on "Z notation" (Zermelo-Fraenkel set theory).
- VDM: describe the Vienna Development Method (VDM) and specification language VDM-SL and/or VDM++.
- XML and XML Schema: describe the XML markup language format and the role of XML Schema to define valid XML (XML Schema, like a class definition, specifies structure while XML instances, like objects, contain valid data).
- XSLT: describe the XSLT (Extensible Stylesheet Language Transformations) declarative XML transformation language.
- XQuery: describe the XQuery XML query language.
- RDF: describe the Resource Description Format in XML. RDF is a metadata data model. RDF is a general method for conceptual description or modeling of information that is implemented in web resources, e.g. using XML.
- gSOAP: describe the "gSOAP" C/C++ XML data binding tool. What C/C++ type declaration extensions does it use to bind XML to C/C++? Give an example client/server implementation.
- VHDL: describe the VHDL hardware description language. Is VHDL also suitable as a programming language or only as a hardware design language? Why not use C to describe hardware?
- TeX/LaTeX: describe the TeX/LaTeX document markup language. The LaTeX "programming language" has markup syntax and programming constructs such as "if" and TeX operates by macro expansion that resembles function invocation.
- MATLAB: describe the MATLAB programming language for science and engineering.
- SAS: describe the SAS system and its 4th generation programming language.
- LePUS3: describe the object-oriented, visual design description language LePUS3 for software modeling and formal specification.
Copyright: Robert van Engelen, Florida State University, 2011.
Last modified: Monday, January 24, 2011