Proposal for aDigital Media Capstone Project

In Partial Fulfillment of the RequirementsFor a Master of Liberal Arts Degree

Harvard UniversityExtension School

June 2016

Courtney Majocha14 Belmont St.781.346.8039

Woburn, MA, 01801cdmajocha@gmail.com

Proposed Start Date: July 27, 2016Anticipated Date of Graduation: May 26, 2016

1. Tentative Project TitleThe Official Website of the Pretend Football League: A WordPress Application

2. AbstractI currently participate in a Fantasy Football league that requires a complex system of record keeping with a heavily manual component. With more than six years worth of data, and much more to come, this is not only time-consuming, but also leads to the potential for human error and a limited sharing of resources across league members. I would like to solve for both the data management and data access matters that currently plague the league.

The aim of this project is to create a website for my fantasy football league to supplement our league site, and to manage the intricacies and historical data pertinent to the keeper format of our league.

Although the weekly head-to-head game play and scoring can be handled through an external provider, there are gaps that are not covered. Those gaps are to be expected when you attempt to customize a free model to create a specialized prototype as our league has done.

For the past six years, we have managed these extra customizations manually. As the years have gone by, however, that system has proven more and more unwieldy and places a heavy burden on our commissioner.

I have identified ways that I could help automate things so that the entire league would have access to key information without having to ask the commission to delve into excel spreadsheets. The following proposal will outline the ways in which I will use a WordPress CMS to create a supplemental website for my league that will allow for better sharing of information, more accurate record keeping, and a better overall user experience.

3. Capstone Project Description

3a. Background

The Pretend Football League, or PFL, was formed six years ago as a way for a group of friends and family to play in fantasy football league together. As a means of trying to ensure forward thinking and long-term participation, it was determined that this would be a keeper league.

2

In such a format, each team owner is allowed to keep three players on their roster from season to season. There are certain caveats to that however, that really complicate the record keeping.

1. Players drafted in the first round can not be kept2. Players can only be kept for two consecutive seasons (even if there are

two different owners), before they must be thrown back into the draft3. Each team owner must surrender the draft pick that corresponds to the

player they are keeping. So, if you draft Tom Brady in the second round in 2015 and you want to keep him in 2016, then you will lose your 2nd round pick in the 2016 draft.

4. Finally, the eighth round in the last round in which picks can be surrendered. So if you are keeping three players who were eighth round picks in 2015, then you will have to surrender your 6th, 7th, and 8th pick in 2016.

Needless to say this can get complicated. While league members typically know the situation of players on their own roster, they’re usually not as sure about players on other teams. It can make trades pretty difficult. In the off season, you might want to trade your second round pick for a potential keeper, but you have to know that the player you’re getting in return isn’t a second round pick.

What this normally results in is countless emails and texts to the commissioner to look up what round players were drafted in two years ago, or whether a certain player is eligible to be kept. It’s exhausting and not at all efficient.

As trades are made, players are kept and seasons change, there are so many variables at play. The draft board is constantly being updated throughout the off-season, rosters are changing, etc… and all of this is done manually.

I’m confident that I can create a more centralized repository of data in a website that all league members would be able to access to review the information for themselves. There would be an initial output of effort to build out the historical data, but once that initial migration was completed it would be much easier from season to season to update and maintain.

I’ve gleaned some key takeaways from the courses I’ve taken in the Harvard Extension ALM Program that I know could drastically improve upon this situation. While I’m not the league commissioner, I do understand his burden,

3

and I am the league member with the technical skills most able to accept this challenge. The league is eager to have a better system in place.

I think it would not only make for a better user experience for the league, but I feel like it would better level the playing if there was more transparency. I think some members find the system too complex and eschew trades because of that.

3b. Work I plan to do This capstone project will involve the building and launching of a new supplemental PLF Website on a WordPress CMS.

I will design and conceptualize a new site for the league, and build it on the WordPresss CMS platform.

First I will consult with the league commissioner and gather feedback from other league members to get a firm understanding of what features/ information that they would want integrated into this site

Next I will create a wireframe and try to ensure the usability of the site. For this, I will bring in league members to make sure that they understand how the site is intended to function and to see if they might identify anything that is potentially confusing or if there are any items that have not been addressed

Once I have a working model, I will then stand up the site on a host platform and work to build out the functionality that I need in the actual environment and which plugins I would like to integrate into the site.

Since this site will need to use tabular data, I want to make sure that I have easily manipulated tables that present information in a clear manner.

