SLC Fantasy NBA League
MoSCoW
Could
Should
Must
Won't
Prescribed Criteria
Self Determined Criteria
Target Users
Students
Years 7-12
Both familiar and unfamiliar with NBA
Difference in ideas and goals with the application
Teachers
Many different ages
many different roles as staff
wish to administrate the website
User Experience Requirements
Must be easy to understand and use
must have a similar feel to genuine fantasy sport applications
Stakeholder Requirements
Functional Fantasy sport application
Available/Accessible for any SLC student
Developer Environment
Application interface
Create/Edit custom NBA teams
database editing interface
API interface
Data Interfaces
API
Web Server
API Database
Application Database
Data Requirements
Create custom team with API data
Contain players & their info
API info
Player Info
ID, Name, position, height, weight, team
Team Info
ID, Abbreviation, City, Conference, Division, Name
Game Info
ID, Date, Score, Season, Period, Status, Time, Teams
Data Formats for Exchange
JSON
Text Based
XML
Text based
Javascript object syntax
Data Security Risks
Data Privacy Risks
Assumptions
Constraints
Impacts
Personal
Social
Economical
Privacy concerns, Data use
Social connections established via sense of community
Running site for free costs money(in a real world scenario)
Universal syntax
Hacking of user account
Phishing
Poor Database design
API reliance, if API is false, application is false
Web application, hosted online, easier for servers to go offline
Only works directly with its own API and nothing else.
Inadequate validations can make accounts that dont belong to you easy to access
The Risks of XML used with SOAP
A general lack of security is a danger to user safety online
User has internet access
User can access both application database and API database
User has competency in similar applications