Acting

Strategizing

Reviewing

- Viewing personal performance statistics

- Viewing team performance statistics

- Finding out details of upcoming match up

- Learning about this week's topic (e.g., oil industry)

- Learning about strategies for scoring points this week

u18_start u18_end u18_line
u19_start u19_end u19_line
u20_start u20_end u20_line

- Reading reports and expert commentary, speculating

  about other team's strengths and likely moves

u25_start u25_end u25_line
u26_start u26_end u26_line

- I need to know what's going on in order

  successfully to compete.

- I need logistical information in order to make

  decisions about my time.

- Organizational

- Curious

- Underinformed

- Bored, seeking distraction/entertainment

- I want to know how I'm doing and see my

  progress/status in the league.

- Competitive

Log in/out

u47_start u47_end u47_line

review

Dashboard

u56_start u56_end u56_line

Schedule

Stats

Issue Edu

- I need to know what my options are for gaining points

  this week.

- I need to know what actions my opponent is likely to

  take, so I can determine how to defeat them.

- I need information that can help me make predictions.

- Thoughtful

- Interested

- I'm bored and want to be entertained/distracted.

u79_start u79_end u79_line

News

strategize

THINKING

FEELING

DOING

Stats

Reports

Commentary

Options

map of system features

anticipated user attitudes and behaviors

u114_start u114_end u114_line

act

Donate

Share

Vote

Petition

Protest

Write

Volunteer

Document

Actions related to these features are actually executed within other systems or in the physical world.

- I want to participate in this competition.

- I hope my actions are better than the other team's.

- Competitive

- Motivated

- Executing one of the actions available via the dashboard

  or described by it (voting, signing a petition, writing to

  a senator, sharing information on social media, protesting,

  volunteering, donating money, documenting experiences)

System Requirement: Interaction with Pre-Loaded Dataset

X

Schedule

u176_start u176_end u176_line

Schedule information will be pulled from a pre-loaded dataset of dates, times, and match-ups.

System Requirement(s): Interaction with, and periodically updates of, a stats database

u185_start u185_end u185_line

- Statistics functionality will require interaction with a database of statistics related to individual and team performance.

- Statistics to be collected and saved are TBD.

- Statistics functionality will also require  GUI decisions in terms of data display and interactivity: Graphs, Charts, Etc.

- Stats database will need to be updated periodically as individual performance and team performance changes

Stats

X

System Requirement(s): Curation, organization, and display of relevant news

u198_start u198_end u198_line

- News functionality will require either (a) some automated, algorithmic mechanism by which to collect and organize relevant news reported

elsewhere on the web, or (b) a similar, manual process conducted by an admin-level user

News

X

System Requirement(s): Curation, organization, and display of issue education

u213_start u213_end u213_line

- Issue education functionality will require the manual writing and publishing of issue education content on the part of an administrative user.

  If this information is collected and created prior to the start of the "season," then it could be pre-loaded in a database and displayed automatically

  at the relevant moment. However, it is more likely that this content would need to be written and published weekly in anticipation of each match-up.

Issue Edu

X

System Requirement(s): Curation of opportunities and "portals" or links to external spaces

u228_start u228_end u228_line

- Donation functionality will require manual discovery of donation opportunities related to a given issue.

- Any donations that can be made electronically will be handled outside the system, but links to external systems will be provided.

- The system will require a mechanism for tracking, recording, and allotting points for donations made externally.

Donate

X

System Requirement(s): Social media sharing functionality

u243_start u243_end u243_line

- Social media sharing functionality will allow users to share information via Facebook, Twitter, Instagram (possibly others TBD), in order to gain points.

- Users should also be able to share, via social media, an "announcement" of the actions they have taken in the league (similar to Amazon's

  "I just purchased…" functionality).

Share

X

System Requirement(s): Document external voting in the system

u258_start u258_end u258_line

- Actual voting would need to happen out in the physical world, rather than through the system.

- The system would need to be able to record (and perhaps validate?) that someone had indeed voted, in order to allocate points

- Ideally, since this is a speculative scenario, perhaps we could imagine that voting does indeed happen electronically...

X

Vote

System Requirement(s): Curate, organize, and link to external online petitions

u273_start u273_end u273_line

- Petition functionality will require either (a) an algorithm that identifies and aggregates links to relevant online petitions, or

  (b) a user who manually accomplishes the same thing.

- Petitions that are signed electronically will need to communicate back to the system to award points for petition actions

- Petitions that are signed in the physical world will need to be communicted back to the system somehow?

X

Petition

System Requirement(s): Document external protesting in the system

u288_start u288_end u288_line

- Actual protesting would need to happen out in the physical world, rather than through the system.

- The system would need to be able to record (and perhaps validate?) that someone had indeed protested, in order to allocate points

X

Protest