Topics Discussed:


We started by taking a look at the technology and discussing where it stands and a means of testing it.  We then broke up into 4 groups to discuss the following subjects:


• Chanakya and Khanjan attempted to get FrontlineSMS working with Clickatell for a faster outbound messaging system.
• Kaylyn updated the website so that it was up-to-date
• Scott laid out what pieces of the technology needs to be tested, and developed a plan for doing so
• The marketing and business team discussed the various stories for each insertion scenario.

The Current Plan for Testing

Things to Test:
1)Sustainability (Does it crash after a certain amount of time?) OS, Frontline, Phone, etc.
2)Keywords (are they consistently stripped by Frontline?)
3)Database Security (if someone attempts to write to a rating as someone else is reading what happens?)
4)Reliability (How often, if ever, does Frontline drop messages?)
5)PHP(What happens if a keyword is correct, but message content incorrect?)
6)Efficiency (Speed...Hopefully find away to test Clickatell)
7)Learning the system (how fast can someone figure out the system. Simplicity?)

How to Test:
i. Set up the WishVast system on a computer to be used only for WishVast
ii. Distribute a list of message formats to our group.
iii. Periodically test these requests to WishVast over a few days
iv. Items 3 and 5 will be tested by Kaylyn and I on our own.


Testing number 7
i. Get friends the message formats
ii.  Ask them to perform certain tasks (join group, send message, rate, get rating)

After working on our own we reconvened and discussed and reviewed all that we had come up with in our groups.  We then discussed what we would have for next week:


• The technology team would have the system in place ready for testing.
• The business and marketing teams will have scripts for their youtube videos started and being reviewed.


We then called the meeting for the night.

Topics addressed:


Idea Pitch update:
Adam provided an update on the results of the IdeaPitch competition and the feedback that was received. Chris and Chanakya also shared their thoughts and feedback from the competition.


Technology Updates:
The current status of the technology was discussed and the plan moving ahead was formulated. Scott mentioned the possibility of combining some of the old Java code with some new code to develop a non internet based solution as a back-up. On the internet-dependant aspect, Chanakya will obtain the exact method of buying credit for Frontline/Clickatell and report to Khanjan to buy the credit to conduct testing.


Scenario Development:
Not much progress was reported on the development of the slides for the 3 final scenarios. It was decided that these slides will be submitted to Khanjan latest by Wednesday morning, after the involved members, primarily being, Adam, Chris, Christian and Mike meet and work on it together.


YouTube Video Teams:
A small amount of time was spent in setting the teams for the ENGR 497 YouTube video presentations.


UGE Poster Challenge:
A very significant amount of time was spent on looking at the version of the poster developed by Christian and Mike. Discussion was held on the same, changes suggested and an improvised plan of action was set in place for a new poster. The poster will be presented on Wednesday April 7 @ 9:30 AM in the HUB. Christian and Mike will be presenting the poster.


Website:
A large amount of time was spent on discussing the several aspects of the website, since not much development was made since the previous meeting, according to Khanjan. A new structure and menu bar was discussed and decided upon by the entire class in agreement. While Kaylyn will champion the development of the website, the write-ups were split between the entire team so as to minimize the load on any one individual. It was decided that a fully functional website will be set up before the next class on April 7. 


Business Team update:
A detailed update was provided by the business team from their latest class presentation slides. A lot of the assumptions made regardingwere discussed and improvised upon, for hte business team to develop further. A specific task assigned to them was the development of a model for Khanjan, within which new numbers could be plugged in.