Biweekly Project Progress Report 2

 

Team One

 

June 28, 2003

 

Team Members:             John Mickus (leader)

Ari Adelberg

R.J. De Castro

Pik Chan

Saksit Siriprayoonsak

 

The following table summarizes the progress of each team member:

 

Name

Progress Achieved

(June 14th – 27th)

Current/Future Progress

(June 28th – July 11th)

John Mickus

1.   researched on the following issues:

·   usage of XML in standalone software

·   how Perl may be useful in these applications

·   CGI modules and their possible application with XML

 

2.   decided on basic structure of our database group project

 

3.   met with group on two different occasions and decided on new systems for creating bi-weekly progress reports.

 

4.   delegated responsibilities to each group member for the group project.

 

5.   completed compilation of research material from group members and submitted final result to Saksit for conversion into PowerPoint format

1. Ari Adelberg has taken on the responsibility of maintaining the two basic tables needed for the database of our group project. 

 

2. Any new tables will be delegated to other members to help distribute workload.

 

3. In preparation for our group project, responsibilities have been delegated to members as follows:

·   R.J. De Castro – Anonymous Inventory Searching

·   John Mickus – Interface for Adding/Removing Inventory

·   Ari Adelberg  - Login Screen for Employee

·   Saksit  - Interface for Rental Checkout/Return

·   Pik Chan – Interface for Adding/Removing Personnel

Ari Adelberg

1.   Supplied the “XML::Generator And Related Modules” portion of our group research assignment.

 

2.   Editing group research project during Saksit’s final preparation of the slides for the PowerPoint presentation.

 

3.   Produced rough draft of entity-relationship design for our database project “Rental Regulator” .

 

4.   Prepared a miniature lecture about XML for group research presentation

1. Finalize table design for first increment of our database project “Rental Regulator”.

 

2. Create tables for “Rental Regulator” in group Oracle account.

 

3. Supply team members with Oracle code/instructions for creating identical tables in their personal Oracle directories for use in development.

 

4. Begin working on Perl/Oracle code for “Rental Regulator” login screen.

 

5. Present “Introduction to XML” materials to class during our group research presentation on June 28th.


 

Name

Progress Achieved

(June 14th – 27th)

Current/Future Progress

(June 28th – July 11th)

R.J. De  Castro

1.  Researched on Perl & XML related subtopics.

 

2.  Decided to focus on the most commonly used Perl XML interface modules such as XML::Simple, XML::SimpleObject and XML::TreeBuilder

 

3.  Researched the said modules and wrote that section of the group research paper.

 

4.  Discussed with team members the specifics of the database project “Rental Regulator”

1. Research on how Oracle and Perl work together

 

2.        Figure out a design to implement the search feature of our program

Pik Chan

1.   Researched on how Perl XML modules parse and validate XML documents.

2.   Wrote the “Parsing and Validating XML  Documents In Perl” section of the group research paper

3.   Formatted the final group research paper

4.   Research on Perl XML modules including XML::Parser, XML::XPath, XML::Writer etc. for individual paper

5.   Attended group meetings on our database project and chose the “Adding/Removing Personnel” feature to implement

6.   Compiled the bi-weekly progress report 2

1. Research on Oracle/Perl.

2. Begin to work on Perl/Oracle code for the “Adding/Removing Personnel” feature of our database project.

3. Prepare for individual paper presentation.

Saksit Siriprayoonsak

1.    Researched on what is XML and how Perl and XML are related.  Summarized about XML.

2.    Selected “Using XML and Relational Database with Perl” as subtopic.  Wrote a summary of the subtopic for the group research paper

3.    Studied the DBI Module, DBI::XDBMS Module and its code

4.    Generated the group research paper in PowerPoint format for group presentation

5.    Discussed with team members on the database project “Rental Regulator”

6.    Kept progress status report for the team

1. Give a presentation on group research paper

2. Research on Oracle, such as how to create a table, update table and record.

3. Research on how Perl works with Oracle.

4. Write code for the “Rental Checkout/Return” feature of the database project

5. Debug the code and combine with other team members’ code. 

 

 

 

Four team meetings were held since June 14, 2003.  Details of each meeting are summarized as follows:

 

On June 14, 2003

 

The following issues were accomplished during our team meeting on June 14, 2003 at SDSU campus:

 

·       All members will e-mail their final drafts for the group research paper to John by June 19 midnight so that John can compile them. 

·       John will forward a copy of the compiled group research paper to Saksit on June 20.  Saksit will transform the group research paper into a PowerPoint format and he will also add graphics to it.

·       Pik will prepare the biweekly project progress report 2.

·       Individual topics for the research paper were selected:

1. John – Usage of Perl & XML in Standalone Software Packages

2. Ari – Using Perl & XML to store Program Configuration Data

3. R.J. – Perl XML QuickStart: The Perl XML Interfaces

4. Pik – Parsing and Validating Document in Perl

5. Saksit – Using XML and Relational Database with Perl

 

On June 17, 2003

 

The following issues were accomplished during our online meeting on June 17, 2003:

·       Group Project topic was selected. 

·       Ari will prepare the Group Project Topic Description.  He will circulate it to all members for comments.

·       Ari will then incorporate all members’ comments into the Group Project Topic Description.

 

On June 23, 2003

John Mickus and Ari Adelberg met for about two hours to discuss several issues which ranged from the database design to the planning of the next day’s group meeting.  Several changes were made to the database design, including the elimination of the “Customer/User” entity.

 

On June 24, 2003

Group meeting took place on SDSU campus.  Responsibilities were delegated to each group member and Ari Adelberg was appointed as “DataBase Administrator”.  We discussed plans for group research presentation (such as who will speak and what will be cut out).  Moreover, changes were made to the database design.  We begin to work on group project.