Closed jacobthemyth closed 9 years ago
Before I forget, CRC's & User Stories: https://atm-notecards.divshot.io/?set=homework-02-10
I'm having some trouble with the concept of CRC Classes - what's the scope there exactly? Is my user a class unto themselves? Do I need to break down portions of the app, like separate cards for data retrieval and local filtering? I feel like I'm either waay too granular or not granular enough.
Repo for ApiMashUp here: https://github.com/ATMartin/TIY-HW-17-ApiMashUp
Will implement router tomorrow. It's late. Sorry.
http://img.photobucket.com/albums/v380/poopII/butIamLeTired.jpg
CRC cards are just meant to be an exercise to help clarify the problem / jobs to be done. I usually make a User card, though not an App card. The actual implementation details (data retrieval, local filtering) would not be part of the CRC process. It's meant to develop a vocabulary that you could use to describe the problem the app solves without talking about the actual app (no UI, no ajax or network requests). Not sure if that helps.
Router added to that repo. Thanks!
Added full app & associated files. Thanks!
API Mashup Part 1
Description
You will inventing and creating an app that combines data from two APIs. The only constraint is that it should be cool. Part 1 of this project involves planning the application.
Objectives
Learning Objectives
After completing this assignment, you should:
Performance Objectives
After completing this assignment, you be able to:
Details
Deliverables
main.js
index.html
Requirements
Normal Mode
Additional Resources
Google APIs