I will also need a communication tool integrated into the site. Trade negotiations are currently handled through a combination of texts and emails, and it’s often frustrating to negotiate multi-team deals. I would design this site to solve for that issue.

I would like to integrate an NFL API into the site so that members could have the ability to look up player data directly from this site.

4

I will also need to adjust the WordPress permissions so that I can serve up unique dynamic data to league members.

Finally, I will develop a custom fully responsive theme and then create a child version of that theme so that I can alter the functions.php file without compromising the out of the box functions.php inherent in WordPress core.

Throughout the design and development process, I will be consulting with members of the league to make sure that the end product is one that will be universally adopted and utilized amongst the members.

3c. Technology Choices

I will use Siteground for my web hosting. I’ve utilized their service in the past and found their interface easy to use. My site traffic will be small, so I don’t anticipate needing anything more than the most basic plan.

I will employ the WordPress CMS as the framework for this site, and I will develop a custom fully responsive theme to apply to the site. My plan would be to utilize an existing grid system like bootstrap or foundation in the development of the theme.

I believe WordPress is a good solution for this site, because it gives me the robust back end features that I need to customize and build the site to perform the necessary functions. Once built, however, it boasts an intuitive user interface that I could easily train other league members to manage. Since one of the main impetuses for creating this site is to ease the burden of data management placed on a single member, the idea of a site that many members can update and edit solves for that in an appealing way.

I plan to integrate an NFL API into the site so that league members could research players directly from this site. This site offers reasonably priced API options. I would opt for the premium membership and parse out the information that I needed. I would use this in tandem with a WordPress API plugin such as Custom Database Tables.

I would like to integrate a messaging system like Slack into the site to aid in the league communication, especially concerning trades and multi-party deals. I think that plugin such as Slack sync would make sense and would suit my needs.

5

My site will only be for a select group of users. Since I will be collecting some PII in the form of an email address, I will ensure that I have the proper security in place. I will also make sure that both WordPress core, as well as my plugins, is updated regularly to ensure that I am update to date with their security measures.

I’ve gained a great deal of experience through both my courses that I’ve taken at Harvard Extension as well as in my professional career.

The two UX classes that I’ve taken (ISMT S-170 Information Systems Design and CSCI E-34 User Experience Engineering) have impressed upon me the need for careful planning and consultation prior to launching a final product. Truly understanding the needs of the user, and understanding that you are developing for an audience that is not necessarily you, are key takeaways from my courses at the Extension School. While I already have a good grasp of my personas and the use cases for my site, I will certainly consult with end users on design and information architecture to make sure this site is easy and fun to use. Without that, I risk limited adoption.

The web design courses that I’ve taken, particularly DGMD E-20 Developing Interactive Media, DGMD E-25 Web Content Management Systems, CSCI E-15 Dynamic Web Applications, and DGMD E-27 Modern, Mobile Front-End Design II, have given me the tools to construct well-designed websites with clean code that meet accessibility and industry standards across the web.

From these courses, I’ve deepened both my front-end skills and taken my first steps into programming.

Professionally, I’ve been working on the web for much of my career, but as my time at Harvard Extension has progressed, so too have my capabilities and responsibilities. In my current career, I serve as an admin for a large WordPress site, and I also stand up smaller sites regularly.

I would like to utilize this project to delve deeper into WordPress and to integrate some of the programming skills that I’ve acquired. I would like to become more familiar with manipulating the PHP files rather than just the CSS and HTML. Strengthening these skills would be a great benefit to my career, and the insight I’d gain working on this project would have definite real-work applications for me.

6

4. Prior Work

Our league has existed this long by using ESPN.com’s free fantasy football application in conjunction with a number of documents and spreadsheets that are manually compiled and managed.

We currently use ESPN.com to handle the bulk of our game play. ESPN’s model allows us to create divisions and set up a full-season schedule. ESPN then automates the weekly match ups so that all of the scoring can be handled through their platform.

Their system does allow for some customization. We were able to select which sort of scoring model we wanted to use for our league, and determine how many points certain aspect of scoring would be worth.

ESPN allows us to change divisions if need be, and it handles the storage of our rosters. We can trade players and ESPN will allow us to move players from roster to roster.

ESPN also has a system in place to handle the waiver wire. Players can be dropped from rosters and league members can bid on available free agents to fill those empty roster spots. This is another area where we are afforded some customization. We can select which days the waiver wire will be open, how bidding for new players works, and who has priority in the event of a tie.

