Questions and Topics We Can Help You To Answer:
Paper Instructions:
analyzing several scenarios and determining what technologies would work well together to solve these problems. For each answer, back up your reasoning with why you chose each technology, strategy, etc.
Scenario 1: Logging
In this scenario, you are tasked with creating a logging server for any number of other arbitrary pieces of technologies.
Your logs should have some common fields, but support any number of customizeable fields for an individual log entry. You should be able to effectively query them based on any of these fields.
How would you store your log entries? How would you allow users to submit log entries? How would you allow them to query log entries? How would you allow them to see their log entries? What would be your web server?
Scenario 2: Expense Reports
In this scenario, you are tasked with making an expense reporting web application.
Users should be able to submit expenses, which are always of the same data structure: id, user, isReimbursed, reimbursedBy, submittedOn, paidOn, and amount.
When an expense is reimbursed you will generate a PDF and email it to the user who submitted the expense.
How would you store your expenses? What web server would you choose, and why? How would you handle the emails? How would you handle the PDF generation? How are you going to handle all the templating for the web application?
Scenario 3: A Twitter Streaming Safety Service
In this scenario, you are tasked with creating a service for your local Police Department that keeps track of Tweets within your area and scans for keywords to trigger an investigation.
This application comes with several parts:
An online website to CRUD combinations of keywords to add to your trigger. For example, it would alert when a tweet contains the words (fight or drugs) AND (SmallTown USA HS or SMUHS).
An email alerting system to alert different officers depending on the contents of the Tweet, who tweeted it, etc.
A text alert system to inform officers for critical triggers (triggers that meet a combination that is marked as extremely important to note).
A historical database to view possible incidents (tweets that triggered an alert) and to mark its investigation status.
A historical log of all tweets to retroactively search through.
A streaming, online incident report. This would allow you to see tweets as they are parsed and see their threat level. This updates in real time.
A long term storage of all the media used by any tweets in your area (pictures, snapshots of the URL, etc).
Which Twitter API do you use? How would you build this so its expandable to beyond your local precinct? What would you do to make sure that this system is constantly stable? What would be your web server technology? What databases would you use for triggers? For the historical log of tweets? How would you handle the real time, streaming incident report? How would you handle storing all the media that you have to store as well? What web server technology would you use?
Scenario 4: A Mildly Interesting Mobile Application
In this scenario, you are tasked with creating the web server side for a mobile application where people take pictures of mildly interesting things and upload them. The mobile application allows users to see mildly interesting pictures in their geographical location.
Users must have an account to use this service. Your backend will effectively amount to an API and a storage solution for CRUD users, CRUD 'interesting events', as well as an administrative dashboard for managing content.
How would you handle the geospatial nature of your data? How would you store images, both for long term, cheap storage and for short term, fast retrieval? What would you write your API in? What would be your database?
reference answer:
https://github.com/zijing2/CS554/blob/master/lab8/Huang_Zijing_CS554_A.pdf
https://github.com/bradford-smith94/cs554/blob/master/Lab8/bsmith8_cs554-lab8.tex
https://github.com/rsutariy/CS-554-Web-Programming-2/blob/master/LABs/Lab-8/Sutariya_Ruchika_Lab8.pdf
