Team Meeting

This team meeting was quite long one. We had to meet up on weekend because we were given multiple tasks to complete before the spring break. So we decided to complete the work well in advance. Myself and Jay met in the Lawson around 3:30 pm, we did some amendments related to the ER-model(which was getting regularly modified since many days). Then we had dinner and then again met at Owen residence hall. John joined us in the Owen hall, he already prepared a rough draft what we have to accomplish on that day(thanks to John).I had taken a rough sketch of what was told to be done before Spring break, so I brought that document. Jay had to go to the professor's office and emailed us the chapters 2 and 3 . The chapters had the required information about the ER models and also various other things that we were expected to do. We had to go through the two chapters before the team meeting. As expected we all went through the two chapters.
We made the final ER- model without any more flaws and also the Use-case. The professor asked us to prepare the Tables (the next version of the ER models) for the database. We were busy with the preparation of the tables required the database. Later we started to describe all the attributes of the use case diagram. The description will let people know what exactly is going on in the back end.
For Example:
Add Event:

                 1.     CLICK ADD ADMIN BUTTON 
                 2.     Select * from User
                 3.     Page will be loaded with columns (name, email, room #, adminflag) where adminflag is a checkbox

a.     If adminflag is true, load the checkbox with a checkmark

b.     If adminflag is false, load the checkbox with a blankmark

c.     If userID of current = session userID, then set box to uncheckable
4.     CLICK SUBMIT BUTTON

             5.     INSERT INTO
a)The text that is in the Capital are the functions that user will perform. 

      b)" * " implies all
      c)The text that is underlined is related to the Database.

We followed these notations in order to avoid confusion to the team members and also the project partner.