c

c
c
c
c
c
Date: March 31, 2010
Author: Niranjan Thevathas
Project Manager: Dr. Dario Del Degan
Team Leader: Abdullah Tabassum
Team Members: Sivaprasath Balasubramaniyam and Niranjan Thevathas Patrick
Subject: ECE297 Communication and Design
c

cc


c

The following table lists each of the member¶s contribution over the last week.

Task Person Assigned Due Date Status

Complete code for Abdullah March 31, 2010 completed

assignment 3

Read requirement Patrick April 4, 2010 incomplete

assignment 4

Read requirement Siva April 4, 2010 incomplete

assignment 4

c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c


c
c

The design team focused on three priorities for this week. The primary focus of the design team
was to discuss the design decisions for Milestone 4 and to delegate tasks to the team members.
The design team also focused on completion of code for Milestone 3. Although code was passing
a majority of test cases there were a few corner cases where the program failed. The test cases
we failed was because of the query function, the user enters predicates with each predicate
separated by a delimiter in our case a V

 and within each predicate the column name, the
condition parameter and the condition value can be separated by as many spaces as the user
wishes to enter, we didn't accommodate for this condition and as a result of this our query
function failed. Once we fixed our functions and considered all the corner cases we passed all the
test cases.

Once the team had completed the code for milestone 3, our next focus was to discuss on the
design decisions and to delegate tasks amongst each other for the Final design document. In our
team meetings this Tuesday, the team discussed on concurrencies such as threading, forks and
system select. The team also discussed on transaction handling and the parts of the document
which are required for revision.

As the team is given the leverage of implementing any concurrency mechanism we wish, our
team decided to implement threading. Threading offers read and write lock mechanism which is
a very secure way of handling information as this ensures that no two users at the same instance
can modify the same key; this avoids data corruption and prevents from loosing information. The
team decided that if we have sufficient time we will implement the other concurrences
mechanisms. The design team decided to use the transaction methodology which was provided to
us in the assignment 4 documentation as it is a more logical and secure way of handling
information.

Once the team had discussed on all the design decisions we then delegated tasks among each
member equally (refer to attribution table). At this time we are working on the design document
and we hope to start revising the document from Friday of this week

 
cc  

c
c

Discuss about next milestone.c