ESPN clearly has the expertise for all of the above-mentioned functions, so I see no need to try to take on these tasks with my site. We have been satisfied with how that aspect of our league has gone, and I would like to build upon that base.

My site will serve as a supplement to the ESPN one, rather than a full replacement. There are areas where ESPN’s model offers no assistance, and those are where we need to devise a more creative solution.

ESPN does allow us to upload league guidelines, which we have done via a Microsoft Word document. This is a very robust document with a great deal of minutia. It’s nice to have and there are definitely times throughout the season where league members need to refer to it. It would certainly be better however if it was presented in a more searchable format with a better UI than a long word doc affords.

7

Integrating a table of contents and improving upon the organization of the document would go a long way toward usability. There are numerous instances on the web of organizations with complex rules and regulations. The best ones make it easy for the user to parse out exactly the information they are seeking without too much clicking or effort.

The Little League Association offers headers and accordions to make complex

regulations easy to digest.

Harvard’s Office of Public Affairs uses filters and a clear structure to help users find the specific scenario pertinent to their inquiries.

8

In addition to the rules/guidelines, the draft poses a challenge for us each season.

While ESPN does let us input draft results and store rosters each season, it does not provide us with the infrastructure for an all-inclusive draft headquarters. We surrender draft picks for keepers and trade draft picks throughout the offseason, something ESPN has been unable to accommodate in the automated drafts they offer through their site. We need to expand off of their base to build a platform that enables our varied machinations.

One challenging issue that was posed to me about the site I intend to create was how I would be handling tabular data, like a draft board, on mobile. If at all possible, I will seek alternative designs to the tabular structure. With that being said, however, there are instances like the draft board where this will be difficult if not impossible.

The US Government DigitalGov website offers a variety of measures to support this endeavor (DigitalGov). Some of their solutions, like removing the tables on mobile or converting the data to a pie chart, will not work for my site.

They do, however, have some solutions that could be applicable such as removing certain columns or creating scrolling tables with a fixed leading column. I will fold this dilemma into my user testing to try to come up with the solution that works best for the members in my league.

9

In terms of real-world solutions WordPress has plugins that accommodate responsiveness such Ultimate Tables, which is updated frequently and is compatible with the latest version of WordPress. I could also opt for a more customized jquery solution that I could code myself. It will all depend on what direction that I decide to go in.

I have anecdotal evidence that suggests league members are primarily accessing information from desktops/laptops rather than via mobile devices, so I will design for desktop first and then make the site responsive for mobile – that goes for all of the elements, not just the tabular data.

Since I know that the draft board will be a highly trafficked tabular page, especially in the off-season, finding the best solution for this page will be critical. As teams look to trade draft picks and determine keeper values, an updated board that everyone can view is imperative.

One solution is to create a customize Google spreadsheet and then embed that into a WordPress page. It’s simple to maintain, but visually lacking. There are more customized options available, and that might be a more enticing direction.

What’s appealing about building this in WordPress via a plugin such as Sports Rankings and Lists or the aforementioned Ultimate Tables plugin is that league members would be able to take advantage of sorting and filtering in a more intuitive way. And on the back end, it offers a drag and drop interface which would allow the commissioner to easily manipulate the draft board as trades are made and picks change hands.

4.1 Requirements

In order for this site to perform as intended, and to benefit the members of this league, it will need to perform the following functions.

1. DRAFT BOARD PAGE/DRAFT BOARD MANAGEMENTThe site will need to display an up-to-date draft board at all times. This will likely be presented in a tabular format. There are 10 teams in the league, and each will make a total of 12 picks, which amounts to 120 total picks. The draft order is determined by the prior season’s standings so it is different every year. The league members will need to be able to see the aggregate of all picks, and they should also be able to filter to see just their own picks, or just another player’s picks. This will keep

10

them advised of their own draft, and aid them in trading for another player’s draft picks.

The key to this page will be creating an interface that is easy to use on the back end as well as the front end. I want teams to be able to quickly access the information that they need, and I want the admins to be able to update the back end easily to account for the frequent changes.

Sample Draft Board

2. PLAYER LOOKUP TABLEThe site will need to contain a database of every player that has been drafted in this league, their keeper status, and what round they were drafted in. This table is critical due to the keeper nature of our league. As I outlined earlier, players can only be kept for two consecutive seasons. If you do keep a player, you must surrender your draft pick corresponding to the round that player was drafted in the prior season. We have all of this data available, but for now it is just pieced together from various excel documents. I want to create a database of all of these players. League members can look up a player that they might be interested in keeping and they can find out if that player is eligible to be kept, what round draft pick they would have to surrender, and what

