Lab - week 14

In this lab we had to complete the presentation slides because the finals week was coming up.
Vashisht, myself and John were busy preparing the slides. Jason and rest of the team members were busy coding.   I was preparing the ER models of the database, it took me considerable time because I had to collect the information and put it together. For more information about the ER diagrams visit Twitter- WISE. I did the ER diagrams for the User, Admin and the Events table of the database. John was speaking to Lorenzo about making the slides more effective and he made necessary corrections to the slides that were required.
We were pretty much ready with the presentation on this day. Every one has been assigned what they will be telling for the presentation on final lab. W have decided to meet on the next Tuesday.

Lab - week 13

As usual we met in the same room in Arms.  The lab started by giving the updates of each team what they have done in the past week. As usual John told about the progress in code that we have made in the past one week.  In this lab we have concentrated more on coding again. The major part of our project was coding. We have divided into small teams and started working on pieces of code that we stopped in the last week. Myself and John , we have decided to do the Admin section.
There are many sections in the Admin part such as:
1)Create Event
2)Delete Event
3)Update User
4)Delete User
5)Read User
6)Update Event

We wrote the code for almost all the parts of the Admin. Myself and John decided to meet this coming Saturday and finish the rest of the Admin section. So we met the next Saturday in Owen hall around 6:00pm. We have worked till 7:30 pm and we managed to complete the major part of the Admin section.
So the meeting that we had on Saturday was very productive and we manged to save some time in the team meetings because of that meeting. Thats all for the lab and the meeting.

Team Meeting - Week 14

This meeting was supposed to be the last meeting of this semester. The basic intention of this meeting was to make sure that there were no bugs in the code that we are going to deliver(actually we are not delivering the project this semester) and also make sure that all our slides are correct without any errors.

I think it was the plan of John to give a demo presentation in the lab so that we will have no problem in giving the presentation on the final day. So it started with Vashisht giving the Introduction and continuing with the slides thereafter. John, Jay and myself joined later. We had to make some fixes to our slides and also to some part of code. There were some problems with the forgetpassword and some other class. We fixed it. Zack and John were working on the code to fix some bugs. I was working on the Use cases and trying to make necessary changes for the slides that we have to present on the final lab.
I gave the presentation on the use cases  of Users and Admin and explained about some other slides as well. I also spoke about the Time line. I think this is s great idea because it is a very good practice for the final presentation.
Finally Jason gave the demo of what we have done.  As usual we have updated on twitter(slides).
For more information visit Twitter-WISE

Team Meeting - Week 13

This team meeting was as usual in Arms EPICS lab. All the members of the team have gathered by 3:30 pm. In this meeting we have coded and we were basically trying to fix some bugs in the code.

I forgot to bring my laptop today to the team meeting , so I had to use John's laptop. Myself and John were working on how to get the Edit and Delete buttons in the correct place we wanted. We also had the problem of how to use the SQL database variables into the C# language. We had to search a lot on the internet to fix the problem . However we have figured a way how to do that. Apart from that we had some difficulties in the codes getting updated on all the machines. So Jason had to go to every laptop and make the necessary changes that have to be made.

Major part of the team meeting was spent in searching for the things that we wanted. So , this is it for this team meeting. 

Team meeting-week 12

First of all I have to say one thing about this meeting. This was as usual held in EPICS lab, but we had lot of fun today. John was making all weird kind of sounds and there were some other things.  Basically what we did today was also coding. Vashisht had some important work to do , so he went after few minutes the meeting has begun. Jason showed us again some interesting code which he has worked in the past week. The code will basically block users and other anonymous customers  access things like create Event and stuff like that. Only admin will be able to do all this kind of things. I have learnt a new way of how to block some users access to certain pages in the website. Its called site manager. We enable the site manger in the web.config file and then we write a separate code for which users to block. We can block specified user to view and do changes with certain pages.  Jay almost finished the  "forgot password ". John and myself were working on " create Event ". We wrote for the create Event and we managed to change some of the database tables.
John and myself have schedules a meeting on Saturday to complete the code related to "Admin".
I learnt a new thing today about how to block some of the users to certain pages. I have also made some changes to the master page(some code for this as well).
So we have pretty much written the code all the meeting and finding new ways to do some interesting things for the site.

Team Meeting- Week 11

I was unable to attend this meeting because I was sick again for the second time in Purdue since my first semester. But I tried to get the gist of what my team members did that day. As far as my knowledge is concerned they have did the coding for the various procedures. Now I don't know what exactly they have discussed but they have come up with some references where you can get information about how to code for all the important procedures.  I can't give much information about this meeting since I didn't attend.

Team meeting- Week 10

