CS471: Web and Mobile Development - Service Clients (100 Points)
Assignment Goals
The goals of this assignment are:- To implement a web service client in node.js
The Assignment
If (and only if) you are using GitHub to submit, you can clone this assignment from GitHub Classroom at https://classroom.github.com/a/Zg7pvINg. Otherwise, you may skip this step!In this assignment, you will choose two REST service endpoints and integrate them together. You may select any two endpoints you want.
Part 1: Service Endpoint Integration
Here are some examples you can choose from (but you don’t have to pick one of these!):
- Google Calendar
- Canvas
- Yahoo! Finance
- Pokemon
- Nexmo SMS Text Messaging
- International Space Station Location
- Spoonacular Recipes
- Open Movie Database
- Text to Speech
- SEPTA
Please advise the instructor of your choices before you begin (this is not intended to restrict you, but just to determine if you need any additional resources to complete the assignment based on the choices you make).
Regardless of the services you choose, you should:
- Connect to one service, download and parse the result
- Use that result to form the input of a request to a second service endpoint, and then process that result accordingly
In your README, please include a paragraph description of your intended audience: who can use your program, and how does it improve their workflow, their life, and/or their community?
Part 2: Presentation
Make a Screencast in which you demonstrate your program, and also review your codebase. Imagine you are explaining how to use these API’s to a new web service developer. Give them a thorough tour! I hope to solicit volunteers to demo their programs to the class!
Submission
In your submission, please include answers to any questions asked on the assignment page in your README file. If you wrote code as part of this assignment, please describe your design, approach, and implementation in your README file as well. Finally, include answers to the following questions:- Describe what you did, how you did it, what challenges you encountered, and how you solved them.
- Please answer any questions found throughout the narrative of this assignment.
- If collaboration with a buddy was permitted, did you work with a buddy on this assignment? If so, who? If not, do you certify that this submission represents your own original work?
- Please identify any and all portions of your submission that were not originally written by you (for example, code originally written by your buddy, or anything taken or adapted from a non-classroom resource). It is always OK to use your textbook and instructor notes; however, you are certifying that any portions not designated as coming from an outside person or source are your own original work.
- Approximately how many hours it took you to finish this assignment (I will not judge you for this at all...I am simply using it to gauge if the assignments are too easy or hard)?
- Your overall impression of the assignment. Did you love it, hate it, or were you neutral? One word answers are fine, but if you have any suggestions for the future let me know.
- Using the grading specifications on this page, discuss briefly the grade you would give yourself and why. Discuss each item in the grading specification.
- Any other concerns that you have. For instance, if you have a bug that you were unable to solve but you made progress, write that here. The more you articulate the problem the more partial credit you will receive (it is fine to leave this blank).
Assignment Rubric
Description | Pre-Emerging (< 50%) | Beginning (50%) | Progressing (85%) | Proficient (100%) |
---|---|---|---|---|
Algorithm Implementation (60%) | The algorithm fails on the test inputs due to major issues, or the program fails to compile and/or run | The algorithm fails on the test inputs due to one or more minor issues | The algorithm is implemented to solve the problem correctly according to given test inputs, but would fail if executed in a general case due to a minor issue or omission in the algorithm design or implementation | A reasonable algorithm is implemented to solve the problem which correctly solves the problem according to the given test inputs, and would be reasonably expected to solve the problem in the general case |
Code Quality and Documentation (30%) | Code commenting and structure are absent, or code structure departs significantly from best practice, and/or the code departs significantly from the style guide | Code commenting and structure is limited in ways that reduce the readability of the program, and/or there are minor departures from the style guide | Code documentation is present that re-states the explicit code definitions, and/or code is written that mostly adheres to the style guide | Code is documented at non-trivial points in a manner that enhances the readability of the program, and code is written according to the style guide |
Writeup and Submission (10%) | An incomplete submission is provided | The program is submitted, but not according to the directions in one or more ways (for example, because it is lacking a readme writeup) | The program is submitted according to the directions with a minor omission or correction needed, and with at least superficial responses to the bolded questions throughout | The program is submitted according to the directions, including a readme writeup describing the solution, and thoughtful answers to the bolded questions throughout |
Please refer to the Style Guide for code quality examples and guidelines.