11

current roster that player is on.

If a player is “not found” in the table, that means that they were never drafted, have never been kept, and they are not on anyone’s current roster. Again, it will be imperative that this table be as easy to use on the back end as it is on the front end. Below you will find a graphic visualization for how I envision this table might function:

Sample Lookup Table

I want to have multiple sortable columns within this table so that league members will be able to sort by position, current team owner, and keeper eligibility. I will be consulting with league members during the user testing exercises to gauge how they would interact with such a table, what sort of searches they would be trying to execute and what basic requirements it would need to have to meet their needs.

I have anticipated some of the basic queries that I think they will be running, but I will get their feedback on this table very early in the process so that I have type to work on the development in response to their feedback.

3. CHAT/COMMUNICATION TOOLThe site will have some sort of a chat feature/discussion forum that will aid in league-wide communication. Discussing trades over text/email can be difficult, and it’s especially hard to loop in more than two players. Likewise, there are times when the league commission wants to

12

communicate a message to all members, and other times when he has more targeted notes for teams.

Another issue that has arisen is that the fact that not everyone knows which channel is going to be the most effective means to communicate with another player. You could be waiting on an email response from someone and not realize that they don’t check their emails at night, or that they prefer to text.

I’d like to take the guesswork out and centralize the communication on this site. From my initial research setting up a slack channel for the league and then integrating the slack plugin into the site seems to be a good solution. League members would be able to direct message one another, or set up private groups to discuss trades. The commission would also have an easy way to reach out to the entire league and vice versa.

To be clear this would only be for communication purposes. The actual mechanism of moving players from one roster to another via a trade would still be handled by ESPN, but this would aid in the negotiation and talks.

13

4. INTUITIVE LEAGUE RULES SECTION This site will host a repository of the league rules in a format that is easy to access and intuitive for players to find the specific rule that they are looking for.

14

Usually when rule questions come into play, it’s because some random occurrence has taken place, and no one is quite sure of the repercussions.

We have rules that govern almost any minutia that arise, but they’re currently hosted in a dense word document.

I want to keep all of the information in tact but present it in a way that’s searchable, so that league members can find the information that they need in a more intuitive way.

It can be fleshed out quite a bit and broken down into sections with related content. Some rules for instance pertain to in-game play like what happens when the score is tied in the playoffs, while others center on roster size, or player transactions. I’d like to create some larger buckets and streamline the rules into these buckets so that the league members will be able to follow a clear path to their destination. A basic example of this structure is outlined below with top-level buckets and a few examples of detail pages beneath.

Scoring Rules o Playoff Ties

PFL Violations and Penalties o Not Fielding a Full Teamo Trade Fraud

Roster Requirementso Understanding the Flex Position

Draft Guidelineso How is the Draft Order Determined

Waiver Wire Transactions

4. NFL PLAYER/LEAGUE DATAI would like to incorporate an NFL roster API into my site so that league members could look up stats on certain players and obtain other information directly from this site.

This is really intended to streamline the user experience. This is information that they can obtain elsewhere, but I don’t want them

15

having to get certain things on one site, and then leave for another site to do other tasks. I think that makes the adoption of this site less likely.

The API that I would be working with would allow for some queries that make quite a bit a sense as far as supporting the intended purpose of this site. I would like for league members to be able to look up NFL bye weeks here, as that’s helpful when making roster decisions. I’d also like to offer access to draft projections, as that makes sense in tandem with the draft board. Finally, there are other queries that could add use throughout the season, such as access to weather reports, which can help you decide which players you should start or sit on any given week.

5. HISTORICAL LEAGUE DATA SECTIONI’d like to collect all of the past league data and create a historical sections that documents past winners, final season standings, season point totals.

There are instances where people like to look back to see if they’re close to a record for wins, or if they’ve scored more points that any other team. It’s really just for personal pride, but still it does come up each season. Again, this is data we have, but as of right now it’s not easily accessible.

This is more of a nice-to-have piece, that’s not critical to the functionality of the website, which is why I’ve prioritized it last. Time-permitting, I would like to include it, but it’s certainly something that I would sacrifice in order to have the other sections perform optimally.

5. Work Plan

5.1 Assumptions, Risk, and AlternativesI feel that my experience both academically and professionally has given me the skills necessary to undertake this project, but there are always unknown elements.