As usual we met in the Neil Armstrong EPICS lab a around 3:30pm. Most part of the meeting we did coding for the site keeping in ind of the big picture that we have to accomplish. Jason told us a few interesting things that he accomplished. We discussed how the master page should look for people. We had some issued with it like, how should it look for a registered user and for some anonymous person.  We discussed how the master page should look like. We also spoke about what attributes should be considered for the primary key.
We came across one interesting problem and we a good fix for the problem.  The problem being what if there is only one user but they have many accounts under the user. I mean there is only one user account for the whole family but there are different user for all the members of the family. What if one of the family member changes his/her address, then there would be a problem because we will not be able to update the person who has changed. So we came up with a fix that makes our code very much flexible and also coder-friendly. We have a separate table  for the Account of these types. So if we implement it this way, if we just change the address in one particular table it automatically changes in other tables in the database as well. So it makes our platform code much more flexible to use and also to be used.  This involved a lot of team work, I mean we had to collect the views of all the other team members and then sort them to what we wanted. Even I have contributed a considerable amount of information in making this decision.
We have pretty much discussed some similar issues for the later part of the meeting.
That's pretty much it what we did this day.

Team Meeting -week 9

We managed to meet on time for today's meeting.  We were trying to complete the procedures for our database. If we complete the procedures part ,it would be very easy to code for us because we described briefly what we are gonna do for each thing.
Example for Log In..here is what we wrote..
Log in (from Home screen):
1.    USER ENTERED EMAIL & PASSWORD
2.    Accept from user entries
3.    Encrypt password
4.    Select * from User where form_email = db_email and form_password = db_password
5.    Check if match
       a.    (yes) Set Session Variables
       b.    (no) Send to log in

As usual we update what we are upto on our twitter page. You can find all our updates since beginning on http://twitter.com/epicswise.
 I have personally written procedures for some of the following
Attend Event, Create Event and some of the others. Here is what I have written for some of the events.

Attend Event:
1.    After Read Event 
2.    USER CLICKS ATTEND EVENT
3.    Go to button action with eventID
4.    UPDATE Signed Up WHERE eventID = eventID and accountID= accountID
5.    Refresh Read Event


Create Event:
1.    ADMIN CLICKS CREATE EVENT
2.    Load form
3.    ADMIN FILLS FORM
4.    INSERT * INTO Events
5.    Refresh Read Event

So I have pretty much worked on getting up the procedures correct. That's what we all did the whole meeting.

Weel 11- LAb

This lab was oriented more towards task completion oriented. We have completed most of the tasks that we were assigned to do. We asked if Professor Gafoor wanted to see what we have done on the past week. He told he would like to see what we did. John and rest of the team tried to explain to Prof.Gafoor what each entity meant and howis each entity related to other. We showed him our procedures as well. I think he was pretty much convinced with the work we did.
  Myself and John began coding for the Website. We have divided the work amongst ourselves so that each person will get the equal exposure and equal work and experience.
I worked on getting the tables in the correct format we wanted. It took me pretty much the whole lab. By the end I got it in the desired format.

Week 10 Lab

Today we did some interesting stuff in the lab. As usual every team told what progress they have made. John form our team has updated the information to the whole class. We later were divided amongst out teams. We have assigned some jobs for ourselves to code. John and myself decided to code for the master page.  The way how the page looks and some other similar stuff. We were working mainly on the database. Xing and Vashisht decided to code for the "forgot password." I mean what exactly should happen when you click the forgot password button. Jay and Jason were working on the login page.

I personally studied some information about the SQL database as I am new to it. I have also watched some videos where I can get some quality information of how stuff is done in SQL. I have stared using the windows laptop that EPICS have given me because it is very easy for me to use a window system than a MAC for the things that I do in EPICS. Earlier, I used to have Windows on my Mac, but I started facing some problems with that,so I switched to Windows for EPICS.
I have also downloaded the Vertrigo server  to use phomyadmin. I think most of you know what it is but just in case you don't know,it is an open source tool written in PHP intended to handle the administration of MySQL over the World Wide Web. It can perform various tasks such as creating, modifying or deleting databases, tables, fields or rows; executing SQL statements; or managing users and permissions.
 One can view how their tables will look in the database. It is very helpful because you can first test your changes on this site and then if the result is what you wanted you can implement them on your database directly. If you feel that you didn't get the desired result you might try doing different things that will get your desired result and then implement on your database. By following this way you can avoid mistakes on your original site. You will not mess up with your database. For more information about phpmyadmin refer to http://www.phpmyadmin.net/home_page/index.php

We have completed partially the task that we were assigned. We did some coding for the master page.

Areas where I have to improve

William has mentioned some key points where I have to improve. I would like to list them out, so that it will be evident that I am trying to work on the areas where I am weak.
1) He told that I am probably spending little time on looking at the big picture, which will help me know where the things will fit in the big picture.
Looking at the big picture is always important, as you will know at which level you are in the particular project.
2)He has also mentioned that I am giving less reflections for my work.
Reflections have to be  very clear because it is a very clear picture of what work we are doing outside the lab. I will try to improve on that.