Research Presentations


I. Overview

Each student will pick up a topic and prepare a presentation
in class. The grade for your presentation will reflect:
 (a) the depth of the research done on the subject;
 (b) the ability to answer questions posed in class;
 (c) the quality of the presentation.
See the class description for the weight of the research
presentation on your course grade.

For the presentation a student will have to:

    1. Carry out a literature search and read several papers.
       I will assist those who have real problems in finding
         references but you are mostly on your own.
        Hint: use Web search engines to locate materials of
         interest. Come during my office hours and talk to me.
    2. Decide upon a subset of papers judged to be the most
        relevant for the subject.
    3. Prepare a brief (one page) abstract of each paper selected in
       step (2). Use the original abstract of the paper as a model, but
       add to it your own evaluation of the paper in terms of:
       relevance to the subject, difficulty, clarity of presentation.
    4. Create a document including the abstracts and send it to me
       at least two weeks prior to the scheduled presentation in class.
       The document should be written in Word and drawings should  be
        done using Visio. The bibliography should follow the format
       below.
    5. Prepare a class presentation. The presentation should last
        about  45 minutes and you should leave 15 minutes for
       questions. The presentations should be done in Powerpoint
        with drawings in Visio. You will need 20-30 slides.
    6. Send me an electronic copy of your presentation 2 days prior to
        your scheduled talk.

II. Topics

1.    Javaspaces and T Spaces
                        Who: Theresa Tamash
                   When:   Monday, November 4, 2002    
2.    PNML - Petri Net Markup Language.
                      Example
              Who:  Nick Paladino
                   When: Monday, September 23       
3.    WSDL - Web Services Description Language
                      Example
                      Who:     Jason Glenn
                   When:   Monday, September 30, 2002 
4.    WSFL - Web Services Flow Language
                      Who:     Guoqiang Wang  - gwang@cs.ucf.edu
                  When:    Monday, October 7, 2002
5.    WfDL - Workflow Description Language and Workflow Patterns.
                      Who:      Li Wang
                   When:     Monday, October 14, 2002
6.    SOAP - Simple Object Access Protocol
                        Who:    Juan Vargas   
                When:    Monday, October 21, 2002
7.   Planning algorithms
                Who:     Han Yu
               When:      Monday, September 9, 2002
8.   RDF - Resource Description Framework
                      RDF Write-up
               Who:     Jon Catlett
               When:   Monday, October 28, 2002  
9.    Java for Embedded Systems                      
               Who:    Felix Hamza Lup
                   When:   Monday, November 18, 2002     
10.   Globus
                      Who:  Yayati Kasralikar
                   When:  Monday, November 25, 2002  

               

The research presentations will be assigned on a
first-come-first-served (FCFS ) basis.
I will schedule the class presentations to integrate
well with the flow of the class.

 III. Sample literature       

[Aal00] Aalst,  W.M.P. van der (2000). Workflow Verification:
   Finding Control-Flow Errors Using Petri Bet-Based Techniques.
   In: Business Process Management (Aalst,  W.M.P. van der, J. Desel,
   A. Oberwies, Eds.),  LNCS, vol. 1806, 161-183.


[Ber98] Berman F. (1998). High Performance Schedulers. In:
    The Grid. Blueprint for a New Computing Infrastructure
    (I. Foster and C. Kesselman, Eds.). Morgan Kaufmann, 279–311.


[BKM98] Barzilai, T., D. Kandlur, A. Mehra, D. Saha, and S. Wise (1998).
    Design and Implementation of an RSVP-Based Quality of Service
    Architecture for ` Integrated Services Internet’. IEEE J. Selected
   Areas in Communications, 16(4).