As a league member, I am making some assumptions about what the functionality should be – a dangerous proposition in terms of UX – know you’re user and your user is not you is a lesson I gained from Harvard Extension. I will be reaching out to other league members to mitigate this risk, but that obviously opens up new ideas and propositions that I might not have considered.

16

While I do have a good deal of experience building websites and working on the front-end design, programming is still a challenge for me. I will do a great deal of research and I will seek out avenues to expand upon my current knowledge base through tutorials, online forums and publications.

If I run into any roadblocks, I might have to adapt the scope of my site, but I hope to be able to troubleshoot issues that arise and still be able to deliver a useful tool for my league.

I will gauge the effectiveness of my project upon the adoption of this site by league members. That’s why the user testing aspect is critical. Since I have direct access to the small pool of users I am developing this technology for, it will be imperative that I get their feedback, so that they will utilize the site moving forward.

5.2 Preliminary Schedule

Below is a tentative outline of the schedule I would like to serve as my guide for this project.

Start Date: 7/27/16 - Items to be completed prior to first class meeting:

1. Sketch out a basic outline for the site on paper and start conceptualizing the layout and site architecture to create a rough wireframe. I will also gather real world examples of functionality I would like to include on my site.

2. Advance User Testing - Interview league members to capture their needs and wants from this site. At this point I will show them the aforementioned outline, along with some of the sample elements to get their feedback. For instance, I will show them the player look up table concept that I have included above to get their thoughts and try to anticipate how they would interact with such an element. 3. Create a shared document via Google Docs and share with all league members. This will function as a place for them to leave feedback on the site as they complete their user testing, and submit requests. Eventually I will transition this document into an evergreen backlog of feature requests and bug reports.

4. Collect all necessary data to be added to the site (spreadsheets of

17

previous drafts, current draft board, league rules document)

5. Discovery phase of the NFL API – Complete the registration process to gain access to the API so that I determine what data can be mined and what is important to integrate into the site. Research tools for integrating the API into the site, and determine which plugins I will need to work with. Create a roadmap for implementation

Items to be completed by 9/12/16

1. Procure Site Hosting from SiteGround

2. Stand up a WordPress Instance on SiteGround and make sure that I am running the most up-to-date version of WordPress and that the site is functioning as intended. 3. Determine the domain name for the site and configure the DNS to make sure that the site is properly configured

4. Research and determine the best security plugin to implement that will help to protect against Brute Force Login Attack, secure the database, and protect the user accounts.

5. From the user feedback gathered from league members, amplify the rough draft of the wireframe and create a more multifaceted model via a wireframe via a tool like balsamiq

Items to be completed by 9/26/16

1. Audit existing league data begin entering the content into WordPress.

2. Finalize the more complex wireframe from Balsamiq (or a similar tool) and share this version with league members to get their feedback so that I can ensure the site is easy to navigate and contains all of the necessary functionality. 3. Determine best way to present the content – discovery into which option might be best for presenting tabular data (research available options and select the best one based up user testing and feedback)

18

4. Start work on the player lookup table. Enter the necessary content to create the database, and being setting up the queries, keeping in mind the feedback from league members in the initial round of user testing.

5. Establish user roles and permissions. Determine which league members will be admins and start creating the documentation for site functionality for admins to use as a point of reference

Website development (start by 10/2/16)1. Finalize the player lookup table and make sure that the queries are working on the front end.

2. Create the draft board page and implement user testing with the previously established admins to make sure the back end interface is easy enough to work with. Update the documentation with instructions for this section.

3. Create the necessary pages for the league rules section, and run user tests on the front end to make sure the information can be accessed in an intuitive way. At this point, I will be sharing the actual draft WordPress pages for this section as opposed to the wireframe that league members have review previously.

4. Add the NFL player search to the appropriate pages, which will be determined during user testing. I will incorporate this using the NFL API and calling upon my research from the discovery phase completed earlier. Once complete, I will run tests to make sure that the search/results are functioning as intended.

Items to be completed by 11/7/16

1. Design and implement a custom theme – the theme will be fully responsive, but designed for desktop first unless user testing discredits my anecdotal presumption that this is the primary device for the majority of the league.

2. Create a custom 404 page that includes an email address to report issues. This will hopefully make it easier for users to report errors. I will also include a contact email in the footer for users to report site feedback, and that email will be forwarded to all of the admins of the site. Finally, I will

19

integrate a feedback component to the communication section that will allow for users to report errors or request additional functionality

3. Set up the chat/communication section either using an embedded Slack channel or an alternate solution and test with another user to make sure that the tool is easy to use and works as intended

