After meeting with Dr. Winfield, Jason and Moon proceeded to develop a high-level system design for Twine. Essentially this is a brief overview of the guts, or inner workings, of the system that can be approached broadly and practically with sufficient time and resources. Shown below is the diagram generated from our meeting:
Meeting minutes are given below.
Jason and Moon’s “Magic” Meeting – February 10, 2009 @ 3:30pm
Purpose of this meeting is to discuss exactly how the system is going to make useful information out of the tweets we get from employees.
-
From the meeting with Dr. Winfield, we decided that there should be an anonymity option when submitting a tweet – a check box perhaps for anonymous or not.
-
Identified three “models” in OOP lingo (tables in a DB)
-
Tweets
-
Attributes:
-
Score
-
Computer by:
-
Submission addtribute (positive, negative)
-
Parsed Text
-
Throw out common of unbeneficial words, such as and, or, but, it, and, etc..
-
Word Proximity and Pairing
-
Word Frequency
-
Punctuation
-
Correct misspelled words or make a guess as to what they meant
-
-
-
-
Content Analysis
-
Parsed Text
-
Throw out common of unbeneficial words, such as and, or, but, it, and, etc..
-
Word Proximity and Pairing
-
Correct misspelled words or make a guess as to what they meant
-
Determine verbs, nouns, proper names
- Assigned a relevancy score to an issue. Can be part of more than one issue.
-
-
-
-
-
Issues
-
Attributes
-
Total tweet score
-
Summation of both positive and negative tweet scores
-
-
Positive tweet score
-
Summation of positives
-
-
Negative tweet scores
-
Summation of negatives
-
-
Controversial score
-
Based on the variation among the scores… standard deviation
-
-
-
-
User
-
Contentment Score
-
Summation of the user’s tweet scores
-
-
-
-
Issues we need to address
-
People post single word tweets
-
“Crap”, “Wahoo”
-
-
How to handle unintentionally or intentionally high value tweets
-
“I HATE MY FREEKING JOB!!!!###$#@%$#”
-
-
