Commentary requirement
There is no
specific format for the commentary as long as you cover the main points,
limitation and relate the paper to your personal knowledge and other topics. One
possible format is
--------------------------------------------------------------------------------
Commentary
Paper: Name of the
paper
First paragraph: summarize the main points of the pape
Second paragraph: point out the limitation of the
paper
Third paragraph: Relate this paper to your personal
knowledge or related topics.
--------------------------------------------------------------------------------
The commentary should fit into one page.
The main component of the course grade is the
project (10% proposal, 20% final presentation, 50% concrete deliverables - see
below). The written commentaries on the papers and student participation
form the remaining 20%. Student presentation and discussion of research
papers carry bonus points.
Projects
The main deliverable of the course is a
self-proposed project. Students (individually or teams of maximum 3) will
design, propose, and implement a project relevant to the enterprise computing
theme. Typically, this will be the construction of some system component
supporting enterprise computing (e.g., electronic commerce or supply chain) or
an enterprise application. Other ideas are certainly possible. You
are encouraged to discuss your ideas with the instructor before proceeding to
the proposal stage. Since this is the first time the course is being
offered, there are no previous examples of project proposals. However, you
may want to look at the project proposals for the course CS8803H (Sp’04)
Advanced Internet Application Development (see <http://www.cc.gatech.edu/~lingliu/courses/cs8803/project>).
You may find examples that give you an idea of the format and length of typical
project proposals. Some ideas for projects follow.
- Mainstream
EComm software. (1.A) Download one of the application servers (e.g.,
WebLogic or Websphere) and use it to build an ecommerce service; run a
simulated or real workload to evaluate its performance. (1.B) Take an
existing ecommerce service and implement it on a different platform (e.g.,
take a service based on Websphere and implement a subset on .NET), then
compare their complexity and performance. (1.C) Add support for wireless
(e.g., cell phone) access to some ecommerce service.
- Research
topics: (2.A) Evaluate the privacy guarantees given by various ecommerce sites
and how they are implemented. (2.B) Evaluate the strategies the large
ecommerce sites are using to defend themselves against denial-of-service
attacks.
Exceptional projects may be expanded as research projects for additional
credit.
Project Requirement
Project Reports
Report
You will need to submit a
project report as a capstone to your project work for this course. The report
ties together your contributions and serves as a "map" or "root document" to
guide us through the corpus of your group's work. We will use the requirements
from last Spring's 8803 Internet Applications course
(here).
Content: Your report should include the objectives of your project, the
research problems you are addressing, the approach/methods you took for
evaluation of your results, the architecture and functional components of your
prototype system, three most interesting contributions of your project design
and/or implementation. (Much of this can come from your proposal.) You are also
expected to summarize
- what
you have learned through the hand-on experience of doing this project, and
- what
concepts and techniques you learned in class are used in the current project
design,
- and
(c) what concepts and techniques you learned in class can be considered for
extension of your current project.
Format: I expect the report to be well written and documented
with references. The presentation style and quality (syntax and grammar) are an
important part of the evaluation and grading of your final project. As the
length of the reports, there is no specific rules, and quality is more important
than quantity. However, as a general guideline we'll be expecting report lengths
of 5 to 10 pages.
|
Date |
Group 1 |
Group 2 |
Group 3 |
Group 4 |
Group 5 |
|
4/12 |
Markus Hedwig, Simon Malkowski, Jason Parekh |
Martin Engel |
Girish Saini |
Closed |
Closed |
|
4/24 |
Qifeng Lin |
Sam Young |
Aditi and Asmita |
Danesh Irani and Tim Garcia |
Closed |
|
4/26 |
Chris Lewis |
Tan |
Jason Spain |
Saurabh Chobe |
Anand Loganathan |
Please e-mail jparekh@cc.gatech.edu to sign up.