4. Implement any additional plugins desired for the basic operation of this site

Items to be completed by 11/21/161. Thorough End-to-End Testing of all the elements and troubleshooting any issues or conflicts.

2. UAT: User Testing of the site. Invite the league members to once again review the site in WordPress now that the design elements are in place to get their final feedback.

3. From the shared Google Doc that was established during preliminary user testing, create an evergreen project backlog to capture any ideas for future iterations or additional functionality that can be completed at a later date

Items to be completed by 12/1/161. Launch site – Confirm that the domain in working, the site is functioning, and that the site is available to all league members.

2. Establish a plan for future maintenance and upkeep and finalize site the documentation.

6. Glossary

Content Management System (CMS): The business dictionary defines Conent Management System as “A software application used to upload, edit, and manage content displayed on a website. A content management system can perform a variety of different tasks for a website including regulating when content is displayed, how many times the content is shown to a specific user, and managing how the content connects or interacts with other elements of the website. This software also enables less technical individuals to manage

20

content on a website easily without having an extensive coding background.” (BusinessDictionary.com)

WordPress: WordPress began as a tool for bloggers to disseminate their content, but it has evolved to become a fully functioning content management system that can be used for enterprise level sites. WordPress is an open source project, which means there are hundreds of people all over the world working on it.

(WordPress.org)

API: An application programming (or program) interface: a set of protocols used by programmers to create applications for a specific operating system or to interface between the different modules of an application. (Dictionary.com)

UAT: “User acceptance testing (UAT) is the last phase of the software testing process. During UAT, actual software users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications. UAT is one of the final and critical software project procedures that must occur before newly developed software is rolled out to the market.UAT is also known as beta testing, application testing or end user testing.” (Techopedia.com)

End-to-End Testing: “End-to-end testing is a methodology used to test whether the flow of an application is performing as designed from start to finish. The purpose of carrying out end-to-end tests is to identify system dependencies and to ensure that the right information is passed between various system components and systems.” (Techopedia.com)

UX: An abbreviation for User Experience. The perception and response of a person toward design elements of software or digital media while interacting with it. (Dictionary.com)

PFL: Pretend Football League. This is the name that we have given to our fantasy football league. This proposal serves as an outline for the new website I will be developing for the league

Keeper League: A fantasy football league in which a specified number of players on a team’s roster can be designated as “keepers” and held onto from season to season.

21

7. References

"Content Management System (CMS)” in Business Dictionary. Source http://www.digitalgov.gov/2014/10/28/trends-on-tuesday-8-ways-to-format-tables-for-responsive-web-design/

Available: http://www.digitalgov.gov, Accessed: June 18, 2016.

"Trends on Tuesday: 8 Ways To Format Tables for Responsive Web Design” in Digital Gov. Source Locations Business Dictionary http://www.businessdictionary.com/definition/content-management-system-CMS.html

Available: http://www.businessdictionary.com, Accessed: June 02, 2016.

"Photographing of and Videotaping in Harvard Buildings and Facilities” in Provost.Harvard.edu. http://provost.harvard.edu/photographing-and-

videotaping-harvard-buildings-and-facilities Available: http://provost.harvard.edu, Accessed: June 2, 2016.

"Updates and Changes To Little League® Rules and Regulations For the 2016 and 2017 Regular and Tournament Season Play” in Little League.org. http://www.littleleague.org/learn/rules/updates-2016-2017-regular-tournament-play.htm

Available: http://www.littleleague.org/, Accessed: June 20, 2016.

“About WordPress” in WordPress.org. Source https://wordpress.org/about/Available: https://wordpress.org, Accessed June 02, 2016

"api," in Dictionary.com Unabridged. Source location: Random House, Inc. http://www.dictionary.com/browse/api. Available: http://www.dictionary.com/. Accessed: June 02, 2016.

"End-to-End Test," in Techopedia.com. Source location: Techopedia.com. https://www.techopedia.com/definition/7035/end-to-end-test Available: https://www.techopedia.com. Accessed: June 02, 2016.

"User Acceptance Testing (UAT)," in Techopedia.com. Source location: Techopedia.com. https://www.techopedia.com/definition/3887/user-acceptance-testing-uat Available: https://www.techopedia.com. Accessed: June 02, 2016.

22

"user experience," in Dictionary.com Unabridged. Source location: Random House, Inc. http://www.dictionary.com/browse/user-experience. Available: http://www.dictionary.com/. Accessed: June 02, 2016.

23